ectoplasmosis
-
Posts
37 -
Joined
-
Last visited
Posts posted by ectoplasmosis
-
-
-
Why are you using a crossover cable? It isn’t 1995...
Try a straight-through patch cable, or via a switch.
0 -
Watchout can certainly play 4K50/60 media, and much higher resolutions, with no problem... if your display servers are specced, built and configured properly!
Our Watchout servers happily play 12x 4K60 media via 6x physical 4K60Hz outputs, WX9100 GPUs and Samsung PM1735 PCIe 4.0 SSDs. Fully framelocked, zero dropped frames.
0 -
The culprit, in my case at least, was definitely the crapware that VMix installs with it (Haali Media Splitter, VMix codecs, etc etc).
Having removed those, but kept VMix, everything now works fine, including VMix.
0 -
Updating the GPU driver is your problem.
0 -
On 7/11/2022 at 9:16 AM, matkeane said:
the culprit appeared to be vMix.
Thanks for your detailed reply; since writing mine, I had also determined the culprit to be VMix, in particular the codecs and ancillary applications that are installed along with it.
After removing those, Watchout and VMix now happily co-exist, with HAP files of all flavours playing as they should.
0 -
Did you ever fix this problem? I'm seeing it on a new Win10 production laptop also...
0 -
Threadripper/EPYC is great, especially for ProRes/TGA image sequence playback (lots of cores).
0 -
You could build a single mammoth EPYC/Threadripper Pro based machine with 3x A5000 GPUs, running Watchout in 3x VMs on VMWare/Proxmox or similar... or you could build 2x much cheaper machines based on a consumer Ryzen/i7/i9 platform with a single AMD WX9100 each, running Windows on bare-metal, giving you 12x total 4K60 outputs for 48x 1080p60 via FX4s.
Will cost less and be likely more reliable.
0 -
Display output numbers will commonly switch, seemingly at random. Make sure to note output numbers shown on the Watchout display splash screens, and use those for display output assignments within the Production software, instead of the Windows/GPU output numbers.
0 -
Thanks for letting us know that you're at least reading this thread.
What would be really helpful is some kind of high-level roadmap for Watchout, specifically in relation to the possibility of implementing major features like Notch, which would directly affect current purchasing decisions.
Your competition seem to be much more open with their plans, which inspires confidence and leads to sales.
0 -
None of the above techniques will work with high-bandwidth HAPQ files, for example; you will experience a flash of black unless you use the ‘jump to cue’ method of looping.
0 -
Or Tyan Tomcat HX S8030 if you can make use of PCIe4.0
0 -
Asrock Rack EPYCD8-2T/R32
0 -
Sounds like you need to contact the server supplier and request that they diagnose why their machines aren’t functioning properly. There are too many variables to list here.
I have had no issues outputting 6x 4K60Hz from the WX9100 servers that I have built; there is no technical limitation with this GPU.For reference, I use Radeon Pro driver 17Q4.1 with Win10 LTSB 1607.
0 -
Do not use Windows 7 with the WX series.
0 -
Have you tweaked your display machines properly?
It’s essential that the display setup timeout registry entries are properly applied when using multiple high-res outputs from a single machine, otherwise you’ll see effects similar to those you’re describing.
0 -
-
Hi, thanks for the reply.
1. No, I have not been able to make the Dynamic Image Server work with any image type, only ‘Desktop’ mode.
2. Yes, the media is located in ‘D:\WATCHOUT\IMG\’, and the defined path is ‘IMG’ as per the user manual. I have also tried setting the path as a shortcut string when launching DIS. If the path is not set, or set incorrectly, the image icon does not show in the DIS window, and it doesn’t crash (but also doesn’t serve the image due to incorrect path).
I’ve attached the dynamic image media item window below.
0 -
Yet another request for NotchLC codec support.
HAP quality is inadequate for many types of content and ProRes/TGA image sequences are too resource-intensive.
0 -
I'm trying to use Dynamic Image Server to host PNG image files; Watchout 6.5 on Win10 LTSB 1607.
When I add a dynamic image on the production machine and select the 'Desktop' option, everything works fine and I can see the desktop image on the display machine output.
When adding a dynamic image with the 'Image' option selected, this causes the Dynamic Image Server to crash.
I have tried using PNG and TIFF files with the same result.
0 -
On 2/12/2020 at 9:50 AM, David Laser said:
why? Do you have any M2 to recommend?
No, I would never use any M.2 drive in a production display machine; they all eventually overheat and throttle when run near the limit of their capability, even with active cooling. The boards are just too dense, and the controllers aren't designed for continuous operation at high load.
We only use industrial PCIe SSDs which run forever without throttling and have capacitor-based power loss protection.
0 -
All our machines are running 17Q4.1, all newer driver versions have problems with HAP playback (power throttling related).
I have just tried running 6x 1080p60Hz displays from two of our W9100-based machines with the above listed software component versions; everything is working fine, no problem at all.
It does take ~15 seconds for WATCHPOINT to settle down and show the logo screen with IP address once all 6 outputs are loaded, but aside from that, everything is working as it should.
0 -
No problem with 6x 1080p60 outputs on W9100/LTSB 1607/6.5 here. Also running 6x 4K60 using WX9100 fine.
Have you tried emulating EDIDs per port, one by one?
0
Problem with audio in HAP files
in WATCHOUT FORUM
Posted
ShutterEncoder is just a GUI for ffmpeg, and ffmpeg's HAP output quality is terrible.
Pay the money for Jokyo, it's worth it.