The disadvantage is like SerraAva said, if you run the routine on the C/D faders and then hit GO on the A/B faders while the routine is running on C/D, the A/B
fader will go on the "Next
Cue" which will potentionally be one of the cues in the subroutine.
I'm not quite sure why this would happen? I assume if your using subroutine cues, you put all of the cues called in by subroutines at the end of your
cue stack, say 800 or 900 range. If you fire
cue 99 in AB,
cue 100 (Subroutine) in CD and then hit go again in AB you should have
cue 101 running in AB while
cue 100 (subroutine) runs in CD. Since
cue 100 is calling cues in the 900s you should never have issues with running a portion of the subroutine incorrectly. You will need to figure out a way of clearing the
effect out of CD, but you can just make a
macro that clears CD (just make the
macro hit the
clear button on CD) and link it to whatever
cue you want the
effect to end on.
Derek, I don't believe you can write subroutines into subs. You can write normal
pile-on subs, effects subs and inhibitive subs, to my knowledge thats it.
Also, the
console has an autoload function? I never knew that. For what we were doing it worked perfectly well with the 5 keystroke delay, as the
effect look lasted for around 12 seconds.