24.08.2013 Views

ETC Ion - Theatre Uwinnipeg

ETC Ion - Theatre Uwinnipeg

ETC Ion - Theatre Uwinnipeg

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Live and Blind<br />

Live and Blind are methods to view and edit data in your show files. When you press the<br />

[Live] key, the screen will show you the live display. When you press [Blind], you will see<br />

the blind display. In either case, you may use the [Format] key to alter how the data is<br />

displayed (see Using [Format], page 43).<br />

When in Live, the data displayed represents the data being sent from the console at that<br />

moment. In other words, the parameter data that is “live” on stage. When you edit data in<br />

live, those changes will become active and visible on stage as soon as the command line<br />

is terminated.<br />

When in Blind, the data displayed represents data from the record target you choose to<br />

view (cues, presets, palettes, and so on). When you edit data in Blind, changes will not<br />

automatically appear on stage, since the data you are modifying is not live. This is true even<br />

if the record target you are modifying is active on stage. It is possible to play a cue in Live,<br />

then switch to Blind and edit that cue in blind without affecting levels on stage. Edits in Blind<br />

do not require a [Record] command to be stored. They are considered stored when the<br />

command line is terminated. Any display that is not the Live display is considered Blind, and<br />

the Blind LED will be illuminated. For example, if you open patch, the blue LED on [Blind]<br />

will be lit to show that you are in a Blind display.<br />

HTP vs. LTP<br />

HTP (Highest-Takes-Precedence) and LTP (Latest-Takes-Precedence) are terms used to define<br />

the output of a channel parameter that is receiving data from multiple sources. In HTP, the highest<br />

level of all sources will be executed. In LTP, the most recent level received will be executed. Cue<br />

lists and submasters can operate as HTP or LTP for intensity parameters only. Non-intensity<br />

parameters (NPs) are always LTP. Submasters can operate as HTP or LTP for intensity. The default<br />

is HTP. <strong>Ion</strong>’s default cue list setting for intensity is LTP (see HTP/LTP, page 193). <strong>Ion</strong>’s default<br />

submaster setting for intensity is HTP.<br />

HTP<br />

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

highest of all inputs. HTP channels are also referred to as “pile-on”, because as control inputs are<br />

added (for example - you may bring up cues and multiple submasters that all have the same<br />

channel recorded at various levels), the system calculates which input has the highest level for that<br />

channel and outputs that level for the channel. As control inputs are removed (you pull some of the<br />

submasters down to zero), the console will adjust the channel level, if required, to the highest<br />

remaining level.<br />

LTP<br />

LTP is applicable to any parameter of any channel. LTP output is based on the most recent move<br />

instruction issued to the channel parameter. Any new values sent to the channel will supersede any<br />

previous values, regardless of the level supplied.<br />

<strong>Ion</strong> determines the LTP value for a channel, which is overridden by any HTP input values that are<br />

higher than the LTP instruction. This is then finally modified by manual control.<br />

Introduction 7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!