Just a couple of other things worth pointing out.
It isn't necessary to select your entire
channel range to make a
blackout. Just store the
blackout cue with the channels that need to be set to zero. Two ways to do this:
[Select Active] [Out] [Record] [Next] [Block] [Enter]
or
[Go to Cue] [0] [Enter] [Record] [n] [Block] [Enter]
(Go to
Cue 0) doesn't impact non-intensity parameters, although a (Go to
Cue Out) will.
If you later add in channels prior to this
cue, they will automatically be set to zero in your blocked
cue.
There is a difference between
block on
Eos and
Ion and other desks you may have worked with.
Blocking is an editing only function. It doesn't impact playback - where channels respond to their last move instruction.
Blocking a
channel doesn't treat that
channel like a move on playback. So, imagine that you have stored
Cue 10 at as a
blackout on a zero count, and you've blocked it (always good practice). If some of those lights are already moving to zero from the previous
cue, and you go on
cue 10, those lights will continue to
fade to zero in the time of the previous
cue (because they didn't receive a move instruction in
cue 10). You can place an assert on
cue 10. Assert is the playback equivalent to
block. It takes any tracked values (and blocked values) and treats them as a move on playback.
Does that make sense??
a