Mike Fahl

At some point there was a feature that sent a messag if you named a Control cue with a leading colon (if memory serves me correctly). At least the display software did that, to its primary controller. Perhaps that "hack" is still in there? Worth giving a try. Test it with a telnet client to see if you get something back when running over such a control cue. Mike

For 1, I would not use polling for that. Use the subscription model intead. WO will then tell you when there's any abrupt change. Interpolate/extrapolate intermediate values based on the data you get. For 2, just give it a try. If it works then you should be good to go. Mike

You can send commands and receive error messages related to those commands through the same network (TCP) connection. This is described in the manual. What do you mean by "receive notifications from WatchOut Outputs"? Mike

If you use the subscription model, there's no need to repeat the command. Whilw the subscription is active, WO will tell you whenever there's a change, without you having to poll it constantly. That's the whole idea. The additional parameter follwing "getStatus n" (where n is 0 for start subscription and 1 to end subscription, if memory serves me correctly) is the path to the auxiliary timeline to subscribe to. Without this parameter, main timeline is targeted. Mike

Remember to quote the target cue name if it contains spaces or other odd characters, Easies is to always quote strings. Mike

If you have multiple NICs on your computer, you may need to set the priority order of NICs in Windows so the one used by Artnet is at the top. If not, WO may send Artnet data on the wrong NIC. Mike

Since this happens only after a full restart, and once the system is up and stable does not happen again until the system is restarted, my guess is on some other program, driver or similar running in the background on the display computer. That "other" thing does something that kicks WATCHOUT out of full screen mode after a several minutes. If the problem were caused by some video codec bug, it should manifest even after running successfully ones, since what then happens is pretty much the same on every run of the show. Of course, the tricky part is finding out what that "other" thing is. Especially since it happens so rarely. Mike

Why would it matter if it gets the command twice? They should both say the same thing pretty much at the samr time anyway, shouldn't they? Mike

I see there's a "UDP/TCP Generic module" as well for Companion. Assuming this module can receive data (to trigger commands or "stacks" in Companion) you should be able to use that one, as WO can send TCP and UDP command strings quite easily. Mike

If prod sw and WN runs on the same PC, you should be able to just put localhost into the address field. If they're on separate PCs, put the IP address of the WO prod PC in this field.

This error message translated to its hexadecimal form is 0xC0000005, which makes it easier to google. It's an "access violation", meaning that the program has attemped to access memory it's not supposed to touch. This is usually a bug (e.g., a null pointer access). Not much you can do about it, except perhaps trying to see if you can reproduce it at will, and if so let Dataton know how to reproduce the error in order to fix it. Sometimes, the Windows event log provides more details when such a crash has occurred, which could also help in pinpointing it: https://www.digitalmastersmag.com/magazine/tip-of-the-day-how-to-find-crash-logs-on-windows-10/ Mike

Contrary to what's said above, looping and/or free-running videos are synchronized across computers. Or, at least that was the case when I was involved. I doubt it has changed since. If looping or free-running video gets out of sync across computers, I would have considered that a bug. Mike

m.2 is usually preferable over SATA-based SSD. Beware of the various types of m.2 sockets though, as the number of PCI lanes can greatly affect the performance. Mike

MP4 is a subset of MOV, using the same atom-based file structure. So it can be confusing. It's really what's INSIDE the file that matters, not its file extension most of the time. Mike

Here's a complete list of QT error codes: http://mirror.informatimago.com/next/developer.apple.com/documentation/QuickTime/APIREF/SOURCESIV/errorcodes.htm The error you see is "noCodecErr", indicating the file uses a codec that can't be found. Since HAP codecs are built into WATCHOUT, QuickTime isn't needed to play such files. But if your file is using an unsupported odec (or an unsupported flavor, as Jim suggests), WO likely falls back on attempting QT (if available), which then fails with the above error. If you have QT on the machine, you can open the file using the QT app, and it may be able to rell you more about what's in the file. If you know it is some form of HAP, it may likely be the "HAP Q Alpha" flavor, which, as Jim says, isn't supported. Mike