ETC Eos Titanium, Eos, and Gio v2.0.0 - Manual (Page 24)

6 Eos Titanium, Eos, and Gio Operations Manual
Move Fade
Move Fade is a lighting control philosophy which determines how cues are played back.
Eos adheres to this philosophy.
In a Move Fade system, parameters do not change from their current setting until they are
provided a move instruction in a cue or are given a new instruction manually.
For example, in cue 1, channel 1 has been given an intensity value of 50%. This value does
not change until cue 20, where channel 1 is moved to 100%. Therefore, channel 1 has a
tracked intensity value of 50% in cues 2-19. If the user applies a manual intensity value of
25% while sitting in cue 5 (for example), that channel will stay at 25% until Cue 20 is
recalled - because 20 is the next cue in which channel 1 has a move instruction.
Cue List Ownership
Eos is capable of running multiple cue lists. Cue list ownership is determined by the cue
from which a channel is currently receiving its value. In Live, a parameter is considered to
be “owned” by a cue list when it is receiving its current value from that cue list.
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.