Anyone;
I would like to know more about the practial usage of move command, assert and assert time in multi-cue list before I do a EOS demo to my customer.
Anyone;
I would like to know more about the practial usage of move command, assert and assert time in multi-cue list before I do a EOS demo to my customer.
Hi,
I've used it while running a cue coming out of an effect. The intensity channels were being controlled by the cue time over the effect time so I put an [intensity] [time] [assert] on the channels so that the transition from effect to cue was tidy.
Also useful if a channel is being used in playback cue list 1 and you want it to be controlled in cue list 2.
I'm sure others know more about it.
Cheers
Crispy
Hi,
I've used it while running a cue coming out of an effect. The intensity channels were being controlled by the cue time over the effect time so I put an [intensity] [time] [assert] on the channels so that the transition from effect to cue was tidy.
Also useful if a channel is being used in playback cue list 1 and you want it to be controlled in cue list 2.
I'm sure others know more about it.
Cheers
Crispy
Or another example that came up today - with a single cuelist.
You have a long cue (Q100) that fades to black over 20 seconds. On a visual cue from stage, however, you have to snap to black (Q101). As both cues have the level of zero, Q101 will need an assertion.
I haven't actually played with this, but I believe Assert is the way forward.
-luke-
If you're actually snapping to black, a block might be better than an assert. That way you don't track a change into your blackout. Just depends on your situation.
www.etcconnect.com