RBeddig

ด้วยความยินดี

Hi Kai, To calculate the conditional layer, you need to add all the conditions... To turn all conditions on is 1073741823. If you then add another "1", you'll turn all conditions off. enableLayerCond 1073741824$0D condLayer.watch

Did someone say so? The HAP family of codecs is widely used on media servers - not only WATCHOUT - as it allows for very large videos in a reasonable to good quality, depending on which flavour of HAP and encoder you're using. With HAP files you can probably play 20+ FHD@60 videos over 4 outputs at the same time if you have a powerful server. The HAP codec compresses videos! The difference to other codecs, e.g. H.264, is that you'll see very little load on the CPU when playing back such files. HAP is actually more compressed than HAPQ. HAP uses less color depth which may lead to banding best visible when using computer generated gradients. HAPQ is a codec with 8bit color depth and better on gradients but it takes quite some space on your SSD and you'll need pretty fast ones too. Never embed audio in HAP files! H.264 is rendered using the CPU and you'll see that the CPU load will be pretty high when playing larger H.264 files. There is also a limit of the actual pixel size when using H.264. With some experience and following the numerous tips on encoder settings (no b-frames, fastdecode,...) you can create high quality H.264 files to be used on WATCHOUT servers. You can even encode H.264 files with very little compression using an i-frame only setting. Then your files will get bigger of course. As Jim said, you should pack your H.264 files in a MP4 container. But be aware, the load on the CPU will be much higher than playing HAP or HAPQ files. MOV and MP4 unfortunately say nothing about the actual encoding. It's just an envelope for your encoded video. Important is, what's inside, like HAP, H.264, H.265, ProRes, Animation,...

What you are referring to are Artnet values, not strings sent via TCP/UDP. Different kind of control but also doable with WATCHOUT. Generate DMX outputs, connect a WATCHOUT dongle and send the values on the Artnet universe and channel which is probably explained in your manual. Note, that Artnet control can lead to false commands since Artnet usually uses a ramp to the value you want to send. This means, if you want to send the value 200 from the current value 0, it may also send some of the values in between before reaching 200.

Their may be two reasons for this: a) you have installed a third-party codec set on your computer which then can "steal" the playback capability from WATCHOUT b) your MP4 files are actually H.265 files which are not supported by WATCHOUT 6. They are supported in WATCHOUT 7.

Maybe rather $24(PVC:muteState)$0D$0A As Jim explained, the dollar sign "$" is a reserved letter inside WATCHOUT. It defines that the next to numbers/letters following a "$" sign are the hex-code for an ASCII letter or a non-printable ASCII code. Other software use other letters to describe a hex-code. The hex-code for the letter "$" is often defined as "x24" (you can find many lists and pictures on www to show you the relation between ASCII and hex-values) where "x" in this case also just tells you that the number is a hex-code. So if you need to send the letter "$" as the first byte of your string, you have to send the hex-code instead. $ > $24 (for WATCHOUT).

There is no command to change display cluster names or such things in the protocol and there are quite a few reasons for that. A way to solve your issues would be to take a closer look at conditional layers and maybe at virtual displays and tiers. Conditional layers can be used to turn layers on or off on-the-fly. You can send those commands from inside WATCHOUT as described by Mickey but a better way would probably be to get yourself a small Elgato Stream Deck or some easy to program control software to send those commands from the outside. In your backup scenario you could route your content through virtual displays before it reaches the "real" display and you could of course route the backup servers to the displays in the same way. As you don't want to show both instances at the same time on the outputs, you'd use conditional layers to make those virtual screens visible which you want to see on the projectors. BTW, there is a video on the Dataton website about backup strategies and this also explains an installation where this approach was used in a fully automated way. https://www.dataton.com/techtalk-video-building-fully-automated-redundancy-for-watchout-in-advanced-fixed-installations Hope it helps!

Can you send some screen shot of your project and how you defined the control cues? I've never seen such issue and we have programmed quite a few projects which work the way you want ti to work.

This message clearly doesn't come from WATCHOUT. If you say, it plays WATCHOUT 5, how old is the display computer? Wrong boot volumes etc. is something I have noticed in the past when the display computer has a RAID set of drives and the RAID got lost in BIOS. This can happen when the CMOS battery is dead.

Yes, media handling will be a bit different with more codecs and content optimization through the new Assets Manager. Display computers will draw relevant content from the Assets Manager and you'll not see any "online" or "update" commands any more as you'll be always online. WATCHOUT 7 has been programmed from scratch as a 64bit application with 16bit internal color processing and much more. While looking more modern and with quite a few user interface enhancements, users of older WATCHOUT versions will easily recognize the producer software and will find most of the well known windows they were used to. With some new ones. Currently it won't be possible to import older shows into WATCHOUT 7.

If you use only one server, are the four outputs of this server in sync? Which LED and controller do you use?

I think this feature was introduced after 2017, together with another few power saving features. The latter then lead to the problems when playing a HAP file since the little CPU load when running HAP made the GPU throttle down.

What sort of adaptors are you looking for? Send me a PM.

Just did a quick scan and reduced the size a bit... Hope it helps! TRANSPAX+ Case Book.pdf

Check out the website: https://www.dataton.com/training/academy-training-videos You'll find several videos on projection mapping here.

Maybe an issue in Companion opening the socket??

Companion has a driver for WATCHOUT (and many, many other event related devices). Create a connection for WATCHOUT, select whether you want to control the production computer or the display computer and then connect buttons with driver functions. Be aware that you need to first enable control of the production computer in the preferences/control window first.

Install Bitfocus Companion software for Streamdeck which has good drivers for WATCHOUT and is free. I would rather install it on the production computer and not the display computer since every extra process on the latter can lead to instabilities. There is also a free but limited version of universe-control which supports the Streamdeck devices. Of course, other solutions are also available but normally with some costs involved.

Wouldn't be surprised if the extender or the cable is the problem. Kramer is not very high on my list of trusted extenders and I have seen integrators running into losses of outputs and content moving to wrong outputs due to bad cables or failing extenders.

Sounds like a driver, hardware or cable issue then.

You mean, the screen turns full red? Or a reddish image? Rebooting WATCHOUT might help for the moment but is probably not a long-term solution. I've not seen such a behavior and I'd suggest to search for the reason. What sort of server are you using? What version of WATCHOUT? How does the cabling between the graphic card and the projector look like?

This looks correct. What you see is the software component watchmaker.exe a.k.a. "watchout" The software on the displays is watchpoint.exe. Just out of curiosity: you're not trying to use a syncboard for your three outputs, are you?

Might be that the 3D mode of the graphic card (which WATCHPOINT uses for performance reasons) doesn't take the non-VESA resolution 4224x1308 50hz while the GDI mode of the graphic card does. I seldom had save and reliable situations where I used very odd custom resolutions. I would definitely stay away from those.

On a WATCHPAX 60/62, you can open the remote control connection from the production software. WATCHPOINT then scales down to a window and in the menu you can find a link to the graphic card settings. Check what the graphic card "sees" as the resolution of your display. If you're sure that your DP-HDMI adaptors support HDMI 2.0, you can try to set the edid setting to the resolution you want to use. Do it one by one so that you can see how Windows reacts to it without loosing the image on the output. The resorting of the outputs when adding or removing a display is something Windows initiates, not WATCHOUT. The only way to prevent this is to use some sort of edid management, either through the graphic card driver or using external edid minders.

Bonjour Benoit, Have experienced this in an installation where one cinema was updated to version 6 while the other still runs version 4. The latter crashed when version 6 went online. In cluster mode though it seems to work. /Rainer