Jump to content
Dataton Forum

Mike Fahl

Dataton Partner
  • Content count

  • Joined

  • Last visited

About Mike Fahl

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Linköping, Sweden
  1. Panasonic Shutter Control Using PJLink

    Your "trick", cowboyclint, likely avoids WATCHOUT closing the connection after a period of inactivity, thereby also avoiding any issues related to having to re-do the handshake. So it makes sense. Mike
  2. Panasonic Shutter Control Using PJLink

    One tricky aspect with the PJLink protocol is that you may NOT send any command to the projector until after its initial handshake. If there's no password set, this is the "PJLINK 0" string received initially from the projector. There's no easy way to make WATCHOUT wait for this initial handshake before sending its command, which is probably why the first attempt after a disconnect sometimes fail and a second command may succeed (because by then the handshake has been sent by the projector). As a side note, PIXILAB's recently introduced control system named BLOCKS provides "intelligent" drivers for projectors and other devices. Our PJLink driver manages this initial handshake before it starts sending commands to the projector. This makes for a more robust implementation than just blindly banging out the commands. Mike
  3. 23.98 frame rates and playback in WO

    No, the upsampling will be to the framerate actually used by WATCHOUT, which is often 60 fps (not 30). If the source is 24, there will always be a discrepancy when upsampling to something that isn't an even multiple. Frame blending, and similar techniques, can be used to improve this (whether done in WATCHOUT or ahead-of-time in, e.g., After Effects). But upsampling to 30 or 60 from 24 is also going to give you larger/heavier files - especially whe using codecs such as HAP, which may negate some of the advantage of upsample ahead of time.
  4. Wouldn't choosing the ADD blending mode in conjunction with controlling the Color tween channels individually do what you want. When all colors are OFF, it should be the same as opacity at 0 with that blend mode. Or am I overlooking something?
  5. Clever idea, Walter. It sounds to me that you may even be able to simplify it further by using a Color tween, binding the DMX vaues to each color channel there, rather than duplicating the content and using "add" blending mode. Worth trying anyway.
  6. Woops, seems I have a mistake above. You may be able to get away with sending just this: GET /cgi-bin/proj_ctl.cgi?key=shutter_on&lang=e&osd=on$0D$0A$0D$0A Note there are two end-of lines at the end of that (last) line. The HTTP protocol specifies header lines should be terminated by CR/LF pairs, and not just $0D as in my example above. For the remaining lines in my example above, my guess is that the projector won't really need any of them. But if you do include them, each line should be terminated by $0D$0A, with an extra $0D$0A at the very end of the whole shebang. You write the whole thing as a single line in WATCHOUT – my example above is split across multiple lines just to make it more readable. Hope this helps!
  7. I doubt you'll be able to simulate a browser request using the network output of WATCHOUT, especially one that requires some form of authentication. If it's possible to turn off the authentication, it may work. Note, however, that you need to send a *complete* GET request, which is a multi-line thing that looks something like this: GET /cgi-bin/proj_ctl.cgi?key=shutter_on&lang=e&osd=on$0D cache-control: no-cache user-agent: PostmanRuntime/7.1.1 accept: */* host: Last ine specifies the IP address of the projector. Each line terminated y a carriage return. There need to be TWO carriage returns at the end of the whole shebang. Using smething like wireshark to snoop the line while sending a working command may hwlp getting things right form WATCHOUT. Even though WATCHOUT's network port disconnects after some time of inactivity, it automatically re-establishes the communication once a new command is sent. However, PJLink may be a bit tricky to deal with due to its initial handshake. Assuming you can make it connect reliably once, your best bet may be to have an auxiliary timeline then sending some harmless command to the projector every 20 seconds or so to keep the port open, and then your command should work without the need to re-open the port. I also believe WATCHNET now has PJLink support, so throwing that into the mix could be an option. Although WATCHNET requires a separate license key and adds some complexity to the system. Mike
  8. HDMI 2.0 HDCP 2.2

    The most common "work-around" is probably to use something like this in between: https://www.tweaking4all.com/home-theatre/remove-hdcp-hdmi-signal/ https://www.alibaba.com/product-detail/HDMI-Splitter-1x4-Ultra-High-Definition_60711570924.html While such a device defeats the whole purpose of HDCP, I'd guess that as long as you're not using it to make illegal copies of copyrighted material you're fine (but, as they say, IANAL).
  9. HDR video content

    As far as I know, it's still 8 bit per color component (RGB). I assume more dynamic range is what you're referring to? Mike
  10. Control Dmx channels with Artnet

    I believe you need to be Online with the production computer for DMX to work. Make sure you're not overlooking this. Mike
  11. Problems showing HTML with Dynamic Image server

    Yet another option, especially if youre not happy with the green screen solution, could be the VMIX broeser renderer: https://www.vmix.com/help20/index.htm?WebBrowser.html This can output NDI, including an alpha channel from what they say. I haven't personally tested it, but from their description, and what I understand of how NDI works in WATCHOUT, it should work. Presumably, the VMIX renderer also supports HTML5 video. If you (or someone else) have tried this, please post your findings here! Mike
  12. Still Tearing in Watchout / Sync Cards

    You're not saying whether tearing is within a single display or across displays. Hetre I'm going to assume within a display. The only reason I can think of for tearing in stills within a single display is that vsync is disabled in the graphics card driver, or that the display device does something stupid. I've tried different file formats File formats shouldn't make a difference, since all images are decoded before you run the show, and cached in an internal format, which is independent of the original image file format. So the first part of the question is, what part of the computer does the heavy lifting of fading a still? Is that the GPU or CPU? GPU. And would additional system RAM or video ram help that? Probably not. We have the appropriate Sync I and Sync II modules. This could indicate you're talking about tearing across display outputs. In which case it more comes down to the behavior of those ync cards, that can sometiumes b rather finicky. I still intermittently get tearing between machines OK, so you're likely talking tearing between computers. Some of my answers above may still help, though. And finally, can someone elaborate on what the "sync chain master" checkbox does under the hood? You should set up one of the cards (the first in the sync chain) to act as the master. The remaining ones are slaved to this master. The master may get external sync if desired, but doesn't have to. Others should not need external sync, but will be synced from the master. Check the "sync chain master" checkbox for the display that acts as the sync master in the chain. I believe this setup is rather important for successful operation. Hope this helps. It's been a while for me, but I believe my recollection here is correct. Mike
  13. New display machine

    Awesome posting, jochri. You've really done your homework. Those thorough Germans at their very best! Mike
  14. hi everyone good day

    Uninstall Medialooks. it's a 3rd party codec pack not compatible with WATCHOUT.
  15. WATCHNET 1.4

    I don't think there is a command in WATCNET to enable imecode chase. Your best solution is probably to put this into a startup script (assuming you're feeding it to the display PC, and not production PC). See "timecodeMode" and "File-based Control" in the WATCHOUT 6 maual for details on how to do this. Mike