Re: [QLab] Devamp then fire next cue

[Rich Walsh]

On 22 May 2013, at 21:44, Matt Weber <mattg...@gmail.com> wrote:

> Hopefully this is not a rookie mistake. I am working with the slices and devamp and trying to figure out how to auto continue a subsequent cue at the completion of the vamped cue. I have a scene transition where I want to vamp the beginning of the track. Once I run the devamp cue I want the first slice to complete then play the second slice (final flourish of the scene change) then auto continue on to the next cue.
>
> I have tried several permutations of ordering the cues but the solution is not jumping out at me. I could just trigger the next cue manually but I would rather automate the action.

You need two Devamp Cues, followed by the "next cue". Both are set to "Start next cue when target reaches the end of the current slice", but the second one has a small Pre Wait too. (NB: it can't be a Post Wait on the first one as this is changed dynamically when the cue runs.)

You GO: the audio starts and loops. You GO again, the first Devamp Cue devamps the loop, then triggers the second Devamp Cue at the end of the looping slice. You need a slight pause (the Pre Wait) so that this second Devamp Cue attaches itself properly to the _second_ slice (not the first), and then fires the "next cue" at the end of it.

Clear?

Rich

[Christopher Ashworth]

On May 22, 2013, at 4:44 PM, Matt Weber <mattg...@gmail.com> wrote:

> Hopefully this is not a rookie mistake. I am working with the slices and devamp and trying to figure out how to auto continue a subsequent cue at the completion of the vamped cue. I have a scene transition where I want to vamp the beginning of the track. Once I run the devamp cue I want the first slice to complete then play the second slice (final flourish of the scene change) then auto continue on to the next cue.
>
> I have tried several permutations of ordering the cues but the solution is not jumping out at me. I could just trigger the next cue manually but I would rather automate the action.

Hi Matt,

This is not a rookie mistake; it's a great question.

First, for context, I'd recommend watching this video if you haven't already:

http://figure53.com/qlab/documentation/slices-and-vamping/

This video very nearly shows how to build what you've described.

To get exactly what you describe (requiring only pressing GO once, instead of twice) would just take setting both devamp cues to "start next cue when target reaches the end of the current slice"

I've attached a screenshot and workspace showing this. Both devamp cues have the "start next cue" option checked.

The end result is a single "GO" will turn off the vamping loop in cue #1, and then start cue #4 when cue #1 finishes playing out the end of the file.

Best,
Chris

[Lucas Krech]

The Amen Break huh? So not only do you murder children but you steal from the most stolen from artist in the history of recorded music. 

For SHAME!!!!

-L

<Screen Shot 2013-05-22 at 9.21.02 PM.png><devamp-example.cues>--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab

Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Matt Weber]

Thanks, that looks so simple now that its working!  I had watched the video and thought that there had to be a way to do it.  The trick is the start next cue on BOTH devamps which I had missed.

Matt

[Rich Walsh]

On 23 May 2013, at 02:22, Christopher Ashworth <ch...@figure53.com> wrote:

> To get exactly what you describe (requiring only pressing GO once, instead of twice) would just take setting both devamp cues to "start next cue when target reaches the end of the current slice"
>
> I've attached a screenshot and workspace showing this. Both devamp cues have the "start next cue" option checked.

In my tests you do need a small Pre Wait on the second Devamp Cue or else it also fires at the end of the first slice.

Rich

[Christopher Ashworth]

Ah, thanks for the catch; I'd need to check the code to see the exact order of operations, but adding a pre wait can't hurt and will certainly ensure things are happy.

-C