Load To Time fire all group + Start Cues = bug?

55 views
Skip to first unread message

Freddy Komp

unread,
Sep 13, 2019, 7:49:31 PM9/13/19
to QLab
Hi lovely people at Figure F53,


I noticed a bug, please add to trackers:


When you have a fire all/timeline group cue with pre-wait start cues in them that point to other video/audio cues, these seem to not load to time correctly with the group; start cues that should have already been executed will only be executed then (and not passing on the loading to time to their targets).


Easy fix?


Cheers,

Freddy

Chris Ashworth

unread,
Sep 16, 2019, 9:08:45 AM9/16/19
to Freddy Komp, ql...@googlegroups.com
Hi Freddy,

I have not been able to understand your description well enough to know if there is a bug here.  Can you please send an example workspace and more specific numbered steps, along with your expectation of the when the results do not match what you expect, to sup...@figure53.com?

Thanks!

Chris 

Rich Walsh

unread,
Sep 17, 2019, 8:33:43 AM9/17/19
to ql...@googlegroups.com
I don't think it's a bug: I think it's a feature. I can't find any documentation on it, but cues that have no length (eg: Start Cues) fire even if you've loaded past them:


I can't imagine a simple answer for QLab to know which zero-length cues you want to interpret as "also load the target cue to time" before starting. I'd put the things you want to play at once in the same Group Cue – this also helps with maintaining sync. Or write a script to load to a group to time and also load cues targeted by the group's children to appropriate times – rather than relying on QLab to guess what you mean correctly.

Rich

Sam Kusnetz

unread,
Sep 17, 2019, 9:12:02 AM9/17/19
to ql...@googlegroups.com
Hello All

On 14 Sep 2019, at 00:49, Freddy Komp <busy...@gmail.com> wrote:

I noticed a bug, please add to trackers:

When you have a fire all/timeline group cue with pre-wait start cues in them that point to other video/audio cues, these seem to not load to time correctly with the group

On September 17, 2019 at 8:33:42 AM, 'Rich Walsh' via QLab (ql...@googlegroups.com) wrote:

I don't think it's a bug: I think it's a feature. I can't find any documentation on it, but cues that have no length (eg: Start Cues) fire even if you've loaded past them:

This is indeed not a bug but an intentional behavior, and the rationale is like this:

If you have a Timeline Group cue with an Audio cue plus a bunch of MIDI cues. Let’s say those MIDI cues do scene recalls on your audio console, with the idea being that as the Audio cue plays a song, things happen on stage and the console needs to be in the proper scene at any given moment of the song.

When you load to time, you want the console to jump ahead to the proper scene, right? So all the MIDI cues have to be triggered or else the console will not be where it should be.

I’m sure there are valid counter-examples, but we think the majority of use cases support triggering zero-length cues as a consequence of load to time.

Easy fix?

Almost never :)

Best
Sam
Sam Kusnetz | Figure 53
Reply all
Reply to author
Forward
0 new messages