WATCHOUT 5.5 - how to set up frame-lock?

[diezweiundvierzig]

can you help me with setting up two machines, each ati V7900 and s400-boards to get the sync from one machine to the other? it won't work! the settings for timing server (nor internal from display either from genlock) will be send over rj to the second machine!

 

we have 5 outputs. 2 @machine 1, 3@machine2. all 1280x1024 for led-wall.

 

I can set it up as it should, but the "green check-boxes" disappear after a few seconds and no sync is established. the gen-lock led is flashing green all the time...

 

whats the issue??? any ideas?

 

machine1 setup:

 

and

 

 

and

 

 

 

machine2 setup:

 

 

and 

 

 

and after a few seconds:

 

[Jonas Dannert]

Hi J. Hopp,

 

Make sure that the S400 settings are correct and complete:

1) Go to the AMD Catalyst Pro software on the first system and set output 1 (i.e. Display computer 1/Display 1)  and make it "Timing Server"

2) Check all other display outputs boxes as "timing clients"
3) Check RJ45 connections as "timing client"
4) Connect the second system with RJ45 cable to the "Timing Client" RJ45 output of the first system
5) On the second system select the connected RJ45 as "Timing Server"
6) Check all display outputs on the second system boxes as "Timing Clients"
7) In WATCHOUT, select the Display that will be syncmaster (i.e. Display computer 1/Display 1), open Display properties -> Advanced and check the box "Use as synchronisation chain master"

There is no purpose for the "House Sync (Genlocked)" unless the outputs need to be synced with video-sources.

If so, do NOT connect the genlock signal to all S400 sync-cards, only to the selected "Timing Server" S400 card.

 

When the hardware side of things is setup, WATCHOUT should adhere to this.

 

/jonas

[diezweiundvierzig]

thanks for that!

 

but: I did it right that way, and the checkboxes unchecked themselfes after a few seconds. now, one day and a lot of "braining", switching, testing,...later: it is working as it should! no idea why not yesterday?!

[jfk]

thanks for that!

 

but: I did it right that way, and the checkboxes unchecked themselfes after a few seconds. now, one day and a lot of "braining", switching, testing,...later: it is working as it should! no idea why not yesterday?!

 

correct me if I am wrong, according to some of your screen shots,

Timing Server is set to to None, so with no timing server, timing client settings will not hold.

[mcsmokey]

 

Hi J. Hopp,

 

Make sure that the S400 settings are correct and complete:

 

1) Go to the AMD Catalyst Pro software on the first system and set output 1 (i.e. Display computer 1/Display 1)  and make it "Timing Server"

2) Check all other display outputs boxes as "timing clients"

3) Check RJ45 connections as "timing client"

4) Connect the second system with RJ45 cable to the "Timing Client" RJ45 output of the first system

5) On the second system select the connected RJ45 as "Timing Server"

6) Check all display outputs on the second system boxes as "Timing Clients"

7) In WATCHOUT, select the Display that will be syncmaster (i.e. Display computer 1/Display 1), open Display properties -> Advanced and check the box "Use as synchronisation chain master"

 

There is no purpose for the "House Sync (Genlocked)" unless the outputs need to be synced with video-sources.

If so, do NOT connect the genlock signal to all S400 sync-cards, only to the selected "Timing Server" S400 card.

 

When the hardware side of things is setup, WATCHOUT should adhere to this.

 

/jonas

 

Why not feed every S400-card with its own genlock? just curious

 

regards

Robert

[Jonas Dannert]

"Why not feed every S400-card with its own genlock? just curious"

 

Partly because video genlock does not equal graphics card framelock.

 

One AMD FirePro S400 (or NVidia QuadroSync) sync card and it's corresponding graphics cards 1st output, acts as Timing MASTER for a system,

all other outputs and their sync & graphic cards, acts as Timing CLIENTS. 

They are connected together through short RJ45 Cat5 cables, not running TCP/IP, but sync clock signal.

 

If a video genlock signal is required, it should normally ONLY be connected to the Timing MASTER's sync card.

 

/jonas

[diezweiundvierzig]

"Why not feed every S400-card with its own genlock? just curious"

 

Partly because video genlock does not equal graphics card framelock.

 

One AMD FirePro S400 (or NVidia QuadroSync) sync card and it's corresponding graphics cards 1st output, acts as Timing MASTER for a system,

all other outputs and their sync & graphic cards, acts as Timing CLIENTS. 

They are connected together through short RJ45 Cat5 cables, not running TCP/IP, but sync clock signal.

 

If a video genlock signal is required, it should normally ONLY be connected to the Timing MASTER's sync card.

 

/jonas

thx jonas. I did it right the right way - as I ever do! but this time, it won't work the one day - the other it did and does (and still does).

but all the time, there was no chance to get the genlock working in the Timing Master!

[michalp]

You send genlock timings for resolution 576i@50Hz, displays are 1280x1024@50 so resolution is diferent, I thing that is the problem.

try to send genlock 720p@50 and displays resolution 1280x720@50Hz. Or same scheme 1080i....

We use that and its working.

[Alex Ramos]

You can't use a genlock different from the screen frequency.

 

For exemple. 

Working in a 50hz TV studio, and using WO to drive LCD wall that only work at 60hz, its NOT possible to use house sync. 

The only option were is to use one of the outputs as Timing server.

[michalp]

Genlock signal is not only 50Hz or 60Hz, it contains components that define resolution.