Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by jfk

  1. WATCHOUT versions 4.2 through version 6.6.x will work under Windows version 7. Beyond that, we can only make a guess. It is my guess now that Microsoft has officially ended support for Windows 7, the next major release (i.e. WATCHOUT 7) will require Windows 10. When that release will see the light of day, your guess is as good as mine.
  2. I suggest you take a look at this ... Pretty much the same holds true for all BlackMagic Design capture cards.
  3. I am a bit baffled by your issue. I can not think of any reason software developers would expect to deal with system clock changes during normal operation. Specially with software that includes millisecond timing accuracy. If you feel you must change the system clock, quit WATCHOUT, make your system clock change, then restart WATCHOUT.
  4. i am probably misinterpreting what you mean by that. MIDI is essentially RS-422 (a balanced line) at a reasonable data rate and you can run it quite a long distance without issue. Longer than a twisted pair ethernet hop for sure. WATCHOUT is commonly used in theatre today (well, before the pandemic) without an operator and without the production computer, triggered from the lighting console via MSC.
  5. What you built already exists. The ETC Eos has the ability to output MIDI Show Control (MSC). WATCHOUT supports synchronising to MSC. You can designate any control cue with a cue number that matches a cue number in the EOS. Anytime the EOS executes a cue, WATCHOUT will jump to the control cue with the matching number and run. In normal show the cues would be in sequence so it is resting on the matching cue number, response is immediate. During rehearsal when you jump around, the timeline will stay in synch with the EOS, but when you jump there will be a brief period while the mew media is load
  6. FYI If an external keyer is an option, many external keying solutions send two SDI signals (one is the video and one is the key). This is supported in WATCHOUT using two SDI inputs and the “masked by layer above” function.
  7. There is no facility within WATCHOUT to add delay to live video. You would need to add a video delay device prior to sending the signal to WATCHOUT.
  8. That does nor rule out an error in the meta data related to duration. As a simple test, try slightly reducing the duration of the first clip.
  9. For your described purpose, absolutely yes. No. Do not do this. Video compression makes this a bad idea. By using a separate video on a single timeline for each cue, each cue will begin with an I-frame.
  10. When triggering aux timelines from the Stop state, it is important to allow enough time at the head of the timeline for the video to cache. Starting video to soon could result in inconsistent playback. Alternately, send the aux timeline a pause to wake it up and cache prior to sending the run command.
  11. Assuming the large error is not occurring at start and does not correct shortly after a start, synch loss that significant is possibly a network issue where the UDP multicast packets that maintain synch are lost or delayed.
  12. No, KEYLINK requires a SMARTPAX connection. BTW Digital SMARTLINK can also accept switch closure input to trigger TRAX events. But like KEYLINK, Digital SMARTLINK also requires a SMARTPAX or SMARTPAX QC connection. But KEYLINK is much easier to connect. I only mention Digital SMARTLINK in case one might be on hand.
  13. Took me a few minutes, but, found it in my personal / private web storage . Stored as a .zip archive. http://dataton.net/dna/Software/Micsoft6.zip
  14. Something similar exists in the status window. You can display main timeline position in hours, minutes, seconds, frames by changing the time display to the timecode format of your choice.
  15. The pinned topic above states ... The Service Desk is part of our new Help Center, https://dataton.atlassian.net/servicedesk/customer/portals, where you, apart from requesting technical support, also can submit Bugs or Feature requests.
  16. I think those errors are the side effect of watchmaker’s failed access to the watchpax. Are there other errors preceding that error? Is there external control connection to the watchpax? Is it possible you have two iterations of watchmaker running?
  17. Command ID tagging is quite simple, but effective. It is covered in the User Guide.
  18. I see no evidence of you entering your request in the Dataton Service Desk system. Not sure where you sent an email, but that is not the way to start your request, as described in
  19. First question, is the signal NDI or NDI-HX? Placing a NDI media object on a virtual display does not activate the NDI stream until the virtual display is active on a timeline. If you are not using standby, the best way to keep the NDI stream active is to place the NDI media item on a standby layer of the main timeline from 0.0 time to the end of the main timeline.
  20. I had posted exactly what you requested in this forum. It appears it has been removed by a forum administrator. i.e. you will need to obtain developer information outside of a public forum. Contact Dataton via
  21. Once upon a time, Dataton provided a simple free of charge “web app” to do this. However, newer security provisions in iOS prevent that type of app today (i believe iOS 9 was the last version that worked with the iOS WATCHOUT Remote web app). The easiest way today is to use WATCHNET. Although WATCHNET is frozen, it still supports features prior to WATCHOUT 6.4. (i.e. do not use Task window folders and you will be fine with the current version). However, WATCHNET requires a non-display server PC and a WATCHNET license (i.e. a WATCHNET License is any WATCHOUT License that supports WAT
  22. You did not indicate the specific version of WATCHOUT. There is an anomaly in some WATCHOUT versions where NDI when all the computers involved set are to fixed IP addresses. Try setting all your computers to DHCP to see if that straightens it out.
  23. Yes, you can control display computers directly, aka cluster mode. Turn off your production computer when controlling in cluster mode. Reboot your display computer. After sending authenticate 1 send a load “yourshow” to establish cluster mode (where “yourshow” is the exact case sensitive name of your show, same as the .watch file name without the .watch portion). typically the presence of production results in the no authority error, as production locks out most control when it is present.
  24. It is possible to load a new show without the image being interrupted between the shows. granted, there is a pause. as for automated, the second show can be loaded from the first show.
  • Create New...