ectoplasmosis

Any ideas?

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.

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.

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.

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.

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.

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?

I wouldn't use MP4 content or a consumer-grade M.2 SSD.

Another voice calling for the return of seamless standby updating behaviour. The black flash across all screens in version 6.5 is unacceptable during rehearsals.

Reliable looping between cues on aux timelines is possible using the methods above, providing your server hardware is powerful enough. SSD IOPs and read speed, GPU horsepower and PCIe bandwidth must be sufficient and balanced to enable seamless and accurate jumping between cues whilst playing high-bitrate non-keyframed content. Our 6-output servers can happily loop 6x 4K60fps HAPQ video layers in aux timelines simultaneously with no blank frames.

Any progress with fixing this bug? Thanks!

... As for WoL; ‘SFP+’ was meant as a qualifier as I’d only ever use 10GbE over fibre/DAC and never 10GbaseT over copper due to excess heat and reliability issues with Aquantia NICs.

No 10Gb SFP+ NICs that support WoL as far as I know; the SFP+ modules would need to be powered for WoL to work. I don't know about 10GbaseT as I avoid it due to heat & cable quality issues.

This wouldn't work as the bug is induced by the amount of actual displays connected to (or emulated by) the display server, regardless of how many displays are part of a project. I will be manually transferring content via SMB networking in the mean time. This consistently hits the full 10Gb/s speed that the hardware is capable of.

Hi Joakim, 6.4.1 is the only version that I have tried as this is a new build. I'm assuming this problem is a combination of Watchout transfer protocol and network adapter settings? If you could assist that'd be very much appreciated.