Hi all,
First off: coming from an Obsession 2 background, I understand the reasons for blocking channels in cues where they have been recorded at the tracked level, i.e. if channel 1 goes to full in cue 1 (and tracks) and when recording cue 4, channel 1 is recorded at full, then a partial block appears on that channel. Having the block is a good way to know that there is a redundant ‘hard’ command in that cue.
That’s fine, it can be slight tedious to clear all those blocks but essentially … fine.
Now (unlike when programming the Obsession 2) when I’m recording cues with moving lights, I will create the state, record it and then mark all the moving bits.
In this example, channel 1 in cue 4 moves to FP1. If I mark channel 1 in cue 3 then I get partial blocks on channel 1 in cue 4.
Surely the raison d'être of mark is to make sure the NIP’s are the same in the previous cue. Therefore, is the block not redundant (unsightly and a bit of a pain in the bum)?
My understanding of tracking is that data recorded will track ahead until it hits a point where it is told to change. Therefore, if you change the light upstream in the cue list, the data will track on until it hits the downstream cue, then it will change.
So my question is… why does mark create the partial block, as its function is to make sure that the NIPS are in the previous cue?
Also, does this become redundant when I can [system blocks: disabled]?
Sorry for the long post
Crispy
