Jump to content
Dataton Forum

Mike Fahl

  • Content Count

  • Joined

  • Last visited


About Mike Fahl

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Linköping, Sweden

Recent Profile Visitors

1,685 profile views
  1. I don't believe MICSOFT manuals ever existed in electronic form. But if they did, I'm sure Jim has a copy stashed away somewhere. Also, note that MICSOFT predates TRAX, and isn't file compatible. I.e., any show you may have producer in TRAX will not load into MICSOFT. Mike
  2. The "authenticate" command isn't needed on the UDP port as far as I can recall. From the IOCORE manual, it definitely doesn't seem tp support appengin $0D as a "carruage return". You may want to send the command without any carriage return when using UDP. If that doesn't work, the only way by which you can send CR as far as I can tell from the manual is to send the entire command as HEX. Another option is yo send the command as TCP instead of UDP. Here you need to use the authenticate command. But in this case, you can mix sending commands as text and the CR as hex (here just 0D). Mike
  3. Yes, I believe the last (often large) number is the "system time". All times are in mS. WO will send such messsages to subscribers when there's an abrupt change (such as a timeline starting/stopping). In between such abrupt changes, WO will send an update every couple of seconds anyway. You then need to extrapolate from the most recent value if you need more continuous time position data. Mike
  4. I don't think IOCORE interprets $0D as carriage return, but sends it as plain text, which is then not understood by WO. Check the documentation of IOCORE to see how to send control characters. You may also simply try removing the trailing $0D after each command. As you send them with UDP, WO may accept them without explicit line ending (since UDP sends an individual packet for each command anyway). Mike
  5. Please contact Dataton Support for obtaining access to these details. I no longer work there, so I don't want to pass along information that's not in the official documentation. Mike
  6. Jim, I guess that should be DHCP (i.e., automatic/dynamic IP address). HDCP is something quite different. Mike
  7. You can just make the edge-blend gradient in Photoshop or similar, and add it as a separate layer on top. It's essentially a black image with a transparency gradient. Test, djust the curvature of the gradient as required, update the media, rinse and repeat. Mike
  8. If the error only affects aux timelines in folders, then it may be that Manager hasn't been updated to work with those. The control protocol syntax is a bit weird in this area. This works fine in PIXILAB Blocks of course, with the only caveat being that timelines in folders can not be named the same as top level aux timelines, or aux timelines in other folders. Mike
  9. Many lighting consoles take LTC timecode. If so, that may be an option (using a WAV file to play timecode from your WATCHOUT timeline). Mike
  10. Below is Microsoft's official description of the error you received, from this page https://docs.microsoft.com/en-us/windows/win32/directshow/error-and-success-codes So there's likely something unsupported in your MOV file, as Rainer suggests above. VFW_E_UNSUPPORTED_STREAM 0x80040265 Cannot play back the file: the format is not supported.
  11. Wow! That's a "blast from the past"! I seriously doubt you'll find any, but who knows. Whaddoyaknow; here's a post from Mal Padgett that actually includes a POWERPAX! Mike
  12. There seems to be AAC audio in the file, as far as I can tell from your screenshots above. I don't think WO supports that format (at least it didn't when I was involved). Perhaps that causes some trouble durig playback. You may want to remove the audio track from the file, to see if it plays OK without it. If so, add it back as a separate WAV file with its own cue for playing it, rather than embedding it into the video. Mike
  13. Consider two edges that cross, forming a "corner". Each pixel in this corner, coming from each of the projectors, must be at 50% brightness, for the combined brightness to come out as 100%. The pixel next to this, just outside the blended area, must be 100%, since there's no blend there. Now, if you move one of the projectors by 1 pixel, you'll have a very notceable 100+50=150% brightness right there, clearly visible as a bright line. Hope this helps. Mike
  14. Most ARTNET montor programs work only on Windows. Here's a cross-platform solution that also works on Mac and Linux: https://github.com/pixilab/artnet-monitor Mike
  15. You can add custom masks inside the Display Settings dialog box (assuming you use WATCHOUT 6). See under MASKING in the DISPLAYS AND PROJECTORS chapter. Note that it's not possible to create a "good" mask for the arrangement you show above. The pixel at the intersecting edges must be 50% intensity, meaning that a 1 pixel error in alignment will be visible in that area. That has nothing to do with WATCHOUT and everything to do with physics. Mike
  • Create New...