The system looks for dimmer values above 0 that uses tracked values. If needed then it stores the tracked values
before creating the values in the previous cues, thus preventing the cue from changing because of the tracking.
3.6. What is Cues
Cues is where we store the active values for our fixtures. This is very useful if we want to play it back later.
Cues are like a container where we can put values from our programmer. It then remembers the values. Cues are
often stacked in a cue list.
The cues and the cue lists are stored to Executors and can only exist on executors. You can't have cues outside the
executors. You can of course have values in your programmer without storing them in cues.
This can sound a little complicated, but the console usually does this for you. If you have active values and press
store and then a key associated with an Executor then it will store a cue. If it don't know what you want to do, then
it might ask in a window.
Cue also keeps the information about how we enter the cue. That's information like the fade times and delay and
what triggers the cue (could be a Go key or something else).
Related links
What is Executors
What is the Programmer
What is Tracking
How to Work with Cues
Cue Key
Cue Command
Cue view
3.7. What is Executors
Executors are the faders and keys below the screens (except the right screen).
They come in two versions. One with two keys and a fader and the other is just one key.
The keys have a printed symbol on them. It's and for the ones with two keys there's also a . You can change
the function of these keys using the Change Functions of Executor Buttons window.
To Next Page
Loading...
Need help?
General