jfk

FYI that 'feature' only works for control cues in the main timeline. And it only works in cluster mode, it does not work in production mode.The sting is sent to an active control connection (port 3039).

No, active adaptors will not change the behavior. Provided all displays are powered on and available prior to WATCHPAX power up, and providing the WATCHPAX is powered down while all displays remain powered up and active - the display output numbering should not change on the next power up. Adding hardware EDID managers will allow you to achieve the necessary active displays at power down and prior to power up if need be.

You might try 1080i30. Seems some vendors indicate 1080i60 when they mean 60 fields per second, while WATCHOUT means frames per second, and since there are two fields per frame, 1080i 60 fields = 1080i 30 frames.

Depends how you define "proper synch". AMD cards require an S400 to achieve ScanLock, even with a single graphics card. (nVidia Quadro cards will provide ScanLock with a single card and no synch card).

BTW WATCHOUT 6.6 was released last week and includes support for NDI 4.1

No, RTTrPM is an open source protocol that is available to anyone, it is not a proprietary protocol.

The protocol for position value motion tracking supported by WATCHOUT is RTTrPM (Real-Time Tracking Protocol - Motion). A google search of the kinesys / manufacturer's website for the RTTrPM protocol comes up blank. Google search for RTTrPM on kinesys.com So it does not look promising.

You did not indicate your WATCHOUT version. There may be a bug related to output cues on aux timelines in some versions of WATCHOUT. For testing, try putting the cue in the main timeline.

HEIC will not open inn MAcOS Sierra, so I cannot see your images. Never seen an issue with the output of the logo screens being blurry, very strange. BTW Always indicate the WATCHOUT version you are asking about.

sort of. It is about how the specification is interpreted. With interlaced video, there are two fields per frame. (Progressive video does not have fields, only frames). I see some vendors who define interlaced 25 frames as 50 fields. i.e. 50 fields per second interlaced equals 25 frames per second interlaced.

There is no guide on how to program Crestron. External control of WATCHOUT Display (cluster mode) is documented in the WATCHOUT User Guide. The information needed for any control system programmer is there. I am aware of numerous WATCHOUT systems operating in cluster mode controlled by Crestron systems. A very impressive one driving a flat panel wall behind a small stage off of the casino area at Ceaser's Palace. That system automatically picks up shows available on the display machine and provides a menu to choose from. Once a show is selected, it automatically finds all the tasks (aux timelines) and provides menus to run and control them. So if you edit the show, or add new shows, the control system just incorporates the changes without any change to Crestron programming. Very impressive. BTW Those are the same functions demonstrated in the old sample Adobe Flash program - WATCHOUT Remote (now discontinued).

The best way to move a show is via the function built-in to watchmaker for exactly that purpose, File - Consolidate To ... This allows you to save the result anywhere you want. Granted, that is not convenient going back and forth. But it is the most foolproof way to accomplish the task. Otherwise, you must be precise in the location you store your media assets. It is critical that you maintain relative file references for media by storing all media assets in the folder where your .watch file is located or subfolders of that folder. If you maintain this on all your computers, you should be able to move the new .watch file and any new assets back and forth.

Agreed. They are a side effect of a single basic error that is not shown in your list. You may have to look in the watchpoint log file to discover additional info.

Thanks all for the feedback on performance. When providing such useful information it would be helpful if you included the WATCHOUT version providing the observed performance.

Yes, the WATCHOUT License (USB key) must be connected and watchmaker must be online to send ArtNetDMX output. (there are some versions with a bug where some outputs work offline, but do not count on it).