"force black" Q, as in no matter if there is still the previous cue fading, when you press go, you certainly get a blackout? if yes, then Assert the blackout
"force black" Q, as in no matter if there is still the previous cue fading, when you press go, you certainly get a blackout? if yes, then Assert the blackout
e.g units are plotted into Q1, Same units are plotted in Q2 but in a different position. One does not want to see the move.
A dedicated force black command will insert a point Q prior to, in this case 2, ie 1.9 and make 2 a follow on. It will recalculate and assign the appropriate timings so that every thing is in sync at the end of Q2.
Q1.9 fades the mlx so a look ahead/Mark can b done, Q 2 then fades in the state and the mlx in their positions.
I have worked out away, I think , of doing all this manually, but we all know how impatient LD's and Directors can get when they are asked to wait a sec while the programmer/operator pounds away at the console.
what eos family consoles can do is Automark. this means you have to have a cue, where the movers fade out, but the console will reposition them by itself, so when you fade in cue 2, the don't openly move but are already where they are supposed to go
Unfortunatly sometimes we are forced to use the same mover in one Q and then in the next and it is not always easy trying to explain to the LD and or Director that if you don't want to see the mover move/change gobo,color etc. then u will have give me as the programmer the oppertunity of plotting a dark Q so that I may make the change.
I think that there may be a strong need for Directors and some LD's to do a basic course on the basic operating principles of a moving light and colour scroller.
