Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by jfk

  1. Sure sounds like a Windows preparation issue.
  2. Not a lot of information there. Your screen shot shows offline, but not in Standby, please provide more information on the circumstances preceding the “freeze” and describe what you mean by “freeze”? Guess 1 Had a customer whose production server would worked flawlessly in editing and cue to cue run through, but would freeze during a show when waiting in pause for the point in the live presenters script to trigger the next cue. Turns out the run throughs never paused as long as the real shows, and a prolonged pause convinced Windows that a period of inactivity is occurring and
  3. BTW reducing the WATCHOUT Display / projector refresh rate would likely make it worse. Either run the camera at a slower refresh rate or lock the server and camera to a common reference.
  4. You are correct, most likely your camera is at 60 fps and it is not in synch with the WATCHOUT Display output. Reducing your cameras rate to 30 fps is a potential solution. If you must record at 60fps, a WATCHPAX 60B or 60C contains a hardware synch card (or any server with a hardware synch card) that can be genlocked to house reference which would also require you to genlock the camera as well.
  5. Is the WATCHOUT 6 test on the same computer?
  6. The most common cause is a second network interface in the production computer. Your description exactly matches that issue. Did someone activate WiFi in your production computer recently? If you require two NICs, then the WATCHOUT NIC must be the first NIC in Windows NIC order to prevent this. If there is only one NIC, this issue will not occur. If you search the forum, you will find numerous posts with this issue. A recent post in the responses even includes info on how to change Windows NIC order in Win 10. There are other potential causes for what you describe, but your pos
  7. A very qualified yes. The mp4 codec has many option settings and those parameters can significantly affect stability. For example, an mp4 with bi-directional frames will probably play ok once in a quick test, but run that same file over and over again over the course of a day and it will often take the server down. The encoding setrings for mp4 are similar to mp2, so the details described in this article apply to mp4 as well. reference: https://knowledge.dataton.com/knowledge/how-to-encode
  8. Before considering MacOS issues, are you sure you have the correct license for WATCHNET? reference:
  9. You might have better results asking the question here … https://forums.presonus.com/viewforum.php?f=357
  10. localHost is always the device itself. So are you saying the iPad can not see itself? Otherwise, while the server computer running a browser can see the local server as localHost, any other device on the network (like an iPad) must use the valid network address of fhe Network Interface of the server.
  11. It is probably not the issue, but to rule it out, did you check the audio output assignments in each audio cue on the aux timeline?
  12. Not possible / recommended. It would defeat the purpose of a locked down predictable / repeatable configuration. At the very least, if you were to figure a way to hack it, it would void all warranty and support.
  13. Possibly put them in a composition?
  14. The error code is from Windows, not WATCHOUT. As you can not install drivers on a WATCHPAX, it may indicate the lack of a driver needed for that device. Most people would use an HDMI to NDI Ethernet adaptor when using a WATCHPAX to bring in a live signal.
  15. i am not sure if simply creating the DMX output at address 512 is enough. If its status does not change, it may still optimize out. Just to be sure, for the purpose of testing, create an aux timeline 2 seconds long with a DMX cue fade up 1 second, fade down 1 second, run it and loop it.
  16. Understood, but that is a valid transmission and that device is not fully compliant with the standard if it is refusing to accept that Sequence byte.
  17. i am no expert, but could it be that particular lighting device considers any transmission not containing the full 512 addresses as a flawed transmission and ignores it? The standard does not require all addresses be transmitted. Yet sending the full range is the norm for most consoles, etc. WATCHOUT is the outlier. Still, as you can see other devices deal with it. Easy enough to check. Add a DMX Output in the same universe and set it to address 512. This forces WATCHOUT to transmit the entire range.
  18. Slingle key jump - no. You can hit Ctrl-F and then type any control cue name (case sensitive) followed by Enter key to jump to that cue.
  19. Thanks for reporting back your r success. Sorry i did not provide the known good version number in my previous response. As you correctly indicate, nVidia driver version 460.89 is the recommended version for best results with WATCHOUT.
  20. There is an issue with recent nVidia drivers, you may need to go back to an older nVidia driver version.
  21. I see you have cross posted this in the Facebook WATCHOUT User Group. So i will duplicate my response from that thread. It is true, Dataton does not support specific vendors products. Dataton supports standards. Prior to v6.3, Dante was supported via the Microsoft WDM standard. v6.3 and later changed audio support to the more modern profesional standard ASIO (and the newer Microsoft standard WASAPI). Dante Virtual Sound card offers support for both WDM & ASIO standards. So when migrating from versions before 6.3 to 6.3 and later you may very well need to reinstall audio drivers. Als
  22. The speaker selection should work for the 3.5mm output. Might check the connections and impedance match. What build is your WATCHPAX 4? The Focusrite 3rd gen driver is in the latest WATCHPAX 4 build (r38) only, you may need to update the build.
  23. It appears you are selecting Realtek Digital out. WATCHPAX have no built-in digital audio out. The 3.5mm jack is analog audio out, so the correct selection would be Speakers. (Would be more convenient if they just called it analog.) Timecode in requires a compatible USB audio interface (and you can only have one audio interface, so if you want to output audio and read timecode, a single interface must provide both). Current versions of WATCHOUT support ASIO for the audio input - i.e. ASIO for both output and input. (much older ASIO versions of 6 used a mix of ASIO output, but Di
  24. All WATCHPAX 2 include support for version 5.5.x. Most WATCHPAX 2 include support for any version 6 variant, up to and including the most recent version 6 release (6.6.5 as of today). There are some early production WATCHPAX 2 that only support v5.5.x. To be sure, use the License Manager in WATCHOUT 5.5.x Production to check supported versions. The reason you should check with 5.5.x if you are unsure of v6 support is you must go online to check the version. If you go online using v6 production on a v5 only WATCHPAX 2, you will “brick” the unit, requiring it to be returned for service to r
  25. Thank you for checking that Rainer. And to make things more confusing on AMD cards, those two legacy signal clocks can be dynamically assigned to any two of the four outputs. This is the anomalous behavior i referred to in the post above. i.e. AMD cards can only support two passive adaptors. And the ports supporting passive adaptors can dynamically change. As native DisplayPort output does not require the legacy clocks, using only active adaptors eliminates this concern.
  • Create New...