Subroutine jump-to-cue
Configuring DMX512
About Dimmer display
6
Previously, when your subroutine performed a jump-to-cue command, the
jump acted like a blocking cue, causing all LTP channels running in the
background to fade out. That meant that all background cues ended upon
the execution of a jump-to-cue command.
Now, if you choose a jump-to-cue style for your subroutine, you can
specify whether you want the execution of that command to cause
blocking or not. The default condition is blocking.
Select blocking or no blocking for
jump-to-cue commands.
Changes to DMX512 port settings are made in the Output Configuration
display. In that display, you can reset each port's mode of operation
(normal or Dimmer Doubled), DMX512 starting address and signalling
speed.
In version 3.03 code, the softkey used to change the DMX512 starting
address was labeled DMX512 Start. It has been relabeled Starting
Dimmer in version 3.1 code with no change in function.
Softkey S3 in the Output Configuration display has
been relabeled with no change in function.
You can use the About Dimmer display to reveal information about
dimmer patching and dimmer settings. If using ETCLink at the same time,
About Dimmer also displays rack assignment and load information.
New for the About Dimmer displays is a field that identifies the port and
port address to which a dimmer is patched.
About Dimmer identifies the port and port address
to which the dimmer is patched.
Subroutine jump-to-cue
Need help?
Do you have a question about the Expression and is the answer not in the manual?
Questions and answers