Jump to content
Dataton Forum

Jeff Miller

Member
  • Content Count

    11
  • Joined

  • Last visited

Everything posted by Jeff Miller

  1. ADDENDUM: I am using the computer names of course. But today I learned a lot more about this issue. Changing the frequency works because when you then go online it pushes out the modified show to the display computers. Today I was able to run the show from the production computer at both 60hz and 59.94hz in sync. However, if I change the frequency and then go online, but start playing the show too early, apparently one of the display computers is getting the changed frequency and the other isn't and it plays out of sync (even with the production computer). Now, still, if I have
  2. I have a show running on two display computers. There are 9 screens. 5 on one Display Computer, 4 on the other. Watchout 6.3.1. Planar screens and extenders. The show was set to 60hz framerate. The two computers would play together, but be slightly out of sync. By less than half a second. I discovered if I used the Preferences in Watchout Production and set to 59.94hz, it played in perfect sync. When I take this same show and use Autostart to have one computer drive the show without the Production computer, it goes back out of sync. I tried switching which one is the master, and it is alw
  3. I have a complex Show on 4 display computers. Unfortunately, 2 of the computers have the new AMD WX9100 card and are not always stable. I have done a lot of work to keep them happy, but still there is an occasional hiccup and Watchpoint crashes. Watchdog catches it and restarts Watchpoint. Watchpoint enters the show. However it just stays on a single frame and does not run with the rest of the cluster. Is this the usual behavior? Is there any way to configure the cluster such that it will be picked back up and resync? One other note on this. In order to get the WX9100 cards to run,
  4. Thank you for posting @piccinaezio It is nice to know I am not alone. I am currently still working with 2018 Q4 drivers. It works, but I am severely limited as to what I can do in the show if I want it to be stable (run for 24 hours reliably). I ran a show on 2 of my display computers with Nvidia P5000 and P6000 cards for 36 hours clean. I put the same show on the AMD WX9100 computers and it crashed one of the display computers after running 15.5 hours. No logs, no dumps, no indication of why. All the screens on that computer show "no signal" although the computer still seems to be on. No
  5. UPDATE: We upgraded graphics cards to the AMD FirePro WX9100. We were running a show on 2 computers. After a period of time ranging from 4 hours to 12 hours, one of the display computers freezes in playback for ~33 seconds and then all signal is lost on all 6 screens. The computer is still on, but does not respond to anything and there is no way to get video signal back. Had to use power button to shut off. Because of this I went back to 2017q4.1 drivers as suggested above. I am currently running long term test on this. However, with Watchout 6.3.1 and these AMD 2017 Q4.1 drivers I can no
  6. I have a show that runs on 3 computers. Watchout 6.3.1 Dell 7920 Rack Intel Xeon Silver 4114 2.2GHz, 3.0GHz Turbo, 10C, 9.6GT/s 2UPI, 14M Cache, HT (85W) DDR4-2400 1st Windows 10 Pro for Workstations (4 Cores Plus): Fully Tweaked with Dataton guide 2.5" 512GB SATA Class 20 Solid State Drive 16GB (2x8GB) 2666MHz DDR4 RDIMM ECC AMD FirePro W9100, 32GB, 6 mDP, (7920 Rack) The show is a ~3 minute cycle. The show ran for 21.5 hours and then the computer that launched the show (the master) logged the following in the watchdog log: { "date" : "2019-01-11", "time" : "7:29:26:9
  7. Is there a site or document that can tell me what a WATCHPOINT exit code might mean? I have gotten a WATCHPOINT exited abnormally code 3221226356, but I don't know what this is telling me.
  8. I am using the most current 2018q4 AMD drivers with no problems. Although I am not using midi or remote access.
  9. Quick follow-up. I just installed WATCHOUT 6.3.1. Now I can launch WATCHPOINT.exe and it runs the display program properly. I will now test out some of the other issues I was having.
  10. Here is what I am working with: Dell 7920 Rack Intel Xeon Silver 4114 2.2GHz, 3.0GHz Turbo, 10C, 9.6GT/s 2UPI, 14M Cache, HT (85W) DDR4-2400 1st Windows 10 Pro for Workstations (4 Cores Plus) Multi - English, French, Spanish 2.5" 512GB SATA Class 20 Solid State Drive 16GB (2x8GB) 2666MHz DDR4 RDIMM ECC AMD FirePro W9100, 32GB, 6 mDP, (7920 Rack) WATCHOUT 6.2.2 I have completed modifying the Windows 10 with the Windows 10 Enterprise Tweaking Guide. I can run WP.exe. It runs as follows: 12 seconds all screens go Black. 18 seconds all screens go back to desktop. 42 s
×
×
  • Create New...