Miro

This is not an easy task because different media use the hardware very differently. For image sequences and HAP you need a lot of disc bandwidth while other media have RAM and CPU bandwidth as bottlenecks. There are some good tools to monitor CPU and GPU load remotely but most tools are very bad at monitoring memory and disc bandwidth. We will look into this and compile a testshow that we can upload after ISE.

Sounds like a firewall problem. The WATCHPAXes needs to access the production computer in order to download media.

Hi, the card is working and we have both the 4x HDMI and 4x SDI on our test bench. For WATCHOUT 6.1.5 (released by the end of this week) we use Magewell's low latency mode but the latency is still 1-2 slower than Datapath's cards. WATCHOUT 6.1.5 also adds better support for their USB devices as well (or any USB video capture that uses standard microsoft drivers).

There is a very ugly hack if the cue if compatible with the older version. 1. Copy the cue from WATCHOUT 6.1.2 2. Paste it into notepad 3. On the third line change "WATCHMAKER" 6 1 2 0 to "WATCHMAKER" 6 0 2 0 4. Select the whole text in notepad and copy it. (Ctrl+A and then Ctrl+C) 5. Paste to WATCHOUT 6.0.2 If you lucky it works. =) We need to improve the compatibility within major versions in the next major version.

Hi, I tested the WX 7100 a couple of weeks ago and it has the same bug. Also gamer hardware like Radeon RX and semi-professional cards like Sapphire GPRO has all the same problems.

Can it be related to this issue: http://forum.dataton.com/topic/2248-watchout-614/?p=9522

Hi, three 4K shouldn't be a problem with AMD but there is a bug in their driver preventing DirectX9 to run 4x 4K. AMD are working on this issue and I hope they find a solution soon. Nvidia don't have these problems in windows 7 and the WATCHPAX4 can drive 4x 4K screens at 60Hz. For the AMD W9100, are you running displayport all the way? Technically the card is capable of at least 3x 4K@60Hz and 6x 4K@30Hz but you need to have proper cables and adapters. If running 60 Hz you also need to enable displayport 1.2 in some monitors.

Hey, I just spent some time testing DMX by setting up two WATCHOUT production computers, where one sends DMX outputs to the other's DMX inputs and the other way around. I could reproduce similar glitches when changing universes while beeing online. However, if you restart WATCHOUT and go online again then the problems are gone. Obviously, something isn't cleared properly when switching universes and will be fixed in 6.2. A tip is to run this software to monitor your DMX network to see which device is sending what: http://www.lightjams.com/artnetominator/ Best Regards, Miro

Or re-arrange your disks and plug the windows disk to the 3 Gb/s SATA2 port. 300 MB/s should be enough for booting & running windows. The RAID-0 partition will speed up from 600 MB/s to ~900-1000 MB/s depending on your disks. I depends on what you want to run. As example a 4K UHD HAP Q video in 60 Hz will use around 400 Mb/s..

As I said before.. "We will add better support for network video in 6.2 but at the moment its a bit tricky to do stuff like this."

Hi, WATCHOUT will use the same display configuration that you have setup in your display driver. If you have mirroring enabled then WATCHOUT will use that and mirror your displays. So you need to setup your displays correctly in AMD's, NVIDIA's or Intel's control panel first. The settings are usually stored per display so if you change displays you need to update your settings unless you use EDID emulation.

Hi, there is a texture size limit for DirectX9 on the GPU which normally is 16K x 16K. It's much smarter to rearrange your LED tiles from 30'000x850 on an area corresponding to 4x UHD 4K monitors like 7680x4320. The media will probably be more coding efficient also. WATCHOUT uses frame sync but not swap sync/barrier so if the computers in the cluster are too slow they might miss a v-sync interval every now and then. One computer could drop a frame which will cause tearing if it's neighbors doesn't drop the same frame.

Hi, We don't supply a AAC decoder so WATCHOUT will use any directshow filter available on your system. Do you have the same audio problem in WATCHOUT 6.1.4?

When a HAP is dropping frames it's usually when the power plan is not set to "High performance". The "Balanced" power plan that is default in windows is clocking down the PCI bus causing the HAP to stutter. However the timeline shouldn't stop. Do you have something else on the timeline simultaneous as the HAP?

Hi Kate, first you must make sure that your display computers supports WOL (Wake On Lan). WATCHOUT will record the information needed for WOL when shutting down the display servers and then broadcast the WOL magic packets when a startup is required. Most computers don't have this feature enabled and some don't even support it. I just did a quick search and you could look at these links: http://windows7-issues.blogspot.se/2011/03/wake-on-lan-wol-for-windows-7-made-easy.html http://www.howtogeek.com/70374/how-to-geek-explains-what-is-wake-on-lan-and-how-do-i-enable-it/ I hope this helps. Best regards, Miro

Hi, it shouldn't really matter but I would recommend to uninstall the old version and then install the new version on the production computer. Then you can push the new version to the display servers when you go online.

If you still have problems with clicking/popping sounds then it's probably not a bug in WATCHOUT but an interference problem between the GPU and sound device on the PCIe bus. This issue occurs on relatively new computers (including WATCHMAX) with Intel C612 or X99 chipsets. This interference comes when the GPU changes it's clock frequency. This occurs more often with AMD hardware than with NVIDIA cards. The problem is not limited to WATCHOUT and can be triggered in any application as soon as audio and video are played simultaneously. The solution to this problem is to force the PCIe link speed for the GPU. We will be testing this fix and include it in WATCHOUT 6.1.5 if it works well. Until then you need to set it manually. Run regedit Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\4D36E968-E325-11CE-BFC1-08002BE10318\0000 Create a DWORD (32-bit) Value named “ForcePcieLinkSpeed” and set the value to 3 Reboot If you by any chance have a 0001, 0002 or 0003 folder in the 4D36E968-E325-11CE-BFC1-08002BE10318 folder then repeat step 3 in all these folders. Best Regards, Miro

Thomas, your jumping issue should be resolved in the latest release: http://forum.dataton.com/topic/2248-watchout-614/

WATCHOUT 6.1.4 has been released and you can download it here: http://www.dataton.com/downloads/watchout Release notes: Dataton WATCHOUT® version 6.1.4 Resolved issues Fixed error in WAV file playback that was introduced in version 6.1.3. It occurred only when playing the audio repeatedly, either by using looping, or by using control cues.

Just to clarify.. mp4 is a container that can contain different video streams encoded with codecs like H265, H264, H263/MPEG-4, etc. Decoding H264/AVC compared to H263 on a CPU is usually a bit heavier since H264 is a more complex codec (better compression). What's the resolution and frame rate of the 26 video streams? Is the quality the same using wmv compared to H264? Also we don't supply any wmv codecs so this depends on whats installed on your system.

The current version of NDI is also running using TCP. It syncs pretty well but is a bit bandwidth heavy. 1080p at 60Hz needs slightly more than 100 Mb/s per stream/server for filmed content and a bit less for computer generated content. The latency in NDI is usually 1-2 frames.

It's because we don't supply (nor license) the DVCPROHD decoder. But you could install that codec as a directshow filter and then WATCHOUT should be able to use it. WATCHOUT prioritize it's installed codecs but if no match is found then it looks whats available on the system.

We moved the issue to be solved in WATCHOUT 6.1.5. It needs to be tested before release and right now there is no time since 6.1.4 will be released today.

Yes, gathering statistics like dropped frames is something we are looking at in future versions. //Miro

What do you mean exactly? As a media item?