Timecode cues stopping when other cues end

[Steven Lemke]

I have a show where I am running two video outputs (one to a projector and one to a display for the conductor with punches/streamers/click. I am using the timecode window to see a running time of each cue. This worked fine when I was using two computers synced with ethernet and using OSC to have one machine control another. Now I am trying to set this up on one machine. I have a group with the two video cues and the timecode cue auto followed by a fade cue which fades and stops the previous group. My problem is that as soon as the fade on the previous group ends, the timecode for the current cue stops. Is there a particular way I need to arrange these cues to prevent this from happening?

Also, even though the two videos in a group are identical in length and have identical in points, they are not playing together in sync. There is usually at least a .2sec difference. Sometimes as much as a full second. Any ideas?

I am running QLab 3.1.7 on a 2.3 Core i7 MBP with 16 gig RAM running 10.9.1

Steven Lemke

[micpool]

The attached screenshot shows a cue list that works. During the fade Timecode display gets both time codes and flickers between them but as soon as timecode 1 stops the counter is correct.

For me the  videos also run in sync even if I use big high bitrate files  that momentarily freeze when they start. As soon as they stop stuttering they are bang in sync.

How are you observing they are out of sync? If you open the audition window are they out of sync in that?

Are they in sync then drifting or do they start out of sync?

Mic

[micpool]

Sorry, I can see your time code display problem now. I was using the separate timecode display app which works fine not the timecode window in Qlab.

[micpool]

There doesn't seem to be a way to program round it either. The inbuilt timecode window reads the last started timecode but if any running timecode is stopped, it stops.

If you stop the previously running timecode then start the new one you need a quite big delay for it to work. You could put in a .5s delay and adjust the start value of the new timecode to .5s

Or use the separate timecode reader

http://figure53.com/downloads/TimecodeDisplay.zip

Cant replicate the sync problem though

Mic

[micpool]

Inbuilt timecode window does seem to have a bug.

Just stopping a non running (and disarmed) timecode cue (by selecting and pressing S or fading and stopping a group it's in)  anywhere in the list stops the timecode window.

Mic

[Sam Kusnetz]

Thanks for the catch. I've added it to our (unsurprisingly huge) list.

Best
Sam

--
Sam Kusnetz | Figure 53 Field Operative
s...@figure53.com

[Steven Lemke]

Thanks for your help. How do you incorporate the Timecode Display app into the cues? 

[micpool]

You don't have to, it just listens to all incoming all the time. Routing timecode  to an IAC bus will do it

Mic

[micpool]

You can script it to automatically open with an autorun cue when you open the workspace

try

tell application "Timecode Display" to activate

end try

[Steve Lemke]

Got it. Thanks!


> On Jan 28, 2015, at 10:00 AM, micpool <m...@micpool.com> wrote:
>
>