Jump to content

SFluster

Member
  • Posts

    20
  • Joined

  • Last visited

About SFluster

  • Birthday 08/15/1989

Profile Information

  • Gender
    Male
  • Location
    Los Angeles

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SFluster's Achievements

(3/3)

  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. 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. 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:
  4. Another option is to create a UDP string output for the local production machine and use the network control protocol to set input values. eg. setInput Opacity 1 1000$0D
  5. I'd love for an ETA to accompany the purple progress bar when pushing media to displays
  6. You could get a couple more outputs more cheaply with a 1x3 MST Hub. This has the added benefit of having the extra outputs appear as separate displays in windows/watchout.
  7. 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
  8. you can do this with Ctrl+Tab & Ctrl+Shift+Tab
  9. You can take the output from resolume as an input or number of inputs into watchout using capture cards. The LIGHT nightclub at Mandalay Bay in Las Vegas works exactly like this.
  10. 1. This is incorrect 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. This one I'm not sure has a clear answer. I'll leave it to someone who has a better understanding.
  11. 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
  12. Might be apple software update. I believe it defaults to checking for updates weekly.
  13. 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.
  14. Request to pin this post to the top of this forum
  15. Off topic here, but I LOVE the Noctua NH-D15 CPU cooler. Good choice!
×
×
  • Create New...