Jump to content
Dataton Forum

Walter Soyka

Member
  • Content Count

    23
  • Joined

  • Last visited

1 Follower

About Walter Soyka

  • Rank

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

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

  1. Well, now that I know about it, I'll use this all the time! It would be really excellent if this were supported as an official feature. I'd hate to build a show that relied on it, only to have the behavior "fixed" in a future version. Thanks, w.
  2. Our thread-starting setup defined displays by direct IP address. I'll use computer names on the next one and see if it makes a difference. Thanks so much, JJ! w.
  3. Nice, JJ! We were also syncing via S400 without genlock in the original post, and we were running WATCHOUT 6.1.6. w.
  4. Thanks, WatchDog. I have a revised version for V6 which also adds - and = for zoom, and PgDn/PgUp for timeline navigation, just like Ae. I'll post it here next week! w.
  5. Thanks for the sample! Now I get what you were describing -- using the Z position to enforce a compositing order. I really liked being able to see under the screen masking with my compositing VD setup, but this is a good workflow for a lot of other shows! And my apologies for going OT. I think that virtual displays are a flexible, important tool, but if my use of them contributed in any way to the cueing latency bug, I thought it might be good information for JJ and the developers to know. w.
  6. Yes, but then I couldn't run any cue at any time, because a lower cue couldn't overtake a higher cue. I needed to combine features of "Always on top" and "Task list order," so I used VDs to enforce the compositing order my show required. w.
  7. In case the use of virtual displays impacts the issue we're chasing, I'll describe our setup on the show that started this topic. We used three virtual displays to enforce a compositing order with three different kinds of "Always on top" auxiliary timelines: Content Logos Masking for moving screens Each kind played in their own dedicated space on stage. The media cues for the VDs were on the main timeline and output to projectors: two straight-up, two rotated with geometry correction and pixel density adjustment. The stacking order of the VD media cues composited con
  8. @JJ Myers If there's anything that we can do to help, let me know. I'd love to see this repro'd and resolved, so we can use WATCHOUT with confidence. w.
  9. Yes, I had this issue on a show last year. Here's a thread about it: http://forum.dataton.com/topic/2558-latency-on-running-cues/ The displays did have multiple NICs, and I did use virtual displays extensively. w.
  10. Technically it was Apple that dropped QuickTime support. For now, the best alternative to render directly to Hap from After Effects is probably AfterCodecs: https://aescripts.com/aftercodecs/ Personally, I generally render to an intermediate and then encode to Hap separately. You can keep an older version of Adobe Media Encoder for this. w.
  11. You could set up your loop with control cues: one that marks the beginning of the loop, and one at the end that jumps playback back to the beginning of the loop. Place the "Loop Back" control cue on a conditional layer, and clear the "Loop Back" condition via an auxiliary timeline. To set conditions via aux timelines, you'll have to add a String Output to control WATCHOUT via TCP/IP or UDP (and enable control of the production PC software if that's how you'll be running it). You can use the "enableLayerCond 1$0D" command to set Condition 1 and "enableLayerCond 0$0D" to clear all conditions
  12. Thanks, Mike. We were already using TCP control of the production PC from Widget Designer. The production PC was responding immediately to Widget control; the displays were responding to control from the production PC on a delay. Once the issue occurs, the delay is consistent until WP.exe is restarted, and occurs whether the cue was fired indirectly from WD or directly from the production PC. With respect to Klangreich's post from yesterday: he has a a completely new show exhibiting the same issue, without WD in the mix yet. After an hour or two of programming and frequent updates, the lat
  13. I can provide some additional context on this show. WiFi is off; firewalls are off. We are controlling the production PC with Christie Widget Designer via TCP/IP on the same . The content in each timeline starts 0.1 seconds in, and we are manually loading (with "halt") each aux timeline several seconds (usually 10 or more) before playing them (with "run"). We haven't narrowed down the exact cause, but something is happening that makes the displays suddenly respond after approximately 2 seconds' delay. All displays respond immediately to the TCP-based control (like scrubbing the timelin
  14. Over my last couple shows, I've been working on an AutoHotkey script which adds some useful keyboard shortcuts to the WATCHOUT production software: Add media file, New folder, Add new text, Add new composition, Add new video proxy, Y rotation tween, and a cheat to sort of duplicate the selected composition. I've shared the script if anyone is interested: http://www.keenlive.com/renderbreak/2013/09/custom-watchout-keyboard-shortcuts/ I hope this is helpful to others, and I'm always open to feedback and suggestions. w.
×
×
  • Create New...