The Xciter philosophy
Xciter
user
manual
21
3.4
Behavior of show elements
We call a running scene or sequence a process. You may not see it, but while you are programming or
creating a show, Xciter is running several processes in parallel (background scenes, sequences, playback
faders, programmer, direct access buttons, lamp procedures, etc.).
The following sections cover the behavior of show elements inside a show.
3.4.1
Process priority
Very often these processes have common channels, which means that they try to apply their own value to
the same destination, i.e. the same DMX address. Xciter has the following scheme to prioritize these
processes. This way you will get the same behavior every time you run the show and – most importantly –
you can predict that behavior when programming it.
system functions
programmer, active
programmer, inactive
override playbacks
sequences
background scene
default
direct access
highest priority
lowest priority
Lamp on, Lamp off, Lamp reset
smoke, strobe, extra1, extra2
active channels in scene editor, stored
temporary active channels in editor, not stored
sequences, activated with faders, during show
sequences A, B, C, D in the cue
background scene in the cue
default scene, when no other processes are active
0
1
2
4
5
6
7
8
Example 1: You have programmed some PAN and TILT values and dimmer open for a certain fixture in
the background scene. While this background scene is active in the show, you select the same fixture and
move the joystick. By doing this you put PAN and TILT values in the programmer on layers 5 and 6. These
layers have a higher priority (see priority table), thus you override the PAN and TILT values of the
background scene. This action is also called manual fixture override.
---
---
---
---
80
---
---
100
128
255
---
24
80
255
---
100
DIM
PAN
TILT
COLW
Programmer active
Programmer inactive
Background Scene
Result on DMX