kFrogStudio Posted March 2, 2020 Report Share Posted March 2, 2020 Hi We need some help with a WO instalation of a client that has a WO player running 6x 4k@30Hz. We were asked to setup the show but before we were able to do any of that we had a battle just to get WO running on the 6 Outputs. System: OS: Windows 10 Enterprise 2016 LTSB CPU: i7-7820X @ 3.60GHz Ram: 16Gb Graphic Card: WX9100 8Gb Outputs: 6x Mini DisplayPort 1.2 to HDMI 18G with HDR Active Converter Signal: 6x Kit Tx+Rx Extron 330 DP Display: 6x Samsung Videowall 3x3 Step by Step 1º - Setting the right Edid to be emulated on the graphic card. Getting the right combo of EDID emulated on the graphic card was a nightmare. First we were able to setup the system and run the full 6 outputs on windows environment. Since we had limitation on the resolution that the Extron extenders supported we tried to get everything working at 4K @ 30Hz @ 8bits. When we were able to get this working, with image on all 6 videowalls we start running WO and all hell broke loose... As soon as we started launching the Watchpoint.exe we got in trouble... what happen was something that I've never experience with WO before. When we run Watchpoint.exe it would behave as aspected, it would show the logo, do the countdown that we set and then... all went black... and everything crashed... sometimes we would get control after some ctrl+w or ctrl + alt + del, but most of the times we needed to reboot the machine... Since we had this troubles we reverted the configuration to 6x1080p@30Hz and everything worked.. We loaded a show, set a autorun.txt and everything worked as expected. When we reverted to 4k we got the same trouble all over again.. For debug we started adding one screen at a time and some times we were able to configure 5x displays, but the end result was always the same.. WO would crash after the logo and countdown. ALL BLACK on 6 outputs and windows crashed.. After a lot of trial and error and to many reboots we managed to figure it out.. The main cause of the crash was the Edid that was emulated on the graphic card... although everything worked in windows environment and with multiple displays with that edid, the system wouldnt run with all of the 6x outputs... Everything started to work when we introduced a new Edid that was created by us, based on the Samsung Lcd original Edid.... 2º Problem - Error on Autorun show. "No Show Available" Now we have a even more strange problem. Everything is working, the show is setup correctly and loads on start up via a autorun.txt. Coollll .. but when we disconnect the display server from the network (unplug the ethernet cable) the system wont load/run the show from the autorun.txt and would result on the crash of the WO system and present a console with the error on the display... Basically the display configuration of WO is not running as it should without the cat5 cable connected and active on the player... and because of that when the show tries to run it crashs.. If we reboot the server with the cable connect to a active source it all goes as aspected. Does anyone had this problem and know why this strange behavior ? Thank you all Composição 2.mp4 Composição 1.mp4 WATCHDOG_00001.log WATCHPOINT_00001.log 0 Quote Link to comment Share on other sites More sharing options...
Dataton Partner Benoit Posted March 2, 2020 Dataton Partner Report Share Posted March 2, 2020 Hi, Windows is probably configure to not set the IP address if network cable is not present. Try to remove the autostart, remove the network cable and start watchpoint. What IP address is shown ? Rgds, Benoit 0 Quote Link to comment Share on other sites More sharing options...
kFrogStudio Posted March 2, 2020 Author Report Share Posted March 2, 2020 5 hours ago, Benoit said: Hi, Windows is probably configure to not set the IP address if network cable is not present. Try to remove the autostart, remove the network cable and start watchpoint. What IP address is shown ? Rgds, Benoit Thank you for the help. I Have set everything as it should in the network properties. Fixed IP, and only ipv4 on. WO shouldn't run the show? It always check the ip of the display? But where can I enable or disable that function on windows? I will test that when I get back to the client Thank you 0 Quote Link to comment Share on other sites More sharing options...
ectoplasmosis Posted March 2, 2020 Report Share Posted March 2, 2020 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 Quote Link to comment Share on other sites More sharing options...
kFrogStudio Posted March 2, 2020 Author Report Share Posted March 2, 2020 9 hours ago, ectoplasmosis said: 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. The display was acquire by the client from a WO supplier and was already on premise. I'm supposing that it should be already optimized for 6x 4k. So it's best to check all the registry? That information is not on the tweak list, but rather on the forum, right? Just anyone can check if all the drivers are the right ones? Thank you all. 0 Quote Link to comment Share on other sites More sharing options...
ectoplasmosis Posted March 3, 2020 Report Share Posted March 3, 2020 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 Quote Link to comment Share on other sites More sharing options...
Muath I J Posted March 11, 2020 Report Share Posted March 11, 2020 Here is my suggested trouble shooting method to save your time to know which output is giving you a headache : 1- remove the force EDID from all outputs (if its forced ) and unplug all outputs except for output 1 then restart the machine. 2-in WO production deactivate all the outputs except output 1 by ticking the box (use this display ) . 3- now make sure u have set the proper EDID that matches output 1 config. in WO and try to go online ( without forcing the signal). 4- now if it worked keep adding one output at a time and go online, until you find which output is causing the issue then troubleshot that output. ***please note when forcing the EDID make sure you upload the file to each output separably and never copy it from another output as it may cause EDID conflict. Best of luck 0 Quote Link to comment Share on other sites More sharing options...
kai Posted March 13, 2020 Report Share Posted March 13, 2020 On 3/11/2020 at 8:23 PM, Muath I J said: Here is my suggested trouble shooting method to save your time to know which output is giving you a headache : 1- remove the force EDID from all outputs (if its forced ) and unplug all outputs except for output 1 then restart the machine. 2-in WO production deactivate all the outputs except output 1 by ticking the box (use this display ) . 3- now make sure u have set the proper EDID that matches output 1 config. in WO and try to go online ( without forcing the signal). 4- now if it worked keep adding one output at a time and go online, until you find which output is causing the issue then troubleshot that output. ***please note when forcing the EDID make sure you upload the file to each output separably and never copy it from another output as it may cause EDID conflict. Best of luck Hi, Thank you so much for share your tips, KAI 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.