Peter

Hi Angelica: Thats good to know! Thanks for the update. Just wondering, do you know if the NDI discovery server feature (included in NDI 4.0) will be added to this next version of WATCHOUT build as well? Regards, Peter

Just wondering, any chance that dataton can look into updating WATCHOUT support for NDI to version 4.0 or above and include NDI discovery server support? I run large amount of NDI stream via WATCHOUT and the ability to use discovery server will allow for much more stable source discovery instead of using mDNS (NDI 3.8 or below). Regards, Peter

Would love to know about the same thing as well. NDI output will be useful in my particular use case as well.

Hi everyone, I am just evaluating WatchOut 6, and I am trying to use WatchOut 6 to create a more interactive show / event that is tie into a game. To do that, there is a requirement for us to sent some triggering signal from the game (an external sources) and then once WO6 receive the signal, then WO6 will then trigger different certain layer of animations or effects, etc. The source of these signal could be from another computer in the same network, or it could be a physical button, etc. So this is where I get confuse by looking at the WatchOut 6 manual. From what I read, WatchOut can take MIDI input (audio), and DMX input (lighting), but how does generic WatchOut Input work in WO6? Can it accept signal / trigger from another computer on the same network? If so, how does this get implemented, or how does the communication being handle? I couldn't find any reference or examples on how this is done. Like, what kind of protocol does the signal being transfer? Is it via TCP/IP? Or is there a specific API that allow the communication, etc? Is there anywhere that I can find an examples or reference? If anyone can give some reference materials or some help on this area, that will be great. Thanks for your help in advance. Regards, Peter