Jump to content

SFluster

Member
  • Posts

    20
  • Joined

  • Last visited

Posts posted by SFluster

  1. I'd probably use a separate machine to run the Google slides presentation and capture it as a video input of some kind, NDI if you don't have the capture card(s) necessary for your setup.

     

    That'd make it easier to keep your display servers from touching the internet.

  2. On 5/13/2021 at 8:33 AM, alastair young said:

    ...but if theres the equivelent of F13 available im all ears

    Watchout will recognize F13-F24 if you have a way to send those keystrokes! I just tried this autohotkey script

    +F1::F13
    +F2::F14
    +F3::F15
    +F4::F16
    +F5::F17
    +F6::F18
    +F7::F19
    +F8::F20
    +F9::F21
    +F10::F22
    +F11::F23
    +F12::F24

    which maps [shift+F1-F12] to [F13-F24] with a test show that had control cues from F1-F24 and it worked!

     

    I'm pretty sure the streamdeck software can be mapped to the F13-F24 keys if you don't want to use companion to just call the specific control cues by name.

  3. 2 hours ago, Sean said:

     

    Creating a loop using a jump cue to hop back to the beginning of the video file - movie doesn't get preloaded so we get a frame of black

     

    I like to place a still a layer below the videos with a duration longer than the video I want to loop. In my experience it keeps that black frame from appearing with the jump. see attached example:

    loop.png

  4. I've had good luck with an X-keys xk24 panel connected to a raspberry pi.

    I put the xkeys panel in hardware mode (seen as a keyboard) and have the buttons emulate F13-F24. On the RPi I use xbindkeys to bind those key presses to bash scripts that send commands to watchout production machines. 

    The scripts use netcat to send commands via UDP

     look like this:

    #!/bin/bash -xv
    
    echo "run" | source ~/Scripts/IP.sh & echo "run" | source ~/Scripts/IP2.sh

    and source a script like this:

    #!/bin/bash -xv
    
    IP="192.168.0.50"
    PORT="3040"
    
    sudo ip netns exec WOprimary nc -4 -u -w $IP $PORT

    that defines the IP and port of the watchout machine you're sending to

    the ip netns portion is a holdover from when I needed the commands to send through separate network interfaces (some clients wanted the backup system to be on a discrete network from the primary so they could use the same IPs for everything) It can be omitted if you're only using one network interface on the RPi.

    Whole thing looks like this. (case is 3d printed to accommodate the RPi underneath the x-keys panel. If anyone is interested i could probably find and upload the .stl somewhere)

    My goal with this setup was to keep it as simple as possible. There's no feedback from the device since I'm controlling and looking at the production software.

    ===

    Another solution I've been playing around with is the elgato stream deck. Right now the way I have it set up is with a program a friend of mine (actual developer kinda guy unlike me) whipped together that sends UDP commands (again since I don't need feedback from watchout) to as many IPs as you want.

    Each button uses the "open" command on the streamdeck to open a shortcut with the arguments I want in the target box. The program gets the IP addresses from a text file in the same directory as the exe. (If anyone is interested I can upload the exe for this. Maybe the source too if he doesn't mind)

    The shortcuts look like this and the panel looks like this

     

     

     

     

     

  5. Hello there. I am new to watchout and have several questions:

     

     

    1. I have been informed that the spec for the production PC must be identical to the Display PC. Is this correct?

     

    1. This is incorrect

     

    2A. Let's say I have one display PC and 6 projectors and the vga card is a GTX1060 with 4 outputs, I would then need to use 2 MST hubs to output to all 6 projectors. Is this doable?

     

    2B. How would I use WO to blend the projectors on the MST hub? Logic tells me this is not possible.

     

     

    2A. Most of the MST hubs I've seen are 1x3 or more. you shouldn't need more than 1 hub.

    2B. It's my understanding that windows (and therefore watchout) sees displays connected though MST hubs as discrete outputs. There shouldn't be any difference in the production software between using a hub and not.

     

    3. How much VGA VRAM do I need to playback (no 3D modeling or texturing) video of 3840 x 2400 resolution.

     

    3. This one I'm not sure has a clear answer. I'll leave it to someone who has a better understanding.

  6. Just ran into this issue and found a solution in case anybody comes searching for this like I did.

     

    the gefen is looking for carriage return line feed at the end of the command. so if you're looking to call presets the command would be

    #callpreset 1$0D$0A
    

    Where 1 is the preset number

  7. I tried doing this a few years ago on version 5. I was able to get the ImagePro to switch but it had an almost 90 second delay between the command being sent and the ImagePro actually switching sources.

     

    I know this isn't very helpful. Just posting to say I'd also be interested in a solution to this.

  8. Hey, I was wondering if anyone had any experience controlling an ImagePro II from Watchout. I haven't had a ton of time to really dig through the user manuals, but from the quick glances I've been able to catch I haven't been able to find much on the proper syntax for the commands I'd need to automate the switching. I'd really appreciate a walkthrough of the process.

     

    Thanks!

  9. Hey,

     

    I've got 8 machines with Watchout 5.1 on Win7 32bit and have followed the tweak list almost exactly (running SSDs and decided to remove the page file)

     

    I've been trying to figure out the steps to re-enable simple file sharing with these machines, but I haven't been able to get anywhere after 2 days of trying.

     

    Can anyone help me out?

     

    Thanks.

×
×
  • Create New...