Tracking vs. cue only, Move fade, Htp vs. ltp – ETC Element v2.1.0 User Manual

Page 248: Tracking vs. cue only move fade htp vs. ltp

Advertising
background image

236

Element User Manual

Tracking vs. Cue Only

Element is, by default, a tracking console. Tracking relates to how changes to cue data are

handled. New data is saved to a cue, and unchanging data is allowed to track through to

the next cues until a change or move instruction is given. When editing a cue in tracking

mode, changes will track through subsequent cues as long as that previous data was also

tracking through those cues.

It is possible to change the default setting of Element to “Cue Only”. This prevents changes

from tracking forward into subsequent cues, unless overridden with a track instruction.

Element also has a [Cue Only/Track] button that allows you to record or update a cue as

an exception to the default setting. Therefore, if the console is set to Tracking, the button

acts as Cue Only. If console is set to Cue Only, it behaves as a Track button. When the Cue

Only override is used to edit previously tracked data, the adjustment is made only in the

current cue. The tracked data is protected in the following cues.

See

Using [Cue Only / Track], page 109

for more information.

Move Fade

Move Fade is a lighting control philosophy which determines how cues are played back.

Element 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.

Move Fade systems allow for fade-within-fade behavior. Fade-within-fade means that you

can start a long fade in one cue, and the following cues will not affect the long fade as long

as none of the following cues contain move instructions for the channels in the long fade

cue. A blocked value is considered a move instruction.

Additionally, manual changes to channels will not be removed by pressing [Go] unless the

incoming cue contains a move instruction for those channels.

HTP vs. LTP

HTP (Highest-Takes-Precedence) and LTP (Latest-Takes-Precedence) are terms used to

define the output 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. The cue list and submasters can operate as HTP or LTP for intensity

parameters only. Non-intensity parameters (NPs) are always LTP. Element’s default cue

list setting for intensity is LTP. Element’s default submaster setting for intensity is HTP and

channel faders are LTP. The cue list behavior and the submaster behavior can be modified

by the user. The channel behavior cannot be modified.

HTP

HTP is only applicable to the intensity of a channel. HTP channels will output the level that

is the highest of all inputs. HTP channels are also referred to as “pile-on”, because as

control inputs are added (for example - you may bring up cues and multiple submasters that

all have the same channel recorded at various levels), the system calculates which input

has the highest level for that channel and outputs that level for the channel. As control

inputs are removed (you pull some of the submasters down to zero), the console will adjust

the channel level, if required, to the highest remaining level.

Advertising