Cues with long timing

Hi Jeff,

Assert is needed whenever you want to force a move on channels which may already be moving.

Example:

Cue 1 - Time 5 - Channel 1 @ FL

Cue 2 - Time 2:00 - Channel 1 @ 0

Cue 3 - Time 0 - Channel 1 @ 0 (tracked value/no move instruction)

If you were to run Cue 3 whilst Cue 2 was still running, channel 1 would continue to fade under Cue 2's down time. Putting an Assert on Cue 3 will force the channel to 0 as soon as Cue 3 is run.

If you have a transition, or blackout which it is essential all channels involved in it are in the right place at the right level, putting an Assert on that cue will ensure it works as expected.

Hope that's a help

Dan

Thank you for the explaination.  I kind of understand what it does.  Just wondering if anyone can give a reason this is not a good idea as comon practice to go ahead and enter an assert on "long" fade outs just to have as a safety when things go unplanned in the human world and the cue needs to exit.  If having it there causes any particular problems.

The only reason not to assert a cue is artistic, especially if you're not dealing with a blackout.  Say your long cue is a sunset or some other shift, you want the subsequent cues to run while the tracked channels are still moving.  If you want the color shift to definitely finish by a certain point, you would want to assert the cue.

-Josh

The only reason not to assert a cue is artistic, especially if you're not dealing with a blackout.  Say your long cue is a sunset or some other shift, you want the subsequent cues to run while the tracked channels are still moving.  If you want the color shift to definitely finish by a certain point, you would want to assert the cue.

-Josh