Skip to slice

[friendl...@gmail.com]

Hello 

I have a piece of music that I loop in the middle, which I then devamp to continue playing to the end:

What I want to happen is after the last slice plays, I want it to jump back to the middle slice. 

Is there a way of doing this?

Thanks

[micpool]

Re are many clever ways of doing this, but probably none more,efficient than aucontinuing to a duplicated cue with the start moved to the slice point

Mic

Wednesday, August 9, 2017 at 5:58:30 PM UTC+1, friendl...@gmail.com wrote:
> Hello 
>
>
> I have a piece of music that I loop in the middle, which I then devamp to continue playing to the end:
>
>
>
>
>

[micpool]

Sorry this won't actually work.

Firstly, I meant auto -follow not auto continue

But interestingly the effective duration of a cue with an infinite loop on a slice is shorter than a cue with a play 2 times loop on a slice

 i.e  the post wait time is not recalculated on each iteration of an infinite looping slice so the next cue will fire when the original unsliced duration of the cue is reached, not when the playhead reaches  the end of the file.

The simplest option is to use QLab 2 style de-vamping without slices , i.e :

duplicate  the cue 3 times

set start and end times to for each cue to make cues for beginning middle and end

use   auto follows,  loops and  devamps  as appropriate to get the structure you want

copy and paste to do the repeated sections

something like this attached workspace

Mic

On Wednesday, August 9, 2017 at 7:16:23 PM UTC+1, micpool wrote:

There are many clever ways of doing this, but probably none more,efficient than auto-continuing to a duplicated cue with the start moved to the slice point

[sftechguy]

Pretty clever stuff.  I did find that to get it to work in QLab v4 a small change must be made to the devamp cue.  There's now an option to either devamp the currently looping slice or the currently looping cue.  In this example, you must select the "devamp the currently looping cue" option. Then it works like a champ.  Thanks again, Mic, for another creative solution.

A couple of things I noticed/wondered about while playing around with this:

1:  If you start the cue list from the beginning and then hit GO while cue Beginning is still running, things go on their merry way and the CODA will play while Beginning is still running. This may be a QLab bug/feature, and I wonder if a devamp cue shouldn't be allowed to execute until its target is actually executing. Maybe it should pend until its target starts... I'm not sure of all the implications that might entail.

2:  It would be nice if a devamp cue set to "start next cue when target reaches the end of the current slice" had some sort of indicator of this in the autofollow/autocontinue column.  Maybe an autofollow symbol in parentheses..?

3:  Playing through the cue list in a normal fashion, when the sequence is done the playhead is positioned on Looped section (unloooped). Seems to me we should be in a state of nothing on deck.

Again, nifty solution to the problem!

-s

[micpool]

Yes that's true.

As with any cue sequence, if you think it is possible someone could muck it up catastrophically then you have to program that possibility out.  Here is a QLab 4 version which makes it difficult to devamp early and even if someone gets trigger happy and steps through the safety cue the sequence will complete in a non catastrophic fashion.

The stepping over a dummy cue technique is also useful if there is a go that is habitually being called or operated early.  I had a cue in a recent show where the operator was stopping a lift sound effect  1 second after it had started. They were operating lights and cue lights as well, and it was just one of those 'rubbing your head and patting your stomach' things that the sound go button always twitched with one of the other cues. Adding the firebreak cue meant that if they did hit the sound button again in the really complex lift starting sequence it didn't matter, and if they didn't after 5 secs the next cue would start automatically.

This workspace is also an example of the group cue only style of programming which avoids auto continue and auto follows entirely. 

Mic