Table of Contents
Advertisement
Run mode features
20.1.2 NO transparency
Cue 1
A: SEQ1
B:
C:
D: SEQ3
BG1
Launch cue 1:
•
SEQ1 starts running on layer A.
•
SEQ3 starts running on layer D.
•
BG1 starts running on the cue scene level.
Launch cue2:
•
Xciter kills the sequence and cue scene processes that were started with cue 1.
•
SEQ2 starts running on layer B.
•
SEQ4 starts running on layer D.
•
BG2 starts running on the cue scene level.
The following processes are running as a result of cue 1 followed by cue 2:
•
SEQ2 is running on layer B.
•
SEQ4 is running on layer D.
•
BG2 is running on the cue scene level.
20.1.3 Precautions
You have to remain consistent when you assign sequences to cues.
Observe the following example:
Cue 1
A:
DIM open
B:
C:
D:
PT wall
BG1
In cue 1 you want the dimmer open and pan/tilt on the wall.
In cue 2 you want a dimmer with effect and pan/tilt to the centre of the dance floor.
Cue 1 followed by cue 2 does not produce the results you wanted. OK, pan/tilt goes to the center because
you placed both pan/tilt sequences on the same layer. But the dimmer sequence from cue 1 keeps running
70
Cue 2
A:
B: SEQ2
C:
D: SEQ4
BG2
Cue 2
A:
B:
DIM eff
C:
D:
PT centre
BG2
Xciter user manual
running processes
A:
B: SEQ2
C:
D: SEQ4
BG2
running processes
A:
DIM open
B:
DIM eff
C:
D:
PT centre
BG2
Advertisement
Table of Contents
