28
Priority Stacks
The consoles maintains so called „Priority Stacks“ which are used to figure out which values have been
last set by which playback to calculate output values accordingly. There is a “Low Priority” stack, as well
as a “High Priority” stack. Think of it as two different stacks of paperwork, where the piece of paper on
top of the stack is the most recent one. Cuelists set to high priority will always take precedence over non-
high priority cuelists.
Programmer Priority
The general programming layer, called the “Programmer” always takes precedence over playbacks,
unless it is in “Blind”-Programming mode. This may seem a bit strange at first glance, but in fact is very
useful since the programmer enables the user to gain additional control over the consoles output at any
time.
Priority Overview
The console has the following priority concept:
[Highlight]
5 Group Submasters
Playbacks at High Priority
2 Playbacks at Low Priority
Lowest
1 Default Values
Multiple Playbacks
The console allows multiple different cuelists to be run at the same time. You can have several cuelists
active at the same time, each on its own playback.
Examples
Starting multiple Cuelists
Lets say you start multiple cuelists one after another controlling the same fixture:
#1: Intensity 80%
#2: Intensity and Color 50% Red
The next table will show you what the results would be:
80% Blue Gobo 2