Jump to content

Mike Fahl

Member
  • Posts

    721
  • Joined

  • Last visited

Posts posted by Mike Fahl

  1. I don't think WATCHNET can do this, since there's no incoming API endpoints of this kind there AFAIK. I do know that PIXILAB Blocks can handle this, though, and it has full control capabilities for WATCHOUT. Blocks could even act as the web server for providing those six buttons through the internet, if so desired. Or use an external web server, connecting to an API end point in Blocks.

    Another option, if Blocks is too much for what you need here, would be to have a VPN connection between the web server and the network where WATCHOUT lives, and then make the web server use the regular WATCHOUT control protocol commands through that VPN tunnel. How to do so depends on the web server being used and how the VPN is configured.

    Mike

     

  2. The load command in the protocol re-loads the show, and is probably the closest to an "update" you can get from a control point of view. The Update command of the production software also pushes new content to the display cluster. But if you're controlling the display cluster directly (which is the normal way once the system is installed), there is no production software there to push updates from.

    I'm also a bit confused by your term "reader" here. Is that a typo, or what do you mean?

    Mike

     

  3. vMix has a built-in browser feature, and can output NDI into WATCHOUT. The Watchout Dynamic Image Server used to have this feature too, but I don't know if that's still around (and vMix may be less expensive and better here actually). What's nice with the vMix solution compared to capturing it off the screen as Sean suggests above, is that you actually can get a true alpha channel out of vMix (assuming the web page is desiged with this in mind - not specifying a background color). I can provide a link more information on how to set up vMix for true alpha channel into WO if that sounds interesting.

    Mike

  4. We just did a live stream of our Blocks 5 launch from RTSP camera to YouTube. We used the open source OBS streaming solution, which worked perfectly. You can watch the result here.

    You do need to get the right URL of course. Those can be tricky to find. Port 554 is standard for the RTSP protocol. You say you got an RTSP URL working fine in VLC and OBS already, which is a good sign. Are you trying to get the stream into WATCHOUT? Or what's your problem here, and how does it relate to this forum?

    Mike

     

  5. Interesting that it loads OK once WO is restarted (presumably by the watchdog), but not with the previous show loaded. So sounds like a bug to me. Since it crashes, the Windows Event log pertaining to the crash will likely be of more use than any WO log, as it may indicate where and why WO crashed. I often found that to be useful in figuring out where things went wrong and fix it. You may need to dig around a bit in Windows Event viewer, assuming it's still there (don't recall for how long those are preserved).

    Mike

     

  6. Quote

    Has anyone had any experience of the Soundpax unit

    Yes; it never really existed ;-). It was more of a concept, based on a Pioneer car stereo deck, if I remember correctly. That deck went out of production before we got around building a product around it. 

    Mike

  7. I don't think WATCHNET supports that options. FYI, PIXILAB Blocks does support this setting, and has similar WATCHOUT control functions as WATCHNET. It also does many other things. This is a separate product though, and is not a Dataton solution. WATCHNET wasn't really designed as a full fledged presentation product, with its own media presentation capabilities, but more as a remote control solution specifically for WATCHOUT.

    Mike

  8. 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

  9. Easiest way to trigger such a function on a console is usually if the console can receive DMX. Then use a DMX channel to trigger a GO. Send DMX to the console from WATCHOUT (over ArtNET, so may require an interface if the console doesn't take ArtNET right away).

    Mike

  10. 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

     

  11. 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

  12. 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

  13. 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

  14. 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

  15. 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

  16. 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

     

×
×
  • Create New...