Introduction 17
When alternating between cue lists in sequential playback, an active cue list does not necessarily
own a channel unless that list has provided the last move instruction for that channel. For example,
assume a channel is owned by cue list 1 and is at a tracked value. If a cue from another cue list is
executed and provides a move instruction for the channel in the new cue, the channel is now owned
by the second cue list. It will not return to cue list 1 until that cue list provides a move instruction for
the channel.
Assert may be used to override this default behavior, allowing a cue list’s control over a channel to
resume, even when the channel’s data is tracked.
This rule is not followed when executing an out-of-sequence cue. An out-of-sequence cue is any cue
that is recalled via [Go To Cue], a Link instruction, or manually changing the pending cue. In general
applications, the entire contents of the cue (both moves and tracks) will be asserted on an out-of-
sequence cue.
Block vs. Assert
In previous ETC consoles, placing a block instruction on a channel was a way to treat a tracked value
as a move instruction, both in editing and playback. In Eos, this behavior is now split up. Blocked
channel data is an editing convention only, and it prohibits tracked instructions from modifying the
associated data. Blocked data has no impact on playback; the channels will continue to play back as
though they were tracks. Assert is used to force playback of a tracked/ blocked value.
Assert is not available on Element 2.
Live and Blind
Live and Blind are methods to view and edit data in your show files. When you press the [Live] key,
the screen will show you the live display. When you press [Blind], you will see the blind display. In
either case, you may use the [Format] key to alter how the data is displayed (see Using [Format] (on
page56)).
When in Live, the data displayed represents the data being sent from the console at that moment. In
other words, the parameter data that is “live” on stage. When you edit data in live, those changes
will become active and visible on stage as soon as the command line is terminated, unless auto play-
back has been disabled in Setup. See Auto Playback (on page160) for more information.
When in Blind, the data displayed represents data from the record target you choose to view (cues,
presets, palettes, and so on). When you edit data in Blind, changes will not automatically appear on
stage, since the data you are modifying is not live. This is true even if the record target you are modi-
fying is active on stage. It is possible to play a cue in Live, then switch to Blind and edit that cue in
blind without affecting levels on stage. Edits in Blind do not require a [Record] command to be
stored. They are considered stored when the command line is terminated. Any display that is not the
Live display is considered Blind, and the Blind LED will be illuminated. For example, if you open patch,
the blue LED on [Blind] will be lit to show that you are in a Blind display.
HTP vs. LTP
HTP (Highest-Takes-Precedence) and LTP (Latest-Takes-Precedence) are terms used to define the out-
put of a channel parameter that is receiving data from multiple sources. In HTP, the highest level of
all sources will be executed. In LTP, the most recent level received will be executed. Cue lists can oper-
ate as HTP or LTP for intensity parameters only. Non-intensity parameters (NPs) are always LTP.