Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited

About stiegzinator

  • Rank

Recent Profile Visitors

516 profile views
  1. After doing some tests, I discovered that Windows 10, in combination with the extenders, were seeing the projectors at a recommended resolution higher than the native resolution of projectors. When I set the resolution to the native resolution, I'd get the 59 Hz error and the scaled down image in the raster. When I raised it to the higher resolution, everything works flawlessly. Still haven't exactly figured out why Windows 10 is trying to force the projectors into a higher resolution.
  2. I'm just now building and testing new Windows 10 builds and I'm running into this exact issue, with a slight addition. WX 7100, Q4 2017 driver, 4 outputs, all with active adaptors as well as EDID emulators to an extender. All 4 outputs are the exact same projector, and when I go online the first time, I get the changed refresh rate to 59 Hz. Was there any solution found for this? The addition that I'm finding is that Windows doesn't seem to be seeing the full raster of the projectors and scaling it down. I have a Windows 7 computer that works perfectly, both on the scaling as well as the
  3. We had this issue happening to us a couple years ago, shortly after v6 was brand new. We ended up creating a work around/check for it, and not really solving the root cause, so couldn't add much to the discussion. My suspicion is that it's something that rarely happened before, but might have been exacerbated with v6.2.2. I can say that we were using display addresses and not names, so that could have still been a factor, as you were guessing.
  4. Does anyone have any recommendations for motherboards for a new Watchout build. Besides the obvious, make sure it's compatible with the processor, what else is a must have? One of the challenges for my particular use is that we have some Dell workstations that we've made into display machines, and one of the settings in the BIOS for those computers is WOL from an S5 state, which from everything I've been reading, is something that I shouldn't be able to do. I'm guessing it's a custom BIOS setting for Dell computers, but not something that is at all standard. The main reason I'd like to m
  5. I'm also wondering about this, myself. I understand how to go about doing it, but I don't really understand what Watchout is doing with one versus the other and why one causes problems. Isn't the IP address just one way of uniquely differentiating between computers? Why would one method of identification be so different from another method?
  6. I could be wrong, but my understanding of Newtek's tools is that they use/need a change of frame, of some sort, to start outputting the stream, which you achieve when you move your mouse and/or reveal the taskbar. Is there some sort of change that you could have programmed into the Scan Converter computer at the top of your cue? On the other hand, if all you're doing is showing still images, is there any way you could have those images in Watchout so you wouldn't need to use NDI Scan Converter at all?
  7. Think of it this way, in a 30 fps video, 1 frame is 0.033 seconds, so your time difference of 45.52 and 45.53 is less than 1/3 of a frame, which does not give you a lot of room for error. My standard practice when programming is to put the pause cue on a .9 and the actual content on a whole number, giving me a 0.1 second gap between pause cue and content; whether it's image content, a UDP cue, or whatever. 95% of the time, the 0.1 second is just fine, but for instances where I want/need it to be tighter, I'll move the pause cue closer to the content.
  8. I was running OS 10.12.6 and Adobe AE 14.2.2. The designer was also running AE 14.2.2 and was on an earlier Mac OS, but I don't remember which one.
  9. I solved the issue. I've reinstalled the Newtek NDI Adobe CC plugin several times, but it took another fresh install after I disabled IPv6 on my Mac to get it to work.
  10. I'm curious why Computer name is preferred over IP address. Does it really make a big difference whether you identify the display on computer name or IP address?
  11. I have the most recent NDI tools installed on a Mac, including the NDI Adobe Creative Cloud plugin. I have the plugin enabled in After Effects to output video preview. I have the Mac networked together on a Watchout production computer. The problem I'm having is that Watchout is only showing a black screen for the NDI stream from After Effects. I've installed the NDI Studio Monitor on the production computer to test the connection, and it's seeing the After Effects stream just fine. I ran NDI's Scan Converter on the Mac, and both Watchout and the Studio Monitor could pick that up, but Wat
  12. When I talked to my IT department about that, their thoughts was that the group policies were something that you could change as part of your work group and would get carried through to all computers that join that work group, meaning you'd theoretically need to only set it up once for all computers. If you build it once and image it across all of your builds, the group policies would be carried over anyways, so I'm not sure how it would exactly save on build time.
  13. I'll give it a try, but since we've had the issue with 2 separate display computers, I'm not sure changing which USB port it's coming out of will change anything, but who knows.
  14. We've been having an intermittent issue in one of our spaces. So far, it hasn't caused any show issues, but it's more of an annoyance for the operators. We're triggering WATCHOUT using MSC from an ETC light board using a MIDI gateway on the lighting network. The MIDI gateway is connected to a MIDIMan MIDISport 2x2 anniversary addition interface that is connected to the production computer. The intermittent problem we're having is that MSC will just stop working. The solution we've found is to power cycle the gateway, close WATCHOUT, unplug and replug the Midiman, and reopen the WATCHOUT show f
  15. Good to know I'm not the only one that thinks that. As an added thing I forgot to mention, remoting into the display computer and going back to full screen was a quick fix that my technician mentioned doing, which to my mind points even more to network issues and not USB. Our next show after we've implemented these fixes is tomorrow, so fingers crossed we don't see it again.
  • Create New...