Goto Q Out, Goto Q 0, and Off

Do you mean "Out" ?.  Don't see "Off" button on Eos or Ion.

- Out is self executing (doesn't require an Enter press) and take the intensities of those channels in the command line to null

- Go to Cue 0, takes all channel intensities to null, but leaves Non - Intensity Parameters (NIP's) at their values

- Go to Cue Out sets all channel values, intensities as well as NIP's to null.

SB

Off is in the "live" controls by the master fade pair on the eos.  

usesafesets said:

 

Off is in the "live" controls by the master fade pair on the eos.  

 

And I'll amend my comment that it's not on the Eos version of the Off-Line Editor

SB

Off will restore control to the background fader state (master cue list, at this time) and leave the "off" cue list where it currently is in the cue stack.   So, go to cue 0 and Go to cue out reset the cue list to the top, drive intensity to zero (go to cue 0) or drive all parameters to home value (go to cue out).

Hope that helps!

a

It totally does. Thanks Anne. Can you currently OFF with a macro? And to further my understanding. When you off, and units are not being used by the master playback, the values stay the same as the list that was just offed but become null? 

Yes, you can store the off command in a macro, and it can be learned live.  Keep in mind, though, that this will "off" whatever is currently loaded to that physical location.  There is another thread about the macro being stored based on the cue list, rather than the physical fader.  This is certainly doable (not right now), but it introduces some ambiguity.  It is possible to have a cue list loaded to different playback numbers (not just a different instance of the same playback).  So, if we add the ability to off/release the cue list, we will have to figure out which instance of that cue list you mean, in the event it is loaded to multiple playbacks.  Working on that! :-)

Yes, if there is no information for a channel/param coming from the master cue list, intensities are driven to home (zero) and NPs remain as currently set, but in an unowned state.  We are using "assert" timing in setup to control the timing of these actions.

:-)

a

Yes, you can store the off command in a macro, and it can be learned live.  Keep in mind, though, that this will "off" whatever is currently loaded to that physical location.  There is another thread about the macro being stored based on the cue list, rather than the physical fader.  This is certainly doable (not right now), but it introduces some ambiguity.  It is possible to have a cue list loaded to different playback numbers (not just a different instance of the same playback).  So, if we add the ability to off/release the cue list, we will have to figure out which instance of that cue list you mean, in the event it is loaded to multiple playbacks.  Working on that! :-)

Yes, if there is no information for a channel/param coming from the master cue list, intensities are driven to home (zero) and NPs remain as currently set, but in an unowned state.  We are using "assert" timing in setup to control the timing of these actions.

:-)

a

Great. That sounds good. On the note of playbacks. It would be nice to be able to assign those virtual playbacks as the programmer. And to lock them. So that when I unload, or release a list from a physical fader, the desk doesn't reassign a new playback to the list.