Show Cue System

I have sound Q1 activated Manual Go Button, followed by sound Q2 activated Hot Key Trigger, then followed by a fadeout Q3 (of Q1) activated Auto Start after end of sound Q2. After successfully triggering Q2 using the appropriate hot key, the fadeout Q3 refuses to start.

My questions are:
Can anyone else repeat this?
Is this intended by design?
Is there any way to auto start a fadeout cue after completing a hot key triggered sound cue?

This is all on version 10.7.4.
Thanks!

Put Q3 as a subcue of Q2 and set the relative start time to the length of Q2

This is a get around, I can't try your original setup at the moment

HTH

Thanks for your suggestion, Boswell, but not sure that would satisfy my application. The reason why I have Q2 activated as a hot key trigger is because I may need to stop it or restart it (by hitting the hot key again) before Q3 can start. In other words, Q3 should start ONLY after Q2 completes in its entirety, not after any arbitrary time delay.

I can't try your suggestion at the moment either, since I'm not at my workstation, but I hope this makes sense. Any other suggestions would be very helpful.
Thanks again!

Hi paross . .
I've just set up the same set of Cues as you described and I am indeed getting the same result.
I also tried autostarting another audio Cue after the Hot Key Cue and that failed to start either.
Thirdly I set up Q2 in 'Toggle' mode and made it loop until released, but unfortunately that still didn't fade out Q1.
It certainly may be a bug but I'm sure Mike can throw some light on this . . . It's an interesting scenerio and will probably crop up again . . .
When I get a moment I'll experiment again and see if there's another solution . . . . .
Cheers . . . Martin

After reading my post I realised a work around.
Instead of making Q2 a hot key I made it an Audio Cue (manual) and looped it.
I then made Q3 a manual SFR Cue with 2 commands . . . the first was to activate Q2 to be released from the loop and play until the end, and the second was to activate Q1 to fade out and stop.
A good feature of this is that you can take some time before the performance to set some good loop points within Q2.
Hope this helps . . . Martin

A very clever workaround, Martin - Thanks! I also ended up doing something similar, but this will certainly work for now. Yet I am curious if this is a bug or as intended. In any case, thanks again guys for all your suggestions!

paross wrote:Yet I am curious if this is a bug or as intended.

Looks like a bug although I haven't tried this myself. I expect the bug is caused by the fact that a hot key cue never achieves "completed" status as when the cue ends the status is reset to "ready".