Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited

About Nate

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

305 profile views
  1. Hey Merten. Your best direction is probably to pair the Dynamic Media Server with something like an Eye Fi card. If the server and Eye Fi card share the same wireless network, you can install the Eye Fi software on your media server and have the photos sync to a designated folder. Then, it's all up to how you want to import those photos into watchout. I have used this in the past and it's close to instant but occasionally there has been a delay between the card and the pc depending on where the card is in proximity to the wireless router. Hope this helps.
  2. I've wanted virtual midi keypad show control for a while. I wanted to assign channels, rename buttons, theme actions by color, etc. Basically, I wanted a show control I could customize for each show that would output a midi signal Watchout Production could understand and output to my display machines. Well, after a morning of hunting and testing, I think I found a pairing that does the trick. So, for those of you without a midi show controller OR who have been looking for a virtual solution, here is one that is currently working for me: LoopBe1 – Virtual Midi Driver $14 Commercial (Free for Personal Use / Testing) http://www.nerds.de/en/download.html AVD “Midi Buttons” – Configurable Midi Controller Keypad https://www.audiovisualdevices.com.au/software/midibuttons/index.php Free for Personal and Commercial use. Install LoopBe1 and it will create a virtual midi device on your computer that essentially listens for a midi show controller to send it information. Then, just open Midi Buttons and start configuring your cues. It definitely takes some configuration but, it does work and really breaks you out of Watchout's "Task" window. Here was a button configuration that worked for me inside of Watchout: (ensure you set Output1 to LoopBe and set it to Active in the configuration window) Press: Note On Channel: 1 Note: 2 Velocity: 1 Output: 1 Press / Release Release: Note Off (all other details same as above) Add a new Midi Note Input and have it "learn" that button. You should see channel 1 and note 2 listed. Now, assign the input to a task and watch it work. I tested this on a Windows 7 machine running WO 5.5. There are obvious drawbacks like not having sliders or being able to halt aux timelines with the stop button in the WO task window but, I get a fullscreen show control to customize that could even work on a touchscreen monitor if configured correctly.
  3. Awesome Jonas. I will test that configuration now. Thanks for the reply!
  4. I just recently finished a show where we ran a 3-output edge-blend from a single display computer. I also had an additional triple-output display computer on-site as a backup. I ran both of them together on the same network switch with the production computer. All outputs ran into a HDSDI switcher so we could send any output we wanted up to the projectors. For this event, I would push the final show to the primary display computer, save a "backup" version of the show, change the display IP addresses in the backup version, and then push the show to the backup. It worked well enough but, I would like a more seamless solution since, in the event of a display crash, the backup would be waiting for cues from my production machine and I would have to close the original show and open the backup version before being able to resume playback (losing precious seconds of recovery time during a show). My question is: Is the solution as simple as stacking the backup displays on-top of (or underneath) the primary displays on the watchout stage so it fires all of them in unison? So, if layered, it would be layered something like this: Primary Displays: [ Display 1a ][Display 2a][Display 3a] Backup Displays: [ Display 4b ][Display 5b][Display 6b] In theory it seems like it would be an ideal solution but, I was wondering if anyone else has a better live backup solution. Thanks!
  5. I use the Korg nanoKONTROL2 to fire AUX timelines and adjust a few fades. Pros: It's affordable, runs via usb, gives light feedback to buttons when you push them, and doesn't require a special driver for the windows machines I have used it on. Cons: Cheapest quality sliders on the planet. They pretty much fall off the unit if you shake it too hard. So, for a push-button cue solution, it's great. For a fade solution, try something else.
  6. @Jonas - Setting the video standard to "other" definitely improved some of my screen tearing. Also, thanks for the clarification about interlacing on digital sources. @Walter - Dropping fown to 1280x720 completely cleared up the screen tearing. I am still experimenting with some Vision capture settings to see if I can get Watchout to cooperate but, right now, it is a working solution. @Mike - It's definitely 1920x1080 @60hz. I did confirm that in the output settings of the computer sending the signal. I'll have to look into the player/file itself to see what might be causing it to tear during output. Thanks for the response guys!
  7. First off, thanks for all the answers to other member posts on here guys. There's a lot of great info that has kept my work flow going because I was able to find an answer rather than post/comment. That said, I do have a question. I have a 1920x1080 60hz VGA input coming into my Vision capture card. Vision recognizes the input correctly and I have assigned it as Input Device 1 in Watchout. When I load up my timeline, I am able to see the input but it does have some "jaggy" image issues when playing power point fades or video through it. So, I figure I can deinterlace it to solve the issue but, when deinterlacing is applied to this input inside Watchout (both on good or best quality), the input feed completely disappears (however, if I exit watchout on the display machine, vision viewer app still shows the feed). When I remove the deinterlacing, the input comes back in watchout. Here is my Live Input settings: Input Device: 1 Signal Input: RGB 1 Video Standard: 1080p 60 Preview: Thumbnail No Edge Trimming Dimensions: 1920x1080 (WO 5.3, Windows 7, WatchRack) I'd really like to get deinterlacing working to solve the screen tearing. Any idea where I have gone wrong?
  8. Further inspection has shown that, while my original input was set to "component" for DVI and worked normally, 5.2 seems to require it to be set to RGB. Changing it to RGB, updating the display computer, and firing the show yields a capture display. I am currently working without issue on 5.2 due to this change only.
  9. Uninstalling, rebooting, and reinstalling the vision driver did not solve my problem. The issue persists.
  10. Can you explain the process you used to reinstall the driver? Did you uninstall, reboot, and then reinstall the same version?
  11. I recently upgraded my display computer to Watchout version 5.2 (from 5.1). I did this by uninstalling Watchout and Codemeter, restarting the system, and then installing 5.2. Now, when I push a show originally made in 5.1 (but recently saved to a 5.2 version), I get an error reporting back from my display machine saying that it does not see a feed coming in from my VisionRGB capture card. I have opened the Vision software and can confirm that it is receiving a feed. I also confirmed that WatchPoint is still looking for the capture card on the same input as designated in the show. So, everything looks great on the settings side. I have tried an uninstall which included deleting remnant files from my Watchout folder without success. I have tried deleting the show files from the display computer and pushing a fresh copy without success. I have created a new 5.2 show with only a capture input and still received no feed from the card. Finally, I rolled back to 5.1 and pushed my original show. The capture comes up perfect like before. So, what's the story here guys? Does 5.2 require a Vision driver upgrade or setting change?
  • Create New...