ETC Ion - Theatre Uwinnipeg

Lighting Control Console
Operations Manual
Version 1.7
Copyright © 2009 Electronic Theatre Controls, Inc.
All Rights reserved.
Product information and specifications subject to change.
Part Number:4310M1210-1.7.0 Rev A
Released: 2009-07

ETC, Eos, I on, Emphasis, Expression, I nsight, Imagine, Focus, Express, Unison, Obses s ion II,
ETCNet 2, EDMX, Revolut i on, and Sensor+, are either registered trade marks or trademarks of
Electronic Theatre Cont rols, I nc. in the Unit ed Stat es and other countries.
ETC permit s the reproduc t i on of m ateri a ls i n this m anual only for non-c o m m ercia l purpos e s .
All other righ ts are reserved by ETC.
ETC i n t e n d s t h is d o cume n t , w het h e r p r i n t e d o r e l ectr oni c, t o b e p r o v i d e d i n i t s e n t i r e ty.

Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . .1
Using this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Register Your Ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Help from ETC Technical Services . . . . . . . . . . . . . . . . . . . . . . . . . .3
Important Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Channel = Fixture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Record Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Move Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Syntax Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Parameters and Parameter Categories . . . . . . . . . . . . . . . . . . . .5
Tracking vs. Cue Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Move Fade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Block vs. Assert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Live and Blind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
HTP vs. LTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Other Reference Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Help System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Online Eos/Ion User Forums . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Chapter 1 System Overview . . . . . . . . . . . . . . . . . . . . .9
System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Remote Processor Unit (RPU). . . . . . . . . . . . . . . . . . . . . . . . . .10
Remote Video Interface (RVI) . . . . . . . . . . . . . . . . . . . . . . . . . .10
Radio Focus Remote (RFR) . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Console Geography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Littlites
Cleaning Ion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Console Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Output Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Channel Counts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Cues and Cue Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Record Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Faders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Outputting DMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Chapter 2 System Installation . . . . . . . . . . . . . . . . . . .17
Basic System Risers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Large System Riser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
i

Chapter 3 System Basics . . . . . . . . . . . . . . . . . . . . . .21
Setting Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Power Up the Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Power Down the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Your First Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Single Monitor Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Dual Monitor Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
The Central Information Area (CIA) . . . . . . . . . . . . . . . . . . . . . . . . .27
Parameter Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Collapse/Expand the CIA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Lock the CIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Locking the Facepanel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Using the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Virtual Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Organizing the Direct Selects . . . . . . . . . . . . . . . . . . . . . . . . . .30
Using Direct Selects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Clear Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Display Control and Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Opening and Closing Displays. . . . . . . . . . . . . . . . . . . . . . . . . .33
Swap Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Scrolling within a Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Zooming Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Graphical User Interface (GUI) Display Conventions. . . . . . . . . . . .35
Indicators in the Live/Blind Display . . . . . . . . . . . . . . . . . . . . . .35
[Data] Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
[Time] Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
[Label] Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Using Flexichannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Indicators in the Playback Status Display . . . . . . . . . . . . . . . . .41
Using [Format] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Encoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Encoder Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Locking the Encoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Using Softkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Context Sensitive Softkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Changing Softkey Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Chapter 4 Managing Show Files . . . . . . . . . . . . . . . . .47
Create a New Show File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Open an Existing Show File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
ii Ion Operations Manual

Selective Partial Show Opening . . . . . . . . . . . . . . . . . . . . . . . .50
Merging Show Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Printing a Show File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Saving the Current Show File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Using Quick Save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Using Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Importing Show Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Exporting a Show File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Deleting a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Chapter 5 Patch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
About Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Clearing the Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Changing the Patch View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Channel View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Address View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Create and Edit Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Select Channel, Set Device Type, and Output Address . . . . . .63
Patching a Dimmer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Tutorial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Dimmer Doubling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Moving and Copying Channels . . . . . . . . . . . . . . . . . . . . . . . . .65
Unpatch a Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Patching Moving Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Tutorial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Patching a Compound Channel. . . . . . . . . . . . . . . . . . . . . . . . .67
Display Pages in Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
{Patch} Display and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .68
{Attribute} Display and Settings . . . . . . . . . . . . . . . . . . . . . . . . .70
{Database} Display and Settings . . . . . . . . . . . . . . . . . . . . . . . .72
Using {Offset} in Patch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Patch Channels from the Encoder LCD . . . . . . . . . . . . . . . . . . . . . .73
Using the Scroller/Wheel Picker and Editor . . . . . . . . . . . . . . . . . . .74
Using the Picker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Using the Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Calibrating a Scroller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Deleting Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Fixture Creator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Creating a New Fixture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
iii

Copying a Fixture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Importing a Custom Fixture . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Update Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Chapter 6 Using Groups . . . . . . . . . . . . . . . . . . . . . . .87
Recording Groups Live. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Ordered Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Editing and Updating Groups in Live . . . . . . . . . . . . . . . . . . . . .89
Selecting and Recalling Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Deleting Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Group List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Open the Group List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Ordered View and Numeric View. . . . . . . . . . . . . . . . . . . . . . . .90
Editing Groups from the Group List . . . . . . . . . . . . . . . . . . . . . .90
Using Groups as a Channel Collector . . . . . . . . . . . . . . . . . . . .91
Chapter 7 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Opening Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Desk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Chapter 8 Basic Manual Control . . . . . . . . . . . . . . . .107
Selecting Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
Select Channels From the Keypad . . . . . . . . . . . . . . . . . . . . .108
Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Setting Intensity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Level Wheel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Manual Control of Non-intensity Parameters (NPs) . . . . . . . . . . . .111
Parameter Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Setting Parameters with the Keypad . . . . . . . . . . . . . . . . . . . .112
Setting Non-intensity Parameters with the Encoders . . . . . . .112
Using the Color Picker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Select Last . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Multiple Intensity Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Lamp Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Using +% and -% . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Channel Intensity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Non-intensity Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Remainder Dim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Highlight and Lowlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
iv Ion Operations Manual

Highlight/Lowlight Rem Dim. . . . . . . . . . . . . . . . . . . . . . . . . . .125
Sneak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Flip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Channel Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Address at Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Address Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Flash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Using {Move To}. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Chapter 9 Storing and Using Presets . . . . . . . . . . . . 129
Storing Presets Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Storing Presets Using [Record] . . . . . . . . . . . . . . . . . . . . . . . .130
Storing Presets using [Record Only] . . . . . . . . . . . . . . . . . . . .131
Recalling Presets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Editing Presets Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Rerecord . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Using the Preset List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Opening the Preset List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Editing Presets in Blind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Editing in Table View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Editing in Spreadsheet View . . . . . . . . . . . . . . . . . . . . . . . . . .136
Deleting Presets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Removing Channels from a Preset . . . . . . . . . . . . . . . . . . . . .136
Chapter 10 Storing and Using Palettes . . . . . . . . . . . . 137
About Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Palette Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Intensity Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Focus Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Color Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Beam Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Storing Palettes Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Storing Palettes with [Record] . . . . . . . . . . . . . . . . . . . . . . . . .139
Storing Palettes with [Record Only] . . . . . . . . . . . . . . . . . . . . .140
Using Filters with Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
Recalling Palettes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
Editing Palettes Live. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Rerecord . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Editing Palettes in Blind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
Entering Blind Palette from Live . . . . . . . . . . . . . . . . . . . . . . .144
Editing in Blind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
v

Editing Palettes in Spreadsheet View . . . . . . . . . . . . . . . . . . .145
Editing Palettes in List View. . . . . . . . . . . . . . . . . . . . . . . . . . .146
Deleting Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Removing Channels from a Palette . . . . . . . . . . . . . . . . . . . . .147
Chapter 11 Working with a Single Cue List . . . . . . . . . 149
Basic Cueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Cue Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Recording Cues in Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Using Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Using Record Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Using Selective Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
Using [Cue Only / Track] . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Setting Cue Level Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Non-intensity Parameter Category Timing. . . . . . . . . . . . . . . .156
Delay Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Discrete Channel or Parameter Timing . . . . . . . . . . . . . . . . . .158
Assigning Cue Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
Clearing Cue Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Assert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
AllFade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Mark. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Preheat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Using the Execute List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
Modifying Cues Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Using [At] [Enter] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Using Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Using Record Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Move To. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
[Update] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Recording and Editing Cues from Blind . . . . . . . . . . . . . . . . . . . . .171
From Summary or Table Views . . . . . . . . . . . . . . . . . . . . . . . .172
From the Cue Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Using Encoders in Blind. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
Deleting Cues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
In Track Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
In Cue Only Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Chapter 12 Using Mark . . . . . . . . . . . . . . . . . . . . . . . . 175
AutoMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Conditions Triggering an AutoMark . . . . . . . . . . . . . . . . . . . . .176
Allowing a Live Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
AutoMark and Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
Referenced Marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
vi Ion Operations Manual

Setting Referenced Mark Flags . . . . . . . . . . . . . . . . . . . . . . . .177
Applying Flags as Channels are Marked . . . . . . . . . . . . . . . . .178
Reference Marks and Timing. . . . . . . . . . . . . . . . . . . . . . . . . .181
Chapter 13 Using Filters . . . . . . . . . . . . . . . . . . . . . . . 183
Record Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
Partial Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Removing Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Storing Data with Record Filters . . . . . . . . . . . . . . . . . . . . . . .186
Chapter 14 Working with Multiple Cue Lists . . . . . . . . 187
Recording to a New Cue List . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Using Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Using Record Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Using Assert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Using AllFade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190
Changing the Active Cue List . . . . . . . . . . . . . . . . . . . . . . . . .190
Using [Go To Cue] with Multiple Cue Lists. . . . . . . . . . . . . . . . . . .191
Using Go To Cue 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
Using Go To Cue Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
Using the Cue List Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Open the Cue List Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Chapter 15 Advanced Manual Control. . . . . . . . . . . . . 195
Using [Copy To] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Using [Recall From] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
Using {Make Null}. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
In Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
In Blind. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Using {Make Manual} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
Using {Make Absolute} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
Using [Capture] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
Using [Undo]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
Chapter 16 Multipart Cues. . . . . . . . . . . . . . . . . . . . . . 203
About Multipart Cues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
Record a Multipart Cue in Live . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
Creating a New Multipart Cue in Live . . . . . . . . . . . . . . . . . . .204
Setting Multipart Cue Attributes . . . . . . . . . . . . . . . . . . . . . . . .205
vii

Using Update in Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
Storing a Multipart Cue in Blind . . . . . . . . . . . . . . . . . . . . . . . . . . .207
Changing a Single Part Cue to a Multipart Cue. . . . . . . . . . . .207
Changing a Multipart Cue to a Standard Cue . . . . . . . . . . . . .207
Deleting a Part from a Multipart Cue . . . . . . . . . . . . . . . . . . . .207
Chapter 17 Cue Playback . . . . . . . . . . . . . . . . . . . . . . 209
Introduction to Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
Playback Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
Selected Cue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
Live / Blind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
Out-of-Sequence Cues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Go To Cue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
Slider Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
Assigning Faders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
Changing Fader Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
Playback Fader Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
Go and Stop/Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
[Go To Cue] [0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
Using Assert (Playback Button) . . . . . . . . . . . . . . . . . . . . . . . .218
Using Timing Disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
Using Freeze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
Using Stop Effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Release a Fader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Turning a Fader Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Using Rate Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Chapter 18 Using Park . . . . . . . . . . . . . . . . . . . . . . . . 221
Using Park . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
Park Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
Parked Values in Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
Scaled Parked Values in Live . . . . . . . . . . . . . . . . . . . . . . . . .224
Parked Addresses in Live . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
Park Values from the Park Display . . . . . . . . . . . . . . . . . . . . .225
Chapter 19 Creating and Using Effects . . . . . . . . . . . . 227
About Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
The Effect List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
Effects Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229
Effect Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
Step Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
Program a Step Effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235
Absolute Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
Program an Absolute Effect. . . . . . . . . . . . . . . . . . . . . . . . . . .238
Relative Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239
viii Ion Operations Manual

Focus Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239
Color Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240
Linear Effects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240
Define a Pattern Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241
Program a New Relative Effect . . . . . . . . . . . . . . . . . . . . . . . .241
Apply an Existing Effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
Editing Effects Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
Stop an Effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
Deleting an Effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
Effects on Submasters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243
Configuring an Effect Submaster. . . . . . . . . . . . . . . . . . . . . . .243
Recording an Effect to a Submaster . . . . . . . . . . . . . . . . . . . .243
Running an Effect from a Submaster. . . . . . . . . . . . . . . . . . . .243
Chapter 20 Using About . . . . . . . . . . . . . . . . . . . . . . . 245
About [About] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246
[About] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
About System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
About Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249
About Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250
About Cue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
About IFCB Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
About Presets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
Chapter 21 Storing and Using Submasters . . . . . . . . . 255
About Submasters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
Recording a Submaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
Submaster Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
Additive vs. Inhibitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
Proportional vs. Intensity Master . . . . . . . . . . . . . . . . . . . . . . .257
HTP vs. LTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
Exclusive Submasters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
Independent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
Changing Fader Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
On Fader Wings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
On the Slider Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
Loading Submasters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
On Fader Wings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
On the Slider Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
Updating a Submaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
Deleting a Submaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
Using Bump Button Timing With Submasters . . . . . . . . . . . . . . . .261
Controlling Subfades Manually . . . . . . . . . . . . . . . . . . . . . . . .261
Submaster List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262
Editing Submasters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262
ix

Chapter 22 Storing and Using Macros. . . . . . . . . . . . . 263
About Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
Store a Macro from Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
Using the [Learn] key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
Macro Editor Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266
Create a New Macro from the Display. . . . . . . . . . . . . . . . . . .268
Edit an Existing Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269
Play a Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
Stop a Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
Delete a Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
Chapter 23 Storing and Using Curves. . . . . . . . . . . . . 271
About Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272
Creating and Editing Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
Creating a Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
Editing Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274
Applying a Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
To Channels In Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
To Cues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Delete a Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Chapter 24 Using Show Control . . . . . . . . . . . . . . . . . 277
About Show Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Internal vs. External Time . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Programming an Event List . . . . . . . . . . . . . . . . . . . . . . . . . . .279
Time Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
Enabling Time Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
Timing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
Enabling the Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281
Programming a Time Code Event . . . . . . . . . . . . . . . . . . . . . .281
Learn Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281
Execution While Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281
Real Time Clock (RTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
Enabling Real Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
Real Time Clock Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
Programming Real Time Clock Events . . . . . . . . . . . . . . . . . .282
Analog Inputs and Relay Outputs. . . . . . . . . . . . . . . . . . . . . . . . . .283
Analog Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
Relay Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
MIDI Show Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
x Ion Operations Manual

MIDI Show Control Devices. . . . . . . . . . . . . . . . . . . . . . . . . . .283
Ion Command Interpretation . . . . . . . . . . . . . . . . . . . . . . . . . .284
Serial (RS-232). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
Enabling Serial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
Serial Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
Chapter 25 Multiple Users . . . . . . . . . . . . . . . . . . . . . . 287
About User ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
Assigning User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
Chapter 26 Using Partitioned Control . . . . . . . . . . . . . 289
About Partitioned Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
How to Use Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
Setting Up Partitioned Control . . . . . . . . . . . . . . . . . . . . . . . . .290
Partition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
Creating New Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291
Deleting Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291
Using Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292
Partitions in Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292
Flexichannel in Partitioned Control . . . . . . . . . . . . . . . . . . . . .292
Appendix A Eos Configuration Utility (Eos Shell). . . . . 293
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
What the Utility Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Eos Configuration Utility Reference . . . . . . . . . . . . . . . . . . . . . . . 294
General Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Maintenance and Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Appendix B Multi-console and Synchronized Backup . 307
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Multi-console setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Synchronized Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Appendix C Remote Processor Unit (RPU) . . . . . . . . . 315
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
xi

Software Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Basic Use Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Net3 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
Appendix D Remote Video Interface (RVI). . . . . . . . . . 319
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Basic Use Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Appendix E Remote Control. . . . . . . . . . . . . . . . . . . . . 323
Remotes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Remote Focus Remote (RFR) . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Console Section Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325
Basic Use Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
LCD General Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327
RFR Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Technical Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Appendix F Universal Fader Wings . . . . . . . . . . . . . . . 335
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
1 x 20 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
2 x 10 and 2 x 20 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
User Guidelines for Fader Wings . . . . . . . . . . . . . . . . . . . . . . . . . 338
xii Ion Operations Manual

Introduction
Welcome to the Ion Operations Manual. This manual is a comprehensive resource for users of the
Ion control system.
This chapter contains the following sections:
• Using this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
• Register Your Ion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
• Help from ETC Technical Services. . . . . . . . . . . . . . . . . . . . . .3
• Important Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
• Other Reference Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
• Online Eos/Ion User Forums. . . . . . . . . . . . . . . . . . . . . . . . . . .8
Introduction 1

Using this Manual
In order to be specific about where features and commands are found, the following naming and
text conventions will be used:
• Facepanel buttons are indicated in bold [brackets]. For example, [LIVE] or [Enter].
Optional keys are indicated in , for example, or .
• Browser menus, menu items, and commands you must perform are indicated in bold
text. For example: In the File menu, click Open. Or: Press [Record] [Preset] [Enter].
• Alphanumeric keyboard buttons are indicated in all CAPS. For example, TAB or CTRL.
• Keys which are intended to be pressed or held simultaneously are indicated with the
“and” symbol. For example, [Load] & [Timing Disable].
• Softkeys and clickable buttons in the Central Information Area (CIA) are indicated in
bold {braces}. A note about (more softkeys): this command is always
indicated as optional, and is only indicated once in an instruction regardless of how
many pages of softkeys exist. This is because there is no way to predict what softkey
page you are on at any given time. Press until you find the required
command.
• References to other parts of the manual are indicated in italics. When viewing this
manual electronically, click on the reference to jump to that section of the manual.
Note:
CAUTION:
WARNING:
Notes are helpful hints and information that is supplemental to the main text.
A Caution statement indicates situations where there may be undefined or
unwanted consequences of an action, potential for data loss or an equipment
problem.
A Warning statement indicates situations where damage may occur, people may
be harmed, or there are serious or dangerous consequences of an action.
Please email comments about this manual to: TechComm@etcconnect.com
2 Ion Operations Manual

Register Your Ion
Registering your Ion system with ETC ensures that you will be notified of software and library
updates, as well as any product advisories.
When you register, you will also be enrolled in “My ETC,” a personalized ETC Web site that
provides a more direct path of communication between you and ETC.
Register now at http://www.etcconnect.com/product.registration.asp.
Help from ETC Technical Services
If you are having difficulties, your most convenient resources are the references given in this user
manual. To search more widely, try the ETC Web site at www.etcconnect.com. If none of these
resources is sufficient, contact ETC Technical Services directly at one of the offices identified below.
Emergency service is available from all ETC offices outside of normal business hours.
When calling for assistance, please have the following information handy:
• Console model and serial number (located on back panel)
• Dimmer manufacturer and installation type
• Other components in your system (Unison ® , other consoles, etc.)
Americas United Kingdom
Electronic Theatre Controls Inc. Electronic Theatre Controls Ltd.
Technical Services Department Technical Services Department
3031 Pleasant View Road 26-28 Victoria Industrial Estate
Middleton, WI 53562 Victoria Road,
800-775-4382 (USA, toll-free) London W3 6UU England
+1-608 831-4116 +44 (0)20 8896 1000
service@etcconnect.com service@etceurope.com
Asia Germany
Electronic Theatre Controls Asia, Ltd. Electronic Theatre Controls GmbH
Technical Services Department Technical Services Department
Room 1801, 18/F Ohmstrasse 3
Tower 1, Phase 1 Enterprise Square 83607 Holzkirchen, Germany
9 Sheung Yuet Road +49 (80 24) 47 00-0
Kowloon Bay, Kowloon, Hong Kong techserv-hoki@etcconnect.com
+852 2799 1220
service@etcasia.com
Introduction 3

Important Concepts
Before using Ion, you should read and familiarize yourself with the concepts defined below. You will
find that understanding these terms and concepts will improve your efficiency with Ion.
Channel = Fixture
Output
A fixture is defined as a group of related addresses that together control a device. An
examples of a fixture would be an ETC Revolution. This moving light contains 31
parameters that together allow you to perform various functions such as pan and tilt. Each
of these attributes is addressed by a different output.
Ion treats fixtures and channels as one and the same. Unlike former ETC consoles where
a fixture occupied one channel for each parameter, Ion assigns each fixture a single
channel number. Individual parameters are then associated with that channel as additional
lines of channel information.
Outputs are the method by which level changes to channels are conveyed to attached
devices. These outputs are patched to channels. In its simplest form, an output is the data
signal sent from the console to turn on a light or modify a fixture parameter.
Record Target
A record target is any data location that you can store data using a [Record] or [Record
Only] command. Examples of record targets are cues, palettes, presets, and macros.
Move Instruction
A move instruction is any change to a parameter from its previous stored value. Any change
to a channel’s intensity is a move instruction. Any change to a channel’s pan or tilt is a move
instruction. Any change to a channel’s color mixing is a move instruction, and so on.
Syntax Structure
Note:
Most instructions can be entered into Ion through the command line. When entering data
into the console, the Ion command line expects instructions to be entered in a specific
structure, or syntax.
Generally speaking, the order of syntax can be described as:
• What are you trying to affect? (Channel, group)
• What do you want it to do? (Change intensity, focus, pan and tilt)
• What value do you want? (Intensity at full, Iris at 50)
Naturally other commands will be used in the course of programming your show, but most
other functions are modifiers of these three basic steps: modifying the channel(s) you are
are working with, determining what parameters of those channels you are impacting, and
what value you want them to assume. When working with record targets, the syntax is
similar.
Not all actions on Ion must be entered from the command line, although many will
result in a command line instruction. Other actions bypass the command line
entirely.
4 Ion Operations Manual

Enter
Since the command line can receive multiple edits and instructions at once, it is necessary
to let Ion know when you have completed your instruction in the command line. This is done
with the [Enter] key.
There are some commands which are self-terminating, and therefore do not require [Enter]
to be pressed. Some (but not all) of these commands are:
• [Out]
• [At] [+][+]
• [At] [-][-]
• [Full] [Full]
• Actions from the direct selects
Parameters and Parameter Categories
Ion divides fixture parameters into four major parameter categories: Intensity, Focus, Color, and
Beam. These are the parameters in each category:
• Intensity . . . . . . . . . . Intensity
• Focus . . . . . . . . . . . . Pan and Tilt
• Color. . . . . . . . . . . . . All color parameters (such as color wheel, CMY, scrollers, and
so on).
• Beam . . . . . . . . . . . . Any parameter not covered in the other categories.
Tracking vs. Cue Only
Ion is, by default, a tracking console. This means two things. First, tracking relates to how
cue lists are created. Once data is in a cue list, it will remain a part of that cue list, at its
original setting, and track forward through subsequent cues, until a new instruction is
provided or until it is removed from the cue list using filters or null commands.
Secondly, tracking relates to how changes to cue data are handled. Unless otherwise
instructed by a Cue Only command, changes to a parameter in a cue will track forward
through the cue list until a move instruction (or block command) is encountered.
It is possible to change the default setting of Ion to “Cue Only”. This prevents changes from
tracking forward into subsequent cues, unless overridden with a track instruction.
Ion 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.
Introduction 5

Move Fade
Move Fade is a lighting control philosophy which determines how cues are played back. Ion
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. The
original intensity of 50% will not be reapplied in subsequent cues unless specifically called
out by the cue or manually performed.
Cue List Ownership
Ion is capable of running multiple cue lists. In a multiple-cue-list console, cue list ownership
is an important concept. 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 Ion, 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.
6 Ion Operations Manual

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], page 43).
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.
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 modifying 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 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. Cue
lists and submasters can operate as HTP or LTP for intensity parameters only. Non-intensity
parameters (NPs) are always LTP. Submasters can operate as HTP or LTP for intensity. The default
is HTP. Ion’s default cue list setting for intensity is LTP (see HTP/LTP, page 193). Ion’s default
submaster setting for intensity is HTP.
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.
LTP
LTP is applicable to any parameter of any channel. LTP output is based on the most recent move
instruction issued to the channel parameter. Any new values sent to the channel will supersede any
previous values, regardless of the level supplied.
Ion determines the LTP value for a channel, which is overridden by any HTP input values that are
higher than the LTP instruction. This is then finally modified by manual control.
Introduction 7

Other Reference Materials
Help System
A keyhelp system is also contained within your Ion console. To access help, press and hold [Help]
and press any key to see:
• the name of the key
• a description of what the key enables you to do
• syntax examples for using the key (if applicable)
Note:
Keyhelp is included on most tangible action buttons on your Ion console. This
includes most softkeys and clickable buttons as well as the traditional keys on the
keypad.
As with hard keys, the “press and hold [Help]” action can be also used with
softkeys and clickable buttons.
Online Eos/Ion User Forums
You are encouraged to visit and participate in the ETC Eos/Ion User Forum, accessible from the
ETC web site (www.etcconnect.com). This gives you access to an online community of Eos and Ion
users where you can read about other users’ experiences, suggestions, and questions regarding
the product as well as submit your own.
To register for the ETC Eos/Ion User Forum:
Step 1: Go to ETC’s community web site (www.etcconnect.com/community). An introduction
page to the online community will open.
Step 2: You may register for the forum using the “register” link in the introduction or by
clicking the “join” link in the upper right corner of the page.
Step 3: Follow the registration instructions provided by the community page.
8 Ion Operations Manual

Chapter 1
System Overview
Inside this chapter you will find general descriptions of your Ion control console, how it fits into a
network control system, and the various areas of user interface.
This chapter contains the following sections:
• System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
• Console Geography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
• Cleaning Ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
• Console Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
• Outputting DMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
1 System Overview 9

System Components
Console
Ion is designed from conception as a fully integrated controller for conventional lights and
multi-parameter devices (for example: moving lights, color scrollers, gobo wheels). Attention to
detail across all areas of the system design and architecture allows you the utmost flexibility and
customization of use.
Ion allows designers and programmers to develop a mutual vocabulary for moving light control.
This implementation of simple and uniform syntax for moving light control provides a solid
foundation for both experienced and inexperienced moving light users.
Remote Processor Unit (RPU)
The RPU can be used as the primary or backup processor for the system or for primary playback in
installations that do not require a control console after initial programming is completed.
For more information, see the appendix Remote Processor Unit (RPU), page 315.
Remote Video Interface (RVI)
The remote video interface allows remote interaction with the lighting control system. This can be
for display purposes only. Additionally, with a mouse and alphanumeric keyboard attached, the RVI
can be used as a remote programming station. The RVI provides supports for a maximum of two
DVI or SVGA monitors, 1280x1024 minimum resolution.
For more information, see the appendix Remote Video Interface (RVI), page 319.
Radio Focus Remote (RFR)
The RFR provides wireless control of key front panel functions.The base station for the RFR can be
networked into the system, or can connect to a console or remote device using the USB interface.
For more information, see the appendix Remote Control, page 323.
10 Ion Operations Manual

Gateways
Ion is part of a fully networked system capable of direct output of both ETCNet2 and Net3.
Gateways can be configured to listen to either ETCNet2 or Net3 and provide interface to devices in
the lighting system that do not accept network communication directly. Gateways are provided for
DMX/RDM output, show control input and output and analog input and output.
• Net3 to DMX/RDM gateways are provided with a maximum of four outputs, which can be
male, female, or terminal strip.
• Show Control Gateway supports MIDI In/Thru and Out and SMPTE In.
• I/O Gateway supports 24 analog inputs, 16 SPDT contact closure outputs, and RS-232 serial
protocol.
1 System Overview 11

Console Geography
Below is a diagram of the Ion console with references made to specific areas of use. The terms and
names for each area and interface are used throughout this manual.
Parameter category/
Paged encoders
encoder page buttons
Note:
Power button
USB port
LCD screen
Blackout and
Grandmaster
Terminology
Power Button
The Ion hardware was recently revised. For previous hardware versions, please
see the Ion v.1.4 Operations Manual Rev B.
The power button on the front of the console is used to power up the Ion console. A separate power
switch, located in the rear panel of the console, can be used to disconnect power from the console’s
internal components.
WARNING:
Playback
controls
IEC receptacle
Control
keypad
MIDI Out and In
Hard power switch VGA port
DVI video
Ethernet
ports 4 USB
ports port
Navigation keys
Level
wheel
DMX ports
1 and 2
Softkeys
Remote
trigger
port
Phone
Remote
Port
Before servicing the Ion control console, you must switch off the power
from the rear of the console and disconnect the power cord completely.
12 Ion Operations Manual

USB Ports
One USB port is provided on the front of the console to connect any USB storage device. An
additional four USB ports on the rear panel of the console can be used to connect peripherals such
as an alphanumeric keyboard, pointing device, or touchscreen control for external monitors.
Encoders
Encoders and the LCD (see below) for control of non-intensity parameters are provided at the top
center of the console. The four encoders are pageable controls, which are populated on the LCD
with the parameters used in your show.
The encoders can also be used to enter information into your patch.
LCD
This display accompanies the CIA as an additional user interface. This LCD offers you softkeys,
encoder information, and an additional view of the command line.
Load
The load button is located above the fader pair at the bottom of the LCD and is used to load the
specified cue.
Control Keypad
The control keypad area is divided into three general sections including record targets, numeric
keypad and modifiers, and special function controls.
Level Wheel
Proportionally adjusts intensity for selected channels. It also provides scrolling and zoom functions
in various modes.
Navigation Keypad
Used for quick access to the live and blind displays, format, paging, and navigation within displays.
Parameter Category/ Encoder Page Buttons
Parameter buttons are used to select parameter categories and change encoder pages.
IEEE Ethernet 802.3 Ethernet Port
Ethernet port for connection to a network switch, network gateways, and accessory devices.
Littlites ®
You may connect a Littlite to the side of your Ion console.
Cleaning Ion
Should the exterior or LCD of your Ion require cleaning, you may gently wipe them with a
dampened (not dripping), non-abrasive paper towel or soft cloth.
If this does not clean the console sufficiently, you may apply some window cleaner (containing
ammonia is fine) to the cloth and repeat the process until clean.
1 System Overview 13

Console Capacities
Output Parameters
• 1,024 outputs (DMX channels)
-or-
• 1,536 outputs (DMX channels)
-or-
• 2,048 outputs (DMX channels)
Channel Counts
• 10,000 channels
Cues and Cue Lists
• Up to 999 cue lists
• Up to 10,000 cues
Record Targets
• 1,000 Groups
• 1,000 x 4 Palettes (Intensity, Focus, Color and Beam)
• 1,000 Presets
• 1,000 Effects
• 1,000 Macros
Faders
• 1 dedicated Master Playback, with Go and Stop/Back
• a maximum of 200 configurable playbacks, with Go and Stop/Back
• a maximum of 300 configurable submasters, with Bump and Assert/Select
14 Ion Operations Manual

Outputting DMX
In order to output control levels from Ion, you can either use the DMX ports on the back of the
console (see Local DMX, page 305 in the ECU appendix) or you may connect a Net3 gateway or
Net2 node. If your device receives Net3 or ETCNet2 directly, no gateway or node is required.
Nodes and gateways must be given an IP address before they can function with Ion. This may
require using NCE (Network Configuration Editor) or GCE (Gateway Configuration Editor) and a
Windows ® PC to configure the gateways or nodes. The NCE or GCE Software CD and related user
manuals and setup guides were packaged with your gateway or node. Use these materials to
prepare them for use with Ion.
For more information on Net3 gateways or Net2 nodes, see the product literature that accompanied
the hardware or download it from our website at www.etcconnect.com.
1 System Overview 15

16 Ion Operations Manual

Chapter 2
System Installation
This chapter depicts the placement of Ion in a few lighting system risers. It also details connection
of the various components of your Ion hardware.
This chapter contains the following sections:
• Basic System Risers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
• Large System Riser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
2 System Installation 17

Basic System Risers
Ion Console
Ion Console
Net3 Gateway
Remote Processing Unit
DMX/RDM
To ETCNet2/3
Net3 Gateway
Sensor+® Dimmers
DMX/RDM
To ETCNet2/3
18 Ion Operations Manual

Ion Console
Client Software
Eos Console
Large System Riser
Ethernet
Two Remote
Processing Units
(RPU - for backup)
Net3 Remote
Video Interface (RVI)
Radio Focus
Remote
(RFR - Receiver)
Net3
Gateways
Radio Focus
Remote
(RFR - Transmitter)
Contact In, Contact Out, RS232
MIDI, SMPTE
DMX/RDM
Sensor+ Dimmers
2 System Installation 19

20 Ion Operations Manual

Chapter 3
System Basics
This chapter explains the base level procedures for setting up, navigating, and understanding how
to operate Ion.
This chapter contains the following sections:
• Setting Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
• Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
• The Central Information Area (CIA) . . . . . . . . . . . . . . . . . . . .27
• Using the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
• Display Control and Navigation . . . . . . . . . . . . . . . . . . . . . . .33
• Graphical User Interface (GUI) Display Conventions. . . . . .35
• Using [Format] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
• Using Flexichannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
• Encoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
• Using Softkeys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
3 System Basics 21

Setting Up the Hardware
Follow these steps to prepare your Ion for use.
Step 1: Place your console on a firm, level surface. Be sure to leave space for access to the
rear of the console. You will need to connect several items to the ports on the back.
Step 2: Connect any monitors to the proper ports on the back of the console.
Note:
Ion supports up to 2 monitors, either 2 DVI monitors or 1 DVI and 1 VGA.
Step 3: Connect the keyboard and mouse. Attach to the appropriate connector on the back of
the console.
Step 4: If you will be connecting to an Eos/Ion network, connect the appropriate ethernet
(CAT 5 or better) cable to the ethernet port on the back of the console.
Step 5: If you plan on using the DMX ports on the back of Ion to control your lighting system,
attach the appropriate DMX connector and cable to the desired port. These ports
default to output DMX universes one and two. Configuration is required to use any
other universe. For more information, see Local DMX, page 305 in the ECU appendix.
Step 6: Attach the appropriate IEC power cable for your location to the IEC connector on the
back of the console, just above the power switch.
Your console hardware is now ready to be powered up.
22 Ion Operations Manual

Power
Power Up the Console
Note:
Note:
Step 1: Attach the appropriate power cable to the IEC connector on the rear of the console.
Step 2: Press the I/O switch (I is “on”) next to the IEC connector on the rear of the console to
turn power on. This will provide power to all internal electronics.
Step 3: Press the power button, located in the top left corner of the console, above the USB
port. The button LED will illuminate blue to indicate the console is running. The
console will boot up into the Ion environment. The Ion system is now ready for use.
Power Down the Console
Note:
You need to wait about 30 seconds between steps 2 and 3.
In the future, you may go straight to the welcome screen by adjusting a setting in
the ECU. See Show Welcome Screen, page 297 in the ECU appendix.
Step 1: After saving your show (see below), in the browser menu select File>Power Off
Console. A dialogue box opens asking you to confirm.
Step 2: Confirm this command by clicking {OK} in the dialog box. The console will power
down.
Ion is a persistent storage console. Therefore if you shut down your system
without saving the show file, you will return to the same place in your show when
you reboot.
3 System Basics 23

Your First Interaction
When you first start up Ion, you will immediately enter the Ion software environment. A welcome
window will greet you with a {Let’s Begin} button visible on the screen. Use your mouse to click on
{Let’s Begin} or you can press the [Enter] key.
Since Ion can be set up with one or two monitors, what you will first see depends partly upon the
number of monitors you are using.
Single Monitor Configuration
When using a single monitor, the top half of the initial display screen becomes the primary viewing
area for displayed information. Ion will first open with the live table display on the top (primary) half
of the screen and the CIA on the bottom half of the screen.
When the CIA is open, one line of the playback status display is visible above the double arrows.
You can view more of the playback status display by collapsing the CIA (see Collapse/Expand the
CIA, page 27).
Primary screen -
live display
Playback
Status Display
Initial View - Primary/CIA
Command
line
24 Ion Operations Manual
CIA

You can use the [Swap] key to change the view of the display. Multiple presses of [Swap] will yield
the following responses:
• First press - Expanded View - expands the top (primary) portion of the display to the full
screen. This essentially hides the CIA from view.
• Second press - Playback Status View - exposes the CIA again and switches the primary
area to the playback status display.
• Third press - Primary/CIA View - returns the screen to the original primary display with the
CIA exposed.
As you open other displays later while programming, they will open in place of the live table view.
The playback status display is always the display visible by pressing [Swap].
Expanded View
Live Display
Playback Status View
3 System Basics 25

Dual Monitor Configuration
When two monitors are used, one monitor will show the playback status display as well as the CIA
and the other monitor becomes the primary area for displayed information. In this dual
configuration, Ion will first open with the live table display open on the primary monitor and the
playback status and CIA visible on the other monitor.
Dual Monitor
Primary Display (Live)
You can press the [Expand] key to expand the primary display onto the secondary display.
Dual Monitor
Primary Display (expanded)
Dual Monitor
Playback Status Display
To return to the original view, press [Expand] again. For additional information on displays, see
Display Control and Navigation, page 33.
Please see External Monitor Arrangement, page 298 for more information on configuring Ion for a
dual monitor configuration.
26 Ion Operations Manual

The Central Information Area (CIA)
The Central Information Area (CIA) is displayed on the lower portion of the screen. By default, the
CIA consists of two primary areas: the parameter display and the browser.
Parameter display
Parameter category button labels
Parameter Display
This display shows the parameters available for patched channels. It is also where you can select
which parameters to view in live or blind. The parameter display will dynamically change depending
on the channel (fixture) selected and its applicable parameters.
Browser
The browser is the interface for numerous functions including saving a show, opening a show,
changing settings, viewing record target lists, opening displays and many other functions.
Collapse/Expand the CIA
Browser
Double arrows
CIA show/hide
CIA lock
(shown
unlocked)
It is possible to collapse the CIA from view. To do this, you can click the double arrow icon centered
above the CIA. The CIA will collapse from view, exposing a larger viewing area of whatever display
is visible above the CIA. The double arrows will move to the bottom of the screen.
To expand the CIA into view again, click the double arrow at the bottom of the screen. The CIA will
reopen.
3 System Basics 27

Lock the CIA
You can lock the CIA in place to prevent it from being collapsed.
To lock the CIA, click on the lock above the browser. The double arrow above the CIA will
disappear and the lock will “lock”.
To unlock the CIA, click the sunken lock again and the double arrows will reappear.
Locking the Facepanel
It is possible to lock out the facepanel, which prevents any actions from the command line or CIA.
To lock out the facepanel, press [Clear] & [Escape]. To unlock the facepanel, press [Clear] &
[Escape] again.
28 Ion Operations Manual

Using the Browser
To use the browser, you must first draw focus to it by clicking anywhere in the browser area of the
CIA or by pressing the [Displays] key.
When focus is on the browser, the window border highlights in gold. The scroll lock LED illuminates
red and the paging keys will now control selection in the browser.
Menu arrows
Opened menu
Sub menus
Note:
• Use the page arrow keys to move the selection bar up and down the list. You can also use the
level wheel to scroll through the list.
• When the bar highlights the desired menu, press [Page ] to open the menu.
• Continue pressing [Page ] to open submenus.
• Scroll to the item you wish to open using [Page ] or [Page ] and then press [Select]. You
may also click the item you wish to open and then press [Select]. You can also use the level
wheel to scroll in the browser.
• If you wish to close a submenu scroll to that item and press [Page ].
• To draw focus to the browser at any time, press the [Displays] key.
Virtual Keyboard
The [Select] key can be used to confirm a choice in the browser.
Selection bar
Scroll bar
It is possible to open a virtual keyboard in the CIA which mimics the hard keys found on the actual
Ion keypad. This virtual keyboard is accessible from the browser.
The virtual keyboard is found with the other virtual controls in the browser. Navigate to
Browser>Virtual Controls>Virtual Keyboard.
This will give you click access to the Ion hardkeys on the CIA. The browser and parameter display
will be hidden from view while the virtual keyboard is open. To close the virtual keyboard, press the
[Displays] button.
3 System Basics 29

Direct Selects
Ion gives you the option of opening direct select modules on the monitors.
To open the direct selects on a monitor:
Step 1: Go to Browser>Virtual Controls>5 x 10 Direct Select Module. A window will open
in the CIA displaying your monitor placement options for the module.
Step 2: Click the placement option in the CIA in which you want the module to appear.
To close the direct selects on a monitor:
Step 1: Go to Browser>Virtual Controls>Close Module. The placement screen will appear
again in the CIA.
Step 2: Click the placement of the module you wish to close. The module will be removed.
For information on populating direct selects see Organizing the Direct Selects below.
Slider Module
If you prefer to have faders available to you, the monitors can be populated with virtual faders,
called slider modules.
To open the slider module on a monitor:
Step 1: Go to Browser>Virtual Controls>Slider Module. A window will open in the CIA
displaying your monitor placement options for the module.
Step 2: Click the placement option in the CIA in which you want the module to appear.
To close the slider module on a monitor:
Step 1: Go to Browser>Virtual Controls>Close Module. The placement screen will appear
again in the CIA.
Step 2: Click the placement of the module you wish to close. The module will be removed.
Organizing the Direct Selects
You have considerable flexibility in how you organize the direct selects. They may be arranged to
display one of several different types of data.
To choose which information to view:
Step 1: Click the {Select} button for any block of direct selects. You will be offered the
following choices to view: Channels, Groups, Intensity Palettes, Focus Palettes,
Color Palettes, Beam Palettes, Presets, Macros, and Effects.
Step 2: Click the button for the data you wish to view and the associated direct selects will
populate with any recorded information of that type. If there is no recorded information
of that type the block of buttons will remain empty but will populate with data of that
type as associated record targets are stored.
Step 3: You may also click {Select} again, without choosing any option, to return to the
previous state.
You can increase or decrease the size of any set of direct selects by pressing the {20/50} button,
which will change the display between one set of 50 buttons and two sets of 20 buttons.
30 Ion Operations Manual

Using Direct Selects
Direct selects allow access to a number of controls, including a channel select display. If there are
more items than can be viewed at once, you may view subsequent pages by using the page buttons
({Page }, {Page }) by the direct selects.
Selecting Channels with Direct Selects
Channel direct selects are highlighted when selected. Channel selection is generally an additive
process, if channels 1-5 are selected, pressing {Channel 6} adds channel 6 to the selection,
leaving channels 1-5 also selected. Pressing {Channel 6} again will deselect the channel.
If you have labeled channels in patch, those labels will be displayed above the channel number
when viewing channels in the direct selects.
It is possible to double hit a channel button. This selects that channel and deselects any previously
selected channels.
• {Channel 1} - adds channel 1 to currently selected channels, if not currently selected.
• {Channel 1} {Channel 10} - adds channels 1 and 10 to currently selected channels.
• {Channel 1} {Channel 1} - selects channel 1, deselects all other channels.
• {Page } - pages direct selects down by one page.
• {Page } - pages direct selects up by one page.
3 System Basics 31

Clear Functions
You can access the various clear options from the browser by selecting {Clear} from the main
browser menu. The clear functions window will open in the CIA.
From this menu you can select one of the available clear options by clicking on the desired button
in the CIA. Ion will ask you for a confirmation before performing the selected clear. For {Clear
Targets}, Ion will allow you to choose which record targets you want to clear.
From the {Clear Targets} screen you can select which record targets you wish to clear. The buttons
at the center of the CIA represent all of the record targets that you can choose to clear. By default
all components are selected (gray) and will be cleared. To withhold any targets from being cleared,
simply deselect them in the CIA by clicking the respective button.
To reselect all targets, click the {Reset} button and all buttons will return to gray (selected). To stop
the process, click the {Cancel} button.
When you have selected or deselected all of the record targets you require, click {OK}.
After clearing, the CIA will return to the browser. If you want to perform additional clear functions,
you must select {Clear} from the browser again.
To exit the clear functions screen without clearing, press the [Displays] key at any time or select a
clear button and then select {Cancel} from the confirmation screen.
32 Ion Operations Manual

Display Control and Navigation
Opening and Closing Displays
Displays can be opened and closed in different ways, depending on the display. Many displays are
accessible from the browser, while other displays are accessible from the LCD softkeys. The blind
displays of record targets (also called “lists”) can be quickly accessed by double pressing the record
target button (for example, [Preset] [Preset] opens the preset list).
From the browser
Open and navigate the browser as described in Using the Browser, page 29. When you open a new
display (such as the cue list index, group list, or patch), it will open on the primary display. If the
display does not open to a monitor (such as setup or the browser) it will open in the CIA.
Again, any time you wish to return to the browser, simply press [Displays].
From the hardkeys
You can open list views of any record target by double-pressing the key for the desired record
target.
From the LCD softkeys
To open any displays accessible from the softkeys, press [Displays]. The softkeys will repaint to
display:
• Effect Status
• Color Picker
• Patch
• Setup
• Curves
• Browser
Any of these softkeys will open the associated display with a single press.
Closing Displays
To close any display:
• Press the [Displays] key again to open a different display.
• Press [Escape] to close the active display. The screen will return to live or blind.
• Press [Live] or [Blind] to replace the display with the live/blind view.
To close a display in the CIA, press the [Displays] key and the browser will reappear.
3 System Basics 33

Swap Displays
When using two monitors, you can swap displays between monitors by pressing the [Swap] key.
Press it again to return to the original configuration.
Scrolling within a Display
By default the page keys will advance/retreat a display by one page per press. However, to scroll
through displays you may press the [Scroll Lock] key on the keypad. The LED on the button
illuminates red when in scroll lock mode.
Scroll lock is a toggle state. When scroll lock is first pressed:
• [Page ] - scrolls table, spreadsheet and channel views down,
• [Page ] - scrolls table, spreadsheet and channel views up,
• [Page ] - scrolls table and spreadsheet views right,
• [Page ] - scrolls table and spreadsheet views left.
Zooming Displays
You may zoom in and out on displays. To do this, press and hold the [Format] button and scroll the
Level Wheel to alter the display. Scrolling the wheel up zooms in. Scrolling the wheel down zooms
out. Zooming the channel summary display when it is in 100 channel mode is not supported. You
can also zoom using a wheel on a mouse.
34 Ion Operations Manual

Graphical User Interface (GUI) Display Conventions
Ion relies on many traditional ETC indicators which you may be familiar with, as well as some new
ones. This section identifies the graphical and colorful conventions used in Ion to indicate
conditions to you.
Indicators in the Live/Blind Display
This is the live/blind summary view.
Note: The color and text conventions described below apply regardless of the format of
live/blind being used (see Using [Format], page 43).
Channel Number
Straight line under
channel heading
Intensity data (I)
Effect data
No other parameter
categories
Wavy line under
channel heading
Intensity data (I)
Focus data (F)
Color data (C)
Beam data (B)
F, C, B icons
when collapsed
Conventionals
Most of the channels in the above image are conventional
channels (intensity is the only available parameter).
Conventionals have a straight line beneath the channel
number. They also display only the top field, intensity, as
no other parameters are available on a conventional
channel.
Moving Lights or Multi-parameter Devices
Several channels in the image are moving lights
(possessing more parameters than just intensity).
Moving light channels have a wavy line beneath the
channel number as well as parameter category indicators
at the bottom of the channel.
This view also has additional data fields beneath intensity
(F, C, B). This information can be suppressed by pressing
and holding [Data] and any of the encoder paging keys
(Focus, Color, Image, Shutter, or Form). Doing so will
leave only the intensity field and FCB indicators at the
bottom of the channel.
3 System Basics 35

Color indicators
Ion uses color to indicate the selection state and information about channel or parameter levels.
Channel numbers/channel headers
Selected
Unselected
• Gray number . . . . . . . . .Unpatched channel number.
• White number . . . . . . . .Selected channel number.
• Bright White number . .Channel is parked.
• Gold number . . . . . . . . .Channel is captured.
• Gold outline . . . . . . . . .Selected channel.
• Number with no graphicDeleted channel.
Channel or parameter levels
• Red. . . . . . . . . . . . . . . . .Manual data (any data that has been set but not yet stored to
an active cue or submaster).
• Blue . . . . . . . . . . . . . . . .The intensity value is higher than in the previous cue.
Non-intensity parameters (NPs) are in blue when any move
instruction has occurred. Unmarked.
• Green . . . . . . . . . . . . . . .The intensity value is lower than in the previous cue.
Also used in reference marking to indicate a channel has just
marked.
• Magenta. . . . . . . . . . . . .In a mark cue, the recorded value is tracked, unchanged from
a previous cue, or in a reference cue, that a stored mark is still
intact.
• White . . . . . . . . . . . . . . .The value is blocked.
• White with an underscoreValue is autoblocked.
• Gray . . . . . . . . . . . . . . . .Default or the value is a null value (from either {Make Null}
or a filter). When nulled, a gray “n” appears next to the value.
• Yellow . . . . . . . . . . . . . .Data set from a submaster.
36 Ion Operations Manual

Text Indicators in live/blind
Please note examples of text indicators in the following graphic:
“B” “_” (underscore) “C” “I” “N” “A”
“t”
“Ph” “R” “M”
“P” “+” “Pr” “Q 10/4” “CP2” “MK”
Color conventions listed above apply to text indicators as well. Therefore red indicates a manual
value that must be stored.
Color conventions listed above apply to text indicators as well. Therefore red indicates a manual
value that must be stored.
• _ . . . . . . . . . . . . . . . . . . .Underlined value (white) indicates a system-applied block
(also called an auto-block).
• A. . . . . . . . . . . . . . . . . . .Indicates the channel or parameter is asserted.
• B. . . . . . . . . . . . . . . . . . .Indicates the channel or parameter is manually blocked. This
block must be stored.
• C. . . . . . . . . . . . . . . . . . .Captured Channel
• I . . . . . . . . . . . . . . . . . . .Channel is controlled by an inhibitive submaster or
grandmaster. When displayed in the Block flag, “I” indicates
a cue level intensity block.
3 System Basics 37

• IP, CP, FP, BP . . . . . . . .Indicates that the value is referenced to a palette (Intensity,
Color, Focus, or Beam). This text is followed by a number,
indicating which palette is being referenced. This can be
substituted with the palette label if the “Show Reference
Label” setting is activated (see Show Reference Labels, page
103). Holding down [Label] will toggle between the palette
label and palette number.
• MK . . . . . . . . . . . . . . . . .Indicates the channel is marked for a later cue. The cue
number is indicated in the other categories (see “Q” below).
• N. . . . . . . . . . . . . . . . . . .Indicates the value is null (from either {Make Null} or a filter).
• P . . . . . . . . . . . . . . . . . . .Indicates the channel is parked.
• Ph. . . . . . . . . . . . . . . . . .Indicates the channel is at a preheat level.
• Pr . . . . . . . . . . . . . . . . . .Indicates that the value is referenced to a preset. This text is
followed by a number, indicating which preset is being
referenced. The preset label may also be shown if this setting
is enabled (see Show Reference Labels, page 103). Holding
down [Label] will toggle between the preset label and preset
number.
• Q. . . . . . . . . . . . . . . . . . .Found in the non-intensity categories of a marked channel.
The “Q” is followed by a number indicating which cue the
mark is in preparation for.
• t . . . . . . . . . . . . . . . . . . .The channel has discrete (parameter/category-specific)
timing.
• + . . . . . . . . . . . . . . . . . . .Found in place of parameter data in summary view. Indicates
that not all parameters in that category are at the same value.
This indicator is found only in the summary view or in table
views when the parameters are collapsed into a category
view.
• ! . . . . . . . . . . . . . . . . . . .Indicates an ACN or RDM error.
The symbols that appear in the Mark flag include:
• D. . . . . . . . . . . . . . . . . . .AutoMark is disabled.
• R. . . . . . . . . . . . . . . . . . .Indicates a manual reference override. Manual changes have
been made that override a previously stored reference (such
as to a palette or preset). Once recorded, the reference will
be broken. If updated, the referenced target will be updated
as well, unless otherwise instructed.
• M . . . . . . . . . . . . . . . . . .Indicates a mark is placed, but manual, and must be stored.
Is blue when stored.”m” indicates cue is not marking.
• + . . . . . . . . . . . . . . . . . . .Indicates a cue is both a marking and reference cue when
displayed in the mark flag.
• - . . . . . . . . . . . . . . . . . . .Indicates a dark move, a cue that has any non-intensity
parameters moving on channels whose intensity is at 0.
• x . . . . . . . . . . . . . . . . . .Indicates that a mark has been placed, but the mark is
broken.
38 Ion Operations Manual

[Data] Key
Pressing and holding [Data] allows you to view the values behind any referenced or marked data.
[Data] exposes the next lower reference level. So if you view a palette reference and press [Data],
the absolute data will be displayed instead. If you are viewing a preset, absolute or palette data will
be displayed, depending on what is contained in the preset.
The [Data] key is also used in combination with the encoder paging keys to change the level of
detail in summary and views, and to select parameters to view in spreadsheet modes.
[Time] Key
Pressing and holding [Time] allows you to view discrete timing data behind any channel parameter.
[Time] exposes channel or parameter specific timing for any channels in the current cue. The first
value is the delay time. If “--” is displayed, there is no delay. The value to the right of the / is the
transition time.
[Label] Key
Pressing and holding [Label] toggles the view to show reference labels or numbers depending on
what display setting is being used. See “Show Reference Labels” on page 103.
3 System Basics 39

Using Flexichannel
Flexichannel (use of the [Flexi] key) allows you to view only channels meeting a certain criteria in
the live/blind display, therefore removing unwanted data from view. Flexichannel has several
available states which include allowing you to view:
• All channels
• All patched channels
• All show channels (any channels that have data stored in a cue or submaster)
• Active channels (channels with intensity above zero or a move instruction)
• Selected channels
In flexi mode, any selected channels (including the last channel selection) are always included in
the view. Gaps in channel numbers are indicated by a vertical line between the channels where a
gap in numbering occurs.
To change flexi modes in the live/blind display, press [Flexi] to cycle through the views listed above.
When [Flexi] is held down, the softkeys change to represent all of the available flexi states. You can
select the desired flexi view from those keys.
[Next/Last] can be used to select the next or last channel in the current flexi mode.
[Thru] can be used to view only channels in the current flexi mode (except for selected channels
mode) as long as either the first or last channel in the [Thru] range is included in the current flexi
mode. To include channels not in the current flexi mode, [Thru] [Thru] can be used.
Flexichannel with Timing
You may also engage a “Channels with Timing” flexichannel state by pressing [Time] & [Flexi].
This will display all channels that have discrete timing in the current cue and will remove channels
without discrete timing from view.
You may still press [Time] to view the discrete time behind any parameter or category.
The display will remain in this state until you disengage it by pressing [Time] & [Flexi] again.
View Channels
You may select specific channels to appear in another flexichannel state called “View Channels”.
This state does not exist until you select channels to view. After view channels is activated, it will
appear in the rotation of flexichannel states when [Flexi] is pressed.
To select channels to view:
Step 1: Select channels on the command line (do not press [Enter]).
Step 2: Press and hold [Flexi].
Step 3: Press {View Chans}. The “View Channels” flexi state will be created and the
channels you selected will be visible in it.
The channels you selected will be visible in this flexi state until you select other channels and press
{View Chans} again. At any time, you can access the last channels you defined for this state by
pressing [Flexi] until this state is visible.
To redefine the selected channels in the state, simply follow the steps above again.
40 Ion Operations Manual

Indicators in the Playback Status Display
Indicates the timing for a
category.
Color indicators
• Gold . . . . . . . . . . . . . . . .Any item (cue, list, page) highlighted in gold indicates
“current”.
Outlined in gold indicates “selected”.
• Red. . . . . . . . . . . . . . . . .Cue fade is in progress (cue list area)
Text indicators
Indicates that timing has
been applied but there is
no move instruction.
If blank, default time is
used and there is no move
instruction
• + (see cue 6) . . . . . . . . .Indicates that there is discrete timing within the associated
cue. Found in the cue display “Timing” area.
• * (see cue 4) . . . . . . . . . .Indicates the cue has an allfade command. Found in the cue
display “Flags” area.
• A or a (see cues 3&4). . .Indicates an asserted cue. “A” indicates the entire cue is
asserted. “a” indicates a channel or parameter assert only.
Found in the cue display “Flags” area.
• B or b (see cue 5). . . . . .Indicates a blocked cue. “B” indicates the entire cue is
blocked. “b” indicates a channel/parameter block only. Found
in the cue display “Flags” area.
• F9 (see in cue 8) . . . . . .Indicates a follow time associated with the cue (in this case,
9 seconds). Found in the cue display.
3 System Basics 41

• H4 (see in cue 6) . . . . . .Indicates a hang time associated with the cue (in this case 4
seconds). Found in the cue display.
• I (see cue 9) . . . . . . . . . .Indicates an intensity blocked cue. Found in the cue display
“Flags” area.
• M or m . . . . . . . . . . . . . .Indicates a marked cue. “M” indicates an AutoMark or a
reference mark that is used by a subsequent cue. “m”
indicates a reference mark that is currently unused by any
subsequent cue (see Using Mark, page 175). Found in the
“Flags” area.
• P (see in cue 3) . . . . . . .Indicates the cue will preheat. Found in the cue display
“Flags” area.
• R (see in cue 8) . . . . . . .Indicates the source cue which refers back to an earlier mark
(see Referenced Marks, page 177).
42 Ion Operations Manual

Using [Format]
Some displays have multiple formats. When the display is first opened, it opens in its default view.
The default view for Live/Blind is table view, with all parameter categories displayed. When the
default format has been changed, those new settings will be used whenever the display is changed
back to that format.
Live and Blind share formatting. When you change from one format to another format, you are
always working with the same format until you change it. The exception to this is spreadsheet,
which is only available in blind. If you are working in blind spreadsheet, when you return to live you
will be working with the table or summary view, based on which one you were last using.
Summary View
The summary view displays the largest number of channels of any of the formats. Below you can
see channels 1-60 are shown. This format is best used to see large numbers of channels’ intensity
data and/or parameter category data. Individual parameters are not visible in this view.
FCB icons will appear at the bottom of the channel area for channels that have those parameters
patched to them.
When the summary view has been collapsed to show only intensity data, you may include focus,
color, or beam data in the summary view by holding down the [Data] key and pressing any encoder
paging key (located to the right of the LCD). This displays all categories.
Channel numbers
F, C, B data
Intensity data
3 System Basics 43

Table View
Table view is available in live or blind. Unlike summary view, table view displays the fixture type
associated with channels and details about each channel’s category or parameter levels.
In live, table view displays all active channel data being output from Ion. In blind, it will display all
data for a single record target (cue, preset, palette) depending on what is viewed. In table view,
focus, color, and beam information can be viewed in either a summary of these three categories.
To expand a category to show detail, press the [Data] or [Params] key and the associated
parameter key. For example, [Data] [Color] will change the color category from a summary view to
a detailed one. To collapse a category. press the [Data] or [Params] key and the associated
parameter key. You cannot hide a category from view.
When a category has been expanded, to hide or reveal only certain parameters, press and hold
[Data] and then select the parameter buttons of the appropriate parameters in the CIA. The
parameters will be displayed or suppressed depending on the current view.
Notice that when you hold down the [Data] button, the buttons of parameters that are currently
selected for viewing will be highlighted in the CIA.
In the table view, a slight space is provided between fixture types, giving a clear delineation
between them. The name of the fixture type is displayed at the top of the section for that fixture.
Channels with only intensity parameters will display the same as in summary view.
Expanded category Parameter data
Fixture types
Live Table View
Summarized category
Fixtures with only
type-specific
parameters displayed
44 Ion Operations Manual

Spreadsheet (Blind Only)
Spreadsheet format is available only in blind mode. It is useful for viewing channel data and trends
for multiple cues, submasters, palettes, or presets at one time. Cues and other record targets are
displayed on the vertical axis and channel data is visible on the horizontal axis.
Since this is a blind-only view, changes made in this view are immediate and do not require a record
or update.
As with table view, spreadsheet format allows you to choose exactly which parameters you want to
view. Parameters can be expanded/suppressed by holding [Data] and pressing the desired
parameter buttons in the CIA. Category data is not available in spreadsheet, but you may hide all
parameters of a specific category by holding [Data] and pressing the desired parameter category
button (also called “encoder paging keys”). By default, the spreadsheet view displays just intensity.
Cue numbers
Channel number
Parameters
3 System Basics 45

Encoders
The encoders are one of two ways to control the non-intensity parameters (NPs) of multipleparameter
devices. The four encoders are identified by the encoder LCD, just beneath the
encoders.
Encoder Navigation
Use the encoder page buttons (located to the upper right of the encoder LCD) to choose which
parameters are currently available on the encoders. There are six readily usable buttons: [Focus],
[Color], [Custom], [Form], [Image], and [Shutter]. Pressing any of these will change the
parameters controlled by the encoders.
Some fixtures have more parameters than can be displayed on one encoder page. The number of
pages for each category is displayed at the right side of the encoder screen. To view the other
pages, simply press the [Color], [Custom], [Shutter], [Image], or [Form] button to advance the
pages. The number of pages is indicated in the LCD.
Locking the Encoders
It is possible to lock out the encoders. To lock out the encoders, press [Clear] & [Encoder Page
Keys]. To unlock, press [Clear] & [Encoder Page Keys].
Using Softkeys
Some of the features and displays in Ion are accessible from the softkeys, which are located in the
bottom right area of the LCD.
Remember the use of the [Displays] button. This button offers softkeys that access the following
displays:
• Effect Status
• Color Picker
• Patch
• Setup
• Curves
• Browser
Each of these displays offers its own specific softkeys of relevance.
Context Sensitive Softkeys
Softkeys are context sensitive and will change depending on a number of factors including: the
active display, the current command line, the active record target and so on. Ion always repaints the
softkeys to coincide with your current action.
To get the full use of features on your Ion system, be sure to familiarize yourself with the softkeys
that become available as you program your show.
Changing Softkey Pages
When there are more relative softkeys than the six available softkey buttons, the LED in the [More
SK] button will light. Press [More SK] to view the additional softkeys.
46 Ion Operations Manual

Chapter 4
Managing Show Files
This chapter explains how to create, open, and save your show files. Each of these operations are
accomplished through the browser area in the CIA.
This chapter contains the following sections:
• Create a New Show File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
• Open an Existing Show File . . . . . . . . . . . . . . . . . . . . . . . . . .48
• Merging Show Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
• Printing a Show File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
• Saving the Current Show File . . . . . . . . . . . . . . . . . . . . . . . . .55
• Using Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
• Importing Show Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
• Exporting a Show File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
• Deleting a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
4 Managing Show Files 47

Create a New Show File
To create a new show file, navigate within the browser to: File> New> and press [Select].
You will be prompted for confirmation that you want to create a new show. Press {OK} to confirm or
{Cancel} to discontinue the operation. {Patch 1to1} will be selected by default. If you wish to not
have a 1 to 1 patch, deselect the {Patch 1to1} button and click {Ok}.
A new show created with {Patch 1to1} selected will have a 1 to 1 patch and 1 to 1 channel to sub
assignment.
Show File Names
Names of show files may appear in the browser list in normal text or in bold text. Files in normal
text indicate that there is only one show file stored by that name.
Bold show names indicate that there are several versions of the show file stored under that name,
the bold one being the most recent. To access the most recent show file, simply select the bold
name. You may right arrow [] from the bold name to expand a list of previous versions beneath it
in the browser. Select the desired show from the expanded list.
Open an Existing Show File
To open an existing Ion show file, navigate within the browser to: File> Open> and press [Select].
Ion provides you with multiple locations to retrieve an Ion show file (.esf) including:
• Show File Archive - This is the default storage location for show files when a show file is
created and saved. Folders are automatically created to store older versions of a show file.
This allows you the ability to open the latest version or an earlier version of a show file if
desired.
• File server - if one is connected. When there is no file server connected, it will not display in
the browser.
• USB (E:) device - When a USB device is connected and an Ion show file (.esf) is available on
the device, you will notice the USB is displayed in white text and is expandable. When the USB
device is connected and no Ion show file is loaded on the device, you will notice the USB (F:)
is displayed in a grey color and is not selectable.
Open the desired location:
• To open a show file from the Show File Archive, navigate within the browser to: File> Open>
Show File Archive and press [Select].
• To open a show file from the file server, navigate within the browser to: File > Open> File
Server> and press [Select].
• To open a show file from a USB device, navigate within the browser to: File> Open> USB (E:)
and press [Select].
48 Ion Operations Manual

Select the specific show file
• Navigate within the specified storage location and select the show file you wish to open, press
[Select].
• If the selected show has multiple time stamps, navigate to the desired revision and press
[Select].
This will open the partial show loading screen in the CIA.
From this screen you can select which components of the show file you wish to load. The buttons
at the center of the CIA represent all of the show components that you can choose to load. By
default all components are selected (gray) and will be loaded. To withhold any show components
from loading, simply deselect them in the CIA by clicking the respective button.
To reselect all show components, click the {Reset} button and all buttons will return to gray
(selected). To stop the show load process, click the {Cancel} button.
When you have selected or deselected all of the show components you require, click {OK}.
Ion loads the selected show to the console.
4 Managing Show Files 49

Selective Partial Show Opening
If you select the {Advanced} button in the partial show opening screen, you will have the
opportunity to load partial components from the show file and be able to specify the desired location
of those partial components in the new show file.
CAUTION:
On a partial show open, if any record targets are not opened, any existing data of
that type will be cleared from the console.To merge show data, merge should be
used. See “Merging Show Files” on page 52.
For example, you could specify only cues 5-10 from cue list 2 and load them as cues 20-25 in cue
list 7 in the new show. You could also specify only specific palettes, presets, effects, and so on. To
see the complete list of show components, press the {Advanced} key in the partial show loading
screen.
Selected Show Components
As you specify components, they are added to a table in the CIA. In the table, fields with a dark
background may be edited, fields with a light gray background do not apply to that component. For
each component in the list, you can specify the desired range by clicking in the proper area in the
table and entering numbers from the keypad. The columns in the table are:
• List - The list you are taking data from (such as a cue list).
• List Target - The list you are adding the data to.
• Start - The first in a range of components (such as a range of cues).
• End - The last in a range of components.
• Target - The desired location of the components in the new show file (for ranges, this
will be the location in the new show of the first component in the range, the others will
follow in order).
50 Ion Operations Manual

To open only partial components from a show file:
Step 1: From the browser, navigate to the desired show file (see Open the desired location:,
page 48).
Step 2: When the partial show load screen appears, click the {Advanced} button. The partial
components selection screen will appear in the CIA.
Step 3: Select the show components that you wish to load by clicking on their respective
buttons on the left side of the CIA. The components will appear in the list to the right
as you select them.
Step 4: Click any fields for which you want to enter specific numbers. The field (if editable) will
highlight in gold.
Step 5: Enter the numbers using the keypad to specify the desired cues/groups/effects and so
on.
Step 6: Click {OK} to load the components to the new show.
You may exit the partial show load screen at any time by clicking the {Cancel} button. This will
return you to the browser.
You may clear all selected components from the table at any time by clicking the {Reset} button.
You may exit the advanced loading screen at any time by clicking the {Advanced} button. This will
return you to the general partial show load screen.
4 Managing Show Files 51

Merging Show Files
Ion supports the merging of .esf show files.
Note:
Merging show files is different from opening show files. When you do a partial
open of show components, untouched record targets are cleared. When you do a
merge, those record targets remain.
You have the option of merging .esf show files from the Show File Archive, a File Server (if
connected), or a USB device.
To merge a show file, navigate within the Browser to: File> Merge>. Navigate to the desired
storage location and press [Select]. When using merge, Ion displays only the available files.
Navigate to the specific file and press [Select].
This will open the merge screen in the CIA. From this screen you can choose which aspects of the
show file you want to merge. By default all aspects are unselected (black). Selected show aspects
will appear in gray.
If you select the {Advanced} button in the merge show loading screen, you will have the
opportunity to load partial components from the show file and be able to specify the desired location
of those partial components in the current show file.
For example, you could specify only cues 5-10 from cue list 8 and load them as cues 20-25 in cue
list 7 in the new show. You could also specify only specific palettes, presets, effects, and so on. To
see the complete list of show components, press the {Advanced} key in the merge show loading
screen.
Selected Show Components
As you specify components, they are added to a table in the CIA. In the table, fields with a dark
background may be edited, fields with a light gray background do not apply to that component. For
each component in the list, you can specify the desired range by pressing the proper area in the
table and entering numbers from the keypad. The columns in the table are:
• List - The list you are taking data from (such as a cue list).
• List Target - The list you are adding the data to.
• Start - The first in a range of components (such as a range of cues).
• End - The last in a range of components.
• Target - The desired location of the components in the new show file (for ranges, this
will be the location in the new show of the first component in the range, the others will
follow in order).
52 Ion Operations Manual

To merge only partial components:
Step 1: From the browser, navigate to the desired show file (see Open the desired location:,
page 48).
Step 2: When the merge show load screen appears, press the {Advanced} button. The
partial components selection screen will appear in the CIA.
Step 3: Select the show components that you wish to merge by pressing on their respective
buttons on the left side of the CIA. The components will appear in the list to the right
as you select them.
Step 4: Press any fields for which you want to enter specific numbers. The field (if editable)
will highlight in gold.
Step 5: Enter the numbers using the keypad to specify the desired cues/groups/effects and so
on.
Step 6: Press {OK} to load the components to the current show.
Printing a Show File
Ion provides you with the ability to save a show file or aspects from a show file to a PDF file for
printing. Ion has three locations to save the PDF files including the Show File Archive, the File
Server (if connected), or a USB device (if connected). Saving the PDF file to a USB (F:) device,
allows you to then print the PDF from a personal computer. Printing directly from Ion is not
supported. To save a PDF of an Ion show file, navigate within the browser to: File> Print> and
press [Select].
This will open the printing screen in the CIA. From this screen you can choose which aspects of the
show file you want to save to PDF. By default all aspects are selected (gray) and will be saved. To
withhold any show aspects from printing, simply deselect them in the CIA by touching the
respective button. Deselected show aspects will appear in black.
4 Managing Show Files 53

To reselect all show aspects, press the {Reset} touchbutton and all buttons will return to gray
(selected). To stop the show file from being saved to a PDF and return to the browser, press the
{Cancel} button. When you have selected/deselected all of the show aspects you require, press
the {Ok} touchbutton to create the PDF file.
You can also choose to print specific portions of show aspects. To select this information, press the
{Advanced} button. The touchbuttons at the center of the CIA will again represent all of the show
aspects that you can choose. By default all aspects will be deselected (black).
Selected Show Component
As you select aspects, they will be added to the table in the CIA. For each component in the list, you
can specify the desired range by pressing the proper area in the table and entering numbers from
the keypad. The columns in the table are:
• List - The list you are taking data from (such as a cue list).
• Start - The first in a range of components (such as a range of cues).
• End - The last in a range of components.
To deselect all show aspects, press the {Reset} touchbutton and all buttons will return to black
(deselected).
To return to the main print screen, press the {Advanced} button. To stop the show file from being
saved to a PDF file and return to the browser, press the {Cancel} button. If you are ready to save
the file, press the {Ok} button. You will be prompted to name the file.
The PDF will have the show name, date and time it was created, and date and times for when the
show file was last saved. It also gives the Ion software version information. If multiple aspects were
selected to save to the file, there will be hyperlinks at the top of the PDF so you can quickly jump to
a section.
54 Ion Operations Manual

Saving the Current Show File
To save the current show data, navigate within the browser to: File> Save> and press [Select].
The Show File Archive is the default storage location for show files when they are saved. The new
time stamp located beneath the show file name on the CIA indicates that the show file has been
saved.
All previous saves are stored in the Show File Archive with the time stamp following the file name.
Using Quick Save
To save the current show data to the hard drive without having to navigate to the browser, hold
down [Update] and press [Select].
Using Save As
To save an existing Ion show file to a different location or with a different name, navigate within the
browser to: File> Save As> and press [Select].
Ion provides you with three locations to save an Ion show file (.esf) including the Show File Archive,
the File Server (if connected) or a USB device (if connected).
Navigate to the desired storage location and press [Select]. When using “Save As” to save the
show file to a specific location, the alphanumeric keypad will display on the CIA. Name the show file
and press [Enter]. The show file will be saved in the specified location with the show file name you
entered with a time stamp suffix.
By default, the current show file name will be used. Press [Clear] until this is removed. When
saving from an untitled show file, the default name will be “showfile”.
4 Managing Show Files 55

Importing Show Files
Ion supports the import of standard USITT ASCII, Light Wright, and .esf show files.
Note:
CAUTION:
You have the option of importing standard USITT ASCII (.asc) or Light Wright (.txt or .asc) from the
Show File Archive, a File Server (if connected), or a USB device.
To import a show file, navigate within the Browser to: File> Import> (Type of file to import) and
press [Select]. If you are importing an USITT ASCII file, you will have two options, Import as Library
Fixtures or Import As Custom Fixtures. Import as Library Fixtures will allow Ion to try to match the
fixtures in the file with fixtures in the Ion library. Import as Custom Fixtures will bring the fixtures in
as they are in the file. It is recommended to use Import as Custom Fixtures.
Navigate to the desired storage location and press [Select]. When using import, Ion displays only
the available files. Navigate to the specific file and press [Select].
Exporting a Show File
Ion supports ASCII show file import from a number of other control consoles,
including the Obsession, Expression and Emphasis product lines, as well as the
Strand 300 Series. Please note that all show files must be saved in an ASCII
format prior to importing them into Ion.
The way data is stored and used is often different between different consoles.
Imported data may not playback exactly the same between consoles.
Export your Ion show file to a a standard USITT ASCII, .csv, Focus Track, or Fast Focus Pro show
file using the export feature.
To export your Ion show file in ASCII format, navigate within the browser to: File> Export> and
press [Select]
You have the option of exporting your show file in ASCII format to the Show File Archive, to a File
Server (if connected), or to a USB device.
Navigate to the desired storage location and press [Select]. The alphanumeric keypad will display
on the CIA. Name the show file and press [Enter]. The file will be saved in the specified location
with the file name you entered with a “.asc” file extension.
You can export Ion show files as a .csv format by navigating within the browser to: File> Export>
CSV and select the location for the export, the Show File Archive, a File Server (if connected), or to
a USB device.
Files can also be exported as in a Focus Track or Fast Focus Pro format by going to File> Export>
Fast Focus Pro or Focus Track and select the location for the export, the Show File Archive, a File
Server (if connected), or to a USB device.
56 Ion Operations Manual

Deleting a File
Ion provides you with the ability to delete show files from the Show File Archive and the File Server
from within the browser.
To Delete a Show File
Navigate within the browser to: File> Open and press [Select]. Navigate to the desired show file
and press [Delete]. Press [Enter] to confirm or any other key to abort the deletion process.
File Manager
Ion has a file manager, which provides a way to manage show files. See “File Manager” on
page 303.
4 Managing Show Files 57

58 Ion Operations Manual

Chapter 5
Patch
The Patch is where patching data is stored and can be viewed using the patch display. Once a
channel is patched to an output, and the output is connected to a device (for example a dimmer,
moving light, or accessory), the channel will then control that device.
This chapter contains the following sections:
• Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
• Create and Edit Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
• Patching a Dimmer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
• Patching Moving Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
• Display Pages in Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
• Using the Scroller/Wheel Picker and Editor . . . . . . . . . . . . .74
• Calibrating a Scroller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
• Changing the Patch View . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
• Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
• Deleting Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
• Fixture Creator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
• Update Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
5 Patch 59

About Patch
Ion treats fixtures and channels as one and the same, meaning each fixture is assigned a single
control channel number. Individual parameters of that fixture, such as intensity, pan, tilt, zoom, or
iris are also associated with that same channel number but as additional lines of channel
information.
You are required to enter only the simplest data to patch a device and begin programming your
show, such as the channel number, the device type (if needed), and address. When you provide
more information in the patch, you will have more detailed control and improved function during
operation.
One or more devices may be patched to a single channel. For example you may want to patch a
group of dimmers to the same channel. In addition you may patch multiple devices to the same
channel for building a compound or accessorized fixtures. For example a Source Four ® with a color
scroller and a gobo changer may be patched to a single channel. This is referred to as a compound
channel.
Ion also allows you to create and edit the patch from the encoders and LCD. For details on this
method, see Patch Channels from the Encoder LCD, page 73.
When you open a new show file, Ion gives you the option of creating a 1-to-1 patch. This means that
the patch will automatically have channel 1 patched to output 1, channel 2 to output 2, and so on up
to the maximum channel count of your console.
Clearing the Patch
You can clear the patch entirely by accessing the clear functions from the browser. Select {Clear}
from the main browser menu. The clear functions window will open in the CIA.
To clear the patch, click {Clear Patch}. A confirmation is required before the patch will be cleared.
To exit the clear functions screen without clearing, press the [Displays] key at any time or select a
clear button and then select {Cancel} from the confirmation screen.
60 Ion Operations Manual

Displays
To begin patching your show, you must first open the patch display.
To open the patch display:
Step 1: Press the [Displays] button.
Step 2: Select the {Patch} softkey on the Ion LCD screen.
The patch display will open on the primary display and the CIA will display the patch controls.
Changing the Patch View
By default, patch is displayed in a sequential channel view. While in the channel patch view, any
numeric entry from the keypad is assumed to be a channel.
Channel View
Note:
It is recommended that you use the patch by channel display when working with
moving lights or other multi-parameter devices.
By default, the patch display lists channels on the X axis and device attributes on the Y axis. In this
view the channels are sorted numerically with the address in the second column. In the “patch by
channel” display, the command line entry defaults to selecting channels. To specify an address in
this mode, use the {Address} field shown in the CIA or press [At] after the channel entry.
5 Patch 61

Address View
You can change the patch display to sort by DMX address by pressing [Format]. The channel
number is now indicated in the second column and the command line changes its default entry to
“Address.” To specify a channel in this mode, use the {Channel} field shown in the CIA or press
[At] after the address entry.
While in address patch view, any numeric entry from the keypad is assumed to be an output
address.
As it is possible to patch by either output address or port/offset, pressing the [Data] key will toggle
the display to show the alternate output information.
62 Ion Operations Manual

Create and Edit Patch
Select Channel, Set Device Type, and Output Address
Each field identified in the patch display is also displayed in the CIA as a button. You can select the
fields using the page arrow keys (with “scroll lock” engaged) and edit them using the control keypad
or from the CIA buttons.
Selecting Channels
You may select channels for patching and editing using the keypad or direct selects.
Keypad
Channels may be selected in all of the same methods as defined in Selecting Channels, page 108.
When channels are selected, the patch display will show those channels and highlighted in gold.
After selecting the channel or group of channels, you may set each of the attributes beginning with
the device type, followed by the starting address. See “{Patch} Display and Settings” on page 68.
Note:
Status in the Patch Display
When patching conventional dimmers, it is not necessary to specify the device
type. “Dimmer” is assumed.
The first column in the patch display will advise you when a channel requires your attention.
• “!” is displayed next to a channel number to indicate there is a dimmer feedback error.
Helpful hints:
• [At] [Next] [Enter] - finds the next available address range large enough to accomodate the
selected device
• [At] [2] [/] [Next] [Enter] - finds the next available address range on universe 2.
• [At] [7] [7] [7] [Next] [Enter] - finds the next available address after 777.
• [At] [/] [9] [Enter] - patches address 9 on the same universe that was last used.
5 Patch 63

Patching a Dimmer
Tutorial
Note:
Step 1: To patch a dimmer you must first open the patch display. You may open the patch
display from the browser or by pressing [Displays]>{Patch}.
Step 2: Enter a channel number from the control keypad.
• When typing any number from the control keypad, and patch is in default
channel mode, channel is assumed and is placed on the command line.
Alternatively, when patch is in address mode, address is assumed and is placed
on the command line. Channel mode and address mode are toggled using the
[Format] key in the patch display.
• You can also use the [+], [-] and [Thru] keys to make your channel selection.
• [1] [Thru] [5] [0] [At] [1] [Enter] patches channels 1 through 50 to addresses 1
through 50 sequentially.
Step 3: Enter the DMX address or addresses.
• You may press [At] and enter the DMX address using the control keypad. The
DMX address may be entered in standard format ([1] [0] [2] [5] [Enter]) or by
using port and offset ([3] [/] [1] [Enter]).
• Multiple addresses may be patched to a channel in a single command. For
example, [1] [0] [At] [1] [0] [5] [+] [2] [0] [5] [+] [3] [0] [5] [Enter] would patch
channel 10 to address 105, 205, and 305. When more than one device is
patched to a channel, Ion automatically creates parts for each device. This is
used if you need to access an address directly in the patch-by-channel display.
Step 4: To select a device interface (optional), click {Interface}.
• This displays up to six buttons labeled {ACN}, {EDMX}, {ArtNet}, {Avab UDP},
{DMX}, and {Default}. Select an interface for the selected device. Once your
selection is made, the command line will populate with the selected interfaces
and terminate. If left blank, the {Default} is used as selected in the {Network}
section of the ECU. See “Protocols” on page 299.
Step 5: To label the channel press the [Label] key and enter the desired text on the
alphnumeric keyboard.
Step 6: Press {Attributes} to assign any of the following (see {Attribute} Display and
Settings, page 70):
• a proportional patch
• a curve
• a preheat setting
Step 7: Select the {Database} softkey to specify notes and keyword text related to the
selected channel for reference and future queries.
• Clicking the {Notes} or a {Text} fields opens the virtual PC keyboard on the
CIA. Pressing [Enter] returns the CIA to the database page.
If you create several addresses with multiple parts, you can select the same part for multiple
channels by selecting a channel range and using the {Part} key:
• [5] [Thru] [9] [Part] [2] [Enter] - selects only part 2 of channels 5-9.
64 Ion Operations Manual

Dimmer Doubling
You can patch channels in Ion to accomodate for dimmer doubling with Sensor+ dimmer racks. This
is done using the softkeys available in patch ({No Dim Dbl}, {A}, and {B}).
For Example:
Let’s assume you patch 96 channels of dimmers to addresses 1-96.
• [1] [Thru] [9] [6] [At] [1] [Enter]
Now you wish to dimmer double 1-12 of your Sensor+ rack and you want these to be
channels 97-108. To patch this, press:
• [9] [7] [Thru] [1] [0] [8] [At] [1] {B} [Enter]
Channels 97-108 are patched to address 1-12 B, while channels 1-12 are now patched to
address 1-12 A.
To remove the dimmer doubling from these addresses, you must first press [Format] to
enter Address mode and then press:
• [1] [Thru] [1] [2] {NoDimDbl} [Enter]
Addresses 1-12 have been returned to single dimmer modes and channels 97-108 are now
deleted.
By default, doubled dimmers start with an offset DMX address value of 20000. Therefore, in the
above example, address 1B (channel 97) is actually controlled by DMX address 20001. Address 2B
is actually controlled by DMX address 20002 and so on. This offset matches the default offset in
CEM+ when configuring your Sensor+ dimmer rack for dimmer doubling. To change the default
offset value, see Show Settings, page 95.
Moving and Copying Channels
Channels can be moved from one location to another within patch.
• [1] [Copy To] [Copy To] [7] [Enter]
The second press of the [Copy To] key changes the command into a “Move To”.
This syntax will move the patch information for channel 1 to the patch for channel 3. All data in the
show file that was stored at channel 1 is also move to channel 3.
To copy a channel to another location within patch:
• [1] [Copy To] [2] [Enter]
To copy a channel to another location within patch and all record targets in the show:
• [1] [Copy To] [2] {Entire Show} [Enter]
Unpatch a Channel
To unpatch a channel while in patch you can press:
• [n] [At] [0] [Enter]
Unpatched channels can still be manipulated and can have data stored for them, but they do not
output any information (as they are unpatched).
Replace
By default, if you patch an address to a channel that is already patched, Eos will create a new part
for the new address. If you want to replace the current address with the new, use {Replace}:
• [n] {Replace} [n] [Enter] - replaces the address in part 1 of the selected channel.
5 Patch 65

Patching Moving Lights
The process of patching moving lights requires more detail than patching a dimmer. Specific
information is required for more advanced control of the features offered by moving lights.
Tutorial
Note:
Note:
Step 1: To patch a moving light you must first open the patch display. You may open the patch
display from the browser or by pressing [Displays]>{Patch}.
Step 2: Enter a channel number or multiple numbers from the control keypad.
• When typing any number from the control keypad, and patch is in default
channel mode, channel is assumed and is placed on the command line. You
can use the [+], [-] and [Thru] keys to make your channel selection.
For example: [1] [0] [1] [Thru] [1] [1] [0]
Alternatively, when patch is in address mode, DMX address is assumed and is
placed on the command line. Channel mode and address mode are toggled using
the [Format] key in the patch display.
Step 3: Click the {Type} button in the CIA.
Step 4: Select a device type from the fixture library.
a: Press {Manfctr} from the CIA to display the fixture library. The two columns
on the left are pagable and show manufacturer names.
b: Use the arrow buttons to scroll the list of manufacturers. Selecting a
manufacturer repaints the device columns with all devices from that
manufacturer that are available for patching.
c: Scroll through the device list and make your selection. After the selection is
made, the fixture or device type will be placed on the command line after the
channel number and displayed in the box beneath the {Type} button.
Notice the two softkeys {Show Favorites} and {Manfctr} located beneath the
CIA.
These softkeys provide you with the option of showing only the library of fixtures/
devices that are already patched in the show and your favorites/ Eos default
devices, {Show Favorites} or all fixtures/devices available in the library sorted by
manufacturer {Manfctr}.
Step 5: Enter a starting address for the selected channel or group of channels.
• Press [At] and enter the address using the control keypad. The address may be
entered in standard format ([1] [0] [2] [5]) or by using port and offset ([3] [/] [1]).
66 Ion Operations Manual

Step 6: To select a device interface (optional), click {Interface}.
• This displays up to six buttons labeled {ACN}, {EDMX}, {ArtNet}, {Avab UDP},
{DMX}, and {Default}. Select an interface for the selected device. Once your
selection is made, the command line will populate with the selected interfaces
and terminate. If left blank, the {Default} is used as selected in the {Network}
section of the ECU.
Step 7: Select the {Attributes} softkey to set detailed moving light attributes.
• The following buttons may be available on this page: {Invert Pan} and {Invert
Tilt}, {Swap}, {Scroller}, {Gobo Wheel}, {Color Wheel}, {Preheat},
{Proportion}, and {Curve}.
• If your moving light includes parameters such as a color scroller or gobo
wheel and you have custom gels or non-standard patterns installed, use the
Scroller/Wheel Picker and the Editor to modify the device patched (See
Using the Scroller/Wheel Picker and Editor, page 74). The more specific your
patch data (including accurate colors and patterns) the more detailed
programming and operating will be.
Step 8: Select the {Database} softkey to specify notes and keyword text related to your
selected channel for reference and future queries.
• Clicking the {Notes} or {Text} button opens the virtual PC keyboard on the CIA.
Clicking [Enter] returns the CIA to the database page.
Patching a Compound Channel
A compound channel consists of any channel that controls more than one device. It can consist of
mutliple dimmers patched to the same channel or accessories patched to a channel (such as a
fixture with a color scroller, a fixture with a gobo wheel, and so on). By default, Ion will add a part if
you are trying to patch to a channel that has already been assigned an address.
To patch a compound channel in channel format:
• [9] [At] [5] [4] [0]
Assuming that channel 9 is already patched to an address, this will create a part 2 and
address it at output 540.
• [8] [Part] [2] [At] [5] [1] [3]
This will create a part 2 for channel 8 and address it at output 513. If you wish to patch by
address while in the channel view, press:
• {Address} [5] [1] [3] [At] [8] [Enter]
This will perform the same action as the previous example, assuming channel 8 was
previously patched to an address.
To patch a compound channel in address format:
• [5] [1] [3] [At] [8] [Enter]
This will perform the same action as the previous example, assuming channel 8 was
previously patched to an address.
CAUTION:
Note:
It is recommended that you do not patch more than one multiple-parameter device
(such as moving lights) to the same channel. Doing so can cause extreme
difficulty in controlling the devices.
If at any point you try to patch an address that is already in use, Ion will post an
advisory to indicate this, preventing you from duplicating addresses in your patch.
5 Patch 67

Display Pages in Patch
Softkeys available for use while in patch include {Patch}, {Attributes}, and {Database}. Pressing
any of these softkeys opens a paged view of the patch display and redraws the CIA to an expanded
view of fields related to the selected page.
When creating and editing your patch, page through each of these softkeys individually to enter
more specific data about your selected device.
{Patch} Display and Settings
When patch is opened, Ion defaults to this display. It provides access to data input fields that you
may use to define devices in your lighting system.
• {Channel} - In the patch display, all channels are displayed in numerical order. When multiple
devices are patched to the same channel, the channel number is only displayed in the first
row, additional devices are indicated with part extensions (example P2) on the next row of the
table.
• Select the channel number using the control keypad or the direct selects.
• {Type} - Ion defaults to patching dimmers. To specify a specific device type for the selected
channel, press the {Type} button from the CIA.
• The two columns on the left side of the CIA are pagable and show manufacturer names.
The four columns to the right of the manufacturer’s list are pagable devices that are
available from the selected manufacturer for patching.
• Selecting a specific manufacturer repaints the display with all devices that are
available from that manufacturer. After you select a device, the device type appears
in the command line, in the {Type} box in the CIA, and in the “Type” field for
that channel in the patch display.
• {Label} - An optional user-defined label. You can use the [Label] key to display the virtual PC
keyboard on the CIA. Pressing {Label} or [Label], after a label has already been assigned,
will display the label on the command line for editing purposes. Pressing [Label [Label] will
delete the text.
• [1] [At] [5] [Label] [Enter] - patches channel 1 to output 5 and labels
channel it “S4 house right”.
68 Ion Operations Manual

Note:
Note:
Note:
• {RDM Discovery} - If enabled, Ion will obtain RDM device information when available. The
default setting is “Disabled”. RDM must be enabled in the ECU before discovery is allowed.
See “Enable RDM” on page 301. When enabled, the console will automatically make
discovered RDM devices available for patching. The console will set everything required to
patch the device except the channel number. RDM discovery can be disabled at any time to
stop automatic RDM device additions and modifications.
Ion only supports RDM devices that are connected through an external ACN
gateway. Supported gateways are the ETC Net3 4 or 2 port Gateways.
{RDM Discovery} will default back to disabled on its own on console reboot.
• {Address} - A required entry field for any device. You may use the [At] key rather than the
{Address} button.
• Use the keypad to define the starting address for the device (from 1 to 32767) or a port
and offset value.
Press and hold the [Data] key to show the complimentary value. For example if
you have entered address value 514, the complimentary value would be port and
offset 2/2.
• You may enter a start address without defining an end address. Ion will draw this
information from the library data. If you wish to leave a larger output gap than required
by the library, use [Offset]. See Using {Offset} in Patch, page 72.
• If you specify a start address that conflicts with other channels already patched, the
conflicting channels will be unpatched after a confirmation from the user.
• {Interface} - An optional field used to specify what network interfaces should be used for the
output. When the field is left blank, the default data output is used as selected in the {Network}
section of the ECU. For more information about setting defaults, see Protocols, page 299. The
interface options available are Default, ACN, EDMX, ArtNet, Avab UDP, and DMX, depending
on what has been enabled in the {Network} section of the ECU for the console. If an output
option is not enabled, it will not appear in the {Interface} list.
• {Flash} - will bring a channel or address to full, and then every other second the level will
move to 15%. That will hold for 1 second, and then the level will return to full. The channel or
address will keep flashing until either the command line is cleared.
Below are some examples of patching from the {Patch} display:
Patching a generic dimmer:
[1] [At] [5] [Enter] - patches channel 1 to output 5.
[1] [Thru] [2] [4] [At] [1] [Enter] - patches channel 1-24 to outputs 1-24.
Patching a moving light:
[2] {Type} {ETC} {Revolution IM/SM Wybron} [At] [1] [1] [Enter] - patches an ETC
Revolution ® fixture to channel 2, with a starting output address of 11.
5 Patch 69

{Attribute} Display and Settings
The {Attributes} page provides you with optional fields for additional information and details about
the configuration of your system. Attribute settings include {Preheat}, {Proportion}, {Curve},
{Invert Pan}, {Invert Tilt} and {Swap}.
When the selected device includes a color scroller, a {Scroller} button will be displayed in the CIA,
when the selected device includes a color wheel or a gobo wheel, {Color Wheel} or {Gobo Wheel}
buttons will appear.
Click the desired attribute button and use the keypad to set the attribute value
• {Preheat} -This field allows you to specify an intensity value to preheat incandescent
filaments. When a preheat flag is applied to a cue, any channels that are fading from zero to
an active intensity and have been assigned a preheat value in patch will preheat in the
immediately preceding cue.
• [1] {Preheat} [0] [3] [Enter] - channel 1 is assigned a patched preheat value of 3%.
The preheat flag is applied to a cue as an attribute when the cue is recorded.
• {Proportion} - An attribute to set a modifier for the intensity of the device. If the patch limit is
set at 90% (for example), the actual output will always be 10% lower than the specified
intensity parameter, as impacted by the various playbacks or submasters. This value is set
numerically in a range of 0% to 200%.
• [1] {Attributes} {Proportion} [1] [2] [5] [Enter] -applies a 125% proportion to channel
1.
• [1] {Attributes} {Proportion} [Enter] - removes the applied proportion from channel 1.
• {Curve} - Used to assign a curve to an address in patch. In patch, curve is applied to intensity
parameters only.
From channel view:
• [1] {Curve} [4] [Enter] - applies curve 4 to the intensity parameter of channel 1.
• [2] [Part] [3] {Curve} [3] [Enter] - applies curve 3 to the intensity assigned to channel
2, part 3.
From address view:
• [3] {Curve} [3] [Enter] - assigns curve 3 to address 3.
• [3] [/] [2] {Curve} [4] [Enter] - assigned curve 4 to universe 3, address 2.
• {Invert} - A moving light attribute used to invert the output of pan, tilt, or both. Select either the
{Invert Tilt} or the {Invert Pan} button on the CIA.
• [2] {Attributes} {Invert Pan} - inverts the output of the pan parameter.
70 Ion Operations Manual

• {Swap} - A moving light attribute used to exchange pan and tilt levels. Select the {Swap}
button on the CIA.
• [2] {Attributes} {Swap} - swaps the pan and tilt parameters for channel 2.
• {Scroller} - An attribute used to change the scroll loaded in a scroller or moving light. Select
the {Scroller} button on the CIA to display the scroller picker and the scrolls available for your
device. See “Using the Picker” on page 74.
• [2] {Attributes} {Scroller} - opens the Scroller Picker in the CIA for scroll selection for
channel 2.
• {Gobo Wheel} - An attribute used to change the gobo wheel loaded in a moving light. Select
the {Gobo Wheel} button on the CIA to display the wheel picker with gobo options available
for your device. See “Using the Picker” on page 74.
• [3] {Attributes} {Gobo Wheel} - selects channel 3 and opens the Wheel Picker in the
CIA for gobo wheel selection.
• {Color Wheel} - An attribute used to change the color wheel loaded in a moving light. Select
the {Color Wheel} button on the CIA to display the wheel picker with the options available for
your device. See “Using the Picker” on page 74. “More” as shown in the patch display,
indicates additional parameter properties are available for the selected device, such as the
color and gobo wheels.
• [4] {Attributes} {Color Wheel} - selects channel 4 and opens the wheel picker in the
CIA for color wheel selection.
5 Patch 71

{Database} Display and Settings
The {Database} page provides you with additional fields for entering information. These fields
include {Notes} and {Text 1} through {Text 4}. Clicking on {Text 1} through {Text 4} will open up a
display for selection of keywords. It will display keywords that were already created as well as
showing an option for creating new keywords. Clicking on {New Keyword} will display an
alphanumeric keyboard for entering in a new keyword.
• {Text} - Text fields are used to provide up to four keywords (see Keywords, page 80) about
any channel or group of channels. These fields can be anything that you think is important
about a channel, such as its location (FOH), an attribute of it (wash, spot) or other
characteristics of the channel (such as gel R80). You may use the virtual PC keyboard in the
CIA, or an external keyboard, to provide up to 30 characters of key words about the device.
• [5] {Database} {Text 1} < FOH right> [Enter] - adds text to channel 5.
• {Notes} - Provides you the ability to attach a text note to a channel or group of channels.
Select the {Notes} button on the CIA to display the virtual PC keyboard. You may type a label
or any length of note regarding your channel in this space.
• [5] {Database} {Notes} [Enter] - adds a note to channel 5.
Using {Offset} in Patch
Using the {Offset} feature in patch allows you to force a numerical offset between the starting
address of channels in patch or for offsetting your channel selection. This feature is useful when
you have configurable devices in your show such as a Source Four Revolution which has option
slots for additional addresses (scrollers, indexing pattern wheels, and so on), or when you want to
start your addresses at some known multipler.
• [1] [Thru] [5] {Type} {Source Four Revolution} [At] [1] {Offset} [3] [1] [Enter] - fixtures will
be patched with a patch address offset of 31 channels, allowing you to have additional space
within the patch for a given fixture type regardless of configuration or personality.
• [1] [Thru] [2] [0] {Offset} [2] {Type} {VL1000} [At] [1] {Offset} [2] [0] [Enter]- selects every
other channel in the list and patches them with an offset of 20 addresses.
72 Ion Operations Manual

Patch Channels from the Encoder LCD
Command
Line
You may use the encoders and LCD to patch channels in Ion. This is an alternative to using the
methods described above. The end result will be the same, this simply gives you the ability to patch
without requiring the use of the mouse or external touchscreen.
To patch channels from the encoders and LCD:
Step 1: Press [Displays]>{Patch}. The LCD will change to display the patch interface.
Note:
Encoder ID Fields
Softkeys
Step 2: Select the channel you wish to patch.
• [9] [7] [Enter]
Step 3: Using the encoders directly above “Manufacturer”, select the manufacturer of the
fixture you want to patch. Once the manufacturer is selected, the fixtures available
from that manufacturer automatically load to the “Type” encoder.
.
If you wish to patch a standard dimmer, select “Generic” from the manufacturer list
and “Dimmer” from the fixture list. Or you can simply press the [At] key (as in
Patching a Dimmer, page 64) and dimmer is assumed.
Step 4: Select the desired fixture type from those available from the manufacturer using the
encoder above the “Type” field. When the desired type is displayed, press the “Type”
encoder to select the displayed fixture type.
Step 5: Change the DMX universe, if needed, using the encoder above the “Universe” field.
Step 6: Set the address to the desired number using the encoder above the “Address” field.
Address number is shown as 1-512 with the network address displayed in
parentheses. When the proper address is shown, press the encoder to select the
address. Your fixture is now patched.
5 Patch 73

Using the Scroller/Wheel Picker and Editor
The scroller and wheel picker allows you to choose a specific scroll, color wheel, or gobo wheel
from standard manufacturers and associate them with fixtures. You may also create customized
scrolls or wheels using the editor to match custom devices installed in your fixture.
Using the Picker
Default color and pattern media for the selected fixture, as determined in the fixture library, is
displayed in the {Attributes} page. Only the media attribute that is available for the selected fixture
will display.
In the sample image below, the selected channel (1) is a Source Four Revolution with a color
scroller. If the selected channel included a color wheel and two gobo wheels, each device would be
represented in the display with a button.
Select the desired attribute to open the picker.
The picker displays on the left half of the CIA when you select the specific attribute ({Scroller},
{Color Wheel} or {Gobo Wheel}). The picker displayed is specific to the selected attribute (the
scroll picker will display when {Scroller} is clicked, the color wheel picker will display when {Color
Wheel} is clicked, and so on).
Select the scroll or wheel type.
74 Ion Operations Manual

The picker displays buttons for the standard scroll or wheel type of the selected channel. The
default selection is the wheel as shipped from the manufacturer (derived from the fixture library).
Displayed to the left of the standard scroll or wheel selection is a list of each color or gobo as they
are installed in the selected device (frame by frame). When the color or pattern image is available,
it will display next to the frame name.
In the above image, {ETC Scroll} is the default scroll for the selected ETC Source Four Revolution.
The list of gel colors as they are installed in the scroll are displayed to the left with a color chip for
easy reference. Selecting any other type, such as {Martin Scroll}, redraws the frame list to match.
The softkeys displayed beneath the picker are {Clear}, {New}, {Copy}, {Edit}, and {Delete}.
• {Clear} - clears the selection type from the selected channel in the picker.
• {New} - creates a new scroll or wheel and provides additional softkeys to enable the Editor.
See Using the Editor below.
• {Copy} - makes a copy of the currently selected scroll or wheel type, which can then be edited
using the editor. See Using the Editor below.
• {Edit} - used to edit an existing scroll or wheel.
• {Delete} - used to remove the selected frame only from a scroll or wheel that you have
created.
Using the Editor
The editor is used to create new or edit copied scrolls and wheels. While in the picker display, you
can create a new scroll or wheel by pressing the {New} softkey or make a copy of an existing scroll
or wheel by selecting the source, then pressing the {Copy} softkey.
The editor does not limit how many frames you can add to the scroll or wheel for the selected
fixtures. Keep in mind that any fixture has its own limitations. For example, a Source Four
Revolution color scroller is limited to 24 frames. If you have created a custom color scroll with 30
frames, the Source Four Revolution will only provide you access to the first 24 frames that you
created. This applies to wheels as well.
When using the editor, the following softkeys are available for use:
• {Insert} - inserts a new frame above the selected frame.
• {Delete} - removes the selected frame.
• {Edit} - changes the selected frame.
• {Done} - completes the editing process.
• {Label} - displays the virtual PC keyboard on the CIA for labeling the new scroll or wheel.
5 Patch 75

Creating a new scroll or wheel
When you create a new scroll or wheel, {New Wheel x} appears in the wheel list as the selected
button. The frame list will be empty with only “New” displayed in frame 1.
You can label the new wheel by pressing the {Label} softkey and typing the desired label on the
virtual PC keyboard and pressing {Enter}.
To select a color or pattern for the specific frame in the scroll or wheel, select the “NEW” text. The
available gel, color, gobo and effect media selections will be displayed.
Manufacturer
list
When a manufacturer is selected from the list, the catalog selection changes to display only the
selected manufacturer’s offerings. When a specific catalog is selected, the media will display in the
last three columns of the editor.
When you make a media selection, the display returns to the new wheel frame list where additional
frames can be added to the scroll or wheel (using the {New} frame button) or you can click in the
next frame area to add more frames.
Note:
Manufacturer
catalog
Cataloged media
(sorted numerically)
The media selection includes the following softkeys:
• {Gel}, {Color}, {Gobo}, and {Effect} - each will
display available media selections as they are
cataloged by the associated scroll or wheel
manufacturers.
• {Open} - places the frame in Open White. Generally,
the first media frame is open.
• {Cancel} - cancels the media selection and returns to
the frame editor.
An {Invert} softkey will display when creating or copying a wheel or scroller.
{Invert} is used to reverse the order of frames.
76 Ion Operations Manual

Editing a copy of a scroll or wheel
If a copy has been made of an existing scroll or wheel, the copied scroll or wheel will display as
{New Wheel x} before the standard manufacturer offerings. The frame list will include an exact
duplicate of the copied selection.
To make a change to a frame you must first select the frame then press {Edit} to display the media
selection. Or you can insert a new frame above a selected frame using the {Insert} softkey.
For example, to insert a new frame in between existing frames 2 and 3, select frame 3 and press
the {Insert} key. The media selection will display.
Manufacturer
List
Manufacturer
catalog
cataloged media
(sorted numerically)
The media selection includes the following softkeys:
• {Gel}, {Color}, {Gobo}, and {Effect} - each will
display available media selections as they are
cataloged by the associated scroll or wheel
manufacturers.
• {Open} - places the frame in Open White.
• {Cancel} - cancels the media selection and returns to
the frame editor.
When a manufacturer is selected from the list, the catalog selection changes to display only the
selected manufacturer’s offerings. When a specific catalog is selected, the media will display in the
last three columns of the editor.
When you make a media selection, the display returns to the new wheel frame list where additional
frames can be edited in the scroll or wheel.
5 Patch 77

Calibrating a Scroller
You can calibrate the center point of any frame in a scroller using the calibrate feature. This will
ensure that color scroll frames will be centered over the aperture of the fixture when you advance
a color scroll frame-by-frame. You can do this using the virtual encoders or the encoder LCD.
Calibrating a scroller is normally done from the live display.
Note:
It is recommended that you calibrate your scroller frames starting with the last
frame and working backward to the first frame. This will help ensure a complete
and accurate calibration.
Calibration may need to be performed when you initially patch a scroller and may
need to be adjusted through the course of operation as spring tension changes in
a color scroller
To calibrate a scroller from the virtual encoders:
Step 1: In the browser, navigate to Virtual Controls>Encoder. A new window will open in
the CIA.
Step 2: Select {Open as Primary Display} in the CIA. Virtual encoders will open on the
display screen.
Step 3: Select the channel of the scroller you wish to calibrate.
Step 4: Press the [Color] encoder button to the upper right of the LCD. Multiple presses may
be required before the scroller encoder is visible in the virtual encoder display.
Step 5: Use the encoder to move all the way to the last frame of the scroller.
Step 6: Watch the scroller and continue adjusting the frame until it is centered in the desired
position.
Step 7: Click {Calibrate} in the virtual encoder display. The new center position is now stored
for the selected channel.
Step 8: Click {Last} in the virtual encoder display to move to the center point of the previous
frame.
Step 9: Visually verify if the center point of the new frame is accurate. If it is, press {Last} again
to move to the previous frame in the scroll. If not, follow the calibration procedure
again.
Step 10: Repeat steps 6-9 until you have calibrated all of the frames.
Step 11: Press [Live] or [Blind] to close the virtual encoder display.
You can also calibrate from the encoder LCD. This eliminates the need for the virtual encoder
display.
78 Ion Operations Manual

To calibrate from the LCD:
Step 1: Select the channel of the scroller you wish to calibrate.
Step 2: Press the [Color] encoder button to the upper right of the LCD. Multiple presses may
be required before the scroller encoder is visible in the virtual encoder display.
Step 3: Use the encoder to move all the way to the last frame of the scroller.
Step 4: Watch the scroller and continue adjusting the frame until it is centered in the desired
position.
Step 5: Press and hold the scroller encoder. {Calibrate} becomes visible as a softkey in the
encoder LCD.
Step 6: Press {Calibrate}. The new center position is now stored for the selected channel.
Step 7: Continue holding the encoder and press {Last} to move to the center point of the
previous frame.
Step 8: Visually verify if the center point of the new frame is accurate. If it is, press {Last}
again to move to the previous frame in the scroll. If not, follow the calibration
procedure again.
Step 9: Repeat steps 6-9 until you have calibrated all of the frames.
5 Patch 79

Keywords
Query is a feature available in Eos, but not in Ion. Since show files are compatable between the two
consoles, in Ion you can assign keywords to channels that can be queried when the show file is
loaded onto an Eos.
If you plan on being able to query channels in Eos based on a keyword association, the keyword
must be defined in patch.
To enter a keyword for a channel:
Step 1: Press [Displays], to the right of the LCD.
Step 2: Press the {Patch} softkey.
Step 3: Press {Database}.
Step 4: Select a channel or range of channels in the command line.
Step 5: Click one of the {Text (1-4)} buttons in the CIA to specify which keyword you are
entering. A list of previously defined keywords will be posted. Select from these or
press {New Keyword}. A virtual alphanumeric keyboard will appear.
Step 6: Type the keyword or words you wish to use. You may use either the virtual or external
keyboard.
Step 7: When finished, press [Enter].
Once keywords have been created, they will appear in the keyword section of the CIA when a query
is performed in Eos.
Deleting Channels
It is possible to delete channels in patch. Deleting channels is different from unpatching in that
deleted channels cannot be manipulated or have parameter data stored for them. When deleted,
the channel numbers will still be visible in the live/blind display, but the channel outline, containing
the parameters and level information, will be removed from the display.
For Example:
To delete channels in the patch display, press:
• [6] [Thru] [1] [0] [Delete] [Enter] [Enter]
In the live blind display, the channel numbers will still be visible but the channel outlines and
parameter data will be hidden from view.
80 Ion Operations Manual

Fixture Creator
Ion provides you with the ability to create your own fixture type within patch and store it with your
show file. You can name the fixture, assign all necessary parameters, define the address and
operational range of those parameters, and set lamp controls.
The fixture creator is accessible from patch. Once a fixture has been created, it is stored in the
show file. It is not added to the fixture library.
To open the fixture creator:
Step 1: Press [Displays]>{Patch} to open the patch display. Or you may open it from the
browser.
Step 2: Select any channel (it need not be the channel for the fixture you are creating, but it
can be) from the keypad.
Step 3: Click {Type} in the CIA patch display. The left side softkeys will change to offer fixture
type options.
Step 4: Click {User}. This will display buttons for all currently patched fixtures in the CIA.
Step 5: Click {Edit}. This will open a list displaying those same fixtures that are currently
patched. This is the fixture creator.
5 Patch 81

Creating a New Fixture
New fixtures are created from the fixture creator list in the CIA (see above).
To create a new fixture, click {New}. A new fixture will be added to the bottom of the fixture list.
Name New Fixture
Once the new fixture appears in the list, it is recommended that you name the fixture you are about
to create.
To name a fixture in the creator list:
Step 1: Press [Page ] to arrow down to the new fixture.
Step 2: Click {Type}. The virtual PC keyboard will open in the CIA.
Step 3: Enter the desired name for the new fixture on the virtual (or attached alphanumeric)
keyboard.
Step 4: Press [Enter]. The name will appear in the “Type” column for the new fixture.
Add parameters
After naming the fixture, you can specify which parameters the new fixture contains.
82 Ion Operations Manual

To add parameters to a new fixture:
Step 1: Use the [Page] keys to select the new fixture from the fixture list.
Step 2: Click {Edit}. That fixture will open in a new display in the CIA.
Note:
Step 3: Determine the total number of parameters that your fixture has. Do not count 16-bit
channels as two channels, this will be done in a later step.
Step 4: Click {New} to add parameter slots. Repeat this step until you have as many slots as
are required by the number determined in step 1.
When {New} is clicked, the parameter slot will appear in the list with a default
name in the “Parameter” column. You may disregard these default parameters as
you will redefine the designations in a later step.
Step 5: Use the [Page] keys to navigate to any parameter slots that you wish to alter the
default parameter designations for.
Step 6: When you have selected a slot, click {Parameters}. The CIA will display buttons
representing all of the available parameters.
a: Click the {>>} and {

Step 7: Click the button for the desired parameter in the CIA.
Step 8: Repeat steps 3-5 until you have entered all of the required parameters for the new
fixture.
If you are missing a parameter slot: At any point you can use the [Page] keys and
{Insert}, to insert a parameter slot above the selected one.
If you want to remove a parameter: you can use the [Page] keys and {Delete}, to remove
a parameter from the list.
Define parameter channels
Once you have added and specified all of the parameters for the new fixture, you can now define
the address requirements, size, and ranges for each of them.
To define the size (8-bit or 16-bit) of any parameter:
Step 1: Use the [Page] keys to navigate to any parameter that you wish to alter the size of.
The system defaults to 8-bit for any new parameter.
Step 2: When selected, click {Size}. This will toggle the parameter from 8-bit to 16-bit. If 16bit
is selected, the system automatically applies a value in the “LDMX” column. This
value can be altered (see below).
To define the DMX address of any parameter:
You can alter the default DMX address assigned to any parameter in the list. This is not the actual
address that will be used when patched, but rather it is the order of address for the parameter
relative to the other parameters in the fixture.
Step 1: Use the [Page] keys to navigate to the “DMX” column of the desired parameter.
Step 2: Enter the desired address using the keypad.
CAUTION:
Be careful not to duplicate any address in the DMX order of parameters in the new
fixture. Ion does not prevent you from duplicating addresses.
To define the LDMX address of any 16-bit channel:
LDMX or “low-DMX” is the DMX address for the second half of any 16-bit channel. If used in
Coarse/Fine determination. The DMX channel defines the “Coarse” adjustment and the LDMX
defines the “Fine” adjustment.
Step 1: Use the [Page] keys to navigate to the “LDMX” column of the desired parameter.
Step 2: Enter the desired address using the keypad
84 Ion Operations Manual

To alter the Home settings for any parameter:
You can define the value for any parameter’s “home” value.
Step 1: Use the [Page] keys to navigate to the “Home” column of the desired parameter.
Step 2: Enter the desired home value (0-255) using the keypad.
Range editing a parameter
You can enter the operational ranges for specific slots within any specific parameter (such as color
scroller, color wheel, gobo wheel, and so on).
For example, if the parameter were “Gobo Wheel”, and the fixture included a four-slot gobo wheel,
you can use ranges to determine the minimum or maximum values for each of those slots. You can
also label the slots and define the minimum or maximum values that will appear in the channel
display for that parameter.
To define the range values for any parameter:
Step 1: Use the [Page] keys to navigate to the parameter that you want to add ranges to.
Step 2: Click {Ranges}. The range list will open.
Step 3: Determine the total number of slots required by the parameter. Be sure to include
“open” slots when needed.
Step 4: Click {New} to add ranges. Repeat this step until you have as many slots as are
required by the number determined in step 3.
Step 5: Use the [Page] keys to select the range and field you wish to edit. Fields are:
• Min - enter the minimum value (0-255) for the range slot you are defining.
• Max - enter the maximum value (0-255) for the range slot.
• User Min - enter the value that will be displayed to users (for example, what will be
displayed in the live summary view) when the slot is at its minimum value. Value
can range from -9999 to 65535.
• User Max - enter the value that will be displayed to users when the slot is at its
maximum value. Value can range from -9999 to 65535.
Step 6: Click {Label} to add a label to any range slots. These will appear in the encoder LCD
when the related parameter is displayed for the new fixture.
Step 7: Click {Done} when you have finished editing the ranges.
Copying a Fixture
It is possible to copy an existing fixture and then edit its parameters. In the fixture editor, there is a
{Copy} button. Pressing {Copy} when a library fixture is selected will create a copy of that fixture
and will assign it a new name. This new fixture can then be edited.
Importing a Custom Fixture
You can import custom fixtures from an ASCII show file, see Importing Show Files, page 56.
Update Library
When a new library is installed on Ion (for example, included in a software update), changes in
library data will not automatically update your show files. This is to prevent library changes from
affecting a functional show file.
In the event that you wish to update the show’s fixture data to match a new library, you may enter
the fixture creator (see Fixture Creator, page 81) and click {Update Lib}. You will need to confirm
this choice by clicking {Ok} to update or {Cancel} to return to the previous screen. This will update
the show file fixture data with any relevant changes from the new fixture library.
5 Patch 85

86 Ion Operations Manual

Chapter 6
Using Groups
Groups are channel selection devices used for fast recall of specific channels. A maximum of 1000
groups can be recorded. Once recorded, they are accessible from the keypad, direct selects, and
through the displays.
This chapter contains the following sections:
• Recording Groups Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
• Selecting and Recalling Groups. . . . . . . . . . . . . . . . . . . . . . .89
• Group List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
6 Using Groups 87

Recording Groups Live
Record groups of channels that you want to have available for fast recall later. Groups can be
stored as whole numbers (such as Group 5) or as decimals of tenths or hundredths (such as Group
2.5 or Group 7.65). Only whole number groups can be stored using the direct selects, any decimal
designations for groups must be stored using the keypad.
All groups may be labeled. These labels are then displayed on the direct selects as well as in the
group list. Group numbers will not display in either until the groups have been created.
The following syntax examples illustrate the various methods and features available when
recording groups:
• [1] [thru] [5] [Record] [Group] [7] [Enter] - records only channels 1 - 5 to group 7.
• [Record] [Group] [7] [Enter] - records all channels with non-default values to group 7.
• [5] [Thru] [9] [Record} {Group 7} - records channels 5-9 to group 7 using the direct selects.
• [3] [Thru] [8] [Record] [Group] [8] [.] [5] [2] [Enter] - records channels 3-8 to group 8.52.
• [-] [3] [Record] [Group] [7] [Enter] - records all channels, except channel “3,” to group 7.
• [Record] [Group] [7] [Label] [name] [Enter] - records as above and adds a label to the
group.
• [Record Only] [Group] [7] [Enter] - records channels with manual data to group 7.
• [Record Only] {Group 7} - records channels with manual data to group 7 using the direct
select.
Ordered Channels
When recording groups, channels are ordered in the group based on their selection order when the
group is stored. This ordering is useful combined with [Next] and [Last] functions and when
applying effects to groups.
For Example:
If you record a group by selecting channels in the following order:
• [1] [+] [3] [+] [5] [Thru] [9] [Record] [Group] [1] [Enter]
and later you select Group 1 and press [Next], the channels will be accessed, one at a time,
in the same order in which they were initially selected.
If new channels are added to an ordered group using an update command, those channels are
added to the end of the channel list from an ordering perspective.
When a group is previewed using the group list, the display defaults to showing the ordered view.
Channels can be reordered as needed from this list. Use the [Format] key to change to a numeric
listing of channels. For another example:
• [1] [0] [Thru] [2] [Record] [Group] [1] [Enter
This will record channels 10 through 2 to Group 1, and then if you select the group you can
cycle through the channels using [Next] starting with 10, then 9, then 8, and so on.
88 Ion Operations Manual

Offset
You can use the {Offset} softkey to aid in channel selection prior to storing groups. The offset
options are {Odd}, {Even}, {Reverse}, and {Random}. For example:
• [1] [Thru] [9] {Offset} {Odd} [Record] [Group] [5] - records all odd numbered channels
between 1 and 9 to Group 5.
• [1] [Thru] [2] [0] {Offset} {Reverse} [Record] {Group 3} - records channels 1-20, in reverse
order, to Group 3 using the direct selects.
Editing and Updating Groups in Live
Existing groups can be updated or rerecorded in Live. If you rerecord an existing group, a
confirmation is required (unless disabled in “Setup”). By rerecording a group, you replace the
contents of the group, you do not add to it. Updating a group does not require a confirmation and
adds channels to the group, rather than replacing them.
Other editing or updating examples are:
• [Group] [x] [Label] [Label] [Enter] - clears the label.
• [Group] [x] [Label] [name] [Enter] - stores a new label.
• [1] [Thru] [5] [Update] [Group] [n] [Enter] - adds channel 1-5 to existing Group n.
• For record examples, please see Recording Groups Live, page 88.
Selecting and Recalling Groups
Groups may be recalled from the control keypad or the direct selects.
To select a group:
• [Group] [1] [Enter] - selects all channels in Group 1
• [Group] [1] [at] [5] [Enter] - selects Group 1 and places all channels within at 50%
• {Group 1} - Selects all channels in Group 1
If [Next] is used after a group selection, it accesses the first ordered channel in that group. Pressing
it again accesses the second ordered channel in that group, and so on. [Next] - used after the last
channel in the group - accesses the first channel in the group again.
[Last] may be used with group selects similar to [Next]. Press [Select Last] to reselect the entire
group.
Deleting Groups
When you delete a group, the group number and all contents from the Group List Index and direct
selects are deleted. Delete commands require a confirmation by default. This can be altered in the
default settings. If you disable confirmations, the second enter is not required in the following
examples:
Group deletion features include:
• [Delete] [Group] [5] [Enter] [Enter] - deletes group 5.
• [Delete] [Group] [3] [+] [Group] [5] [Enter] [Enter] - deletes groups 3 and 5.
• [Delete] [Group] [3] [Thru] [9] [Enter] [Enter] - deletes groups 3 through 9.
• [2] [Delete] [Group] [7] [Enter] - deletes channel 2 from group 7.
6 Using Groups 89

Group List
The group list allows viewing and editing of groups.
Open the Group List
To open the group list you can:
• Press [Group] [Group]
• Press [Blind] & [Group]
• In the browser, select “Group List” from the Record Target Lists
You can navigate within the group list using [Next] and [Last] or by selecting the group you want to
work with.
Ordered View and Numeric View
By default, grouped channels will be displayed in ordered view. Therefore, grouped channels will
appear in the order they were added to the group (see Ordered Channels above). If you wish to
view the channels in numeric view, press the [Format] key and the view will be switched (channels
will appear in numeric order from lowest to highest).
This setting is important in defining next and last functionality within groups in live/blind. If left in
numeric format, when using [Next] or [Last] group selection channels will be selected in numeric
order. If left in ordered view, they will be selected based on their order of being stored to the group.
Editing Groups from the Group List
An existing group can be modified without the need for recording or updating, as follows:
• Select the required group by pressing [Group] [n] [Enter], or using [Next] and [Last] to
navigate through the list.
The selected group is highlighted in gold and above the CIA command line, “BLIND: Group x” is
displayed.
The following actions are now possible:
• [Label] [name] [Enter] - adds or modifies a group label.
• [Copy To] [Group] [7] [Enter] - copies the contents of the selected group to group 7.
• [2] {Insert Before} [9] [Enter] - inserts channel 2 into the group, placing it before channel 9
in the ordered view.
• [2] {Insert After} [5] [Enter] - inserts channel 2 into the group, placing it after channel 5 in the
ordered view.
• [2] [Delete] [Enter] - removes channel 2 from, the group.
• {Random} [Enter] - rearranges the channels in the group randomly.
• {Reverse} [Enter] - reverses the order of the channels within the group.
90 Ion Operations Manual

Using Groups as a Channel Collector
[Group] can be used as a quick way to collect channels from submasters, cues, palettes, or
presets.
The following actions are possible:
• [Group] [Cue] [1] - selects all the channels in cue 1.
• [Group] [Sub] [3] - selects all the channels in submaster 3.
• [Group] [Int Palette] [5] - selects all the channels in intensity palette 5.
6 Using Groups 91

92 Ion Operations Manual

Chapter 7
Setup
This chapter describes the processes involved in changing your system settings to meet your
preferences. It also covers advanced setup functions.
This chapter contains the following sections:
• Opening Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
• Show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
• Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
• Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
7 Setup 93

Opening Setup
To enter the setup screen, press [Displays]>{Setup}.
The CIA will repaint to display the setup screen and the softkeys will change to display the various
subcategories of setup. Ion defaults to display show settings, however if you have changed the
view to another subcategory, Ion will remember the view you were in when you return to setup.
The setup subcategory softkeys are:
• Show
• Desk
• Security
Show
When you select the {Show} softkey, the CIA repaints to display the following screen:
The buttons on the left are the setting categories within show setup. The show setup categories are:
• Show Settings
• Cue Settings
• Fader Configuration
• Filter Setup
• Encoder Configuration
• Show Control
• Partitions
94 Ion Operations Manual

Show Settings
Click {Show Settings} to enter this category.
Five fields will be available to you: {Num of Channels}, {Auto-Mark}, {Dim. Dbl. Offset},
{Partitioned Control}, and {Home Preset}. To change the setting for any of these fields, click the
field in the CIA to activate it. If the field requires data, enter it from the keypad. If the field is a toggle
state, one click of the button will switch the field to its other state.
Changes from this screen are systemwide and will impact all Ion consoles and clients connected to
the system.
{Num of Channels}
You may use this field to set the number of channels in your Ion to the number of channels in your
system. Ion supports a maximum of 10,000 channels. Enter the number of channels for your
system using the keypad. This entry must be confirmed with the [Enter] key.
{Auto-Mark}
This toggles the AutoMark settings between enabled and disabled (see Using Mark, page 175 for
more information). AutoMark is disabled by default.
{Dimmer Double Offset}
This allows you to set the address offset for dimmer doubling. The default for this is 20000, to match
the Net2 standard offset, including Sensor+ software.
{Partitioned Control}
Enables or disables the assigning of partitions. Default is “Disabled” (see Using Partitioned Control,
page 289 for more information).
{Home Preset}
Allows you to specify a preset that will be used as the home level for all non-intensity parameters
stored in the preset, instead of the fixture library defaults. This preset will be applied for all “Go to
Cue Out” and home commands. Intensity values in the preset will be ignored. Channels not
included in the assigned home preset will continue to home to their library defaults.
Cue Settings
This screen allows you to set the default cue times for the parameter categories of your Ion system.
To change a time, click the parameter category button in the CIA and enter the desired time on the
keypad. To set a time for all categories at once, press [Intensity Up] [Thru]. Pressing [At] selects
manual times.
The categories for which you may set default times are:
• Intensity Up
• Intensity Down
• Focus
• Color
• Beam
7 Setup 95

Fader Configuration
This screen allows you to specify what your faders are assigned as: playbacks, submasters, or
grandmasters. These faders can be used by opening the virtual faders (see Slider Module, page
30) or by using the Universal Fader Wings (see Universal Fader Wings, page 335).
Note:
Unless you need a grandmaster or a cue list loaded to more than one fader, it is
generally not necessary to use the fader configuration screen. Assigning cue lists
and submasters can all be done from live.
Defined as Submaster Defined as Playback
Defined as Grandmaster
To change the configuration of any fader, use the {Page} buttons to access the fader page you wish
to alter. For the desired fader, click the appropriate button (playback, submaster, or grandmaster)
for the configuration you desire. Then click the {Mapped to} button and enter the number you want
to map the fader to (see Mapped to...below). When you are done making changes, click {Close}.
To leave this screen at any time without saving changes, you must click {Close}.
Mapped to...
This button is used to specify the action target of any fader. It allows you to define the fader target
that a slider is assigned to. Mapping is specific to the type of fader configuration (playback,
submaster, or grandmaster).
Submaster - A maximum of 300 submasters can be recorded. {Mapped to} defines the
submaster number that will be controlled by the specified slider. If a submaster slider is
mapped to 10, when submaster 10 is recorded it will appear on that slider.
Grandmaster - A maximum of 1 grandmaster may be assigned. A grandmaster inhibits all
live intensity values. If the grandmaster is set at 50%, all live intensities will be at 50% of
their actual values. Inhibited levels from the grandmaster do not impact data storage.
Playback - A maximum of 200 playbacks can be assigned. {Mapped to} allows you to have
the same playback appear on multiple pages as it represents a playback number, not a
specific fader or cue list number. To change the mapped location of any playback, click the
{Mapped to} button for that slider and enter the number you wish to assign to it.
Unmapped - Selecting unmapped for any fader leaves that fader open and unoccupied.
96 Ion Operations Manual

Grandmasters, submasters, and playbacks may appear on more than one fader page.
In a partitioned control environment, the mapping of the faders (with the exception of the master
fader) is global.
Note:
Specifying a {Mapped to} location does not specify the cue list that will be loaded
to that playback. Cue lists can be assigned to any playback. {Mapped to}
establishes the order in which faders will be loaded.
Whatever playbacks are mapped to “1”, they will auto-load with the first recorded
cue list. Any playback mapped to 5 will auto-load with the fifth recorded cue list,
and so on.
Master fader pair
It is possible to map the master fader pair as well. This will allow separate users to have different
lists loaded to the master fader pair. The default mapping for the pair is 0.
7 Setup 97

Show Control
This section allows you to adjust settings for MIDI show control, time code (MIDI or SMPTE),
analog, and serial functions
{SMPTE Time Code Rx}
This touchbutton is used to toggle SMPTE time code between “Enabled” and “Disabled”, thereby
controlling whether Ion can receive SMPTE time code. Choosing “Disabled” will disable all
timecode lists that have a SMPTE source. The default for this setting is “Enabled”.
{MIDI Time Code Rx}
As above, but for MIDI instead of SMPTE. The default for this setting is “Enabled”.
{Resync Frames}
This touchbutton allows you to configure how many frames need to be synced before timecode
starts running. Frames can be from 1-30. Default is 2 frames.
{MSC Receive}
This touchbutton toggles the setting for receiving MIDI Show Control from an external source
between “Enabled” and “Disabled”. The default setting is “Disabled”.
{MSC Receive Channel}
Also known as "Device ID" this setting allows you to establish the MIDI Show Control device ID for
Ion. The device ID can be set from 0-126. Ion will process commands sent to the matching Device
Id. Ion will also process commands sent to Device Id 127 (All Call). For example:
• {MSC Receive Channel} [5] [0] [Enter]
{ACN - MIDI Rx ID(s)}
This setting allows you to specify the MIDI Show Control data that Ion will receive when transmitted
over the Advanced Control Network (ACN). When set, Ion will receive MSC data from any gateway
that has its “MIDI In Stream ID” set to the same number. ACN_MIDI Receive ID can be from 1-32.
ID ranges may be used. For example:
• {ACN_MIDI Receive ID} [2] [5] [Enter]
{MSC Transmit}
This touchbutton toggles the setting for transmitting MIDI Show Control data between “Enabled”
and “Disabled”. The default setting is “Disabled”.
{MSC Transmit Channel}
Also know as "Device ID" this setting allows you to establish the device ID with which Ion will
transmit MIDI show control information. A device ID can be from 0-126 or 127 (All Call). For
example:
• {MSC Transmit Channel} [5] [0] [Enter]
98 Ion Operations Manual

{ACN - MIDI Tx ID}
This setting allows you to specify the ID number of MIDI Show Control data that Ion transmits over
an Advanced Control Network (ACN). When set, Ion will transmit MSC data to any gateway that has
its “MIDI Out Stream ID” set to the same number. ACN_MIDI Transmit ID can be from 1-32. ID
ranges may be used.
• {ACN_MIDI Transmit ID} [2] [5] [Enter]
{Analog Inputs}
This touchbutton toggles the setting for receiving analog inputs between “Enabled” and “Disabled”.
Default is “Enabled”.
{Relay Outputs}
This touchbutton toggles the setting for allowing Ion to trigger external relays. Options are
“Enabled” or “Disabled”. The default is “Enabled”.
{Serial Enable}
This touchbutton toggles the ability to receive serial commands. Options are “Enabled” or
“Disabled”. The default is “Enabled”.
{Serial Group Ids}
This touchbutton is for setting up which serial group IDs the Ion will listen to. Serial Group IDs are
from 1-32. Ion can be set to listen to multiple group IDs.
• {Serial Group Ids} [1] [+] [5] [Enter]
Partitions
Pressing the {Partitions} button in Show setup opens the partition display in the CIA. This display
shows any recorded partitions, including the four pre-existing partitions. For more information, see
Using Partitioned Control, page 289.
Note: Filter setup and encoder configuration settings are not available at this time.
7 Setup 99

Desk
This setup softkey accesses settings for the user identified on the associated Ion device. Changing
these settings does not impact other Ion controllers on the network assigned a different user ID.
{Record Defaults}
This screen enables you to change general record defaults as well as change the default parameter
category times associated with certain actions ([Back], [Go to Cue], and [Assert]).
To change the setting for any of these fields, click the field in the CIA to activate it. If the field
requires data, enter it from the keypad. If the field is a toggle state, one click of the button will switch
the field to its other state.
Auto Playback
When enabled, this feature automatically plays back cues and submasters as they are stored and
releases manual control. For submasters to automatically play back, the slider must be at full. This
field is a toggle state between “Enabled” and “Disabled”. When auto playback is “Disabled”, all
manual levels are maintained and cues must be loaded and executed on playbacks. The default is
“Enabled”.
Track
This field allows you to switch between tracking and cue only modes (see Tracking vs. Cue Only,
page 5). The default is “Tracking”.
Record Confirm
This setting allows you to enable or disable the confirm action when storing over a previously
recorded target. The default is “Enabled”.
Delete Confirm
This field allows you to enable or disable a required confirmation before any delete command is
executed. The default is “Enabled”.
100 Ion Operations Manual

{Manual Control}
This desk setting button gives you access to Ion manual control settings.
Manual Time
In this section you may change the default times for manual changes to occur in live. Times can be
set for each parameter category (Intensity Up, Intensity Down, Focus, Color, and Beam). You may
use the [Thru] key to enter a value for all categories.
• {Int Up} [Thru] [9] [Enter]
The default for each of these is 0 seconds.
Manual Control
This section allows you to specify the values for certain buttons and settings used in manual
control. To change any value, click the appropriate button in the CIA and use the keypad to enter a
new value.
Preserve Blind Cue - This enables the console to recall the last selected cue in blind when
you return to blind. The default is disabled.
Level - This sets the default for Level (which is accessed in Ion by double pressing [Full]).
Any value between 0-100 may be entered. The default is 100.
Plus% - This sets the level for the +% (which is accessed in Ion by pressing [At] [+][+]),
which will increase the selected channel by the set percentage. Any value between 0-100
may be entered. The default is 10%.
Minus% - This sets the level for -% (which is accessed in Ion by pressing [At] [-][-]), which
will decrease the selected channel by the set percentage. Any value between 0-100 may
be entered. The default is 10%.
Highlight Preset - This field is used to specify the preset that will be used for highlight
commands.
Lowlight Preset - This field is used to specify the preset that will be used for lowlight
commands.
High/Low Rem Dim - This enables a Remainder Dim when any highlight or lowlight
commands are given, thereby temporarily dimming any channel not participating in the
High/Low.
Rem Dim Level - This allows you to set the level for all Remainder Dim commands. The
default is 0.
Default Times
In this section you may change the default times for sneak commands and the respective feature
response times based upon parameter category. The default for these is 5 seconds, except for back
time, which uses a default of 1 second.
7 Setup 101

{Face Panel}
Sounds
You can adjust the frequency and length of the audible sounds that Ion delivers. Sounds are
qualified as being either an error sound or an advisory sound. Both types of sounds can be adjusted
from this setup screen in the CIA.
To adjust a sound, move the virtual slider with the mouse on the CIA. To hear the result of your
adjustment, click the {Test} button respective to the sound type, located beneath the sliders.
To turn off all sounds completely, error and advisory alike, click the {Turn Sounds Off} button. The
sound area will then be replaced with a {Turn Sounds On} button, which can be pressed to
reactivate audible signals in Ion.
Level Wheel
You can adjust the increment and acceleration effect of the level wheel from this screen as well.
To alter the number of ticks in a full turn of the level wheel, adjust the slider labeled “LW ticks”. This
will increase or decrease the amount of change effected when you use the level wheel. A higher tick
setting will increase the amount of change resulting from one turn while lower settings will decrease
the amount, making smaller adjustments easier to perform. The options range from 50 - 255 ticks.
The default is 150.
Ion also provides an adjustable acceleration feature for the Level wheel. This feature allows you to
adjust the wheel’s sensitivity to fast adjustments, thereby temporarily overriding the number of ticks
setting. To adjust the level wheel acceleration, use the virtual slider labeled “LW Acc. Factor”. The
higher the slider setting, the less sensitive the level wheel will be to acceleration. The lower the
setting, the more sensitive it is. When set low, the faster you move the wheel, the greater the
increment covered by a revolution. When movement stops, the normal LW ticks will be reinstated.
Encoder
Similar to “LW Acc. factor” (see above), the encoder acceleration factor is used to adjust the
acceleration of all encoders.
To adjust the encoder acceleration, use the virtual slider labeled “Encoder Acc. Factor”. The higher
the slider setting, the less sensitive the level wheel will be to acceleration. The lower the setting, the
more sensitive it is.
“Encoder Tic Freq.” can be used to increase or decrease the number of ticks in a full turn of the
encoder.
{Face Panel Keypad}
This screen allows you to adjust the auto repeat settings (delay and speed) for the facepanel
keypad as well as enable/disable the blackout and grandmaster functions for your Ion.
102 Ion Operations Manual

{Displays}
This desk setting button gives you access to the Ion display settings.
High Contrast Display
This button toggles the setting between “Enabled” and “Disabled”. When enabled, high-contrast
brightens the cue numbers and channel numbers in displays and also brightens the magenta used
to show tracked values.
The default setting for this is “Disabled”.
Show Reference Labels
This button toggles the setting between “Enabled” and
“Disabled”. When enabled, referenced record targets (such
as presets or palettes) with labels will have their labels
displayed in the live/blind display rather than their target
type and number. [Label] can be used to toggle between
views.
Reference
labels
The default setting for this is “Disabled”.
Group Chans By 5
You can turn off/on the grouping of channels in groups of 5
in the live summary view from this field.
The default for this setting is “Enabled.”
User Id
You can Change the User ID for the console by selecting this button and entering a number from the
keypad. For more information on User ID see About User ID, page 288.
100 Channel Display
This setting can be used to display 100 channels at a time in the live summary view. The default for
this setting is “Disabled.”
Cmd Line on PSD
This setting can be used to display an optional command line on the Playback Status Display. The
default for this setting is “Disabled”.
7 Setup 103

{PDF File Settings}
This screen allows you to select the orientation and paper type for PDF files.
{LCD Settings}
This screen allows you to adjust the brightness and contrast settings for the Ion LCD and the fader
wing LCDs.
{Fader Wing Config}
This screen allows you to manually configure the positions of fader wings connected to the Ion. The
console will default to configuring the wings on its own.To manually configure, you must click on the
{Manual Config. Off} softkey.
Clicking on the {Manual Config. Off} button turns manual configuration on and displays the Fader
Wing Configuration screen.
104 Ion Operations Manual

Clicking {Identify} will display numbers on each wing’s display to aid in configuration. The numbers
do not identify the wings as to their actual order. Order is determined from left to right. The left most
wing will contain the first faders, unless a 1x20 wing is attached. A 1x20 will always contain the first
faders regardless of other wings to the left of it.
Click and drag the wings to match your physical layout. Click {Apply} to save the changes. Clicking
{Reset} will restore to the last saved configuration. Clicking {Manual Config. On} will turn off
manual configuration and will require a restart of the application before the console will
automatically configure the wings.
{RFR Settings}
This screen is for allowing RFR connections. The default setting is “Enabled”.
Security
This feature will be available in a future release.
7 Setup 105

106 Ion Operations Manual

Chapter 8
Basic Manual Control
Ion provides a variety of ways to select and command control channels. This chapter identifies the
many basic ways you can select channels and manipulate show data within Ion.
This chapter contains the following sections:
• Selecting Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
• Setting Intensity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
• Manual Control of Non-intensity Parameters (NPs) . . . . . .111
• Home. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
• Lamp Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
• Using +% and -% . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
• Remainder Dim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
• Highlight and Lowlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
• Sneak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
• Flip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
• Channel Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
• Address at Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
• Address Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
• Using {Move To}. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
8 Basic Manual Control 107

Selecting Channels
Ion provides interactive ways to select channels including the control keypad and direct selects.
Channels are deselected when any action is taken on the keypad that is unrelated to manual
control, such as recording groups and cues, or updating a record target, etc. You can also press
[Clear] after a terminated command line to clear the channel selection.
Select Channels From the Keypad
The keypad defaults to selecting channels, therefore no channel key is provided. Channels may be
selected on the control keypad using the [+], [-], and [Thru] keys for consecutive or nonconsecutive
channel selection.
The following examples illustrate various methods of selecting channels from the control keypad:
• [5] [Enter] - selects channel 5.
• [5] [+] [7] [Enter] - selects non-consecutive channels 5 and 7.
• [5] [thru] [9] [Enter]- selects channels 5 through 9.
• [2] [thru] [8] [-] [5] [Enter] - selects a range of channels 2 through 8, except channel 5.
• [-] [6] [Enter] - removes channel 6 from the current selection list.
• [+] [1] [Enter] - adds channel 1 to the current list of channels.
Note:
You may use [+] and/or [-] multiple times to add or remove multiple channels from
the selection. [Thru] lists may be entered in ascending or descending order.
Note: The [Thru] command uses the current flexichannel state. Channels not included
in the flexichannel mode (except selected channels mode) are not collected in a
thru range. [Thru] [Thru] can be used to collect all channels in the range, even if
they are not in the current flexi mode. See “Using Flexichannel” on page 40.
108 Ion Operations Manual

[Next] and [Last]
The [Next] and [Last] buttons increment and decrement channel selection. If only one channel is
selected, [Next] increments the channel selection to the next sequential channel, while [Last]
decrements the channel selection by one.
Select channel 10 then change the selection to channel 11 using the [Next] key:
• [1] [0] [Enter]
Channel 10 is selected with a gold outline around the entire channel and the channel
number is indicated in white.
• [Next]
Channel 11 is now selected with a gold outline and white channel number while channel 10
is no longer selected.
If there is no specific channel selected when [Next] or [Last] is pressed, channel 1 is selected.
When a group of channels is selected, pressing [Next] or [Last] selects the first or last channel in
the channel list.
For Example:
Channels 11 through 20 are selected:
• [Next]
Channels 11 through 20 are still the specified channel list but only channel 11 is selected
for control. You can now sequentially press [Next] or [Last] to cycle through the list. Press
[Select Last] to reselect the entire range.
Note:
Offset
[Next] and [Last] work with the current flexichannel state. See “Using
Flexichannel” on page 40.
{Offset} is a feature used to select a range of channels from a broader channel selection. For the
offset feature to function, you must first select a group of channels, then press {Offset}. When
{Offset} is pressed, the softkeys change to the following: {Even}, {Odd}, {Reverse}, and
{Random}. These keys, along with the numeric keys from the keypad are used to create channel
offsets. These channel commands can be combined with group record functions.
The following examples illustrate how offset works:
• [1] [thru] [10] {Offset} {Even} [Enter] - selects channels 2, 4, 6, 8, 10.
• [1] [thru] [2] [0] {Offset} [3] [Enter] - from the selected group, this syntax would select
channels 1, 4, 7, 10, 13, 16, 19 which is an offset of every third channel from the selection.
• {Group 5} {Offset} {Random} [Enter] - selects all channels in Group 5 and places them in
random order. This selection may be used only temporarily or it may be recorded to a new
Group.
• [1] [thru] [2] [0] {Offset} {Even} {Random} [Enter] - selects all even channels within the
range and puts them in random order.
• {Offset} [4] [Enter] -selects every fourth channel in the current channel selection.
8 Basic Manual Control 109

Setting Intensity
Channel intensity may be manually entered from the keypad, set with an intensity palette (if
programmed) or set with the level wheel. Pressing [At] after channel selection assumes an
intensity value will be added to the selected channels. You may also use the [Full] button to bring
the selected channels to their full intensity or you may use the [Out] button to fade the intensity out.
Use the Level ([Full][Full]), +% ([At] [+][+]) and -% ([At] [-][-]) keys to affect the intensity value of
selected channels. Each of these keys are set at a specific value established in the Setup ({Manual
Control}, page 101).
• Level is set by default to full (100% intensity).
• +% and -% are each set by default value of 10 points.
The following examples illustrate the various methods of setting intensity:
• [1] [+] [3] [At] [5] [Enter] - selects channels 1 and 3, and sets an intensity level of 50%.
• [1] [thru] [5] [-] [4] [Full] [Enter] - selects a range of channels 1 through 5, except channel
4, and sets the intensity to full.
• [1] [thru] [8] [At] [+] [3] [Enter] - adds 30% to all intensities in the channel selection. If they
were at 50, they will now be at 80. If channels 1, 3, and 5, were at 30 and 4 was at 50, they
would be 60% and 80% intensity, respectively.
• [5] [thru] [8] [At] [-] [3] [Enter] - scales the intensities of the selected channels in the list down
30% of their current values.
• [1] [thru] [4] [At] [/] [1] [3] [0] [Enter] - scales the intensities of the selected channels in the
list up 30% of their current values. If channels 1 through 4 were at 40% intensity, this would
scale them up by 30% to a value of 52.
• [2] [+] [5] [level wheel] - roll the wheel up for greater intensity or down for less intensity.
• [1] [Full][Full] - selects channel 1 and sets it to the level as established in Setup.
• [Group] [9] [Out] - selects all channels in Group 9 and sets the intensity values for those
channels to zero. As long as channels are on the command line you can continue to address
them with commands without having to reselect them.
• 1] [0] [At] [At] - selects channel 10 and sets an intensity level of full.
For Example:
• [1] [thru] [5] [Full] [Enter]
The selected channels are highlighted in gold, with white channel text and red intensity
values (indicating manual data). You may continue to modify channels 1 through 5 since
they are still selected and displayed on the command line.
• [At] [-][-] [At] [-][-]
This command would reduce the intensity of channels 1 through 5 by 20%.
• [at] [7] [5] [Enter]
You can continue manipulating the selected channels so long as the channels are selected and
displayed on the command line.
Level Wheel
You may set intensity for selected channels or addresses using the level wheel. Rolling the level
wheel upwards increases intensity. Rolling it downwards (towards you) decreases it.
110 Ion Operations Manual

Manual Control of Non-intensity Parameters (NPs)
Non-intensity parameters can be set with a variety of controls including the control keypad, buttons
on the central information area (CIA) and the encoders.
Parameter Display
The parameter display in the CIA is populated with only those parameters that are found in the
patched devices. As channels are selected, the parameter display will change to show only
parameters relevant to the selected channels.
The parameters are divided into the following categories: Intensity, Focus, Color and Beam. Each
parameter category is represented with buttons at the bottom of the CIA. These buttons allow you
to select the entire collection of all parameters within that category in one button press. You can
also select a single parameter from a category using that parameter’s button in the parameter
display.
Beam has three subcategories which correspond to the way the encoders are mapped. They are
{Shutter}, {Image}, and {Form}. These subcategories are represented with buttons in the CIA.
Pressing these buttons allows you to select all parameters within those subcategories.
Within the CIA, in the upper left corner, notice the {All NPs} button. When pressed, this collects all
non-intensity parameters for further editing.
Some examples of using parameter buttons are:
• [1] {Iris} [5] [Enter] - Places the iris parameter of channel 1at 50%.
• [Group] [4] {Zoom} {Edge} [Out] [Enter] - Sends any zoom and edge values for all fixtures
in group 4 to 0%.
8 Basic Manual Control 111

Setting Parameters with the Keypad
When the CIA is placed in parameter mode, all parameters of selected channels may be given
numeric values through the keypad. Linear devices can be provided instructions from 0 to100, pan
and tilt are controlled from -270 to 270 and -135 to 135 respectively. Saturation controls are
represented from 0 to 360 and Hue controls are represented from 0 to 100. CMY and RGB are
represented from 0-255.
When no channels are selected, the CIA shows all of the parameters that are available in the
lighting system. When channels are selected, the CIA condenses to show only the parameters that
are appropriate to the selection set. If channels are selected that have different device types, such
as spot and wash lights, the CIA will show all of the available parameters. Parameters that are not
available to all channels are greyed out.
The following examples illustrate how to set parameter values with the keypad:
• [5] {Iris} [5] {Zoom} [6] [5] {Edge} [5] [Enter] - sets channel 5 to an iris value of 50%, a zoom
value of 65%, and an edge value of 50%.
Note:
Pressing down on an encoder will place the associated parameter onto the
command line for numeric entry.
Setting Non-intensity Parameters with the Encoders
Encoders provide a quick method to adjust current values for non-intensity parameters. The four
encoders are pageable using the six encoder page buttons to the upper right of the encoder LCD.
The encoder page buttons consist of: [Focus], [Custom], [Color], [Form], [Image], and [Shutter].
Form, Image and Shutter are subcategories within the broader parameter category of Beam.
• Focus - includes pan and tilt control.
• Custom - includes intensity and intensity MSpeed.
• Color - includes all color mixing controls (CMY, RGB, HS), as well as scrollers, color wheels
and color effects.
• Form- includes parameters that affect the quality or size of the light output, such as edge,
zoom, iris, IMF, frost, etc.
• Image - includes anything that drops into the gate, such as gobos, effects wheels, etc.
• Shutter - includes all of the framing devices for the luminaire.
The LCD beneath the encoders indicates the parameters they control and provides additional
information about the current status of those parameters. Encoder pages populate with parameters
relevant to fixtures in the show patch. When you access a parameter page, controls that are not
available for selected channels are suppressed.
112 Ion Operations Manual

Encoder LCD screen
The encoder LCD displays the active parameter category loaded on the encoders, as selected by
the page buttons. Each encoder has an associated control section in the LCD that provides visual
indication of:
• The parameter it controls.
• The current setting (value) of the parameter.
For Example:
Encoder
wheel 1
Encoder
wheel 2
Encoder
wheel 3
Encoder
wheel 4
The above graphic shows the encoder LCD displaying the focus parameters for a moving
light.
• Encoder 1 is controlling pan.
• Encoder 2 is controlling tilt.
• Encoder 3 is controlling position MSpeed.
• Encoder 4 is not assigned.
Pressing a different encoder page key loads the encoders with other parameters of that type (if
available).
8 Basic Manual Control 113

Encoder paging
The number of pages for each category is displayed at the right of the LCD. You can go directly to
the page required by pressing the encoder page button and a page number. For example:
• {Form} & [3] - this will take you to the third page of the form category.
Information in the encoder LCD is only as accurate as the patch information for that channel. For
example, when you are working with color scrollers, the standard manufacturer color frames will be
displayed for scroller controls unless you have created a custom scroll for the selected channel in
patch using the Scroll Editor.
When you have created a new scroll or wheel in patch for any channel and that channel is selected,
the custom information is displayed in the associated encoder LCD. See “Creating a new scroll or
wheel” on page 76.
The encoder pages change depending on the channels selected. Below are scenarios to explain
some of the possible operating conditions:
• Parameters that are in the show patch but do not apply to the selected channels are
suppressed. The parameter name will be displayed in grey, but controls will be withheld as
they are not applicable to the selected channel.
• When a group of channels is selected with some parameters that are similar but others that
are not, the following will occur:
• Parameters that are shared by all selected channels are displayed in white, with control
provided for all channels.
• Parameters that are available to some, but not all, of the selected channels are
displayed in grey, with all available controls indicated. You may use these controls but
the channels that do not support the relative parameters will not respond to the actions.
• Parameters that none of the selected channels support are displayed grey, with only
the parameter name shown.
• When you access a parameter page, the encoder wheels will automatically load and display
the first page that has a valid parameter for the selected channels.
Encoder softkeys
If you press the encoder for any parameter, the softkeys change to display options relevant to that
parameter. These may include {Home}, {Last} and {Next}, or {Min} and {Max}, and depending on
the type of parameter, a {Mode} or {Calibrate} button.
Home
Each parameter has an associated {Home} softkey. This accesses any parameter and returns it to
its default position. Additionally, the control keypad has a [Home] key. The [Home] key on the
control keypad is a channel level instruction, meaning the entire luminaire will return to its home
position unless you modify the instruction by selecting specific parameters or parameter categories.
The following examples illustrate use of these two keys, both from the control keypad and the
softkeys:
• {Home} - when pressed from the encoder LCD, only the associated parameter of the selected
channels will return to its home position.
• [1] {Home} [Enter] - homes all non-intensity parameters of channel 1. When this command
overrides playback data, it results in a manual value for the associated parameters. When this
command is an override of only manual data, it returns the parameters to their home position
and removes the manual setting.
• [1] {Color} [Home] [Enter] - homes all of the color data for channel 1. You may also use the
[Color] encoder page button for this command.
114 Ion Operations Manual

Min and Max
{Min} and {Max} are displayed when the parameter is linear, such as a shutter. Use these keys to
set a minimum and a maximum setting for a parameter.
Next and Last
{Next} and {Last} are displayed when the parameter is segmented such as a fixed gobo or color
wheel or a color scroller. Use these keys to increment or decrement in full frames.
Mode
The {Mode} key is provided to select different modes for the encoder wheel such as rotate, index,
or special effects.
• When more than two modes are available, the {Mode} key can be pressed repeatedly,
advancing through the various modes. Each mode will display beneath the current
parameter setting.
• When only two modes are available, the alternate mode is indicated instead of a
{Mode} key. Toggling that button switches the encoder wheel to the alternate mode.
Flip
The {Flip} button, available in the Pan/Tilt section of the encoder LCD, is used to flip the unit into its
exact same position, but from the other direction. Depending on the current values of pan and tilt,
there may be multiple flips.
Trackball On/Off
The {TrckbllOn/Off}, as displayed in the Pan/Tilt section of the encoder LCD when either the pan
or tilt encoder is held down, is used to give pan and tilt functionality to a mouse or trackball
device.When this function is turned on, above the CIA will be a message saying “Cursor as Pan/
Tilt”.
Multiple Encoder Control
When parameters require more than one encoder for full control, the encoder LCD provides
indication that the encoders are related to each other by name. Typically, additional modes will load
on other pages but will reference the master parameter unique name. If there are multiple instances
of a device in a single channel (such as two fixed gobo wheels or two color wheels, etc.), each
device will load onto separate encoders.
Virtual Encoders
You can use the virtual encoder module to view encoder information in a format more similar to Eos.
Virtual encoders can be opened on the display and manipulated with the mouse. Color tiles, gobos,
and other information can be viewed in the virtual encoder display. Encoder buttons are more
readily available to you from the virtual encoders as well.
To use the virtual encoders
Step 1: Navigate to Browser>Virtual Controls>Encoder.
Step 2: Select {Open as Primary Display} in the CIA options. The virtual encoders will open
on the display.
Step 3: Manipulate the actual encoders and view the data available to you on the virtual
encoder display.
Step 4: When you are done with the virtual encoders, press [Live] or [Blind] to return to the
normal display.
8 Basic Manual Control 115

Form Control
Form (a subcategory of Beam) collects the parameters that affect the quality of the beam, including
the iris, edge, frost, etc. ‘Shutter’ and ‘Image’ are the other two subcategories of Beam.
When the [Form] encoder page button is selected, the LED will illuminate and the encoders
automatically populate with the “Form” parameters as specified in the show patch. If there are more
parameters in the show patch than will fit on the first page of the encoders, press the [Form] button
again to page through the remaining parameters in the category or press [Form] and a page
number to jump to a specific page.
The form parameters may include:
• Edge - controls the hard and soft qualities of a spot luminaire. While some fixtures may call
this parameter “focus”, it is always represented as “edge” in Ion, to avoid confusion with
“Focus” which refers to pan and tilt data. The edge encoder provides two buttons, [Hard] and
[Soft], which set the selected luminaire to its hardest (sharpest) edge or its softest edge. These
values are set to the system default value for the selected luminaire, but may be modified as
required on a per fixture basis.
• Iris, Zoom, Strobe and IMF- each parameter has in/out, narrow/wide, or fast/slow settings.
Iris and Zoom also have programmable limits, called in/out and narrow/wide respectively. The
strobe mode setting varies based on the fixture type.
Image Control
Image is the collection of parameters that affect the contents of the beam (gobo, prism, effects
wheel, etc.).
116 Ion Operations Manual

Shutter Control
Pressing the [Shutter] button displays shutter controls, if there are any fixtures with framing
devices patched.
Press the [Shutter] button again to access the additional shutter controls, available to the specific
channel.
Color Control
Depending upon the specific device, color can be established manually with the encoders using:
• CMY color-mixing
• Hue and saturation color mixing
• RGB color-mixing
• Selection from a color wheel or scroller
You may also specify color by using the hue and saturation (HS) color picker and gel picker.
It is also possible to set non-intensity parameter data with direct entry using the control keypad and
using the parameters on the CIA.
• [1] [At] [4] {Cyan} [5] [5] [Enter]
Note:
Custom Control
Color scroller data will display on the encoders and displays as frame numbers,
F1, which would be frame 1, F2 for frame 2, etc. F1.5 is halfway between 1 and 2.
F2+ will display if the frame is less than 2.5 and F2- if the frame is greater than 1.5.
After the frame number, the gel number will also be displayed.
Frame numbers can be used from the command line. [2]{Scroller}[5][Enter] will
send channel 2’s scroller to frame 5. Frames can also be selected by using the
DMX address for that frame. Pressing [/] twice will post DMX to the command line.
[3] {Scroller} [/][/][2][5][5] [Enter] will send channel 3’s scroller to the frame with
the DMX address of 255.
Pressing the [Custom] button displays intensity controls.
8 Basic Manual Control 117

Using the Color Picker
Press the [Displays] button and select the {Color Picker} from the softkeys to display the color
picker in the CIA.
Within the color picker, you will
see columns of buttons to the
right. The first button {Color
Format} is for toggling between
native (RGB, CMY, color scroller,
or color select) and hue and
saturation. The other buttons are
manufacturer catalogs of gels. To
display a specific manufacturer’s
catalog, press the specific
manufacturer or catalog and
select the desired gel. The
{Bright. to Full} button will only
appear if selected channels have
a brightness parameter.
When channels are selected and a specific gel is chosen, the color picker will show a dot which
represents the selected fixture(s). The dot is a visual indication of the color each fixture can
accommodate, closest to the gel selected. This tool is most useful when color matching between
different fixture types to maintain an even field of color. You can click in the picker to go to the hue
and saturation values or you can match a specific gel color from the manufacturers’ list on the right.
Selecting a specific gel will also produce the hue and saturation value.
What is Hue and Saturation?
Hue is the actual color. It is measured in angular degrees around the cone
starting and ending at red = 0 or 360 (so yellow = 60, green = 120, etc.).
Saturation is the purity of the color, measured in percent from the center of
the cone (0) to the surface (100). At 0% saturation, hue is meaningless.
Brightness is measured in percent from black (0) to white (100). At 0%
brightness, both hue and saturation are meaningless.
Gel colors can also be manually entered into the command line. [6] [Color] [1] [/] [1050] [Enter]
assigns Apollo gel number 1050 to channel 6. Each of the manufacturers have been assigned a
number, which can be seen beside their name in the Color Picker display.
When channels are selected, a black line may appear in the color picker. This line indicates what
colors can be mixed by the fixture. If a color lies outside of the line, that color is out of the range of
that device. If no black line is visible, the fixture has not yet been calibrated and the color matching
will be approximated.
The gel picker is normalized to 3200 degrees. Therefore, if you are setting Rosco 80 (R80) on a arc
source device, it will appear to be the same color as R80 on an incandescent source.
Encoders
When both CMY and RGB mixing systems are present in the lighting system, they take priority in
the encoder mapping, followed by fixed wheels, then scrollers. A CMY color mixing fixture may not
be placed in RGB mode, nor can an RGB fixture be placed in CMY mode.
• When the device is a fixed color wheel or a color scroller, you can use the encoder to select
the desired frame. Pressing the {E} expands the display to include a button for each frame
indicated with both a location number (example: “#5”) and a label (example: “Rosco R80”).
The specific colors within the scroller or wheel are specified in patch. See “Creating a new
scroll or wheel” on page 76.
118 Ion Operations Manual

Home
Ion is equipped with a [Home] hardkey. This hardkey allows you to home a specific parameter.
Additionally, you may home all of a channel’s non-intensity parameters or home only a specific
category (I, F, C, B).
Homing a channel, category, parameter, or submasters will return it to the default value.
• [1] [Home] [Enter] - homes all parameters for channel 1, except intensity.
• [1] [Color] [Home] [Enter] - homes all color parameters for channel 1.
• [Group] [1] [Color] [Focus] [Home] [Enter] - homes the color and focus parameters of all
channels in group 1. You can use the category keys in the CIA or the encoder paging keys.
• [Sub] [1] [Home] [Enter] - homes submaster 1.
• [Sub] [1] [Thru] [Home] [Enter] - homes all submasters.
You can select a preset to provide home values for non-intensity parameters (instead of fixture
library default values) when home commands are used. Store a preset with modified home values
for only the channel parameters you would like at a different value than default. And then assign
that preset to Home in Setup (see Show Settings, page 95). Intensity will disregard the preset
value. Any channels that are not included in the preset assigned to Home in Setup will use their
library defaults.
Select Last
The [Select Last] key allows you to reselect the previous channel selection. This includes multiple
channel selections, groups, and so on. Using [Select Last] [Select Last] you can recall the last
completed command line. However [Select Last] [Select Last] will not terminate the command
line, [Enter] is required.
When pressed and held, the softkeys on Ion change to display the following additional options:
• {Select Active} - selects all active channels.
• {Select Manual} - selects all channels with manual data.
• {Select All} - selects all channels.
8 Basic Manual Control 119

Multiple Intensity Channels
When a multiple intensity channel is patched, Ion assigns it a master intensity. The master intensity
can be used to control the multiple intensities together. The master intensity is handled in the same
way as the intensity of a single intensity channel. Levels can be set via the level wheel, from the
keypad, and the encoders. Master intensity can also be set via the parameter buttons in the CIA.
{Intens} controls the master intensity. The other intensities will default to 100%.
Control of the individual intensities of a multiple intensity channel is handled using keypad with the
parameter buttons in the CIA (see Manual Control of Non-intensity Parameters (NPs), page 111) or
the encoders. Pressing the [Custom] button will map the intensity parameters to the encoders. You
can either use the encoder itself to adjust the level or you can press down the encoder of the
parameter you wish to put on the command line.
Levels assigned to the individual intensities will act independent of each other and the master
intensity.
• [1][0][0] {Intens 3} [At] [5][0] - sets intensity 3 of channel 100 to 50% intensity.
• [1][0][0] [At] [7][5] - sets the master intensity of channel 100 to 75% intensity. All
intensities for channel 100 will be set to 75% unless they have a separate intensity set.
In Table view, Ion will default to showing all intensity parameters associated with the channels.
In summary view, the master intensity is shown. If one of the
multiple intensities has a value, an ‘+’ will display beside the
master intensity.
indicates that
there is a level
set from an
individual
intensity
120 Ion Operations Manual

Lamp Controls
Lamp controls allow you to execute control functions of selected fixtures such as calibrate, douse
lamp, strike lamp, and reset. Each fixture type has its own set of lamp control options which are
available to you when you select the fixture from live and press the {Lamp Cntrls} softkey. This
information is also available using [About] (see Using About, page 245).
For Example:
• [1] [1] [Enter] {Lamp Cntrls}
-or-
• [1] [1] [Enter] [About] {Lamp Cntrls}
This screen displays any lamp controls associated with the selected channel (this is also the “Lamp
Control” subscreen of About). If the channel is a conventional (intensity-only) fixture, no parameters
will be displayed. When the selected channel is an automated luminaire, options specific to the
fixture type will display for use.
Exit the lamp controls display by pressing [Displays].
Pressing any of these parameter control
buttons will affect the selected channel
immediately.
8 Basic Manual Control 121

Using +% and -%
Use +% and -% to incrementally change parameter values. To access this function on Ion, press
[At] [+][+] or [At] [-][-]. By default, +% and -% are assigned a value of 10. This can be changed in
Setup. This can be used with any parameter.
Channel Intensity
When channels are selected, pressing [At] [+][+] increments the intensity level by 10 (or by the
value established in setup, see {Manual Control}, page 101). Alternatively, you may press [At] [-][-
] to decrement the intensity level by 10. You may use these keys consecutively to “add to” or
“subtract from” the intensity level.
For Example:
Select channels 1 through 10 and set them to an intensity level of 45% from the keypad.
• [1] [thru] [1] [0] [at] [4] [5] [Enter]
Change the intensity level to 65% using +% which is set to its default value of 10% in the
setup menu.
• [At] [+][+] [At] [+][+]
Non-intensity Parameters
+% and -% may be used to incrementally adjust non-intensity parameters as well.
For Example:
• [1] {Iris} [At] [+][+] [At] [+][+]
• [Zoom] [At] [-][-] [At] [-][-]
122 Ion Operations Manual

Remainder Dim
[Rem Dim] temporarily provides a zero intensity to all channels except those that are currently
selected, those that are parked, or those with intensity contributions from submasters. If the
remainder dim command is reversed, the stage returns to its previous state. You may use the
following commands for remainder dim:
• [Next] and [Last]- moves through the channel list.
• [select channels] [Rem Dim] [Enter] - sets all non-selected channels to zero
• [Rem Dim]- clears the rem dim function and returns the stage to its previous state
Pressing [Rem Dim] again releases all channels from rem dim mode and restores the stage to its
previous state. Using the [Next] and [Last] buttons releases the current selected channel from
Remainder Dim mode and sets its intensity to zero, while selecting the next or last channel and
continuing Rem Dim operation.
For Example:
Assume channels 5 through 9 are selected and set at an intensity level of 50% and
channels 10 through 15 are selected and set at an intensity level of 70%. Select channel 9
and dim the remaining channels.
• [9] [Rem Dim] [Enter]
Channel 9 is set at an intensity level of 50% and all remaining channels are dimmed to zero.
• [Next]
Selecting [Next] changes the channel selection to channel 10 which is set at an intensity
level of 70%, the level set in the previous state, and all remaining channels including
channel 9, are dimmed to zero.
[Rem Dim] can be used in groups including the use of [Next] and [Last] buttons to progress
through the channels within the selected group.
For Example:
Assume you have group 1 selected (includes channels 1 through 10) with an intensity value
of 50%, group 5 selected (includes channels 11 through 20) with an intensity value of 70%,
and group 7 selected (includes channels 21 through 30) with an intensity value of 100%
• [Group] [1] [at] [5] [Enter]
• [Group] [5] [at] [7] [Enter]
• [Group] [7] [at] [Full] [Enter]
Select only Group 1 and dim the remaining Groups using the [Rem Dim] feature.
• [Group] [1] [Rem Dim] [Enter]
Channels 1 through 10 are selected with an intensity value of 50%, and all remaining
channels are at a 0% intensity. You may progress channel by channel through the selected
group (Group 1, channels 1 through 10) using the [Next] or [Last] key. Each press of the
[Next] or [Last] key cycles you through only the channels of the selected group.
Using [Next] or [Last] negates the ability to return to the previous stage state by using
[Rem Dim].
8 Basic Manual Control 123

You can set the dim level for all remainder dim commands in Setup (see {Manual Control}, page
101). When set to a value other than zero, all rem dim commands will bring intensity to this level
instead. However it won’t bring an intensity up. For example, if the rem dim level in setup is set to
50%, [Rem Dim] will drop any value above 50% to 50%, but not add intensity to any channels
below 50%.
It is possible to override the dim level temporarily by specifying a level after the [Rem Dim]
command.
[Rem Dim] can also be used to exclude channels from a submaster or cues during a [Record] or
[Update].
For Example:
Using [Rem Dim] You can modify which channels are recorded in the submaster. For this
example, assume that channels 1 through 10 are at full. You’ve recorded that to submaster
one. Using [Rem Dim], you can modify the record so only channels 1 through 5 are
recorded to the submaster.
• [1] [Thru] [1] [0] [At] [Full] [Enter]
• [Record] [Sub] [1] [Enter]
• [1] [Thru] [5] [Record] [Sub] [1] [Rem Dim] [Enter]
The same works for [Update]. Using the same example, the submaster can be updated to
contain only channels 1 through 5 at full.
• [1] [Thru] [1] [0] [At] [Full] [Enter]
• [Record] [Sub] [1] [Enter]
• [1] [Thru] [5] [Update] [Sub] [1] [Rem Dim] [Enter]
Without the [Rem Dim] command, the submaster would still contain channels 1 through 10
at full.
A [Rem Dim] command can also be used on a selective cue record. It will force any channels not
included in the record, but are tracking forward from a previous cue, to zero.
124 Ion Operations Manual

Highlight and Lowlight
Ion can be placed in Highlight or Lowlight mode. Channels selected while in these modes will either
go to a default setting, or to a value provided by a highlight/lowlight preset (established in setup).
Modifications can then be made to those channels. Any changes will be maintained when the
highlight/lowlight mode is removed.
Highlight is very useful to isolate and adjust individual fixtures. Lowlight is simply an alternative
state that might be useful at different points in programming (for example, perhaps you want
shutters to be open for Highlight, but not so in Lowlight).
To place Ion in highlight mode, press {Highlight} [Enter]. The command line will show that
highlight is currently in use.
If no highlight preset is established, or for channels that have no value stored in the highlight preset,
the following values will be applied to channels as they are selected:
• Intensity - full
• Focus parameters - no change from present state
• Color parameters - home value
• Shutter parameters - no change from present state
• Image parameters - home value
• Form parameters - no change from present state
For Example:
Assume you want to adjust the pan/tilt positions of Group 4, which is currently in Focus
Palette 7.
Step 1: Enter Highlight mode - Press {Highlight} [Enter].
Step 1: Select group 4 - [Group] [4] [Enter].
Step 2: Press [Next] to select the first channel only.
Step 3: Adjust pan/tilt as desired.
Step 4: Press [Next] to advance to the next channel.
Step 5: Continue these steps until all channels have been modified as necessary. Either of
these adjusted pan/tilt positions to a new focus palette or update the current focus
palette.
Step 6: Press {Highlight} [Enter] to remove the highlight state.
Ion can be placed in Lowlight mode by pressing {Highlight} {Highlight} [Enter]. The default
settings for lowlight are the same as highlight.
You may assign both a highlight and a lowlight preset in setup (see {Manual Control}, page 101).
Any preset may be used. Channels/parameters that are not included in the presets assigned to
Highlight and Lowlight will continue to use their default highlight values (see above).
Highlight/Lowlight Rem Dim
In addition to the highlight/lowlight preset, there is also a setting for {Highlight Rem Dim} in setup.
When enabled and highlight/lowlight mode is active, the intensity for all non-selected channels are
automatically set to the Rem Dim value established in setup, if that Rem Dim value is lower than the
channel’s current intensity. This can be used to help further isolate the channels you are working
with in Highlight/Lowlight Mode
If you do not wish to enable Rem Dim globally in setup, you can specify a rem dim on the command
line for temporary use.
• {Highlight} [Rem Dim] [Enter]
8 Basic Manual Control 125

Sneak
The [Sneak] command (when a destination is not provided) removes manual changes from
selected channels and allows the channels to sneak back to their background states (cue or
submaster instruction, if any). For Expression users, this is similar to Release.
If there is no background state from the playbacks, the channel parameters will be set to their home
position. The sneak command follows the sneak timing default established in Setup (see Setup -
{Manual Control}, page 101), unless a timing value is provided as part of the sneak command.
The sneak command can also be used to send a channel parameter to a specific destination, either
with or without timing. The following examples illustrate the various methods of using the sneak
command:
• [channel list] [Sneak] [Enter] - releases manual control, setting parameters to their
background state. If there are current values for those parameters from a playback, those are
the values that will be restored. If there are no values from a playback, the parameters are set
to home (or default) position.
• [channel list] [Color] [Sneak] [Enter] - sneaks color of the selected channels to the default
or background state.
• [Sneak] [Enter] - when no channels are selected, restores all channels with manual values
to their background state.
• [Sneak] [Sneak]- puts {AllNPs} [Sneak] on the command line, which sneaks out all nonintensity
parameters. [Sneak][Sneak] is a self-terminating command.
• [Sneak] [3] [Enter] - restores all channels with manual values to their background
state in 3 seconds.
• [Group] [5] [9] [Sneak] [Enter] - selects group 5 and sneaks it to color
palette 9 using default sneak time.
• [Group] [3] [at] [1] [Sneak] [7] [Enter] - selects group 3 and sneaks
it to color palette 1 in 7 seconds.
• [Sub] [4] [At] [5] [0] [Sneak] [2] [Enter] - selects submaster 4 and sneaks it to 50% in 2
seconds.
Note:
When recalling a reference from the direct selects to use with the sneak
command, the sneak command has to be entered before the reference.
• [Chan][1] [Sneak] {Preset 1}- selects channel 1 and sneaks it to preset 1 using default sneak
time.
• [Chan][2][Sneak][2]{Intensity Palette 3} - selects channel 2 and sneaks it to
intensity palette 3 in 2 seconds
Flip
The {Flip} feature is used to invert the pan and tilt values of selected channels to achieve the same
focus position from the opposite yoke position. This allows you to correctly focus a fixture that may
be at the end of its pan or tilt range or to correct a fade that may be moving in an undesired
direction. {Flip} is a softkey in the encoder LCD. To access it, press and hold either the “Pan” or
“Tilt” encoder, then press the corresponding softkey.
The following example illustrates the use of {Flip}:
• [channel list] {Flip}
126 Ion Operations Manual

Channel Check
Channel check allows you to quickly step through all of your patched channels. This is useful for
checking lamps or checking focus.
Note:
The following examples illustrates the how to use the channel check feature:
• [1] [at] [7] {Channel Check} [Enter] - brings channel 1 to 70% intensity
• [Next] - channel 1 returns to its background state and channel 2 is set to 70% intensity.
• [Next] - channel 2 returns to its background state and channel 3 is set to 70% intensity.
For Example:
If the command line currently reads:
• [1] [at] [5] [Enter]
You may still place channel 1 in channel check mode even though the command line is
terminated. Press:
• {Channel Check} [Enter]
Use [Next] or [Last] to progress through the channel list to complete the channel check.
Any other key press other than [Next] or [Last] will terminate channel check mode.
Channel check follows the current flexichannel state
Address at Level
The {Address} softkey in Live is used to send level information directly to an output address.
• {Address} [5] [Full] [Enter] - sets output address 5 to full. It will return to its previous level
once the command line changes.
With {Address} on the command line, you can use the level wheel to adjust the level.
After using the {Address} command, [Next] and [Last] may be used to increment the address
number and set it to the same level. Addresses return to their previous level once the command line
is cleared or [Next] or [Last] is used to increment to the next address.
This feature is useful when you want to perform an address or dimmer check.
Address Check
Address check allows you to quickly step through all of your patched addresses.
Note:
Parked dimmers will not be affected by the channel check feature.
Address check differs from Address at Level because it skips non-intensity
parameters of patched addresses. Since address check follows the current
flexichannel state, it can be used with all channels to identify unpatched channels,
or with flexi-patched to only show the intensity addresses of patched channels.
{Address}[1] [at] [Full]{Check} [Enter] - brings address 1 to full intensity.
Use [Next] or [Last] to progress through the address list to complete the address check. Any key
press other than [Next] or [Last] will terminate address check mode.
8 Basic Manual Control 127

Flash
Using the {Flash} softkey in Live will bring a channel or address to full, and then every other second
the level will move to 15%. That will hold for 1 second, and then the level will return to full. The
channel or address will keep flashing until either the command line is cleared, or [Next]/[Last] is
used to increment to the next channel or address.
[1]{Flash}[Enter] - will bring channel 1 to full, then to 15%.
{Address}[1][0]{Flash}[Enter] - will bring address 10 to full, then to 15%.
Using {Move To}
While technically not a manual control instruction, {Move To} will be very useful when managing
record target data stored from manual control.
{Move To} allows you to take recorded data from one location and move it to another location. For
example:
• [Color Palette] [1] {Move To} [5] [Enter]
• [Preset] [3] {Move To} [8] [Enter]
• [Cue] [9] {Move To} [2] [Enter]
• [Preset] [1] {Move To} [Color Palette] [3] [Enter]
• [Int Palette] [5] {Move To} [Preset] [1] [0] [Enter]
When a {Move To} command is given, data is removed from its current location and moved to its
new location. If the new location already contains data, a confirmation is required by Ion (unless
disabled in Setup). Existing data in the new location will be completely overwritten if a {Move To}
command is confirmed.
The {Move To} softkey appears when a record target type (cue, preset, palette) is indicated on the
command line. Some targets (macros, groups, effects) only have the {Move To} option when
viewing in the blind list view. You can also hit [Copy To] [Copy To] to access {Move To}.
When using {Move To} to convert a preset into a palette, all information not relevant for that palette
will be removed.
128 Ion Operations Manual

Chapter 9
Storing and Using Presets
Presets are very similar to palettes in that they are collections of data for specific channels to
facilitate cue creation. Presets, however, can collect all data for a given channel (intensity, focus,
color, beam) rather than just one parameter type.
Up to 1000 presets may be stored in Ion using decimals or whole numbers and they can contain
absolute data or a mix of IFCB palettes. Presets can not refer to other presets.
This chapter contains the following sections:
• Storing Presets Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
• Recalling Presets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
• Editing Presets Live. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
• Editing Presets in Blind. . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
9 Storing and Using Presets 129

Storing Presets Live
Presets can be recorded live using the keypad or the direct selects. Both [Record] and [Record
Only] can be used to record presets, with or without filters. See “Storing Data with Record Filters”
on page 186.
[Record] will store all channels that are not at their default values, and it will record all information
about those channels, including parameters that are still at default. Therefore presets can contain
all of the same information as a cue, but they have no timing information or cue attributes (such as
follow, delay, or cue overrides). When recorded or rerecorded, presets are automatically recalled on
stage. Presets may be individually labeled and each has an optional notes field.
Storing Presets Using [Record]
The [Record] key will store all parameter data for channels that are not at their default values, as
modified by the filter settings in the CIA. This will store all parameter data that is not default even if
it is not manual data. If filters are used, only the parameters enabled by the filters are stored.
When you record data to a preset live, the channels involved in that preset will then actually be in
that preset.
The following methods can be used to store presets using [Record]:
• [Record] [Preset] [5] [Label] [name] [Enter] - Records all parameter data for all channels not
at default and adds a label to preset 5.
• [Record] [Preset] [Next] [Enter] - Records data to the next sequential preset number.
• [-] [2] [Record] [Preset] [n] [Enter] - stores the preset, withholding the group or channels
specified.
• [Channel list] [Record] [Preset] [6] [Enter] - stores the preset, but only the data for the
channel list supplied.
• [Record] & {Preset 8} - stores the preset to the specified direct select.
Note:
When using selective record, you must specify the channel list to be included (or
excluded as the case may be) as part of the [Record] command. Otherwise, all
parameters of channels with non-default values will be stored in the preset.
You may also use the filters and {Make Null} as additional tools to decide what
data will be stored. For more information on these features see Using Filters.
When you rerecord an existing Preset, a confirmation will be required, unless confirmations have
been disabled in Setup.
130 Ion Operations Manual

Storing Presets using [Record Only]
[Record Only] is a selective record process that stores only manual parameter data. Therefore,
when used to record presets, only manual data for channels will be stored in the preset. As with
[Record], filters and {Make Null} can be used to further modify what information is stored. See
“Storing Data with Record Filters” on page 186.
The following methods can be used to store presets using [Record Only]:
• [Record Only] [Preset] [5] [Label] [name] [Enter] - records manual parameter data for all
channels and adds a label to preset 5.
• [Record Only] [Preset] [Next] [Enter] - records manual data to the next sequential preset
number.
• [-] [3] [Record Only] [Preset] [n] [Enter] - stores the preset, withholding the group or
channels specified.
• [Channel list] [Record Only] [Preset] [6] [Enter] - stores the preset, but only the manual
data for the channel list supplied.
• [Channel list] {Color} [Record Only] [Preset] [7] [Enter] - stores only manual color data for
the specified channels to the preset.
9 Storing and Using Presets 131

Recalling Presets
Channels must be selected when recalling a preset. If a selected channel or parameter has no
value in the preset, it will stay in its current position. If you want to recall all channels in a preset, you
can press [Recall From] [Preset] [x]. Presets on direct selects will grey out if they are not
applicable for the current channel selection.
If you only want to recall certain parameters of the preset, select channels and enter the required
parameters (or those not required, using the [-] key) in the command line (see command examples
below).
When a preset is recalled, parameter changes will follow the manual timing defaults, if enabled. Any
preset which is contributing to live output from Ion is considered to be “active.”
You may recall presets using any of the following methods:
• {Preset 8} - recalls the associated preset data for selected channels.
• [Preset] [2] [Enter] - recalls preset 2 for selected channels.
• [Channel List] [Preset] [2] [Enter] - recalls the preset data for the channels in the selection
list.
• [Channel List] [Color] [Preset] [5] [Enter] - recalls only the color data from the specified
preset for the specified channels.
• [Color] & {Preset 7} - recalls just the color data from the specified preset for selected
channels.
• [Recall From] [Preset] [3] [at] [5] [Enter] - recalls all channels in preset 3, and sets all
intensity values at 50%. The original intensity data is still linked to the preset. If the intensity
change is desired you must update the preset to maintain the change and the link, or make
the data absolute before storing to another record target.
• [Channel List] [Preset] [7] [Enter] [at] [/] [5] [Enter] - recalls preset 7 for selected channels.
Intensity values will be recalled at 50% of their recorded state. The intensity link is maintained.
If the intensity change is desired the user either needs to update the preset to maintain the
change and the link, or make the data absolute before storing to another record target.
• [Recall From] [Preset] [9] [Enter] - selects all channels with data stored in preset 9.
• [1] [Recall From] [Preset] [1] [At] [5] [0] [Enter] - recalls the intensity of channel 1 from
preset 1 at 50% of the stored value. If channel 1 was set to 50 in preset 1, it’s recalled value
would be 25.
132 Ion Operations Manual

Editing Presets Live
There are two ways to edit a preset in Live. You may rerecord the preset or you may use [Update].
Rerecord
Rerecording follows the conventions of [Record] and [Record Only]. The only exception is that a
confirmation is required to actually rerecord the preset.
For Example:
Preset 5 has already been recorded. To rerecord Preset 5, recall the preset:
• [Preset] [5] [Enter]
Adjust parameters as needed. You may also adjust the parameters of previously excluded
channels in order to add them to the preset. When you are done, rerecord the preset.
• [Record] [Preset] [5] [Enter] [Enter]
Update
[Update] is used to record parameter modifications back to a preset. When updating, you must
specify the preset to be updated. You may do this using the keypad or the direct selects.
For the purposes of the following descriptions, assume that there are no active cues on stage.
Updating referenced values while cues are active is covered in Modifying Cues Live, page 165.
For Example:
To update a preset, first recall the preset for any channels you wish to edit.
• [1] [Thru] [5] [Preset] [1] [Enter]
Make required changes to the desired parameters using the keypad or encoders. Once you
have achieved the desired look, update the preset.
• [Update] [Preset] [1] [Enter]
or
• [Update] & {Preset 1}
When updating a preset, only channels that are already in the preset will be updated. You need to
select channels or parameters to force new data into a preset when using [Update].
9 Storing and Using Presets 133

Using the Preset List
The preset list displays all recorded presets. List views only allow you to change attributes; no
editing can be done directly in list view. Pressing the {Edit} softkey takes you to the blind view of the
selected preset, in the last format you used in blind. This will allow you to edit the preset.
You can navigate the preset list using [Next] and [Last].
Opening the Preset List
Blind presets can also be viewed in the preset list and can be accessed in a number of ways.
To view the preset list in blind you may:
• Press [Preset] [Preset]
• Click on Preset List in the Browser>Record Target Lists
Move To
You can move presets within the preset list using the {Move To} softkey. You can also hit [Copy To]
[Copy To] to access {Move To}.
• [3] {Move To} [8] [Enter] [Enter] - moves preset 3 to preset 8. Preset 3 will be
removed from the list. The second [Enter] is not required if you have disabled confirmations
in setup.
You can also move data from a palette to a preset and vice versa. It is important to remember that
when using the {Move To} command that data is removed from its current location and moved to its
new location.
Copy To
You can copy presets within the list to another location in the list using [Copy To].
• [2] [Copy To] [9] [Enter] [Enter] - copies the contents of preset 2 to preset 9.
Preset 2 will remain in the list. The second [Enter] is not required if you have disabled
confirmations in setup.
You can also use [Copy To] from palettes to presets.
134 Ion Operations Manual

Editing Presets in Blind
All presets can be viewed and edited in blind. To open a preset in blind, you can do any of the
following:
• Press [Blind] & [Preset]
• Press [Blind] & {Preset x} - opens to the specific preset
• Press [Preset] [Preset] and then {Edit} when a preset is selected in the list
CAUTION:
You may change the way you view information in the preset list by pressing the [Format] button.
This will cycle the preset list through two different views; spreadsheet and table.
Editing in Table View
Table view shows the data for one preset at a time in a table. Channels are displayed on the Y axis
and parameters are shown along the X axis. Viewing presets in the table is useful if you want to see
data for numerous channels in one specific preset.
To change which preset you are viewing you may use the [Next] or [Last] keys or you may select
the exact preset from the keypad or direct selects. You can make changes to the preset by selecting
channels and altering parameter values. In addition to normal editing functions, you may also use
the following commands in this view: [Copy To], {Make Absolute}, {Make Null}, {Move To}, and
{Replace With}.
Here are some examples of the additional preset editing features you have while editing in table
view:
• [select channels or parameters] [Make Abs] - changes the data for any palette references
within the preset into absolute data that no longer references another record target.
• [select channels or parameters] [Make Null] - removes the data for the specified channel or
parameter from the preset.
• [Preset] [5] {Move To} [Preset] [9] [Enter] - this will move the contents of preset 5 to preset
9. Preset 9 will be created and preset 5 will be deleted.
• [Preset] [1] [Copy To] [5] [Enter] - this will copy the contents of preset 1 to preset
5. You may also copy ranges of presets to new locations.
• [1][Recall From][Preset][1][Enter] - will recall the contents for channel 1 in preset 1.
Note:
.
When editing presets in Blind, changes to presets are automatically stored.
Therefore no update or record command is required.
While editing presets in blind, hitting [Recall From][Recall From] will put [Recall
From][Preset] on the command line.
9 Storing and Using Presets 135

Editing in Spreadsheet View
Spreadsheet view shows a range of presets along the Y axis and channels and channel parameters
along the X axis. Viewing presets in spreadsheet view is useful when you want to compare data
between presets.
You may select a preset from the spreadsheet using the [Next] or [Last] keys to move through the
list or you may select the exact preset from the keypad. You may also select a range of presets to
edit at once. You can make changes to the preset(s) by selecting channels and altering parameter
values. In addition to normal editing functions, you may also use the following commands in this
view: [Copy To], {Make Absolute}, {Make Null}, {Move To}, and {Replace With}.
In addition to the examples given above in table view, here are some examples of the additional
preset editing features you have while editing in spreadsheet view:
• [Preset] [1] [thru] [5] {Move To} [9] [Enter] - this will move presets 1-5 to
presets 9-14 respectively. You do not have to supply the end value for Ion to perform the move.
If presets 9-14 already exist you will be asked to confirm this move.
• [Preset] [1] [Thru] [5] [Enter] {Iris} [5] [0] {Replace With} [2] [5] [Enter] - for presets
1-5, this command will replace any iris parameter values of 50 with values of 25. This range
editing using [Replace With] can only be done in spreadsheet view.
Deleting Presets
You may delete presets in the following ways:
• [Delete] [Preset] [1] [Enter]
• [Delete] [Preset] [1] [Thru] [5] [Enter]
Presets can be deleted from any screen, at any time. A confirmation is required to delete, unless
confirmations have been disabled in Setup.
Removing Channels from a Preset
You can remove specific channels from a preset. This can only be done from blind.
For Example:
Open the preset in blind:
• [Blind] & [Preset]
Select the preset you wish to edit:
• [Preset] [5] [Enter]
Remove channels by pressing:
• [2] [+] [4] [+] [6] [Thru] [9] [At] [Enter]
Or you can remove a specific channel parameter from the preset by pressing:
• [5] [+] [7] {Color} [At] [Enter]
You may also remove a channel or parameter from a range of presets by pressing:
• [Preset] [1] [Thru] [5] [Enter] [1] {Color} [At] [Enter]
You can remove channels from live by pressing:
• [channel list] [Delete] [Preset] [2] [Enter]
136 Ion Operations Manual

Chapter 10
Storing and Using Palettes
Palettes are building blocks that can be used to create presets, cues and effects. Palettes are a
critical component when using moving lights and can save considerable programming time when
editing show data.
This chapter contains the following sections:
• About Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
• Palette Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
• Storing Palettes Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
• Recalling Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
• Editing Palettes Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
• Editing Palettes in Blind . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
10 Storing and Using Palettes 137

About Palettes
Palettes are referenced data. This means that when included in presets, cues, or effects, changes
to the contents of the palette are propagated into all of the places the palette is stored. Four types
of palettes are available; Intensity, Focus, Color, and Beam.
Ion supports up to 1,000 palettes of each of the four types. Palettes can be recorded as decimal or
whole numbers and are automatically filtered into IFCB categories. Color data cannot be placed in
beam palettes, intensity cannot be included in focus palettes, and so forth. This makes the process
of creating palettes easier, faster and less work. If you need to create a reference that will include
a mix of IFCB information, presets can be used. See “Storing and Using Presets” on page 129.
Palette Types
Intensity Palettes
Intensity palettes can easily be created for use with all channels that have intensity parameter data.
Focus Palettes
Focus palettes can be created for all channels that have pan and tilt functions.
Color Palettes
Color palettes can be created for all channels that have any color parameter data. Color palettes
store any combination of color data, including CMY, RGB, and HS settings, color scrollers and color
wheels.
You will find that [Record Only], filter settings, and selective store commands will be very useful
when storing color palettes.
Beam Palettes
Beam palettes can be created for all channels that have any beam parameter data. It is rare when
storing beam palettes that you will wish to include all of the beam parameters for channels.
Therefore, [Record Only], filters, and selective store commands will be very useful when storing
beam palettes.
138 Ion Operations Manual

Storing Palettes Live
Palettes may be stored in live or blind. There are a variety of methods for determining what data is
stored into a palette but [Record], [Record Only], and using filters are the most common ways.
When [Record] is used, Ion will store the relevant parameter category data (intensity, focus, color
or beam) for all channels that are not currently at their default value.
[Record Only] is a type of selective store that can be used to store only the relevant parameters
that have manual data. Filters and selective storing provide additional methods to control what is
stored into a palette.
Storing Palettes with [Record]
The most common method to create palettes is to store them from Live. Palettes can be numbered
from 0.01 through 1000 and each can be given a label. [Record] will store the relevant current
parameter data for all channels with non-default data for the appropriate palette type, as modified
by the filter settings on the front panel.
For Example:
Assume you want to create a custom color using the color picker (for hue and saturation
data) or the encoders (for CMY data) and store that data to a custom color palette. First you
must select channels.
• [1] [thru] [1] [1] [Enter]
Using the color picker, adjust the hue and saturation levels to the desired look. Or you can
use the encoders to set the desired color using CMY color mixing or the gel picker. When
the color is selected, store the palette.
• [Record] [Color Palette] [4] [Label] [Enter]
Notice that when you recorded the color palette, all of the color data for channels 1 through
11 is displayed in live with the reference “CP 4”. Because [Record] was used, it stored all
of the color parameters for those channels.
Note:
[Record] will store the entire parameter category into a palette. [Record Only]
stores just the values you have adjusted manually to the target palette. See
“Storing Palettes with [Record Only]” on page 140.
When a palette is created, the channels and the parameters involved in the record action are
automatically set to the palette reference (“CP 4” in this instance). To view the absolute data for
those channels, press and hold the [Data] key.
The following methods can be used to store palettes using [Record]:
• [Record] {Color Palette 1} - stores all color parameter data to color palette “1” and deposits
it to the first color palette direct select.
• [Record] [Focus Palette] [2] [Label] [Enter] - records focus parameter data for all
channels not at their default state and adds a label to focus palette “2”.
• [Record] [Color Palette] [Next] [Enter] - records data to the next sequential color palette
number.
• [-] [5] [Record] [Beam Palette] [Next] [Label] [Enter] - stores to the next sequential
beam palette, withholding the group or channels specified and adds a label.
10 Storing and Using Palettes 139

Selective Storing Palettes with [Record]
Palettes can also be created using selective storing, which allows you to specify only the channels
and or parameters that you want to store.
The following examples illustrate various methods of selectively storing palettes using [Record]:
• [1] [thru] [3] [Record] [Intensity Palette] [2] [Label] [Enter] - records the intensity
data for selected channels 1 through 3 and adds a label to intensity palette 2.
• [Group] [2] [Record] [Beam Palette] [Next] [Enter] - records the beam parameter data for
Group 2 to the next sequential beam palette number.
• [-] [9] [Record] [Focus Palette] [5] [Enter] - stores the focus data to focus palette 5,
excluding the group or channels specified.
• [1] [Thru] [9] {Iris} {Zoom} [Record] [Beam Palette] [5] [Enter] - stores all zoom and iris
data for channels 1-9 to beam palette 5.
Note:
When using a selective store, you must specify the channel list to be included or
excluded, identified by the [+] [-] modifier, as part of the [Record] command.
Otherwise all channels with appropriate non-default data will be stored in the new
palette.
Also, selective storing is useful when you are doing a “one-time” selective store
action. If you are recording a series of palettes with only specific parameters, it will
save you time to set a record filter (see Using Filters with Palettes, page 141).
Storing Palettes with [Record Only]
[Record Only] is a selective record process that stores only manual parameter data. When used to
record palettes, only the manual parameter data for channels will be stored in the palette. As with
record, filters can further restrict stored data if they are enabled when using [Record Only]. See
“Storing Palettes Live” on page 139.
Note:
If you use [Record Only] to record to an existing palette, the data will be added
to that palette. The original palette will not be completely overwritten. Only manual
changes will be stored to the palette.
It is also possible to [Update] to add specific changes to the record target. See
“Editing Palettes Live” on page 143.
The following methods can be used to selectively store manual parameter data to palettes using
[Record Only]:
• [Record Only] [Color Palette] [2] [Enter]- records only the manual color parameter data to
color palette 2.
• [Record Only] [Beam Palette] [5] [Label] [Enter] - records manual beam
parameter data for all channels and adds a label to beam palette 5.
• [-] [9] [Record Only] [Color Palette] [Next] [Label] [Enter] - stores to the next
sequential color palette, withholding the group or channels specified and adds a label.
• [select channels] [Record Only] [Focus Palette] [2] [Enter] - stores focus palette 2, but only
includes the manual data for the specified channels and parameters.
• [1] [Thru] [9] {Iris} {Zoom} [Record Only] [Beam Palette] [5] [Enter] - stores only manual
zoom and iris data for channels 1-9 to beam palette 5.
140 Ion Operations Manual

Using Filters with Palettes
Filters can be used to modify what data is stored to a palette by a record action. The parameters
that are active or filtered allow those parameters to be stored to record targets.
To filter a parameter:
Step 1: Click the {Filter} button in the top-right corner of the parameter grid in the CIA.
Step 2: In the CIA, click the button for the parameter you wish to store.
Step 3: Click the {Filter} button again to stop filter selection. “Filter On” appears next to the
parameter category label in the CIA.
To determine which parameter is filtered in the category:
Step 1: Click the {Filter} button in the top-right corner of the parameter grid in the CIA. All
actively filtered parameters are highlighted in grey. You may need to click the arrow
button in the grid for that parameter category to page to additional parameters in the
category.
Filters are a toggle state. To remove filters, click {Filter} and then click the highlighted parameter
buttons in the CIA to deactivate the filters.
For more information on filters, see Using Filters, page 183.
10 Storing and Using Palettes 141

Recalling Palettes
Palettes may be recalled from the control keypad or from direct selects. When palettes are recalled,
all data is manual and will display in red. Recalled palettes are applied only to selected channels,
therefore you must select channels before recalling a palette. If a selected channel or parameter
has no stored value in the recalled palette, it remains in its current state. Palettes on direct selects
will grey out if they are not applicable for the current channel selection.
You can select all the channels included in a palette by pressing [Group] [Palette] [x] [Enter]. You
can also recall an entire palette by pressing [Recall From] [Palette] [x] [Enter].
Recalled palettes will appear as manual data for the specified channels. That data will appear as
abbreviations of the palette type (IP3 = Intensity Palette 3, FP8 = Focus Palette 8, and so on), or as
the palette label as defined in the displays settings (see Setup, page 93). To see the numeric values
behind any palette (or other referenced value), press and hold the [Data] key.
When palettes are recalled, channels with stored data in the palette will follow that data according
to manual time settings. Palettes may also be recalled using the sneak feature (with default sneak
time) or a time specified using the [Time] key.
For Example:
Select channels 1 through 8 at intensity level 45 and sneak into color palette 4 over 40
seconds.
• [1] [thru] [8] [at] [4] [5] [Sneak] [4][0] [Color Palette] [4] [Enter]
You will notice channels 1 through 8 intensity and color parameters sneaking to the
required values over a period of 40 seconds.
You may also use groups to recall palettes. For example:
• [Group] [1] [1] [Beam Palette] [5] [Enter]
• [Group] [5] {Color Palette 6}
Palettes may also be recalled from the direct selects which automatically terminates the command
line. To recall only specific parameters of a palette, select channels and the required parameters (or
those not required, using the [-] key) in the command line.
The following are methods that can be used to recall palettes.
• [selected channels] {direct select} - recalls the associated (IFCB) palette data for the selected
channels.
• [selected channels] [Palette] [n] [Enter] - recalls the associated IFCB palette for selected
channels.
• [Channel List] {edge} [Beam Palette] [n] [Enter] - recalls only the edge data from the
specified beam palette for the selected channels.
• [Group] [n] [Palette] [z] [Enter] - recalls all of the data in the palette and applies it to the
selected group.
• [Intensity Palette] [y] [at] [/] [z] [Enter] - recalls the intensity palette for selected channels
and sets all recalled intensity values to a proportioned level of their recorded states.
Note:
The above example breaks the referenced link to the intensity palette. To maintain
the link, the palette must be recalled without a modified intensity value. Calling
back the intensity palette at full will also break this link.
When recalling palettes, only channels that are selected at the point of recall will be affected by the
palette recall. The data recalled from a palette is referenced. To break the reference you may use
{Make Absolute}.
142 Ion Operations Manual

Editing Palettes Live
Note:
Rerecord
Rerecording follows the conventions illustrated in the [Record] and [Record Only] sections
detailed earlier in this chapter. The only exception is that a confirmation is required to record over
an existing palette.
For Example:
Color palette 4 has already been recorded. To rerecord color palette 4, adjust the
parameter values as needed (you may also adjust the parameters of previously excluded
channels in order to add them to palette) then rerecord the palette.
• [Record] [Color Palette] [4] [Enter] [Enter]
Update
If a palette is already recorded, [Record] replaces all existing data. [Record Only]
is a selective store, therefore it adds data. Recording over a previously existing
palette requires a confirmation, if confirmations are enabled in the setup menu.
It is also possible to [Update] to add manual changes to the record target.
Live changes can be updated to both active and inactive palettes. When updating a parameter in an
active palette, that parameter will no longer be absolute data, but will now be in the updated palette
on stage.
The following illustrates how to update color palette 2 when no cues are active and you have
recalled channels within that palette.
• [Update] [Color Palette] [2] [Enter] - any manual changes for channels
originally in the palette are updated in color palette 2.
• [1] [Update] [Color Palette] [2] [Enter] - adds channel 1’s manual data to color palette 2.
• [-] [3] [Update] {Color Palette 2} [Enter] - withholds manual changes for channel 3 from the
update to Color Palette 2 using the direct selects.
If a channel or parameter does not have data in the palette being updated, it will not be added to
that palette unless the user specifically requests it by specifying the channel.
10 Storing and Using Palettes 143

Editing Palettes in Blind
CAUTION:
Palettes can be viewed and edited in blind in the table and spreadsheet views.
Entering Blind Palette from Live
• [Blind] & [Palette] - pressing this will display the first recorded palette of the selected type
(Intensity, Focus, Color or Beam) in blind or return to the last palette of this type viewed in
blind.
• [Blind] {Palette Select 1} or [Blind] [Palette] [1] [Enter] - pressing this will display the
specified palette “1” in blind.
• [Palette] [Palette] {Edit} - opens the list view of the palette type and then opens blind palette.
View palettes from blind
While in any blind mode, when no channels are selected, you can enter a palette from the
command line or direct selects. This will take you into blind channel mode for that palette.
• [Color Palette] [n] [Enter]
You may also cycle through the available palettes using [Next] and [Last].
Editing in Blind
The following are representative methods used for editing palettes in blind:
• [2] {Iris} [At] [Enter] - removes the current parameter category setting from channel 2.
• [1] {Iris} [5] [0] [Enter] - selects channel 1 and sets iris value to 50.
• [2] [Copy To] [5] [Enter]- copies the information from channel 2 to channel 5.
• [6] [Recall From] [Focus Palette] [1] [Enter] - recalls the values for channel 6 from Focus
Palette 1.
You may use the encoders to set blind levels as well.
When editing in blind, it is possible to remove an instruction from any palette by selecting the
channel and parameter and pressing [At] [Enter] or {Make Null} [Enter].
[Recall From], [Copy To], {Replace With}, and {Move To} may be used to create and edit palette
data. See Advanced Manual Control, page 195.
Note:
.
When editing palettes in blind, changes to palettes are automatic, therefore no
update or record command is required.
While editing palettes in blind, hitting [Recall From][Recall From] will put [Recall
From][Palette] on the command line.
144 Ion Operations Manual

Editing Palettes in Spreadsheet View
Spreadsheet view shows a range of palettes along the Y axis and channels and channel
parameters along the X axis. Viewing palettes in spreadsheet view is useful when you want to
compare data between palettes.
You may select a palette from the spreadsheet using the [Next] or [Last] keys to move through the
list or you may select the exact palette from the keypad. You may also select a range of palettes to
edit at once. You can make changes to the palette(s) by selecting channels and altering parameter
values. In addition to normal editing functions, you may also use the following commands in this
view: [Copy To], {Make Absolute}, {Make Null}, {Move To}, and {Replace With}.
The following are representative methods used for editing palettes in blind spreadsheet:
• [Color Palette] [1] [Thru] [9] [Enter] - selects color palettes 1 through 9.
• [1] {Scroller} {Make Null} [Enter] - sets channel 1 scroller value null in the selected color
palette.
• [1] {Scroller} [4] [Enter] - sets channel 1 scroller value to 40 in the selected color palette.
In addition to the examples given above, here are some examples of the additional palette editing
features you have while editing in spreadsheet view:
• [palette type] [1] [thru] [5] {Move To} [9] [Enter] - this will move
palettes 1-5 to palettes 9-14 respectively. You do not have to supply the end value for Ion to
perform the move.
• [Beam Palette] [1] [Thru] [5] [Enter] {Iris} [5] [0] {Replace With} [2] [5] [Enter] - for
palettes 1-5, this command will replace any iris parameter values of 50 with values of 25. This
range editing using [Replace With] can only be done in spreadsheet view.
10 Storing and Using Palettes 145

Editing Palettes in List View
When you press the specific Intensity, Focus, Color or Beam palette button twice, a list view for the
associated palette type is opened on a new tab (or brings the list view into focus if already open).
You can also open the list view from the browser. See “Using the Browser” on page 29.
From the list view, you can select a palette for editing, which changes focus to blind channel view,
with the specified palette ready for editing. In addition, you can add palettes to your listing and edit
the labels for each palette in the list.
For Example:
In the list view, you can select palettes and relabel or move them.
• [1] [5] [Label] [Enter]
While in the specific palette category list view, the {Move To} and {Edit} softkeys are available for
use.
To move a specific palette to a different location:
• [1] {Move To} [3] [Enter] - moves the contents and label of the specific palette 1 to palette 3.
If palette 3 is already used, you will be asked to confirm that you want to overwrite the existing
recorded palette. You can also hit [Copy To] [Copy To] to access {Move To}.
You can also move data from a preset to a palette and vice versa. It is important to remember that
when using the {Move To} command that data is removed from its current location and moved to its
new location.
To copy a specific palette to a new palette:
• [2] [Copy To] [5] [Enter] - copies the contents of palette 2 to the new palette 5.
You can also use [Copy To] from presets to palettes.
To edit any palette data from the List View:
• [1] [5] {Edit} [Enter] - selects palette number 15 and brings the blind display into focus, with
palette 15 selected for editing. You can use the [Next] and [Last] buttons to access the other
palettes, or select a new palette for editing from the keypad.
146 Ion Operations Manual

Deleting Palettes
To delete color palette 1, press [Delete] [Color Palette] [1] [Enter] [Enter]. When palettes are
deleted, any references in cues will be converted to absolute data.
Removing Channels from a Palette
You can remove specific channels from a palette. This can only be done from blind.
For Example:
Open the palette in blind:
• [Blind] & [Color Palette]
Select the palette you wish to edit:
• [Color Palette] [5] [Enter]
Remove channels by pressing:
• [2] [+] [4] [+] [6] [Thru] [9] [At] [Enter]
You may also remove a channel or parameter from a range of presets by pressing:
• [Beam Palette] [1] [Thru] [5] [Enter] [6] [At] [Enter]
You can remove channels from live by pressing:
• [channel list] [Delete] [Color Palette] [2] [Enter]
10 Storing and Using Palettes 147

148 Ion Operations Manual

Chapter 11
Working with a Single Cue List
When cues are created they are stored in a cue list. By default, recording cues will result in a single
cue list, identified as cue list 1. While other cue lists can be recorded in Ion, this chapter deals
primarily with working in a single cue list. For more information on multiple cue lists, see Working
with Multiple Cue Lists, page 187.
This chapter contains the following sections:
• Basic Cueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
• Recording Cues in Live. . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
• Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
• Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
• Modifying Cues Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
• Recording and Editing Cues from Blind . . . . . . . . . . . . . . .171
• Deleting Cues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
11 Working with a Single Cue List 149

Basic Cueing
A cue is a record target comprised of channels with associated parameter data, discrete (channel
or parameter level) timing, cue timing, and cue attributes (such as preheat, follow or hang
instructions, and so on).
In Setup, you have determined if Ion will operate in a Cue Only or Tracking mode. By default, the
system is set to tracking, therefore this section of the manual primarily addresses working in
tracking mode. It is important to know which mode you are working in, as it impacts how cues are
edited.
• If your console is set in Track mode (default), changes move forward through the cue list until
a block or a move instruction is encountered.
• If your console is set in Cue Only mode, changes to cues have no impact on subsequent cue
data.
Cue Numbering
Cues can be numbered from .01 - 9999.99.
Ion provides you with multiple ways to number your cues. The most common methods are listed
below:
• After pressing record, enter a cue number which can be a whole number (1) or a decimal
number (1.1).
• After pressing record, rather than entering a cue number you may press [Next], which will
automatically number the cue with the next sequential number in the cue list. For example, the
current cue is numbered cue 1.1, pressing [Record] [Next] will automatically number the new
cue 1.2.
• When recording decimal cues, it is not necessary to specify the leading cue number if a
decimal cue has already been recorded. For example, if the current cue is numbered 5.2,
when you enter the next record command, you can just enter [.] [5] to record cue 5.5.
• Whole numbered cue - [Next] increments the next whole numbered cue.
• Tenths numbered cue (.1) - [Next] increments in tenths.
• Hundredths (.01) numbered cue - [Next] increments in tenths.
150 Ion Operations Manual

Recording Cues in Live
When using [Record], all parameters of any lights that have non-default values, either from manual
control, other cues, or submaster playback are stored in the target cue.
Channels that have all default values, meaning they have never been changed, are not included in
the record action, unless you specifically select the channel and press {Make Manual}. Other
possible exclusions are parameters withheld by use of filters, or if the channel parameters have
been filtered (see Using Filters, page 183). You can also select individual parameters of individual
channels (such as Cyan and Iris) and place them in a null state using the {Make Null} button if the
values are not needed in the cue you are recording.
Ion is a tracking console, meaning once something is recorded into the cue list, the cue list will
always contain information about that channel or parameter unless it is nulled, using the {Make
Null} command, or filtered using the parameter filters.
When cues are recorded they are automatically played back and manual values are released,
unless auto playback on record has been disabled in setup. Upon playback, displayed parameter
levels will be color coded for clarification of the record action:
• Blue - intensity has increased from the previous cue or a non-intensity parameter has
changed.
• Green - intensity level has decreased from the previous cue or a non-intensity parameter has
marked.
• Magenta - level has tracked from a previous cue.
• White - level has been blocked (see Block, page 162).
Using Record
When the [Record] button is pressed the keypad defaults to cue mode; use of the [Cue] button is
optional. The following are representative examples of recording cues in Live. Once the cue record
has been specified, cue attributes such as timing can be combined and entered in any order you
wish.
• [Record] [5] [Enter] - records all parameters of any channels with non-default data
into the specified cue number 5.
• [Record] [5] [Label] [name] [Enter] - records the specified cue and provides an
alphanumeric label.
11 Working with a Single Cue List 151

Using Record Only
[Record Only] is similar to [Record] except that it selectively stores only manually set values,
preventing unwanted levels (such as from a submaster or another cue list), from being recorded
into the cue. Therefore, when used to record a cue, only the manual data for channels will be stored
in the cue. Any values in the previous cue that were unchanged will track into the new cue.
All of the same commands used for [Record] may also be used for [Record Only].
• [Record Only] [Next] [Enter] - stores only the manually set values into the next cue
in the list.
• [Record Only] [Cue] [3] [Enter] - stores only the manually set data into cue 3.
• [2] [thru] [8] [Record Only] [9] [Enter] - stores only the manually set data for
channels 2 through 8 into the target cue 9.
• [Group] [2] [Record Only] [Cue] [5] [Enter]- stores only the manual data from group 2 into
cue 5.
• [selected channels] {Color} [Record Only] [4] [Enter] - stores only the color data for
the selected channels into cue 4.
As with [Record], filters can further restrict stored data if deployed when using [Record Only]. See
“Using Filters” on page 183.
152 Ion Operations Manual

Using Selective Store
You may use the [-] button to withhold information from a cue or use the [+] button to specify a
particular channel or parameter to be included in the record action. These actions are both selective
stores.
For information on a selective store using filters see Partial Filters, page 185.
Using a Positive Selective Store
You may record only specified parameters into cues. If the cue has already been stored, this action
adds the specified channel parameters to the existing cue data.
To record only specific channels into a new target cue:
• [1] [thru] [5] [Record] [4] [Enter] - this records only channels 1 through 5 into cue 4.
• [channel list] [Record] [5] [Rem Dim] [Enter] - this will store the selected channels
into the target cue. Any channels active in the previous cue that are not in the selected channel
list will be set to zero in cue 5.
To record only specific parameters into a target cue:
• [1] [thru] [5] [Focus] [Color] [Record] [4] [Enter] - records the focus and color data
for channels 1 through 5 into cue 4. Any other data on stage would not be stored in the target
cue.
Using a selective store for a new record target will track in values from the previous cue that are not
included in the record action.
Using a Negative Selective Store
It is possible to withhold data from a cue by using the [-] key as follows:
• [-] [Group] [3] [thru] [6] [Record] [9] [Enter] - records the specified cue,
with the exception of any channels associated with groups 3 through 6.
• [-] [3] [thru] [6] [Record] [9] [Enter] - records the specified cue, with the exception of
channels 3 through 6.
• [-] [Sub] [7] [Record] [Enter] - records the selected cue, without the input from submaster 7.
• [-] [Sub] [Record] [Enter] - as above, except withholds the contents of all submasters.
• - [Color] [Record] [8] [Enter] - records cue 9 without any color data.
11 Working with a Single Cue List 153

Using [Cue Only / Track]
In Track Mode
When you create a new cue, any unchanged channel parameter data from the previous cue is
tracked into the new specified cue. Any changes in this new cue will also track forward into
subsequent cues until a move instruction is encountered. The [Cue Only/Track] key is an
exception to this behavior. When you record a cue in the middle of an existing cue list, using the
[Cue Only] button will prohibit new information from tracking into the subsequent cue. When you
rerecord or update a cue, the modifications will not track forward.
Note:
With system set to “Track”
• [Record] [5] [Cue Only] [Enter] - records cue 5. New values or changes will not track
into the subsequent cue.
• [-] [Color] [Record] [5] [Cue Only] [Enter] - as above the recorded data will not track
forward and all color data is excluded from the record operation.
• [Record Only] [5] [Cue Only] [Enter] - records all manual data, but doesn’t allow it
to track into subsequent cues.
• [-] [5] [Record] [6] [Cue Only] [Enter] - records the specified cue, except the
contributions from channel 5. The stored data will not track forward in the list.
In Cue Only Mode
In the following examples, the command [Cue Only] indicates the same key hit of
[Cue Only/Track] which is a single button on the keypad. The system setting
determines the actual context of the button depending on the mode in which the
system is operating.
For clarity, only the contextual function of the button is used in the examples.
When you create a new cue, any channel parameter data from the previous cue is tracked into the
new cue. The [Cue Only/Track] key can be used as an applied exception to the cue only/track
system setting.
Note:
In the following examples, the commands [Track] indicate the same key hit of
[Cue Only/Track] which is a single button on the keypad. The system setting
determines the actual context of the button depending on the mode the system is
operating.
For clarity, only the contextual function of the button is used in the examples.
With system set to “Cue Only”
• [Record] [5] [Track] [Enter] - records cue 5. This data will track forward in the list until
the next move instruction or block.
• [-] [5] [Color] [Record] [6] [Track] [Enter] - records the specified cue, except the
color data from channel 5. The data will track forward in the list until the next move instruction
or block.
• [Record Only] [2] [thru] [7] [Track] [Enter] - stores all manual data. The stored data
will track from cue 2 and stop at cue 7.
154 Ion Operations Manual

Timing
Cue timing can be applied in a variety of ways. At a cue level, timing categories are provided for
intensity up, intensity down, focus, color and beam transitions. Each of these times can have an
associated delay. Timing can also be applied directly to a channel or a specific parameter. This is
called discrete timing.
Time can be entered in minutes and seconds (example 10:15), or seconds and tenths of seconds
(example 1.3), or 100ths of seconds (example 1.35) with valid fade times from zero to 99.59. When
no time is applied at a cue level, the defaults established in System Setup are used. See “Setup” on
page 93.
Setting Cue Level Timing
Unless you specify otherwise, Ion assigns default fade times to any cue you record. Default timing
is designated in Setup. Cue level timing can be applied when a cue is recorded or can be added or
modified later.
Following are some examples of record commands with cue level timing:
• [Record] [5] [Time] [9] [Enter] - puts a time of 9 seconds on all parameter timing
categories.
• [Record] [6] [Time] [3] [Time] [9] [Enter] - specifies the intensity up, focus, color, and
beam times at 3 seconds and the down time at 9 seconds. The first instance of [Time] is used
for intensity up fade (meaning intensity value is fading to a higher level than is previously set)
and the second instance of [Time] is used for intensity down fade time (intensity values fading
to a lower level than is previously set).
• [Record] [2] [Time] [Enter] - resets time to default value. If the cue is recorded with
split time, this command only resets the upfade time.
• [Record] [2] [Time] [Time] [Enter] - resets the down intensity time to the default
value.
Note:
Note:
Unless FCB timing is specifically set, it always defaults to the up fade time value.
If a cue is provided split fade times with no delay on either side, and those times
are later the same values, the split time is cleared.
11 Working with a Single Cue List 155

Manual Timing at a Cue Level
It is possible to assign a time of “manual”, for manual parameter transition through the associated
fader. Manual times are assigned by using the {Manual} softkey that is displayed when recording
a cue.
• [Record] [4] [Time] {Manual} [Enter] - applies a manual time. If the cue had
previously been given split times, would apply a manual to the upfade, focus, color, and beam
times. If the cue had a single time, all of the timing would be “manual” and controlled by the
fader.
• [Record] [4] [Time] [Time] [Manual] [Enter] - applies a manual intensity time to the
downfade.
• [Record] [4] {Color} [Time] [Manual] [Enter] - applies a manual time to any color
data changes in cue 4.
Non-intensity Parameter Category Timing
Timing can also be applied for focus, color, and beam parameter categories at a cue level. By
default, FCB timing is the same as intensity upfade time. Once FCB timing is different than intensity
upfade time, those times are no longer affected by intensity upfade changes.
When you apply a time to an individual parameter category and that category has no movement,
the time is displayed in grey. The specified timing will remain in grey until that category is provided
with a move instruction, at which point it the timing will display in white.
• [Record] [2] {Color} [Time] [7] [Enter] - records cue 2 with a cue level color time of 7.
• [Record] [2] {Color} [Time] [Enter] - resets the color time of cue 2 back to the default
value.
• [Record] [2] [Time] [Time] [Time] [7] [Enter] - records cue 2 with a cue level focus
time of 7. In this example, each press of the [Time] key steps through each timing value (up
time, down time, focus time, color time and beam time.
• [Record] [2] [Time] [7] [Enter]- records cue 2 and puts a time of 7 on all parameter
categories (if FCB all had the same times to begin with).
Note:
It is not necessary to rerecord a cue to alter stored timing data. You can simply
redefine the time by specifying the cue and re-entering the time value(s).
• [Cue] [5] [Time] [8] [Enter] - Redefines the all category times to 8
seconds (If FCB all had the same timing).
• [Cue] [2] {Color} [Time] [5] [Enter] - Redefines color time to 5
seconds.
• [Cue] [3] {Focus} [Time] [-] [2] [Enter] - Removes 2 seconds from
the current time.
• [Cue] [7] {Beam} [Time] [+] [3] [Enter] - Adds 3 seconds to the
current time.
156 Ion Operations Manual

Delay Time
Delay is used to stage the execution of parameter categories within a cue or cue part. The
countdown of a delay time begins the moment the cue is executed (for example, pressing [Go]).
Delay times can be added to any cue or to any specific parameter category within the cue, which
will postpone the parameter transition until the delay time has elapsed.
Following are some examples of recording with a delay:
• [Record] [2] [Delay] [5] [Enter] - stores cue 2 with a 5 second delay on intensity.
• [Record] [2] [Time] [9] [Delay] [3] [Enter] - records cue 2 with a 9 second upfade,
delayed from Go by 3 seconds.
• [Record] [2] [Time] [7] [Delay] [Enter] - records cue 2 with a 7 second upfade, and
removes a delay time on the upfade.
Delay can be useful when you do not want a parameter to change (i.e. intensity down) until other
changes have begun or completed their transition. Delay can be used to affect only the parameters
in the specified category.
• [Record] [2] [Color] [Delay] [8] [Enter] - records cue 2 with a delay time of 8 seconds
for the color category.
11 Working with a Single Cue List 157

Discrete Channel or Parameter Timing
Discrete timing can be applied to a specific channel or parameter. You must select the channels that
you want to apply the time to, otherwise the system assumes you are addressing the selected cue.
Following are some examples of use:
• [channel list] [Color] [Time] [3] [Enter] - adds a time of 3 seconds to all of the color
parameters of the channel list that have a move instruction.
• [Frost] [Time] [7] [Enter] - assigns a time of 7 seconds for the frost attribute of all selected
channels.
• [Select last] [Frost] [Time] [7] [Enter] - selects the last channel selection and applies a time
of 7 to any manual frost values.
Discrete delay times can also be placed on a channel parameter.
• [1] {Color} [Time] [4] [Delay] [3] [Enter] - places a time of 4 seconds and a delay of 3
seconds on all color parameters of channel 1.
When timing has been applied to a channel parameter in live, a small red “t” will be displayed with
the channel. This indicates the timing must be stored or updated to the required cue. When this is
done, the “t” is displayed in blue. In the Playback Status Display, a “+” is displayed in the associated
parameter category time field, indicating that not all of the parameters in the cue will use the cue
timing. The [Time] key can be held down to see the discrete delay or time information for channels
in Live/Blind. Delay is displayed first, followed by the timing value.
158 Ion Operations Manual

Assigning Cue Attributes
You can record cues with specific attributes to affect how cues behave when executed. Cue
attributes include follow time, hang time, link, loop, curve, rate and label. Cue attributes can be
entered when the cue is initially recorded, or they can be added or modified at a later date.
Follow/Hang
A follow time creates an auto-follow which automatically activates the next cue in the sequence
when the follow time of the associated cue has elapsed. The follow time begins counting from the
moment the cue is executed.
The hang time is also an auto-follow, but rather than counting from the moment the cue is executed,
it is calculated from the completion of the cue. You can assign a negative value to a hang time,
allowing a subsequent cue to overlap an active cue.
You can assign either a follow time or a hang time, but not both. Both features are accessed using
the [Follow/Hang] key on the console. Following are some examples of use:
• [Record] [5] [Follow/Hang] [8] [Enter] - records cue 5 and provides a “follow” time
of 8 seconds which impacts the start of the next cue in the list. The following cue will
automatically initiate on the same fader when the follow time has elapsed. The follow time will
begin counting down when the associated cue (Cue 5) is executed.
• [Record] [5] [Follow/Hang] [Follow/Hang] [8] [Enter] - records cue 5 and provides
a “hang” time of 8 seconds which impacts the start of the next cue in the cue list. The following
cue will automatically initiate on the same fader when the hang time has elapsed. The hang
time will begin counting down when the associated cue (Cue 5) is complete.
• [Record] [5] [Follow/Hang] [Follow/Hang] [-] [5] [Enter] - records cue 5 and
provides a ‘”hang” time of negative 5 seconds.
To remove a Follow/Hang time:
• [Cue] [x] [Follow/Hang] [Enter]
11 Working with a Single Cue List 159

Link/Loop
Link allows cues to be run out-of-sequence, by causing a different cue number to be loaded into the
pending file of the playback fader when the cue that carries the link instruction is activated. If a
follow or hang time is included with the cue attributes, the activation of the linked cue will occur
when the follow or hang time has elapsed. The link can be within the cue list or to a cue in another
cue list.
Following is an example of using link:
• [Record] [2] {Link/Loop} [8] [Enter] - records the specified cue 2 and
provides a link to cue 8 in the cue list. When cue 2 is played back, the linked cue is loaded into
the pending file of the associated fader.
Loop is provided as a method to link a series of cues and loop them a number of times in a
sequence. Once the sequence of cues has played back the first time, the system recognizes the
loop command and plays the sequence again.
If the first cue in the sequence is a cue with an assert attribute or has move instructions for
channels, values from the last cue are not allowed to track through into the first cue when it is
looped back. But without a move or assert in the first cue, values from the last cue will track into the
first cue when it loops back. A loop specified with “0”, loops the sequence indefinitely.
Following is an example of using loop:
• [Cue] [2] {Link/Loop} [1] {Link/Loop} [3] [Follow] [4] [Enter] - records a link from
cue 2 back to cue 1. Because there is a follow time, cue 1 will automatically trigger 4 seconds
after cue 2. If cue 1 also has follow time, it will automatically trigger cue 2. This sequence will
run 4 times (once plus 3 loops) and then stop in cue 2. The loop value specifies the number
of times the loop instruction will be performed. Since the sequence has run once prior to the
loop command, the total number of passes will be the specified number of loops +1.
160 Ion Operations Manual

Rate
The {Rate} softkey can be used to apply a rate adjustment to all timing in the cue. The default rate
is 100%, which is real time. To slow a cue down, set the rate below 100%, to speed the cue up, set
the rate above 100%. The range rate for a cue is 0 - 2000%. A timing value of 5, with a rate of 50%
will replay in 10 seconds. A timing value of 5, with a rate of 200% will replay in 2.5 seconds.
Following is an example of using rate:
[Record] [4] {Rate} [1] [2] [5] [Enter] - records the specified cue, and places a rate
override instruction on all timing values. The cue would now be played back at 125% of recorded
time values.
Note:
Curve
{Curve} is used to affect the percent completion of a cue or part by applying the curve’s output level
as the percent completion for all fade calculations.
Following is an example of how to assign a curve to a cue:
• [Cue] [6] {Curve} [5] [Enter] - applies curve 5 to cue 6.
When a curve is applied to cue, it impacts only the intensity transitions in that cue. When applied to
a cue part, it impacts any parameters moving in that part. For more information on creating and
using curves see Storing and Using Curves, page 271.
Label
[Label] is used to attach an alphanumeric label to a cue or cue part.
Following is an example of how to apply a label to a cue:
• [Record] [7] [Label] [Enter] - records cue 7 and applies the label as entered
on the alphanumeric keyboard.
Pressing [Label], when a label has already been applied to a cue, will display the label on the
command line for editing. Pressing [Label] a second time will clear the label, or you can press
[Clear] to remove the label one character at a time.
Clearing Cue Attributes
You can use the playback rate override function to determine the rate at which you
want to play the cue back, and then apply that rate to the cue. This eliminates the
need to adjust all of the timing in the cue if you only need to speed it up or slow it
down.
To clear attributes from a cue:
• [Cue] [n] [Follow/Hang] [Enter] - removes the follow or hang time from the specified cue “n”.
• [Cue] [n] [Label] [Label] [Enter] - removes the label from the specified cue “n”.
• [Cue] [n] {Link/Loop} [Enter] - removes the link instruction from the specified cue “n”.
• [Cue] [n] [thru] [y] {Rate} [Enter] - removes the rate instruction in cues “n” through “y”.
You may combine these to remove multiple attributes at once:
• [Cue] [n] [Follow/Hang] {Link/Loop} [Enter] - removes the follow time and link instruction.
11 Working with a Single Cue List 161

Flags
Flags can be applied to cues to change specific behaviors. Flags can be set for “Block”, “Assert”,
“AllFade”, “Mark”, and “Preheat”.
Block
You can apply a block to a cue, a cue part, to any channel (or group of channels), or parameter (or
group of parameters) within a cue. Block is an editing function, it has no impact on how the data is
played back.
At a cue level
A cue level block causes all tracked values in the cue to be treated as move instructions for editing
purposes, which prohibits any data changes from tracking into the cue. Parameters that are not
included in the cue are not impacted by the block instruction.
Blocks do not protect a cue, channel or parameter from being modified by a range edit, nor are they
protected from a trace instruction (see Using Trace, page 170). It is assumed that if you use the
trace instruction, then you really want the initial value to change. A block will stop the trace from
moving any further backwards through the cue list.
Ion also supports an “auto-block” function. Auto-block can protect your cue data from unwanted
changes. For example, in cue 5 you set channel 1 to 50%. It is stored as a move instruction. Then,
you later go back to an earlier cue and set channel 1 to 50% and it tracks forward to cue 5.
Channel 1 will be “auto-blocked” in cue 5. Even though it is now at the same value as the previous
cue, the original concept of a move instruction is maintained.
Blocks that you have applied will display parameter data in white. Auto blocks are displayed in
white, with a white underscore.
• [Cue] [5] [Block] [Enter] - “B” is displayed in the flags field, indicating a cue level block. When
this cue is recalled, all data that would otherwise appear as a tracked value, will be displayed
in white. Any changes upstream in the cue list will not impact this “blocked” cue data.
• [Cue] [6] {Intensity} [Block] [Enter] - “I” is displayed in the flags field, indicating a cue level
intensity block.
At a Channel or Parameter Level
Blocks can also be applied to a channel or a channel parameter. This can be done in live or blind.
When applied in live, the block instruction must be stored or updated to the appropriate cue.
• [9] [Block] [Enter] - applies a block to channel 9. A red “B” appears near the channel in the
live display, indicating a block has been applied but is not yet stored.
• [Group] [5] [Color] [Block] [Enter] - applies a block to all of the color parameters for group 5.
When the block instruction has been stored or updated, any tracked values the block was applied
to will be displayed in white.
Channel level blocks and auto-blocks are indicated in the cue list by a “b”, representing a partial
block.
162 Ion Operations Manual

Assert
Assert is a way to make a tracked or blocked value act as a move instruction on playback. It is often
used in a multiple cue list environments, or to assure that a transition happens in the desired time
See Using Assert, page 189 for more information on asserts in multiple cue lists.
Assert can be useful in a single cue list.
For Example:
Cue 10 is a blackout with a zero count. It is common practice to block blackout cues. Let’s say
though that some of the lights were fading to zero in cue 9. You hit [Go] for cue 10 before cue 9 is
finished. The lights that were fading to zero in cue 9 will continue their downfade in the timing for
cue 9 since cue 10 doesn’t provide them with a new move instruction. If you assert cue 10, the lights
will bump to black as expected.
AllFade
Any cue can have an allfade flag applied. An allfade sends the intensity for all channels not included
in the cue to zero. Submasters, any captured channels and the contribution from any faders that are
set to independent are unaffected, unless the cue executing the allfade is also set to independent.
An allfade flag “*” is identified in the playback status display for the specified cue.
• [5] [Allfade] [Enter] - sends intensity for all channels not included in the allfade cue
to zero.
The allfade instruction is useful as a quick cleanup, to get back to a known state on stage, without
having to worry about what channels need to be set to zero.
Mark
The Mark flag is used to relay information about either automarks or reference marks. When using
automarks, an “M” will display in the flags field for the specific cue that will execute an automark. A
“D” is displayed when automark has been disabled for a cue or a cue part.
When using reference marks, an “M” will display in the flags field for any cue that will execute a
referenced mark. An “R” displays when a cue is the source of a mark. See “Using Mark” on
page 175.
Preheat
Preheat can be used to warm filaments in the cue immediately preceding an intensity upfade from
0. Preheat values can be assigned channels individually in patch (see {Attribute} Display and
Settings, page 70).
Preheat is assigned on a cue (or cue part) basis and, if assigned, any channel in that cue with a
preheat value assigned in patch will fade to that intensity in the cue immediately preceding the cue
with the preheat flag. Cues with a preheat flag will display an “P” in the preheat flag column
(indicated by a “P” at the top of the column).
When a channel is in a preheat state, a “Ph” is displayed in the intensity field of that channel. When
a preheat is executed, the preheat value is established using the upfade time of the associated cue.
It is possible to hold the [Data] key to see the actual preheat values.
11 Working with a Single Cue List 163

Using the Execute List
The execute list can be used to trigger actions on other faders, and to trigger macros. Additionally,
you can enter instructions that sync the “Go” of other cue lists.
When you press {Execute}, a dialog box appears. This provides a list of the available analog
triggers and MIDI triggers. Also, fields are available to enter specific data relating to the macro, cue
number and cue list that you wish to execute.
To trigger a macro:
• [Cue] [1] {Execute} [Macro] [5] [Enter] - triggers Macro 5 when cue 1 is executed.
To trigger cue lists press:
• [Cue] [1] {Execute} {Cue} [4] [/] [6] [/] [Enter]
• [Cue] [1] {Execute} {Cue} [2] [/] [thru] [5] [/] [Enter]
To trigger a specific cue on another fader:
• [Cue] [4] {Execute} [Cue] [4] [/] [5] [Enter]
When cue list triggers are set, the system will automatically execute same numbered cues on the
associated cue list. For example, assume that the last instruction above was applied to cue list 1,
cue 1. When cue 1/1 is executed, any cues numbered “1” in cue list 2 thru 5 will be executed
accordingly. If there is not a cue 1 in those lists, no action is taken on them. If there are cue numbers
on secondary cue lists that are not in cue list 1, those cues are skipped and the subsequent cue
taken as an “out-of-sequence” cue when triggered.
Therefore, it is valuable to create dummy cues in the master cue list if needed, to ensure that no
cues on the secondary cue lists are skipped.
Removing a trigger:
To remove a trigger, access the cue number and press {Execute}, the record target type and press
[Enter].
• [Cue] [5] {Execute} {Cue/Macro} [Enter]
164 Ion Operations Manual

Modifying Cues Live
Recorded cues can be modified live. Cue attributes (such as link, loop, label and so on) may be
edited as well. The cue does not need to be active (played back) to change cue attributes. You may
also change cue attributes for a range of cues if you wish.
Using [At] [Enter]
A useful feature when editing cues is [At] [Enter]. This is a simple feature which allows you to
select any channel or parameter, or several of them, and remove their move instructions, allowing
the value from the previous cue to be manually recalled.
[At] [Enter] is essentially a “recall from the previous cue” command; it completely removes a move
instruction and any manual data, and replaces it with the value from the previous cue.
For Example:
Cue 5 is active in Live.
• [Group] [1] [Focus] [At] [Enter]
This command lifts the current move instructions for Group 1 focus, and recalls the focus
data for those lights from the immediately preceding cue. It is now manual, and can be
stored or updated as required.
You may also use [At] [Enter] to affect only certain channels or parameters by selecting them
specifically:
• [2] [At] [Enter] - this will remove the changes for channel 2 only.
• [2] [Color] [At] [Enter] - this will remove only the color data changes for channel 2.
• [2] [Thru] [5] [+] [9] [+] [1] [1] [Thru] [1] [5] [-] [1] [2] [-] {Zoom} [At] [Enter]- removes
the changes for only the selected channels for all parameters except zoom.
Using Record
You may modify a cue by rerecording it entirely. After making changes to channels or parameters:
• [Record] [Enter] [Enter] - will replace any data in the active cue with the current stage
settings.
• [Record] [Cue] [x] [Enter] [Enter] - will replace the any data in cue “x” with the current
stage values.
Note:
Using [Record] will record all parameters of all non-default channels onstage.
This means that all other cue data and submaster data will be included in the
record action.
This is a common method when working with a single cue list. When working with
multiple cue lists or submasters, [Record Only] is a useful tool.
11 Working with a Single Cue List 165

Using Record Only
Modifying existing cues using [Record Only] is considered a “selective store” function. As such, it
adds or modifies only manual data to the target cue, but leaves any other data that was already in
the cue intact and does not include playback values from other cue lists or submasters. [Record
Only] is a good way to modify existing cues without including contributions from other playbacks in
the cue. In that way, it is very similar to update.
• [Record Only] [Enter] [Enter]- adds the current manual data to the selected cue.
• [Record Only] [Cue] [x] [Enter] [Enter] - adds the current manual data to cue “x”.
Move To
You can use the command {Move To} to move a cue from one location in the cue list to another.
• [Cue] [4] {Move To} [8] [Enter] - moves the contents of cue 4 to cue 8.
Cue 4 is removed entirely. If cue 8 already existed, a confirmation will be required before
replacing cue 8 (unless confirmations have been disabled in setup). Any contents of cue 8 will
be replaced entirely.
166 Ion Operations Manual

[Update]
Update is a powerful feature, and also very versatile. Using a combination of [Cue Only], [Track],
[Trace], and {Make Absolute}, the number of ways you can update specific information and
manual data is virtually endless. Below you will find some examples of how data can be updated to
various record targets either at once, or individually. This list is by no means exhaustive, so you are
encouraged to try methods of updating on your own.
Update Dialogue Box
When you press [Update], a dialogue box will open in the CIA and the following options are
displayed:
• {Update All} - updates the background cue and all references (nested and otherwise). Ion
defaults to this option.
• {Make Absolute} - updates the background cue and convert all levels to absolute values,
thereby removing any references.
• {Break Nested} - updates the background cue’s first level of reference only, thereby breaking
any reference beyond the first. For example, if cue 1 channel 1 references preset 3, which
then references color palette 5, when updated with this option, preset 3 would be updated,
color palette 5 would not, and the reference to CP5 would be broken in preset 3.
The dialogue box also provides you with a listing (by record target) of what channels or parameters
will be impacted by the update instruction. If the channel contains a reference in the cue, it is
indicated. If not, a “+” is displayed. Any channels not owned by the background cue are displayed
as “Unowned” and will therefore be excluded from the update.
Update Dialogue Box
Once you have made a selection from the available options, press [Enter] and the target will be
updated.
11 Working with a Single Cue List 167

Updating to References
When a cue is active, it is possible that various record targets (palettes or presets) will be played
back within that cue. As changes are made to the data in that cue, as well as to the individual
palettes or presets, updating both the cue and references within that cue is simple. When you have
overridden a reference in a cue, the data is displayed in red with a red “R” in superscript next to the
channel’s intensity.
By default, Ion updates any referenced data that was included in the cue.
For Example:
Cue 5 is recalled Live. It contains references to color palette 1 and preset 2. You make
changes to channels included in these record targets. To update both the cue and the
palettes or presets, press:
• [Update] [Enter]
This will automatically take the manual changes and update them to color palette 1 and
preset 2. Therefore cue 5 now references these new values, and the modifications to CP1
and PR2 have propagated through all of the show data.
If you had made changes to other channels that were not included in the palettes or presets
used in cue 5, those values would also be updated to the cue as absolute data.
Updating Without References (Make Absolute)
If you want to record your changes to the cue without updating the references, you may use {Make
Absolute} break the associated to the reference. The {Make Absolute} command can be applied
to the required channels or parameters before the update instruction, or they can be applied during
the update.
• [Update] {Make Absolute} [Enter] - breaks the references for any parameters which have
been changed and update the cue with the changes. The referenced target will no longer be
displayed in the channels which were made absolute. All of the data updated in cue 5 will now
be shown as absolute data.
• [5] [Thru] [9] [Update] {Make Absolute} [Enter] - breaks only the references for channels 5-
9 and record their manual values to the cue. Other manual values will not be included in this
update.
You may also use [Record Only] to break references.
For Example:
Cue 5 is active and onstage. Channels 5-20 are currently referencing preset 1. You make
changes to channels 5-9. The data for these changes is now manual. Press:
• [Record Only] [Enter] [Enter]
If there were other changes on stage, you could have commanded:
• [5] [thru] [9] [Record Only] [Enter] [Enter]
Only the manual data will be recorded as an update to cue 5. The reference to preset 1 for
channels 5-9 is broken and now the cue will display the absolute data rather than the
reference indicator.
Update Break Nested
This is used only when presets that have embedded palette data are modified in a cue. If you wish
to maintain the link to the preset, but not impact the palette that was the source of the preset,
[Update] {Break Nested} can be used.
168 Ion Operations Manual

Using Cue Only/Track
The [Cue Only/Track] key can be used as an applied exception to the cue only/track system
setting. Therefore if the system is set to Cue Only, the key behaves as a [Track] command.
Alternatively, if the system is set to Track, the key behaves as a [Cue Only] button.
For more information on Tracking vs. Cue Only see Tracking vs. Cue Only, page 5 in Setup.
[Cue Only/Track] can be used in conjunction with record or update functions. Following are some
examples of use:
Note:
In the following examples, the commands [Cue Only] and [Track] indicate the
same key hit of [Cue Only/Track] - a single button on the keypad. The system
setting determines the actual context of the button.
For clarity, only the contextual function of the button is used in the examples.
With system set to “Track”
• [Record] [5] [Cue Only] [Enter] [Enter] - rerecords cue 5. This will make the changes
to cue 5 only. The changes will not track forward through the list.
• [-] [Color] [Record] [5] [Cue Only] [Enter] [Enter] - as above, but changes to color
parameters will not be included in the record and all data that was included will not track
forward. Color data in the cue remains unchanged.
• [Update] [5] [Cue Only] [Enter] - updates cue 5 with only those manual parameters
that were receiving their instructions from that cue. The changes will not track forward in the
list. Note that if the data being updated were referenced, this action updates the referenced
target as well.
• [-] [5] [Record] [7] [Cue Only] [Enter] [Enter] - rerecords the specified cue, except
the contributions from channel 5. The changes will not track forward in the list.
With system set to “Cue Only”
• [Record] [5] [Track] [Enter] [Enter] - rerecords cue 5. This will force the changes to
track forward in the list until the next move instruction or block.
• [-] [5] [Color] [Record] [7] [Track] [Enter] [Enter] - rerecords the specified cue,
except the color data from channel 5. The recorded changes will track forward in the list.
• [Update] [3] [thru] [7] [Track] [Enter] - updates cues 3 thru 7. Range updates are
subject to the normal rules of track/cue only in determining impact on subsequent cues.
11 Working with a Single Cue List 169

Using Trace
[Trace] works just as Track does, except it allows changes to be tracked backwards through the
cue list, until it sees a move instruction. A trace will track into, but not beyond, a blocked instruction.
Following are some examples:
• [Update] [5] [Trace] [Enter] -updates cue 5, and tracks changes backward until a
move instruction is encountered. If the system is in track mode, the change will track forward
in the cue list until the next move instruction or block. If in cue only mode, this has no impact
on subsequent cues.
• [Update] [Trace] [Cue Only/Track] [Enter] - updates the selected cue and tracks changes
backward until a move instruction is encountered. If the system is in track mode, the change
is prohibited from tracking forward in the list. If in cue only mode, the change is allowed to track
forward.
Updating the Current Cue
The current cue is updated by simply pressing [Update] [Enter]. When only one cue list is active,
this update will include any changes to all channels.
Updating a Source Cue
To update the source of a level in the current cue (therefore, a move instruction in a prior cue) you
must specify a trace for the desired channel(s).
• [5] [Update] [Trace] [Enter] - updates any manual changes for channel 5 in the current cue.
Any tracked values for channel 5 are traced back to the source of the value (the original move
instruction) and changed to the new value. The value for traced changes in the current cue will
be magenta indicating it is a tracked value.
• [Trace] [Trace] - If a channel was inactive in the cue (either because it had not previously
been used in the cue list, or it was a tracked zero) and is set to a new level, by default the new
level will not track back. You can force it by pressing [Trace] twice.
Updating a Non-Active Cue
It is possible to use the same update commands illustrated above to update inactive cues (cues not
live onstage). In these situations, if the updated cue is not the source of a channel’s live value,
manual data will remain manual. If the updated cue is the source of the current value, the values will
change to magenta (indicating tracked) when the update is completed.
170 Ion Operations Manual

Recording and Editing Cues from Blind
Press [Blind] and the selected cue will be displayed. You can make changes to cues in the blind
display using either the summary, table, or spreadsheet views.
Note:
If changes are made in the blind display to an active cue, these changes will not impact the current
stage state. To make blind changes active you can press [Assert] & {Load} button for the fader
associated with the cue.
Move instructions can be removed from a cue by selecting the channel and pressing [At] [Enter].
This allows all values from the previous cue to track into the current cue. You can also use this
command for specific parameters as well.
For Example:
Suppose you are in blind cue 5 and you make changes to channels 1-5:
• [1] [Thru] [5] [At] [5] [Iris] [3] [5] [Enter]
Intensity goes to 50% and Iris to 35%. You decide to remove the Iris instruction:
• [Iris] [At] [Enter]
The Iris value from the previous cue tracks in. Then you remove the intensity change as
well:
• {Intensity} [At] [Enter]
All values from the previous cue track in.
Instead of using multiple commands, you can, in one command, return the channels to their
values from the previous cue:
• [1] [Thru] [5] [At] [Enter]
The impact of blind edits on subsequent cues is determined by the default setting of Track/Cue Only
mode. Obviously in track mode any changes will track forward until the next move instruction,
unless [Cue only] is pressed. In cue only mode any changes will apply only to the selected cue. If
you want values to track forward, the [Track] button will allow it. The track/cue only instruction must
be applied when a value is entered. [Trace] can also be used to have changes trace back to the
initial move instruction. Such as:
• [1] [Thru] [5] [At] [5] [Cue Only/Track] [Enter]
• {Intensity} [Cue Only/Track] [At] [Enter]
• [1] [Thru] [5] [At] [5] [Cue Only/Track] [Trace] [Enter]
To Live From Blind
Edits in blind take effect immediately. [Record] or [Update] commands are not
required in blind.
From blind, a softkey {Live} is posted when you press [Recall From] or [Copy To] to allow you to
copy to or recall information from live. The following examples only work with the {Live} softkey, not
the [Live] hard key.
• [1] [Recall From] {Live} [Enter]
• [2] [Copy To] {Live} [Enter]
11 Working with a Single Cue List 171

From Summary or Table Views
Use the [Format] key to cycle through the available views (see Using [Format], page 43).
Summary view allows you to see the greatest number of channels at once, though parameter data
is somewhat truncated. Channels with focus, color, or beam data are indicated with a respective F,
C, or B beneath the level data. This view is useful for viewing lots of channel data at once or for
editing primarily intensity values.
Table view grants you greater visibility of parameter data and a reduced number of visible channels.
This view displays channels along the y axis and parameters along the x axis. Parameter
categories are always visible (I, F, C, and B). You can also view specific parameters by pressing
and holding the [Data] button and then pressing the category softkey(s) for the parameters you
wish to view. This will expand the category to show any parameters used in the show. You can also
deselect the parameters you do not wish to see. This is remembered the next time you go to table
view.
The table view is useful for viewing and editing all parameters for a smaller number of channels.
Both summary and table views allow you to make changes to channels or parameters.
From the Cue Spreadsheet
The cue spreadsheet is another useful blind view of cue data. In spreadsheet view, cues are listed
on the y axis and channels and parameters are displayed on the x axis. This view is useful for
viewing a limited number of channels over a span of numerous cues. This makes spreadsheet view
useful for viewing overall trends in channel and parameter data.
Editing cue ranges is possible in spreadsheet view. {Move To} is only available from this view. To
select an entire cue range, you can press [Cue] [enter the first cue] [Thru] [Enter].
172 Ion Operations Manual

Replace With
{Replace With} is used to select channels that have certain specified values and then provide new
instructions for those values.
For Example:
Select a range of cues:
• [Cue] [1] [Thru] [9] [Enter]
Select a range of channels that are used throughout these cues and enter a change
instruction:
• [1] [Thru] [7] [Color Palette] [5] {Replace With} [3]
[Enter]
This instruction finds all instances of channels 1-7 in cues 1-9 that are in color palette 5 and
replace CP5 with CP3. Be aware of the track/cue only settings when using this command.
The range of possibilities of potential {Replace With} commands is virtually endless and can be
applied to single cues or channels, ranges of cues or channels, parameters of any type, or timing
data.
Move To
{Move To} is used to move cues from one location in a cue list to another location in the same or a
different cue list. When cues are moved, values that were tracks or move instructions and now
match the previous cue will be auto-blocked by the system. The impact on subsequent cues is
based on track/cue only settings as described above. Below is an example of {Move To}:
• [Cue] [2] {Move To} [9] [Enter] - the contents of cue 2 moves to cue 9. Cue 2 is
deleted. If cue 9 already existed, a confirmation would be required to overwrite it. You can also
hit [Copy To] [Copy To] to access {Move To}.
In the above example, any tracked values in cue 2 become blocks (see Block, page 162) or moves
in cue 9, as well as any move instructions which now match the previous cue. Cues after cue 9 are
affected based on the default setting of track/cue only. Any values in the cue after cue 2 that tracked
from moves in cue 2 are changed to move instructions.
Ranges of cues can be moved as well. You can also move cues to other cue lists. In either of these
situations if any cue is to be overwritten, a confirmation is required.
Using Encoders in Blind
When a cue is specified, you can select channels and alter parameters using the encoders. [Cue
Only/Track] can be placed on the command line to determine how these changes will impact
subsequent cues.
11 Working with a Single Cue List 173

Deleting Cues
Cues, lists of cues, or ranges of cues can be deleted. When deleting cues, the track/cue only setting
of the console will determine how subsequent cues are affected. The [Cue Only/Track] button can
be used to modify the default behavior as needed.
In Track Mode
When the console is in track mode, deleting a cue also removes any move instructions provided by
the cue. For example, assume you have stored cues 1-10 and cue 5 contains move instructions for
channels 1-5. If cue 5 is deleted, the move instructions are deleted as well and the values from cue
4 will track directly into cue 6 and beyond.
In this instance, if you used the [Cue Only] button in the delete instruction, cue 5 would be deleted,
but the tracked values in cue 6 that originated in cue 5 would remain and be converted to move
instructions.
In Cue Only Mode
When the console is in cue only mode, any subsequent tracked values are not eliminated, but are
converted to move instructions instead.
In the example above, deleting cue 5 (in cue only mode) would result in any tracked values in cue
6, that originated in cue 5, being converted to move instructions.
If you apply the [Track] button to the delete instruction, the move instructions from cue 5 are
deleted and the values from cue 4 would then track into cue 6 and beyond.
Some examples of cue deletion are:
• [Delete] [5] [Enter] [Enter] - deletes cue 5. Subsequent cues in the list are affected
depending on the console default setting as described above.
• [Delete] [6] [Cue Only/Track] [Enter] [Enter] - deletes cue 6, making exception to the
default setting, as described above.
• [Delete] [7] [Part] [1] [Enter] [Enter] - deletes part 1 of cue 7.
• [Delete] [8] [Part] [1] [Thru] [3] [Cue Only/Track] [Enter] [Enter] - deletes parts 1-
3 of cue 8, making exception to the default setting, as described above.
• [Group] [1] [Delete] [2] [Enter] - deletes any channels in group 1 from cue 2. Cue 2
remains in the cue list and any channels not in group 1 are unaffected.
• [Delete] [2] [thru] [8] [Cue Only/Track] [Enter] [Enter] - deletes cues 2-8, making
exception to the default setting, as described above.
174 Ion Operations Manual

Chapter 12
Using Mark
{Mark} is an instruction that automates the process of presetting moving lights to their required
state in a cue, prior to fading intensity up. This allows your moving lights to unobtrusively perform
non-intensity parameter transitions in an inactive (darkened) state.
Ion provides two different methods to mark lights: AutoMark and Referenced Marks.
This chapter contains the following sections:
• AutoMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
• Referenced Marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
12 Using Mark 175

AutoMark
The AutoMark feature is a system default setting and can be turned on or off at a global level. The
system default for this setting is off. To change the default settings see Show Settings, page 95.
When AutoMark is enabled, non-intensity parameter transitions will occur in the cue immediately
preceding the cue in which the changes are stored, if intensity in that cue is moved from zero to any
active level. Therefore, the preceding cue “executes” the AutoMark.
AutoMark information is displayed for cues or cue parts. It is not a channel instruction. AutoMarked
cues are indicated by an “M” in the M column of the playback status display.
AutoMarks will execute using the time of the cue in which the moves occur (the cue indicated by
“M”). The exception to this is if discrete timing is stored with the move instruction, in which case the
discrete time will be used.
Conditions Triggering an AutoMark
The following rules determine which channels AutoMark is applied to and how it is deployed:
• The marked cue must have a move instruction for intensity of moving lights above zero or null.
• The marked cue must have a move instruction for non-intensity parameters of those channels.
• AutoMark will not occur if the channel is receiving an intensity instruction from another source
(such as a submaster or HTP fader).
• AutoMark must be enabled for an AutoMark to occur. AutoMark is based on the current setting
of the default during playback. It does not matter what the setting is at the point of record.
• On a “per channel” basis, an AutoMark does not occur until:
• Any parameter delay time has elapsed and
• The intensity has reached zero and the parameter has completed any previous
movement.
Allowing a Live Move
When AutoMark is “On” it is possible to override it on a per cue (or cue part) basis. The override will
be available through a softkey, “AutoMark Off”. This softkey is not visible when AutoMark is
disabled in default settings.
AutoMark can be disabled on cues or cue parts.
When enabled, the cue that executes the mark will have an “M” in the flags field. If AutoMark is
disabled, allowing a live move, a “D” is displayed in the flags field of the cue or cue part where the
data is stored.
By using AutoMark with multipart cues, it is possible to have some parameters mark and others
move live.
AutoMark and Timing
An AutoMark will happen in the time of the cue in which is moving (the “M” cue), unless the channel
has discrete timing. In which case, the discrete timing will apply to the moves. Discrete timing is
applied in the cue where the move instruction is stored.
176 Ion Operations Manual

Referenced Marks
Referenced marks are user-specified marks that are manually applied to specific channels or
parameters. When AutoMarks are disabled, referenced marks may be used. AutoMark and
Referenced Marks cannot be used simultaneously.
Note:
If you begin programming with AutoMark enabled, and then disable the feature, all
of the AutoMarks in the show are converted to referenced marks.
There are essentially two parts to a successful referenced mark. The first part is the cue with the
mark flag (set by the user). This is the cue in which any non-intensity parameters will change. This
cue is referred to as the marked cue.
The second part is the cue with intensity value for the channels in question. This is referred to as the
source cue. This is also the cue where the non-intensity moves are stored.
In order to use mark properly, you must specify channels to be marked in the source cue. Ion will
not assume all moving lights apply to any given mark.
There are two ways to apply a referenced mark. You can apply a mark flag at a cue level and then
subsequently reference that flag in a later cue, or you can apply a mark in a cue and reference back
to an earlier cue.
Referenced marks are useful because the non-intensity parameter data is stored in the cue that
actually fades the lights up. Therefore, any changes to the non-intensity parameter data is modified
in the source cue. You do not need to worry about changing it in the marked cue.
Setting Referenced Mark Flags
You can apply a mark flag by pressing:
• [Cue] [n] {Mark} [Enter]
This sets a flag (M) on a cue for later marking activity. In subsequent cues, when channels are
marked, they will preset for movement in this cue (unless told to mark elsewhere).
When you are building a cue containing channels that you want to mark, do the following:
• [select channels] {Mark} [Enter]
• Store the cue, following normal procedures. Ion will automatically look backwards in the cue
list for the first mark flag it encounters.
For Example:
Assume you had placed a mark flag on Cue 10 (this is becomes the Marked Cue).
• [Cue] [10] {Mark} [Enter]
Later you store Cue 12 with a mark instruction on channels 1-10 (this becomes the Source
Cue).
• [1] [thru] [10] {Mark} [Enter] - Note that channels 1-10 are displayed with a red
“M” in the upper right corner.
• [Record] [1] [2] [Enter]
Since no specific mark instruction was given to the channels in cue 12, the channels will
mark back to the first “M” encountered in the preceding cues of the cue list, provided that
the intensity for those channels is “out” throughout the duration of the mark.
When Cue 10 is played back, the non-intensity parameters of channels 1-10 will fade to the
values stored in Cue 12. Then in Cue 12, the intensity will fade up on those channels.
12 Using Mark 177

Mark Display Indicators
In the previous example, indications that a mark had been placed are as follows. Cue 10 would be
shown with a mark flag (M) in the cue list. In addition, when cue 10 is played back, channels 1-10
will show a green “MK” in the intensity field, while the non-intensity parameters would show the
source cue number in green “Q12” (the MK in the intensity field is green if, in cue 10, the lights are
fading to zero and then the NPs are marking. If, in cue 10, channels 1-10 were already at zero, a
magenta “MK” will be displayed).
The source cue (cue 12) would include a green “M” next to the intensity level and any non-intensity
parameter values would be displayed in green. Also, in the cue list, cue 12 would have an “R” in the
mark flags field. If a mark has been placed on a cue, but that cue is not yet marking any lights, the
“M” will be represented as “m”. You will also see an “m” if the mark is no longer in tact.
Applying Flags as Channels are Marked
You may also apply a mark flag to a previous cue by doing the following:
• [select channels] {Mark} [Cue] [5] [Enter]
• [Record] [Cue] [8] [Enter]
This would mark cue 5 to perform any non-intensity moves stored in cue 8. The display indicators
for this mark would be the same as shown in the previous example. As long as intensity is at zero
within the cue range, if there are any non-intensity move instructions for these channels between
these two cues, they will be removed.
It is also possible to mark only certain parameters for marked moves, while allowing live moves for
other parameters.
For Example:
If you wanted to mark only focus, and allow all other parameters to transition while the light
is fading up, you can press:
• [1] [thru] [10] [Focus] {Mark} [Enter]
Removing Referenced Marks
Mark is a toggle state. Therefore, the first mark command sets a mark. The second removes it.
To remove a mark flag from a cue, press:
• [Cue] [n] {Mark} [Enter]
To remove a mark from a channel:
• [select channel] {Mark} [Enter]
Note:
If a mark is removed from a channel in live, the corresponding cue must be
updated.
178 Ion Operations Manual

It is also possible to mark to a cue that doesn't exist, and when the mark is stored, Ion will
automatically create the cue to mark to.
For Example:
If cue 2 does not exist yet:
• [select channels] {Mark} [2] [Enter]
The command line will display, “Create Mark Cue?”
• [Enter]
When the cue is stored, the system will automatically create a cue 2 and mark the lights to it.
If a light is marked and that mark is later broken (for example being used by a move instruction
stored in the mark range), Ion will attempt to repair the mark. This is done by automarking in the cue
previous to intensity fading up, if possible. This will be indicated in the cue list by a “*” in the cue
immediately proceeding the “R” cue.
Mark Earliest
The {Earliest} command can be used with {Mark} to mark the channel into the cue after the last
intensity moved from a nonzero level to 0. The mark is stored and behaves exactly as if you had
typed the cue number instead of {Earliest}. This works in blind, or in live if you record afterwards.
For Example:
Cue 2 moves the intensity for channel 1 to 0, Cue 3 thru 4 have no intensity for channel 1,
and Cue 5 has the intensity move to full. From Cue 5:
• [1] {Mark} {Earliest} [Enter]
This will work the same as [1] {Mark} [Cue] [2] [Enter], and will mark from cue 2 to cue 5.
Note:
[Mark] {Earliest} will mark through block cues or blocked intensity moves of 0,
until it finds the earliest intensity move to 0. If the cue immediately before the cue
being marked is the earliest intensity move to 0, it will mark in that cue.
12 Using Mark 179

Mark Symbols
The symbols that appear in the Mark flag include:
• D. . . . . . . . . . . . . . . . . . .AutoMark is disabled.
• R. . . . . . . . . . . . . . . . . . .Indicates a manual reference override. Manual changes have
been made that override a previously stored reference (such
as to a palette or preset). Once recorded, the reference will
be broken. If updated, the referenced target will be updated
as well, unless otherwise instructed.
• M . . . . . . . . . . . . . . . . . .Indicates a mark is placed, but manual, and must be stored.
Is blue when stored.”m” indicates cue is not marking.
• + . . . . . . . . . . . . . . . . . . .Indicates a cue is both a marking and reference cue when
displayed in the mark flag.
• - . . . . . . . . . . . . . . . . . . .Indicates a dark move, a cue that has any non-intensity
parameters moving on channels whose intensity is at 0.
• x . . . . . . . . . . . . . . . . Indicates that a mark has been placed, but the mark has been
broken. If possible, Ion will automark the lights.
180 Ion Operations Manual

Reference Marks and Timing
Movement of non-intensity parameters in conjunction with a mark will adhere to the following timing
rules.
If discrete timing is used for non-intensity parameters:
When channels execute a mark, the moves will use the discrete time(s) assigned to them
in the source cue.
For Example:
A mark is applied to Cue 5, making it the marked cue.
• [Cue] [5] {Mark} [Enter]
Later, channels 1-10 are assigned discrete timing and a mark instruction:
• [1] [thru] [1] [0] {Focus} [Time] [8] {Mark} [Enter]
Then, those channels are recorded into Cue 10:
• [Record] [1] [0] [Enter]
In this instance, when Cue 5 is executed, channels 1-10 will perform their focus parameter
moves in 8 seconds, as specified in Cue 10 (the source cue, which is the source of their
move instruction).
If no discrete timing is used for non-intensity parameters:
When channels execute a mark, the moves will use the time recorded in the marked cue.
For Example:
Cue 5 is recorded with a time of 10 seconds.
• [Record] [5] [Time] [1] [0] [Enter]
A mark is applied to Cue 5 as above.
• [Cue] [5] {Mark} [Enter]
Later, channels 1-10 are assigned a mark instruction and then recorded into Cue 10 with
no discrete timing:
• [1] [thru] [1] [0] {Mark} [Enter]
• [Record] [1] [0] [Enter]
When Cue 5 is executed, channels 1-10 will perform their non-intensity parameter changes
in 10 seconds, as specified in Cue 5 (the marked cue).
12 Using Mark 181

182 Ion Operations Manual

Chapter 13
Using Filters
Filters are used to determine which parameters can be stored to cues, palettes, and presets. The
filter selection tool in the CIA affects record operations as long as the filters are set.
This chapter contains the following sections:
• Record Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
• Storing Data with Record Filters . . . . . . . . . . . . . . . . . . . . .186
13 Using Filters 183

Record Filters
Record filters are used to select specific parameter data to store to record targets. When no filters
are selected, all parameters can be stored, as appropriate to the [Record], [Record Only] and
selective record action used.
Note:
When storing show data, applied filters are highlighted and allow the associated
parameters to be stored in record targets.
When filters are deselected (not highlighted), they prohibit storing the associated
parameters.
There is no difference between having all filters selected and having no filters
selected (default). In either state, all parameters are available for recording.
Record filters are applied from the CIA using the following buttons:
CIA - parameter
buttons
Filter button
Parameter category
buttons
The parameter category buttons can be used to select filters, as follows:
• Intensity (enables recording intensity data)
• Focus (enables recording pan and tilt)
• Color (enables recording color data)
• Beam (enables recording all beam data)
184 Ion Operations Manual

To apply record filters by category:
Step 1: Click {Filters} in the top-right corner of the parameter grid in the CIA. The parameter
buttons change to display filter selection.
Step 2: Click the parameter category button {Intensity/Focus/Color/Beam} for the category
you want to include in the record target. All parameters in that category will be
highlighted and “Filter On” will appear above the softkey.
Step 3: Click {Filters}. The buttons return to their normal appearance.
In subsequent record functions, only the filtered categories will be recorded. You may apply multiple
category filters at once. Remember that applying all filters and no filters yields the same effect.
Partial Filters
If you do not want an entire category to be recorded, you may apply parameter specific filters
(partial filters) instead.
To apply partial filters:
Step 1: Click {Filters} in the top-right corner of the parameter grid in the CIA. The parameter
buttons change to display filter selection.
Step 2: Click the parameter button (for example {Zoom}) for the parameter you want to
include in the record target. That parameter will be highlighted and “Filter On” will
appear above the softkey.
Step 3: Click {Filters}. The buttons return to their normal appearance.
In subsequent record functions, only the filtered parameters will be recorded. You may apply as
many partial filters at once, as you wish. Any unfiltered parameters will not be included in record
actions. In live, unfiltered parameter data is displayed in its proper color, but a grey “n” (indicating
null data) will appear in the upper left corner of the parameter’s field.
Removing Filters
Applying filters is a toggle state. To remove any filter, simply repeat the application process
described above. When pressed again, any applied filter will be removed.
To remove all filters at once:
Step 1: Press and hold [Filters]. The parameter buttons change to display filter selection.
{Clear Filters} appears in the upper left corner of the parameter buttons.
Step 2: Press {Clear Filters}. Any applied filters will be removed and the highlights will turn
off.
Step 3: Release [Filters]. The buttons return to their normal appearance. All parameters are
now available to record functions.
13 Using Filters 185

Storing Data with Record Filters
If a record target is stored with filters in place, the filters allow only associated parameter data to be
recorded in the target. Non-filtered data is not included when you record.
The various record targets are affected by filters in the following ways:
• Palettes - Palettes by definition are already filtered. The color and beam filters can be used
to further modify what is stored in the color and beam palettes, however.
• Presets - Active filter settings impact what is stored in presets.
• Cues - Active filter settings impact what is stored in cues, even when using “record only”
commands.
• [Update] - Filter settings are ignored.
• [Recall From] - Recall from instructions are not affected by the filters.
186 Ion Operations Manual

Chapter 14
Working with Multiple Cue Lists
Ion provides many useful tools to allow you work efficiently and simultaneously with multiple cue
lists. This chapter focuses on the features and methods used when working with more than one cue
list.
This chapter contains the following sections:
• Recording to a New Cue List . . . . . . . . . . . . . . . . . . . . . . . .188
• Using Assert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
• Changing the Active Cue List. . . . . . . . . . . . . . . . . . . . . . . .190
• Using the Cue List Index. . . . . . . . . . . . . . . . . . . . . . . . . . . .192
14 Working with Multiple Cue Lists 187

Recording to a New Cue List
When recording cues, cue list 1 is initially used as the default cue list. Cue list 1 is displayed with
only the cue number. It does not have a lead cue list number or a “/”. To record to another cue list,
that list must be specified. Cues will then be recorded to that cue list until another list is specified,
or until the selected cue is changed in live.
You may record up to 999 cue lists in an Ion show file.
The cue list that you are storing to is always determined by the selected cue, unless you specify a
different cue list. The selected cue is displayed just above the command line on the CIA, and at the
bottom of the live/blind screen.
The selected cue is the last cue that you affected in live. This includes a record, an update or a
playback action such as [Go], [Back], or a [Go To Cue] instruction, or simply changing the timing
on a cue. It is very useful to keep an eye on the selected cue.
Using Record
[Record] will record all parameters of any channels that have non-default values to a specified cue.
To record to a new cue list, press:
• [Record] [2] [/] [5] [Enter] - this will create cue list 2 and will record the data to cue
5 in that cue list.
Any cues recorded after this will automatically record to cue list 2 until another cue list is specified
or the selected cue changes the cue list number.
Using Record Only
[Record Only] can be used to create a new cue list instead of [Record]. [Record Only] stores only
manual data to the specified cue.
To record to a new cue list press:
• [Record Only] [2] [/] [5] [Enter] - this will create cue list 2 and will record all manual
data to cue 5 in that cue list.
The cue list display will change to show only data from cue list 2. Any cues recorded after this will
automatically record to cue list 2 until another cue list is specified or the selected cue changes the
cue list.
Make Manual
This softkey can be used to convert live cue or submaster data into manual values, allowing them
to be included in the [Record Only] operation. Therefore data from other cues or lists can be
selectively converted to manual data and then stored to another cue/list using [Record Only].
For more information on {Make Manual}, see Using {Make Manual}, page 199.
188 Ion Operations Manual

Using Assert
By default, channel parameters only respond to move instructions during playback (see Cue List
Ownership, page 6). The [Assert] function allows tracked or blocked data from a cue to be
replayed, even when another cue list has taken control of that channel or parameter.
Assert can be applied to cues, cue parts, channels, channel parameters, or to entire cue lists.
Asserted channels will play back their tracked and blocked values, regardless of cue list ownership,
when the associated cue is replayed.
At a Cue Level
When applied at a cue level, [Assert] ensures that all data in the cue - both moves and tracks - will
be played back at their stored values.
To place an assert on a cue press:
• [Cue] [x] [/] [y] [Assert] [Enter] - the cue will assert all of its channels upon playback. An “A”
will be displayed in the “A” column of the cue attributes (cue index, playback status, and so
on); indicating the cue has been asserted.
At a Channel Level
When applied at a channel or parameter level, assert ensures that the entire channel or the
specified parameter will be played back at its stored value.
To place an assert on a channel or group of channels:
Step 1: [select channels] [Assert] [Enter] - a red “A” will appear next to all of the channels’
parameters in the live/blind display. This indicates the assert is placed, but not yet
recorded to a cue.
Step 2: [Record] [x] [Enter] - the red “A” turns to blue in the live/blind display,
indicating the assert has been recorded. In the cue x row of the playback status
display or the cue list index, a lower case ‘a’ appears in the “A” column, indicating that
a partial assert is included in cue x.
You may also store this assert using [Update] or you can apply it in blind.
To place an assert on specific parameters:
Step 1: [select channels] {Intensity/Color/Focus/Beam or parameter buttons} [Assert]
[Enter] - places an assert on the specific parameters of the selected channels.
Step 2: [Record] [x] [Enter] - the assert is recorded to cue x. In the cue x row of the
playback status display or cue list index, a lower case “a” appears in the “A” column,
indicating that a partial assert is included in cue x.
Assert is a very useful tool allowing channels that have been seized by other cue lists to be
repossessed by the associated cue list, while still allowing the asserted channel data to be treated
as tracked instructions.
Assert can also be used from the command line to manually replay portions of a cue without having
to replay the entire cue. Assert in this mode can only be used with cues that are currently active.
To place an assert on a portion of a cue:
• [Group] [6] [Assert] [Cue] [4] [Enter] - asserts the instructions for the channels in group 6
in cue 4.
14 Working with Multiple Cue Lists 189

Using AllFade
Allfade is a cue attribute that commands any intensity values on stage that are not provided by the
associated cue to fade to zero intensity when the cue is played. The allfade will adhere to the
downfade time of the associated cue.
This is useful in conjunction with assert, so you can regain control of channels from other cue lists
and fade other channels from that cue list out.
Note:
Channels with tracked values in the associated cue will not fade out in response
to an allfade. These tracked values are part of the associated cue and therefore
will be played back.
To assign an allfade to a cue:
• [Record] [n] [/] [m] [Allfade] [Enter] - records cue n/m as an allfade cue, thereby
forcing any channels not in the cue to fade to zero on playback.
Like many other cue attributes, allfade is a toggle state. To remove the allfade flag, specify the cue
and press [Allfade] [Enter].
Changing the Active Cue List
The active cue list will be displayed in detail on the playback status display. This view is changed by
the following actions:
• Recalling another cue list in the command line - [Cue] [3] [/] [Enter]
• Recording a cue to another cue list - [Record] [3] [/] [8] [Enter]
• Playing back a cue from the fader of another cue list - press [Go] for the associated fader.
190 Ion Operations Manual

Using [Go To Cue] with Multiple Cue Lists
[Go To Cue] defaults to the currently selected cue list. [Go to Cue] is a live function. It can not be
used to change cues in blind. [Go to Cue] instructions can be executed from any operating mode,
without returning to live.
By default, a Go to Cue instruction is an out-of-sequence cue and will follow the rules of such (see
Out-of-Sequence Cues, page 212).
For examples of how to use [Go To Cue] in playback, please see Go To Cue, page 213.
Using Go To Cue 0
[Go To Cue] [0] is a command line instruction that resets all intensity values not owned by another
fader to default, including any manual values that are not an override to another active fader value.
[Go To Cue] [0] [Enter] also resets the selected cue list to the top of the list, with the first cue
pending.
To [Go To Cue] [0] on another cue list, press:
• [Go To Cue] [2] [/] [0] [Enter]
Note:
Captured channels, independent values and values from other faders running a different cue list
are not affected by a [Go To Cue] [0] command.
When [Go To Cue] [0] is executed, any intensity values owned by the associated cue will fade out,
while all non-intensity parameters remain in the current state. A [Go To Cue] [0] instruction does
not impact the input from other programmers using partitioned control, unless the channels or
parameters are shared.
[Go To Cue] [0] & [Load]
You can use the [Go To Cue] [0] button, located with the playback controls, in conjunction with a
fader load button to send a specific cue list to cue 0. This action does not use the command line. On
the desired fader, simply press:
• [Go To Cue 0] & [Load]
Using Go To Cue Out
Ion has an added intensity parameter for LED fixtures, that by manufacturer
default, have only RGB parameters but no intensity parameter. With this added
control, the LED fixture will respond to the [Go To Cue] [0] command.
To reset all parameters to their default state (unless they are controlled by a submaster) and reset
all cue lists that are loaded to faders so that the first cue of each list is pending, press:
• [Go To Cue] [Out] [Enter]
14 Working with Multiple Cue Lists 191

Using the Cue List Index
Stored
cue lists
The cue list index is a blind display list which shows the cue list you are working with, the cue status,
any other stored cue lists and what (if any) faders the lists are loaded onto. All cue attributes can be
edited from the list including whether the cue list is set to independent or not, and if the intensity
values in the cue list will play back as HTP or LTP. While cue attributes can be changed in live or
blind, independent and HTP/LTP settings can only be set in the cue list index.
Open the Cue List Index
You can access the cue list index by pressing [Cue] [Cue], or you can navigate within the browser
to Record Target Lists > Cue List Index and press [Select].
Selected
cue list
Cues in
selected list
List boundary
(to move up or down,
hover mouse here)
The top half of the cue list index displays all stored cues, including cue attributes, for the selected
cue list. The bottom half of the cue list index displays all stored cue lists. The selected cue list is
highlighted.
Using the mouse, you can move the barrier between the stored cue display (top) and the stored list
display (bottom) to increase or decrease the viewing area of either section. Hover the mouse arrow
over the list boundary until it changes to the familiar “move boundary” icon. Then click and drag the
boundary up or down to the desired height.
192 Ion Operations Manual

Cue List Attributes
Cue list attributes determine how the cue list will interact with other playbacks. Cue list attributes
include:
• The cue list number
• Playback
• The cue list label
• Fader proportional or intensity master (I-Master)
• Independent On or Off (default is off)
• Intensity HTP or LTP setting (default is LTP)
• Assert
• External links
When a cue list is loaded to a fader, all attributes of that cue list are in effect. When a new cue list
is loaded, the attributes of that cue list are in effect, and any manually set behavior of the fader
(such as filter states, timing disable, etc.) are maintained.
When the cue list index is in focus, the sofkeys change to {HTP/LTP}, {Independent}, {Assert},
{Solo Mode}, {Fader}, and {Edit}.
HTP/LTP
The {HTP/LTP} softkey is a toggle state between LTP (latest takes precedence) and HTP (highest
takes precedence). For more information on HTP/LTP see HTP vs. LTP, page 7.
All parameters other than intensity are LTP.
Intensity, by default, is also LTP. Cue lists can be set with an HTP intensity override. When a cue list
is set to HTP, intensity values provided by that cue list will override the LTP value (of which there
can be only one), provided the HTP instruction is higher than the LTP value. When a cue from an
HTP cue list is executed, Ion determines if the intensity value when the cue is complete will be
higher than the current setting. If so, the intensity will begin to fade from its current value to the
required value in the incoming cue using the cue's upfade time.
Note that this behavior is relevant only to cues. If an HTP cue is going to provide a higher level than
a submaster value, Ion will wait until the value is matched before assuming control of the intensity.
The following example illustrates the use of the {HTP/LTP} softkey in the cue list index:
• [1] [/] {LTP/HTP} [Enter] - toggles the selected cue list between HTP/LTP behavior.
Independent
The {Independent} softkey sets a cue list to independent. Any channel parameters currently under
the control of an independent playback cannot be changed by other non-independent playbacks or
submasters. Independent status is equally shared between other independent cue lists and
submasters.
The following example illustrates the use of the {Independent} softkey in the cue list index:
• [2] [/] {Independent} [Enter] - toggles the selected cue list between non-independent
and independent mode.
14 Working with Multiple Cue Lists 193

Solo Mode
The {Solo Mode} softkey is useful in multiple programmer situations. {Solo Mode} is used to pull
a cue list out after it has been synced with other lists for editing purposes.
For Example:
Cue List 1 is being used by one programmer and Cue List 2 was programmed by a second
programmer. For the run of the show, the lists are synced so they run together. But if
changes need to be made to Cue List 2 and not affect the playback of Cue List 1, {Solo
Mode} can be used.
• [Cue] [2] [\] {Solo Mode} [Enter] - places Cue List 2 into solo mode.
{Solo Mode} is a toggle state. So if Cue List 2 is already in solo mode, and [Cue] [2] [\] {Solo Mode]
[Enter] is used again, that list will no longer be in solo mode.
Fader type
Faders can be set as Proportional or Intensity Master (I-Master). This affects how cues are recalled
and modified. See “Proportional vs. Intensity Master” on page 257.
Proportional faders, when the slider is set to zero prior to the execution of a cue, will withhold
playback of intensity data until the slider is raised. Intensity data will then be played back
proportionally according to the level of the fader. Once the slider reaches full, the cue is considered
complete and the cue is released from the manual fader. If the slider is at any value other than zero
when the cue is executed, intensity values will play back normally. If the slider is returned toward
zero, intensity in the cue will face to the previous level.
Faders set as Intensity Masters will master the intensity level for cues during playback. Therefore,
intensity masters set below 100% will proportionally limit playback of intensity data relative to the
level that the slider is set. All non-intensity parameters are unaffected by the slider. Once the slider
has reached full, control of intensity is retained. If the slider is moved toward zero, intensity will
proportionally fade toward zero (not the previous state as per proportional faders).
For Example:
The playback fader for cue list 1 is an intensity master and the slider is set at 50%.
When a cue is played back on this fader, intensity values will raise to 50% of their final
values and then stop. As the intensity master is raised/lowered, intensities will increase/
decrease accordingly. Once the slider has reached full, control of intensity is retained.
Move To
The {Move To} softkey is used to move cues from one location in a cue list to another location in the
same or even a different cue list. When cues are moved, values that had tracked will be matched to
the previous cue and will be auto-blocked by the system. The impact on subsequent cues is based
on track/cue only conventions.
The following example illustrates the use of the {Move To} softkey in the cue list index:
• [1] [/] [2] {Move To} [2] [/] [1] [Enter] - moves the selected cue 2 from cue list
1 to the new list 2. When a cue list is moved, any links that referenced the cue list are changed
accordingly.
Alternatively, you could use [Copy To] to copy the content of the cue to another cue or cue list.
Edit
The {Edit} softkey opens a blind channel view of the selected cue and changes focus from the cue
list index. You can change the blind display to spreadsheet or table view by pressing the [Format]
key. You can edit any of the cue attributes for the cue selected in the index, but the cue contents
must be edited in the blind display. See “Recording and Editing Cues from Blind” on page 171.
194 Ion Operations Manual

Chapter 15
Advanced Manual Control
This chapter describes some more advanced features for manual control functions. These features
can save you valuable programming time.
This chapter contains the following sections:
• Using [Copy To] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
• Using [Recall From]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
• Using {Make Null} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
• Using {Make Manual}. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
• Using {Make Absolute} . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
• Using [Capture] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
• Using [Undo] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
15 Advanced Manual Control 195

Using [Copy To]
[Copy To] allows you to copy all data from one channel to another, either within the current working
mode or to a different record target. [Copy To] works much like [Recall From], but in the opposite
direction, [Copy To] forces data to a channel from the selected channel, whereas [Recall From]
pulls it from a channel to the selected channel.
By using the IFCB category buttons or parameter buttons, you may copy subsets of channel data.
Entire cues, cue ranges and cue lists can be copied to other locations. To only copy over intensity
levels, use the {Only Levels} softkey.
When referenced data is copied, if the copy target also has data in the reference that is being
copied, the target will be placed in that reference (such as, CP 1), at its stored values. If the copy
target is not included in the reference, absolute data will be copied to the target, and not the
reference.
Below are some examples of copy commands from record targets. This command is very versatile
and the following list is far from exhaustive:
• [2] [Copy To] [Cue] [5] [Enter] - copies all information for channel 2 to cue 5.
• [2] [Time] [Copy To] [Cue] [5] [Enter] - Copies just the timing data for all parameters of
channel 2 to cue 5.
• [2] [-] [Focus] [8Copy To] [Cue] [5] [Enter] - Copies all parameter data for channel 2, other
than focus, to cue 5.
• [Group] [3] [Copy To] [Preset] [6] [Enter] - copies current information for group 3 to preset 6.
• [3] [Copy to] [6] [Cue] [8] [Enter] - copies the data from channel 3 to channel 6 in cue 8.
• [3] [Copy to] [4] [thru] [9] [Enter] - copies the data from channel 3 to channels 4 thru 9.
• [3] [Copy to] [8] [Cue] [2] [/] [1] [Cue Only/Track] [Enter] - copies the data from channel 3
to channel 8 in cue 2/1 and takes exception to the track/cue only settings in regard to
subsequent cues in cue list 2.
• [Cue] [2] [/] [Copy to] [Cue] [7] [/] [Enter] - copies all of the contents of cue list 2 to cue list 7.
• [Cue] [1] [/] [1] [thru] [1] [0] [Copy To] [Cue] [5] [/] [5] [Enter] - copies cues 1 thru
10 from cue list 1 to cue list 5, starting with cue 5.
• [1] [Copy To] [2] [0] {Only Levels} [Enter] - copies only the parameter information from
channel 1 to channel 20.
196 Ion Operations Manual

Using [Recall From]
[Recall From] is similar to [Copy To], except that it retrieves data from other locations, and can be
used only for a channel list recalling from the same channel list but in a different location (for
example, a cue). [Recall From] is essentially a “copy from” command.
All parameter data for selected channels will be recalled, or by using the IFCB category buttons or
parameter buttons, you may recall subsets of channel data. To only recall only intensity levels, use
the {Only Levels} softkey.
Below are some examples of recall commands from record targets:
• [2] [Recall From] [5] [Enter] - recalls all recorded data from cue 5 for channel 2.
• [2] [-] [Focus] [Recall From] [5] [Enter] - recalls all data for channel 2 from cue 5,
except focus (pan/tilt - XYZ) data.
• [Group] [3] [Color] [Focus] [Recall From] [Preset] [6] [Enter] - recalls the color and focus
information from preset 6 for the channels in group 3. Could also be used with a channel
selection set instead of a group.
• [Group] [3] [Color] [Recall From] [7] [Make Absolute] [Enter] - recalls color data for
group 3 from cue 7 and breaks any references to record targets.
• [2] [Recall From] [Sub] [4] [Enter] - recalls all recorded intensity data from sub 4 for channel
2.
• [Recall From] [Intensity Palette] [1]- recalls all of the values stored in intensity palette 1.
Note:
.
In live or blind, hitting [Recall From][Recall From] will put [Recall From][Cue]
on the command line.
15 Advanced Manual Control 197

Using {Make Null}
The {Make Null} softkey can be used to withhold parameter data from record or update actions in
live, and remove parameter data from record targets in blind. {Make Null} is applied using channel
selection and can impact entire channels, individual parameters, or parameter categories.
In Live
When you apply a {Make Null} instruction to channels or parameters in live, channel data is still
visible onstage, but that data is essentially rendered invisible to record commands. Similar to filters
(see Record Filters, page 184), {Make Null} acts as an “ignore” instruction in live, not a remove
instruction. When channel data is nulled, the values for that data in the live display turn grey and an
“N” appears next to the data field.
{Make Null} differs from park in that you can still manipulate data onstage (through manual control
or through playback) but that data will be unavailable for record actions.
Some examples of using {Make Null} in live are:
• [1] [Thru] [5] {Make Null} [Enter] - converts all parameters of channels 1-5 into null data.
• [2] {Color} {Make Null} [Enter] - changes only color data for channel 2 to null data.
• [9] [Thru] [5] {Pan} {Make Null} [Enter] - changes only the pan data for channels 5-9 to null.
Null instructions are lifted in two different ways. First, as {Make Null} is a toggle state, it is possible
to reselect the channel and parameter followed by {Make Null} [Enter]. This lifts the null state.
Additionally, a Go To Cue instruction will remove the null state.
In Blind
When applied in blind, {Make Null} can be used to mask instructions in a cue after it has already
been stored. A {Make Null} instruction can also be applied to channels or parameters in palettes,
presets, and submasters, thereby removing the data from the target entirely, in the same way that
[At] [Enter] does.
When applied to channels or parameters in cues, {Make Null} doesn’t remove the data from the
cue, it simply makes it unavailable for playback. It has the same effect on move instructions that it
has on tracked values.
Some examples of using {Make Null} in blind are:
• [Color Palette] [1] [Enter] [3] {Magenta} {Make Null} [Enter] - removes all magenta
parameter data for channel 3 from color palette 1.
• [Preset] [5] [Thru] [9] [Enter] {Intensity} {Make Null} [Enter] - removes all intensity data for
all channels in presets 5-9.
• [Cue] [8] [Enter] [2] [Thru] [7] {Make Null} [Enter] - nulls all data for channels 2-7 in cue 8.
• [Cue] [9] [Enter] {Intensity} [Make Null] Enter] - nulls all intensity data for all channels in cue
9.
In the cue scenarios above, {Make Null} differs from using [At] [Enter] in that instead of allowing
values established in previous cues to track in, {Make Null} both restricts the recorded data from
playing back and prevents other values from tracking in. Therefore, if the cue were executed as an
out-of-sequence cue or asserted, no data would play back or track in for any nulled values.
198 Ion Operations Manual

Using {Make Manual}
The {Make Manual} softkey can be used to convert cue or submaster data into manual values,
allowing it to be included in [Record], [Record Only], and [Update] operations.
• [5] {Make Manual} [Enter] - selects channel 5 and makes all of its current parameter settings
manual data.
• [8] {Focus} {Make Manual} [Enter] - selects channel 5 and makes all of its focus data
manual.
• [9] [Thru] [3] {Color} {Intensity} {Make Manual} [Enter] - selects channels 3-9 and makes
their color and intensity values manual.
Using {Make Absolute}
Referenced data can be transformed into absolute data using the {Make Absolute} softkey. This
softkey is available in live or blind. Referenced data is channel or parameter data that is derived
from a palette or preset. {Make Absolute} can be used to leave a parameter unchanged, but break
its palette or preset reference.
The following examples illustrate how to change referenced data into absolute data.
• [4] {Make Absolute} [Enter] - selects channel 4 and makes any referenced data for that
channel absolute data.
• [7] {Color} {Make Absolute} [Enter] - selects channel 7 and makes its color data absolute.
• [3] [thru] [9] {Color} {Intensity} {Make Absolute} [Enter] - selects channels 3-9 and makes
their color and intensity data absolute.
In each of these examples, the channel display will change to show the result of the command.
Wherever the reference was previously indicated (IP, FP, CP, BP, Pr), an absolute value (numerical)
will be seen.
In live, data that is changed to absolute is also made manual, thereby requiring a record or update
instruction if the results are to be maintained.
{Make Absolute} can also be used in conjunction with an update command, allowing a cue to be
updated while also breaking the reference to palettes or presets that were manually modified.
For example, [Update] {Make Absolute} [Enter] will update the active record target. Any manual
values that were modifications to a palette or preset stored in the cue will be updated as absolute
data in the cue. The reference will be discarded.
15 Advanced Manual Control 199

Using [Capture]
Capture is a manual independent state. Any captured channel parameter data will be unaffected by
playback, but will respond to manual control operations.
When channels are selected, [Capture] [Enter] captures all parameters of those channels. They
will remain unavailable for playback or submaster override until they are released from the captured
state. Capture is a toggle state, so to release parameters from a captured state, press [Capture]
[Enter] again.
For Example:
• [1] [Thru] [9] [At] [Full] [Capture] [Enter]
A “C” is displayed next to the captured parameters (intensity) in the channel display. The
selected channels are now captured and are unavailable for playback or submaster
instructions until they are released from capture.
You may also capture specific parameters of a channel using the parameter buttons in the CIA.
For Example:
• [7] [Focus] [Capture] [Enter]
If a group of channels are selected, and some of those channels are captured and some are not,
the first press of [Capture] releases all channels from the captured state and the second press
captures all manual settings for the selected channels.
Uncaptured channels remain at their current values until restored to previous values or a new
instruction is provided. You may restore channels to their background or default state using the
[Sneak] [Enter] feature (see Sneak, page 126). Or you may leave them in a manual state until a
new instruction is received.
It is also possible to “latch” capture on. This will automatically capture all manual changes as they
are made. Pressing [Capture] [Capture] [Enter] automatically captures subsequent manual
changes. The command line will read “Capture Enable * and the Capture LED will illuminate. To
remove the capture latch, press [Capture] [Capture] [Enter] again.
200 Ion Operations Manual

Using [Undo]
Undo is a method to reverse or “undo” certain operations performed in the software.You can use
[Undo] to reverse any command that results in a change to data that would be saved to the show
file or any command that changes manual levels in live. Commands that can be reversed using
[Undo] are:
• Record and update operations
• Delete commands
• Manual level changes
If there are any commands in the command line, pressing [Undo] once clears the command line.
Once the command line is empty, pressing [Undo] will start the undo process.
When [Undo] is pressed from an empty command line, the command history display will open in
the CIA and the most recent completed command is highlighted in gold. If you press [Enter], you
will undo your last command.
You may use the page arrow keys to select multiple commands. When [Enter] is pressed an
advisory is posted. When [Undo] is pressed again, all highlighted commands will be undone and
subsequently removed from the command history. When removing more than one command, a
confirmation is required.
After an Undo has been performed, a {Redo} button will appear in the command history. You may
press this button followed by [Enter] and the last undo will be “redone” to reinstate the removed
commands.
In a multiple user environment, each user is only able to undo the changes that they made. In the
undo command history, the user will only see the commands that they used.
Note:
Command History
Commands to be
undone
Not all commands can be undone including playback actions and manual
attributes placed on channels or encoder actions.
Command histories are kept for each editing session which begins when the console logs on to the
network or when you load a new show file. Each user builds an individual command history, specific
to the commands they have entered.
You can open the command history at any time by pressing {Cmd History}.
Commands that do not affect manual input or record targets (loading a cue, running a cue, or
moving a submaster) are not included in the command history.
15 Advanced Manual Control 201

202 Ion Operations Manual

Chapter 16
Multipart Cues
Cues can be divided into up to 20 parts. This chapter describes the methods used to create and edit
multipart cues.
This chapter contains the following sections:
• Record a Multipart Cue in Live . . . . . . . . . . . . . . . . . . . . . . .204
• Storing a Multipart Cue in Blind . . . . . . . . . . . . . . . . . . . . . .207
16 Multipart Cues 203

About Multipart Cues
Cues can be divided into up to 20 parts. Each part can have its own channels or parameters, levels
and timing information. Multipart cues can be stored in live or blind using the same conventions to
record a standard cue.
There are three basic ways to create a multipart cue. You can build a multipart cue part-by-part in
live, you can break an existing cue into multipart cues in live, or you can break an existing cue apart
in blind.
A channel or parameter can only be provided an instruction once in a multipart cue. For example, it
isn't possible to adjust color for channel 1 in Cue 1 Part 1 and then also provide a different
instruction for channel 1 color in Cue 1 Part 8.
Default part timing is drawn from the cue level timing defaults established in Setup; you may also
assign discrete timing to channels in each part as you would for a single part cue.
Record a Multipart Cue in Live
Storing a multipart cue in live is accomplished in similar fashion to storing a single part cue.
However, rather than storing the entire cue, you select and store just the channels that you want in
each part.
Please note that there are a variety of different ways and different orders to go about creating a
multipart cue. The following examples represent some, but not all, of those ways.
Creating a New Multipart Cue in Live
Build part-by-part
Make desired changes to the stage state. If all of the changes that you have made are to go into a
part, press:
• [Record Only] [Cue] [2] [Part] [1] [Enter]
Continue making changes and storing parts as you go.
Build parts from cue end state
In most instances, you will create the end state of the cue and then break it into parts. To do this,
you use selective storing commands, as follows:
• [channel or parameter selection] [Record] (or [Record Only]) [n] [Part] [a] [Enter]
• [channel or parameter selection] [Record] (or [Record Only]) [Part] [b] [Enter]
Each part can contain its own cue level timing and other attributes. Follow/Hang, Link and Loop,
and Allfade commands can be placed at the cue level only—they cannot be placed on a part. Also,
through the channel selection, you can put channel parameters into different parts.
Part 1 of any multipart cue is where all unassigned move instructions will reside. Therefore, if the
body of the cue (which is the normal behavior) is to be in part 1, you can simply select the channel
or parameter list that you wish to place in parts 2 and higher.
204 Ion Operations Manual

Setting Multipart Cue Attributes
Cue attributes, such as [Time], [Delay], [Block], [Assert], [Label], [Rate], [Mark], and
{AutoMark Off} can be assigned in part cues. They are stored and function exactly as they do in
single part cues.
Cue part attributes can be defined as the parts are recorded, or they can be added after the part has
been created. For example:
• [Record] [Cue] [2] [Part] [1] [Delay] [8] [Enter]
• [Cue] [4] [Part] [3] {Color} [Time] [6] [Enter]
• [Cue] [8] [Part] [9] {AutoMark Off} [Enter]
• [Record Only] [Cue] [5] [Part] [2] [Assert] [Enter]
For more on cue attributes, see Assigning Cue Attributes, page 159.
16 Multipart Cues 205

Using Update in Live
Updating a multipart cue is generally the same process as updating a single part cue, except you
will provide a specific part cue number in the update command.
Various referenced data, such as palettes or presets, can be assigned to build a multipart cue. If
you have made changes to referenced data within a multipart cue, thereby creating manual data,
pressing [Update] [Enter] updates both the multipart cue and any referenced data with the new
levels, as it does with single part cues.
You can update a part of a multipart cue with only selected parameters as well.
For Example:
Assume you have written cue 1, which is a multipart cue and is active. Part 2 includes
channels 1 through 5 referencing intensity palette 2 which is set at 25%. Select channels 1
through 5 and change the intensity value to 21%. The data in live will indicate the new levels
in red, and an “R” is displayed to indicate the reference has been broken.
To update cue 1 part 2, including the new intensity levels, breaking the reference to the
intensity palette, press:
• [1] [Thru] [5] {Make Absolute} [Enter]
• [Update] [Part] [2] [Enter]
To update cue 1 part 2 and the referenced palette with the new levels:
• [1] [Thru] [5] [Intensity] [Update] [Part] [2] [Enter]
For Example:
When cue 2 is active, select channels 1 through 5 and set new levels for the color scrollers.
Update only part 4 of the multipart cue 2 with the new scroller levels.
• [1] [Thru] [5] [Scroller] [Update] [Part] [4] [Enter]
206 Ion Operations Manual

Storing a Multipart Cue in Blind
Note:
Changing a Single Part Cue to a Multipart Cue
When working in blind, more often than not you will be breaking a single part cue into a multipart
cue. It is quite possible to create a new cue in blind and follow the exact same process, except in
addition to pulling channel parameters into parts, you will also be providing them with move
instructions or block commands. It is worth noting that tracked instructions do not belong to any
specific part of a multipart cue.
Select the cue you wish to break apart and specify the first part you wish to create. Part 1 is
generally where the body of the cue resides. Therefore, if you specify any part other than part 1, all
of the move instructions in the cue are placed in part 1.
Begin by selecting any channels that you wish to move into some part other than part 1.
• [1] [Thru] [5] [Part] [2] [Enter]
• [6] [Thru] [1] [0] {Intensity} [Part] [3] [Enter]
• [6] [Thru] [1] [0] {Color} [Part] [4] [Enter] - and so on.
As you create each part, that part is now selected. It is possible to select the channel parameter you
want and press [Part] [Enter] to pull that data into the selected part.
Note:
Edits in blind take effect immediately, they do not require a [Record] or [Update]
command.
When breaking a cue into a multipart cue in blind, the [Part] button is a required
instruction. Channel selection will not automatically assign a channel into a part.
Use of the [Part] key allows you to add only specific channel parameters to the
part. For example:
• [5] [Thru] [9] {Color} [Part] [Enter]
Changing a Multipart Cue to a Standard Cue
To change a multipart cue to a standard cue, delete all of the parts of the cue.
For Example:
Cue 4 is a 3 part cue that include channels 1 through 20. To change cue 4 back to a
standard single cue:
• [Delete] [Part] [1] [Thru] [3] [Enter]
Deleting a Part from a Multipart Cue
When you delete parts of a multipart cue, any move instructions in the deleted part are moved to the
first available part. If you want to delete move instructions out of a cue part, you have to select the
channels and [At] [Enter] or null them.
• [Delete] [1] [Part] [1] [Enter] [Enter]
• [Delete] [6] [Part] [1] [Cue Only/Track] [Enter] [Enter]
• [Delete] [Part] [1] [+] [2] [Enter] [Enter]
• [Delete] [Part] [1] [thru] [3] [Enter] [Enter]
16 Multipart Cues 207

208 Ion Operations Manual

Chapter 17
Cue Playback
Ion has many features that aid in cue playback. The playback section is located on the left side of
the console and includes the master fader pair, grandmaster, load button, and the fader control
button. Virtual faders (see Slider Module, page 30) and the fader wings can also be used in
playback.
This chapter contains the following sections:
• Introduction to Playback. . . . . . . . . . . . . . . . . . . . . . . . . . . .210
• Selected Cue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
• Out-of-Sequence Cues . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
• Assigning Faders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
• Changing Fader Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
• Playback Fader Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . .215
17 Cue Playback 209

Introduction to Playback
Cues may be played back using the master playback fader pair. While any cue list can be loaded to
these faders, the first cue list you record to will automatically load to the master fader pair.
The master playback fader pair is located to the left of the control keypad. The master is a split
cross-fader pair. The two buttons beneath the master fader pair are [Go] and [Stop/Back]. The
[Load] button is located directly above the fader pair and the area of the LCD above it corresponds
as well, displaying the current cue and list active on the master fader.
Playback Controls
.
Load button
Master
fader
pair
Fader
control
button
210 Ion Operations Manual

Selected Cue
The selected cue is always indicated just above the CIA. The selected cue and all of its attributes
are displayed near the bottom of the live/blind display and on the playback status display.
Live / Blind
When working in live, the selected cue is always the last cue you recorded, edited, updated or
played back. When entering blind for cues, the selected cue will be selected and displayed.
Changing the selected cue in blind will cause the playback status display to change as well, (unless
preserve blind cue has been enabled in Setup) allowing you to see all the attributes of the cues
surrounding the selected cue. When you return to live, the selected cue is synchronized to the last
selected cue in that mode.
When in Live or Blind, if you press [Live] or [Blind] respectively, the selected cue will set to the last
executed cue. This cue will appear on the command line.
The attributes of the selected cue (such as timing, attributes, label and external links) are shown at
the bottom of the live/blind display, below the command line.
In Live
To load a new cue to the faders, select the cue on the command line, press [Enter], and then press
[Load]. When the [Go] button is pressed, the activated cue will be the selected cue.
For Example:
Assume cue list 1 is currently loaded to the master fader pair. To load cue 2/1:
• [Cue] [2] [/] [1] [Enter] [Load]
Cue 2/1 will load to the pending file of the master fader pair.
In this example, the last cue executed from cue list 1 is still the active cue, while cue 2/1 is
pending. When [Go] is pressed, 2/1 will be executed.
You can also load cue list 2 by pressing [2] [/] [Enter] [Load]. This will load the first cue of
list 2 into pending.
The selected cue is changed by go, record, or update instructions as well as cue modification or
selecting a cue on the command line. When you execute a cue that has a follow or hang time, the
next cue will become the selected cue when activated.
In Blind
While in blind, changing the selected cue will change the playback status display to show
information surrounding that cue.
CAUTION:
When editing in blind, changes to cues are automatic, therefore no update or
record command is required.
While working in blind mode, cues can be executed in live using [Go], [Back], and [Go to Cue], but
this does not change the cue you are working with in blind.
17 Cue Playback 211

Out-of-Sequence Cues
An out-of-sequence cue is any cue that is played back in one of the following ways:
• Cue is executed using a [Go To Cue] command.
• Cue is executed by a link instruction.
• Cue is loaded into a fader’s pending file.
• Cue is re-executed using [Assert] & [Load] or is asserted from the command line.
Generally, when an out-of-sequence cue is executed, the entire contents of the cue will be played
back (move instructions and tracked values).
For Example:
Cue 1 sets channel 1 to full. That value is tracked forward until cue 10. The programmer
plays back cue 1 on fader 1. Then the programmer sets channel 1's intensity to 50%
manually. If she executes cue 2, channel 1 remains at 50%, as it is a channel parameter
that is not receiving a move instruction from the incoming cue.
However, if she presses [Go to Cue] [5] [Enter] (an out-of-sequence execution), even
though the value for channel 1 in Cue 5 is a tracked value, channel 1 will fade from the
manual value of 50%, to full in the Go-to-cue time.
212 Ion Operations Manual

Go To Cue
[Go to Cue] instructions can be executed from any operating mode. By default, a [Go to Cue]
instruction is an out-of-sequence cue and will follow the rules of such (see Out-of-Sequence Cues
above.
Following are examples of [Go To Cue]:
• [Go To Cue] [5] [Enter] - all parameters with values in cue 5 are faded to those values, even
if they are tracked.
• [Go To Cue] [Next] [Enter] - takes you to the next cue in the active list.
• [Go To Cue] [Last] [Enter] - takes you to the previous cue in the active list.
When a [Go To Cue] instruction is executed, any null states applied with {Make Null} are removed.
To maintain the make null setting, you should use [Capture] for the required channels.
Go To Cue Timing
[Go To Cue] uses go-to-cue timing established in Setup, page 93. You can use a [Go To Cue]
instruction with different timing options as follows:
• [Go To Cue] [2] [Time] [1] [Enter] - this command would take you to cue 2 in 1 second.
• [Go to Cue] [Next] [Time] [3] [Enter] - this command would take you to the next cue in the
selected list in three seconds.
• [Go to Cue] [Last] [Time] [2] [Enter] - this command would take you to the previous cue in
the selected list in two seconds.
• [Go To Cue] [8] [Time] [Enter] - this command would take you to cue 8 using all timing values
stored in cue 8.
Other Go To Cue options
When [Go to Cue] is pressed, the softkeys in the CIA are changed to provide Go to Cue modifiers
to enhance your playback ability.
From these softkeys, you can specify that when going to a cue, only some elements of that cue will
be played back. Specifically you can choose to play back:
• single parameter channels only (conventionals),
• [GoTo Cue] [1] {SingleParam} [Enter]
• multiple parameter channels only (moving lights),
• [GoTo Cue] [2] {MultiParam} [Enter]
• move instructions only,
• [GoTo Cue] [3] {MovesOnly} [Enter]
• use marks,
• [GoTo Cue] [5] {Use Marks} [Enter]
• or you can choose play back a cue and withhold any link (follow, hang, execute instructions)
it may contain.
• [GoTo Cue] [4] {MinusLinks} [Enter]
These can be combined within the command line as well:
• [Go To Cue] [1] {MultiParam} {MovesOnly} [Enter]
17 Cue Playback 213

Slider Module
You can have access to multiple cue lists at once by using the virtual faders (see Slider Module,
page 30) or fader wings. This will give you the ability to run multiple cue lists or submasters from
multiple faders at the same time.
Assigning Faders
Playbacks and submasters can be defined on the fader pages in setup (see Setup, Fader
Configuration, page 96). The location of playbacks and submasters can also be mapped live as the
contents of those targets are stored. Grandmasters must be defined in setup.
If a fader is an empty playback, an empty submaster, or is unmapped, a cue can be loaded to that
location by selecting the cue from the command line and clicking the associated [Load] key. On the
fader wings, the load function is accessed by pressing both buttons associated with the fader. The
fader will then be automatically assigned as a playback, using the lowest unused playback number.
Once a cue list is loaded to a fader, storing to that cue list automatically plays the cue back on the
appropriate fader, when auto playback on record is enabled in Setup.
When a cue list is loaded to a playback, all cue attributes of that cue list are in effect. When a new
cue list is loaded, any fader attributes that can be set as direct action from the facepanel (such as
filters, timing disable, etc.) are maintained. Loading a new cue does not change the manual fader
attributes.
With Auto Playback Enabled
“Auto Playback” is a record function enabled in setup (Setup, page 93), that automatically executes
cues recorded in live on playback faders. When the cue is executed on the playback fader, any
manual parameters involved in the record operation are automatically released to the cue and all
other values stored in the cue are owned by that cue.
When the first cue is stored on Ion, that cue automatically loads on the master fader.
Assigning Playback Faders Manually
To load a new cue into the pending file of a playback fader, when “Auto Playback” is disabled in
setup or when you want to move a cue list to a different fader, first place that cue or list number on
the command line, press [Enter], then click or press the associated [Load] button for the
destination playback fader.
• [Cue] [4] [Enter] [Load] - changes the selected cue and loads it to the associated fader. This
action assumes cue 4 is from the same cue list as is currently selected.
• [Cue] [3] [\] [Enter] [Load] - changes the selected cue list and loads cue list 3 to the
associated fader.
Changing Fader Pages
Ion has 30 pages of ten faders each. When using virtual faders, you can page through the 30
available pages of faders by clicking the desired page in the virtual fader display. Click the arrow
buttons to advance through the page number buttons until you find the desired page. When using
fader wings, holding down [Fader Page] and bump buttons 1-30 (if available) will change to the
appropriate page.
214 Ion Operations Manual

Playback Fader Controls
In Ion, many of the buttons mentioned below exist as softkeys. In order to have access to some of
these keys, press [Fader Control]. The softkeys will change to display the fader control keys. You
may press [More SK] if the green LED is illuminated, to view additional fader control buttons.
Go and Stop/Back
Using [Go]
The [Go] button is used to execute the cue currently in the pending file of the associated fader.
When [Go] is pressed, all parameters assume their required positions in the recorded times, unless
they have been recorded with manual timing.
Using [Stop/Back]
All fader activity can be instantly stopped mid-transition by pressing the [Stop/Back] button for the
required fader. To resume the cue, press the [Go] button. To fade to the previous cue on that fader,
using default “back” timing, press the [Stop/Back] button again from this state.
When a cue on the playback fader is complete, the first press of [Stop/Back] will go back to the
previous cue. Subsequent presses of [Stop/Back] will step backwards sequentially through the
cue list from that point. [Stop/Back] uses default back time as established in Setup. See “Cue
Settings” on page 95. Or you can back into the previous cue using specific timing by pressing:
• [Go to Cue] [Last] [Time] [n] [Enter].
[Go To Cue] [0]
You can use the [Go To Cue] [0] button, located with the playback controls, in conjunction with a
fader load button, to send a specific cue list to cue 0. This action does not use the command line.
To do this:
Step 1: Press [Fader Controls]
Step 2: If necessary, press [More SK] until {Go ToQ 0} is visible in the LCD.
Step 3: Press and release {Go To Cue 0}.
Step 4: Press or click [Load] for the desired fader. The cue list will go to cue 0.
For more information on this action, see Using Go To Cue 0, page 191.
17 Cue Playback 215

Using Manual Control
There are three types of manual control for playbacks:
• Cues can be stored with manual timing. When cues have stored manual timing, the default
behavior of the fader is to control those manual values.
• Cues can be captured for manual intensity control only. This is possible only when the
associated cue has no manual timing values.
• Cues can be manually overridden using the [Man Override] & [Load] feature which captures
all parameter transitions.
In each of these cases, follow time counts down from [Go]. The hang time will be started when the
potentiometer reaches full or when the last parameter reaches its end state from timing, whichever
comes last.
Manual Timing Control
Manual timing can be set for any parameter or group of parameters. The potentiometer is then used
to control the progress of a transition.
For Example:
Assume the active cue contains an instruction to set color at 5 for channel 1.
The pending cue contains an instruction to set channel 1 to color 12 and the color
parameter has a manual time. Press [Go] to activate the cue. Channel 1 color does not
change.
As you move the fader up manually, channel 1 color moves proportionally from color 5 to
color 12. Any parameters with timing will start their moves at the press of [Go] and be
unaffected by the manual control.
To program a channel manual time:
• [1] {Color} [Time] {Manual} [Enter] - assigns a manual time to channel 1. This must be
recorded or updated to a cue.
Manual timing can also be set at a cue level:
• [Record] [Cue] [5] [Time] {Manual} [Enter]
Manual timing can also be set at a cue category level:
• [Record] [Cue] [6] [Color] [Time] {Manual} [Enter]
216 Ion Operations Manual

Manual Intensity Override
An intensity transition may be taken over manually and the transition captured by dropping the
fader down until it reaches the percentage of cue completion (i.e. if the cue is 50% complete, when
the fader is manually dropped to 50%, the intensity transitions will be captured and the intensity
portion of the cue completed by moving the fader manually between 50% and full or anywhere in
between). If the fader is dropped below 50%, the fader will fade all intensity values proportionally
from their captured values to their previous values.
If a fade is captured and the faders are not reset to 100% prior to the next press of the [Go] button,
the fader will automatically reset to 100% upon cue execution. Alternatively, you can set the fader
to 0% before executing the next cue to capture the cue for manual intensity control when the [Go]
button is pressed if the fader is set to proportional control. Intensity control is released from the
fader when the cue is considered complete (when the fader is brought back to 100%). If the fader
is set as an Intensity Master, the intensity control is maintained, even when the cue has completed.
If a pending cue has any manual control properties, you may either preset the fader to zero or, if it
is a virtual fader, the console will automatically set the fader to zero when the [Go] button is
pressed. The master fader pair must be manually set.
Manual intensity override is not possible if there is any manual timing in the cue, as the
potentiometer is already occupied with that control.
Manual Override
Manual override allows the potentiometer of the associated fader to control all parameters in a
transition state on that fader. When [Fader Controls] {Man Override} & [Load] are pressed, all
activity on that fader is frozen.
The potentiometer is used to manually complete the cue transition for all parameters. If the fader is
operating in a paired mode, the left fader controls the intensity upfade and all non-intensity
parameters, while the right fader controls all intensity downfade actions. Manual control override
automatically releases when the cue is complete.
A group of faders can be collected for manual override by pressing or clicking [Man Override] &
[Load] (continue adding faders by clicking the associated [Load] buttons).
17 Cue Playback 217

Using Assert (Playback Button)
Use {Assert} & [Load] for the associated fader to re-run the active cue in that fader, following the
same rules as [Go To Cue]. Assert can be used to regain control of all cue contents, apply a newly
set independent state to the associated fader, or make any changes in blind to an active cue on
stage.
When [Fader Controls] {Assert} & [Load] are used together, the entire contents of the cue are
replayed. You can assert just certain elements of a cue by using the command line.
Following are some examples of asserting elements of a cue from the command line:
• [channel list] [Cue] [5] [Assert] [Enter] - asserts the selected channels with values from cue
5. Note that cue 5 must be active for this command to execute.
• [channel list] [Color] [Cue] [1] [Assert] [Enter] - asserts the color values from cue 1 for the
selected channels.
Using Timing Disable
The {Time Disable} softkey, used with [Fader Controls] and [Load], causes timing data to be
ignored for any cues that are activated on the associated playback fader. When a playback fader is
in timing disable mode, you will notice “TD” in the associated fader display.
To release the playback fader from time disable mode, press [Fader Controls] {Time Disable} &
[Load] again. You can also cut the next cue in by pressing [Timing Disable] & [Go] or the last cue
by pressing [Timing Disable] & [Back].
Using Freeze
{Freeze} can be used to halt all playback activity on any active faders. To activate a freeze for only
a specific fader, press [Fader Controls] {Freeze} & [Load].
There are two ways to remove the freeze command:
• Press {Freeze} & [Load] again for the specific faders to unfreeze the activity.
• Press {Assert} & [Load] or [Go] or [Stop/Back] for the specific faders to resume the activity.
You may freeze and unfreeze cues and effects from the command line.
• [Effect] [2] [Fader Controls] {Freeze} [Enter] - to freeze effect 2. Freezing a specific effect
is different from stopping an effect. Freeze will stop the effect exactly where it is.
• [Effect] [6] [thru] [9] [Fader Controls] {Freeze} [Enter] - to freeze a specified range of
effects.
When an effect is in freeze mode, you can use the same command to unfreeze:
• [Effect] [2] [Fader Controls] {Freeze} [Enter]
• [Effect] [6] [thru] [9] [Fader Controls] {Freeze} [Enter]
218 Ion Operations Manual

Using Stop Effect
The {Stop Effect} softkey can be used to stop all effects from operating on any or all faders, or it
may be used with the control keypad to stop a specific effect.
• To stop all effects on a fader, press [Fader Controls] {Stop Effect} & [Load] of the
associated fader.
• To stop a specific effect regardless of the fader it is operating on, press [Effect] [2] [Fader
Controls] {Stop Effect} [Enter].
When an effect is stopped, all impact of the effect is removed and the stage output is as though the
effect has never been activated.
Release a Fader
To release a fader, thereby clearing all cues from that fader, press [Fader Controls] {Release} &
[Load] for the associated fader. When a fader is unloaded, control is returned to the master fader.
If there are no values for unloaded channels from the master fader, channels are set to default.
Channels return to the master fader using the category level timing of the active cue on that fader.
If the master fader is released, the fader is cleared and any intensity values owned by that fader are
set to zero, any non-intensity parameters remain in their current state.
All fader attributes (timing disable, filters, and so on) are cleared by the release action.
Turning a Fader Off
To turn a fader off, press [Fader Controls] {Off} & [Load] of the associated fader. When a fader is
turned off, the cue list is maintained on that fader, and any values provided by the fader are returned
to the master fader or their background state.
Press {Off} & [Load] again to turn the associated fader back on. The active cue is replayed,
following the rules for assert.
You can turn the fader back on by pressing the Go or Stop/Back button on the fader, or by executing
a [Go to Cue] for the cue list on that fader, provided the cue list is not already active on another
playback.
17 Cue Playback 219

Using Rate Override
To collect a playback fader for rate control, press [Fader Controls] {Rate} & [Load] for the required
fader. When {Rate} is pressed without [Load], it always collects the master fader for rate control. A
subset of faders can be collected by pressing and holding {Rate} while clicking the [Load] button
for the associated faders you would like to add. When no faders are under rate control, pressing
[Rate] collects the master fader for rate override.
Use the rate encoder to adjust the rate dynamically. The default is 100%, which is real time
(example: 5 seconds = 5 seconds). Decrease the percentage to slow the cue down. Setting the rate
to 0% will stop the cue. Increase the percentage to speed up the event.
Following are some examples of rate:
• A 50% decrease rate applied to a 5 second event will play the cue in 10 seconds.
• A 200% increase rate applied to a 5 second event will play the cue in 2.5 seconds.
The top rate adjustment is 2000%. All timing values associated with a cue (including any follow or
hang times) are affected by the rate modification proportionally.
If a cue is complete, any rate adjustment applied affects the cue in the pending file. When that cue
is subsequently activated, the adjusted rate is used to direct timing. Press {Rate} again to rate
control off and reset to 100%
220 Ion Operations Manual

Chapter 18
Using Park
This chapter describes using park functions from both the live and park display.
This chapter contains the following sections:
• Park Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
• Parked Values in Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
• Scaled Parked Values in Live . . . . . . . . . . . . . . . . . . . . . . . .224
• Park Values from the Park Display. . . . . . . . . . . . . . . . . . . .225
18 Using Park 221

Using Park
The park instruction allows you to set a channel or parameter to a specific value and have it remain
at that level on stage (live mode), prohibiting manual control override, cue or submaster playback
modification. Park may also be used to place a scaling instruction on the intensity output of a
channel.
Note:
Parked values are withheld from all record targets, but you can manually set levels for parked
channels and parameters and store those values into record targets. Keep in mind that the values
set and stored in live do not actually output to the system if the parameter is parked.
When channels or parameters are parked, the LED on the [Park] button illuminates and the live
display will indicate “Parked Channels” or “Parked Dimmers” in the top right corner. In addition, any
parked channel or parameter will be indicated with a white channel number and a “P” will be visible
in the channel. When the parked channel or parameter is unparked, it reverts to the level the
console is currently providing, or its default value if there is no current instruction.
Park instructions are not subject to partitioned control. Any programmer or operator may park and
unpark channels or parameters as needed. Parked parameters set by radio focus remotes (RFR)
will automatically unpark when the associated device goes offline.
Channels, parameters and outputs can be parked and unparked from live and from the park display.
Park Display
A parked channel intensity is not impacted by grandmaster or blackout operations.
You can access the park display by pressing [Park] [Park] or [Blind] & [Park]. The park display
shows all parked channels and parameter values on the top half of the screen and all parked
addresses (dimmers) on the bottom half of the screen. Parked channels displayed on the top of the
screen can be displayed in the summary, table, and packed table views seen in the live/blind
display by using the [Format] key.
When a channel intensity is parked, the parked value will be indicated in white text. When a channel
has a non-intensity parameter that is parked, that parameter will also be indicated with white text.
The display also provides detail of which user parked the channel or parameter (when multiple
users are on the system).
When an address is parked, it will appear in the bottom half of the park display. The address, parked
value, affected channels and parameters are indicated.
222 Ion Operations Manual

Parked Values in Live
Channels and parameters may be parked and unparked from the live display. Following are some
examples:
To park a channel, parameter, or group from live:
• [2] [At] [5] [0] [Park] [Enter] - parks channel 2 intensity at 50%
• [2] [Intensity] [Park] [Enter] - parks the intensity of channel 2 at its current value
• [2] [Park] [Enter] - parks all parameters of channel 2 at their current settings
Note:
If a channel list is constructed in which some channels are parked and some are
unparked, [Park] [Enter] will unpark them all. A confirmation will be required.
• [2] [At] [Park] [Enter] - if channel 2 is unparked, this command parks intensity at the current
value. If the intensity for channel 2 is parked, this command unparks intensity.
• [2] [Color Palette] [8] [Park] [Enter] - parks the color for channel 2 in color palette 8.
• [2] [Color] [Park] [Enter] - parks channel 2 color at its current value.
• [Cue] [6] [Park] [Enter] - parks all the channels stored in cue 6 at their levels provided in the
cue.
• [Park] [Enter] - clears all parked channels and scaled park instructions (see Scaled Parked
Values in Live, page 224). A confirm is required. When a channel is unparked, it reverts to the
level the console is currently providing, or its default value if there is no current instruction. A
confirmation will be required.
18 Using Park 223

Scaled Parked Values in Live
A scaled parked value allows the intensity output (only) to be modified proportionally in live. Scaled
park values are ignored when storing a record target. The setting on the display indicates what
should be stored, not the actual scaled value. An example of how to set a scaled parked value in
live includes:
• [3] [At] [/] [1] [2] [5] [Park] [Enter] - sets a scaled value of 125% on channel 3 intensity. In
other words, whenever channel 3 is active, it will be active 25% higher than its current setting.
• [3] [At] [/] [8] [5] [Park] [Enter] - sets a scaled value for channel 3. Whenever channel 3 is
active, it will playback 15% lower than its current setting.
Remove the scaled parked value:
• [3] [At] [/] [Park] [Enter] - unparks a scaled intensity for channel 3.
• [Park] [Enter] - unparks all parked channels.
A channel can have both a scaled parked value and a parked intensity value. Keep in mind that the
parked intensity has priority over (and overrides) scaled park values. A channel can have a parked
value or a scaled park value, but not both.
Parked Addresses in Live
DMX addresses can be parked in Live. When in live, an {Address} softkey exists beneath the CIA.
Below are some examples of parking an address in live:
• {Address} [5] [At] [5] [0] [Park] [Enter] - parks output 5 at 50% intensity.
• {Address} [5] [Park] [Enter] - unparks output 5. A confirmation will be required.
• {Address} [Park] [Enter] - unparks all parked outputs. A confirmation will be required.
224 Ion Operations Manual

Park Values from the Park Display
You can park and unpark channel parameters or addresses from the park display. Open the display
by pressing [Park] [Park] or [Blind] & [Park]. While in this display, it is assumed that you want to
park channels or parameters, therefore the use of the [Park] key is not necessary when parking,
but is required for unparking.
Following are examples for parking channel parameters from the park display:
• [3] [At] [4] [5] [Enter] - parks channel 3 at 45%.
• [3] [Color Palette] [4] [Enter] - parks color for channel 3 at color palette 4.
Following are examples for clearing parked values while in the park display:
• [channel list] [Park] [Enter] - unparks channels in the list.
• [channel list] [At] [Enter] - unparks channels in the list.
Below are examples for parking addresses in the park display:
• {Address} [5] [At] [5] [0] [Enter] - parks address 5 at 50% intensity.
• {Address} [5] [At] [Enter] - unparks address 5.
Parked channels
Parked addresses
18 Using Park 225

226 Ion Operations Manual

Chapter 19
Creating and Using Effects
Effects are a method within Ion to provide dynamic, repetitive action to channels. This chapter
explains the different types of effects, and how to use them.
This chapter contains the following sections:
• About Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
• The Effect List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
• Effect Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
• Step Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
• Absolute Effects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
• Relative Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239
• Program a New Relative Effect. . . . . . . . . . . . . . . . . . . . . . .241
• Apply an Existing Effect . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
• Effects on Submasters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243
19 Creating and Using Effects 227

About Effects
Effects are manual control functions that can be applied to a channel parameter and then included
in cues or submasters. Cues can contain both standard transitions for some channels and
parameters and effects for the same or other channels and parameters.
A single channel parameter cannot have more than one effect applied at any time. However, a
channel may have one effect running on one parameter and another effect running on a different
parameter.
Effects have user defined properties and attributes which are applied to the effects whenever they
are used in cues. Effects also have cue level overrides, which allow you to use an effect in multiple
locations, and modify its size, shape or rate in individual cues.
Within Ion, effects are broken up into three fundamental behavior types; Step, Absolute, and
Relative effects.
The Effect List
At any time you may press [Effect] [Effect] to view the effect list. Any recorded effects will be
displayed here. The effect list is a blind view and any changes made in this view are automatically
stored; a record command is not required.
Notice that there are effects existing in this list prior to any being recorded. Effects 901-916 are
preprogrammed relative effects that are automatically available to you (see Relative Effects, page
239).
To navigate this list use the navigation keys as described in Display Control and Navigation, page
33 or select the effect number you wish to work with. Notice that when you select the effect list, the
CIA changes to display the information for the currently selected effect.
228 Ion Operations Manual

Effects Editor
When viewing the effect list, the selected effect is displayed in the CIA. The effect properties and
attributes are shown in categorized buttons in the CIA. To change any property or attribute, press
the corresponding button and enter data as required.
The properties display of the effects editor is shown below and definitions of properties follow.
Type
Defines the effect type: step-based, absolute, or relative (linear, focus, or color). To change the
type, press {Type} and then press the desired effect type in the buttons to the left.
• [1] {Type} {Step based} [Enter]
Scale
Applies only to relative effects. This modifies the amount the pattern is offset from the current
parameter values. The scale is expressed as a percentage increase or decrease (25 = 25% of the
programmed value).
• {Scale} [3] [0] [Enter] or you may adjust this using the “Scale” encoder.
Cycle Time
Provides a cumulative time to complete one full iteration of an effect. In relative effects, the cycle
time determines the length of time required for one channel to complete the cycle.
In absolute and step-based effects, the cycle time determines the time required to complete one full
iteration of the effect. In these effect types, modifying the cycle time changes the timing values
proportionally within the effect itself.
To change the cycle time, press {Cycle Time} and then enter the desired time (in minutes and
seconds) from the keypad, followed by [Enter]. This can also be adjusted from the encoder.
19 Creating and Using Effects 229

Duration/Cycle
This determines the length of time an effect will run. To specify, press {Duration/Cycle} and then
choose the desired method from the buttons that appear to the left. The options are:
• {Infinite} - for step and absolute effects, the effect will run until the channel is provided a new
instruction or the effect is stopped. Relative effects with an infinite duration will run until a stop
flag is applied.
• {Duration} - the effect will run for a set amount of time given in minutes and seconds. Enter
the time from the keypad.
• {Num cycles} - the effect will run for a set number of iterations. Enter the number using the
keypad.
• {Duration/Cycles} {Num Cycles} [1] [0] [Enter]
Parameters
This allows you to select which parameters will be involved in the selected effect, by default. By
entering a value here, you do not need to specify the required parameter when placing an effect on
a channel group.
To add or remove parameters to the effect, press {Parameters} and then select the desired
parameters from the buttons that appear to the left.
• {Parameters} {Iris} [Enter]
Attributes
These determine the basic behavior of the effect. Attributes include behaviors such as forward,
reverse, bounce, positive, negative, and random grouping or random rate. The attributes are
slightly different between step, absolute and relative effects.
• Forward - the effect will run in the programmed direction (the arrow on the pattern
editor indicates “forward” for pattern effects, step and absolute effects will follow
numerical order).
• Reverse - effect will run in the opposite direction of forward or reverse numerical
direction. Forward and Reverse are mutually exclusive settings.
• Bounce - effect will run first in forward, then in reverse. Subsequent passes alternate
between forward and reverse.
• Positive - effect will run the steps (on state and off state) as programmed. This is
applicable to step effects only.
• Negative - inverts the on state and off state for the effect. This is applicable to step
effects only.
• Random Grouping - channel distribution or step order (depending on the type of
effect) are applied in a continuously random fashion.
• Random Rate - this overrides the cycle time of the effect. Random Rate is applied in
a range (for example 5- thru 150).
Play with these behaviors to see how they alter your effect.
230 Ion Operations Manual

Entry
Establishes at what time and how channels will enter the effect. To change the entry method press
{Entry} and then choose a method from the buttons to the left. Entry modes vary by effect type. The
options are:
• {Cascade} - channels enter the effect according to the trail and cycle time values (if
applicable).
• {Immediate} - all channels enter the effect instantaneously.
• {Fade by Size} - the effect will achieve its full value as allowed by the pattern or step or
absolute values using the In Time.
• {Fade by Size and Rate} - the effect will achieve its full value as allowed by the pattern or step
or absolute values and ramp up to full speed using the In Time.
Exit
Establishes at what time and how channels will exit the effect. To change the exit method press
{Exit} and then choose a method from the buttons to the left. Exit modes vary by effect type and
how the effect is stopped. The options are:
• {Cascade} - channels leave the effect when they have completed their last pass (number of
cycles) or when they do not have enough time to make a final complete pass (duration).
• {Immediate} - all channels exit the effect instantaneously.
• {Fade by Size} - when the effect is exited, values will return to their background state while
still running using the exit time.
• {Fade by Size and Rate} - when the effected is exited, channels will stop running the effect
and return to their background state using the exit time.
• {Stop and Fade} - when the effected is exited, channels will stop running the effect and return
to their background state using the exit time.
• {Stop and Hold} - when the effect is existed, channels will halt exactly where the effect left
them.
Time (Entry or Exit)
These fields establish the length of time for channels to enter or exit the effect. It can be entered in
minutes and seconds from the keypad. These timing values are applied to the entry and exit
modes. Cue level timing is the default for these. Press {Entry Time} [Enter] or {Exit Time} [Enter].
To reset to defaults, press [Time] [Enter]
19 Creating and Using Effects 231

Grouping
Grouping is used only in relative and absolute effects. This determines how channels currently
running the effect will be grouped throughout the pattern. To change this press {Grouping} and
then enter the number of lights you want grouped together.
Grouping defaults to {Spread}. This means that every light the effect is applied to will act as an
individual element, moving through the effect sequentially based on the channel selection order,
cycle time, and trail times. You can enter any number you require. A grouping of 2 means that every
other light in the selection list when the effect is applied will move together through the effect.
Grouping of three means every third light, and so on.
Your options are 1-29 or {Spread} which will distribute each channel in the effect evenly and treat
it as a separate group.
• {Grouping} [2] - every other channel (in a range of channels) will be grouped when
running the effect.
When an effect is applied to a group in live, that group is distributed by order, using this grouping
function. If a group list is created and an effect applied, each group is considered an individual
element within the effect.
Trail
Trail is applicable to relative and absolute effects. Trail determines how channels are to follow each
other through the effect; it is a percentage of the cycle time. Trail can be any value from 0-100%,
even, or solo. The default is even. For example:
• {Even} - the groups will be distributed evenly throughout the pattern. This is calculated by
dividing the cycle time of the effect by the number of groups of channels.
• {10%}-{90%} - when the first group is 10% through the effect, the second group will start the
effect, and so on through the remaining groups. Therefore, the groups will trail n% behind
each other, as a percentage of the cycle time.
• {Solo} - the first group will execute the entire pattern. When done, the second group will
execute the entire pattern, and so on.
Using Encoders with the Effect Editor
When any effect is specified in the command line, the encoder LCD automatically repaints to
display the following properties:
• Cycle Time (Default is 5 seconds for relative effects)
• Scale
• Shape (Vertical or Horizontal as defined by the {Mode} button)
• Axis
At any time, you may use the encoders to adjust these properties within the effects editor for the
specified effect.
232 Ion Operations Manual

Effect Status Display
To view the effects currently running, you may press [Displays]>{Effect Status} to reveal the effect
status display in the CIA.
This display shows you any currently running effects and gives you the ability to edit the effect while
running. When an effect is selected, the encoders and encoder screen change to allow you to
manipulate the effect according to rate, size, horizontal form, vertical form, and axis.
For Example:
To edit an effect, select the effect using the command line or by clicking on the effect in the
status display.
• [Effect] [9] [0] [2] [Enter]
The encoder screen repaints so that the encoders now control the five attributes in the
columns of the effect status display:
• Rate - modifies cycle time. Default is 100% and can be modified from 0%-2000%.
• Size - modifies scale. Default is 100% and can be modified from 0%-2000%.
• Shape (Vertical or Horizontal as defined by the {Mode} button) - default is 100% and
can be modified from 0%-2000%.
• Axis - default is 0° and can be modified by +/- 180°.
Use the encoders or softkeys to adjust the effects while watching the effect on stage.
The effect itself can be accessed for editing from this display by pressing {Edit}. Any changes made
directly in the live effect editor are made to the effect itself and must be stored. Cue level overrides
also must be stored or updated to the required cue, but do not impact the basic effect itself.
Effect attributes modified in the effect status display can be reset to their previous values using the
softkeys:
• {Rate} [Enter] - resets the rate to the previous value.
19 Creating and Using Effects 233

Step Effects
In step effects, each step contains an on-state and an off-state. The on-state is the action the
channels in the step should take when the step is active. The off-state is the action the channels in
the step should take when the step is not active. Step effects are a quick and easy way to build
simple chases.
When building step effects, channels must be defined for each step. This is different from absolute
and relative effects.
Once complete, you may play back the effect on all channels embedded in it by pressing [Recall
From] [Effect] [x] [Enter]. Or you may specify only certain channels to play back from the
embedded channel list.
A step effect is displayed in a chart with the following columns:
• Step - indicates the step numbers.
• Channels - displays the channel(s) in the step.
• Param - displays the parameter (if other than intensity) controlled by the step.
• Step Time - time from triggering the associated step to triggering the next step.
• In Time - the length of time for the channels to fade to the “on-state”.
• Dwell Time - the length of time the step remains in an “on-state”.
• Decay Time - the length of time it takes for the channels to fade to the “off-state”.
• On State - the parameter level (in%), or referenced data to be used for the on-state.
• Off State - the parameter level (in%) or referenced data to be used for the steps offstate.
If you want the “off-state” to be the background state from playback, select the
column and press [At] [Enter].
All times are entered from the keypad in minutes and seconds, tenths and hundredths.
Here is an example of a step effect when viewed in the CIA:
Step effect softkeys
234 Ion Operations Manual

Program a Step Effect
Below is the process used to program the effect illustrated in the image above.
For Example:
To open the effects list press:
• [Effect] [Effect]
Establish the number of the effect by pressing:
• [1] [Enter]
The CIA will repaint with unpopulated fields for the new effect. Assign the effect as “step”
by pressing:
• {Step-based}
The effect will appear in the list and the CIA will repaint with the default entries for the effect
and a step chart for the effect. Define the number of steps by pressing:
• {Step} [1] [Thru] [6]
The steps will populate the chart and will remain selected. To make identical changes to all
steps at once, you may now use the page arrow keys to navigate the chart. To make
changes to only a single step, specify only one step in the command line, default values are
drawn from the previous step.
After paging to the “Channels” column, specify the channels for the effect.
• [1] [thru] [1] [2] [Enter]
Channels 1-12 will be broken up and distributed through the steps in the chart. Choose the
parameter you would like in the effect by pressing:
• {Parameters} (Intensity is assumed unless another parameter is
specified)
All steps are now intensity based. Use the page arrows to access the “Step time” column.
Enter the desired step time:
• [1]
Page arrow to the Dwell Time (In time is left at 0) column and enter a dwell time:
• [1]
Page arrow to the Decay Time column and enter a decay time:
• [.] [2] [5]
Page arrow to the On State column and enter the on state percentage:
• [1] [0] [0]
Page arrow to the Off State column, or use the softkeys to go to the desired field, and enter
the off state percentage:
• [5]
Adjust any of the effect details on the right side of the CIA by pressing the appropriate detail
button and making changes (see Effects Editor, page 229).
Note:
The cycle time is an aggregate of all of the timing in the effect and indicates how
long it will take to make one full pass through the effect. If the cycle time is modified
by the keypad or the encoder, it proportionally adjusts all of the timing within the
effect.
19 Creating and Using Effects 235

Delete a step
To delete a step from a step-based effect, specify the effect in the command line and press delete:
• [Effect] [1] {Step} [4] [Delete] [Enter] [Enter]
• [Effect] [1] {Step} [4] [Thru] [8] [Delete] [Enter] [Enter]
Insert a step
To insert a step anywhere in the effect, specify the step you wish the new step to be inserted before.
• [Effect] [1] {Step} [4] {Insert} [Enter] - Inserts a new step before step 4. If step four does not
exist, it also creates the steps necessary to have “step 4” and then places a step ahead of it
as well.
Inserted steps result in all succeeding steps to be bumped one place lower in the effect. In the
above example, by inserting before step 4, step 4 would become step 5, step 5 would become 6
and so on. The inserted step would become the new step 4.
236 Ion Operations Manual

Absolute Effects
Absolute effects are a listing of sequential actions that channels are to take. They differ from step
effects in that there is no on/off state, rather they define progressive behavior from one action, to the
next, to the next, and so on. The best example of this is that palettes and presets can be used as
actions in absolute effects.
Absolute effects differ from relative effects (which are also progressive) in that you are specifying
exactly what actions you want the lights to take, rather than mathematical offsets from the current
state (relative effects).
Absolute effects also do not contain an embedded channel list. Therefore, the effect must be
applied to channels in order to be played back.
Absolute effects are displayed in a chart with the following columns:
• Action - displays the action number.
• Time - the time for the action to fade in.
• Dwell - the duration of the action before moving to the next action.
• Level - indicates either the level of the parameter specified in the effect, or the
referenced value for the channel(s) to perform (Palette or preset as defined in the
command line).
Absolute effect softkeys
In the above image, actions 1-4 indicate referenced values in the “Level” column (palettes or
presets), though these values can be absolute data as well.
19 Creating and Using Effects 237

Program an Absolute Effect
Below is the process used to program the effect illustrated in the image above.
For Example:
To open the effects list press:
• [Effect] [Effect]
Establish the number of the effect by pressing:
• [Effect] [8] [Enter]
The CIA will repaint with unpopulated fields for the new effect. Assign the effect as absolute
by pressing:
• {Absolute}
The effect will appear in the list and the CIA will repaint with the default entries for the effect
and an action chart for the effect. Define the first action by pressing:
• {Action} [1] [Enter]
The step will populate the chart and will remain selected. You can also create a range of
actions at once, using the [Thru] button, if desired. Use the page keys to navigate to the
different columns
After arrowing to the “Time” column (or using the softkeys), specify the fade in time for the
actions.
• [5] [Enter]
Page arrow to the Dwell column and enter a dwell time:
• [5] [Enter]
Page arrow to the Level column and enter the desired referenced target:
• [Color Palette] [5]
Page arrow down and a new action will be created. All fields default to the values in the
previous action. Page to the next action in the Level column and enter the referenced
target:
• {Color Palette 8}
Page arrow down to the next action in the Level column and enter the referenced target:
• [Color Palette] [2]
Page arrow down to the next action in the Level column and enter the referenced target:
• {Color Palette 4}
Adjust any of the effect details on the right side of the CIA by pressing the appropriate detail
button and making changes (see Effects Editor, page 229).
238 Ion Operations Manual

Relative Effects
A relative effect is an offset from the current state of a channel parameter. There are three different
types of relative effects: focus, color, and linear. Each of the these effect types have a graphic editor
designed specifically for the parameters involved.
Relative effects have many of the same properties and attributes as step-based and absolute
effects.
Ion is preprogrammed with 16 relative effects which represent some of the most commonly used
patterns and parameters. These are automatically visible in the effects list and can be manipulated
using the encoders to conform to your needs. You may also custom build relative effects.
Note:
Focus Effects
Focus effects are designed to impact a channel’s pan and tilt parameters. These are represented in
the horizontal and vertical axes of the graph in the effects editor. They can be created from live or
blind and the properties can be set in the effects editor as any other effect (see Effects Editor, page
229).
New focus effects default to a circle. You can clear this and draw your own shape by pressing
{Edit}>{Clear} and drawing on the graph with your finger or the mouse. Press {Apply} when you
are done. Canned focus effects can be modified in the same manner. The green arrow indicates
default direction of motion, which can be modified in attributes.
Focus Effect
As you learn to use the effects editor with relative effects, it is recommended that
you experiment with the preprogrammed effects until you understand the
fundamentals and how effects can be altered.
19 Creating and Using Effects 239

Color Effects
Color effects impact only color parameters. Hue and saturation offsets can be used which are
represented in the horizontal and vertical axes of the graph in the effects editor. The {Parameters}
key within a color effect displays the various color mechanisms used in any patched channels.
New color effects default to a circle. You can clear this and draw your own shape by pressing
{Edit}>{Clear} and drawing on the graph with your finger or the mouse. Press {Apply} when you
are done. Canned color effects can be modified in the same manner. The green arrow indicates
default direction of color shift, which can be modified in attributes.
Color Effect
Linear Effects
A linear effect does not have to be parameter specific. Rather it can simply be a reference to a linear
diagram which can be applied to any parameter. You can redraw the linear diagram for an existing
linear effect by pressing {Edit}>{Clear} and then tracing the diagram on the graph with the mouse
or your finger. Press {Apply} when you are done.
Linear Effect
240 Ion Operations Manual

Define a Pattern Shape
Shapes can be defined for any relative effect (focus, color, or linear).
To define a shape, press the {Edit} softkey beneath the pattern editor. The softkeys will change to
{Apply}, {Restore}, {Clear}.
• Press {Clear} to clear the pattern.
• Draw a new pattern using your finger (or the mouse). If you want to return to the original
pattern, press {Restore} before pressing apply.
• When you have the proper pattern drawn, press {Apply}. The pattern will be applied to the
effect.
Note:
If you delete a preprogrammed effect (for example, after making changes to it) the
effect will return to its default value. Preprogrammed effects (901-916) cannot be
deleted.
You can also copy effects to another effect location and modify them from there.
This will leave the original effect untouched.
• [Effect] [904] [Copy To] [8] [Enter]
Program a New Relative Effect
To open the effects list press:
• [Effect] [Effect]
Establish the number of the effect by pressing:
• [Effect] [4] {Type} {Linear/Focus/Color} [Enter]
The effect will appear in the effect list and the CIA will repaint with the effect details visible.
Manipulate the effect using the encoders, effect graph, or property fields so that the effect
meets your needs (see Effects Editor, page 229 for details on effect properties and
encoders).
19 Creating and Using Effects 241

Apply an Existing Effect
Once an effect has been created, it will appear in the effects list. To apply an existing effect, press:
• [Select Channels] [Effect] [x] [Enter]
or using the direct selects
• [Select Channels] {Effect x}
The selected channels will begin their changes as programmed in the effect.
Since step based effects have an embedded channel list, those effects can be recalled by [Group]
[Effect] [n] [Enter] or [Recall From] [Effect] [n] [Enter] without selecting channels.
Editing Effects Live
To edit an effect while it is running, press:
• [Displays] {Effect Status}
The effect status display will open in the CIA and any currently running effects will be visible in the
display. Selecting the effect number in the status display will select the effect for editing. Select the
effect you want to edit live by pressing:
• [Effect] [x] [Enter]
Use the encoders to adjust the attributes as described in Effect Status Display, page 233.
Adjustments are cue overrides and don’t impact the core effect.
To edit other properties of the effect in live, press {Edit} and the effects editor will open (See Effects
Editor, page 229). Changes made in the editor will impact the effect itself and all instances in which
the effect is used. Changes made to effects in the effect status display impact only that instance of
the effect. Changes made directly in the effect editor impact all instances of that effect.
Stop an Effect
Pressing [Stop Effect] [Enter] will stop all running effects.
To stop a specific effect, press: [Stop Effect] [x] [Enter].
You may also stop effects on specific channels by [selecting channels] [Stop Effect] [Enter].
You may also remove an effect instruction by [selecting channels] [Effect] [At] [Enter]. This
command will work in live or blind. You can also stop the whole effect by pressing [Effect] [x] [At]
[Enter].
Deleting an Effect
To delete an effect, press [Delete] [Effect] [n] [Enter] [Enter]. If you delete one of the default
effects (901 through 916) that effect will return to its default values.
242 Ion Operations Manual

Effects on Submasters
Channels running effects can be loaded onto a submaster. Pressing the bump button of the
submaster starts or stops the effect.
For the submaster to control the rate and/or size of the effect, it must be configured as an effects
submaster. When a submaster is defined as effect, only the effect information is stored. The slider
will then have control of the in and out behavior of the effect.
If the submaster is set to additive, the slider will control non-effect values only.
Configuring an Effect Submaster
To configure an effect submaster, press:
• [Sub] [x] {Mode} [Enter]
Note:
The {Mode} softkey toggles between inhibitive, effectsub, and additive. Press
{Mode} until effectsub is on the command line.
Recording an Effect to a Submaster
To apply an existing effect, press:
• [Select Channels] [Effect] [x] [Enter]
Recording to a submaster, press:
• [Record] [Sub] [x] [Enter]
Running an Effect from a Submaster
The way effects are played back from a submaster depends on its mode, and whether the
submaster is set to be a proportional fader or an intensity master.
Below is an example of four different submasters, in different modes, with the same effect stored to
them.
Effect on an Additive/Proportional Submaster
The submaster contains the intensity, pan/tilt data, along with the effect. Pressing the bump
button starts the effect. The fader controls values not affected by the effect. Pressing the
bump button again stops the effect.
Effect on an Additive/Intensity Master Submaster
Pressing the bump button marks the lights, and starts the effect. The fader brings up any
intensities stored in the submaster. Pressing the bump button again stops the effect.
Effect on an Effect/Proportional Submaster
Pressing the bump button starts the effect. The fader controls the rate and/or size based on
the effect’s entry behavior. Pressing the bump button again stops the effect.
Effect on an Effect/Intensity Master Submaster
Pressing the bump button starts the effect. The fader controls the rate and/or size based on
the effect’s entry behavior. Pressing the bump button again stops the effect.
In other words, there is no difference between a proportional fader and an intensity master when
the submaster is configured to be an effect submaster.
19 Creating and Using Effects 243

244 Ion Operations Manual

Chapter 20
Using About
[About] provides detailed information regarding selected elements. When opened, it appears in the
CIA and remains open until closed or until another action forces it to close.
This chapter contains the following sections:
• [About] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
• About Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249
• About Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250
• About Cue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
• About IFCB Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
• About Presets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
20 Using About 245

About [About]
Pressing [About] puts the console in “about” mode, which allows you to examine “about”
information indefinitely, simply by selecting the element you are interested in.
When in about mode, selecting a channel will reveal information about that channel. Below are
examples of the “Current Values” view (see below) of information that is presented when selecting
conventional or moving lights.
Conventional Channel Current Values
Moving Light Channel Current Values
The buttons on the right side of the about screen alter the information that is displayed for the
selected channel. The selected button is highlighted in gray. The buttons are:
• {Current Values} - this shows any current information that the channel is receiving and
following.
• {Background} - this displays any information that is being sent to the channel, but not
adhered to since another source has ownership of the channel.
• {Moves} - this shows the previous move, value of the previous move, the next move, and its
value.
• {Usage} - this shows where and how a channel is used.
• {Patch} - this displays patch information about the channel.
• {Lamp Controls} - this displays any parameters associated with the channel. If the channel
is a conventional (intensity-only) fixture, no parameters will be displayed. If it is a moving light,
this key will access lamp controls.
246 Ion Operations Manual

[About]
When [About] is pressed, the CIA presents the following information:
• Channel count for the console
• Software version
• Copyright notifications
• Device name
• Assigned as (Primary/Backup/Client/Offline)
• User ID
• Number of patched and unpatched addresses
• Priority (ACN and Net2)
• IP Address
About System
When {About System} is pressed, the CIA displays a list of all network devices that are connected
to Ion. These network devices include:
• Consoles
• RPUs
• RVIs
• PC Clients
• Show Control Gateways
• I/O Gateways
• Unison processors
• CEM+
• Net3 Gateways
• ETCNet2 Nodes
Each network device will display the following information:
• Device Type
• Name/Component
• Status
• Connected
• IP Address
20 Using About 247

Clicking on a CEM+ in the {About System} list will display the following information about that
device:
• Rack Name
• Rack Type
• Ambient Temperature
• Phase A,B,C voltages
• Frequency
• Filter Hours Remaining
• Rack Errors
• Group Number
• Group Name
• Network Settings
• Software Version
Buttons available in the CEM+ {About System} screen are {Activ. Preset}, {Deactiv. Preset}, and
{Clear Errors}.
Note:
Clearing CEM+ errors from Ion will be temporary unless the errors have been fixed
at the CEM+. Errors displayed on Eos will clear on their own once they have been
cleared from the CEM+.
248 Ion Operations Manual

About Channel
Press [About] to put the CIA into “About” mode. When a channel is selected, the information below
is displayed: You can select the information you wish to view from the four buttons located on the
right side of the CIA. The buttons are:
{Current Value} displays information that indicates:
• Channel number
• Device Type
• Most recent intensity move (cue number)
• Next intensity move
• What the channel is inhibited by (if anything)
• A list of all parameters on the channel showing the current value and its source, the
absolute value, delay and timing information, and any parked values.
{Background Value} displays similar information:
• Channel number
• Device Type
• A list of all parameters on the channel showing the background value and its source,
and the DMX value.
{Moves} displays information that shows:
• Parameters
• Previous move
• Value of the previous move (preset, palette, or absolute data)
• Next move
• Value of the next move (preset, palette, or absolute data)
{Usage} displays information on how the channel is used, such as:
• Maximum Intensity
• Total number of cues it appears in (based on intensity)
• Total number of intensity moves
• Cue lists it is used in
• List of submasters that include the channel
• List of cues that have move instructions for the channel
• List of cues with dark moves for the channel
{Patch} displays the following information:
• the channel’s address range
• the proportional patch level
• curve (if any)
• preheat information (if any)
• swap/invert pan/tilt status
• any keywords associated with the channel
• List of all parameter values with their address, home value, and parked value (if any)
{Lamp Controls} displays controls for the lamp or other parameters of the device (if it is a moving
light).
20 Using About 249

About Address
Press [About] to put the CIA into “About” mode. When an address is selected, the information
below is displayed: You can select the information you wish to view from the five buttons located on
the right side of the CIA. The buttons are:
{Address} displays the following information:
• Address number (displayed as straight address and port/offset)
• Dimmer label (if any)
• Associated channel number, which is a hyperlink to the [About] channel display.
• Part number (if any)
• Notes
• Output value (ACN, Net2, ArtNet, Avab UDP, or DMX)
• Current output value and source of output
• Parameter controlled by the address
• Home Value
• Basic patch information
• Extended patch information (if available)
• If it is a scroller, color/gobo wheel, the assigned scroll or wheel is indicated
{Next Part} & {Last Part} will advance to the next part or go back to the previous part. These
buttons only display for addresses with parts.
{Go To Patch} is a shortcut to edit the patch for the address selected. This will open up the patch
display.
{Lamp Controls} displays controls for the lamp or other parameters of the device (if it is a moving
light).
{Address Check} will bring current address to full.
{Next/Last Unpatched} will allow you to see what addresses closest to the current address are
currently unpatched.
250 Ion Operations Manual

{Sensor AF} - appears when the current address is patched to a dimmer in an ETC Sensor rack.
Sensor feedback must be enabled. See Enable Sensor Feedback, page 301 for more information.
Note:
{Sensor AF} displays the following information:
• Sensor dimmer name
• Dimmer module type
• Rack/Position
• Rack dimmer level (displayed as a percentage)
• Rack dimmer source
{Sensor AF} displays the following information, which can be modified from Ion:
• Mode
• Curve
• Threshold
• Scale Minimum
• Scale Maximum
• Preheat
• Preheat Timing
• Advanced Features (AF)
The following buttons will also be displayed:
• {Set Dimmer} sets that dimmer to an intensity.
• {Unset Dimmer} unsets a dimmer.
• {Clear Errors} clears any dimmer errors that are present for that address.
Note:
For Sensor feedback, the CEM+ must be running software version 3.0 or later.
Clearing CEM+ errors from Ion will be temporary unless the errors have been fixed
at the CEM+. Errors displayed on Ion will clear on their own once they have been
cleared from the CEM+. Some CEM+ errors can only be cleared at the CEM+.
20 Using About 251

{Device Details} - appears when the current address is patched to a RDM device. RDM devices
must be enabled through the ECM and discovered through the patch. See Enable RDM, page 301
and {Patch} Display and Settings, page 68.
{Device Details} displays the following information and allows some changes to be made to:
Note:
Note:
• Device Label (displayed at the top by the address number)
• DMX Address (can be changed in this display by clicking on the property or value)
• DMX Label (same as the device label, but the label can be changed here by clicking on
the property or value)
• Type
• Manufacturer
• Device ID
• Footprint
• Version
• Lamp State
• Lamp Hours
• Head DC Voltage
• Lamp On/Off
• Gel Distance Traveled
• Gel2 Distance Traveled
• Fan RPM
• Ambient Temperature
• Gel Temperature
• Device Errors (will only display if there are current errors)
• Clear Errors
Device Errors are displayed in four different colors depending on severity.
Note:
Changes may take a few seconds to take effect. They will propagate to the RDM
device and then back to the console’s patch and about displays.
Changing the address can not cause any part of the fixture to move to a different
universe or communication with the device maybe loss. The universe is set into
the gateways port configuration.
Color severity is determined by the device manufacturer.
• Gray - unknown or not an error
• White - Advisory
• Yellow - Warning
• Red - Error
252 Ion Operations Manual

About Cue
The following information will be displayed:
• if the cue is active and what fader it is playing on
• timing data for the cue (including discrete timing)
• any effects running
• number of move instructions in the cue
• what channels move in the cue
About IFCB Palettes
The following information will be displayed when an intensity, focus, color, or beam palette is
selected:
• the number of cues the palette is used in
• the number of presets the palette is used in
• the number of move instructions the palette is used in
• the first cue the palette is used in
• the last cue the palette is used in
• the number of cue lists that use the palette
About Presets
When a preset is selected, the following information will be displayed:
• the number of move instructions the preset is used in
• the first cue the preset is used in
• the last cue the preset is used in
• the number of cue lists that use the preset
20 Using About 253

254 Ion Operations Manual

Chapter 21
Storing and Using Submasters
Faders, both virtual and physical, can be assigned as submasters. This chapter explains how to
assign and use submasters on your Ion console. You may also use submasters with Universal
Fader Wings. For more information on these, see Universal Fader Wings, page 335.
This chapter contains the following sections:
• About Submasters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
• Loading Submasters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
• Using Bump Button Timing With Submasters . . . . . . . . . .261
21 Storing and Using Submasters 255

About Submasters
Submasters can store any parameter data for channels. When storing from Live, Record Only and
Record can both be used to determine what contents are stored. You can copy cues, presets, or
palettes to a submaster as well. Channels running effects can be loaded onto a submaster. See
“Effects on Submasters” on page 243. Submasters can be accessed using the slider module (see
Slider Module, page 214) or the Universal Fader Wings (see Universal Fader Wings, page 335).
Faders can be configured as submasters in setup (see Fader Configuration, page 96) or they can
be defined while programming. In blind, submasters can be created by using the [Thru] [Thru]
syntax.
• [Sub] [1] [Thru] [Thru] [1] [0] [Enter] - will create subs 1 through 10.
When set as a submaster, the bottom button beneath the potentiometer acts as a bump button or a
mark button depending on the submaster type (Proportional or Intensity Master). The button above
the bump can be used to select all of the channels associated with the submaster, if the submaster
is inactive. This is equivalent to the syntax [Group] [Sub] [x] [Enter]. When the submaster is
active, this button will assert the contents of the submaster when pressed.
It is possible to program upfade, dwell, and downfade times in association with the submaster
bumps.
On fader wings, when a submaster bump LED is blinking, it means that the submaster must be
homed due to either changes to its content or to its mode. In either case, reset the submaster by
dropping it to zero and the moving it back to the desired position. Inhibitive submasters (see below)
that are blinking must be homed to 100% rather than zero. The LED will also blink when the
submaster is in a “Held” state via bump button timing
Recording a Submaster
You can record current stage contents directly to a submaster. To do this, set levels in live as
needed then record them to the submaster. See the following examples:
• [Record] [Sub] [5] [Enter] - records all current values to sub 5.
• [Record Only] [Sub] [5] [Enter] - records the manual values of the current stage state to sub
5.
• [Record Only] [Sub] [5] [Label] [xxxx] [Enter] - as above, with a label.
• [Record] [Sub] [5] {Mode} [Enter] - as above, and alters mode between inhibitive or additive.
Other submaster properties (HTP/LTP, Exclusive, and so on) can be assigned in this way as
well.
You can also record selected channel data to submasters as well. See below:
• [Channel List] [Record] [Sub] [5] [Enter] - records all data for the channel list to sub 5.
• [Channel List] [Record Only] [Sub] [5] [Enter] - records manual data for the channel list to
sub 5.
If the fader is at full when the submaster is stored, you can use the [Rem Dim] command to
automatically release the content to the submaster.
256 Ion Operations Manual

Submaster Displays
In the display window of any programmed submaster, you will see the following:
• Submaster number
• Submaster label (if any)
• Independent flag (if any)
• I-Master flag (I.M. - if any)
• Current setting
Additive vs. Inhibitive
You may define your submaster as additive (contributes to the live output) or inhibitive (limits live
output). Ion defaults to submasters being additive.
To toggle a submaster between additive, inhibitive, or effectsub:
• [Sub] [7] {Mode} [Enter]
Additive submasters are indicated by a green LED or a green outlined fader icon in the fader
window.
Inhibitive submasters display these indicators in red. Channels mastered by an inhibitive submaster
are indicated with an “I” next to the intensity value in the channel display in live. Inhibitive
submasters do not provide levels to the stage picture, they limit them (similar to a grandmaster). It
is possible to put non-intensity parameters onto an inhibitive submaster, but it must be done from
blind.
For more information about effectsub, See “Effects on Submasters” on page 243.
Proportional vs. Intensity Master
A submaster can be set to be either a proportional fader or an intensity master. This is done using
the {Fader} softkey. Ion defaults to submasters as proportional.
Proportional submasters
When a submaster is proportional, the slider will control all contents of the submaster (intensity and
non-intensity parameters) when moved from zero. When a proportional sub is return toward zero,
channel will be returned to their previous level.
The bump button can be used to bump all values to their recorded levels in the submaster, or, by
assigning timing values, fade the contents of the submaster up or out.
Intensity master
When set to this fader type, the slider will control intensity only. The bump button can be used to
preset (mark) non-intensity parameters stored to the submaster. If the bump is not pressed before
the slider is moved, the slider will also fade the non-intensity-parameters to their recorded values.
Once the non-intensity-parameters are at their end state, the slider only controls intensity. When
dropped toward zero, controlled intensities will be faded toward zero.
To toggle a submaster between a “Proportional” or “I-Master” fader:
• [Sub] [8] {Fader} [Enter]
21 Storing and Using Submasters 257

HTP vs. LTP
Submasters can be set to be either Highest-Takes-Precedence (HTP) or Latest-Takes-Precedence
(LTP). This setting is applied to intensity only. Non-intensity parameters are always LTP. Ion
defaults all submasters to HTP. For more information on HTP and LTP see HTP vs. LTP, page 7.
To toggle a submaster between HTP and LTP:
• [Sub] [6] {HTP/LTP} [Enter]
Exclusive Submasters
Submasters can be placed in exclusive mode. This prohibits storing the contribution of the
submaster into any record targets. In essence, this acts as a fixed [-] [Sub] [Record] command.
To place a submaster in exclusive mode:
• [Sub] [5] {Exclusive} [Enter]
Independent
You can also set a submaster to “independent”, allowing submaster values to remain unaffected by
other submasters or playback fader instructions. They will, however, still be impacted by manual
control, grandmaster, blackout, park instructions, or other play faders and submasters on
independent.
Inhibitive subs can not be set as independent.
To toggle a submaster between independent “on” or “off”:
• [Sub] [7] {Independent} [Enter]
Changing Fader Pages
On Fader Wings
The fader wing is paged using the [Fader Controls] button on the Ion console. Fader pages are
delineated in 20 fader increments. If you advance to the next fader page, your entire fader wing
array will advance by a total of 20 faders.
To change the fader page of a fader wing:
Step 1: Press and hold the [Fader Controls] button on the Ion console. The LCD on the fader
wing will display the available pages beneath the fader bump buttons.
Step 2: Press the bump button corresponding to the page you wish to display on the fader
wing. The fader wing will display those faders after your selection is made.
On the Slider Module
The slider module is paged on Ion using the page buttons that are displayed to the right of the
module. There are 30 available pages of sliders. Pages are delineated in 10 fader increments. Click
on the appropriate page button to access that row of sliders. You can scroll through the available
pages by clicking the arrow button(s) next to the page buttons.
258 Ion Operations Manual

Loading Submasters
Submasters can be loaded with cues, presets, or palettes.You can convert an empty fader to a
submaster without configuring it in setup. Any fader can be configured and loaded with a submaster
if:
• the fader is not configured
-or-
• the fader is configured as a playback but has no cue list loaded to it
-or-
• the fader is configured as a submaster, but that submaster is empty.
Regardless of the fader configuration in setup, if the above conditions are met, the fader can be
loaded with the submaster specified on the command line.
If a submaster with data (or a playback fader) already occupies the fader, that fader must be
released before another submaster can be loaded.
To release a fader that contains a submaster:
Step 1: Press and hold [Fader Controls].
Step 2: If necessary, select the fader page that contains the desired fader. Pressing the
appropriate page bump button on the fader wing or use the page controls with the
slider module.
Step 3: Press {Release}.
Step 4: Press both buttons ([Load]) of the desired fader. The fader will be released but will
remain configured as a submaster
On Fader Wings
Faders on fader wings can be configured as submasters by pressing both buttons of the desired
fader. In this instance, this acts as a [Load] button.
To load a fader with a submaster:
Step 1: Specify the submaster on the command line.
• [Sub] [5] [Enter]
Step 2: Press both buttons ([Load]) for the desired fader. The submaster will load to the fader.
On the Slider Module
• [Sub] [5] [Enter] {Load} - loads submaster 5 to the fader associated with the load button.
• [Cue] [5] [Sub] [4] [Enter] - loads the contents of cue 5 to submaster 4 (a {CopyTo}
command will appear within the syntax on the command line).
• [Cue] [5] {Load} - loads cue 5 to the submaster associated with the chosen load button.
• [-] [5] [Cue] [5] [Sub] [6] [Enter] - loads the contents of cue 5, minus channel 5, to submaster
6.
• [Cue] [1] [thru] [5] [Sub] [1] [thru] [4] [+] [7] - sequentially loads cues 1 thru 5 to subs 1, 2,
3, 4 and 7.
• [Cue] [1] [thru] [5] [Sub] [1] [thru] [Enter] - sequentially loads cues 1 thru 5 to subs 1 thru
5 (a {CopyTo} command will appear within the syntax on the command line).
21 Storing and Using Submasters 259

Updating a Submaster
It is possible to make changes to a submaster in live mode. [Update] is used to store changes to a
submaster.
• [Update] [Sub] [5] [Enter] - updates sub 5 to include changes in live output only for channels
already in submaster 5. You can also press the bump button for submaster 5 to select it.
• [Channel list] [Update] [Sub] [5] [Enter] - adds only the specified channels to submaster 5.
Labels can be changed without restoring the contents as well:
• [Sub] [6] [Label] [xxxx] [Enter]
• [Sub] [6] [Label] [Label] [Enter] - removes the label.
Deleting a Submaster
You can delete a submaster using the [Delete] key. When a submaster is deleted, the slider
remains configured as a submaster, but it will be empty.
• [Delete] [Sub] [5] [Enter] [Enter] - deletes the contents of sub 5.
260 Ion Operations Manual

Using Bump Button Timing With Submasters
Each submaster bump can have three different timing values: Upfade, Dwell, and Downfade (see
below). The default timing is set so that the bump functions as an “on” flash key for additive
submasters and an “off” flash key for inhibitive submasters. Effects on submasters will follow
submaster timing, unless timing has been placed in the effect itself
The three timing values are:
• Upfade time - this is the time for the submaster to fade from its home position to its target
position (0 to Full if additive, Full to 0 if inhibitive). The default time is 0.
• Dwell time - this is the time the submaster look will hold before starting the downfade. This
can be set to a specified time, or to “Hold” or “Manual”. “H old” time maintains the submaster
values until the bump is pressed a second time. “Manual” time applies the submaster values
only as long as the bump is held. The default is “Manual”.
• Downfade time - this is the time for the submaster to fade from its target position to its home
position. The default time is 0.
At any time, the potentiometer can be used to manually override fade progression or a submaster
triggered with time.
To add bump button timing live:
• [Sub] [8] [Time] [3] [Time] [4] [Time] [3] [Enter] - adds a 3 second upfade, 4 second dwell
and 3 second downfade to submaster 8.
• [Sub] [4] [Time] [Time] {Manual} [Time] [3] [Enter] - adds a manual dwell time and a 3
second downfade time to submaster 4. When the bump is pressed and held, it will flash on and
stay on until the button is released, at which time it will begin the downfade.
• [Sub] [4] [Time] [3] [Time] {Hold} [Enter] - adds a 3 second upfade time, and a ‘hold’ dwell
time. When the bump is pressed, the upfade starts. Once at the target value it will remain there
until the button is pressed again. The downfade will “bump” to zero.
• [Sub] [4] [Time] [Enter] - resets all time for submaster 4 to default (Up = 0, Dwell = Manual,
Down = 0).
Controlling Subfades Manually
It is possible to take control of submasters even if they have recorded time. To capture the fade you
must push the potentiometer past the current fade level. Once this is done, control is transferred to
the potentiometer for full manual control.
You may then use the potentiometer to increase or decrease the submaster level as needed.
21 Storing and Using Submasters 261

Submaster List
You can access the submaster list by pressing [Sub] [Sub] or through the browser (Record Target
Lists>Submaster List>[Select]).
The list view includes a list of all stored submasters including their label and all recordable
properties. You can navigate within the list by using the [Next] and [Last] buttons or by selecting
the desired submaster from the command line.
When this tab is active, the softkeys will repaint to supply you with options to affect the submaster
type, or if the submaster is set to independent. You can also move a submaster using [Move To].
For example:
• [Sub] [1] {Mode} [Enter] - toggles the submaster 1 between “additive”, “effectsub”, and
“inhibitive”. This can be done in live as well.
• [Sub] [2] {Independent} [Enter] - toggles submaster 2’s independent setting on and off.
Independent can only be activated on an additive submaster.
• [Sub] [2] {Move To} [Sub 9] [Enter] [Enter] - moves the contents, label, and timing data from
submaster 2 and places it in submaster 9. Submaster 2 is removed.
You may copy the contents of a submaster by using the [Copy To] button.
Editing Submasters
If you want to actually edit the contents of the submaster, you can select the submaster and press
{Edit}. This changes focus to the live/blind display and places you into the blind edit mode for the
specified submaster. You may also press [Blind] and select the required submaster from the
command line.
Any changes made in this screen are automatically stored. A [Record] or [Update] command is not
required.
262 Ion Operations Manual

Chapter 22
Storing and Using Macros
Ion provides you with the ability to record macros, which allow you to compose a series of
programming actions and be able to execute them later by recalling the macro.
This chapter contains the following sections:
• Store a Macro from Live . . . . . . . . . . . . . . . . . . . . . . . . . . . .264
• Macro Editor Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266
• Play a Macro. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
• Delete a Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
22 Storing and Using Macros 263

About Macros
Macros are comprised of any series of button presses (both hard and softkeys), screen commands
and events. Ion provides you with the macro feature to simplify complex or repetitive console
programming and operating tasks that you perform often.
When you record the series of button presses to a new macro, you can later play it back by simply
pressing the macro direct select button, running it from a linked cue, accessing it from a connected
show control system, remotely triggering the macro, or running it from another recorded macro.
You may create up to 1,000 macros either from live, using the macro [Learn] mode to record a
sequence of keystrokes as you perform the operation, or you can create a macro from within the
macro editor display, entering and editing keystrokes into the macro content editor without actually
executing the instructions.
The macro editor display contains a listing of all recorded macros including labels and the contents
of the macros stored. All macro editing is accomplished from the macro editor display.
Store a Macro from Live
The most effective way to store a macro is from live mode using the macro [Learn] mode to record
a sequence of button presses as you enter them. You can include any button press on the console
(hard key or soft key), except [Macro], the arrow keys, [Escape], [Select], and [Learn].
Using the [Learn] key
Pressing the [Learn] key while in live mode places the console in macro learn mode. The [Learn]
key flashes and the CIA displays “Learning” above the command line. Assign a number identifier
(from 1 to 1000) to the Macro using the control keypad and press [Enter]. The CIA flashes
“Learning Macro ####” above the command line. This indicates that the console is ready to record
the macro.
Note:
It is helpful if you plan your macro content in advance of the macro record process.
While in learn mode, each button press is recorded as content, even the [Clear]
button if you have mistaken a keystroke. There is no way to fix a content error in
live mode, but you can rerecord the macro as needed or you can edit the recorded
macro in the macro editor, removing any unneeded commands. See “Edit an
Existing Macro” on page 269.
264 Ion Operations Manual

Begin writing the sequence of button presses and events for the macro record. When you have
finished with the series of events and button presses, press the [Learn] key again to exit macro
learn mode.
Examples of a macro record function include:
• [Learn] [1] [Enter] [Go To Cue] [Out] [Time] [0] [Enter] [Learn] - records macro 1 with the
go to cue out command.
• [Learn] [5] [Enter] [1] [Full] {Chan Check} [Enter] [Learn] - records macro 5 with channel
1 at full in channel check mode. To check the next channel in the list, press [Next].
• [Learn] [4] [Enter] [-] [Sub] [Record] [Learn] - records macro 4 with instructions to record
a target excluding all submaster data.
• [Learn] [2] [Enter] [-] [Group] [6] [Color] [Record] [Learn] - records macro 2 with
instructions to record a target excluding the color data from group 6.
You can also create a macro in live that bumps submasters across fader pages but first you must
have channels assigned to the submasters.
For Example:
Write submasters 1 through 5 and 15 through 17, each with its own channel selections at
100%. Then press:
• [Learn] [1] [Enter] [Bump1] [Bump2] [Bump3] [Bump4] [Bump5]
• [Fader Page]
• [Bump15] [Bump16] [Bump17] [Learn]
Once you have created the macro from Live in [Learn] mode, you can easily edit the sequence
from the macro editor display. See “Macro Editor Display” on page 266.
22 Storing and Using Macros 265

Macro Editor Display
Macro editing is accomplished from the macro editor display. As an alternative to recording your
macro in live, you may create it from this display instead. Open the macro editor display from the
browser by navigating to Record Target Lists > Macro Editor, then press [Select]. The editor will
display on an external monitor.
The display is divided horizontally, the top portion displays the macro contents in detail while the
bottom portion lists all macros, including the label and contents.
While in the macro editor display, any numeric entry on the command line is assumed to be a macro
number. If the macro number entered already exists and [Enter] is pressed, the macro list will page
to the selected macro and the macro content detail section will display all of the contents of the
selected macro. If the macro number entered does not exist in the list and [Enter] is pressed, an
empty macro will be created with the specified macro number.
266 Ion Operations Manual

While in the macro editor display, the following functions may be performed using the control
keypad and softkeys:
• [Label] - when a macro is selected and [Label] is pressed, the alphanumeric keypad will
display on the CIA. Label the macro and press [Enter].
• [1] [Label] [Enter] - labels macro 1
• [Delete] - when a macro is selected and [Delete] [Enter] is pressed, you will be prompted to
confirm the deletion of the selected macro. To confirm press [Enter], to abort press [Clear].
• [1] [Delete] [Enter] [Enter] - deletes macro 1 from the list.
• [Copy To] - when a macro is selected and [Copy To] is pressed, you will be prompted to enter
the macro number that you want to copy the contents of the selected macro to. You will be
prompted to confirm the copy process, press [Enter] to confirm or [Clear] to abort the copy
to process.
• [1] [Copy To] [6] [Enter] [Enter] - copies the entire contents of macro 1 to macro 6.
• {Edit} - when a macro is selected and {Edit} is pressed, you will have entered edit mode for
the selected macro. Three notable changes to your macro editor display include:
• A blinking cursor in the macro content detail portion (top) of the display.
• ”Press [Select] to save or [Escape] to cancel changes” flashes above the command
line.
• The available softkeys change to {Loop Begin}, {Loop Num}, {Wait}, {Delete},
{Cancel}, and {Done}.
• {Move To} - allows you to move and reorganize your macros anywhere in the macro list
numerically.
• For instance, if you have macros 1 through 5 in the list, and you want to move or change
macro 1 to macro 6 so that your most commonly used macros are first in the list, you
would press [1] {Move To} [6] [Enter]. This leaves only macros 2 through 6 in the list.
22 Storing and Using Macros 267

Create a New Macro from the Display
From the macro editor display, enter any unrecorded macro number from 1 to 1000 and press
[Enter]. Your new macro number will display in the macro list in numerical order but will not have a
label or any contents.
To store the macro contents, select the macro and press {Edit}. A cursor appears flashing in the
macro content detail portion of the display, ready for you to add the macro content.
For Example:
Create macro 3. Write the instruction to set all active channels to 50%, then sneak them to
their original levels over 10 seconds and last, link to macro 5.
• [3] [Enter]
• {Edit}
• [Group] [5] [At] [5] [Enter]
• [Sneak] [Time] [1] [0] [Enter]
• [Macro] [5] [Enter]
• [Select]
While in macro edit mode, all keys are entered as content except the macro editor softkeys, arrow
keys, [Escape], [Select] and [Learn] keys.
268 Ion Operations Manual

Edit an Existing Macro
When you have created a macro using macro learn mode from live or otherwise, you can edit the
content of your macro by removing or adding commands and special macro softkey functions (such
as wait, loop, and so on).
From the macro editor display, select an existing macro number and press [Enter]. The selected
macro contents will display the detail section. Press {Edit} to make changes to the content.
When in edit mode, the browser changes to display all softkeys available for the system that would
otherwise be difficult to find when recording a macro.
Next to the softkeys display are paging buttons to page through the available softkeys. When used,
these paging buttons will not be stored as content in your macro.
In addition, a new set of macro editor softkeys are displayed while in edit mode including:
• {Loop Begin} - inserts a loop start command.
• {Loop End} - inserts an end command for a loop with a limited number of iterations. An infinite
loop is assigned when you use “0” for the iterations.
• {Wait} - inserts a pause.
• {Delete} - removes commands from the macro.
• {Wait for Input} - Inserts a pause in the macro to allow you to enter data. The pause lasts until
you press the [Macro] key again. Then the remainder of the macro will be completed.
• {Done} - exits macro edit mode. You may also use the [Learn] key to enter and exit edit mode.
In edit mode, the cursor in the macro content detail section of the display provides use of the arrow
keys to navigate through the existing content list. Use of the arrow keys will not be stored to the
macro content.
To add content, place the cursor in the section that you want to insert, then add the command. To
delete a command, place the cursor ahead of the content to be deleted, then press the {Delete}
softkey.
Press [Select] when you have completed all editing. Press [Escape] to abort.
22 Storing and Using Macros 269

Play a Macro
You can play a macro from the command line, from the direct selects, run it from a linked cue, or
from another macro.
To play macro 5 from the command line press [Macro] [5] [Enter]. “Running Macro 5” displays
above the command line in live while the macro is running.
To run macro 5 from the macro direct selects simply press {Macro 5}. “Running Macro 5” displays
above the command line in live while the macro is running.
To run macro 5 from cue 1 press:
• [Cue] [1] {Execute} [Macro] [5] [Enter]
If you would like to run multiple macros from cue 1, press:
• [Cue] [1] {Execute} [Macro] [6] [Enter]
• [Cue] [1] {Execute} [Macro] [7] [Enter]
Each macro has to be entered individually. The previous example would result in macros 5 through
7 being executed from cue 1.
To run a macro from another macro, see the example under Create a New Macro from the Display.
Stop a Macro
If you need to stop a macro while running (for example, during an infinite loop) you may press
[Escape] and the macro will stop.
Delete a Macro
You can delete a macro from the macro editor display by selecting the macro and pressing [Delete]
[Enter]. You will be prompted to confirm the deletion. Confirm by pressing [Enter] again, or abort by
pressing [Clear].
For Example:
Delete macro 5 from the macro list.
• [5] [Enter]
• [Delete] [Enter] [Enter]
Or from any display:
• [Delete] [Macro] [5] [Enter]
270 Ion Operations Manual

Chapter 23
Storing and Using Curves
A curve is a relationship between the timing of a fade and the output level of a cue, cue part or
dimmer at each point of time during that fade. By using a non-linear curve, you can create a variety
of effects, accommodate variations and deficiencies in your lighting equipment, alter the transition
ramp, and protect equipment from stress.
This chapter contains the following sections:
• About Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272
• Creating a Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
• Editing Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274
• Applying a Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
• Delete a Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
23 Storing and Using Curves 271

About Curves
You may apply curves to dimmers in patch. Curves may also be applied to cues and to cue parts.
When applied to a cue, the curve impacts only the intensity moves in that cue. When applied to a
cue part, the curve impacts all parameter moves stored in that cue part.
When applied in patch, the intensity transition will follow the ramp defined by the curve during its
fade. This value is determined by referencing the output value of the curve at that percentage and
outputting the curved level rather than the percent level. Up to 100 points of delineation can be
established in a curve, each with its own intensity value if desired.
When applied to a cue, the “percent completion” of the cue is determined by applying the curve’s
output level as the percent completion for all fade calculations. For single-part cues, the calculation
applies only to intensity. For multipart cues, however, the curve applies to all parameters in the part.
Ion provides nine pre-programmed, commonly used curves. They can be edited or copied to a new
curve location. When a pre-established curve is deleted, it will return to its original state.
The curve editor can be accessed by pressing [Displays] {Curve} or from the browser,
Browser>Record Target Lists>Curves. When selected, the curves list will open as a separate tab
and the CIA will show the graphical output of the first curve in the list.
You can scroll through the list using the [Next] and [Last] keys, or you can specify a curve in the
command line.
• {Curve} [9] [0] [4] [Enter] - selects curve 904 from the list and displays its shape in the
CIA.
272 Ion Operations Manual

Creating and Editing Curves
Creating a Curve
When you have opened the curves display (see About Curves, page 272), you can select a curve
or create a new curve by pressing:
• {Curve} [x] [Enter]
If the curve is already stored, the contents are displayed in the CIA. If this is a new curve, a linear
curve is displayed.
Pre-established Curve
New Default (linear) Curve
23 Storing and Using Curves 273

Editing Curves
Using the Keypad
Once selected and displayed in the CIA, you can edit a curve from the keypad. Points are
established in increments of five. You can add more points from the keypad.
• [3] [At] [1] [Enter] - adds control input point “3” and sets its curve level at 10%.
• [7] [7] [At] [Full] [Enter] - adds control input point “77” and sets its curve level at full.
You can specify points and adjust their levels in the command line or you may use the keys below
to alter the curve:
• [Page ] - selects the next fade completion point.
• [Page ] - selects the previous fade completion point.
• [Level Wheel] - adjusts the output level of the selected point.
• [Page ] - raises the selected point’s output by 1%.
• [Page ] - lowers the selected point’s output by 1%.
• [Full] - sets the selected point’s output to full.
• [Out] - sets the selected point’s output to zero.
• [At] [+][+]- raises the selected point by the amount for +% established in setup.
• [At] [-][-]- lowers the selected point by the amount for -% established in setup.
Using the curve display
Once a curve is displayed in the CIA, you can press {Edit} to edit the curve in the editor display.
In the curve editor you can trace the desired shape of the curve using the mouse on the screen. As
you progress through drawing the curve, intensity values will be added for existing points on the
curve. If you add points to the curve (from the keypad) those points will be adjusted as well.
You can also toggle between an “interpolated” or “stepped” curve shape. Ion defaults to
“interpolated”. To switch to “stepped”, press the {Stepped} softkey. Once pressed, this softkey
changes to {Interpolated}, which allows you to switch back.
Below are two examples of the same curve. The first is interpolated and the second is stepped.
Clearing the curve
Interpolated Curve Stepped Curve
At any time, you can clear a curve from the curve editor display by pressing the {Clear} softkey.
This will return the curve to its original linear shape or to its default shape if it is a pre-established
curve.
274 Ion Operations Manual

Applying a Curve
To Channels In Patch
Curves can be applied to any intensity parameter in patch. Once added, the curve number appears
in the channel’s “Curve” column of the patch display.
• [Displays] {Patch} {Attributes} [1] {Curve} [9] [0] [1] [Enter] - applies curve 901 to
channel 1 intensity.
• [Displays] {Patch} {Attributes} [2] [Thru] [8] {Curve} [2] [Enter] - applies curve 2 to
intensity for channels 2 thru 8.
• [Displays] {Patch} {Attributes} [1] {Curve} [At] [Enter] - removes the curve from
channel 1.
To Cues
Curves can also be applied to cues or cue parts in Live/Blind. This affects the percent completion of
the cue or part by applying the curve’s output level as the percent completion for all fade
calculations. Once added to a cue, the curve number appears in the cue’s “Curve” column of the
cue list in the playback status display.
• [Cue] [5] {Curve} [4] [Enter] - applies curve 4 to cue 5.
• [Cue] [4] [/] [6] [Thru] [9] {Curve} [9] [0] [6] [Enter] - applies curve 906
to cues 4/6 through 4/9.
• [Cue] [5] {Curve} [At] [Enter] - removes any curve from cue 5.
• [Cue] [8] [Part] [3] {Curve} [6] [Enter] - applies curve 6 to part 3 of cue 8.
Delete a Curve
While in the curve display, you can delete a curve in the following ways:
• [Delete] {Curve} [3] [Enter] [Enter] - deletes curve 3 from the list.
• [Delete] {Curve} [9] [0] [1] [Enter] [Enter] - since curve 901 is a pre-established
curve, this command will return curve 901 to its default state, thereby removing any
edits to it.
• [Delete] [Enter] - deletes the currently selected curve.
23 Storing and Using Curves 275

276 Ion Operations Manual

Chapter 24
Using Show Control
Ion supports MIDI Show Control, MIDI and SMPTE Time Code, Serial (RS-232) commands, Analog
Inputs and Relay Outputs, and Real Time Clock (RTC).
This chapter contains the following sections:
• About Show Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
• Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
• Time Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
• Real Time Clock (RTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
• Analog Inputs and Relay Outputs . . . . . . . . . . . . . . . . . . . .283
• MIDI Show Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
• Serial (RS-232) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286
24 Using Show Control 277

About Show Control
The Ion Show Control system is made up of MIDI Show Control, Serial (RS-232), Time Code (MIDI
or SMPTE), Analog Inputs and Relay Outputs, and Real Time Clock (RTC).
MIDI Show Control and Serial require minimal setup from Ion and will be discussed at the end of
this chapter. Time Code, Analog Inputs, and RTC require the use of the Show Control Display,
which is accessed by pressing [Displays]>{Record Target Lists}>{Show Control Display}. The
Show Control Display allows for the creation of event lists.
Setup
Ion provides user-definable settings for show control which can be accessed by pressing
[Displays]>{Setup}>{Show}>{Show Control}. For more information, see Show Control, page 98.
Events
An event consists of a time or address, and an action. An event plays back (or “fires”) when the
clock reaches or passes the specified event time, or an input is seen on an address. Multiple events
can be fired at the same time.
Ion supports three event actions: run a cue, control a submaster, and fire a macro. Cues can be run
from any cue list and will play on their assigned fader. Submasters can be bumped, turned on, or
turned off. Submasters do not have to be assigned to a fader. Macros execute without interaction
with the command line. If another macro is fired before the first macro completes, the first macro will
finish its action before the second is started.
Internal vs. External Time
The Ion Show Control system makes use of two timing sources, internal and external. The different
protocols use internal and external clocks in different ways.
Time Code (MIDI or SMPTE) normally requires timing information from an input source, like a show
control gateway. Ion can receive MIDI Time code via the MIDI input on the rear of the console. This
timing source is referred to as external time, since it is coming from a source external to Ion.
If the external time source stops for any reason, each Time Code event list within Ion has an internal
timing source which will assume control, if enabled. This internal timing source requires three
pieces of information to determine how to generate its timing: first time, last time, and frame rate.
When the internal clock reaches the last time, it will reset to the first time and continues running.
Although external timing may run faster or slower than real time, the internal clock runs only at real
time.
Analog uses external time only.
Real Time Clock uses internal time only. Since that timing information doesn't come to Ion from an
external source, it is important that all the correct information for time zone, latitude, and longitude
are properly setup in the Eos Configuration Utility.
278 Ion Operations Manual

Programming an Event List
Getting started with an event list is the same regardless for which Show Control protocol you are
using.
To program an event list in Ion, you first must open the show control display. Go to:
• [Browser]>{Record Target Lists}>{Show Control Display}
Create an event list by specifying it in the command line. This display follows the “Cue List/
Cue” structure in calling out Event Lists/Events.
• [1] [/] [Enter]
Specify what the list will respond to (MIDI, SMPTE, Analog, or RTC).
• [1] [/] {Type} {MIDI} [Enter]
Define the group or source.
• [1] [/] {Source} [8] [Enter]
Activate the internal and/or external timing functions (see Internal vs. External Time, page
278). These functions are toggle on/off states.
• [1] [/] {Internal} {External} [Enter]
When defining an event list it is feasible to enter multiple commands in the same command line.
This can speed your programming of an event list. For example:
• [2] [/] {Type} {MIDI} {Source} [5] [Enter]
Once the list is created, you will then need to create the specific events. Those steps will vary
depending on what protocol is being used.
24 Using Show Control 279

Time Code
Ion has time code functionality based on a timing source and a list of events that execute at specific
times of that timing source. You can compile event lists and have them play back later while
following a timing source.
Time code lists can receive timing data from either SMPTE or MIDI sources. Ion accepts up to 32
SMPTE sources and 32 MIDI Time Code (MTC) sources (each are numbered from 1-32).
Enabling Time Code
Ion has global enablers for MIDI Time Code and SMPTE. These are found in Setup, Show Control,
page 98.
If the MIDI Time Code setting is disabled, all MTC event lists are disabled as well. If enabled, all
MTC lists are enabled. The same is true for SMPTE.
Timing Data
Timing data is given in the form of (hours) : (minutes) : (seconds) : (frames). Therefore a timing
value of 06:25:15:20 would be 6 hours, 25 minutes, 15 seconds, 20 frames.
The number of frames per second is determined by the timing source and the event list must be set
to this same number of frames when programming. Number of frames can be 24, 25, or 30.
Color coding
The color of the time in the “Status” column of the event list display indicates the source of the
timing data. The colors and indications are:
Green - Valid external timing is being received.
Red - The internal clock is the data source and is running.
Grey - No timing data is available.
280 Ion Operations Manual

Enabling the Clocks
The internal and external clocks can be enabled separately for each time code list. If you enable the
external clock only, events will play back as long as valid timing data is received. When the timing
data stops, the events will stop.
When you enable the internal clock only, it starts running immediately and triggers events
appropriate to the time.
When both internal and external clocks are enabled, the internal clock does not start running until
the first valid external time is received. After that, it will run whenever the external time source is
absent.
Loop times
First and last times define the overall loop. Times can be set anywhere from 00:00:00:00 to
23:59:59:29. When external time is being received, Ion ignores these times. However, you should
still set them to match whatever loop times the external clock is using.
Internal clock
You can set the internal clock at any time by pressing [Time] and entering a time.
Programming a Time Code Event
Define the first time and last time for the event list (times are given as 00:00:00:00).
• [1] [/] {FirstTime} [2] [0] [1] [5] {LastTime} [2] [0] [4] [5] [1] [5] [Enter]
Specify the number of frames per second (FPS) used by the timing source (24, 25, or 30).
• [1] [/] {FrameRate} [2] [5] [Enter]
Specify the timing for the event.
• [4] [Time] [2] [1] [4] [5] [1] [6] [Enter]
Now create the events that the list will trigger.
• [1] [Cue] [2] [Enter]
• [2] [Cue] [3] [Enter]
• [3] [Sub] [5] [Enter]
You can also add or remove frames from events.
• [1] [Thru] [5] [Time] [+] [5] [Enter]
Depending on your time settings, Ion will look for an input time (or start its own internal
clock) and events will play back at their specified times.
Learn Mode
If you specify an event list in the command line, you can press the [Learn] hardkey to activate learn
mode for that list. When in learn mode, an event is created with the current list time whenever a cue
is activated, a submaster bump is pressed, or a macro is run.
If [Learn] is pressed while viewing any other screen than the show control display an empty event
will be placed on all event lists that are in learn mode.
Multiple time code lists can be in learn mode simultaneously, each with their individual times.
Execution While Editing
If the internal or external clock is running, events will fire, even if you are in the edit screen. As soon
as an event is created, the event list is resorted and the new event is eligible for playback.
24 Using Show Control 281

Real Time Clock (RTC)
Ion has the ability to run Real Time Clock (RTC) events. RTC events are used to run a cue,
submaster, or macro at a specific time on specific days. RTC events can run at a certain time of
day, like 5:00pm on Tuesdays, a certain date, or at a time based off of astronomical events, such
as sunrise and sunset.
Enabling Real Time Clock
RTC is enabled or disabled in Setup. See Show Control, page 98 for more information.
For RTC events to work properly, time zone, latitude, and longitude should all be setup correct.
Those settings are found under the General tab in the Eos Configuration Utility. For more
information see General Settings, page 296.
Real Time Clock Events
RTC events are created using the Show Control Display. RTC events consist of a time field, a day
or date field, and an action. Time for RTC events can be specified as local time or as time relative
to the astronomical events, sunrise and sunset. Local time is displayed in the 24 hour format. For
example, if you want an event to run at 2:50pm, you would need to set it for 14:50.
Programming Real Time Clock Events
Define the Time and Data for each event.
• [1] [Time] [1] [5] [0] [0] {Days} {Mon} {Wed} {Fri} [Enter] - sets the time for 3:00pm
on Mondays, Wednesdays, and Fridays.
• [2] [Time] {Before Sunset} [3] [0] {Days} [1] [+] [2] [+] [3] [+] [6] [Enter]- sets the
time for 30 minutes before sunset.
• [3] [Time] {After Sunrise} [6] [0] {Date} [3] [0] {Month} [1] [0] {Year} [2] [0] [0] [8]
[Enter]- sets the time for an hour after sunrise on October 30, 2008.
Note:
Days of the week can either be entered in from their softkeys, or you can enter
them in from the keypad. Monday is 1.
Creating the action for each event is the same as Time Code.
• [3] [Cue] [1][2] [Enter]
282 Ion Operations Manual

Analog Inputs and Relay Outputs
Analog Inputs
Analog inputs are available on the Ion.Each analog event in the event list consists of a port address
and an action. There is a global enable for all analog inputs in Setup, see Show Control, page 98.
You will also need to configure set the group and address for the port. See Contact Closure (remote
trigger connector), page 305.
Analog Input Events
Analog Input events fire when the analog input passes a certain level. Action types supported are
the same as Time Code; run a cue, control a submaster, and fire a macro.
Create an Analog Input Event where an input on address 1 will fire Cue 10.
• [4] [/] [1] {Address} [1] [Cue] [1] [0] [Enter]
If you select the submaster option, you will have an additional option of fader, which will map the 0-
10v input to the level of a specified submaster.
Relay Outputs
Relay outputs are available on the Ion. Relay outputs are also often called remote triggers, contact
closures, or contact outputs. To configure, see Relay Out (remote trigger connector), page 305.
Relay outputs are controlled by external links in cues. See Using the Execute List, page 164.
MIDI Show Control
Ion has two MIDI ports on the rear of the console. For configuring the ports. see MIDI, page 305.
Data Sources
MIDI Show Control (MSC) receives data from a MIDI input source. There are 32 available MIDI
sources, numbered 1-32. MIDI consists of many types of data, but MSC looks only at MSC data.
Other MIDI transmitted data is ignored by MSC.
MIDI Show Control Devices
MIDI Show Control data carries a device ID within the data packet. MSC setup allows for the
specification of two device IDs: one for reception and one for transmission.
Only MSC data with the correct receive device ID, or an ALL CALL ID, will be interpreted by Ion.
All outgoing MSC data contains the specified transmit device ID within.
24 Using Show Control 283

Ion Command Interpretation
When Ion receives a command from a MIDI source, it will look for and support the following MIDI
commands in the following ways:
• Go Runs a cue
• Stop Pauses a cue
• Resume Resumes a paused cue
• Set Controls a submaster, playback, or grandmaster
• Fire Runs a macro
The cue-related commands (go, stop, resume) affect Ion based on the cue and list fields also
contained within the MSC data. Cue and list fields will correspond directly to the Ion cues and cue
lists. In the command/effect tables below, if a field is present in the MSC data, the name is indicated
(such as “Cue” or “List”). If it is not present in the data, a “-” is indicated. For example, “Cue -”
implies that a cue is specified in the data, but not a list.
Go
When accompanying a MIDI “Go” command, data for the following fields will result in the following
effects:
Stop
When accompanying a MIDI “Stop” command, data for the following fields will result in the following
effects:
Resume
Cue Data
Field
List Data
Field Effect
Cue List Runs the specified cue in the specified cue list
Cue - Runs the specified cue in the default cue list
- List Runs the next cue in the specified list
- - Runs the next cue in the default cue list
Cue Data
Field
List Data
Field Effect
Cue List Stops the specified cue & list (if running)
Cue - Stops the running cue from the default cue list
- List Stops the current cue from the specified list
- - Stops all cues
When accompanying a MIDI “Resume” command, data for the following fields will result in the
following effects:
Cue Data
Field
List Data
Field Effect
Cue List Resumes the specified cue & list (if stopped)
Cue - Resumes the specified cue in the default cue list
- List Resumes the current cue in the specified list
- - Resumes all stopped cues
284 Ion Operations Manual

Set
The “Set” command allows MSC to control potentiometers using both a numeric control number
(which specifies the potentiometer) and a data field (which controls the level: 0-100). Control values
are as follows:
Accompanying any of these indications in the MSC data, a numeric value of 0-100 would set the
specified potentiometer to that level.
All other control values are ignored.
Fire
Control
Value Indication
1-127 Submaster 1-127
128 Primary playback in
129 Primary playback out
510 Grandmaster
This command fires a macro. MSC supports macros 1 through 127 only. Therefore a numeric value
of 1 - 127 would accompany this command.
24 Using Show Control 285

Serial (RS-232)
The serial interface allows RS-232 commands to be sent to Ion through Ion’s serial port.
Enabling Serial
Receiving serial commands can be enabled in Setup, see Show Control, page 98. Serial is enabled
by default. You will also need to tell the console which serial group(s) that it will be listening to.
Serial Commands
All text will be stored until a carriage return, a “\r” or “#”, is encountered to show the end of the
command. The carriage return will act as the [Enter] key for the command line. If the text begins
with a “$”, the text that follows until the carriage return will be sent to the command line for user 0
and processed as if that user had typed it. For example:
• $ Chan 1 Thru 10 At Full /r – sets channels 1 through 10 to full manually.
All other text that doesn’t start with a “$” will be sent to the Ion event handler. Here are a few
examples:
• Go 1 – fires playback 1
• Cue 1 2 – run cue 2 from list 1, on the appropriate fader
• Cue 1 – fire pending cue from list 2
• GoCue0 1 – clear playback 1 (fires cue 0)
• Release 1– release playback 1
• Off 1 – turn playback 1 off
• Resume 1 – resume playback 1
• Assert 1 – assert playback 1
• Stop 1 – stop playback 1
• Stop Cue 1 2 – stop cue 2 from list 1 if it is running
• Stop – stops all
• Resume Cue 1 2 –resume cue 2 from list 1 if it is stopped
• Resume – resumes all
• SubAssert 1 – assert submaster 1
• SubUnload 1– unload sub 1
• SubDown 5 - presses sub 5’s bump button down
• SubUp 5 – releases sub 5’s bump button
• SubMove 1 50 - sets sub 1 to 50
• PlaybackMove 1 50 - sets playback 1 to 50 percent
• Grandmaster 1 100 - set Grandmaster 1 to full (there’s currently only 1 Grandmaster)
• Macro 1 - fires Macro 1
Note:
Text requires a carriage return to terminate the command line.
286 Ion Operations Manual

Chapter 25
Multiple Users
Ion can be set to act as a separate user from other consoles on the Ion system, or it can be set to
act as the same user as another console. This is done by changing the user ID.
This chapter contains the following sections:
• About User ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
• Assigning User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288
25 Multiple Users 287

About User ID
When multiple users are on the Eos or Ion network, they can all act as one combined user, as all
separate users, or any of the varying degrees between.
Any Ion console, RPU, Eos console, RVI or client PC can be a separate user on the Eos/Ion
network. Certain Eos/Ion devices work well as independent users while others are intended to
share a user ID with another device. For example, consoles and RPUs are likely candidates for
working with a unique user ID while RVIs and client PCs can be useful sharing an ID with another
device to track programming information from a second location.
Eos/Ion devices sharing User IDs will share certain data, while those with different IDs will not.
Below are the differences in multi-console data depending on User ID.
Data shared between Eos/Ion devices with the same User ID
• command line
• null channels in live
• selected channels
• filters
• selected cue
• live/blind mode
• setup>desk settings
Data specific to the Eos/Ion device, regardless of User ID
• current slider page
• current encoder page
• focus on displays without command line
• display configuration (layout, format, visible parameters, flexichannel)
• paging without changing selected target or channels
Data identical between all Eos/Ion devices, regardless of User ID
• all stage levels and edits
• all data stored in the show file
• playback, sub and grandmaster contents and progress
The default User ID for any Eos/Ion device is 1. You may change this based on your preference to
allow/restrict the functionality described above.
Assigning User ID
User ID can be defined in setup (see {Displays}, page 103).
When multiple programmers are working on an Ion system, partitioned control can be used to
restrict a specific user’s access to certain channels. This can help avoid overlapping control of
channels by multiple programmers at once.
For more information on partitioned control, see Using Partitioned Control, page 289.
288 Ion Operations Manual

Chapter 26
Using Partitioned Control
Partitioned control allows discrete control and programming of channels between multiple
programmers. Partitions can restrict access to specific channels by a particular user.
This chapter contains the following sections:
• About Partitioned Control. . . . . . . . . . . . . . . . . . . . . . . . . . .290
• Setting Up Partitioned Control . . . . . . . . . . . . . . . . . . . . . . .290
• Partition List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
• Creating New Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . .291
• Using Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292
26 Using Partitioned Control 289

About Partitioned Control
When multiple programmers are working on an Ion system, partitioned control can be used to
restrict a specific user’s access to certain channels. This can help avoid overlapping control of
channels by multiple programmers at once.
Channels can be included in more than one partition.
Partitions only affect which channels a user has access to. They do not affect playback. As cue
attributes are shared, in most instances programmers using different partitions will choose to store
into different cue lists.
How to Use Partitions
The primary use of partitioned control is to allow more than one programmer to work on a show file
at the same time without the risk of one user storing data for another user’s partitioned channels.
The most common example of this situation is when one user is programming moving lights while
another user programs conventional fixtures. Partitioned control allows these users to divide the
channels between them so they may work simultaneously. If one user stores data using [Record]
or [Record Only], partitioned control will guarantee that only data for their partitioned channels will
be stored. Data for channels not in the partition will be ignored when any store commands are
performed.
Setting Up Partitioned Control
Partitioned control is enabled or disabled in show settings (see Show Settings, page 95). Partition
defaults to “Disabled”. Enabling or disabling partitioned control is a systemwide setting, so all
consoles on the network will adhere to the setting.
Partition List
To view the partition list, click the {Partitions} button in Show Settings. This display lists all existing
partitions. There are four pre-programmed partitions in Ion, they are:
• Partition 0 - No channels and no fader control. This is the default for all users when partitioned
control is enabled for the first time on a show. To gain control, you must select a different
partition.
• Partition 1 - All channels. Allows the user access to all channels.
• Partition 2 - Single Parameter Channels. Allows the user access to only channels with a
single parameter.
• Partition 3 - Multiple Parameter Channels. Allows the user access to only channels with
multiple parameters.
To select a partition in the list, enter it in the command line.
• [Partition] [2] [Enter]
If partitioned control is enabled, this will now be your assigned partition.
290 Ion Operations Manual

Creating New Partitions
To create a new partition, press:
• {Partition} [x] [Enter] - where “x” is a number that does not yet exist in the partition list.
This will create a new partition, highlight it in the list, and (if partition is enabled) assign it as your
partition.
To assign channels to that partition, enter them in the command line:
• [1] [Thru] [9] [6] [Enter]
You can also use [+], [-], and [Group] to further modify the channels in the partition. When adding/
subtracting channels to a partition, if you do not use [+] or [-] before channel numbers, the numbers
will replace the channels in the partition, rather than adding to or subtracting from them. This
overwriting does require a confirmation (if enabled in setup).
When you are finished, you can press {Done} to return to the setup screen.
Deleting Partitions
To delete any partition, simply type the syntax in the command line:
• [Delete] {Partition} [5] [Enter] [Enter] - deletes partition 5 from the list.
Preprogrammed partitions cannot be deleted.
26 Using Partitioned Control 291

Using Partitions
When partitions are enabled and a partition is selected, you may only record data for the channels
included in the partition, with the exception of parking and unparking channel parameters or playing
back cues. If you try to control a channel that is not in your partition, you must confirm that you want
to control that channel. You will not, however, be able to store information for that channel.
If you select a range of channels and set them to a level and some of those channels are not
included in the partition, you must confirm the command. After which, the command will be allowed
on the channels not in the partition
When you record a target (cue, preset, palette), only those channels that are partitioned to you are
recorded. Other programmers’ record actions to the same target can add to it (they do not replace
it) unless channels are shared. When shared, the last value provided at the point of the record
action will be stored.
Partitions in Playback
In general, partitions do not affect playback. In Ion, how faders are configured and what is loaded
to those faders is shared across all control devices.
When cues are played back from any console, regardless of partitions, that cue will be played back
in its entirety. This ensures that while partitions are used, any user can activate a cue and all users
will see that cue played back on the system.
To facilitate partitioned programming, Ion allows you to change the fader number of the master
fader pair on any console. This allows you to have different cue lists on the master fader pair of any
consoles on the network. Using this feature, programmers can work within their partitions, using the
master fader pair for their specific cue list, without affecting the cue list that is loaded to the master
fader of another console.
Flexichannel in Partitioned Control
When partitioning is enabled, a new flexi state, "Partitioned" is available as a softkey. When this is
enabled, the flexi state is limited to only those channels defined in the current partition. This view
may be further modified by use of the remaining flexi states.
292 Ion Operations Manual

Appendix A
Eos Configuration Utility (Eos Shell)
Overview
This appendix covers the Eos Configuration Utility (ECU) and
its use. This is a component of the Eos Lighting Control System
and is used for both system configuration and performing basic
level test functions of your Ion console. These instructions
illustrate how to use the utility, but do not specify what changes
to make as these are based on your preferences and can be
changed to suit your control needs.
Ion uses the ECU for the same purposes as Eos. There is a section of the ECU dedicated solely to
the Ion console. It grants you the ability to configure the DMX, MIDI, contact closure, and relay ports
on the back of the console. For more information see Ion, page 305.
What the Utility Does
Here is a brief list of some of the actions that can be performed from the ECU.
• Configure the IP address of the console
• Configure the services to provide IP addresses to other devices
• Configure the monitors
• Set the date, time, time zone, and location
• Change the system language or the alphanumeric keyboard layout
• Choose to boot the console in Primary, Client, Backup or Offline mode
• Perform a simple button and encoder response test
• Update software
• Save log files
• Deep clear the system
• Backup show files
• Using the file manager
A Eos Configuration Utility (Eos Shell) 293

Eos Configuration Utility Reference
During the boot process, a countdown timer will appear near the Ion logo. There are two ways that
you can force the console to boot into the utility instead of the main console application. You can
either click with a mouse the countdown timer itself or you can hold down “e”, “o” and “s” at the
same time on a connected alphanumeric keyboard. You have 5 seconds to do either one if you want
to go directly to the configuration utility.
Otherwise, you can always enter the ECU from the Ion application by choosing Browser>Exit Ion.
Starting Screen
Clicking Primary will
start the console in
Primary mode
Clicking Client assigns
this console as a client.
Clicking Offline will put
the console in offline
mode and will not interact
on the network with other
devices.
This is the starting screen of the utility. From here you can choose to boot the console in one of
several different modes, change various settings, or shutdown the console.
Primary
This is the mode for using a single console on a network. On a system with multiple consoles, the
primary is the console that client and backup consoles synchronize with, making it the source of all
information a client or backup console sees on the network.
Primary mode can be run on Eos, Ion, and RPUs (Remote Processor Unit).
Client
Ion Welcome Screen / Eos Configuration Utility entry point
Clicking Backup will assign this console
as a backup to a processor in Primary
mode.
Clicking Settings will take you to the
settings and screens of the Eos
Configuration Utility (ECU) described
below.
Clicking Shutdown will shutdown the Ion
console after a confirmation.
A device set to client mode can act as a remote controller or remote video station for a system. A
client device cannot output to the lighting system. Only a primary or backup processor can do this.
User ID determines some interaction between the client and the primary console. If the client and
the primary console have the same User ID, they will act as one. If they have different User IDs,
they will have separate command lines.
Client mode can run on Eos, Ion, RPUs, RVIs, and personal computers with the client dongle.
294 Ion Operations Manual

Backup
Backup mode requires a primary console be online to synchronize. Once this is done, a backup
console intakes all show data for use in the event that it needs to assume control of the lighting
system.
The main difference between backup and client modes is what happens in the event of primary
processor failure. If the primary fails, a backup will automatically ask if you want it to take control as
the master of the system or if you want to troubleshoot the problem.
User ID determines some interaction between the backup and the primary console. If the backup
and the primary have the same User ID, they will share the same command line. If they have
different User IDs, they will have independent command lines.
Backup mode can be run on Ion consoles and Ion RPUs (Remote Processor Unit). For more
information on Ion backup systems, see Multi-console and Synchronized Backup, page 307.
Offline
Offline mode puts the software in a state where there is no network activity, no control, no
connections with other consoles or any other network devices.
This mode is primarily intended for offline editing of a show file.
Offline mode can be run on Eos, Ion, RPUs, RVIs, and personal desktop or portable computers.
A Eos Configuration Utility (Eos Shell) 295

General Settings
Device Name
This specifies the name the Ion console will use to identify itself on the network to other devices.
Examples might be Booth Console and Tech Table.
Time
The time the console is using. This can be set manually (direct data-entry) or via SNTP (Simple
Network Time Protocol) time service. Please see Network Settings, page 299 for more information.
The time is displayed in a 24-hour format as HH : MM : SS.
Date
The date the console is using. This can be set manually (direct data-entry) or via SNTP (Simple
Network Time Protocol) time service. Please see Network Settings, page 299 for more information.
The time is displayed as MM / DD / YYYY.
Time Zone
The time zone the console is using. This is an offset from Greenwich Mean Time (GMT). Each
setting in the pull-down list displays the offset, the name of the time zone and a couple of cities in
that time zone.
Language
If you do have a USB keyboard attached, you
can use either keyboard for the data-entry.
When you click on a field to change the
entry, an appropriate keyboard (numbers
only vs. full alphanumeric) will pop-up to
provide a data-entry method even without a
keyboard connected to the console.
Allows you to select the display language of Ion. Choices are English, German, French, Spanish,
Turkish, Italian, Russian, Japanese, and Chinese.
296 Ion Operations Manual

Keyboard
Allows you to select the language for the alphanumeric keyboard within Ion. Options are English,
German, Italian, Swiss, Norwegian, Turkish, Czech, and Russian.
Show Welcome Screen
When this is checked, the Eos console will boot into the Configuration Utility every time instead of
booting directly into the main Eos application.
Backup Auto Switch
Switches to the backup automatically if the primary should go offline.
Show Archive Path
This is the default location to save show files. The full path must be typed in and specified in a legal
Windows format. The default location is a folder on the D: drive.
If you decide to change this setting, it is recommended that you keep this location on the D: drive.
This will keep show files safe during software updates that may include re-imaging the C: drive.
Share Show Archive
Checking this box will enable you to share the show archive folder on the console with another
console or computer.
Latitude
Allows you to select the latitude the console is using.
Longitude
Allows you to select the longitude the console is using.
A Eos Configuration Utility (Eos Shell) 297

External Monitor Arrangement
The number on the
monitors matches the
number of the video port
on the rear of the console.
Ion allows for up to two monitors. The first time Ion boots with two monitors, it may not display
output to both. You will need to configure the monitors in {External Monitor Arrangement} under
{General} in the ECU.
To configure dual monitors:
Step 1: Click an available monitor once to select it. The monitor will now be outlined in yellow.
Step 2: Click on the open left position under Monitor Arrangement. The second monitor will
drop down into the open left position.
Step 3: Click on {Apply}.
Step 4: Click on {Accept} on the General screen.
Once you launch the Ion application, you will then have displays on both the monitors.
Ion Software Update
Available
Selected
This option is used to update the software of the Ion console itself. It does not affect or update the
software in any other networked device such as a Net3 Gateway.
When you click on {Software Update}, the Ion console looks at the root directory of any connected
USB drive for an Ion console software update file.You will be shown the names of any updater files
found on the drive. Select the file you would like to install and click the {Install} button, or click
{Cancel}.
You will also receive a message if no software update file can be found.
298 Ion Operations Manual

Network Settings
Ion Console IP Settings
This is where you specify the IP
address to be used by this
console (manually) or how it
acquires an IP address
(dynamically via a DHCP
server or a link-local address).
Net3 Services Settings
These are settings for the
network services that may be
running on your Ion console.
If you are unable to enable
them, they are not currently
installed on this console.
Network Adapter
This reports if the network adapter is “Online” (configured, connected to a network and operational).
It reports as “Offline” if any one of the above conditions is not true.
Protocols
This is for selecting which protocols the console will output and which ones are included in the
default.
ACN Priority
This sets the control priority for ACN data from this console. The valid range for this setting is 1
(lowest) to 200 (highest). This is the reverse of ETCNet2.
ETCNet2 Priority
This sets the control priority for ETCNet2 data from this console. The valid range for this setting is
20 (lowest) to 1 (highest). This is the reverse of ACN.
Local DMX
This enables DMX output from the local ports on an Ion console.
Avab UDP
This sets the subnet for Avab UDP data from this console. The valid range for this setting is 0-9.
ArtNet
This sets the subnet for ArtNet data from this console. The valid range for this setting is 0-15.
Enable Output in Offline Mode
Checking this box allows for output in offline mode for use with a visualization program.
A Eos Configuration Utility (Eos Shell) 299

Net3 Settings
All settings in this section require a reboot of the console before they will take effect. If this section
is greyed out, or you are unable to change any settings, you don’t have Net3 Services installed on
your console.
Enable Net3 Services
Net3 Services are a suite of services that provide infrastructure support for a Net3/ACN network.
Those services are a dynamic IP address server, a network time server and a file server. Each of
these services are described below.
Unchecking this box acts to disable all of the Net3 Services. Checking the box only enables
services selected to be active.
Enable Address Server
Net3 Services uses a DHCP (Dynamic Host Configuration Protocol) address server. DHCP is a
TCP/IP protocol that dynamically assigns an IP address to a network device when it requests one.
This is a small and simple DHCP server that is intended to be used on non-routed networks. It will
not serve IP addresses across a router.
CAUTION:
Clicking in the enable box will start the DHCP server in the Ion console. It will use the settings below
to determine which IP addresses it gives out.
• IP Address Pool - This sets the starting IP address of the range of IP addresses the DHCP
server will give out.
• Pool Size - This sets how many IP addresses the DHCP server will give out. A setting of 500
means it will give out IP addresses to the first 500 devices that ask for an IP address.
• Subnet Mask - This sets the logical network size vs. the device address. ETC’s default is
255.255.000.000 (class B). This is the subnet mask that the DHCP server will give to network
devices.
• Gateway IP - This specifies the IP address of a router if one is present on your network. This
is the gateway IP address that the DHCP server will send to network devices to use.
If you are on a flat or non-routed network, the Gateway IP address should match the IP
address of the device. In order to configure this DHCP server to send out matching gateway
IP addresses, configure this gateway IP address to match the IP Address Pool field.
Then the DHCP server will give out a gateway IP address that matches the IP address.
Enable SNTP Time Server
Clicking in the enable box will start the SNTP (Simple Network Time Protocol) service. You
determine if the service is running as a client (receiving time messages) or as a server (sending
time messages) during the installation process.
Enable TFTP Server
There should only be a single DHCP server active on a network. It is possible to
start more than one DHCP server on a single network (nothing is built-in to DHCP
servers to prevent this from happening). If this occurs, it will result in unstable
conditions and possibly result in network communications failures.
Clicking in the enable box will start the TFTP (Trivial File Transfer Protocol) server.
• Root Path - This sets the directory where files are to be served through TFTP. This must be
the full path to the directory, including drive letter. For example: C:\etc\nodesbin
300 Ion Operations Manual

Ion IP Settings
These are the settings that determine the method to get an IP address
and/or the actual IP address information that Ion uses for network
communication.
Enable DHCP
If DHCP is selected, the “in use” IP
address information is displayed.
Clicking in the enable box will set Ion to get its IP address dynamically
from a DHCP server. While the console is starting, it will ask for an IP
address from a DHCP server. If one responds, it will use the assigned IP address.
If no DHCP server is available, Ion will default to a self-generated link-local IP address in the range
of 169.254.x.y. The IP address used by Ion in this configuration may change dynamically as
needed. A change should typically only occur when there are changes to the network configuration
or to resolve an IP address conflict.
Enabling or disabling the DHCP setting will require you to reboot Ion for the new setting to take
affect.
Note:
IP Address
If DHCP is disabled, you set the Ion IP address here. This is a static IP address and will remain set
until changed by a user. Ion defaults to an IP address of 10.101.100.101.
If DHCP is enabled, this field will display the IP address that is being used by the console (whether
it is served via DHCP or a self-generated link-local IP address).
Subnet Mask
If DHCP is disabled, you set the Ion subnet mask here. This is a static setting and will remain set
until changed by a user. Ion’s default subnet mask is 255.255.0.0.
If DHCP is enabled, this field will display the subnet mask that is being used by the console
(whether it is served via DHCP or a self-generated link-local IP address).
Gateway
If DHCP is disabled, you set the gateway IP address here. This is a static gateway IP address and
will remain set until changed by a user. Ion’s default gateway is 10.101.100.101.
If DHCP is enabled, this field will display the gateway IP address that is being used by the console
(whether it is served via DHCP or a self-generated link-local IP address).
Advanced Features
Enable Sensor Feedback
Clicking in the enable box will allow Eos to receive feedback over the network from a Sensor+
rack.This option is “Enabled” by default. See About Address, page 250 for more information.
Enable RDM
You cannot set Ion to receive an IP address via DHCP and act as a DHCP server
at the same time. It can either send dynamic addresses or receive them, but not
both at the same time.
Clicking in the enable box will allow Eos to perform RDM functionality including device discovery.
See {Patch} Display and Settings, page 68 and About Address, page 250.
A Eos Configuration Utility (Eos Shell) 301

Maintenance and Diagnostics
Deep Clear
{Deep Clear...} functions in much the same way that New does from the File menu or Reset
System does from the Clear menu (both are found within the browser). A deep clear is
automatically performed when new software is installed. Sometimes it is useful to perform a deep
clear between updates.
The advantage of deep clear is that you can clear all console data before reloading the console’s
current state during boot. This is helpful if you are moving a new console onto the network and don’t
want it to suddenly take control of a system or if you somehow end up with a corrupt show file that
is causing issues upon boot.
It’s worth noting that Deep Clear (like Reset System and File>New) does not reset any of the
settings in the Eos Configuration Utility (ECU) like its operational mode or IP address settings.
Everything in the ECU remains as it was last configured.
Save Logs...
Clicking on the {Save Logs...} button displays a dialog box prompting you to save the console log
files for troubleshooting purposes. By clicking on the {Advanced} button, you can select or
deselect any of the various individual log files to be saved.
Clicking {Next} you will see a drop down menu to select the target export location from any
available write-enabled removable media such as a USB drive.
If you experience software problems with your system that we are unable to reproduce, sending
these log files to ETC Technical Services (see Help from ETC Technical Services, page 3) can help
us isolate the issue. As these files can be rather large, unless otherwise instructed, the file that is
useful will be a “.SDMP” file.
302 Ion Operations Manual

Backup Show Archive
{Backup Show Archive...} allows you to either backup the most current version of each show file
or every version of each file to a USB drive.
Restore Show Archive
{Restore Show Archive...} allows you to restore show files from a USB drive.
File Manager
{File Manager} provides a way to manage show files. You can create and delete new folders,
move, and copy files between the console and USB drives.
Upgrade Console
{Upgrade Console...} is used for upgrading the console's outputs.
Network Drives
{Network Drives...} allows you to select an alternative show file storage location on another
console or computer. After setting this location, it will appear as an option within the save and open
dialogs in Ion.
In the {Network Drives...} dialog box, there is a {Add} button for creating a network drive. In the
Add Network Drive dialog box, you are able to select the drive letter that is appropriate, the network
path, examples would be \\IPAddress\ShowArchive or \\DeviceName\ShowArchive, and network
path type, which is either Eos, Ion, or Other. If Other is selected, you will have additional fields to fill
out for Provider, Username, and Password.
Shared Folders
{Shared Folders...} allows you to see if any folders are currently being shared by the console. You
can select the folder and click {Don’t Share} if you no longer want to share the folder. By selecting
{Don’t Share} here, you will also uncheck the box for Share Show Archive in the General tab.
Log Off
This will log off the current user.
A Eos Configuration Utility (Eos Shell) 303

Face Panel Test...
Face Panel Test provides a way to verify the functional state of all of the keys, encoders and sliders
on the Ion console. The screens are very straightforward. For field diagnostics, you shouldn’t need
more than the sections of Ion Keyboard.
Press/move every key and verify that those events register on the diagnostic test screen.
1
2
3
1 2 3
304 Ion Operations Manual

Ion This screen allows you to configure the ports on the back of the Ion console.
Local DMX
This allows you to change the universe or port speed for the two DMX ports on the back of the Ion
console. Universes can be from 1-64.
The default settings are Universe 1 and Universe 2 respectively with both ports set to maximum
speed (recommended).
Show Control
MIDI
Allows you to set the group number for the MIDI In and MIDI Out ports. Group numbers can be from
1-32. Default for both ports is 1.
Contact Closure (remote trigger connector)
Allows you to set the Group and Address In values for the remote trigger input on the back of Ion.
Relay Out (remote trigger connector)
Allows you to set the Group and Address In values for the remote trigger port on the back of Ion.
Remote Trigger
connector pinout
8 7 6 5 4 3 2 1
15 14 13 12 11 10 9
S1
S2
S3
S4
1
2
3
4
5
6
7
8
A Eos Configuration Utility (Eos Shell) 305
9
10
11
12
13
14
15
Ground
Ground
+ 12Vdc
+ 12Vdc

306 Ion Operations Manual

Appendix B
Multi-console and Synchronized
Backup
Overview
This appendix outlines the procedures required to use multiple Ion/Eos control devices (such as an
Ion console, Eos console, Remote Processor Unit (RPU), Remote Video Interface (RVI), or PC with
client dongle) simultaneously on a network. It outlines the setup, configuration, and behavior that is
entailed in an Ion multi-console scenario.
Ion multi-console functionality is also used to provide synchronized backup of your show while
running multiple Ion devices on the network.
Definition of terms
Familiarize yourself with these terms prior to setting up a multi-console system.
Note:
Ion consoles, Eos consoles, RVIs, RPUs, or a PC running Eos with a client dongle
may all be considered active units on an Ion network. For the sake of brevity, the
term “Ion” is used to represent any and all of these options in the following
descriptions.
• Primary - When an Ion is configured as a primary, other Ion devices can connect and
synchronize with it. If using a backup processor, the primary is the Ion that will be backed up.
Only Ion/Eos consoles and RPUs can be set to primary. By default, all Ion consoles will start
up as a primary.
• Backup - This Ion is capable of taking control of the system if the primary fails. You may input
data and run your show from a backup. There can only be one backup in an Ion network and
you must specify which primary it is backing up. Only Ion/Eos consoles and RPUs can be set
to backup.
• Client - Any online Ion that is not the primary or backup is a client. Client data is sent and
received over the network, and clients will synchronize with a designated primary.
• Offline - Any Ion controller that is disconnected from the Ion network. Changes to show data
performed on an offline Ion will not affect the rest of the Ion network or the lighting system.
• Master - The Ion that is currently sending control data to the lighting system is the master. In
most circumstances this is also the primary. Should a primary fail and a backup takes control,
then the backup will be acting as the master.
• Tracking - Any console that is synchronized with a master is tracking. Once a backup takes
control it becomes a master and is no longer tracking.
• User - A user is an Ion defined by a user ID. If it has a unique user ID, the Ion will operate
separate from other Ion devices on the network, but would still track show data. If it shares a
user ID, Ion will synchronize with like IDs. See User ID and multi-console features, page 310.
• System - One primary Ion, one backup Ion, and (if available) multiple clients synchronized
together.
B Multi-console and Synchronized Backup 307

Multi-console setup
When using multiple Ion consoles on the network, you should adjust some of the settings of your
devices to ensure optimal functionality.
Note:
Designate Primary
By default, all Ion devices will boot as a primary. When using multiple devices on the network, only
one should be designated as a primary. Other devices should be configured as the backup (only
one per system) or clients. There can be a maximum of 12 Ion devices connected to a master.
To change this setting, you must exit the Ion software (Browser>Exit Ion) and then designate the
device as primary, backup, or client as described in the ECU appendix (see Starting Screen, page
294).
DHCP Server
DHCP server supplies IP addresses to network devices. Only one Ion device [typically the Primary]
on the network is necessary to do this properly. Therefore you should disable the DHCP server on
all devices except for the intended primary.
To disable the DHCP server on your device see Ion IP Settings, page 301.
Change Device Name
To easily identify your Ion on the network, change the device name to be representative of the
device (such as “Booth Primary” or “Tech Backup”). This is done in General Settings, page 296.
Backup Auto Switch
It is recommended that you perform the following setting changes before
connecting your Ion device(s) to the network. After the changes are complete,
connect to the network and reboot the device.
Switches to the backup automatically if the primary should go offline. This is enabled in Backup
Auto Switch, page 297.
308 Ion Operations Manual

Change IP Address
All Ion consoles by default have the same static IP address. All Ion RPUs also, by default, have the
same static IP address.
Default Ion Console IP Address: 10.101.100.101
Default Ion RPU IP Address: 10.101.95.101
Each Ion device on the network should be given a unique IP address. If running multiple devices of
the same type (for example - two consoles, or two RPUs), you must alter the default static IP
addresses to ensure proper functionality.
Changing the static IP address is done through the ECU (see Network Settings, page 299), on the
“Network” page. Manually change the IP address of any non-primary Ion device by clicking in the IP
Address field and entering the new number from the keyboard. When done, press [Enter].
Note:
It is recommended that you alter the very last digit of the static IP address by an
increment of one for each additional Ion device on the network. Therefore, if the
master ends in “101”, change the backup to end in “102”, a client to end in “103”
and so on.
B Multi-console and Synchronized Backup 309

User ID and multi-console features
Set in Setup (see {Displays}, page 103), User ID is an Ion/Eos-specific identifier that can be set
uniquely for each Ion device or can be shared between multiple devices allowing for shared data
between consoles. The user ID can be set anywhere from 1 to 10.
Ion devices sharing User IDs will share certain data, while those with different IDs will not. Below
are the differences in multi-console data depending on User ID.
Data shared between Ion devices with the same User ID
• Command line
• Null channels in live
• Selected channels
• Filters
• Selected cue
• Live/blind mode
• Setup>desk settings
Data specific to the Ion device, regardless of User ID
• Current slider page
• Current encoder page
• Focus on displays without command line
• Display configuration (layout, format, visible parameters, flexichannel)
• Paging without changing selected target or channels
Data identical between all Ion devices, regardless of User ID
• All stage levels and edits
• All data stored in the show file
• Playback, submaster, and grandmaster contents and progress
The default User ID for any Ion device is 1. You may change this based on your preference to allow
or restrict the functionality described above.
Note:
Multi-console backup
After you have completed the setting changes described above, connect your Ion
device to the network and reboot the device.
Within an Ion system, you have the added bonus of show data backup. The backup on the system
will receive all show data updates and stage levels so that, in the event of a primary failure, the
backup will be capable of taking control of the system without a loss of show data or live output.
310 Ion Operations Manual

Synchronized Backup
Once you have changed settings to facilitate a multi-console system on the network, you may
activate synchronized backup to ensure show data security.
Ion synchronized backup is designed so that during normal operation the primary console controls
the lighting system and any console configured as backup or client synchronize with the primary.
The following activities will synchronize between consoles when operating in a backup system:
• Playback
• Record operations
• Manually set data
• Show file and show data
Only Ion consoles, Eos consoles, or RPUs can function as a primary or backup.
Setting up Synchronized Backup
Before backup is possible, you must have at least two Ion devices (consoles or RPUs only)
connected to the network. One must be assigned as primary and one as a backup.
To assign a backup to a primary:
Step 1: Exit the Ion/Eos environment (Browser>Exit Ion) on the console you wish to act as
the backup. This will send you to the ECU welcome screen.
Step 2: Click on the {Backup} button in the welcome screen. The console will then startup the
software, this time in backup mode. Ion will try to connect to a master console. The
CIA will say “Waiting for Master. One moment please...”.
Step 3: If the backup doesn’t connect after a few moments, click the {Troubleshoot} button
in the CIA. This will open the network configure screen in the CIA.
Step 4: Select a master console from the list on the right. If no masters are available in the list,
a master console is not connected to the network.
Step 5: Press {Change Master}. The backup Ion will synchronize with the master.
B Multi-console and Synchronized Backup 311

The Ion’s LCD displays the current status of the backup.
If the primary goes offline for any reason, the backup will automatically takeover as the master if
backup auto switch has been enabled, See “Backup Auto Switch” on page 297. This happens with
virtually no effect to the backup other than a change in the CIA heading, which will change to the
following status. If backup auto switch is disabled, the backup will tell the user that the master has
gone away and will ask if they want the backup to take control of the system.
If you enter the Network>Configure screen, it will have changed to the following.
Your backup is now acting as the master and is controlling the lighting system.
Note:
If the primary comes back online, it will not retake control of the lighting system.
The primary will wait until it is redesignated as the master and the backup is
reassigned to it.
If at any point you change masters, you must individually reassign any clients to
the new master through the network configure screen.
312 Ion Operations Manual

Backup Scenarios
Console and console
Two consoles can be used to provide backup. Either can be configured as the primary or the
backup. If the primary console fails, the second console will take control with full show data intact.
This is a useful scenario for touring multi-user applications.
RPU and console
One RPU and one console can be used as a backup option. In this configuration, it is
recommended that you set the RPU as the primary and the console as the backup. In this scenario,
should the RPU go offline, you will still have the full functionality of the console user-interface at
your disposal.
RPU and RPU
Two RPUs may serve as primary and backup also. A backup system of this type can support many
client consoles at once, which you may turn on and off as needed without the need to reset to a
different master each time.
This application is ideal for permanent installations requiring synchronized backup.
B Multi-console and Synchronized Backup 313

314 Ion Operations Manual

Appendix C
Remote Processor Unit (RPU)
Overview
This appendix outlines the setup and configuration of your Ion Remote Processor Unit (RPU). The
Ion RPU can be used as a primary, backup, or client processor in an Ion system (see Large System
Riser, page 19). It can also be used for independent playback applications.
Ion RPU ships with the following:
• Remote Processor Unit
• USB Keyboard
• USB Mouse
• Rack Mount Hardware Kit
• IEC Power cords with varying connectors
• Dual-DVI video Y-adapter - (screen resolution of 1280x1024 required)
• DVI (male)-to-VGA (female) adapter
Hardware Setup
Hard Power
Switch
IEC Power
Connector
Rear Panel
Note:
Dual DVI
Ethernet
PS2 Mouse and Keyboard USB
ports
Step 1: Attach the appropriate IEC power cord to the power connector.
Step 2: Attach the dual DVI connector/Y-adapter to the DVI port. If you have VGA monitors,
attach the VGA adapters to the DVI adapter. Do not use the VGA connectors on the
back of the RPU.
Monitor screen resolution must be at least 1280x1024.
Step 3: Connect the USB mouse and keyboard to the USB connectors. If you want to use a
PS2 mouse or keyboard (not provided), you may use the appropriate connectors on
the RPU.
Step 4: Attach a network ethernet cable to the ethernet port.
Step 5: Once all accessories have been connected, you may activate the hard power switch
on the rear panel.
C Remote Processor Unit (RPU) 315

Front Panel
20 userconfigurable
buttons
(default shown)
Start Up
Backlit
indicators
USB port
Soft power
switch
• The soft power switch activates the RPU (check rear panel to ensure power is connected and
hard power switch is on).
• Backlit indicators identify the operating status (master, backup, client, and so on) of the unit.
• USB port is provided for easy show loading to or from a USB storage device.
• 20 buttons are configurable from the Eos Configuration Utility (ECU). They are set to a default
configuration. The label strips for these buttons are removable and reversible. Any changes
to the button configuration can be written on the opposite side in pencil.
After connecting power to the unit, press the soft power button on the front of the console.
By default, the RPU will boot into the Ion environment as a primary. If you wish to designate your
RPU as something other than a primary, you must exit the Ion environment and choose a different
designation from the Eos Configuration Utility welcome screen.
For more information on multi-console terms such as primary or backup, please see Multi-console
and Synchronized Backup, page 307.
316 Ion Operations Manual

Software Configuration
Settings for the RPU can be altered in the Eos Configuration Utility (ECU). The 20 buttons on the
front panel of the RPU are configurable from the {RPU} section of the ECU.
To configure the RPU buttons:
Step 1: In the Ion browser, select File>Exit Ion and confirm the selection. Eos will close and
you will enter the Ion welcome screen.
Step 2: Click on the {Settings} button. This will open the ECU.
Step 3: On the right side of the screen, click on the “RPU” button to enter the RPU button
setup. A virtual display of the RPU buttons is displayed with the current button settings
labeled on each button.
Step 4: Click on a button you wish to alter. A button window will open.
Step 5: Click on the type of button you want it to be (Macro or Hard Key).
• If Macro - Click on the Macro # box and enter the desired macro number from the
keyboard and press enter. Then click {Accept}.
• If Hardkey - Click on the {Hardkey} drop down menu and select the hard key you
wish to use. Then click {Accept}.
Step 6: Repeat this process for any other buttons you wish to reconfigure.
Step 7: To restore the default buttons at any time, click the {Restore Defaults} button.
To import a button configuration:
You may import an RPU button configuration file from a USB device.
Step 1: Click the {Import} button in the RPU section of the ECU. The RPU will search for valid
RPU button file.
Step 2: If a valid file is found, the ECU will ask you if you want to import the settings. Click
{Yes}. The settings will be imported.
Step 3: Click {Ok}.
To export a button configuration:
You may export your RPU button configuration to a USB device.
Step 1: Click the {Export} button in the RPU section of the ECU.
Step 2: If a USB drive is available, the ECU will ask you to choose the desired drive from the
drop down menu. Click on the desired USB drive.
Step 3: Click {Accept}. The button configuration will be saved to the USB drive.
Step 4: Click {Ok}.
For more information on settings in the ECU, please see Eos Configuration Utility (Eos Shell), page
293.
C Remote Processor Unit (RPU) 317

Basic Use Guidelines
Displays
The RPU can be used with either one or two DVI monitors. You can collapse or expand the CIA on
the displays by engaging the scroll lock and pressing F5. If you are using one monitor, you may find
this feature useful in increasing the efficiency of your available display area.
Net3 Services
By default, both Ion and the Ion RPU ship with all Net3 services enabled.
When used in a multi-console backup system, you must disabled Net3 services for the intended
backup device. If the RPU is the intended primary (recommended, see Backup Scenarios, page
313), some Net3 services must be disabled on the intended backup device (console or RPU).
You must disable the DHCP server and TFTP server. You must also change the SNTP server to
“client” to enable time synchronization between Ion devices. All of this is done using the Eos
Configuration Utility (See Net3 Settings, page 300 and Ion IP Settings, page 301).
318 Ion Operations Manual

Appendix D
Remote Video Interface (RVI)
Overview
The RVI functions as a remote user interface to access and modify the contents of an entire Eos/Ion
show file. You may configure the RVI to run Eos/Ion software in “Client” or “Offline” mode.
This appendix outlines the setup and simple configuration of your Remote Video Interface (RVI) for
use with an Eos/Ion Control System.
.
Electrical Specification
• Operating voltage 100-240 VAC, 50-60Hz (2 amps at 120 VAC)
• Ambient temperature and humidity 0 - 35° C, 95% non-condensing humidity, maximum
• Storage temperature and humidity 0 - 35° C, 95% non-condensing humidity
• CE and ETL Compliant
• Installation Category II, indoor use only
• May operate up to 2000 meters altitude
D Remote Video Interface (RVI) 319
Primary
Master
Backup
Sync
Client
Offline

Hardware Setup
Rear Panel
Note:
Note:
Hard Power
Switch
AC Power
IEC connector
Dual DVI
Display
AC Input
100-240 VAC
50/60 Hz 2A
1
2
Electronic Theatre Controls, Inc.
Middleton, WI Made in USA
Net3 RVI
Mouse
Step 1: Attach the appropriate IEC power cord to the power connector, then to an AC
receptacle.
Step 2: Attach the dual DVI connector/Y-adapter to the DVI port.
If you have VGA monitors, attach the VGA adapters (provided) to the DVI Yadapter.
Do not use the VGA connectors on the back of the RVI.
The minimum screen resolution must be at least 1280x1024 with 32 bit color.
Step 3: Connect the USB mouse and keyboard to the USB connectors. If you wish to use a
PS2 mouse or keyboard (not provided), use the appropriate connectors on the RVI.
Step 4: Attach a network ethernet cable to the Ethernet port. All communications to the
associated control console are made over this Ethernet connection.
• Connection to the console may be made either directly using a Cat5 or better
null-modem cable or through an Ethernet hub or Ethernet switch using standard
Cat5 or better patch cables.
Step 5: When all connections are made, activate the hard power switch on the rear panel.
Step 6: Press the soft power switch, on the front of the unit, to power up the RVI.
If the unit does not power up, check the hard power switch on the rear panel, to
ensure it is switched on.
320 Ion Operations Manual
Dual DVI Display
Keyboard
Not Used
RS-232
Ethernet
Not Used
USB
x4
BTX - L OP IOSHLDR

Front Panel
Removable
label strip
Backlit LEDs
LEDs indicate which mode the unit is operating in (client or offline) and the status of the operation
(sync).
• The “Client” LED will illuminate when the unit is connected as a client of the master
processor.
• Additionally the “Sync” LED will illuminate when the data has been synchronized to the
master console.
• The “Offline” LED will illuminate when the unit is running offline and is no longer in
“Client” mode.
Command Keypad Buttons
The 20 buttons are configurable from the Eos Configuration Utility (ECU). They are set to a default
configuration. The label strips for these buttons are removable and reversible. Any changes to the
button configuration can be written on the opposite side in pencil.
USB Port
The USB port on the front of the RVI unit may be used to connect a USB storage device for show
downloading, uploading, or software updates.
Start Up
At initial startup, the RVI will display the Eos and the Congo logos. Use the mouse to select the Eos
operating system. The RVI will initialize to the Eos environment each time the power is cycled,
unless you choose to revert the operating system in the related settings menu (see “Switch to
Congo from Eos Operating Mode,” in the Net3 Remote Video Interface Setup Guide, page 4).
CAUTION:
Live
Blind
Tab Escape Select
Scroll Lock
20 command keypad
buttons
M001 M002 M003 M004 Stop/Back
M005 M006 M007 M008 GO
Backlit indicators
If you “Exit Eos” and enter the ECU, do not select the “Master” or “Backup” buttons
that are displayed in the ECU welcome screen.
The Net3 RVI will only function as a “Client” on the Eos network or “Offline”.
D Remote Video Interface (RVI) 321
Primary
Master
Backup
Sync
Client
Offline
USB
Soft power
switch

Basic Use Guidelines
Displays
The RVI can be used with either one or two DVI monitors. You can collapse or expand the CIA on
the displays by engaging the scroll lock and pressing F5. If you are using one monitor, you may find
this feature useful in increasing the efficiency of your available display area.
Button Configuration
Settings for the RVI can be altered in the Eos Configuration Utility (ECU). The 20 buttons on the
front panel of the RVI are configurable from the “RPU” section of the ECU.
To configure the RVI buttons:
Step 1: In the Eos browser, select File>Exit Eos and confirm the selection. Eos will close and
you will enter the Eos welcome screen.
Step 2: Click on the “Settings” button. This will open the ECU.
Step 3: On the right side of the screen, click on the “RPU” button to enter the RVI button
setup. A virtual display of the RVI buttons is displayed with the current button settings
labeled on each button.
Step 4: Click on a button you wish to alter. A button window will open.
Step 5: Click on the type of button you want it to be (Macro or Eos Hard Key).
• If Macro - Click on the Macro # box and enter the desired macro number from the
keyboard and press enter. Then click “Accept”.
• If Eos Hard Key - Click on the “Eos HardKey” drop down menu and select the hard
key you wish to use. Then click “Accept”.
Step 6: Repeat this process for any other buttons you wish to reconfigure.
Step 7: To restore the default buttons at any time, click the “Restore Defaults” button.
RVI and RPU button configurations are interchangeable. Therefore you can import button
configurations from one to the other.
To import a button configuration:
You may import an RVI button configuration file from a USB device.
Step 1: Click the “Import” button in the RPU section of the ECU. The RVI will search for valid
RVI/RPU button file.
Step 2: If a valid file is found, the ECU will ask you if you want to import the settings. Click
“Yes”. The settings will be imported.
Step 3: Click “Ok”.
To export a button configuration:
You may export your RPU button configuration to a USB device.
Step 1: Click the “Export” button in the RPU section of the ECU.
Step 2: If a USB drive is available, the ECU will ask you to choose the desired drive from the
drop down menu. Click on the desired USB drive.
Step 3: Click “Accept”. The button configuration will be saved to the USB drive.
Step 4: Click “Ok”.
For more information on settings in the ECU, please see Eos Configuration Utility (Eos Shell), page
293.
322 Ion Operations Manual

Appendix E
Remote Control
Remotes Overview
Three different remotes are available for controlling Ion; the phone remote, the radio focus remote
(RFR), and the iRFR.
Phone Remote
The phone remote allows for remote control of the Ion console by using a wireless phone. The base
station for the phone connects directly to the phone remote jack on the rear of your console. See
“Console Geography” on page 12.The numeric keypad of the phone is used to control channels
and levels.
Phone Remote Functions
The numeric keypad of the phone is mapped as following:
1
+ Thru -
4
Last Macro @
7
5 6
Next Address Full
*/Shift
Clear CL
2 3
Chan
Check
8 9
0 #/Enter
To use the commands in grey, first hit the [*] button followed by the number or symbol above the
grey command. For example, to place a [+] on the command line, press [*] [1].
Pressing [*] [*] will clear the command. Commands entered from the phone remote will appear on
the command line for the console.
E Remote Control 323
Sneak

Remote Focus Remote (RFR)
The Net3 Radio Focus Remote (RFR) provides remote
access to frequently used console features such as dimmer
and channel checks as well as update and record functions.
The RFR handheld remote and receiver unit features a high
frequency (HF) link for bi-directional communication with a
connected console. During operation, the system status can
be viewed on the LCD of the remote.
Note:
Handheld Remote
This appendix covers only RFR operation with the Eos Family control system. For
information on using the RFR with Congo or Congo jr consoles, see the “Congo/
Congo jr User Manual” or the “Net3 Radio Focus Remote Setup Guide” for more
information.
The RFR handheld unit features 24 backlit buttons and two push-button thumb
wheels, one on either side for scrolling to desired targets and selecting them for
interaction. The top side of the remote has an on/off power switch, a high
frequency antenna and a USB mini b port. The USB mini b connection is used to
supply power for the internal rechargeable NiMH battery cell using the provided
power supply.
324 Ion Operations Manual
mode
more sk
Enter
Chan
Push
mode
more sk
@
s1 s2 s3
7 8 9
4 5 6
1 2 3
C
s4
0
s5
.
s6
TH
-
+
Enter
Chan

Base Station Receiver
The receiver includes a USB type B connector and an Ethernet connector (IEEE 802.3af) on the
front of the unit for connection to the console (USB) or to a switch in your Net3 network
Push
USB
When the base station is connected directly to a console by USB type B, the
RFR is powered by and controls only the console the base station is connected
to. ETC supplies a 1.8m (6 ft.) USB cable for base station connection to a
console or USB hub. The maximum distance between products is 5m (16 ft.).
When the base station is connected to Eos/Ion using USB, the RFR remote will
automatically connect to that console when powered.
Ethernet
For use with the Ion console, the base station will need to be plugged into an
ethernet switch. If the switch is not power over ethernet, the base station can receive power via
USB from the console.
Note:
CAUTION:
For single base station use, no configuration is needed if defaults are used. For
multiple base stations, custom configurations, and connection issues, further
configuration will be needed.
You may use either the ethernet connection or the USB connection for data to the
console, but not both.
Console Section Mode
Holding down [.] while the remote is booting up will take you to the
console selection list. This mode is used to select between Direct
USB mode, Base USB mode, or available host consoles for
networking.
Note:
Direct USB
If multiple RFR units are to be used separately within a range of each other’s
receiver units, change the frequency and/or ID settings to avoid conflicts.
Reference Change Frequency and ID Setting below for more information.
For optimal operation, set the base stations apart by at least 5m (16 ft.) to ensure
the two units do not interfere with each other’s operation.
E Remote Control 325
Booth

Change Frequency and ID Setting
A network ID is a separate digital channel on a single high frequency (HF) setting. Changing an ID
setting from the default “1” is useful when multiple systems are utilizing the same frequency.
Note:
If you change the frequency and ID settings in the handheld remote you must also
change the frequency and ID settings to match in the base station.
To change the radio settings on your remote:
Step 1: With the remote power off, press and hold the [C] button.
Continue pressing it and power up the unit. The display
window will show the HF Channel selection screen.
Step 2: Choose an HF Channel (1 - 12) by spinning either thumb
wheel.
Note:
Set HF Channel
1 (2.410 Ghz)
Available: **
Setup: HF EUR
Prev
Default
Next Save
• While setting the HF Channel, the RFR scans each available channel for traffic
which may interfere with the RFR. This feature is used to determine what
frequency to use in your venue.
• In the “Available:” field the RFR will display ***, **, * or “used”. The asterisks
indicate the quality of the signal at that channel. *** is best. “Used” indicates that
other traffic is detected on that channel, but the RFR may still function properly.
Step 3: Press {Next} ([s2]).
Step 4: Choose a network ID by moving either thumbwheel. Allowed range is from 1 to 99.
Step 5: Press {Next} ([s2]).
Step 6: Set the HF power level. This allows you to alter the strength of the transmission signal
from the remote. Allowed range is from +10 dBm to +18 dBm.
• A higher value indicates a stronger signal, but shortened battery life. A lower
value indicates a weaker signal and an extended battery life.
Step 7: Press {Save} ([s3]).
Step 8: You must cycle the power to apply the new settings.
Default [S4] will reset remote settings to their default values. No confirmation is
required.
To change the frequency and network id in your base station receiver with an Ion console:
Step 1: In the browser menu, select File

Basic Use Guidelines
Keypad Function
The keypad illuminates while the keys are in use and remains illuminated while the unit is
transmitting data. After a key is released, the keypad will dim the backlight until the next button
press or transmission.
Most of the buttons on the handheld remote function exactly as they work on the Ion console. A
select few of the buttons require additional explanation.
• [More SK / Mode] - When this button is pressed and released, the soft keys will change to the
next page of softkeys (if there is more than one page available). Press and hold the [More SK
/ Mode] button to display the available RFR modes.
• [Enter / Chan] - When the RFR is connected for use with an Ion console, this button functions
as [Enter], which terminates the command line.
• [@] - The first press of this button is “at”. The second consecutive press is “at level”. The third
press is “at Out”.
• [S1 - S6] - These six buttons are softkeys, defined by the operating mode and identified in the
bottom portion of the LCD (see below).
• [.] - The first press of this button is “.”. The second consecutive press is “/”.
LCD General Layout
Details of current target
Command Line
S1
S4
S2
S5
S3
S6
The handheld remote LCD is divided into four sections. The top section
displays status for the selected target. The middle section displays the
command line. This section scrolls to accommodate viewing long command
syntax. The next section displays the console’s mode status and error
status (if any). The bottom section displays the current function of the soft
keys (it also displays the various modes when [Mode/More SK] is pressed and held).
Thumbwheels
The two thumbwheels on the RFR (one left, one right) have varying functionality depending on the
selected mode (see RFR Operation Modes, page 329). Generally speaking, the left thumbwheel
acts as a level wheel. It increases or decreases intensity for selected channels. The right
thumbwheel behaves as next and last for scrolling through data lists.
E Remote Control 327

Recharge the Handheld Battery
A battery level indicator is found in the upper right corner of the handheld LCD. When the battery is
near to a complete drain, the indicator will flash. When charging, the indicator will depict increasing
power to verify that it is charging.
When the remote is not in use, set the switch to the “Off” position to guard against accidental key
presses and to conserve battery power.
Charge the battery using the USB mini b cable that shipped with your RFR. Connect the USB mini
b connector to the handheld remote and the other end to the USB charger adapter supplied with
your RFR. You may also attach the USB cable to a powered USB hub, personal computer, or your
console. A full recharge may take up to 12 hours.
Provided there is enough battery charge, you may use the remote while charging.
CAUTION:
If you choose to charge the remote from the Ion console, you should unplug the
base station before doing so.
The remote will be functional once it is connected directly to the console. If the
base station is still connected and a command is entered on the remote, multiple
iterations of the command may register and this may create errors in the Ion
command line.
328 Ion Operations Manual

RFR Operation Modes
The Eos/Ion RFR defaults to opening in Live mode. There are other modes available in the RFR,
however. To switch modes, hold down the [Mode/More SK] button and then select the desired mode
from those available by pressing the appropriate softkey. Mode options are: Park, Live, Playback,
and Patch.
Park Mode
This mode is used for parking channels and also for “channel check” and “address check”
functions.
Softkeys
The following softkeys are available in park mode:
• Address
• Channel
• Last
• Full
• Out
• Next
{Address} and {Channel} are used to select addresses or channels for parking.
• [7] [@] [5] [Enter] - Parks channel 7 at 50%.
• {Address} [8] {Full} - Parks address 8 at full.
{Full} and {Out} are used to set those levels for channels or addresses. {Out} parks the channel or
address at 0.
{Next} and {Last} are used for the check functions (see below).
• [9] [@] [Enter] - unparks channel 8.
Channel or Address Check
When a single address or channel is selected, using {Next} and {Last} you can rapidly increment
or decrement through the channels or addresses to verify function. This only works when a single
channel or address is selected on the RFR and then {Next} and {Last} is used.
In this mode, the right thumbwheel will function as next and last commands, and the left will function
as the level wheel.
E Remote Control 329

Live Mode
Live mode is used for modifying levels and recording or updating cues. This mode is intended to
allow you to make basic adjustments to show data. Buttons and softkeys function as they do within
Eos/Ion.
The command line is displayed in the LCD to verify the commands you enter. It also displays details
for the currently selected channel or the current cue (if no channels are selected).
Softkeys
The following softkeys are available on page one of live mode, which is designed to modify levels:
• Home
• Group
• Sneak
• Full
• Out
• RemDim
The following softkeys are available on page two of live mode which is intended for recording or
updating cues:
• Record
• Update
• Time
• Cue only/Track (shown as “Qoly/Tk”)
• Trace
• Macro
In live mode, the left thumbwheel controls the level of the selected channels. The right thumbwheel
acts as next and last buttons, defaulting to next or last cue selection for the currently selected cue
list.
330 Ion Operations Manual

Playback Mode
Softkeys
The following softkeys are available in playback mode:
• Sub
• Load Q
• Stop/Bk
• Macro
• Goto Q
• Go
{Sub} is used to set the level of a submaster.
• {Sub} [5] [@] [7] [Enter] - sets submaster 5 to 70%.
{Load Q} allows you to load a cue into the pending file for the master playback fader pair only.
• {Load Q} [5] [Enter] - Loads cue 5 of the master playback fader to the pending file for that
fader. Pressing {Go} will execute this cue.
{Go} and {Stop/Bk} are duplicates of the [Go] and [Stop/Back] buttons for the Eos/Ion master
fader pair.
{Macro} allows you to execute a macro.
• {Macro} [3] [Enter].
{Goto Q} allows you to jump to any cue in the show.
• {Goto Q} [6] [Enter] - plays back cue 6 for the master playback fader pair.
• {Goto Q} [4] [.] [.] [2] [Enter] - plays back cue 2 from cue list 4. To play back cues from any
other list than the one loaded to the master playback fader pair requires you to specify the cue
list in the command line.
The left thumbwheel controls intensity of a selected submaster. The right thumbwheel acts as next
or last for the most recently selected cue list.
E Remote Control 331

Patch Mode
In patch mode, the LCD displays the channel, address and type for the currently selected
channel(s).
Softkeys
The following softkeys are available in patch mode:
• Address
• A
• B
• /
• Fixture Controls (shown as: FixCtrl)
{Address} allows you to change the address of the selected channel.
• [1] {Address} [1] [Enter] - addresses channel 1 to output 1.
{A} and {B} are used for patching dimmer doublers.
• [9] [7] [Th] [1] [0] [2] {Address} [1] {B} [Enter] - patches channels 97-102 to outputs 1B-6B
(for dimmer doubling).
{/} is used to patch the port and offset.
• [2] {Address} [3] [/] [1] [Enter] - patches channel 2 to port 3 offset 1 or address 1025.
{FixCtrl} is used to display the fixture controls for a channel (if available).
• [6] {FixCtrl} - displays fixture controls for channel 2.
The thumbwheel will scroll through the available fixture controls. Press the thumbwheel to activate
the fixture control.
332 Ion Operations Manual

Technical Specifications
Handheld Transmitter
Output U.S.A. - Default HF:1 (2.410 MHz) with 11
additional HF: channels available (2.410 - 2.465
GHz). 99 groups available per channel.
Antenna - Helical, fixed.
Working range - 90m (300 ft) indoor, 200m (656
ft) in free field.
Size - 160mm(4.5”) x 72mm (2.6”) x 20mm (.8”)
excludes antenna.
Base Station Receiver
Data - USB type B. Ethernet.
Power - USB or Power over Ethernet (PoE).
Size - 112mm(4.4”) x 71mm (2.7”) x 45mm (.7”)
excludes antenna.
Connections - Integral USB mini b connector for
charging the unit.
Power - 2x NiMH rechargeable battery. (Recharge
using the USB connection.)
Weight - 400g (14 oz.) includes antenna.
Connections - Integral USB connector to console
or RPU. Ethernet.
Maximum USB cable length - 5m (16.5’) from
power source using USB.
Weight - 380g (13 oz.) includes antenna.
E Remote Control 333

iRFR
The iRFR is a software application that runs on an Apple iPhone® or iPod Touch. The application
can be downloaded from the Apple Application Store, search for iRFR. The iRFR offers the same
functionality of the RFR. A closed wireless network is needed.
For additional information on the iRFR, including setup, please visit the iRFR Documentation Wiki.
334 Ion Operations Manual

Appendix F
Universal Fader Wings
Overview
Universal fader wings can be used in conjunction with your Ion console to facilitate the use of
submasters and playbacks. The wings are available in 2x10 or 2x20 or 1x20 configurations.
The fader wings are designed to physically attach to your Ion console, thereby receiving power from
the console and eliminating the need for the external power supply. Or you may connect wings to
Ion using a USB cable and provide power using an external power supply.
1 x 20 Setup
The 1 x 20 fader wing is specifically designed to be physically attached to your console. A USB
cable connection is required.
To install the 1 x 20 on your Ion console, follow the instructions that were included with the 1 x 20
wing. Be sure to connect the wing to Ion using the USB cable that was included with the wing.
2 x 10 and 2 x 20 Setup
2x10 and 2x20 Universal Fader Wings may be attached together and then physically attached to
Ion consoles.
Wings may also be connected to Ion or Eos consoles, RPUs, or RVIs using a USB cable. When
connecting fader wings with a USB cable, one external power supply must also be used.
Rules of Connection
Rule One
Your entire system is limited to a total of 300 faders per processor (Ion, RPU, RVI).
Rule Two
No more than three fader wings may be physically attached to each other. This means:
• A maximum of three fader wings may be directly attached to either side of a console (3 per
side).
• A maximum of three fader wings may be connected using a USB cable to form an external
array using an external power supply.
Note:
Only one wing (2 x 10 or 2 x 20) may be used with Eos/Ion offline software running
on a personal computer.
Connecting Wings to Ion
Up to three Universal Fader Wings may be attached together and then connected to Ion using a
USB cable only or by physically attaching them to the Ion console. Both sides of Ion may have up
to three wings attached.
The best way to attach wings together is to attach them in order from left to right.
F Universal Fader Wings 335

Attach Universal Fader Wings
Step 1: Using a #1 Phillips head screwdriver, on the underside of the wing(s) remove the two
screws securing the bumpers that will be removed from the appropriate side or sides
of the wings. The bumpers will be removed in a later step.
a: Carefully turn the wing over and place it faders-down on a clear, flat work
surface.
CAUTION:
Bumpers on
either side
Do not set the wing on the connector side (rear panel). Instead, place it face down
on the faders.
b: Remove and save the two screws securing the bumper to the side of the wing.
1
3
OR
2
Step 2: Turn the wing over to return it to its upright position.
Step 3: Remove the bumper(s) from the wing.
a: Right Side - Gently pull the bumper up until it is flush with the facepanel.
Left Side -Gently push the bumper down until it loosens from the facepanel.
b: Pull the bumper away from the facepanel until it is free from the wing.
Step 4: Repeat steps 2 and 3 for each side of each wing that needs to be exposed.
Step 5: Align the two wings. Lift the wing on the right and place it gently on the hooks provided
on the wing on the left. Check that the two wings are aligned properly front and back,
336 Ion Operations Manual
1

then press down gently on the right wing until it is fully seated. This should be a
smooth connection but may require a little force.
Step 6: Repeat above procedure to connect another wing to the right end of the pair, if
desired.
Step 7: Re-insert screws to secure wings together and secure the bumpers to the sides of the
wings.
Attach fader wing array to Ion
Once all of the desired wings are attached (within the limits above), you may use the same
procedure above to attach the wings to Ion.
Connect Universal Fader Wing(s) to Console with USB Cable
Connect PS313-F
power supply
cable
(included)
Connect
USB cable
(included)
Connect to USB
on the console
Step 1: With the console power off, connect the USB cable (provided) between the console
and one wing as shown above. If multiple wings are joined, only one power and one
USB connection is required for all joined wings.
Step 2: Using the power supply adaptor kit, connect the fader wing to a power source.
Step 3: It is recommended that you run the power and USB cables through the strain relief
included on the back of the wings.
Step 4: Turn the console on.
F Universal Fader Wings 337

User Guidelines for Fader Wings
Fader Wing Interaction With Ion
1x20
When connected with a USB cable, the 1 x 20 will automatically be populated with the faders 1-20.
Any other fader wings will then be populated with successive fader pages.
2x10 or 2x20
Ion will automatically recognize the fader wings and their configuration (2 x 10 or 2 x 20) once they
are connected to the console. The system will configure the faders according to the configuration in
fader wing configuration screen, for more information see {Fader Wing Config}, page 104. The left
most fader will be fader 1 on page 1, next will be fader 2 on page 1, and so on.
Multiple wings connected
If multiple wings are used in conjunction with each other, configuration will automatically adhere to
the following logic.
1x20
Anytime a 1x20 is attached to Ion, it will automatically load the first 20 faders. Other wings will then
be populated, starting with the 21st fader.
2x10 and 2x20
When 2x fader wings are attached to each other, the faders will populate continuously across the
attached array according to the configuration in fader wing configuration screen. The top row of all
wings will be successive from one wing to the next. The bottom row will start where the entire top
row left off and then will also be successive from one wing to the next.
Therefore, when fader wings are attached to each other:
LCD
Top Row Faders
Bottom Row Faders
1 - 10
41 - 50
11 thru 30
51 thru 70
31 - 40
71 - 80
2x10 2x20 2x10
The display at the center of the fader wing shows information about the faders.
For submasters the sub number, label, and current value (0-100%) of the fader are shown. When
the page is changed, the current value will display the necessary percentage the fader must be set
at to match the required level of the submaster.
For playbacks the cue list number will be shown preceded by an “L” {for example “L3” = cue list 3).
Beneath this the current pending cue is displayed in an oval shape.
For Grandmasters, a “GM” is displayed and the current output percentage is shown (100% -
blackout).
338 Ion Operations Manual

Using the Buttons
Each fader is equipped with two buttons beneath the potentiometer. When used with submasters,
the bottom button is the bump key. The top button can be used in two ways. When pressed in
conjunction with the bump button it will act as a “Load” button for that fader and can be used to load
submasters. When pressed individually, it will act as a group select button for all channels in that
submaster. Pressing it in this instance is the same as entering [Group] [Sub] [x] on the command
line.
For playbacks, the bottom button acts as a [Go] button and the top button acts as a [Stop/Back]
button, similar to the buttons beneath the master fader pair on Ion.
When pressed together, these buttons act as a [Load] button for that fader which can be used to
load faders or to use any of the fader controls such as {Release} or {Stop Effect}.
Loading Faders
To load a submaster or playback onto an unmapped fader, specify the desired submaster or cue list
on the command line and press [Enter]. Then press both fader buttons (which equals [Load]).
To load contents to a fader that is already mapped, you may have to release the fader by pressing
and holding [Fader Controls], pressing {Release}, and then pressing both fader buttons ([Load]).
To assign a fader as a Grandmaster, you must do so in the fader configurator in setup.
Fader Wing Paging
The fader wing is paged using the [Fader Controls] button on the Ion console. Fader pages are
delineated in 20 fader increments. If you advance to the next fader page, your entire fader wing
array will advance by a total of 20 faders.
For Example:
If you have a 1x20 and a 2x20 attached to Ion, the initial fader configuration will be faders
1-20 on the 1x20 and faders 21-60 on the 2x20.
If you then advance to the next fader page (using the steps below), the 1x20 wing will
assume faders 21-40 and the 2x20 will assume faders 41-80. This represents an overall
increment of 20 faders for the entire fader wing configuration.
To change the fader page of a fader wing:
Step 1: Press and hold the [Fader Controls] button on the Ion console. The LCD on the fader
wing will display the available pages beneath the fader bump buttons.
Step 2: Press the bump button corresponding to the page you wish to display on the fader
wing. The fader wing will display those faders after your selection is made.
F Universal Fader Wings 339

Using the Faders
When the page is changed, the fader wing LCD will display information for any mapped submaster
or loaded playback. Unmapped faders will display no information.
Submaster LEDs will illuminate in the color of the new submaster loaded on the page (green for
additive and red for inhibitive). Fader wing submasters are not motorized, therefore when you
change pages you may have to manually reset the fader to the proper location to reflect its current
output level. If a submaster setting must be matched to gain control, the LED will flash quickly in the
appropriate color. The LED will stop flashing and illuminate normally once the fader has been
moved to the required location.
When loaded with a playback, you may use the fader to interrupt a fade in progress and switch the
fade to manual timing. First press [Go] and while the fade is in progress, drop the fader to zero and
the raise the fader at the desired rate. Once it is raised fully, the fade will complete and control will
be returned to the buttons.
340 Ion Operations Manual

Index
Symbols
-% . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
+% . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Numerics
1-to-1 patch. . . . . . . . . . . . . . . . . . . . . 60
A
about
about . . . . . . . . . . . . . . . . . . . . . 246
channel. . . . . . . . . . . . . . . . 249, 250
cue . . . . . . . . . . . . . . . . . . . . . . . 253
palettes. . . . . . . . . . . . . . . . . . . . 253
presets . . . . . . . . . . . . . . . . . . . . 253
system . . . . . . . . . . . . . . . . . . . . 247
absolute data
with palettes . . . . . . . . . . . . . . . . 144
absolute effects. . . . . . . . . . . . . . . . . 237
active cue list
changing. . . . . . . . . . . . . . . . . . . 190
Address
in live . . . . . . . . . . . . . . . . . . . . . 127
address
parking in live . . . . . . . . . . . . . . . 224
allfade . . . . . . . . . . . . . . . . . . . . 163, 190
analog inputs . . . . . . . . . . . . . . . . . . 283
assert
and load . . . . . . . . . . . . . . . . . . . 218
at channel level . . . . . . . . . . . . . 189
at cue level . . . . . . . . . . . . . . . . . 189
cue list . . . . . . . . . . . . . . . . . . . . 218
flags . . . . . . . . . . . . . . . . . . . . . . 163
using with cue lists . . . . . . . . . . . 189
assign
virtual faders. . . . . . . . . . . . . . . . 214
At Enter. . . . . . . . . . . . . . . . . . . . . . . 165
AutoMark . . . . . . . . . . . . . . . . . . . . . 176
allowing live moves . . . . . . . . . . 176
timing . . . . . . . . . . . . . . . . . . . . . 176
B
back (key) . . . . . . . . . . . . . . . . . . . . . 215
backup . . . . . . . . . . . . . . . . . . . 307–313
backup console . . . . . . . . . . . . . 307
client . . . . . . . . . . . . . . . . . . . . . 307
master . . . . . . . . . . . . . . . . . . . . 307
offline console . . . . . . . . . . . . . . 307
primary. . . . . . . . . . . . . . . . . . . . 307
backup console
definition . . . . . . . . . . . . . . . . . . 307
basic manual control . . . . . . . . . . . . 107
beam palette
description . . . . . . . . . . . . . . . . . 138
blind
channel display . . . . . . . . . . . . . 144
display indicators . . . . . . . . . . . . . 35
editing cues in . . . . . . . . . . . . . . 171
editing palettes in. . . . . . . . . . . . 144
editing presets in . . . . . . . . . . . . 135
recording cues in . . . . . . . . . . . . 171
spreadsheet view. . . . . . . . . . . . . 45
edit palettes in . . . . . . . . . . . 145
storing multipart cues in. . . . . . . 207
text indicators . . . . . . . . . . . . . . . 37
using encoders in . . . . . . . . . . . 173
block. . . . . . . . . . . . . . . . . . . . . . . . . 162
channels/parameters . . . . . . . . . 162
cues . . . . . . . . . . . . . . . . . . . . . . 162
browser . . . . . . . . . . . . . . . . . . . . . . . 27
clear. . . . . . . . . . . . . . . . . . . . . . . 32
file
save as . . . . . . . . . . . . . . . . . 55
Image. . . . . . . . . . . . . . . . . . . . . . 29
navigating within . . . . . . . . . . . . . 29
virtual keyboard . . . . . . . . . . . . . . 29
bump button
timing . . . . . . . . . . . . . . . . . . . . . 261
C
calibrate scroller . . . . . . . . . . . . . . . . . 78
capture . . . . . . . . . . . . . . . . . . . . . . . 200
Central Information Area (CIA). . . . . . 27
browser . . . . . . . . . . . . . . . . . . . . 27
locking . . . . . . . . . . . . . . . . . . . . . 28
parameter display . . . . . . . . . . . . 27
parameter display in . . . . . . . . . 111
unlocking . . . . . . . . . . . . . . . . . . . 28
virtual keyboard . . . . . . . . . . . . . . 29
341

channel
compound patching . . . . . . . . . . . 67
unpatching . . . . . . . . . . . . . . . . . . 65
channel check. . . . . . . . . . . . . . . . . . 127
channels
asserting. . . . . . . . . . . . . . . . . . . 189
display conventions . . . . . . . . . . . 35
homing . . . . . . . . . . . . . . . . . . . . 119
multiple intensity. . . . . . . . . . . . . 120
ordered with groups . . . . . . . . . . . 88
selecting . . . . . . . . . . . . . . . . . . . 108
in patch . . . . . . . . . . . . . . . . . 63
using about. . . . . . . . . . . . . 249, 250
CIA. See Central Information Area
cleaning Ion . . . . . . . . . . . . . . . . . . . . 13
clear
cue attributes . . . . . . . . . . . . . . . 161
filters. . . . . . . . . . . . . . . . . . . . . . 185
patch . . . . . . . . . . . . . . . . . . . . . . 60
submaster . . . . . . . . . . . . . . . . . 260
clear functions. . . . . . . . . . . . . . . . . . . 32
client console
definition . . . . . . . . . . . . . . . . . . 307
close
displays . . . . . . . . . . . . . . . . . . . . 33
color control
from encoders . . . . . . . . . . . . . . 117
color effects . . . . . . . . . . . . . . . . . . . 240
color indicators
in live/blind . . . . . . . . . . . . . . . . . . 36
color palette
description . . . . . . . . . . . . . . . . . 138
color picker
description. . . . . . . . . . . . . . . . . 118
command history . . . . . . . . . . . . . . . 201
command line
about . . . . . . . . . . . . . . . . . . . . . . 27
syntax structure . . . . . . . . . . . . . . . 4
compound channel
patching . . . . . . . . . . . . . . . . . . . . 67
configuration utility . . . . . . . . . . 293–303
configure
gateways . . . . . . . . . . . . . . . . . . . 15
grandmaster . . . . . . . . . . . . . . . . . 96
Ion DMX ports . . . . . . . . . . . . . . 305
nodes . . . . . . . . . . . . . . . . . . . . . . 15
show control ports . . . . . . . . . . . 305
console
capacities. . . . . . . . . . . . . . . . . . . 14
cleaning . . . . . . . . . . . . . . . . . . . . 13
geography . . . . . . . . . . . . . . . . . . 12
playback controls. . . . . . . . . . . . 210
conventional fixtures
display conventions . . . . . . . . . . . 35
patching (dimmers) . . . . . . . . . . . 64
copy
fixture. . . . . . . . . . . . . . . . . . . . . . 85
copy to . . . . . . . . . . . . . . . . . . . . . . . 196
create
cue. . . . . . . . . . . . . . . . . . . . . . . 151
cue list . . . . . . . . . . . . . . . . . . . . 188
curve . . . . . . . . . . . . . . . . . . . . . 273
fixture in patch . . . . . . . . . . . . . . . 81
group . . . . . . . . . . . . . . . . . . . . . . 88
macro
using editor display . . . . . . . 268
new fixture . . . . . . . . . . . . . . . . . . 82
palette . . . . . . . . . . . . . . . . . . . . 139
preset. . . . . . . . . . . . . . . . . . . . . 130
submaster . . . . . . . . . . . . . . . . . 256
cue
selected, the . . . . . . . . . . . . . . . 211
in blind. . . . . . . . . . . . . . . . . 211
in live . . . . . . . . . . . . . . . . . . 211
cue level timing
setting . . . . . . . . . . . . . . . . . . . . 155
cue list index . . . . . . . . . . . . . . . . . . 192
{edit} . . . . . . . . . . . . . . . . . . . . . 194
{HTP/LTP} . . . . . . . . . . . . . . . . . 193
{independent} . . . . . . . . . . . . . . 193
{move to} . . . . . . . . . . . . . . . . . . 194
{Solo Mode} . . . . . . . . . . . . . . . . 194
opening . . . . . . . . . . . . . . . . . . . 192
cue lists
{assert} & {load}. . . . . . . . . . . . . 218
active list, changing the . . . . . . . 190
attributes . . . . . . . . . . . . . . . . . . 193
new, recording to
using {Record Only} . . . . . . 188
using {Record}. . . . . . . . . . . 188
recording to new . . . . . . . . . . . . 188
using assert . . . . . . . . . . . . . . . . 189
Cue Only mode
deleting cues in . . . . . . . . . . . . . 174
cue playback . . . . . . . . . . . . . . . . . . 209
cue settings
342 Ion Operations Manual

in setup. . . . . . . . . . . . . . . . . . . . . 95
cues
{At} {Enter} . . . . . . . . . . . . . . . . . 165
about . . . . . . . . . . . . . . . . . . . . . 150
applying curves to . . . . . . . . . . . 275
asserting. . . . . . . . . . . . . . . . . . . 189
attributes . . . . . . . . . . . . . . . . . . 159
clearing . . . . . . . . . . . . . . . . 161
follow/hang. . . . . . . . . . . . . . 159
label . . . . . . . . . . . . . . . . . . . 161
link/loop . . . . . . . . . . . . . . . . 160
rate. . . . . . . . . . . . . . . . . . . . 161
basic programming. . . . . . . . . . . 150
block. . . . . . . . . . . . . . . . . . . . . . 162
cue list index . . . . . . . . . . . . . . . 192
opening . . . . . . . . . . . . . . . . 192
deleting. . . . . . . . . . . . . . . . . . . . 174
in Cue Only mode . . . . . . . . 174
in Track mode . . . . . . . . . . . 174
editing in blind . . . . . . . . . . . . . . 171
execute list . . . . . . . . . . . . . . . . . 164
flags . . . . . . . . . . . . . . . . . . . . . . 162
allfade . . . . . . . . . . . . . . . . . 163
assert . . . . . . . . . . . . . . . . . . 163
block . . . . . . . . . . . . . . . . . . 162
mark. . . . . . . . . . . . . . . . . . . 163
preheat. . . . . . . . . . . . . . . . . 163
go to cue . . . . . . . . . . . . . . . . . . 213
manual control during playback . 216
modifying
from spreadsheet view. . . . . 172
from summary view . . . . . . . 172
from table view. . . . . . . . . . . 172
using {At} {Enter} . . . . . . . . . 165
using {move to}
in blind. . . . . . . . . . . . . . 173
in live . . . . . . . . . . . . . . . 166
using {Record Only}. . . . . . . 166
using {Record} . . . . . . . . . . . 165
using {Replace With} . . . . . . 173
using {Update} . . . . . . . . . . . 167
modifying in live . . . . . . . . . . . . . 165
multipart
about . . . . . . . . . . . . . . . . . . 203
changing to . . . . . . . . . . . . . 207
changing to a standard cue . 207
deleting a part . . . . . . . . . . . 207
setting part attributes . . . . . . 205
numbering . . . . . . . . . . . . . . . . . 150
out of sequence . . . . . . . . . . . . . 212
using go to cue . . . . . . . . . . 213
part. See cues - multipart
recording
using {Record Only} . . . . . . 152
using {Record}. . . . . . . . . . . 151
recording in blind . . . . . . . . . . . . 171
recording in live . . . . . . . . . . . . . 151
recording multiparts in live. . . . . 204
settings
in setup . . . . . . . . . . . . . . . . . 95
storing
selective . . . . . . . . . . . . . . . 153
using {Cue Only/Track}
in Cue Only mode. . . . . 154
in Track mode. . . . . . . . 154
storing multiparts in blind. . . . . . 207
timing . . . . . . . . . . . . . . . . . . . . . 155
delay . . . . . . . . . . . . . . . . . . 159
discrete . . . . . . . . . . . . . . . . 158
manual . . . . . . . . . . . . . . . . 156
parameter category . . . . . . . 156
setting . . . . . . . . . . . . . . . . . 155
updating
to references . . . . . . . . . . . . 168
without references. . . . . . . . 168
updating multiparts in live . . . . . 206
using {About} . . . . . . . . . . . . . . . 253
using {Allfade} . . . . . . . . . . . . . . 190
curve
delete. . . . . . . . . . . . . . . . . . . . . 275
in patch . . . . . . . . . . . . . . . . . . . . 70
curves
about . . . . . . . . . . . . . . . . . . . . . 272
applying
to channels in patch . . . . . . 275
to cues. . . . . . . . . . . . . . . . . 275
creating . . . . . . . . . . . . . . . . . . . 273
editing . . . . . . . . . . . . . . . . . . . . 274
custom fixture. . . . . . . . . . . . . . . . . . . 85
D
data (navigation key) . . . . . . . . . . . . . 39
database settings, in patch . . . . . . . . 72
delay timing . . . . . . . . . . . . . . . . . . . 159
delete
cues . . . . . . . . . . . . . . . . . . . . . . 174
curves . . . . . . . . . . . . . . . . . . . . 275
groups . . . . . . . . . . . . . . . . . . . . . 89
macros. . . . . . . . . . . . . . . . . . . . 270
palettes . . . . . . . . . . . . . . . . . . . 147
parts from multipart cues . . . . . . 207
343

presets . . . . . . . . . . . . . . . . . . . . 136
show file . . . . . . . . . . . . . . . . . . . . 57
submasters. . . . . . . . . . . . . . . . . 260
desk setup . . . . . . . . . . . . . . . . . . . . 100
device type
setting in patch . . . . . . . . . . . . . . . 63
dimmer
patching . . . . . . . . . . . . . . . . . . . . 64
See address.
dimmer check
See {Address}
dimmer doubling
in patch. . . . . . . . . . . . . . . . . . . . . 65
direct selects
opening . . . . . . . . . . . . . . . . . . . . 30
organizing. . . . . . . . . . . . . . . . . . . 30
selecting channels with . . . . . . . . 31
discrete timing. . . . . . . . . . . . . . . . . . 158
display
indicators
mark. . . . . . . . . . . . . . . . . . . 178
display indicators . . . . . . . . . . . . . . . . 35
displays
attribute, in patch . . . . . . . . . . . . . 70
blind channel . . . . . . . . . . . . . . . 144
changing format . . . . . . . . . . . . . . 43
close. . . . . . . . . . . . . . . . . . . . . . . 33
color indicators . . . . . . . . . . . . . . . 36
controlling. . . . . . . . . . . . . . . . . . . 33
conventions . . . . . . . . . . . . . . . . . 35
database, in patch . . . . . . . . . . . . 72
effect status . . . . . . . . . . . . . . . . 233
expanding. . . . . . . . . . . . . . . . . . . 35
macro editor . . . . . . . . . . . . . . . . 266
navigating. . . . . . . . . . . . . . . . . . . 33
open . . . . . . . . . . . . . . . . . . . . . . . 33
from the browser . . . . . . . . . . 33
from the hardkeys . . . . . . . . . 33
from the softkeys . . . . . . . . . . 33
parameter. . . . . . . . . . . . . . . . . . . 27
park
parking from. . . . . . . . . . . . . 225
patch
opening . . . . . . . . . . . . . . . . . 61
settings . . . . . . . . . . . . . . . . . 68
playback status
color indicators. . . . . . . . . . . . 41
indicators in . . . . . . . . . . . . . . 41
text indicators. . . . . . . . . . . . . 41
scrolling within . . . . . . . . . . . . . . . 34
spreadsheet view. . . . . . . . . . . . . 45
summary data view . . . . . . . . . . . 43
swap . . . . . . . . . . . . . . . . . . . . . . 34
table view. . . . . . . . . . . . . . . . . . . 44
zooming . . . . . . . . . . . . . . . . . . . . 34
DMX
outputting. . . . . . . . . . . . . . . . . . . 15
from Ion . . . . . . . . . . . . . . . . 305
344 Ion Operations Manual
E
edit (softkey)
in cue list index . . . . . . . . . . . . . 194
editing
cues in blind. . . . . . . . . . . . . . . . 171
curves . . . . . . . . . . . . . . . . . . . . 274
effect
live. . . . . . . . . . . . . . . . . . . . 242
from submaster list . . . . . . . . . . 262
groups
from group list index . . . . . . . 90
groups in live . . . . . . . . . . . . . . . . 89
macros. . . . . . . . . . . . . . . . . . . . 269
palettes in blind . . . . . . . . . . . . . 144
palettes in live . . . . . . . . . . . . . . 143
palettes in spreadsheet view . . . 145
parameters in new fixture . . . . . . 82
presets. . . . . . . . . . . . . . . . . . . . 133
in spreadsheet view . . . . . . 136
in table view . . . . . . . . . . . . 135
presets in blind . . . . . . . . . . . . . 135
ranges for new fixture . . . . . . . . . 85
scroller in patch . . . . . . . . . . . . . . 77
wheel in patch . . . . . . . . . . . . . . . 77
effects
about . . . . . . . . . . . . . . . . . . . . . 228
absolute . . . . . . . . . . . . . . . . . . . 237
programming . . . . . . . . . . . . 238
applying an existing . . . . . . . . . . 242
color. . . . . . . . . . . . . . . . . . . . . . 240
editing
live. . . . . . . . . . . . . . . . . . . . 242
focus . . . . . . . . . . . . . . . . . . . . . 239
linear . . . . . . . . . . . . . . . . . . . . . 240
relative . . . . . . . . . . . . . . . . . . . . 239
color . . . . . . . . . . . . . . . . . . 240
defining a pattern . . . . . . . . 241
focus . . . . . . . . . . . . . . . . . . 239
linear . . . . . . . . . . . . . . . . . . 240

programming . . . . . . . . . . . . 241
status display . . . . . . . . . . . . . . . 233
step . . . . . . . . . . . . . . . . . . . . . . 234
programming . . . . . . . . . . . . 235
stopping . . . . . . . . . . . . . . . . . . . 242
submasters. . . . . . . . . . . . . . . . . 243
using {Stop Effect} . . . . . . . . . . . 219
encoders
about . . . . . . . . . . . . . . . . . . . . . . 46
color control . . . . . . . . . . . . . . . . 117
image control . . . . . . . . . . . . . . . 116
LCD
description . . . . . . . . . . . . . . 113
form control . . . . . . . . . . . . . 116
Image of. . . . . . . . . . . . . . . . 113
locking . . . . . . . . . . . . . . . . . . . . . 46
navigating. . . . . . . . . . . . . . . . . . . 46
setting non-intensity parameters 112
shutter control . . . . . . . . . . . . . . 117
using in blind . . . . . . . . . . . . . . . 173
virtual
opening . . . . . . . . . . . . . . . . 115
use . . . . . . . . . . . . . . . . . . . . 115
with scroller calibration . . . . . 78
enter (key)
using in syntax . . . . . . . . . . . . . . . . 5
Eos/Ion User Forums . . . . . . . . . . . . . . 8
ETC locations . . . . . . . . . . . . . . . . . . . . 3
ETC Technical Services . . . . . . . . . . . . 3
execute list . . . . . . . . . . . . . . . . . . . . 164
expanding displays . . . . . . . . . . . . . . . 35
export
.csv. . . . . . . . . . . . . . . . . . . . . . . . 56
ASCII . . . . . . . . . . . . . . . . . . . . . . 56
Fast Focus Pro. . . . . . . . . . . . . . . 56
show file . . . . . . . . . . . . . . . . . . . . 56
F
facepanel
locking . . . . . . . . . . . . . . . . . . . . . 28
fader control (hardkey) . . . . . . . . . . . 215
fader pages. . . . . . . . . . . . . . . . . . . . 214
faders
assigning . . . . . . . . . . . . . . . . . . 214
auto playback enabled. . . . . 214
manually . . . . . . . . . . . . . . . 214
changing pages . . . . . . . . . . . . . 214
configuration in setup . . . . . . . . . . 96
fader control (hardkey) . . . . . . . 215
intensity master . . . . . . . . . . . . . 194
playback . . . . . . . . . . . . . . . . . . 209
playback controls. . . . . . . . 215–220
go . . . . . . . . . . . . . . . . . . . . 215
stop/back. . . . . . . . . . . . . . . 215
proportional . . . . . . . . . . . . . . . . 194
rate override . . . . . . . . . . . . . . . 220
release. . . . . . . . . . . . . . . . . . . . 219
slider module . . . . . . . . . . . . . . . . 30
turning off. . . . . . . . . . . . . . . . . . 219
virtual . . . . . . . . . . . . . . . . . . . . . 214
assigning . . . . . . . . . . . . . . . 214
virtual See Slider module. . . . . . . 30
file
create new show . . . . . . . . . . . . . 48
filters
about . . . . . . . . . . . . . . . . . . . . . 183
partial filters . . . . . . . . . . . . . . . . 185
record filters. . . . . . . . . . . . . . . . 184
storing data with . . . . . . . . . 186
removing . . . . . . . . . . . . . . . . . . 185
using with palettes . . . . . . . . . . . 141
fixture creator . . . . . . . . . . . . . . . . . . . 81
opening . . . . . . . . . . . . . . . . . . . . 81
update library. . . . . . . . . . . . . . . . 85
fixture library
updating in show file . . . . . . . . . . 85
flags . . . . . . . . . . . . . . . . . . . . . . . . . 162
allfade . . . . . . . . . . . . . . . . . . . . 163
block . . . . . . . . . . . . . . . . . . . . . 162
channels/parameters. . . . . . 162
cues. . . . . . . . . . . . . . . . . . . 162
mark. . . . . . . . . . . . . . . . . . . . . . 163
flash . . . . . . . . . . . . . . . . . . . . . . . . . 128
flexichannel
description . . . . . . . . . . . . . . . . . . 40
partitioned . . . . . . . . . . . . . . . . . 292
flip. . . . . . . . . . . . . . . . . . . . . . . . . . . 126
focus effects . . . . . . . . . . . . . . . . . . . 239
focus palette
description . . . . . . . . . . . . . . . . . 138
follow/hang . . . . . . . . . . . . . . . . . . . . 159
form control . . . . . . . . . . . . . . . . . . . 116
group list index
using . . . . . . . . . . . . . . . . . . . . . . 90
format
changing . . . . . . . . . . . . . . . . . . . 43
345

patch view . . . . . . . . . . . . . . . . . . 61
summary data view . . . . . . . . . . . 43
freeze . . . . . . . . . . . . . . . . . . . . . . . . 218
G
gateways. . . . . . . . . . . . . . . . . . . . . . . 15
go (key). . . . . . . . . . . . . . . . . . . . . . . 215
in playback . . . . . . . . . . . . . . . . . 215
Go To Cue
timing . . . . . . . . . . . . . . . . . . . . . 213
go to cue. . . . . . . . . . . . . . . . . . . . . . 213
with multiple cue lists . . . . . . . . . 191
go to cue 0
& {Load} . . . . . . . . . . . . . . . . . . . 215
command line. . . . . . . . . . . . . . . 191
playback button . . . . . . . . . . . . . 215
go to cue out. . . . . . . . . . . . . . . . . . . 191
grandmaster
configuring . . . . . . . . . . . . . . . . . . 96
Graphical User Interface (GUI)
display conventions . . . . . . . . . . . 35
group list index . . . . . . . . . . . . . . . . . . 90
editing from . . . . . . . . . . . . . . . . . 90
opening . . . . . . . . . . . . . . . . . . . . 90
groups
about . . . . . . . . . . . . . . . . . . 87, 277
deleting. . . . . . . . . . . . . . . . . . . . . 89
editing
from the group list index . . . . 90
editing in live . . . . . . . . . . . . . . . . 89
group list index
opening . . . . . . . . . . . . . . . . . 90
numeric view . . . . . . . . . . . . . . . . 90
ordered channels . . . . . . . . . . . . . 88
ordered view. . . . . . . . . . . . . . . . . 90
recalling . . . . . . . . . . . . . . . . . . . . 89
recording in live . . . . . . . . . . . . . . 88
recording with offset . . . . . . . . . . . 89
selecting . . . . . . . . . . . . . . . . . . . . 89
updating in live . . . . . . . . . . . . . . . 89
GUI. See Graphical User Interface
H
hang . . . . . . . . . . . . . . . . . . . . . . . . . 159
help system
description. . . . . . . . . . . . . . . . . . . 8
high See highlight
highlight . . . . . . . . . . . . . . . . . . . . . . 125
rem dim . . . . . . . . . . . . . . . . . . . 125
home (hardkey) . . . . . . . . . . . . . . . . 119
HTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
in cue list index . . . . . . . . . . . . . 193
346 Ion Operations Manual
I
image control
from encoders . . . . . . . . . . . . . . 116
import
ASCII . . . . . . . . . . . . . . . . . . . . . . 56
custom fixture . . . . . . . . . . . . . . . 85
Light Wright . . . . . . . . . . . . . . . . . 56
show file. . . . . . . . . . . . . . . . . . . . 56
in . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
independent
in cue list index . . . . . . . . . . . . . 193
indicators
in playback status display . . . . . . 41
indicators in live/blind. . . . . . . . . . . . . 35
intensity
manual override in playback . . . 217
set with level wheel . . . . . . . . . . 110
setting . . . . . . . . . . . . . . . . . . . . 110
-% . . . . . . . . . . . . . . . . . . . . 122
+%. . . . . . . . . . . . . . . . . . . . 122
intensity master . . . . . . . . . . . . . . . . 194
intensity palettes
description . . . . . . . . . . . . . . . . . 138
iRFR. . . . . . . . . . . . . . . . . . . . . . . . . 334
K
keypad
selecting channels with . . . . . . . 108
setting parameters with . . . . . . . 112
keywords
adding in patch . . . . . . . . . . . . . . 80
L
label
cue. . . . . . . . . . . . . . . . . . . . . . . 161
lamp controls . . . . . . . . . . . . . . . . . . 121
last (key). . . . . . . . . . . . . . . . . . . . . . 109
learn (key) . . . . . . . . . . . . . . . . . . . . 264
using in show control . . . . . . . . . 281
level wheel

setting intensity with . . . . . . . . . . 110
linear effects . . . . . . . . . . . . . . . . . . . 240
link/loop. . . . . . . . . . . . . . . . . . . . . . . 160
list view
group . . . . . . . . . . . . . . . . . . . . . . 90
palettes. . . . . . . . . . . . . . . . . . . . 146
presets . . . . . . . . . . . . . . . . . . . . 134
opening . . . . . . . . . . . . . . . . 134
submaster
editing from . . . . . . . . . . . . . 262
opening . . . . . . . . . . . . . . . . 262
Littlites. . . . . . . . . . . . . . . . . . . . . . . . . 13
live
{Address} . . . . . . . . . . . . . . . . . . 127
display indicators . . . . . . . . . . . . . 35
editing effects in . . . . . . . . . . . . . 242
editing groups in. . . . . . . . . . . . . . 89
editing palettes in . . . . . . . . . . . . 143
editing presets in . . . . . . . . . . . . 133
modifying cues in . . . . . . . . . . . . 165
park . . . . . . . . . . . . . . . . . . . . . . 223
parking addresses in . . . . . . . . . 224
recording cues in . . . . . . . . . . . . 151
recording multipart cues in . . . . . 204
storing macros in . . . . . . . . . . . . 264
storing presets in . . . . . . . . . . . . 130
text indicators . . . . . . . . . . . . . . . . 37
updating groups in . . . . . . . . . . . . 89
updating multipart cues in . . . . . 206
load
partial show . . . . . . . . . . . . . . . . . 49
submaster . . . . . . . . . . . . . . . . . 259
lock icon . . . . . . . . . . . . . . . . . . . . . . . 28
locking
facepanel . . . . . . . . . . . . . . . . . . . 28
loop. . . . . . . . . . . . . . . . . . . . . . . . . . 160
low See lowlight
lowlight . . . . . . . . . . . . . . . . . . . . . . . 125
LTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
in cue list index. . . . . . . . . . . . . . 193
M
macro editor display . . . . . . . . . . . . . 266
macros
about . . . . . . . . . . . . . . . . . . . . . 263
create new
using editor display . . . . . . . 268
deleting. . . . . . . . . . . . . . . . . . . . 270
editing . . . . . . . . . . . . . . . . . . . . 269
editor display . . . . . . . . . . . . . . . 266
playing . . . . . . . . . . . . . . . . . . . . 270
stopping . . . . . . . . . . . . . . . . . . . 270
storing in live . . . . . . . . . . . . . . . 264
using {Learn} . . . . . . . . . . . . . . . 264
make manual
about . . . . . . . . . . . . . . . . . . . . . 199
with multiple cue lists. . . . . . . . . 188
make null
about . . . . . . . . . . . . . . . . . . . . . 198
managing show files. . . . . . . . . . . . . . 47
manual control
{last}. . . . . . . . . . . . . . . . . . . . . . 109
{next} . . . . . . . . . . . . . . . . . . . . . 109
advanced . . . . . . . . . . . . . . . . . . 195
capture . . . . . . . . . . . . . . . . 200
copy to. . . . . . . . . . . . . . . . . 196
recall from . . . . . . . . . . . . . . 197
channel check . . . . . . . . . . . . . . 127
controlling non-intensity parameters
(NPs). . . . . . . . . . . . . . . 111
during playback . . . . . . . . . . . . . 216
encoder LCD . . . . . . . . . . . . . . . 113
flash . . . . . . . . . . . . . . . . . . . . . . 128
flip . . . . . . . . . . . . . . . . . . . . . . . 126
highlight . . . . . . . . . . . . . . . . . . . 125
home (hardkey) . . . . . . . . . . . . . 119
lowlight. . . . . . . . . . . . . . . . . . . . 125
make manual . . . . . . . . . . . . . . . 199
make null . . . . . . . . . . . . . . . . . . 198
offset . . . . . . . . . . . . . . . . . . . . . 109
remainder dim . . . . . . . . . . . . . . 123
selecting channels . . . . . . . . . . . 108
setting intensity . . . . . . . . . . . . . 110
setting lamp controls . . . . . . . . . 121
settings see setup.
sneak . . . . . . . . . . . . . . . . . . . . . 126
submasters . . . . . . . . . . . . . . . . 261
timing
manual, for cues . . . . . . . . . 156
manual override (key) . . . . . . . . . . . 217
in playback. . . . . . . . . . . . . . . . . 217
mark
about . . . . . . . . . . . . . . . . . . . . . 175
allowing live moves . . . . . . . . . . 176
AutoMark . . . . . . . . . . . . . . . . . . 176
AutoMark timing. . . . . . . . . . . . . 176
347

display indicators . . . . . . . . . . . . 178
flag . . . . . . . . . . . . . . . . . . . . . . . 163
referenced marks . . . . . . . . . . . . 177
removing referenced marks . . . . 178
setting referenced mark flags. . . 177
timing, referenced marks . . . . . . 181
master console
definition . . . . . . . . . . . . . . . . . . 307
merge
.esf . . . . . . . . . . . . . . . . . . . . . . . . 52
show file . . . . . . . . . . . . . . . . . . . . 52
MIDI
ports
configuring . . . . . . . . . . . . . . 305
setup . . . . . . . . . . . . . . . . . . . . . . 98
Show Control . . . . . . . . . . . . . . . 283
move to
in patch. . . . . . . . . . . . . . . . . . . . . 65
move to (softkey)
about . . . . . . . . . . . . . . . . . . . . . 128
in cue list index. . . . . . . . . . . . . . 194
with cues in blind . . . . . . . . . . . . 173
with cues in live . . . . . . . . . . . . . 166
moving lights
display conventions . . . . . . . . . . . 35
patching . . . . . . . . . . . . . . . . . . . . 66
multiconsole . . . . . . . . . . . . . . . 307–310
features of . . . . . . . . . . . . . . . . . 310
multipart cues . . . . . . . . . . . . . . . . . . 203
about . . . . . . . . . . . . . . . . . . . . . 203
attributes
setting . . . . . . . . . . . . . . . . . 205
changing into standard cues . . . 207
changing standard cues into . . . 207
recording in live . . . . . . . . . . . . . 204
storing in blind . . . . . . . . . . . . . . 207
updating in live . . . . . . . . . . . . . . 206
multiple intensity channels . . . . . . . . 120
multiple users . . . . . . . . . . . . . . . . . . 287
N
navigating
encoders . . . . . . . . . . . . . . . . . . . 46
navigation keys
{data} . . . . . . . . . . . . . . . . . . . . . . 39
{time} . . . . . . . . . . . . . . . . . . . . . . 39
next (key) . . . . . . . . . . . . . . . . . . . . . 109
nodes . . . . . . . . . . . . . . . . . . . . . . . . . 15
non-intensity parameters (NPs)
controlling . . . . . . . . . . . . . . . . . 111
setting
-% . . . . . . . . . . . . . . . . . . . . 122
+%. . . . . . . . . . . . . . . . . . . . 122
setting with encoders. . . . . . . . . 112
NPs. See non-intensity parameters
numbering
cues . . . . . . . . . . . . . . . . . . . . . . 150
numeric view
groups . . . . . . . . . . . . . . . . . . . . . 90
348 Ion Operations Manual
O
off (key)
using with faders . . . . . . . . . . . . 219
offline console
definition . . . . . . . . . . . . . . . . . . 307
offset . . . . . . . . . . . . . . . . . . . . . . . . 109
channels in groups . . . . . . . . . . . 89
in patch . . . . . . . . . . . . . . . . . . . . 72
online forums
register for . . . . . . . . . . . . . . . . . . . 8
open
direct selects . . . . . . . . . . . . . . . . 30
displays . . . . . . . . . . . . . . . . . . . . 33
from the browser . . . . . . . . . . 33
from the hardkeys . . . . . . . . . 33
from the softkeys. . . . . . . . . . 33
fixture creator. . . . . . . . . . . . . . . . 81
partial show . . . . . . . . . . . . . . . . . 49
slider module . . . . . . . . . . . . . . . . 30
virtual encoders . . . . . . . . . . . . . 115
ordered channels . . . . . . . . . . . . . . . . 88
ordered view
groups . . . . . . . . . . . . . . . . . . . . . 90
out
go to cue . . . . . . . . . . . . . . . . . . 191
out of sequence cues. . . . . . . . . . . . 212
using go to cue . . . . . . . . . . . . . 213
output address in patch . . . . . . . . . . . 63
output DMX . . . . . . . . . . . . . . . . . . . . 15
from Ion . . . . . . . . . . . . . . . . . . . 305
P
paging
encoders . . . . . . . . . . . . . . . . . . . 46

faders . . . . . . . . . . . . . . . . . . . . . 214
softkeys . . . . . . . . . . . . . . . . . . . . 46
palettes
about . . . . . . . . . . . . . . . . . . . . . 137
as absolute data. . . . . . . . . . . . . 144
beam . . . . . . . . . . . . . . . . . . . . . 138
color . . . . . . . . . . . . . . . . . . . . . . 138
deleting. . . . . . . . . . . . . . . . . . . . 147
editing in blind . . . . . . . . . . . . . . 144
spreadsheet view. . . . . . . . . 145
editing in live . . . . . . . . . . . . . . . 143
filters. . . . . . . . . . . . . . . . . . . . . . 141
focus. . . . . . . . . . . . . . . . . . . . . . 138
intensity . . . . . . . . . . . . . . . . . . . 138
list view. . . . . . . . . . . . . . . . . . . . 146
recalling . . . . . . . . . . . . . . . . . . . 142
rerecording . . . . . . . . . . . . . . . . . 143
selective storing
using {Record} . . . . . . . . . . . 140
storing . . . . . . . . . . . . . . . . . . . . 139
using {Record only} . . . . . . . 140
using {Record} . . . . . . . . . . . 139
types of. . . . . . . . . . . . . . . . . . . . 138
updating . . . . . . . . . . . . . . . . . . . 143
using about. . . . . . . . . . . . . . . . . 253
parameter category timing
setting. . . . . . . . . . . . . . . . . . . . . 156
parameter display
about . . . . . . . . . . . . . . . . . . . . . 111
parameters
display . . . . . . . . . . . . . . . . . . . . . 27
display in CIA . . . . . . . . . . . . . . . 111
homing . . . . . . . . . . . . . . . . . . . . 119
setting
keypad, using. . . . . . . . . . . . 112
park
about . . . . . . . . . . . . . . . . . . . . . 222
addresses in live . . . . . . . . . . . . 224
display
parking from. . . . . . . . . . . . . 225
in live . . . . . . . . . . . . . . . . . . . . . 223
scaled. . . . . . . . . . . . . . . . . . . . . 224
part. See multipart cues
partial filters . . . . . . . . . . . . . . . . . . . 185
partial show loading . . . . . . . . . . . . . . 49
partitioned control . . . . . . . . . . . . . . . 289
about . . . . . . . . . . . . . . . . . . . . . 290
create partitions . . . . . . . . . . . . . 291
partition list . . . . . . . . . . . . . . . . 290
selecting partitions. . . . . . . . . . . 290
setup . . . . . . . . . . . . . . . . . . . . . 290
using partitions . . . . . . . . . . . . . 292
patch . . . . . . . . . . . . . . . . . . . . . . . . . 59
1-to-1 . . . . . . . . . . . . . . . . . . . . . . 60
adding keywords . . . . . . . . . . . . . 80
applying curves in . . . . . . . . . . . 275
assigning curves in . . . . . . . . . . . 70
attribute display . . . . . . . . . . . . . . 70
changing views in . . . . . . . . . . . . 61
clear. . . . . . . . . . . . . . . . . . . . . . . 60
compound channel . . . . . . . . . . . 67
creating . . . . . . . . . . . . . . . . . . . . 63
database display . . . . . . . . . . . . . 72
device type
setting . . . . . . . . . . . . . . . . . . 63
dimmer. . . . . . . . . . . . . . . . . . . . . 64
dimmer doubling . . . . . . . . . . . . . 65
display . . . . . . . . . . . . . . . . . . . . . 61
Image . . . . . . . . . . . . . . . . . . 68
editing . . . . . . . . . . . . . . . . . . . . . 63
scrollers. . . . . . . . . . . . . . . . . 74
wheels . . . . . . . . . . . . . . . . . . 74
editor . . . . . . . . . . . . . . . . . . . . . . 75
fixture creator. . . . . . . . . . . . . . . . 81
move to . . . . . . . . . . . . . . . . . . . . 65
moving channels . . . . . . . . . . . . . 65
moving light . . . . . . . . . . . . . . . . . 66
offset, using . . . . . . . . . . . . . . . . . 72
output address. . . . . . . . . . . . . . . 63
picker . . . . . . . . . . . . . . . . . . . . . . 74
preheat . . . . . . . . . . . . . . . . . . . . 70
scroller picker . . . . . . . . . . . . . . . 74
selecting channels in . . . . . . . . . . 63
settings . . . . . . . . . . . . . . . . . . . . 68
status column . . . . . . . . . . . . . . . 63
tutorial
patching dimmers . . . . . . . . . 64
patching moving lights. . . . . . 66
unpatch a channel . . . . . . . . . . . . 65
wheel picker. . . . . . . . . . . . . . . . . 74
Phone Remote . . . . . . . . . . . . . . . . . 323
playback
fader controls
assert . . . . . . . . . . . . . . . . . 218
freeze . . . . . . . . . . . . . . . . . 218
Go . . . . . . . . . . . . . . . . . . . . 215
manual override . . . . . . . . . 217
349

off. . . . . . . . . . . . . . . . . . . . . 219
rate override. . . . . . . . . . . . . 220
release . . . . . . . . . . . . . . . . . 219
stop effect . . . . . . . . . . . . . . 219
Stop/Back . . . . . . . . . . . . . . 215
timing disable. . . . . . . . . . . . 218
intensity
manual override . . . . . . . . . . 217
manual control during. . . . . . . . . 216
out of sequence cues . . . . . . . . . 212
using {Go} . . . . . . . . . . . . . . . . . 215
using {stop/back} . . . . . . . . . . . . 215
using go to cue. . . . . . . . . . . . . . 213
playback faders
about . . . . . . . . . . . . . . . . . . . . . 209
playback status display
color indicators . . . . . . . . . . . . . . . 41
indicators . . . . . . . . . . . . . . . . . . . 41
text indicators . . . . . . . . . . . . . . . . 41
playing macros . . . . . . . . . . . . . . . . . 270
power
powering down . . . . . . . . . . . . . . . 23
powering up . . . . . . . . . . . . . . . . . 23
preheat
cue flag. . . . . . . . . . . . . . . . . . . . 163
in patch. . . . . . . . . . . . . . . . . . . . . 70
presets
about . . . . . . . . . . . . . . . . . . . . . 129
deleting. . . . . . . . . . . . . . . . . . . . 136
editing in blind . . . . . . . . . . . . . . 135
spreadsheet view. . . . . . . . . 136
table view. . . . . . . . . . . . . . . 135
editing in live . . . . . . . . . . . . . . . 133
list view. . . . . . . . . . . . . . . . . . . . 134
opening . . . . . . . . . . . . . . . . 134
recalling . . . . . . . . . . . . . . . . . . . 132
removing channels from. . . 136, 147
rerecording . . . . . . . . . . . . . . . . . 133
storing
using {Record Only}. . . . . . . 131
using {Record} . . . . . . . . . . . 130
storing in live . . . . . . . . . . . . . . . 130
updating . . . . . . . . . . . . . . . . . . . 133
using about. . . . . . . . . . . . . . . . . 253
primary console
definition . . . . . . . . . . . . . . . . . . 307
print
show file . . . . . . . . . . . . . . . . . . . . 53
proportional fader . . . . . . . . . . . . . . . 194
protocols. . . . . . . . . . . . . . . . . . . . . . 299
ACN . . . . . . . . . . . . . . . . . . . . . . 299
ArtNet . . . . . . . . . . . . . . . . . . . . 299
Avab UDP . . . . . . . . . . . . . . . . . 299
ETCNet2 . . . . . . . . . . . . . . . . . . 299
Local DMX . . . . . . . . . . . . . . . . . 299
350 Ion Operations Manual
R
Radio Focus Remote (RFR). . . . . . . 323
basic use . . . . . . . . . . . . . . . . . . 327
keypad. . . . . . . . . . . . . . . . . 327
LCD . . . . . . . . . . . . . . . . . . . 327
recharging . . . . . . . . . . . . . . 328
thumbwheels . . . . . . . . . . . . 327
changing frequency . . . . . . . . . . 326
in System Overview. . . . . . . . . . . 10
in System Riser
large . . . . . . . . . . . . . . . . . . . 19
operation modes . . . . . . . . . . . . 329
live. . . . . . . . . . . . . . . . . . . . 330
park . . . . . . . . . . . . . . . . . . . 329
patch . . . . . . . . . . . . . . . . . . 332
playback . . . . . . . . . . . . . . . 331
overview
base station receiver . . . . . . 325
handheld remote . . . . . . . . . 324
recharging . . . . . . . . . . . . . . . . . 328
technical specifications . . . . . . . 333
range editing new fixtures . . . . . . . . . 85
rate
cue attribute. . . . . . . . . . . . . . . . 161
rate override. . . . . . . . . . . . . . . . . . . 220
RDM
device details. . . . . . . . . . . . . . . 252
discovery . . . . . . . . . . . . . . . . . . . 69
enable . . . . . . . . . . . . . . . . . . . . 301
real time clock . . . . . . . . . . . . . . . . . 282
recall from . . . . . . . . . . . . . . . . . . . . 197
record
cue list . . . . . . . . . . . . . . . . . . . . 188
using {Record Only} . . . . . . 188
using {Record}. . . . . . . . . . . 188
cues
in live . . . . . . . . . . . . . . . . . . 151
using {Record Only} . . . . . . 152
using {Record}. . . . . . . . . . . 151
cues in blind. . . . . . . . . . . . . . . . 171
filters, with . . . . . . . . . . . . . . . . . 184
groups live . . . . . . . . . . . . . . . . . . 88

multipart cues. . . . . . . . . . . . . . . 204
attributes . . . . . . . . . . . . . . . 205
new cue list . . . . . . . . . . . . . . . . 188
using {Record Only}. . . . . . . 188
using {Record} . . . . . . . . . . . 188
palettes. . . . . . . . . . . . . . . . . . . . 139
with selective store . . . . . . . 140
partial filters, with . . . . . . . . . . . . 185
presets . . . . . . . . . . . . . . . . . . . . 130
submasters. . . . . . . . . . . . . . . . . 256
record defaults
setting. . . . . . . . . . . . . . . . . . . . . 100
record filters
storing data with . . . . . . . . . . . . . 186
referenced marks . . . . . . . . . . . . . . . 177
setting flags . . . . . . . . . . . . . . . . 177
timing . . . . . . . . . . . . . . . . . . . . . 181
register your Ion . . . . . . . . . . . . . . . . . . 3
relative effects. . . . . . . . . . . . . . . . . . 239
relay outputs . . . . . . . . . . . . . . . . . . . 283
release . . . . . . . . . . . . . . . . . . . . . . . 219
Release. See Sneak
rem dim. See remainder dim
remainder dim. . . . . . . . . . . . . . . . . . 123
highlight . . . . . . . . . . . . . . . . . . . 125
Remote Device Management
See RDM.
Remote Processor Unit (RPU) . . . . . 315
button configuration . . . . . . . . . . 317
hardware setup
front panel . . . . . . . . . . . . . . 316
rear panel. . . . . . . . . . . . . . . 315
in System Overview . . . . . . . . . . . 10
in System Riser
basic . . . . . . . . . . . . . . . . . . . 18
large. . . . . . . . . . . . . . . . . . . . 19
start up . . . . . . . . . . . . . . . . . . . . 316
Remote Video Interface (RVI). . . . . . 319
button configuration . . . . . . . . . . 322
hardware setup
front panel . . . . . . . . . . . . . . 321
rear panel. . . . . . . . . . . . . . . 320
in System Overview . . . . . . . . . . . 10
in System Riser
large. . . . . . . . . . . . . . . . . . . . 19
start up . . . . . . . . . . . . . . . . . . . . 321
remove
channels
from presets. . . . . . . . . 136, 147
referenced mark . . . . . . . . . . . . 178
replace . . . . . . . . . . . . . . . . . . . . . . . . 65
replace with . . . . . . . . . . . . . . . . . . . 173
rerecord palettes . . . . . . . . . . . . . . . 143
RFR. See Radio Focus Remote.
RPU. See Remote Processor Unit.
RVI. See Remote Video Interface.
S
save as. . . . . . . . . . . . . . . . . . . . . . . . 55
saving
existing show file . . . . . . . . . . . . . 55
quick . . . . . . . . . . . . . . . . . . . . . . 55
scaled park. . . . . . . . . . . . . . . . . . . . 224
scroller
calibrating . . . . . . . . . . . . . . . . . . 78
editing in patch . . . . . . . . . . . . . . 77
scroller picker . . . . . . . . . . . . . . . . . . . 74
scrolling displays . . . . . . . . . . . . . . . . 34
security
setup . . . . . . . . . . . . . . . . . . . . . 105
select channels
keypad . . . . . . . . . . . . . . . . . . . . 108
select last . . . . . . . . . . . . . . . . . . . . . 119
selecting
channels in patch. . . . . . . . . . . . . 63
selective store
negative . . . . . . . . . . . . . . . . . . . 153
positive . . . . . . . . . . . . . . . . . . . 153
with cues . . . . . . . . . . . . . . . . . . 153
Sensor feedback
enable . . . . . . . . . . . . . . . . . . . . 301
serial (RS-232) . . . . . . . . . . . . . . . . . 286
Services
ETC Technical . . . . . . . . . . . . . . . . 3
settings
attribute, in patch . . . . . . . . . . . . . 70
database, in patch . . . . . . . . . . . . 72
patch . . . . . . . . . . . . . . . . . . . . . . 68
setup . . . . . . . . . . . . . . . . . . . . . . . . . 93
desk settings . . . . . . . . . . . . . . . 100
Displays. . . . . . . . . . . . . . . . 103
Face Panel . . . . . . . . . . . . . 102
manual control
record defaults . . . . . . . . . . 100
MIDI
show control . . . . . . . . . . . . . 98
time code. . . . . . . . . . . . . . . . 98
351

opening . . . . . . . . . . . . . . . . . . . . 94
security. . . . . . . . . . . . . . . . . . . . 105
show. . . . . . . . . . . . . . . . . . . . . . . 94
show control . . . . . . . . . . . . . . . . . 98
show settings . . . . . . . . . . . . . . . . 95
cue settings . . . . . . . . . . . . . . 95
fader configuration. . . . . . . . . 96
SMPTE. . . . . . . . . . . . . . . . . . . . . 98
show control
about . . . . . . . . . . . . . . . . . . . . . 278
analog inputs . . . . . . . . . . . . . . . 283
configure ports . . . . . . . . . . . . . . 305
events. . . . . . . . . . . . . . . . . . . . . 278
MIDI Show Control . . . . . . . . . . . 283
real time clock . . . . . . . . . . . . . . 282
relay outputs. . . . . . . . . . . . . . . . 283
serial (RS-232) . . . . . . . . . . . . . . 286
settings. . . . . . . . . . . . . . . . . . . . . 98
using time code . . . . . . . . . 280–281
show file
create . . . . . . . . . . . . . . . . . . . . . . 48
deleting. . . . . . . . . . . . . . . . . . . . . 57
exporting . . . . . . . . . . . . . . . . . . . 56
importing . . . . . . . . . . . . . . . . . . . 56
loading parts of. . . . . . . . . . . . . . . 49
merging . . . . . . . . . . . . . . . . . . . . 52
name
bold . . . . . . . . . . . . . . . . . . . . 48
normal . . . . . . . . . . . . . . . . . . 48
new. . . . . . . . . . . . . . . . . . . . . . . . 48
open existing . . . . . . . . . . . . . . . . 48
print . . . . . . . . . . . . . . . . . . . . . . . 53
quick save . . . . . . . . . . . . . . . . . . 55
save as. . . . . . . . . . . . . . . . . . . . . 55
saving existing . . . . . . . . . . . . . . . 55
show setup . . . . . . . . . . . . . . . . . . . . . 94
{show settings} . . . . . . . . . . . . . . . 95
shutter control
from encoders . . . . . . . . . . . . . . 117
slider module
opening . . . . . . . . . . . . . . . . . . . . 30
with playbacks . . . . . . . . . . . . . . 214
SMPTE
setup . . . . . . . . . . . . . . . . . . . . . . 98
sneak
description . . . . . . . . . . . . . . . . . 126
softkeys
about . . . . . . . . . . . . . . . . . . . . . . 46
changing pages . . . . . . . . . . . . . . 46
context sensitive . . . . . . . . . . . . . 46
solo mode (softkey)
in cue list index . . . . . . . . . . . . . 194
spreadsheet view . . . . . . . . . . . . . . . . 45
editing palettes in. . . . . . . . . . . . 145
editing presets in . . . . . . . . . . . . 136
modifying cues from . . . . . . . . . 172
modifying using {move to} . . . . . 173
modifying using {replace with} . . 173
status
in patch . . . . . . . . . . . . . . . . . . . . 63
step effects. . . . . . . . . . . . . . . . . . . . 234
stop effect. . . . . . . . . . . . . . . . . . . . . 219
stop/back (key). . . . . . . . . . . . . . . . . 215
storing
palettes
using {Record Only} . . . . . . 140
using {Record}. . . . . . . . . . . 139
presets
using {Record Only} . . . . . . 131
using {Record}. . . . . . . . . . . 130
using record filters . . . . . . . . . . . 186
submasters
about . . . . . . . . . . . . . . . . . . . . . 256
bump button timing with. . . . . . . 261
clearing . . . . . . . . . . . . . . . . . . . 260
deleting . . . . . . . . . . . . . . . . . . . 260
effects . . . . . . . . . . . . . . . . . . . . 243
list . . . . . . . . . . . . . . . . . . . . . . . 262
editing from . . . . . . . . . . . . . 262
loading . . . . . . . . . . . . . . . . . . . . 259
manual control . . . . . . . . . . . . . . 261
recording . . . . . . . . . . . . . . . . . . 256
updating. . . . . . . . . . . . . . . . . . . 260
summary view . . . . . . . . . . . . . . . . . . 43
modifying cues from . . . . . . . . . 172
swap displays. . . . . . . . . . . . . . . . . . . 34
synchronized backup . . . . . . . . . . . . 311
setup . . . . . . . . . . . . . . . . . . . . . 311
syntax
structure. . . . . . . . . . . . . . . . . . . . . 4
using enter. . . . . . . . . . . . . . . . . . . 5
system
using about . . . . . . . . . . . . . . . . 247
System Components . . . . . . . . . . . . . 10
system riser
basic . . . . . . . . . . . . . . . . . . . . . . 18
352 Ion Operations Manual

T
large . . . . . . . . . . . . . . . . . . . . . . . 19
table view . . . . . . . . . . . . . . . . . . . . . . 44
editing presets in . . . . . . . . . . . . 135
modifying cues from . . . . . . . . . . 172
technical services . . . . . . . . . . . . . . . . . 3
text indicators
in live/blind . . . . . . . . . . . . . . . . . . 37
in playback status display . . . . . . 41
time
bump buttons . . . . . . . . . . . . . . . 261
cue
setting . . . . . . . . . . . . . . . . . 155
cues . . . . . . . . . . . . . . . . . . . . . . 155
delay. . . . . . . . . . . . . . . . . . . . . . 159
disable in playback. . . . . . . . . . . 218
discrete. . . . . . . . . . . . . . . . . . . . 158
Go To Cue . . . . . . . . . . . . . . . . . 213
manual control of, in playback . . 216
setting for parameter categories 156
time (navigation key). . . . . . . . . . . . . . 39
time code . . . . . . . . . . . . . . . . . . . . . 280
MIDI . . . . . . . . . . . . . . . . . . . . . . . 98
SMPTE. . . . . . . . . . . . . . . . . . . . . 98
timing disable
in playback . . . . . . . . . . . . . . . . . 218
trace
with update. . . . . . . . . . . . . . . . . 170
Track mode
deleting cues in . . . . . . . . . . . . . 174
trackball . . . . . . . . . . . . . . . . . . . . . . 115
U
undo
command history . . . . . . . . . . . . 201
using. . . . . . . . . . . . . . . . . . . . . . 201
unpatch a channel . . . . . . . . . . . . . . . 65
break nested references
with. . . . . . . . . . . . . . . . . . . . . . . 167
update
cues
using {Cue Only/Track} . . . . 169
without references . . . . . . . . 168
current cue . . . . . . . . . . . . . . . . . 170
dialogue box. . . . . . . . . . . . . . . . 167
fixture library in show file . . . . . . . 85
groups in live . . . . . . . . . . . . . . . . 89
inactive cues . . . . . . . . . . . . . . . 170
options . . . . . . . . . . . . . . . . . . . . 167
palette . . . . . . . . . . . . . . . . . . . . 143
presets. . . . . . . . . . . . . . . . . . . . 133
references
in cues. . . . . . . . . . . . . . . . . 168
source cue . . . . . . . . . . . . . . . . . 170
submasters . . . . . . . . . . . . . . . . 260
using trace . . . . . . . . . . . . . . . . . 170
update dialogue box. . . . . . . . . . . . . 167
user
data between different IDs. . . . . 288
ID
about . . . . . . . . . . . . . . . . . . 288
assigning . . . . . . . . . . . . . . . 288
relation to data sharing . . . . 288
multiple . . . . . . . . . . . . . . . . . . . 287
user ID
relation to data sharing . . . . . . . 310
with multiconsole . . . . . . . . . . . . 310
V
view
spreadsheet, in blind . . . . . . . . . . 45
table. . . . . . . . . . . . . . . . . . . . . . . 44
virtual encoders
opening . . . . . . . . . . . . . . . . . . . 115
use. . . . . . . . . . . . . . . . . . . . . . . 115
with scroller calibration . . . . . . . . 78
virtual faders
assigning . . . . . . . . . . . . . . . . . . 214
virtual faders See slider module. . . . . 30
virtual keyboard . . . . . . . . . . . . . . . . . 29
W
web site . . . . . . . . . . . . . . . . . . . . . . . . 3
wheel picker . . . . . . . . . . . . . . . . . . . . 74
working with a single cue list . . . . . . 149
working with multiple cue lists . . . . . 187
353

354 Ion Operations Manual

Corporate Headquarters 3031 Pleasant View Road, P.O. Box 620979, Middleton, Wisconsin 53562-0979 USA Tel +608 831 4116 Fax +608 836 1736
London, UK Unit 26-28, Victoria Industrial Estate, Victoria Road, London W3 6UU, UK Tel +44 (0)20 8896 1000 Fax +44 (0)20 8896 2000
Rome, IT Via Ennio Quirino Visconti, 11, 00193 Rome, Italy Tel +39 (06) 32 111 683 Fax +44 (0) 20 8752 8486
Holzkirchen, DE Ohmstrasse 3, 83607 Holzkirchen, Germany Tel +49 (80 24) 47 00-0 Fax +49 (80 24) 47 00-3 00
Hong Kong Rm 1801, 18/F, Tower 1 Phase 1, Enterprise Square, 9 Sheung Yuet Road, Kowloon Bay, Kowloon, Hong Kong Tel +852 2799 1220 Fax +852 2799 9325
Service: (Americas) service@etcconnect.com (UK) service@etceurope.com (DE) techserv-hoki@etcconnect.com (Asia) service@etcasia.com
Web: www.etcconnect.com Copyright © 2009 ETC. All Rights Reserved. Product information and specifications subject to change.
4310M1210-1.7.0 Rev A Released 2009-07

END USER LICENSE AGREEMENT (“EULA”)
PLEASE READ THE FOLLOWING CAREFULLY BEFORE
OPERATING/INSTALLING THE SOFTWARE. BY OPERATING/INSTALLING
THE SOFTWARE, YOU WILL BE DEEMED TO HAVE ACCEPTED AND
AGREED TO THE TERMS OF THIS AGREEMENT. THE SOFTWARE IS
LICENSED AND COPYRIGHTED (NOT SOLD).
Subject to the following terms and conditions, Electronic Theatre Controls, Inc.
(“ETC”) grants to you (“User”), a non-exclusive license to use the Software.
1. Grant of License
This is a worldwide, royalty-free, non-exclusive license granted to User subject to
and in accordance with the terms and conditions of this Agreement. ETC intends
to provide, but does not guarantee, updates or upgrades of the Software. ETC
will provide maintenance and support relating to the Software. The Software
may not be transferred, sold, assigned, leased, rented, sublicensed, or otherwise
conveyed, in whole or in part, by User to any third party without ETC’s prior
written consent.
You have acquired a device (“Device”) which includes software licensed by ETC
from one or more software licensors. The Software is licensed, not sold. You
may use the Software only on the Device.
2. ETC’s Software Rights
The Software is a proprietary product of ETC and is protected under all
applicable copyright laws and international treaties. Except for the limited license
granted herein, all right, title and interest to and in the Software remains forever
with ETC.
3. Additional Restrictions
User may not modify, distribute, rent, lease, or sell the Software, but User may
transfer User’s rights under this License on a permanent basis provided User
transfers this License, together with the accompanying Software, and all other
relevant materials, retaining no copies and the recipient party agrees to the terms
of this License. User agrees not to cause or permit the reverse engineering,
disassembly, or decompilation of the Software. Removal, emulation, or reverse
engineering of all or any part of the Software constitutes an unauthorized
modification to the Software and is specifically prohibited. If the Software is
licensed to a User for use in a member country of the European Union, User may
reverse engineer and/or decompile the Software to the extent that sufficient
information is not available for the purpose of creating an interoperable software
program and cannot be obtained by observing, examining or testing the program
(but only for such purposes and to the extent that sufficient information is not
provided by ETC upon written request). User shall not remove any product
MUN 101879-2.009900.0011 1

identification, copyright notices, or other notices or proprietary restrictions from
the Software.
4. Warranty Information
Software is provided “AS IS” under this License, without warranty of any kind,
either express or implied, including, without limitation, warranties that the
Software is free of defects, merchantable, fit for a particular purpose or noninfringing.
The entire risk as to the quality, operation, and performance of the
Software is with User. Should any Software prove defective in any respect, User
assumes the cost of any necessary servicing, repair or correction. This
disclaimer of warranty constitutes an essential part of this license.
5. Upgrades
If this copy of the Software is an upgrade from a previous version of the
Software, it is provided to you on a license exchange basis. You agree by your
installation and use of such copy of the Software to voluntarily terminate your
earlier Agreement and that you will not continue to use the earlier version of the
Software or transfer it to another person or entity.
6. Third-Party Software
The Software may contain third-party software not owned by ETC which requires
notices and/or additional terms and conditions. Such notices and/or terms and
conditions may be obtained by contacting your ETC sales rep and are made a
part of and incorporated by reference into this Agreement. In addition, certain
copyrights notices for such third party software also are included in the
documentation attached hereto. By accepting this Agreement, you are also
accepting the additional notices and terms and conditions, if any, set forth
elsewhere.
7. U.S. Government Restricted Rights
The Software and any documentation were developed at private expense, are
commercial, and are published and copyrighted. The Software and any
documentation may be transferred to the U.S. Government only with the prior
written consent of an officer of ETC. The Software and documentation are
provided with RESTRICTED RIGHTS. Use, duplication or disclosure by the U.S.
Government or any person or entity acting on its behalf is subject to restrictions
as set forth in subdivision (c)(1)(ii) of the Rights in Technical Data and Computer
Software Clause at DFARS (48 CFR 252.227-7013) for DoD contracts, in
paragraphs (c)(1) and (2) of the Commercial Computer Software-Restricted
Rights Clause in the FAR (48 CFR 52.227-19) for civilian agencies, or in the case
of NASA, in Clause 18-52.227-86(d) of the NASA Supplement to the FAR, or in
other comparable agency clauses. The contractor or manufacturer is Electronic
MUN 101879-2.009900.0011 2

Theatre Controls, Inc., 3031 Pleasant View Road, Middleton, Wisconsin, USA,
53562-0979.
8. Limitation of Liability
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER
TORT (INCLUDING NEGLIGENCE), CONTRACT OR OTHERWISE, SHALL
ETC BE LIABLE TO ANY PERSON OR ENTITY FOR ANY INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND
INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND
ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY
SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
THIS LIMITATION OF LIABILITY SHALL NOT APPLY (I) TO DEATH OR
PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO
THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION, (II) FOR
CONSUMERS WITH RESIDENCE IN A MEMBER COUNTRY OF THE
EUROPEAN UNION (A) TO DEATH OR PERSONAL INJURY RESULTING
FROM ETC’S NEGLIGENCE, (B) TO THE VIOLATION OF ESSENTIAL
CONTRACTUAL DUTIES BY ETC, AND (C) TO DAMAGES RESULTING FROM
ETC’S GROSS NEGLIGENT OR WILLFUL BEHAVIOR. SOME
JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF
INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
LIMITATION MAY NOT APPLY TO YOU.
9. Export Administration
The Software, including technical data, are subject to U.S. export control laws,
including without limitation, the U.S. Export Administration Act and its associated
regulations, and may be subject to export or import regulations in other countries.
User shall not directly or indirectly export or re-export the Software, or the direct
product thereof, without first obtaining ETC’s written approval. User agrees to
comply with all regulations and acknowledges that it has the responsibility to
obtain licenses to export, re-export, or import the Software. The Software may
not be downloaded or otherwise exported or re-exported (i) into, or to, any
country to which the U.S. has embargoed goods, or to a national or resident
thereof; or (ii) to anyone on the U.S. Treasury Department’s list of Specially
Designated Nationals and Blocked Persons List; or (iii) to any country facing U.S.
sanctions, as listed by the U.S. Treasury Department’s Office of Foreign Assets
Control.
10. Termination
Notwithstanding the above, ETC may, without prejudice to any other rights or
remedies, terminate this EULA, if any of the following events should occur: (i) if
you fail to perform or comply with any provision or term herein; and (ii) if you
become insolvent, go into liquidation, file or initiate an action for bankruptcy, or
have a receiver, administrative receiver or liquidator appointed or suffer similar
MUN 101879-2.009900.0011 3

measures in any relevant jurisdiction; or if you cease doing business in any form
or are no longer able to meet your obligations within the meaning of this EULA.
11. Confidentiality
You shall keep secret and confidential and shall not disclose to any third party
any and all confidential information owned or otherwise possessed by ETC
including without limitation the Software, the related documents and the contents
of this EULA without prior written approval from ETC.
12. Ownership
ETC and its licensors shall retain exclusive ownership of all world-wide
intellectual property rights in and to the Software and any copies of the Software.
All rights in and to the Software not expressly granted to User in this EULA are
expressly reserved for ETC and its licensors.
13. Warranty for Third Party’s Intellectual Property Rights
You shall indemnify, defend and hold harmless ETC and the Supplier (or
Suppliers, as applicable) from and against any and all losses, damages, claims,
liability, costs and expenses (including reasonable attorney fees), suffered or
incurred by ETC or the Supplier as a result of any claim by any third party that by
reason of your use or application of any intellectual property right contained in
the Software constitutes an infringement of any third party’s property rights,
including but not limited to, patent and copyright.
14. Destruction of the Software
Upon termination of this EULA, you must destroy the Software, the related
documents and any and all copies thereof within ten (10) days after the date of
termination and submit documents evidencing such destruction to ETC.
15. Miscellaneous
A) Complete Agreement: This Agreement is the complete agreement
between the parties with respect to the Software and supersedes any other
communication, written or verbal, with respect to the Software.
B) Severability: The provisions of this EULA are severable; if any term or
provision shall be deemed void or unenforceable by a court of competent jurisdiction,
such declaration shall have no effect on the remaining terms and provisions hereof.
C) Governing Law: This Agreement shall be governed by the laws of the
State of Wisconsin, USA.
MUN 101879-2.009900.0011 4

The Artistic License
Preamble
The intent of this document is to state the conditions under which a Package may
be copied, such that the Copyright Holder maintains some semblance of artistic
control over the development of the package, while giving the users of the
package the right to use and distribute the Package in a more-or-less customary
fashion, plus the right to make reasonable modifications.
Definitions:
* "Package" refers to the collection of files distributed by the Copyright Holder,
and derivatives of that collection of files created through textual modification.
* "Standard Version" refers to such a Package if it has not been modified, or
has been modified in accordance with the wishes of the Copyright Holder.
* "Copyright Holder" is whoever is named in the copyright or copyrights for the
package.
* "You" is you, if you're thinking about copying or distributing this Package.
* "Reasonable copying fee" is whatever you can justify on the basis of media
cost, duplication charges, time of people involved, and so on. (You will not be
required to justify it to the Copyright Holder, but only to the computing community
at large as a market that must bear the fee.)
* "Freely Available" means that no fee is charged for the item itself, though
there may be fees involved in handling the item. It also means that recipients of
the item may redistribute it under the same conditions they received it.
1. You may make and give away verbatim copies of the source form of the
Standard Version of this Package without restriction, provided that you duplicate
all of the original copyright notices and associated disclaimers.
2. You may apply bug fixes, portability fixes and other modifications derived from
the Public Domain or from the Copyright Holder. A Package modified in such a
way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided that
you insert a prominent notice in each changed file stating how and when you
changed that file, and provided that you do at least ONE of the following:
a) place your modifications in the Public Domain or otherwise make them
Freely Available, such as by posting said modifications to Usenet or an
equivalent medium, or placing the modifications on a major archive site such as
ftp.uu.net, or by allowing the Copyright Holder to include your modifications in the
Standard Version of the Package.

) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
4. You may distribute the programs of this Package in object code or executable
form, provided that you do at least ONE of the following:
a) distribute a Standard Version of the executables and library files, together
with instructions (in the manual page or equivalent) on where to get the Standard
Version.
b) accompany the distribution with the machine-readable source of the
Package with your modifications.
c) accompany any non-standard executables with their corresponding
Standard Version executables, giving the non-standard executables nonstandard
names, and clearly documenting the differences in manual pages (or
equivalent), together with instructions on where to get the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
5. You may charge a reasonable copying fee for any distribution of this Package.
You may charge any fee you choose for support of this Package. You may not
charge a fee for this Package itself. However, you may distribute this Package in
aggregate with other (possibly commercial) programs as part of a larger (possibly
commercial) software distribution provided that you do not advertise this Package
as a product of your own.
6. The scripts and library files supplied as input to or produced as output from the
programs of this Package do not automatically fall under the copyright of this
Package, but belong to whomever generated them, and may be sold
commercially, and may be aggregated with this Package.
7. C or perl subroutines supplied by you and linked into this Package shall not be
considered part of this Package.
8. The name of the Copyright Holder may not be used to endorse or promote
products derived from this software without specific prior written permission.
9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED

WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
The End
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
and Clark Cooper
Copyright (c) 2001, 2002 Expat maintainers.
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE
FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH
THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.