ETC Ion Xe Operating Manual

Eos family
Hide thumbs Also See for Ion Xe:
Table of Contents

Advertisement

Eos Family
(Eos Ti, Eos, Gio, Gio @5, Ion Xe, Ion Xe 20, and Element 2)
Operations Manual
Version 2.7.0
Part Number: 4250M1210-2.7.0 Rev A
Released: 2018-05

Advertisement

Table of Contents
loading

Summary of Contents for ETC Ion Xe

  • Page 1 Eos Family (Eos Ti, Eos, Gio, Gio @5, Ion Xe, Ion Xe 20, and Element 2) Operations Manual Version 2.7.0 Part Number: 4250M1210-2.7.0 Rev A Released: 2018-05...
  • Page 2 ETC®, Eos®, Eos Ti®, Gio®, Gio @ 5®, Ion Xe™, Ion®, Element 2™, Element™, ETCnomad®, and ETCnomad Puck® are either registered trademarks or trademarks of in the United States and other countries. All other trademarks, both marked and not marked, are the property of their respective owners.
  • Page 3: Table Of Contents

    Table of Contents Introduction Using this Manual Register Your Console Online Eos Family User Forums Help from ETC Technical Services Other Reference Materials Important Concepts Console Overview Eos Ti Geography Eos Geography Gio Geography Gio@5 Geography Ion Xe Geography Element 2 Geography...
  • Page 4: Using Channel Faders On Element

    Using Device List Clearing the Patch Update Library Fixture Editor Setup About Setup System User Device Basic Manual Control About Basic Manual Control Using Channel Faders On Element 2 Selecting Channels Setting Intensity Manual Control of Non-intensity Parameters (NPs) Home Multiple Intensity Channels Multicell Fixtures Lamp Controls...
  • Page 5 Recalling Palettes Editing Palettes Live Editing Palettes in Blind Using By Type Palettes Removing Channels from a Palette Deleting Palettes Storing and Using Presets About Presets Preset Options Storing Presets Live Recalling Presets Effects In Presets Editing Presets Live Using the Preset List Editing Presets in Blind Using By Type Presets Removing Channels From a Preset...
  • Page 6 Using [Capture] Using [Query] Using [Undo] Cue Playback About Cue Playback Playback Controls Selected Cue Out-of-Sequence Cues Virtual Faders Assigning Faders Displaying Fader Pages With Content Changing Fader Pages Playback Fader Controls Multipart Cues About Multipart Cues Record a Multipart Cue in Live Storing a Multipart Cue in Blind Deleting a Part from a Multipart Cue Creating and Using Effects...
  • Page 7 Recording a Submaster Submaster List Submaster Properties Submaster Information Labeling a Submaster Loading Submasters Using Bump Button Timing With Submasters Execute List Freeze and StopEffect on Submasters Moving and Copying Submasters Releasing Content From a Submaster Updating a Submaster Deleting a Submaster Using About About [About] [About]...
  • Page 8 Stop a Macro Delete a Macro Using Magic Sheets About Magic Sheets Magic Sheet Browser Navigating a Magic Sheet Creating and Editing Magic Sheets Examples of Magic Sheets Virtual Media Server About Virtual Media Server Media Content Exporting Media Content Patching the Virtual Media Server and Layers Creating a Pixel Map Working with the Virtual Media Server...
  • Page 9 MIDI Show Control String Interface MIDI Raw Open Sound Control (OSC) Eos Family Show Control Capabilities Advanced OSC Eos OSC Keys Facepanel Shortcuts Overview Displays Facepanel Operations Eos Family Hotkeys...
  • Page 11: Introduction

    Introduction This chapter contains the following topics: Using this Manual Register Your Console Online Eos Family User Forums Help from ETC Technical Services Other Reference Materials Important Concepts Introduction...
  • Page 12: Using This Manual

    Using this Manual This manual is for use with the Eos Titanium, Eos, Gio, Gio @ 5, Ion Xe, Ion Xe 20, Element 2, Eos RPU, Ion Xe RPU, and ETCnomad Puck control systems. For topics that apply to all of the platforms, Eos will be used.
  • Page 13: 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 website at 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.
  • Page 14: Important Concepts

    The following resources are recommended: John Huntington, Show Networks and Control Systems, (Brooklyn, NY:Zircon Designs Press, 2012) The ETC Support Articles: http://www.etcconnect.com/Support/ Important Concepts Before using your console, you should read and familiarize yourself with the concepts defined below.
  • Page 15 Each of these attributes is addressed by a dif- ferent output. Eos treats fixtures and channels as one and the same. Unlike former ETC consoles where a fixture occupied one channel for each parameter, Eos assigns each fixture a single channel number. Indi- vidual parameters are then associated with that channel as additional lines of channel information.
  • Page 16 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: Level Actions from the direct selects Parameters and Parameter Categories Eos divides fixture parameters into four major parameter categories: Intensity, Focus, Color, and Beam.
  • Page 17 Eos 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 con- sole is set to Cue Only, it behaves as a Track button. Tracking Mode When you create a new cue, any unchanged channel parameter data from the previous cue is tracked into the new specified cue.
  • Page 18 as follows: channel 1's new level is recorded into cue 2, channel 2's level is recorded into cue 1, and channel 3's level is recorded into cue 3. This is because the move instruction for those channels are contained in those cues. In the case of channels 1 and 2, their new level will track into cue 3.Using [Record] <Cue>...
  • Page 19 Block vs. Assert In previous ETC consoles, placing a block instruction on a channel was a way to treat a tracked value as a move instruction, both in editing and playback. In Eos, this behavior is now split up. Blocked channel data is an editing convention only, and it prohibits tracked instructions from modifying the associated data.
  • Page 20 Submasters can operate as HTP or LTP for intensity. The default is HTP. Eos’s default cue list setting for intensity is LTP. HTP is only applicable to the intensity of a channel. HTP channels will output the level that is the highest of all inputs.
  • Page 21: Console Overview

    Inside this section you will find general descriptions of your console and various areas of the user interface. This chapter contains the following topics: Eos Ti Geography Eos Geography Gio Geography Gio@5 Geography Ion Xe Geography Element 2 Geography Console Components Cleaning Your Console Console Capacities Console Overview...
  • Page 22: Eos Ti Geography

    Eos Ti Geography Below is a diagram of Eos Ti with references made to specific areas of use. The terms and names for each area and interface are used throughout this manual. Eos Family Operations Manual...
  • Page 23: Eos Geography

    Eos Ti Fuse Replacement CAUTION: For continued protection against risk of fire, replace only with same type and rat- ing of fuse. CAUTION: Pour ne pas compromettre la protection contre les risques d’incendie, remplacer par un fusible de même type et de mêmes caractéristiques nominales. Fuse replacement information and additional electrical ratings can be found on this label located on Eos Ti’s rear panel.
  • Page 24 Eos Button Modules Note: Button modules are only for use with Eos consoles. The Eos button modules provide the ability for multiple simultaneous button presses with tactile feed- back. The displays and text above each button change to reflect the current mapping of the button. Button modules are available in a 50 button array for use with the direct selects.
  • Page 25: Gio Geography

    3. To remove the module, slide the release latch (located to the right of the respective module) upwards and pull the module out from right to left. Gio Geography Below is a diagram of Gio with references made to specific areas of use. The terms and names for each area and interface are used throughout this manual.
  • Page 26: Gio@5 Geography

    Gio@5 Geography Below are diagrams of the Gio @ 5 console with references made to specific areas of use. The terms and names for each area and interface are used throughout this document. Eos Family Operations Manual...
  • Page 27: Ion Xe Geography

    Ion Xe Geography Below are diagrams of Ion Xe and Ion Xe 20 with references made to specific areas of use. The terms and names for each area and interface are used throughout this manual. Ion Xe Console Overview...
  • Page 28 Ion Xe 20 WARNING: This device contains a lithium battery. Battery may explode if mistreated. Do not recharge, disassemble or dispose of in fire. CAUTION: For continued protection against risk of fire, replace only with same type and rat- ing of fuse.
  • Page 29: Element 2 Geography

    Element 2 Geography Below is a diagram of Element 2 with references made to specific areas of use. The terms and names for each area and interface are used throughout this manual. WARNING: This device contains a lithium battery. Battery may explode if mistreated. Do not recharge, disassemble or dispose of in fire.
  • Page 30: Console Components

    Console Components This section discusses the various console components that were called out in the geography sec- tion. Power Button USB Ports Touchscreens External Monitors Backlit Keys Control Keypad Navigation Keypad Fader Control Buttons Rate and Fader Page Grandmaster and Blackout Level Wheel Master Playback Controls Encoders...
  • Page 31 CAUTION: The USB ports cannot be used for charging devices such as cell phones. Touchscreens Eos Ti Eos Ti is designed with three internal LCD touchscreen displays. LCD touchscreens A & B may be used to display show data (with touchscreen interface), or they may be used as direct selects or a vari- ety of other virtual controls and displays.
  • Page 32 Gio @ 5, Ion Xe, and Element 2 support up to two external Windows 7 compatible display port mon- itors. Note: While it is possible to assign a resolution lower than the minimum (1280x1024), it is recommended to be at 1280x1024 or higher.
  • Page 33 On Element 2, {Rate} is part of the {Fader Control} options. Press [Live] to see the {Fader Control} softkey. To change the fader page on Element 2, press {Page Subs}. See Paging Submasters (on page 364) for more information. Grandmaster and Blackout The grandmaster inhibits all live intensity values.
  • Page 34 Mini Encoder display. To post beam to the command line, double press the shutter, image, or form parameter category buttons. Gio @ 5 and Ion Xe Encoders Encoders are provided above the control keypad, below the touchscreen. The four encoders are pageable controls, which are populated with the parameters used in your show.
  • Page 35 Motorized Faders Note: Ion Xe and Element 2 do not come with motorized faders. One dedicated main playback and ten motorized faders are provided. The faders may be configured as playbacks, submasters, or grandmasters. A hundred pages of 10 faders each are provided. The bottom of the touchscreen shows fader status information and provides a load button for each fader.
  • Page 36: Cleaning Your Console

    Eos Ti, Gio, Gio @ 5, Ion Xe, and Element 2 have DMX ports. To output, connect one 5 pin XLR cable per port. The first port will default to outputting the first universe of DMX, addresses 1-512, the...
  • Page 37 Gio @ 5 has 5 motorized faders x 100 pages for configurable cue lists, submasters, grand mas- ters, IFCB Palette/ Presets lists, or individual instances Ion Xe and Ion Xe 20 have 1 dedicated Master Playback pair, with Go and Stop/ Back Ion Xe 20 has 20 faders with 40 configurable buttons.
  • Page 38 Eos Family Operations Manual...
  • Page 39: System Basics

    C h a p t e r 2 System Basics This chapter contains the following topics: About System Basics The Central Information Area (CIA) Browser Softkeys Displays Display Control and Navigation Live and Blind Displays Playback Status Display Using Direct Selects Encoders Moving Light Controls Fader Configuration...
  • Page 40: About System Basics

    About System Basics This section explains the base level procedures for setting up, navigating, and understanding how to operate your console. Power Up the Console 1. Attach the appropriate power cable to the IEC connector on the rear of the console. 2.
  • Page 41 CIA Icons There are three icons located above the CIA. Favorite CIA Display You can select a favorite default display for the CIA that will show when [Displays] is pressed. The standard default display for the CIA is the Browser. The favorite display will show a gold star icon at the top of the CIA by the arrow and lock icons. Dis- plays that can be selected as a favorite, but are currently not, will show a gray star at the top of the CIA.
  • Page 42 Note: Press [Clear] to remove commands from a terminated command line. Use [Shift] & [Clear] to remove commands from a command line that is not terminated. Syntax Structure (on page 13) for more information on using the command line. Command Line Prompt Note: This feature is only available on Element 2.
  • Page 43: Browser

    When collapsed, only the {All NPs}, {All Speed}, and {Expand Arrow} buttons will be displayed. Labeling [Label] is used to attach an alphanumeric label to an object such as cues, channels, submasters, etc. [Label] [Label] when appended to a record target command, clears the current label. This includes show file labels.
  • Page 44 Use the page arrow keys to move the selection bar up and down the list. You may also use the level wheel to scroll through the list. When the bar highlights the desired menu, press [Page u] to open the menu. Continue pressing [Page u] to open submenus.
  • Page 45 From this menu you can select one of the available clear options by clicking on the desired button in the CIA. Eos will ask you for a confirmation before performing the selected clear. For {Clear Targets}, Eos will allow you to choose which record targets you want to clear. CAUTION: Clear functions cannot be undone by using the Undo option.
  • Page 46: Softkeys

    On Element 2, those softkeys correspond to buttons [S1] - [S6] and [More SK] on the facepanel. For Gio, Gio @5, Ion Xe, and the Eos Programming Wing, you can hold down [More SK] & Encoder Category Button to access the second page of softkeys.
  • Page 47 Eos has the ability to have one of three different workspaces active on individual monitors, as well as to have up to four frames in use in any workspace. Each frame can hold multiple tabs. Each tab con- tains one display. Workspaces Workspaces offer independent display control on all of your connected monitors.
  • Page 48 Note: From an alphanumeric keyboard, hold down either of the bracket buttons ([ or ]) and type in the number of the workspace you wish to view. For examples, hold down [ and press 2 to view workspace 2. Frames Each workspace can have up to four frames in its layout.
  • Page 49 Keys 17 Groups 27 Color Picker 37 sACN Output View Effect Channels 18 Macros 28 Virtual Faders 99 Diagnostics Pixel Maps 19 Snapshots 29 About 100 User Manual 10 Pixel Preview 20 Park 30 Command History Display Tabs The following displays can be selected, and they will open in a new tab in the selected frame: The following displays can have multiple instances open: Channel (Summary) Channel (Table)
  • Page 50: Display Control And Navigation

    Tab Tools Every frame has a tab tools menu in the lower left corner of the frame. Selecting this menu icon will open the tab tools menu, which provides options for opening and closing tabs in that frame. You can left click with a mouse or double tap a tab in focus to also see this menu. The following is a list of menu options.
  • Page 51 of record targets (also called “lists”) can be quickly accessed by double pressing the record target button (for example, [Cue] [Cue] opens the cue list index). The Live/Blind display is open as tab 1. The playback status display is always open as tab 2. Neither of these displays can be closed.
  • Page 52 Closing Displays To close any tab display, select the display by using the [Tab] key or other means of navigation. When the desired display is active, press [Escape] to close it. To close a display in the CIA, press the [Displays] key and the browser will reappear. To close all displays except for the live/blind display and the playback status display (tabs 1 and 2), press [Shift] &...
  • Page 53 recalled from any selected monitor from the Home Screen or the Display Controls menu screen. You can recall a monitor-only snapshot from the command line by using the syntax [Snapshot] [n] [Enter]. When recalled from the command line, the selected snapshot will only affect the monitor from which it was originally recorded.
  • Page 54 Resize Frames Select this icon to resize frames in any of the workspaces on the monitor. After selecting, resizing tools will appear between frames of the workspace and you can select and drag the resize tool icons to adjust sizing as needed. Monitor Mapping Select this icon to arrange your monitors without having to go into the ECU.
  • Page 55 Close All Tabs in This Workspace Select this icon to close all of the tabs in the active workspace on this monitor only. Reset This Display This icon will close all of the tabs and frames and will reset the layout for the active workspace to a single frame displaying the Home Screen, from which you can select new tabs to open.
  • Page 56 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 by holding down the left mouse button and rolling the scroll wheel on a mouse.
  • Page 57 There are three icons: Wand - popup magic sheet Moving Light Beams - popup moving light controls Camera -popup snapshots Popup Magic Sheet This option allows you to view a favorite magic sheet in a small popup window over your current dis- play.
  • Page 58: Live And Blind Displays

    absolute data will be displayed instead. If you are viewing a preset, absolute or palette data will be dis- played, depending on what is contained in the preset. You can lock this mode by pressing [Data] twice. When in display reference values mode, “Data Latched”...
  • Page 59 To collapse the summary view, hold down the [Params] key and press any parameter category key. On Element 2, to collapse the summary view, hold down [Data] and any of the parameter category key in the parameter display (Focus, Color, Image, Shutter, or Form). 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 [Params] key and pressing any para- meter category key.
  • Page 60 When a category has been expanded, to hide or reveal only certain parameters, press and hold [Data] or [Params] 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] or [Params] button, the buttons of parameters that are currently selected for viewing will be highlighted in the CIA.
  • Page 61 In {Preview} mode, the following softkeys are available: {Previous} - previews the last cue run from the selected cue list. {Pending} - previews the pending cue from the selected cue list. The following examples show other functions that are available in Preview: {Preview}[Next] will allow you to preview the cue higher than the one currently selected.
  • Page 62 Live and Blind Configuration Menu (on page 65) Indicators in the Live/ Blind Display Eos 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 Eos to indicate conditions to you.
  • Page 63 Note: The color and text conventions apply regardless of the format of Live/ Blind being used (see Using [Format] (on page 56)). Note: When manual channels are used, there will be an advisory that says "Manual Chan- nels" in red in the upper left hand corner of any Live display. Most of the channels in the above image are conventional channels (intensity is the only available parameter).
  • Page 64 Moving Lights or Multi-parameter Devices This view also has additional data fields beneath intensity (F, C, B). This information can be sup- pressed by pressing [Params] and any parameter category (Focus, Color, or Beam) in the CIA. Doing so will leave only the intensity field and FCB indicators at the bottom of the channel. Multicell Devices Parameter data can also be suppressed in the same way as moving lights.
  • Page 65 You can use flexichannel modes to hide cells or master channels. See Using Flexichannel (on page 66) for more information. Note: A decimal will display at the end of a master channel when flexi cells off is on. Color Indicators Eos uses color to indicate the selection state and information about channel/parameter levels. Channel Numbers/ Channel Headers Gray number Unpatched channel number.
  • Page 66 Dark Red Manual Data (any data that has been set but not yet stored to an active cue or sub- master) from other consoles that are using different user IDs. Blue The intensity value is higher than in the previous cue. Non-intensity parameters (NPs) are in blue when any move instruction has occurred.
  • Page 67 M Indicates a mark is placed, but manual, and must be stored. Is blue when stored.”m” indic- ates cue is not marking. MK Indicates the channel is marked for a later cue. The cue number is indicated in the other categories (see “Q”...
  • Page 68 MC Line Wrap - When enabled, this option keeps all of the cells together of a multicell fixture when viewing it in Live summary view instead of breaking them up across multiple rows. Suppress Target Labels - Hides the Label column in Blind spreadsheet view. Show Reference Labels - When enabled, referenced record targets (such as presets or palettes) with labels will have their labels displayed rather than their target type and number.
  • Page 69 effects, non-intensity moves, or marking.) Selected channels There are three Flexichannel modes, which can be used along with the Flexichannel states: Cells off (displays only the master channels for multicell fixtures. Master channels will display with a "." after the channel number to indicate that they have cells hidden.) Masters Off (displays only the cells for multicell fixtures) Partitioned (displays only those channels defined in the current partition) Note:...
  • Page 70: Playback Status Display

    You may still hold [Time] on Eos or double press [Time] on Eos Ti and Gio to view the discrete time behind any parameter or category. The display will remain in this state until you disengage it by pressing [Flexi] again. About &...
  • Page 71 An optional command line for the playback status display is available. The optional command line must be enabled to use. See Playback Status Display Configuration (on page 74). There are three formats for the playback status display on all consoles except Element 2: Expanded Cue List Format (on the next page) Split Playback Status Display (on page 71) Fader Display Format (on page 71)
  • Page 72 Expanded Cue List Format Pressing [Format] with the playback status display active will access this format. In expanded cue list, the view of the active cue list increases to the full size of the display. The current fader page is visible at the bottom of the screen.
  • Page 73 Fader Display Format Pressing [Format] with the playback status display active will access this format, which shows a view of the fader configurations for 10 pages of 10 faders each (for a total of 100 visible faders. Each fader is color coded based on its assigned target type. Grandmasters and inhibitive submasters are in red, additive submasters are yellow ,playback faders display in green ,and presets and palettes are orange.
  • Page 74 PSD visible showing that cue list, nothing will be paged. Indicators in the Playback Status Display Eos 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 Eos to indicate conditions to you.
  • Page 75 Color indicators Cue List Gold - Any item (cue, list, page) highlighted in gold indicates “current”. Outlined in gold indicates “selected”. Red - Cue fade is in progress Fader Ribbon / Display Red - Grandmasters and inhibitive submasters Yellow - Additive submasters Green - Playback faders Orange - Presets and palettes Text indicators...
  • Page 76 F1 - F10 - Indicate faders numbered 1 through 10 on the console. Found at the bottom of the fader display. F5 (see in cue 1) - Indicates a follow time associated with the cue (in this case, 9 seconds). Found in the cue display.
  • Page 77 The following options are available in the PSD Configuration Menu: Target Grid - this option is only available when the PSD is split, and is used along with the Lock Status option. Target Grid allows you to select either the top or bottom display. Press [Format] to split the PSD.
  • Page 78: Using Direct Selects

    Reorder Columns Reorder columns allows you choose what data displays in the PSD and what order it displays in. By default, all columns except notes will be displayed. The arrow keys on the right can be used to move columns around. Columns are moved in groups. To select a column header to move, click or tap the name.
  • Page 79 Effects - purple Snapshots - red Magic Sheets - magenta Scenes - green Custom - light gray If there are more items than can be viewed at once, you may view subsequent pages by using the page touchbuttons ({p}, {q}) by the direct selects. Hold a page button down and type a number to jump to a specific direct select.
  • Page 80 The following options are available: # of Banks - sets the number of direct select banks that will display. Layout 25, 50, 100, 200 - allows you to select the number of buttons that will display per bank. Rows - allows you to select the number of rows in the banks. Columns - allows you to select the number of columns in the banks.
  • Page 81 Maximize Button Size - sets the size of the direct select buttons to fill the available space. This is similar to Fit to Screen in previous versions of software. Reset to Default - will restore the settings to the default state. If no default state has been set, the Eos default settings will be used.
  • Page 82 Scenes on Custom Direct Selects Scenes can be assigned to custom direct selects. To assign a scene to a direct select, you can either tap on a direct select to open the configuration window, or you can use the command line. From the configuration window, you can select the target type of scene, and the scene number.
  • Page 83 From the configuration window, you can select the target type of scene, and the scene number. Only one scene can be assigned at a time. From the command line, you can select a scene, such as [Cue] [1] {Attributes} {Scene} [1] [Enter]. Then double click on a direct select to assign the selection.
  • Page 84: Encoders

    The bottom two encoders are always in control of pan and tilt respectively from left to right. On Gio, Gio @ 5, and Ion Xe, the four encoders are identified in two ways, by the encoder controls display and the mini encoder status display.
  • Page 85 On Element 2, you can access encoder control by using the ML controls display. See Moving Light Controls (on page 86) for more information. Encoder Display on Eos and Eos Ti The encoder display area will show the name of the parameter it controls, display stepped limits (if any) and also a {Home} button which allows you to set that parameter to its default position.
  • Page 86 Encoder Controls Display The encoder controls display is available on Gio, Gio @ 5, and Ion Xe consoles. Press the [Encoder Dis- play] hardkey to open the encoder controls display.
  • Page 87 Using the Scroller/Wheel Picker and Editor (on page 125)). Mini Encoder Display On Gio, Gio @ 5, Ion Xe, or ETCnomad using a Programming Wing, information on what the encoders are currently controlling can always be found in the mini encoder status display, even when the Encoder Controls Display (on the previous page) is closed.
  • Page 88: Moving Light Controls

    Some fixtures have more parameters than can be displayed on one encoder page. The number of pages for each category is displayed at the top of the encoder touchscreen. To view the other pages, simply press the [Color], [Custom], [Shutter], [Image], or [Form] button to advance the pages or press the button with a number key to go directly to the page you want to access.
  • Page 89: Fader Configuration

    1. Category button (Clicking this button will put the category on the command line.) 2. Parameter button (Clicking the button will put the parameter on the command line.) 3. Home button allows you to home a specific parameter or attribute of a parameter. 4.
  • Page 90 Each fader is color coded based on its assigned target type. Grandmasters and inhibitive submasters are in red, additive submasters are yellow ,playback faders display in green ,and presets, palettes, global effects, and manual time masters are brown. On Element 2, playback faders cannot be assigned. Fader Configuration Window Click on the fader header to open the fader configuration window.
  • Page 91 Note: Content can also be loaded to faders from Live, using the command line and load. Discrete Instance This setting defaults to Yes and applies to cue lists. When a fader is discrete, it will track other faders that are running the same cue list, BUT if a fader that it is tracking manually changes to a different cue list, a discrete enabled fader will not change its content.
  • Page 92 The fader status display can be disabled in Setup. See Displays (on page 165) for more information. 1. Orange box indicates a channel fader. 2. Current channel number controlled by fader. 3. Label (channel and target labels will display). 4. Current channel level. (Level will display regardless of control from fader or keypad.) 5.
  • Page 93 You can also make changes to a fader's configuration while in the fader list display by clicking on a column. A virtual fader will be displayed. Click on the appropriate area of the fader to access the con- figuration options. Selection can be done by clicking in the column or from the command line. Range editing is possible in this display by selecting all the needed faders.
  • Page 94 In the above screenshot, Fader 1 has discrete off . There is a link icon that displays to indicate that dis- crete is off. Master Fader Configuration Click or tap Master Fader to open the master fader configuration window. Target This setting allows you to map a cue list to a fader.
  • Page 95 Grandmaster Configuration When a fader is configured as a grandmaster, you can set the fader itself as a master or disable it. Fader size is set to 1x, and can not be changed. The first button is locked as a load button, and cannot be configured. The second button is disabled and cannot be configured.
  • Page 96 Note: The setting of the manual time master is ignore unless turned on. Changing the manual timing master will not impact any manual changes already in motion. The fader ribbon will display the label of M Time to indicate a manual time master fader. Note: Channel and parameter filters can be assigned to a manual time master.
  • Page 97 Fader list (Tab 35) In Live using the {Properties} softkey Tap or click on {Chan Filter} to assign channels or groups. Tap or click on {Param Filter} to open a list of available parameters that you can filter. Note: Filters will travel with their assigned cue lists and submasters wherever they are mapped.
  • Page 98: Virtual Keyboard

    The following options are available in this configuration menu: Rows - sets the number of rows used for the module. Maximum number of rows is six. Columns - sets the number of columns used for the module. Maximum number of columns is six.
  • Page 99: Sacn Output Viewer

    C - CTRL A - ALT sACN Output Viewer You can open the sACN Output Viewer by pressing [Tab] & [3][7] or selecting the sACN Output Viewer icon from the home screen. The sACN Output Viewer is a place to check the current live outputs on a universe by universe basis. The left side of the viewer is the universe grid.
  • Page 100 The following options are available in this configuration menu: {Follow Command Line} - when enabled, the viewer will follow the command line for selecting addresses. This is enabled by default. Universe - you can select which universe to jump the viewer to. Eos Family Operations Manual...
  • Page 101: Managing Show Files

    C h a p t e r 3 Managing Show Files This chapter contains the following topics: About Managing Show Files Create a New Show File Open an Existing Show File Merging Show Files Printing a Show File Saving the Current Show File Importing Show Files Exporting a Show File Exporting Logs...
  • Page 102: About Managing Show Files

    About Managing Show Files This section explains how to create, open, and save your show files. Each of these operations are accomplished through the Browser (on page 41) area in the The Central Information Area (CIA) (on page 38). Create a New Show File To create a new show file, navigate within the browser to: File>...
  • Page 103 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 and you wish to load an older version, navigate to the desired revision and press [Select]. This will open the partial show loading screen in the CIA.
  • Page 104 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.
  • Page 105: Merging Show Files

    Start - The first in a range of components. 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).
  • Page 106 Note: Media is imported gobo and magic sheet images, and will be included by default when you select Patch, Fixtures, or Magic Sheets. 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 par- tial components in the current show file.
  • Page 107: Printing A Show File

    5. Enter the numbers using the keypad to specify the desired cues/groups/effects and so on. 6. Press {OK} to load the components to the current show Partial Patch Merging You have the option to selectively merge partial patch information or fixtures into a show file by selecting the {Advanced} button in the partial show merge screen.
  • Page 108 In Setup, you can select the page orientation and paper size for these PDF files, see PDF Settings (on page 168) for more information. To save a PDF of an Eos Family show file, navigate within the browser to: File> Print> and press [Select].
  • Page 109: Saving The Current Show File

    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).
  • Page 110: Importing Show Files

    Eos provides you with three locations to save an Eos Family 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.
  • Page 111 Note: Not all data is saved to a .csv file. It is recommended that you first export as a .csv file, modify the file as needed, and then import. See Exporting a Show File (on the next page) for more information. Lightwright Import Once a file has been selected for import, you will now have options for importing.
  • Page 112: Exporting A Show File

    Address Formats Eos will accept mulitple address formats for importing. Examples of those formats are 2/3, 2.3, 2,3, 2-3. Eos will convert all formats to n/n. Device Mapping Devices can also be mapped. Click {Map Devices} to open the following display. Select the Lightwright device and the match from the Eos column.
  • Page 113: Exporting Logs

    {Ok}. You will be prompted to name the file. A .csv file will be created. Exporting Logs Logs are useful tools for diagnosing issues. ETC Technical Services may request that you email logs if they are assisting you with an issue. See Help from ETC Technical Services (on page 11)
  • Page 114: File Manager

    File Manager Eos has a File Manager (on page 485), which also provides a way to manage show files. Eos Family Operations Manual...
  • Page 115: Patch

    C h a p t e r 4 Patch This chapter contains the following topics: About Patch Patch Main Displays Patching Conventional Fixtures Patching Moving Lights, LEDs, and Accessories Patching MultiCell Fixtures Labeling Using the Scroller/Wheel Picker and Editor Settings in Patch Using Device List Clearing the Patch Update Library...
  • Page 116: About Patch

    About Patch Eos treats fixtures and channels as one and the same, meaning each fixture is assigned a single con- trol channel number. Individual parameters of that fixture, such as intensity, focus, color, and beam are also associated with that same channel number but as additional lines of channel information. The Patch is used to associate a channel with addresses and device types.
  • Page 117: Patch Main Displays

    Note: You can open or merge patch data from other show files, see Partial Patch Opening (on page 102) Partial Patch Merging (on page 105) for more information. A 1-to-1 patch can be created from the Clear display. See Clearing the Patch (on page 142) Patch Main Displays To begin patching your show, you must first open the patch display.
  • Page 118: Patching Conventional Fixtures

    Status in the Patch Display Status flags will display on the far left of the patch display to advise you when a channel or address requires your attention. A red “!” or yellow “?” will display when there is an error or warning from an RDM, CEM+, CEM3, or ACN device.
  • Page 119 Additional examples of patch by channel: [5] [At] [1][0][0] [Enter] - patches channel 5 to address 100. [2][0][3] [At] [1][2] [Enter] - patches channel 203 to address 12. Range Patching Range patching using the [Thru] key allows you to quickly patch a group of channels. [1][Thru][2][0] [At] [1] [0] [Enter] patches channels 1 through 20 to addresses 10 through 29.
  • Page 120 Port/ offset refers to the DMX universe or port and the offset of the address. For example, since a single DMX port can transmit 512 addresses (known as a “universe”), the port/ offset for address 515 would look like 2/3 because address 515 is the 3rd address of universe 2. An example of patching by port/ offset in patch by address mode is [2][/][1][0] [At] [2][0] [Enter], which patches universe 2 address 10, or 522, to channel 20.
  • Page 121 [1] [Thru] [9] [6] [At] [1] [Enter] Now you wish to dimmer double 1 through 12 of your Sensor+ rack and you want these to be channels 97 through 108. To patch this, press: [9] [7] [Thru] [1] [0] [8] [At] [1] {B} [Enter] Channels 97 through 108 are patched to address 1 through 12 B, while channels 1 through 12 are now patched to address 1 through 12 A.
  • Page 122 [Copy To] - copies a channel to another location within patch. [Copy To] {Plus Show} - copies a channel to another location within patch and all record tar- gets in the show. [Copy To] {Only Show} - copies a channel to another location with all record targets in the show but not the patch data.
  • Page 123 [6] [Thru] [1] [0] [Delete] [Enter] [Enter] -or- [Delete] [1] [Thru] [1] [0] [Enter] [Enter] CAUTION: If a channel with programmed data is deleted, the recorded data will be lost. [Query] {Unpatched} To quickly delete channels without addresses in the Patch display, you can use the command [Query] {Unpatched} [Delete].
  • Page 124: Patching Moving Lights, Leds, And Accessories

    Assuming that channel 9 is already patched to an address, this will create a part 2 and address it at 540. [8] [Part] [2] [At] [5] [1] [3] [Enter] This will create a part 2 for channel 8 and address it at 513. If you wish to patch by address while in the channel view, press: [Address] [5] [1] [3] [At] [8] [Enter] Assuming channel 8 was previously patched to an address, this will create a part 2 and address it at...
  • Page 125 {Show} provides you with the option of showing only the library of fixtures or devices that are already patched in the show, your favorites, and default devices. {Manfctr} shows all fixtures or devices available in the library sorted by manufacturer. Press {Manfctr} from the CIA to display the fixture library.
  • Page 126: Patching Multicell Fixtures

    more detailed programming and operating will be. See Using the Scroller/Wheel Picker and Editor (on the facing page). Patching MultiCell Fixtures Fixtures that have multiple same-type parameters can have a multicell profile assigned to them. The process for patching multicell fixtures is similar to patching moving lights. There are a few dif- ferences that are important to understand though.
  • Page 127: Labeling

    Note: If the master channel has only a virtual intensity over the cells, an address will not be displayed, as that is a virtual parameter. Labeling To label a channel or address, press the [Label] key with the channel or address selected on the com- mand line.
  • Page 128 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 ref- erence.
  • Page 129 You can label the new wheel by pressing [Label] and typing the desired label on the virtual keyboard and pressing {Enter}. To select a color or pattern for the specific frame in the scroll/wheel, select the “NEW” text and press {Edit} or click the gray box in the C/G column of the frame.
  • Page 130 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 n} before the standard manufacturer offerings. The frame list will include an exact duplicate of the copied selection.
  • Page 131 Scroller Fan Curves Curves can be applied to the scroller fan parameter allowing for the output of the fan to be con- trolled by the intensity of the channel. The curves available for this are the same used for intensity parameters and cues.
  • Page 132 Note: 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: 1. In the Live display, select the scroller channel. 2.
  • Page 133 The displayed calibration information is the DMX level that puts the frame into its center position. Information in the calibration column can be manually edited by clicking on it and typing in a new DMX level. Note: Calibration data will only be applied to scroller wheels that are assigned to a channel. Data will not be displayed when viewing a wheel with an empty command line.
  • Page 134: Settings In Patch

    The shutter frame assembly parameter allows for the shutter assembly to be turned. When {Invert Rack} is disabled, a encoder will move the frame assembly from the right. When enabled, the frame assembly will move from the left. Settings in Patch Softkeys available for use while in patch include {Patch}, {Attributes}, and {Database}.
  • Page 135 [1] [At] [5] [Label] <S4 house right> [Enter] - patches channel 1 to output 5 and labels channel it “S4 house right”. {Address} - A required entry field for any device. You may use the either the [At] or [Address/Patch] key instead of the {Address} button. Use the keypad to define the starting address for the device (from 1 to 32,767,488) or a port and offset value.You may enter a start address without defining an end address.
  • Page 136 {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%.
  • Page 137 {Color Wheels} - An attribute used to change the color wheel loaded in a moving light. Select the {Color Wheels} button on the CIA to display the wheel picker with the options available for your device. See Using the Picker (on page 125) “More”...
  • Page 138: Using Device List

    {Gel} - The Gel field automatically populates with the gel selected from the Gel Picker (on page 184). Adding Keywords in Patch If you plan on being able to query channels based on a keyword association, the keyword must be defined in patch. To enter a keyword for a channel: 1.
  • Page 139 Note: Consoles only support RDM devices that are connected through a Gadget, Local I/O, or external ACN gateway. Supported gateways are the ETC Net3 4 or 2 port Gateways. Gateways need to be running version 5.1 or newer. Dimmer List for CEM+, CEM3, and FDX 2000/3000 Note: For Dimmer Feedback, these software versions are required: CEM+ v3.0 and newer,...
  • Page 140 Label System Rack Module Type Firing Mode Control Mode Curve Recorded Loads Note: The System ID number from CEM3 is not currently supported. Note: Rack numbers and dimmer numbers need to be unique for Eos to properly recognize them. For CEM+, dimmers also need to be patched to different sACN addresses. With a dimmer or dimmers selected, you can edit various dimmer settings in the property view, which will display in the CIA.
  • Page 141 Interface Protocols (on page 480) If using Network RDM, this must be done via an ETC Net3 Gateway and RDM must also be enabled on the DMX ports of the Gateway. The Gateway needs to be running version 5.1 or newer.
  • Page 142 Extracting RDM Fixture -currently getting the data required to create a fixture definition for the device. Extracting RDM Sensors - currently getting the sensor definitions from the device. Offline - no model specific RDM data has been extracted from the device and it is now offline. With a device or devices selected, you can edit various device settings in the property view, which will display in the CIA.
  • Page 143 Patching Discovered Dimmers and RDM Devices When dimmers/devices are discovered, they are not automatically attached to any patched channels in Eos. If you want the benefits of dimmer or RDM feedback, you must attach a dimmer or device to a channel. If you patch a dimmer/device's address to a channel, while in the device list display, the dim- mer/device will be automatically attached to that channel.
  • Page 144: Clearing The Patch

    The notifications you can see are: A red “!” means that the dimmer/ device has errors, such as overtemp, breaker trip, and lamp out. Yellow “?” means that the dimmer/ device has a warning message. Warning messages can include: Multiple devices’ addresses overlap Multiple devices or different devices at this address Patched fixture type mismatch Patched fixture address mismatch...
  • Page 145: Update Library

    When a new library is installed on Eos either from a software update or a separate fixture library file from the ETC website, changes in library data will not automatically update your show files. This is to prevent library changes from affecting a functional show file.
  • Page 146 Creating a New Fixture New fixtures are created from the fixture editor in the CIA . You can either create a new fixture, or copy an existing fixture to edit. See Copying a Fixture (on page 148) To create a new fixture, press {New}. A new fixture will be added to the fixture list. Naming a New Fixture Once the new fixture appears in the list, it is recommended that you name the fixture you are about to create.
  • Page 147 Note: When {New} is pressed, 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. 5. Use the [Page] keys, mouse, or touchscreen to navigate to any parameter slots that you wish to alter the default parameter designations for.
  • Page 148 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. 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.
  • Page 149 4. Press {New} to add ranges. Repeat this step until you have as many slots as are required by the number determined in step 3. 5. Use the [Page] keys to select the range and field you wish to edit. Fields are: DMX Min - enter the minimum value (0 through 255) for the range slot you are defin- ing.
  • Page 150 Color Mix Generator Page Texture Control Generic Control Position Blink Timeline Image Movement Copy Mod Projector Input Timeline Position Speed Internal Media Relay Tracking Object Frame Dimmer Curve Library Select Transition Speed Edge Blend Profile Macro Shape Transition Time Effect File Mode Shape Library Transition Type...
  • Page 151 Merging Custom Fixtures into a New Show File Custom fixtures are saved with your show file and not in the fixture library. If you want to use cus- tom fixtures in a different show file, you will need to use the advanced merge function while in the new show file.
  • Page 152 Eos Family Operations Manual...
  • Page 153: Setup

    C h a p t e r 5 Setup This chapter contains the following topics: About Setup System User Device Setup...
  • Page 154: About Setup

    About Setup This section describes the processes involved in changing your system, user, and device settings to meet your preferences. Several of the options found in Setup can also be configured from the ECU. Their settings are shared between both areas. For more information, see Overview (on page 468) for more information.
  • Page 155 channels can exist in the patch, but they can be distributed throughout the entire 99,999 channel count. Enter the number of channels for your system using the keypad. This entry must be con- firmed with the [Enter] key. Note: Every part in a multipart channel will count as an additional channel for the channel count total.
  • Page 156 To change the setting for any of these fields, press 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 press of the button will switch the field to its other state.
  • Page 157 {Resync Frames} This button allows you to configure how many frames need to be synced before time code starts run- ning. Frames can be from 1-30. Default is 2 frames. MIDI {MSC Receive} This button toggles the setting for receiving MIDI Show Control from an external source between “Enabled”...
  • Page 158 {MSC Tx Device ID} Also known as “Device ID” this setting allows you to set the device ID with which your console will transmit MIDI Show Control information. A device ID can be from 0-127. If set to 127, the console will transmit MSC data to all devices (All Call).
  • Page 159 This setting specifies the UDP port that the console will listen to for OSC receiving strings. Note: ETC recommends using 8000 and 8001 respectively for port numbers. Remember that when setting port numbers on your external device that they should be set to the opposite of what Eos is set.
  • Page 160 Note: Be careful when using a network with a DHCP server. If your external device reboots or is issued a new IP address from a DHCP server, it will no longer receive OSC strings from Eos until you change this setting to match your new IP address at your external device. String UDP {String RX} This setting will enable receiving strings on all Serial RX formats and OSC inputs.
  • Page 161: User

    {String TX IP Address} Sets the destination IP address or ACN devices supporting the ACN String EPI that the console will use to send strings. This can contain either an IP address for UDP string destinations or ACN device names.. A combination of UDP and ACN devices are not supported. Please see String Interface (on page 523) for more specific configuration information.
  • Page 162 To change the setting for any of these fields, press the buttonin the CIA to activate it. If the field requires data, enter it from the keypad. If the field is a toggle state, one press of the button will switch the field to its other state.
  • Page 163 Manual Control This user setting button gives you access to 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.
  • Page 164: Device

    {Preserve Blind Cue} -This enables the desk to display the last selected cue in blind when you return to blind. The default is disabled. {Popup Magic Sheet} - assigns a magic sheet as a popup magic sheet. {Popup Nav Lock} - enables or disables the zoom and scroll navigation for popup magic sheets.
  • Page 165 Outputs This System button gives you access to Outputs settings. These settings are also found in the ECU. Note: Changes to these settings may require a restart. When required, a warning message indicating a needed restart will display. Local DMX The following settings are available: Enable - enables DMX output from the local DMX ports.
  • Page 166 {Sounds} - allows you to enable or disable sounds. When disabled, the volume level controls will not display. {Spacebar [Go]} - allows you to enable the spacebar on an external keyboard as the hotkey for [Go]. By default, it is “Disabled”. {Hide Mouse} - With hide mouse enabled, if the mouse is left idle for 10 seconds, the cursor will go away.
  • Page 167 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. Click and drag the wings to match your physical layout.
  • Page 168 In-Cell Editing When disabled, this setting prevents changes to be made to the cells in the Live/Blind and Playback Status Displays. {In-Cell Editing} is enabled by default. Note: Options in the CIA are not affected by this setting. DirSel.Dbl Clk When enabled, double clicking a direct select button will act as [Recall From] [Record Target] to place the entire contents of that preset, palette, or step-based effect on stage.
  • Page 169 {Live Master} control. Backlit The brightness of the backlit keys on Eos Ti, Gio, Gio @ 5, and Ion Xe are user-definable. The level range is from 0 through 100%, with 50% being the default level. On Element 2, this controls the backlight for the fader position switch.
  • Page 170 Subwing Display For attached wings, you can adjust the brightness and contrast of the wing's LCD displays. The level range is from 0 through 100%, with 55% being the default level. Direct Selects Brightness You can adjust the brightness of the color coding and color swatch used for the Direct Selects. Use the slider for Color Brightness to adjust the color coding of the direct select and the color palette dir- ect select color swatch's brightness.
  • Page 171: Basic Manual Control

    C h a p t e r 6 Basic Manual Control This chapter contains the following topics: About Basic Manual Control Using Channel Faders On Element 2 Selecting Channels Setting Intensity Manual Control of Non-intensity Parameters (NPs) Home Multiple Intensity Channels Multicell Fixtures Lamp Controls Using [+%] and [-%]...
  • Page 172: About Basic Manual Control

    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.
  • Page 173 Note: Selecting channels from the summary or table displays will start a new command line. Select Channels From the Keypad The keypad defaults to selecting channels. Channels may be selected on the control keypad using the [+] and/or [-] and [Thru] keys for consecutive or non-consecutive channel selection. The following examples illustrate various methods of selecting channels from the control keypad: [5] [Enter] - selects channel 5.
  • Page 174 For Example: 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.
  • Page 175 [1] [Thru] [2] [4] {Offset} [4] [/] [4] [Enter] - selects channels 4, 8, 12, 16, 20, and 24. You can select to offset by 2/2, 4/4, 3/3 etc. [1] [Thru] [1][2]{Chan Per Group} [3] {Jump} [1] [Enter] would create these 3...
  • Page 176: Setting Intensity

    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.
  • Page 177: Manual Control Of Non-Intensity Parameters (Nps)

    [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.
  • Page 178 Beam has three subcategories which correspond to the way the encoders are mapped. They are {Form}, {Image}, and {Shutter}. 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.
  • Page 179 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.
  • Page 180 For Eos and Eos Ti, they are displayed in blue at the top of the LCD display. For Gio, Gio @ 5, and Ion Xe, they are displayed at the bottom of the parameter category softkeys. You can go directly to the page required by pressing the encoder page button and a page number.
  • Page 181 When you have created a new scroll or wheel in patch for any channel and that channel is selected, that information will be displayed in the associated encoder display. See Using the Editor (on page 126) When you access a parameter page, the encoders will automatically load and display the first page that has a valid parameter for the selected channels.
  • Page 182 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 auto- matically populate with the “Form”...
  • Page 183 The shutter controls window allows you to move individual shutters by holding down one of the let- ters inside of the shutter graphic. To rotate the shutters, use the <A>, <B>, <C>, or <D> buttons around the outside of the shutter graphic. Encoder Buttons Note: The encoder buttons are used with the encoders for shutter control.
  • Page 184 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 dis- play if the frame is less than 2.5 and F2- if the frame is greater than 1.5. After the frame num- ber, the gel number will also be displayed.
  • Page 185 Color Spaces There are six color spaces that you can choose to work in. All of these spaces are connected. So it doesn't matter which space you wish to work in, the console will translate the information to work with your fixtures. When the color picker is first opened, the CIE xy color space and the gel picker will open by default.
  • Page 186 Note: When a fixture is in HS mode, the brightness control is not provided. Intensity con- trols the brightness. For the CIE xy (CIE 1931) and CIE uv (CIE 1976), the triangle represents the RGB space as defined by the PLASA standard E1.54. Fixtures that comply to that standard can achieve any color within the tri- angle.
  • Page 187 {Brightest} - determines the color match used. This is helpful when working with fixtures that have more than three color components, such as RGBA, RGBWm or ETC's fixtures. Pressing {Brightest} or {Shift} +a gel from the picker will cycle through the three modes.
  • Page 188 How the Gel Picker Affects Scroller and Color Wheel When possible the Gel Picker will select the closest gel as defined in a scroller or color wheel. Note: Some devices contain manufacturer specified gel mixes, and will only allow selection from the Gel Picker of the exact gels in their list.
  • Page 189 Color Path Note: Color path is only applicable for additive mixing systems. Color Path is a option for controlling color fades between cues. By default, color fades happen in the native space of the fixture. If you want a fade that resembles a fade in a different color space, you can do that using color paths.
  • Page 190 - plays / resumes the color fade. - skips to the end of the color fade. You can also click on the color path preview bar to scrub to any point along the fade. Additional controls may be available based on the color path selected. For example, Color Path 7 has additional controls for Hue, Saturation, and Brightness.
  • Page 191: Home

    The following screenshots show a 7 color fixture. This display will change based on the type of fix- ture being used. Note: The grey line shows the composite color of the fixture. If multiple fixtures are selec- ted, the grey line represents the first channel selected. With the Gel Picker (on page 184) open and a gel selected, a dotted line will appear in the Spectrum...
  • Page 192: Multiple Intensity Channels

    [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 chan- nels in group 1.
  • Page 193 information. Multicell fixtures have a master channel with a whole number for a channel number and the appro- priate number of additional cells, which will have point numbers for their channel numbers. To control the whole fixture, select the master channel. To control individual cells, use [.] to put cell only on the command line.
  • Page 194: Lamp Controls

    You can also have a cell selected and still apply data to the master channel as long as the cell does not also have that parameter. When you have selected a cell, if you apply data that does not apply to the master, Eos understands to apply it to the cells instead.
  • Page 195: Using [+%] And [-%]

    Pressing any of these parameter controls buttons will affect the selected channel after a con- firmation. Exit the lamp controls display by pressing [Displays]. Using [+%] and [-%] Use [+%] and [-%] keys to incrementally change parameter values. By default, the [+%] and [-%] keys are assigned a value of 10. This can be changed in Setup. See Manual Control (on page 161) for more information.
  • Page 196: Remainder Dim

    Remainder Dim Note: By default, [Rem Dim] will set to zero. In Setup, you can assign a remainder dim value of something other than zero. See Manual Control (on page 161). For the purposes of this discussion, the default value of zero will be used in examples. [Rem Dim] temporarily provides a zero intensity to all channels except those that are currently selec- ted, those that are parked, or those with intensity contributions from submasters.
  • Page 197 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]...
  • Page 198: Highlight And Lowlight

    To place Eos in highlight mode, press [High_Low] [Enter]. To place Eos Ti, Gio, Gio @ 5, Ion Xe, and Element 2 in highlight mode, press [High] [Enter]. The command line will show that highlight is cur- rently in use.
  • Page 199: Sneak

    Lowlight Preset The {Lowlight Preset}, which is set in Setup> User> Manual Control >Lowlight Preset, is used to define the behavior of specified but not selected channels while using [Next]/[Last] in highlight mode. When in highlight mode, [channel list] or [Group] [n] [Enter] [Next] will select the channel list or group and isolate the first channel.
  • Page 200: Select Keys

    The playback status display will show a red counter for sneak time. If multiple sneak times are being used, the most recently fired sneak time will be displayed. For an example of the sneak counter, see Indicators in the Playback Status Display (on page 72).
  • Page 201 The [Select Last] key allows you to reselect whatever the previous channel selection was. This includes multiple channel selections, groups, etc. Using [Select Last] , Eos will recall your last com- mand line and leave it unterminated for further operation. This will work for a loop of the last five commands.
  • Page 202: Channel Check

    For example, cue 1 is active, and has channels 1 through 5 at full. Using the syntax, [Select Active] [Enter] [At] will post channels 1 through 5 onto the command line. Another example, Channels 10 through 20 have a manual level of 75. Using [Select Manual] [Enter] [Select Last] will put channels 10 through 20 onto the command line.
  • Page 203: Address Check

    Note: 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. Address check differs from Address at Level (on the previous page) because it skips non-intensity parameters of patched addresses.
  • Page 204 Eos Family Operations Manual...
  • Page 205: Using Groups

    C h a p t e r 7 Using Groups This chapter contains the following topics: About Groups Recording Groups Live Selecting Groups Opening the Group List Using Groups as a Channel Collector Using Groups...
  • Page 206: About Groups

    About 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. 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, hundredths, or thousandths (such as Group 2.5, Group 7.65, Group 3.131).
  • Page 207 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.
  • Page 208 [Group] [2] [Enter] [Shift] & [/] [1] [Thru] [4] [Shift] & [/] [Enter] Offset You can use the {Offset} softkey to aid in channel selection prior to storing groups, submasters, pre- sets, palettes, effects, and using park. When {Offset} is pressed, a channel distribution display will open.
  • Page 209 {InterLeave} creates a number of distributed sets of channels, that are not clustered together. [1] [Thru] [1][2]{Chan Per Group} [4] {InterLeave} [Enter] would create these 4 sub- groups: (1,4,7,10) (2,5,8,11) (3,6,9,12). [1] [Thru] [5] [+] [1][1] [Thru] [1][5] [+] [2][1] [Thru] [2][5] {Chan Per Group} [3] {Inter- Leave} [Enter] would create these 5 subgroups: (1,11,21) (2,12,22) (3,13,23) (4,14,24) (5,15,25).
  • Page 210: Selecting Groups

    To create a group with only the master cells: [Group] [3] [4][Enter] [5] [0] [0] [Thru] [5] [0] [3] [Shift] & [.] [Enter] To create subgroups with only specific cells: [Group] [3] [5] [Enter] [5] [0] [0] [.] [1] [Shift] & [/] [5] [0] [1] [.] [1] [Enter] You can also use the {Offset} softkeys to aid in create of groups and subgroups.
  • Page 211: Using Groups As A Channel Collector

    Press [Group] [Group] Press [Tab] [1] [7] 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 (on page 204)).
  • Page 212 [Group] [Int Palette] [5] - selects all the channels in intensity palette 5. Eos Family Operations Manual...
  • Page 213: Using Fan

    C h a p t e r 8 Using Fan This chapter contains the following topics: About Fan Fanning Parameter Data Fan From the Command Line Fanning References Fanning Timing and Delays Using Subgroups with Fan Using Fan...
  • Page 214: About Fan

    About Fan Fan provides the ability to spread parameter and timing values in a range across a channel selection set and have those values be evenly spaced. Fan is applied by channel selection or group order. By default, fan operation is from the start channel. When [Fan] is pressed after a channel selection, the softkeys will repaint to the following fan styles: {Center} - The middle channel in the order is set as the start and will remain unchanged, and the first and last channels will change in different directions.
  • Page 215: Fanning References

    [1] [Thru] [5] [At] [1] <0> [Thru] [3] <0> [Fan] {Mirror} [Enter] - sets channel 1 to 30%, 2 to 20%, 3 to 10%, 4 to 20%, and 5 to 30%. Fanning References When fanning references, such as palettes, if there are more that 2 reference lists are used then the data will be referenced data.
  • Page 216 Eos Family Operations Manual...
  • Page 217: Using Mark

    C h a p t e r 9 Using Mark This chapter contains the following topics: About Mark AutoMark Referenced Marks Using Mark...
  • Page 218: About Mark

    About 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. Eos provides two different methods to mark lights: AutoMark (below) Referenced Marks (on the facing page)
  • Page 219: Referenced Marks

    When enabled, the cue that executes the mark will have an “M” in the flags field. If AutoMark is dis- abled, allowing a live move, a “D” is displayed in the flags field of the cue or cue part where the data is stored.
  • Page 220 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.
  • Page 221 Priority marked cues display indiciators in the PSD. See Mark Symbols (on the next page) for more information. 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.
  • Page 222 Note: {Emergency Mark} can be used to automatically set a mark flag if you had not pre- viously done so. If using {Earliest M} and no cue with a mark flag has already been set, {Emer- gency Mark} will set a mark flag. See Record Defaults (on page 159) for more information.
  • Page 223 [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] <Cue> [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).
  • Page 224 [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. It is also possible to mark to a cue that doesn't exist, and when the mark is stored, Eos will auto- matically create the cue to mark to.
  • Page 225: Storing And Using Palettes

    C h a p t e r 1 0 Storing and Using Palettes This chapter contains the following topics: About Palettes Palette Types Palette Options Storing Palettes Live Recalling Palettes Editing Palettes Live Editing Palettes in Blind Using By Type Palettes Removing Channels from a Palette Deleting Palettes Storing and Using Palettes...
  • Page 226: About Palettes

    About Palettes Palettes are building blocks that can be used to create presets (About Presets (on page 238)), cues (About Single Cue List (on page 252)), and effects (About Effects (on page 332)). 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.
  • Page 227: Palette Options

    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.
  • Page 228 When [Record] is used, Eos 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.
  • Page 229 The following examples illustrate various methods of selectively storing palettes using [Record]: [1] [Thru] [3] [Record] [Intensity Palette] [2] [Label] <name> [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.
  • Page 230: Recalling Palettes

    Storing Palettes to Direct Selects You can store palettes efficiently using the direct selects. Rather than using the [...Palette] hard key and the numeric keypad to specify a palette number, you can simply touch the desired direct select for that palette from the touchscreen. For Example: If you want to store color data to color palette 4, press: [Record]...
  • Page 231 Note: If enabled in Setup, you can double click on a palette direct select button to quickly recall from the selected palette and put its content on stage. See Displays (on page 165) additional information. Recalled palettes will appear as manual data for the specified channels. That data will appear as abbre- viations of the palette type (IP3 = Intensity Palette 3, FP8 = Focus Palette 8, and so on), or as the palette label if defined/enabled in the displays settings in Setup (see Show Reference Labels (on...
  • Page 232: Editing Palettes Live

    Palettes On Faders Palettes can be mapped to faders. See Presets and Palettes Fader Properties (on page 246) for more information. Presets and palettes can be used to create a temporary list of content that can be played back on a fader.
  • Page 233 [Palette] [Palette] {Edit} - opens the list view of the palette type and then opens Blind palette. You can also use the tab number to open the list view. See Editing Palettes in List View (on the next page) for a list of tab numbers. CAUTION: When editing palettes in Blind, changes to palettes are automatic, therefore no update or record command is required.
  • Page 234 When editing in Blind, it is possible to remove an instruction from any palette by selecting the chan- nel and parameter and pressing [At] [Enter] or {Make Null} [Enter]. [Recall From], [Copy To], Move To (accessed by pressing [Copy To] [Copy To]), and {Replace With} may be used to create and edit palette data.
  • Page 235 Indicators for absolute (A), locked (L), and by type (T+) display to the right of the palette number. Note: In the by type channels column, any channel number with an asterisk indicates that the channel does not have any by type data stored to it. 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.
  • Page 236: Using By Type Palettes

    palettes, or select a new palette for editing from the keypad. Using By Type Palettes Storing a By Type Palette If {By Type} is used when recording, the lowest number channel of each fixture type will be the default channel. Generally, when storing by type palettes, you will want only one channel of each fix- ture type in use.
  • Page 237: Removing Channels From A Palette

    tracking channel will then become the new default channel. Any other updated channels will be made discrete. Removing Channels from a Palette You can remove specific channels from a palette. This can be done from blind. For Example: Open the palette in blind: [Blind] [Color Palette] [Enter] Select the palette you wish to edit: [Color Palette] [5] [Enter]...
  • Page 238 Eos Family Operations Manual...
  • Page 239: Storing And Using Presets

    C h a p t e r 1 1 Storing and Using Presets This chapter contains the following topics: About Presets Preset Options Storing Presets Live Recalling Presets Effects In Presets Editing Presets Live Using the Preset List Editing Presets in Blind Using By Type Presets Removing Channels From a Preset Deleting Presets...
  • Page 240: About Presets

    About Presets Presets are very similar to palettes in that they are collections of data for specific channels to facil- itate cue creation. Presets, however, can collect all data for a given channel (intensity, focus, color, beam) rather than just one parameter category. Eos supports up to 1,000 presets, which can be recorded as decimal (up to three places, 0.001) or whole number (up to 9,999.999).
  • Page 241 low, delay, or cue overrides). When recorded or re-recorded, presets are automatically recalled on stage. Presets may be individually labeled. Storing Presets Using [Record] The [Record] key will store all parameter data for channels that are not at their home values, as mod- ified by the filter settings in the CIA.
  • Page 242: Recalling Presets

    [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. Recalling Presets Channels must be selected when recalling a preset.
  • Page 243: Effects In Presets

    Effects In Presets Effects can be stored in a preset, and those presets can be used to create submasters and cues. However, the effect's data is only copied to the submaster or cue, it is no longer referenced through the preset. Note: If used with submasters and cues, the data is not referenced.
  • Page 244: Using The Preset List

    [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]. Using the Preset List The preset list displays all recorded presets. The Preset List only allows you to change attributes; no editing can be done directly in list view.
  • Page 245: Editing Presets In Blind

    <Preset> [1] [Thru] [5] {Move To} [6] [Enter] [Enter] - moves presets 1 through 5 to presets 6 through 10. 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.
  • Page 246: Using By Type Presets

    [select channels or parameters] {Make Null} - removes the data for the specified channel or parameter from the preset. [select channels or parameters] [At] [Enter] - 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.
  • Page 247: Removing Channels From A Preset

    Editing By Type Presets in Blind In Blind, the default channel’s levels will display in blue, discrete data for the other channels will dis- play in white, and any channels that are using the default channel value will display in magenta. Softkeys available for editing presets in blind are {By Type}, {Discrete}, and {Cleanup}.
  • Page 248: Deleting Presets

    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/ 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:...
  • Page 249 Mode You may define your fader as additive (contributes to the live output), inhibitive (limits live output) or an effect fader (presets only). Master A fader can be assigned as a Master. When it is a master, its behavior as a Proportional Master or Intensity Master (I-Master) is drawn from this setting.
  • Page 250 Background Priority Background can have a priority assigned to it. In previous software releases, when content was released, it always returned to the last fader that owned it. Background priority releases to the highest priority content that previously had ownership, provided that content has not be turned off or released.
  • Page 251 Exclude From Record - output is not recorded into any other record target. Exclude From Grandmaster - content cannot be mastered by a grandmaster. Exclude From Inhibitive Sub - content cannot be mastered by an inhibitive submaster Exclude From Solo - content will ignore solo. See Fader and Button Configuration (on page 285) for more information on solo.
  • Page 252 Solo - suppresses any intensity values not provided by the associated content while the solo button is held down. When the button is released, intensity values are restored. Priority and HTP are ignored. Shielded, park and pixel mapping outputs are not affected by the solo but- ton.
  • Page 253: Working With A Single Cue List

    C h a p t e r 1 2 Working with a Single Cue List This chapter contains the following topics: About Single Cue List Basic Cueing Recording Cues in Live Using [Cue Only /Track] Selective Storing Cues in Live Timing Assigning Cue Attributes Flags...
  • Page 254: About Single Cue List

    About Single Cue List A cue is a record target comprised of channels with associated parameter data, discrete (chan- nel/parameter level) timing, cue timing, and cue attributes (such as preheat, follow or hang instruc- tions). 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.
  • Page 255 Channels that have all home values, meaning they have never been changed, are not included in the record action, unless you specifically select the channel and press {Make Manual}. See Using {Make Manual} (on page 303) for more information. Possible exclusions are parameters categories or individual channel parameters withheld by use of fil- ters (see About Filters (on page 288) ).
  • Page 256: Using [Cue Only / Track]

    Using Record Only in Live [Record Only] is similar to [Record] except that it selectively stores only manually set values, pre- venting 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.
  • Page 257: Selective Storing Cues In Live

    With system set to Track [Record] <Cue> [5] [Q Only] [Enter] - records cue 5. New values or changes will not track into the subsequent cue. [-] [Color] [Record] <Cue> [5] [Q Only] [Enter] - as above the recorded data will not track for- ward and all color data is excluded from the record operation.
  • Page 258: Timing

    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] <Cue>...
  • Page 259 For Example: You want the time for cue 1 to be 10 minutes and 15 seconds. [Cue] [1] [Time] [1][0][1][5] [Enter] The command line will show the time as: If you want the time for cue 1 to be in seconds and tenths of a second, like 1.3 seconds, you will type using a decimal.
  • Page 260 [Record] <Cue> [4] {Color} [Time] {Manual} [Enter] - applies a manual time to any color data changes in cue 4. Non-intensity Parameter Category Timing Timing can be also applied for Focus, Color and Beam parameter categories at a cue level. By default, FCB timing is the same as intensity upfade time.
  • Page 261: Assigning Cue Attributes

    Note: Any conditions placed on channel /parameter in live (such as discrete timing, asserts, blocks, etc) must be stored or updated to the cue. Discrete Time as a Percentage Discrete times can be entered as a percentage of the cue time.
  • Page 262 When [Cue] is pressed, the {Attributes} softkey will display. Press {Attributes} to access the following softkeys: {Rate} {Note} {Scene} {Curve} {Preheat} {AF/MF} (Allfade/ Move Fade) {Scene End} Note: Preheat and Allfade are flags. Please see Preheat (on page 267) AllFade (on page 266) for more information.
  • Page 263 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 fol- low 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.
  • Page 264 [Record] <Cue> [2] [Delay] [5] [Enter] - stores cue 2 with a 5 second delay on intensity. [Record] <Cue> [2] [Time] [9] [Delay] [3] [Enter] - records cue 2 with a 9 second fade for all parameter categories, delayed from Go by 3 seconds. [Record] <Cue>...
  • Page 265 [Record] <Cue> [8] [Label] [Block] [Enter] - records cue 7 and applies the name of the hardkey as the label Pressing [Label], when a label has already been applied to a cue, will display the label on the com- mand 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.
  • Page 266 Creating a Scene Break You can add a scene break by using the {Scene} softkey. For example, [Cue] <1 > {Attribute} {Scene} will add a scene to cue 1. The virtual alphanumeric keyboard will open. You will need to label the scene before it is created. Copy To and Move To for Labels, Scenes, and Notes (on page 299) for more information.
  • Page 267: Flags

    [Cue] [n] {Link/Loop} [Enter] - removes the link instruction from the specified cue “n”. [Cue] [n] [Thru] [y] {Attributes} {Rate} [Enter] - removes the rate instruction in cues “n” through “y”. You may combine these to remove multiple attributes at once: [Cue] [n] [Shift] &...
  • Page 268 Auto-block Eos 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.
  • Page 269: Using External Links

    Note: Only AutoMark is available on Element 2. Preheat Preheat can be used to warm filaments in the cue immediately preceding an intensity upfade from 0. Preheat values can be assigned to channels individually in patch (see {Attribute} Display and Settings page 133)).
  • Page 270: Modifying Cues Live

    there is not a cue 1 in that list, no action is taken. 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.
  • Page 271 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”...
  • Page 272: [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”. [Update] Update is a powerful feature, and also very versatile. Using a combination of [Q Only], [Track], [Trace], and {Make Absolute}, the number of ways you can update specific information and manual data is virtually endless.
  • Page 273 Channels that have been manually added to the stage output, but are not overrides of an active cue will update to the selected cue list. Once you have made a selection from the available options, press [Enter] and the target will be updated.
  • Page 274 Cue 5 is active and onstage. Channels 5 through 20 are currently referencing preset 1. You make changes to channels 5 through 9. The data for these changes is now manual. Press: [Record Only] [Enter] [Enter] If there were other changes on stage, you could have used: [5] [Thru] [9] [Record Only] [Enter] [Enter] Only the manual data will be recorded as an update to cue 5.
  • Page 275 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. For a more detailed summary of Trace, please see Using Trace (on page 15) Following are some examples: [Update] <Cue>...
  • Page 276: Recording And Editing Cues From Blind

    If you are currently in cue 5 and you want to update through cue 10, you would use the fol- lowing syntax: [Update] [Thru] <Cue> [10] <CueOnly/Track> [Enter] Update [+] [+] can be used to specify a range of cues for updating. [+] can also be used with [Record] and [Record Only].
  • Page 277 {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...
  • Page 278 Editing From the Blind Spreadsheet The blind spreadsheet is another useful blind view of cue data. While in blind, press [Format] to access the spreadsheet. See Spreadsheet (Blind Only) (on page 60) for more information. In spreadsheet view, cues are listed on the y axis and channels/ parameters are displayed on the x axis.
  • Page 279: Deleting Cues

    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 <Cue>...
  • Page 280: Using The Cue List Index

    In this instance, if you used the [Q 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 instruc- tions. Deleting 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.
  • Page 281 Using the mouse, you can move the barrier between the stored cue display (top) and the stored list display (bottom). Hover the mouse arrow over the list boundary until it changes to the move bound- ary icon. Then click and drag the boundary up or down to the desired height. Command Line Behavior for Cue List Index The command line while in the Cue List Index defaults to cue list selection.
  • Page 282 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 be affected by the playback of Cue List 1, {Solo Mode} can be used.
  • Page 283 The following options are available in this configuration menu: Display Cue Parts - displays the individual parts of a part cue. When not enabled, the number of parts for that cue will display as a superscript number beside the cue's number. Display Cue Links - displays the Link/Loop (on page 261) information.
  • Page 284 Master type (Proportional, Manual Master, or Intensity Master) Intensity HTP or LTP setting (default is LTP) Assert Priority Background Background Priority Phantom Back from 1st Go from Last Stomp Exclude Channel Filters Parameter Filters Faders can be mapped to a cue list in the fader configuration display or by using [Load], see Selected for more information.
  • Page 285 Assert Assert can be turned on or off at the fader level. This property sets the entire cue list to be asserted on playback (even track instructions are replayed). Priority Note: Priority was previously called Independent. Priority is used to protect values from being affected by submasters or playback faders that have a lower priority level.
  • Page 286 Go From Last Go From Last controls the behavior that happens when you press the [Go] button while in the last cue. The following are Go From Last options: Do Nothing (Default Setting) - keeps the last cue in the list active. Cue Out - only fades out channels in that cue list.
  • Page 287 Tap or click on {Chan Filter} to assign channels or groups. Tap or click on {Param Filter} to open a list of available parameters that you can filter. Note: Filters will travel with their assigned cue lists wherever they are mapped. When a filter has been applied, an indicator will display in the fader ribbon.
  • Page 288 Fader Options The following options are available for a playback fader: Master - fader will be a proportional master, a manual master, or an intensity master, depend- ing on the cue list property. Effect Rate - fader centers to home. It controls the rate of any running effects (same behavior as using rate via the Effect Status Display).
  • Page 289: Using Filters

    C h a p t e r 1 3 Using Filters This chapter contains the following topics: About Filters Record Filters Partial Filters Clearing Filters Storing Data with Record Filters Using Filters...
  • Page 290: About Filters

    About 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. Note: Channel and parameter filters can be applied to faders and submasters. Those type of filters affect playback and not record functions.
  • Page 291: Clearing Filters

    1. Press and hold {Filter}. The parameter buttons change to display filter selection. 2. Press 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.
  • Page 292 Eos Family Operations Manual...
  • Page 293: Working With Multiple Cue Lists

    C h a p t e r 1 4 Working with Multiple Cue Lists This chapter contains the following topics: About Working With Multiple Cue Lists Recording to a New Cue List Using [Go To Cue] with Multiple Cue Lists Working with Multiple Cue Lists...
  • Page 294: About Working With Multiple Cue Lists

    About Working With Multiple Cue Lists Eos provides many useful tools to allow you to work efficiently and simultaneously with multiple cue lists. These topics focus on the features and methods used when working with more than one cue list. Note: This feature is not available on Element 2.
  • Page 295 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] <Cue> [2] [/] [5] [Enter] - this will create cue list 2 and will record all manual data to cue 5 in that cue list.
  • Page 296 At a Cue List Level When applied at the cue list level, [Assert] ensures that all values in all cues in that list are asserted on playback. When a cue list has been asserted, the playback status display will show an "A" in the assert column for every cue in that list.
  • Page 297: Using [Go To Cue] With Multiple Cue Lists

    Like many other cue attributes, allfade is a toggle state. To remove the allfade flag, specify the cue and press {Attributes} {AF/MF} [Enter]. For more information on allfade, see AllFade (on page 266) Changing the Active Cue List The active cue list will be displayed in detail on the Playback Status Display and the Cue List Index. 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] <Cue>...
  • Page 298 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.
  • Page 299: Advanced Manual Control

    C h a p t e r 1 5 Advanced Manual Control This chapter contains the following topics: About Advanced Manual Control Using [Copy To] Using [Recall From] Using {Make Null} Using {Make Manual} Using {Make Absolute} Using [Capture] Using [Query] Using [Undo] Advanced Manual Control...
  • Page 300: About Advanced Manual Control

    About Advanced Manual Control This section describes some advanced features for manual control functions. These features can save you valuable programming time. For additional manual control functions, see About Basic Manual Control (on page 170) 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.
  • Page 301 [1][2] [Copy To] [2] [Sneak] <Time> 7 [Enter] Copies the recorded data from channel 12 to channel 2 and sneaks it in 7 seconds. Using the {HTP} softkey with [Copy To] will cause any intensity levels to be ignored if they are less than or equal to the copied value.
  • Page 302: Using [Recall From]

    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. For information on using [Copy To], see Using [Copy To] (on page 298) All parameter data for selected channels will be recalled, or by using the IFCB category buttons or...
  • Page 303: Using {Make Null

    Channel 1 will remain at 50% and channel 2 will go to full. Recall From Park You can use [Recall From] [Park] to set a channel or parameter to the same level as the current park value. For Example: Channels 1 through 5 are parked at 55. To recall that level to channels in live or blind, use the following syntax: [1] [Thru] [1][5] [Recall From] [Park] [Enter] Channels 1 through 5 will be set to 55 and channels 6 through 15 will be unaffected.
  • Page 304 Make Null 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/ parameters in palettes, presets, and submasters, thereby removing the data from the target entirely, in the same way that [At] [Enter] does.
  • Page 305: Using {Make Manual

    Using {Make Manual} The {Make Manual} softkey can be used to convert cue or submaster data into manual values, allow- ing 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.
  • Page 306: Using [Query]

    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 instruc- tions until they are released from capture.
  • Page 307 Unpatched Mark (cue where the intensity is active) Less Than (includes equal to) Greater Than (includes equal to) Broken Mark Marking (future cue) Track Up Moves Down Moves Live Moves Dark Moves Autoblock Block Assert Part Park Time Delay Capture Note: Unless otherwise specified, Eos assumes that a query will apply to current output.
  • Page 308: Using [Undo]

    In the Live/ Blind display, any channels meeting this criteria will be selected. You may use [Next] and [Last] to cycle through the query selection, one channel at a time to control only a specific channel. Other examples of using a query are: [Query] {Isn’t In} [Beam Palette] [2] [5] [Enter] [Query] {Accessory} {Can Be} [Color Palette] [8] [Enter] [Query] {Unpatched} [Delete] [Enter] [Enter]...
  • Page 309 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.
  • Page 310 Eos Family Operations Manual...
  • Page 311: Cue Playback

    C h a p t e r 1 6 Cue Playback This chapter contains the following topics: About Cue Playback Playback Controls Selected Cue Out-of-Sequence Cues Virtual Faders Assigning Faders Displaying Fader Pages With Content Changing Fader Pages Playback Fader Controls Cue Playback...
  • Page 312: About Cue Playback

    IFCB Palette/ Presets lists, or individual instances. Gio @ 5 has one master fader pair and 5 motorized faders with 100 pages. Ion Xe has one master fader pair. Ion Xe 20 has one master fader pair and 20 faders with 100 pages. Element 2 has one master fader pair and 40 faders with 100 pages.
  • Page 313: Playback Controls

    Eos Geography (on page 21) Gio Geography (on page 23) Gio@5 Geography (on page 24) Ion Xe Geography (on page 25) Element 2 Geography (on page 27) Selected Cue When in Live or Blind, if you press [Live] or [Blind] respectively, the selected cue will be the last executed cue.
  • Page 314: Out-Of-Sequence Cues

    Assume you have cue list 1 already loaded to the master playback faders. Now you want to load cue 2/1 to a fader. [Cue] [2] [/] [1] [Load] If you press the [Load] button above the master playback fader, it will load cue 2/1 into the pending file.
  • Page 315 Cue is re-executed using [Assert] & [Load] or is asserted from the command line. (Using Assert (Playback Button) (on page 319)) 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.
  • Page 316 [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 change to provide Go to Cue modifiers to enhance your playback ability.
  • Page 317: Virtual Faders

    Go to Cue Out [Go to Cue] [x] [/] [Out] [Enter] allows you to use the [Go to Cue] [Out] command on a list specific basis. [Go to Cue] [Out] continues to affect all active cue lists. Note: [Go to Cue] [x] [/] [Out] is similar to [Go to Cue] [x] [/] [0] except that any NPs on the fader will fade to their home level.
  • Page 318: Displaying Fader Pages With Content

    When the first cue is stored on Eos, the cue list of that cue automatically loads on the master fader. Any subsequent cue lists stored will load to the next available fader. Assigning Faders Manually The location of playbacks, submasters, palettes, and presets on faders can also be defined as the con- tents of those targets are stored.
  • Page 319: Changing Fader Pages

    Pages 1 through 3 and page 11 have content. If on page 2 you press [Fader Page], you will see pages 3 then 11. After page 11, you will jump back to page 1. When on page 11, as you press [Shift] & [Fader Page] you will see page 3. Changing Fader Pages You can page through the 100 available pages of faders by pressing [Fader Page], which will advance you one page for each press.
  • Page 320 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. When a cue has manual timing values stored with it, the fader will set itself to zero when [Go] is pressed, or you may set the fader to zero before you press [Go].
  • Page 321 [Go To Cue 0] Note: On Eos, the button is [GoTo Q0] . 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. Sim- ply press: [Go To Cue 0] &...
  • Page 322 Using Freeze [Freeze] can be used to halt all effect activity on any active faders. To activate a freeze for only a spe- cific fader, press [Freeze] & [Load]. Note: On Element 2, you will need to use the {Fader Control} softkey, which displays when [Live] is pressed.
  • Page 323 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.
  • Page 324 [1] {Color} [Time] {Manual} [Enter] - assigns a manual time to channel 1. This must be recorded or updated to a cue, when in Live. 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] Manual Intensity Override...
  • Page 325 Note: Associated pending and current cues will remain when using [Off] & [Load]. Note: Pressing [Go] will run the cues in their current sequence. [Release] & [Load] - behaves like [Off] & [Load] except that it sets the pending cue to the first cue in the list and removes the active cue.
  • Page 326 Eos Family Operations Manual...
  • Page 327: Multipart Cues

    C h a p t e r 1 7 Multipart Cues This chapter contains the following topics: About Multipart Cues Record a Multipart Cue in Live Storing a Multipart Cue in Blind Deleting a Part from a Multipart Cue Multipart Cues...
  • Page 328: About Multipart Cues

    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: Building a multipart cue part-by-part in Live Breaking an existing cue into multipart cues in Live...
  • Page 329 [channel/parameter selection] [Record] (or [Record Only]) [n] [Part] [a] [Enter] [channel/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.
  • Page 330: Storing A Multipart Cue In Blind

    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”...
  • Page 331: Deleting A Part From A Multipart Cue

    Note: 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].
  • Page 332 Eos Family Operations Manual...
  • Page 333: Creating And Using Effects

    C h a p t e r 1 8 Creating and Using Effects This chapter contains the following topics: About Effects The Effect List Effects Editor Effect Status Display Effect Channel Display Step Effects Absolute Effects Effect Background Value Modification Beats Per Minute Multiple Intensity HTP Effects Relative Effects...
  • Page 334: About Effects

    About Effects Effects are a method within Eos to provide dynamic, repetitive action to channels.This chapter explains the different types of effects, and how to use them. Effects are manual control functions that can be applied to a channel parameter and then included in presets, cues, or submasters.
  • Page 335: Effects Editor

    To navigate this list use the navigation keys as described in Display Control and Navigation (on page 48) 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. Effect List Navigation Using the [Next]/ [Last] keys will only move between effects in the effect list display.
  • Page 336 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. <Effect> [1] {Type} {Step based} [Enter] Scale Applies only to relative effects. This modifies the amount the pattern is offset from the current para- meter values.
  • Page 337 Parameters This allows you to select which parameters will be involved in the selected effect, by default. By enter- ing a value here, you do not need to specify the required parameter when placing an effect on a chan- nel group. To add/ remove parameters to the effect, press {Parameters} and then select the desired parameters from the buttons that appear to the left.
  • Page 338 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 applic- able).
  • Page 339: Effect Status Display

    {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 ele- ment within the effect.
  • Page 340 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 manip- ulate 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 select it directly from the CIA.
  • Page 341: Effect Channel Display

    Grey - property is drawn directly from the effect. Red - property has been manually modified but not stored. Blue - property is an override to the saved effect. Magenta - property is tracking from a previous cue. Clicking on the Attributes column will open the Effect Attribute Override display. From that display, you can access most of the same properties as those found in the Effect Editor.
  • Page 342: Step Effects

    The following properties can be overridden: Rate Size Axis (Focus Effects Only) H Form (Focus Effects Only) V Form (Focus Effects Only) Note: To add a channel level override, first you will need to be in the Effect Channel display with the effect running.
  • Page 343 Here is an example of a step effect when viewed in the CIA: If an effect step is on the command line or indicated in the blue text to the left of the command line, entering a number on the command line will default to selecting a step for the current selected effect.
  • Page 344 {Parameters} <Intensity> (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: Page arrow to the Dwell Time (In time is left at 0) column and enter a dwell time: 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:...
  • Page 345: Absolute Effects

    assigned to intensity palette 1. The range will wrap to fill any available steps. Inserting 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”...
  • Page 346 In the above image, actions 1 through 7 indicate referenced values in the “Level” column (palettes or presets), though these values can be absolute data as well. If an effect action is on the command line or indicated in the blue text to the left of the command line, entering a number on the command line will default to selecting a action for the previous selec- ted effect.
  • Page 347 {Action} [1] [Enter] The action 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 dif- ferent columns After arrowing to the “Time”...
  • Page 348: Effect Background Value Modification

    [Color Palette] [1] [Thru] [3] - assigns color palettes 1 through 3 to the actions 1 through 6. Actions 1 through 3 will be assigned to palettes 1 through 3. Action 4 will be assigned to color palette 1. The range will wrap to fill any available actions. Effect Background Value Modification For Step and Absolute effects, you can use [+], [-], and [/] to adjust the background value .
  • Page 349: Multiple Intensity Htp Effects

    While in this mode, press [Enter] to establish the BPM. The console will use an average of the last three times you press [Enter] in this mode to calculate the BPM. Pressing [Learn] again will stop this mode. In this mode, every time the BPM changes, a live running effect will be modified accordingly without stopping.
  • Page 350: Relative Effects

    rules of HTP. But, for example, if you were to have three separate effects running on three separate effects submasters and you try to record that into one cue, the cue will only run the effects that were currently at the highest level at the moment of the record. Relative Effects A relative effect is an offset from the current state of a channel parameter.
  • Page 351 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. Other pre-made color effects can be modified in the same manner. The green arrow indicates default direction of color shift, which can be modified in attributes.
  • Page 352: Preprogrammed Rainbow Effects

    Programming a New Relative Effect Below is the process used to program a new relative effect. For Example: 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, and/or property fields so that the effect meets your needs (see Effects Editor (on page 333)
  • Page 353: Stop An Effect

    Adjust the attributes as described in Effect Status Display (on page 337). Adjustments are cue over- rides and don’t impact the core effect. Changes made to effects in the effect status display impact only that instance of the effect. The changes will then need to be recorded or updated. To edit other properties of the effect in live, press {Edit} and the effects editor will open (See Effects Editor (on...
  • Page 354: Using Offset

    Using Offset You can use the {Offset} softkey to aid in channel selection of an effect. For an explanation of the off- set options, see Offset (on page 206). [Select Channels] {Offset} {Random} [Effect] [1] [Enter] Replace With {Replace With} allows you to replace an effect with another one. All overrides will be preserved. [Effect] [1] {Replace With} <Effect>...
  • Page 355 There are several submaster button and fader configuration options that affect how effects run. See Submaster Fader and Button Configuration (on page 369) for more information about those options. Configuring an Effect Submaster To configure an effect submaster, press: [Sub] [x] {Properties} [Enter] Note: The {Properties} softkey will open the submaster properties display in the CIA.
  • Page 356 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.
  • Page 357: Delaying Effects

    Button Disabled - no action is assigned to the button. Macro - allows you to assign a macro as a button action. Delaying Effects A delay can be placed on an effect in a cue or submaster by using the syntax [Effect] [n] [Delay] [n] [Enter].
  • Page 358 Eos Family Operations Manual...
  • Page 359: Using Park

    C h a p t e r 1 9 Using Park This chapter contains the following topics: About Park Park Display Parked Values in Live Parked Addresses in Live Park Values from the Park Display Using Park...
  • Page 360: About Park

    About 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 modi- fication. Park may also be used to place a scaling instruction on the intensity output of a channel. Note: A parked channel intensity is not impacted by grandmaster or blackout operations.
  • Page 361: Parked Addresses In 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.
  • Page 362: Park Values From The Park Display

    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 [Tab] [2] [0]. 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 used for unparking.
  • Page 363 Using Park...
  • Page 364 Eos Family Operations Manual...
  • Page 365: Storing And Using Submasters

    C h a p t e r 2 0 Storing and Using Submasters This chapter contains the following topics: About Submasters Paging Submasters Recording a Submaster Submaster List Submaster Properties Submaster Information Labeling a Submaster Loading Submasters Using Bump Button Timing With Submasters Execute List Freeze and StopEffect on Submasters Moving and Copying Submasters...
  • Page 366: About Submasters

    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 Faders (on page 352) Submasters can be controlled by faders or by the keypad.
  • Page 367: Submaster List

    [Record] [Both Bump Buttons] - records all current values to the fader associated with the bump buttons. Submaster will be stored with the number associated with the chosen fader. You can also record selected channel data to submasters as well. [Channel List] [Record] [Sub] [5] [Enter] - records all data for the channel list to submaster 5.
  • Page 368 If a fader has been configured for default mapping in the fader configuration display, the fader will receive its configuration from the Submaster List. Changes made to a submaster in the submaster list will be shared with any default mapping faders loaded with that submaster. If changes are made to a fader set to default mapping in the fader configuration display, those changes will also happen in the Submaster List.
  • Page 369 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. When non-intensity parameters on a intensity master submaster have been marked using the bump button, the LED on its bump button will blink to tell you that the non-intensity parameters have been marked.
  • Page 370 Background Submasters can have their background states disabled. Background states are enabled by default. When enabled, the content of the submaster will act as a background or previous state for other cues and submasters. When a submaster has its background state disabled, a “D” will be displayed in the Submaster List background column.
  • Page 371 Nothing When Stomped - no action happens to the submaster. Release When Stomped -This function behaves the same as Off When Stomped. Unmark at 0% When this option is on, marked content controlled by the submaster will automatically be released when the fader reaches 0%.
  • Page 372 Button Options The following options are available for submaster buttons: Bump - plays back the submaster at 100% of the recorded level. It will continue to do so until released, unless the submaster has a time assigned or the {Hold} property set. Group/Assert - selects all the channels associated with the submaster, if the submaster is inactive.
  • Page 373: Submaster Information

    Rate Master - homes to center. It adjusts the cue rate, just like rate and load. Fader Disabled - no action is assigned to the fader. Master Only - fader is used to set a level for content to fade to. The slider can be used to live adjust levels when the fader has been activated via the bump button.
  • Page 374: Using Bump Button Timing With Submasters

    [Sub] [5] [Load] - loads submaster 5 to the fader associated with the load button. [Int Palette] [1] [Load] - loads intensity palette 1 to the submaster associated with the chosen 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).
  • Page 375: Freeze And Stopeffect On Submasters

    Note: Macros can also be assigned as a button action. See Submaster Fader and Button Configuration (on page 369) Triggering an Action Pressing the bump button of a submaster will trigger any actions assigned to its execute list. Adding a Trigger [Sub] [1] {Execute} {Macro} [2] [Enter] - triggers macro 2 when submaster 1's bump button is pressed.
  • Page 376: Releasing Content From A 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 can copy the contents of a submaster by using the [Copy To] button. [Sub] [2] [Copy To] [Sub 9] [Enter][Enter] - copies the contents, label, and timing data from sub- master 2 and places it in submaster 9.
  • Page 377 [Delete] [Sub] [5] [Enter] [Enter] - deletes the contents of submaster 5. [Delete] [Sub] [5] {Unmap Faders} [Enter] [Enter] - deletes the contents of submaster 5 and unmaps any faders that are currently mapped to submaster 5. Storing and Using Submasters...
  • Page 378 Eos Family Operations Manual...
  • Page 379: Using About

    C h a p t e r 2 1 Using About This chapter contains the following topics: About [About] [About] {What's New} [About] System [About] Channel [About] Address [About] Cuelist [About] Cue [About] Curves [About] Effects [About] Groups [About] Submaster [About] Macro [About] IFCB Palettes [About] Presets...
  • Page 380: About [About]

    About [About] [About] provides detailed information regarding selected elements. 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 opened, it appears in the CIA and remains open until closed or until another action forces it to close.
  • Page 381: [About]

    [About] When [About] is pressed when the command line is clear, the CIA presents the following inform- ation: System address count Software version Fixture library version Copyright notifications Device name Assigned as (Primary/Backup/Client/Offline) User ID Priority (ACN and Net2) IP Address(es) Number of defined parameters Number of patched addresses Number of unpatched defined parameters...
  • Page 382: What's New

    Only one instance of the documentation can be open at a time. Note: For consoles running Windows XP or Macs running ETCnomad, the manual is not available for viewing. Please see ETC's website, etcconnect.com, to view the online manual or download a PDF version. [About] System When {About System} is pressed, the CIA displays a list of all network devices that are connected to Eos.
  • Page 383: [About] Channel

    Note: If any errors or warnings are present at the rack, the CEM+ / CEM3 will display in red. Clicking on a CEM+ / CEM3 in the {About System} list will open the About Rack display, which shows the following information about the rack: Rack Name (displays as the title) Type Ambient Temperature...
  • Page 384 Next intensity move What the channel is inhibited by (if anything) Keywords Notes A list of all parameters on the channel showing the current value and its source, the DMX value, the absolute value, delay and timing information, marking information, and any parked values.
  • Page 385: [About] Address

    GM exempt Preheat information (if any) Swap/invert pan/tilt status Keywords Notes List of all parameter values with their address, home value, snap parameter, DMX value, and parked value (if any) {Fixture Notes} displays information found in the fixture library such as: Revision Number Release Date Alternate Names...
  • Page 386 {Next/Last Unpatched} will allow you to see what addresses closest to the current address are cur- rently unpatched. {Dimmer Feedback} - appears when the current address is patched to a dimmer in an ETC Sensor rack with a CEM+ or CEM3. Sensor feedback must be enabled. See Interface Protocols (on page 480)
  • Page 387 Scale Minimum Scale Maximum Preheat Enable Preheat Timing Advanced Features (AF) Enable Eos support the following softkey commands from this display: {Ignore Errors} {Clear Errors} Note: Clearing CEM+ or CEM3 errors from Eos will be temporary unless the errors have been fixed at the CEM+ or CEM3.
  • Page 388: [About] Cuelist

    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: Color severity is determined by the device manufacturer.
  • Page 389: [About] Cue

    [About] Cue The following information will be displayed when a cue is selected: the cue number timing data for the cue (including discrete timing) flags attributes number of moves per IFCB provided by the cue current status of the cue intensity moves live NPs moves dark NPs moves.
  • Page 390: [About] Groups

    list of submasters that use the effect list of cues that use the effect Note: Any cues or submasters that have overrides, such as rate, for the effect will display an *. [About] Groups When a group is selected, the following information will be displayed: group number the group label (if any) the channels in the group...
  • Page 391: [About] Presets

    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 {Usage} displays the following information about palettes: Number of cues that move List of channels that use the palette in a cue List of channels stored in the palette that are not used in a cue List of cues in which the palette have a move instruction List of effects that use the palette...
  • Page 392 Eos Family Operations Manual...
  • Page 393: Storing And Using Curves

    C h a p t e r 2 2 Storing and Using Curves This chapter contains the following topics: About Curves Creating a Curve Editing Curves Applying a Curve To Channels In Patch Curves Applied to Cues Applying a Curve To Scroller Fans Delete a Curve Storing and Using Curves...
  • Page 394: About Curves

    About Curves A curve is a relationship between the timing of a fade and the output level of a cue, cue part or dim- mer at each point of time during that fade. By using a non-linear curve, you can create of variety of effects, accommodate variations and deficiencies in your lighting equipment, alter the transition ramp and protect equipment from stress.
  • Page 395: Editing Curves

    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”...
  • Page 396: Applying A Curve To Channels In Patch

    Clearing the Curve At any time, you can clear a curve from the curve editor display by pressing the {Clear Points} softkey. This will return the curve to its original linear shape or to its default shape if it is a pre-estab- lished curve.
  • Page 397: Applying A Curve To Scroller Fans

    [Cue] [5] {Attributes} {Curve} [At] [Enter] - removes any curve from cue 5. [Cue] [8] [Part] [3] {Attributes} {Curve} [6] [Enter] - applies curve 6 to part 3 of cue 8. Applying a Curve To Scroller Fans Curves can also be applied to a scroller fan. When applied to a scroller fan, the output of the fan will be controlled by the intensity of the channel.
  • Page 398 Eos Family Operations Manual...
  • Page 399: Storing And Using Snapshots

    C h a p t e r 2 3 Storing and Using Snapshots This chapter contains the following topics: About Snapshots Recording Snapshots Recalling Snapshots Editing Snapshots Deleting Snapshots Storing and Using Snapshots...
  • Page 400: About Snapshots

    [Record] [Snapshot] [1] On Element 2, you will need to use the {Snapshot} softkey. When recording a snapshot, you will see a preview of all of the displays as they will be recorded in the snapshot. You can choose to select/ deselect various components, monitors, frames, etc from your snapshot.
  • Page 401 On Element 2, the snapshot display is different, and you will only have the visible workshapes and all workspaces option available. From the snapshot menu, the following options are available: Visible Workspaces - includes only the visible workspaces. All Workspaces - include all workspaces, including those not visible at the time of recording. Faders - captures the current state of the faders including: fader page mapping, position of all submasters, and pending cues based on configuration.
  • Page 402: Recalling Snapshots

    Monitors and frames can also be selected or deselected in the preview area. Use the {Frames/Mon- itors} button to select whether you will see monitor or frame numbers in the preview area. When a monitor or frame has been deselected, it will be greyed out. Deselected frames will also have a small red circle with a slash on them.
  • Page 403: Editing Snapshots

    Note: In a system with multiple users, it is recommended that you allot discrete snapshot numbers for each user. Since snapshots are global and can be recorded/ recalled from most devices, assigning numbers for each user will ensure their snapshots are stored and edited properly for their device.
  • Page 404 Eos Family Operations Manual...
  • Page 405: Storing And Using Macros

    C h a p t e r 2 4 Storing and Using Macros This chapter contains the following topics: About Macros Store a Macro from Live Using the [Learn] key Macro Editor Display Create a New Macro from the Display Edit an Existing Macro Play a Macro Stop a Macro...
  • Page 406: About Macros

    About Macros Eos provides you with the ability to record macros, which allow you to compose a series of pro- gramming actions and be able to execute them later by recalling the macro. Macros are comprised of any series of button presses (both hard and softkeys), screen commands and events.
  • Page 407: Macro Editor Display

    [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 content assigned to the submasters.
  • Page 408 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] <name>...
  • Page 409: Create A New Macro From The Display

    {Foreground} When a macro in foreground mode is run manually, it runs on the device that fired it and affects its command line. If a foreground mode macro is fired via show control, it runs on the master device and will affect its command line.
  • Page 410: Play A Macro

    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.
  • Page 411: Stop A Macro

    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]...
  • Page 412 Eos Family Operations Manual...
  • Page 413: Using Magic Sheets

    C h a p t e r 2 5 Using Magic Sheets This chapter contains the following topics: About Magic Sheets Magic Sheet Browser Navigating a Magic Sheet Creating and Editing Magic Sheets Examples of Magic Sheets Using Magic Sheets...
  • Page 414: About Magic Sheets

    About Magic Sheets Magic Sheets are user created interactive displays that offer customizable views for displaying data and programming. Magic Sheets are comprised of objects that are tied to show data, such as chan- nels and palettes. The following are two examples of magic sheets. For additional examples, see Examples of Magic Sheets (on page 431).
  • Page 415 If no magic sheets exist in the show file, the magic sheet browser will be blank except for the New Magic Sheet icon. Click on the icon to open the magic sheet editor. After you have created a magic sheet, you can recall a specific magic sheet, by pressing [Displays] {Magic Sheet} [#] [Enter] or you can navigate to Displays>...
  • Page 416 Magic Sheet List The magic sheet list can be opened by double pressing {Magic Sheet}, pressing [Tab] [1] [4], nav- igating within the browser to Displays> Record Targets> Magic Sheet and pressing [Select] , or using CTRL+S on an external keyboard. The magic sheet list displays a list of all created magic sheets, their labels, and how many views have been saved for each magic sheet.
  • Page 417: Navigating A Magic Sheet

    Zoom to Selection - zooms to show all selected objects. Center on Selection - centers the display on the selected objects without changing the zoom level. Show Reference Labels - when enabled, channel objects that reference record targets (such as presets or palettes) with labels will have their labels displayed in the Magic Sheet rather than their target type and number.
  • Page 418: Creating And Editing Magic Sheets

    Multi-Touch Gestures The following multi-touch gestures can be used with an external multi-touch touchscreen or the on- board monitors on Eos Ti, Gio, and Gio @ 5. Multi-touch is not available on the on-board monitors of Eos. Scroll - touch with two fingers to move around the page. Zoom Out - touch with two fingers and then move your fingers toward each other.
  • Page 419 The main area of the magic sheet will display a grid to aid with layout. The editing tools will be dis- played on the right side of the magic sheet. The editing tool window is divided up into three areas: lay- out tools, the MS Object Library, which is made up of four tabs that contain the MS Objects, and the MS Object Properties.
  • Page 420 Edit Mode (below) Zoom (on the facing page) Alignment (on the facing page) Ordering (on page 421) Edit Mode Clicking on the arrow will open the edit mode options, which include: Grid Enabled - toggles between a grid being displayed and no grid. With the grid enabled, the magic sheet will also have a snap to grid behavior when placing objects.
  • Page 421 Zoom Clicking on the magnifying glass will open the zoom mode options, which include: Reset Zoom - sets the zoom level to 1:1 and centers the magic sheet. Zoom to All - zooms to show all objects. Zoom to Selection - zooms to show all selected objects. Center on Selection -centers the display on the selected objects without changing the zoom level.
  • Page 422 Circle - will layout a circle array of the objects. You can define the numbers of objects and the size of the circle. Align Settings - allows you to align objects either to the left, right, center, or top, middle, bot- tom.
  • Page 423 positioned), click the {Distribute Vertically} button. Distribute Rotation - allows you to distribute objects at an equal rotation between two objects. Set the level of rotation you would like by placing the first and last objects at a rota- tion. Then with all objects selected that you wish to rotate (including the first and last ones you positioned), click the {Distribute Rotation} button.
  • Page 424 Images (on page 424) Background Settings (on page 425) Magic Sheet Objects The following table contains the various magic sheet objects located in the first tab, and a brief description of what they do. Settings for objects can be adjusted in the MS Object Properties (on page 427) area.
  • Page 425 Clock adds a clock. sACN Input displays the sACN input values. Adds a Foundation Motor item Foundation to sync with an actual Found- Motor ation. draws a line. Examples of use Line could be as a pipe for fixtures or a divider between buttons. Truss places truss.
  • Page 426 Importing Fixture Symbols Additional fixture symbols can be imported. The symbol must be saved as a .svg image file, and needs to be tagged properly. These tags can be linked to the channel’s color, intensity or both. The outline section needs to be tagged as etc_symbol_outline0, etc_symbol_outline, and/or etc_sym- bol_outline2.
  • Page 427 You will need to have the images on a USB drive to import them into the desk. Once an image has been imported, it is saved with the show file. To import an image: 1. Click on the import image icon. A separate window will open displaying any found USB drives. 2.
  • Page 428 Live and Blind Backgrounds You can select live and blind backgrounds for magic sheets. These backgrounds can either use a solid color, gradient of two colors, or an image. One of these backgrounds will be used when editing a magic sheet. Select the {Use While Editing} button to use either the live or blind background. Solid When solid is selected, you will have the chance to select a color for the magic sheet background.
  • Page 429 You can select or import an image directly from this tab by pressing the choose a background image icon, if no previous image had been chosen, or by pressing the thumbnail icon of the selected image to change it. Exporting and Importing Magic Sheets Magic Sheets can be exported and imported in .xml format.
  • Page 430 Note: If any object's outline color is set to Link to Channel Intensity, the brightness of the outline color will be tied to the DMX level of the address. The higher that the DMX value is the brighter the outline color will be. Font - the font used for a text object can be changed and adjusted as needed here.
  • Page 431 Zoom - when clicked, the view will zoom in to show all object within that object’s group. Selection - when clicked, all other objects within that object’s group will be selected. Text - changes the text for a text object. Command - assigns a command to be executed.
  • Page 432 If multiple fields have the same justification, they will be stacked in field order. The orientation of fields around the object can be adjusted by pressing the field orientation icon. You can also choose to keep text upright by pressing the icon to the right of the orientation icon. There are three options for orientation: Exterior Bounds - fields will be exterior to the object and will remain at a position regard- less of the rotation of the object.
  • Page 433: Examples Of Magic Sheets

    The blue handles are used to resize objects without keeping the object's aspect ratio. The green handles are used to resize an object while preserving the aspect ratio. The white handles are used to rotate the object. Examples of Magic Sheets The following are examples of magic sheets created using the magic sheets feature.
  • Page 434 Eos Family Operations Manual...
  • Page 435 Using Magic Sheets...
  • Page 436 Eos Family Operations Manual...
  • Page 437: Virtual Media Server

    C h a p t e r 2 6 Virtual Media Server This chapter contains the following topics: About Virtual Media Server Media Content Exporting Media Content Patching the Virtual Media Server and Layers Creating a Pixel Map Working with the Virtual Media Server Effect Layers Pixel Mapping in a Multi-Console System Virtual Media Server...
  • Page 438: About Virtual Media Server

    About Virtual Media Server The virtual media server feature of Eos is comprised of two areas, the virtual media server and its vir- tual layers, and pixel maps. These areas are completely dependent on each other. The virtual media server is a feature used to create layouts of fixtures, known as pixel maps, which then applies media content (images, movies, text, and procedurally generated effects) by way of vir- tual media layers to the pixel map.
  • Page 439: Exporting Media Content

    Options in this display include: {Library (1-255)} - selects the library to import media. {File (0-255)} - selects the file number. {Reorder Libraries} - specify whether or not the library on the source device will be renumbered. If the source device’s library is not numbered, it will be assigned the specified lib- rary number.
  • Page 440: Patching The Virtual Media Server And Layers

    In the patch display, enter the channel number that will be your virtual media server. Press {Type} then {Manufctr} to display the fixture library. Select {ETC}, {Virtual}, and then {Server_Ver_1.0}. Enter the channel numbers that will be your virtual media layers. Press {Type} then {Manufctr} to dis- play the fixture library.
  • Page 441 Limitations of pixel maps include: 40 pixel maps per show file 12 layers per pixel map 16,384 pixels per pixel map grid Open up the Pixel Map display,Displays>More SK>Pixel Maps. The display can also be opened from the home screen, or by using [Tab] [9]. Note: Hovering your cursor above the pixel map will display the column and row location for the pixel.
  • Page 442 Once the pixels have been selected, you need to select their fixture type and then assign the starting address or starting channel. When either {Starting Channel} or {Starting Address} is selected, both fields will be cleared. Address-based pixels can not overlap with channel-based pixels. This includes the entire DMX fixture footprint.
  • Page 443: Working With The Virtual Media Server

    Working with the Virtual Media Server Before you begin working with the Virtual Media Server, you will want to open the Pixel Map Preview display from the home screen or by using [Tab] [1][0]. For manipulating the pixel maps, you can use either the encoders or the ML Controls, which can be opened from the home screen, by using [Tab] [5], or by using the quick access tools.
  • Page 444 {Negative On/Off} - with negative on, the output is the negative of the content. With it off, the content plays back normally. {Image Brightness} - this varies from intensity. The following images illustrates the differences between image brightness and intensity. Note: All Virtual Media Layers operate in 16-bit color mode.
  • Page 445 Mode Description Result Top layer blended with bot- {Over} (Default) tom layer Top layer with opacity {In} reduced by opacity of bot- tom layer Top layer with opacity {Out} reduced by inverse opacity of bottom layer Top layer with opacity reduced by opacity of bot- {Atop} tom layer and then blended...
  • Page 446 Mode Description Result Top and bottom layers {Subtract} color and opacity sub- tracted from each other Top and bottom layers {Multiply} color and opacity multiplied together Top and bottom layers col- {Screen} ors inverted and then mul- tiplied together Does a multiply or screen effect based on the light- {Overlay} ness or darkness of the bot-...
  • Page 447 Mode Description Result Top layer’s color merges with the bottom layer’s {Darken} color, with the darker color winning Bottom layer’s color {Dodge} brightened to reflect top layer’s color Bottom layer’s color {Burn} darkened to reflect the top layer’s color Does a multiply or screen {Hard Light} effect on the lightness or darkness of the top layer...
  • Page 448: Effect Layers

    Mode Description Result Top layer with opacity reduced by inverse opacity of bottom layer, and then {Xor} blended with the bottom layer with opacity reduced by the inverse opacity of the top layer {Library} - selects the image library. {File} - selects the media file within the selected library. {Mask On/Off} - masks takes a lower layer and a higher layer, finds only the non-transparent pixels they have in common, and then displays the common pixels of the higher layer.
  • Page 449 The effects are stored in file 1. File 1:0 is a home position of no effect. 1 through 3 are perlin noise effects, 4 is a perlin noise/ rainbow gradient, 5 through 9 are rainbow gradients, and 10 through 19 are two color gradients.
  • Page 450: Pixel Mapping In A Multi-Console System

    Effects Color Pickers The effect layers have a two color pickers for selecting the start and end colors. You can copy or swap a color between the two color pickers using the buttons located between them. Pixel Mapping in a Multi-Console System When using file based media in a multi-console environment, the primary console should be used as the ‘base’...
  • Page 451 5. Setting up the Backup and Clients 6. On the backup or client, exit to the Eos Configuration Utility (ECU). 7. Press the {Settings} button. 8. Press {Maintenance}. 9. Press {Network Drives}. 10. In the Network Drives display, click the {Add} button. 11.
  • Page 452 14. Click {Ok}. You will now be able to access the primary’s media archive from the backup or cli- ent. This new drive will appear in the browser like a USB drive. 15. Click {Done} and launch the Eos application. Synchronizing Media Archives To view media playback in the Pixel Map Preview display, you will need to first import the required media into your backup and/or client’s local media archive.
  • Page 453: Using Partitioned Control

    C h a p t e r 2 7 Using Partitioned Control This chapter contains the following topics: About Partitioned Control How to Use Partitions Setting Up Partitioned Control Partition List Creating New Partitions Deleting Partitions Using Partitions Partitions in Playback Partitions on Cue Lists Flexichannel in Partitioned Control Using Partitioned Control...
  • Page 454: About Partitioned Control

    About Partitioned Control Partitioned control allows discrete control and programming of channels between multiple pro- grammers. When multiple programmers are working on an Eos Family 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.
  • Page 455: Deleting Partitions

    This will create a new partition, highlight it in the list, and (if partition is enabled) assign it as your par- tition. 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.
  • Page 456: Partitions On Cue Lists

    Element 2 is limited to one cue list. Partitions on Cue Lists A partition may be assigned to a cue list. If a partition has already been applied to a cue list, any chan- nels not in the cue list's partition will not be included in cues when they stored or replayed. Any data for a cue list that already existed before a partition is applied, will be maintained, including data for channels not included in the partition.
  • Page 457: Multi-Console And Synchronized Backup

    C h a p t e r 2 8 Multi-console and Synchronized Backup This chapter contains the following topics: Overview Multi-console Setup Synchronized Backup Mirror Mode Multi-console and Synchronized Backup...
  • Page 458 Familiarize yourself with these terms prior to setting up a multi-console system. Note: Eos Ti, Eos, Gio, Gio @ 5, Ion Xe, Element 2, Ion, and Element consoles, RVIs, RPUs, ETCnomad Puck, or ETCnomad may all be considered active units on an Eos Family network.
  • Page 459 Software versions must match exactly between all devices. All devices have to use the same fixture library. See Update Library (on page 143). The language settings in the ECU must match. See Language (on page 470) The keyboard language setting in the ECU must match. See Keyboard (on page 470) Note: It is recommended that you perform the following setting changes before con-...
  • Page 460 Any Eos, Eos Ti, Gio, Gio @ 5, Ion Xe, and Ion console, RPU,RVI, ETCnomad, and ETCnomad Puck can be a separate user on the Eos Family network. Certain devices work well as independent users while others are intended to share a user ID with another device.
  • Page 461 Set in the Setup (see Users (on page 159)), User ID is an Eos-specific identifier that can be set uniquely for each Eos device or can be shared between multiple devices allowing for shared data between consoles. The user ID can be set anywhere from 1 to 99. The decision to share a user ID is based on the desire to share a common workspace and command line.
  • Page 462 When multiple programmers are working on the 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 mul- tiple programmers at once. For more information on partitioned control, see Using Partitions (on page 453) About Multi-console Backup Within an Eos system, you have the added bonus of show data backup.
  • Page 463 4. Select a master console from the list on the right. If no masters are available in the list, a mas- ter console is not connected to the network. 5. Press {Change Master}. The backup Eos will synchronize with the master. In the CIA of each device, you will see its current status.
  • Page 464 Note: If the primary comes back online, it will not retake control of the lighting system. The primary will wait until it is re-designated as the master and the backup is reassigned to it. You can force the backup to release control back to the primary by going to Browser- >Network>Configuration and pressing the {Release Control} button.
  • Page 465 mands. In the ECU go to Settings> Network> Enable Remote Power Off and Enable Remote Power On. The default setting for both is “Disabled”. Note: Original Eos consoles cannot be remotely powered on. The Remote Power commands are sent from the browser. The command for Power On is sent from Browser>...
  • Page 466 The mirror display can be navigated using the arrow keys or a mouse. When the required host is high- lighted, press [Enter] or double click with a mouse to confirm the selection. This display can also be opened with the keyboard shortcut of ALT + F1. Note: While in Mirror mode, the display will also have options for exiting and powering off the device.
  • Page 467 Exiting Mirror Mode Exiting mirror mode can be done by selecting {Stop Mirroring} in the mirror display or using the key- board shortcut ALT + F2. When exiting mirror mode, the device will return to its normal, working state. Note: Clients without a dongle cannot exit mirror mode.
  • Page 468 Eos Family Operations Manual...
  • Page 469: Eos Configuration Utility

    C h a p t e r 2 9 Eos Configuration Utility This chapter contains the following topics: Overview Eos Configuration Utility Reference General Settings Network Settings Maintenance and Diagnostics Buttons Local I/O Eos Configuration Utility...
  • Page 470: Overview

    Primary mode can be run on Eos Ti, Eos, Gio, Gio @ 5, Ion, Ion Xe, Element 2, Element, ETCnomad Puck, and RPUs (Remote Processor Unit).
  • Page 471: General Settings

    When the primary remains in control, the backup will behave as a client would. Backup mode can be run on Eos Ti, Eos, Gio, Gio @ 5, Ion, Ion Xe, Element 2, Element, ETCnomad Puck, and RPUs. For more information on backup systems, see Multi-console and Synchronized Backup (on page 455)
  • Page 472: Time Zone

    Share Media Archive (on page 472) Latitude (on page 472) Longitude (on page 472) Calibrate Elo Touchscreens (on page 472) Calibrate ETC Touchscreens (on page 473) Monitor Arrangement (on page 473) Software Update (on page 474) Device Name This specifies the name the desk will use to identify itself on the network to other devices. Examples might be Booth Desk and Tech Table.
  • Page 473 Press {Sym} to switch the keyboard from alphanumeric to symbols. When in symbol mode, press {Abc} to return to the alphanumeric keyboard. Use Shift As Eos Shift Allows the SHIFT key on an alphanumeric keyboard to be used as the console's [Shift] key. If not selec- ted, the Z key on an alphanumeric keyboard will function as the [Shift] key.
  • Page 474 2x - if Auto fails to automatically scale up the software on high DPI displays, select this option to force everything to be larger. Disabled - keeps the software at its native sizes and scaling, which will appear to be very small on High DPI displays Show Archive Path This is the default location to save show files.
  • Page 475 External Monitor Arrangement display. See Monitor Arrangement (below) Allows you to calibrate an ETC touchscreen. With the touchscreen connected, press the {Calibrate ETC External Touchscreen}. The first display will have you touch various parts of the display to make sure the cursor follows your finger and the second will have you touch some targets.
  • Page 476 The settings for the on-board monitors are read only. Software Update Software Update allows the installation of Eos Family Software and other ETC-approved software (GCE and NCE). Updating Eos Family Software does not affect or update the software in any other networked device such as a Net3 Gateway.
  • Page 477: Network Settings

    On new consoles, some versions are preselected to be archived when it initially ships from ETC. This includes the version of software that is currently installed from the factory as well as any patches to that version (if available). For future release, you will need to down- load the Eos Family software from the ETC website, etcconnect.com.
  • Page 478 These are the settings that determine the method to get an IP address and/or the actual IP address information that Eos uses for network communication. Note: Eos Ti, Gio, Gio @ 5, Ion Xe, Element 2, RPU3, and RVI3 have dual NICs. Eos has a single NIC. Status This reports if the port is “Online”...
  • Page 479 192.168.98.101 RPU3 10.101.93.101 192.168.93.101 RVI3 10.101.86.101 192.168.86.101 10.101.100.101 NA Ion Xe 10.101.100.20 192.168.100.20 Ion Xe 20 10.101.100.30 192.168.100.30 Ion Xe RPU 10.101.96.201 192.168.96.201 Element 10.101.97.101 Element 2 10.101.99.101 192.168.99.101 If DHCP is enabled, this field will display the IP address that is being used by the desk (whether it is served via DHCP or a self-generated link-local IP address).
  • Page 480 Console Port 1 Port 2 Element 10.101.97.101 Element 2 10.101.99.101 192.168.99.101 If DHCP is enabled, this field will display the gateway IP address that is being used by the desk (whether it is served via DHCP or a self-generated link-local IP address). Physical Address The physical address is the MAC address.
  • Page 481 {Start Anyway} - launches without a network interface. Only User 1 is displayed above the CIA. {Start Offline} - starts in offline mode. {Cancel} - remains in start-up without launching into the Eos application. Ping Ping is used to test the network connection between two devices. Output Protocols This is for selecting which protocols the desk will output and which ones are included in the default.
  • Page 482 Eos allows you to use any sACN universes from 1-63,999.The number of universes that can be used at a time is limited to a block of 256 contiguous universes. The address range equals 1 to 32,767,488, which is 63,999 times 512. Eos and the Net3 Gateways support two versions of sACN, the draft version and the final ratified ver- sion.
  • Page 483 Network Type This setting adjusts the timeout period before a backup device will take control from the master. Standard- After five seconds of no response from the master, the backup will assume the mas- ter has disconnected and will then take control. Engineered - After 1.6 seconds of no response from the master, the backup will assume the master has disconnected and will then take control.
  • Page 484 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.
  • Page 485: Maintenance And Diagnostics

    When configured as a server, a desk will serve out time to other devices on the net- work, acting as a time “master” ETC Net2 Time - With ETC Net2 Time enabled, the time server will periodically broadcast (as a server) or receive (as a client) the current time, which is required by devices running the ETCNet2 protocol, for example, Legacy Unison systems.
  • Page 486 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 (on page 11)) can help us isolate the issue.
  • Page 487 Backup System Settings {Backup System Settings} will open a window that allows you to save .ini file to a selected drive. To backup settings, select a drive from the drop down menu, and press {Accept} to save or {Cancel} to exit without saving.
  • Page 488 If installed on your console, the {Gateway Configuration Editor (GCE)} button will display. Concert If installed on your console, the {Net3 Concert} button will display. UpdaterAtor If installed on your console, the {UpdaterAtor} button will display. Touch Screen Test {Touch Screen Test} opens an application for testing your touchscreens. Upgrade Console {Upgrade Console...} is used for upgrading the desk's outputs.
  • Page 489 \\10.101.90.101\ShowArchive or \\YourDeviceName\ShowArchive) The network path type can be Eos, Eos Ti, Gio, Gio @ 5, Ion, Ion Xe, Ion Xe 20, Ion Xe RPU, Element, Element 2, or ETCnomad Puck. If Other is selected, you will have additional fields to fill out for Username and Password.
  • Page 490: Buttons

    For more information, please see the Setup Guide for your RPU. Setup Guides can be downloaded from the ETC website, www.etcconnect.com. Face Panel Buttons This area is for configuring the buttons the customizable hardkeys on the Eos Ti, Gio, and Gio @ 5 facepanels.
  • Page 491 Local DMX Outputs Note: If you have an external device that has an I/O card, such as a Gadget 2, you can con- figure its ports from this display. The following settings are available: Enable - enables DMX output from the local DMX ports. Default Output Protocol - enables DMX as a default output.
  • Page 492: Rfr

    Local 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 your console.
  • Page 493 Note: These settings need to match between the desk and the RFR. High Frequency Channel The frequency that the RFR is using. There are 1-12 channels. Network ID The Network ID is a separate digital channel on a single high frequency (HF) setting. There are 1-99 IDs available.
  • Page 494 Eos Family Operations Manual...
  • Page 495: Show Control

    C h a p t e r 3 0 Show Control Eos Family consoles support a variety of show control protocols. Specific information about using each type of show control can be found in each type’s section. This chapter contains the following topics: About Eos Family Show Control Show Control Settings Show Control Display...
  • Page 496: About Eos Family Show Control

    About Eos Family Show Control The following is an overview of the show control types and general setup information. The Eos Family can use the following show control protocols: SMPTE - An analog signal indicating time (subdivided into hours, minutes, seconds, and frames) that is used to sync events between multiple devices.
  • Page 497: Show Control Settings

    Show Control Settings In [Setup]>{System}>{Show Control}, you can adjust settings for MIDI Show Control, time code (MIDI or SMPTE), analog, and serial functions. See Show Control Setup (below) Show Control Setup This section allows you to adjust settings for MIDI show control, time code (MIDI or SMPTE), analog, and serial functions.
  • Page 498 {MIDI Time Code Rx} As above, but for MIDI Time Code instead of SMPTE. The default for this setting is “Enabled”. {MSC Rx Device ID} Also known as a “device ID” this setting configures the MIDI channel for the console to receive MIDI Show Control information.
  • Page 499 This setting specifies the UDP port that the console will listen to for OSC receiving strings. Note: ETC recommends using 8000 and 8001 respectively for port numbers. Remember that when setting port numbers on your external device that they should be set to the opposite of what Eos is set.
  • Page 500 {OSC TX Port Number} This sets the UDP destination port to which the console will send OSC strings. {OSC Cue Send String} Allows the user to specify a different outgoing OSC string format for integration with other applic- ations. Use %1 in the string format as cue number and %2 as the cue list number. {OSC TX IP Address} This sets the destination IP address or addresses to which the console will send OSC strings.
  • Page 501 Port Setup Options Eos Ti, Gio, Eos RPU3, Gio @5, Ion Xe, Element 2, Ion, Ion RPU, Element, and Eos Programming Wing have additional ports and connectors located on the rear panel for show control. Additional setup options for these ports and connectors are in the ECU>{Settings}>{Local I/O} and in ECU>{Settings}>...
  • Page 502 Relay Out (remote trigger connector) Allows you to set the Group and Address In values for the remote trigger port on the back of your console. Interface Protocols Additional settings are found in the ECU>Settings>Network. Open Sound Control (OSC) (on page 539) for more information.
  • Page 503: Show Control Display

    Show Control Display The Show Control Display allows for the creation of event lists, which are comprised of events. An Event List defines how incoming show control events are processed by the console – any protocol that can be received by the console is handled here. Each event list uses a different type of show con- trol at a time (time code, analog inputs, RTC, or network).
  • Page 504 Softkeys are available for the various event options: Event - is the event number, used to select or create a specific event from the command line. Can also use [Next]/[Last] to select/navigate through the events. Note: The event number is not fixed, it is just provided as a way to select an event. For example, in time code lists, the events are always chronological.
  • Page 505 Softkeys are available for the various event list options: List - is the event list number. <Event> [1][/][Enter] - creates event list 1. Label - names the event list. Type - sets which type of show control protocol to use; MTC, SMPTE, Analog, Network, or RTC.
  • Page 506 Analog inputs and network inputs use the external setting only as a way to enable and disable the entire list. Creating an Event List Getting started with an event list is the same regardless of which show control protocol you are using.
  • Page 507: Time Code

    Time Code Eos Family consoles can receive internal or external time code to execute event lists. Time code lists can receive timing data from either SMPTE or MIDI sources. Eos Family consoles accept up to 32 SMPTE sources and 32 MIDI Time Code (MTC) sources (each are numbered from 1- 32).
  • Page 508 Timing and 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 from an external source. When the timing data stops, the events will stop. When you enable the internal clock only, it starts running immediately and triggers events appro- priate to the time.
  • Page 509 <Event> [1] [/] {FrameRate} [2] [5] [Enter] When working in Live, to show the Time Code times in the Cue List, go to the Cue List Display. [Cue] [Cue] Select the Cue List to be triggered. [Cue] [1] [/] Now associate the Event List to the Selected Cue List. [Cue] [1] [/] {Execute} {Timecode} {1} [Enter] Both the Event List and the Cue List are ready for events to be added.
  • Page 510 Event timing can also be modified within a range. Let's say an additional 5 frames needs to be added to multiple events. <Event> [1] [Thru] [4] [Time] [+] [5] [Enter] Note: You will notice as events are added to the event list, the time code will display on the Playback Status Display.
  • Page 511 A {Learn Events} softkey is available in the event list. This macro-able item allows you to enable and disable show control learn mode. Macros containing this softkey will not be included in learned events. Other Macros can be learned as events in an Event List. Use {SC Learn} softkey in the Macro Editor to enable/ disable excluding specific Macros from being learned as events.
  • Page 512: Real Time Clock (Rtc)

    Real Time Clock (RTC) Eos Family consoles have 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.
  • Page 513 <Event> [1] [Time] [1] [5] [0] [0] [Enter] - sets the time for 3:00pm. <Event> [1] {Days} {Mon} {Wed} {Fri} [Enter] - adds on Mondays, Wednesdays, and Fridays. Note: Days of the week can either be entered in from their softkeys, or you can enter them in from the keypad using the conventional modifiers (+, -, thru).
  • Page 514: Analog Inputs

    Analog Inputs Eos Family consoles can accept analog input through a variety of interfaces. 0-10VDC inputs are received through a Net3 I/O Gateway. Contact closures can be received through the built-in remote trigger port on the desk (when available) and through a Net3 I/O Gateway. The I/O Gateway can be set up through the Net3 Concert software.
  • Page 515 <Event> [4] [/] {Internal} [Enter] Create an analog input event where an input on address 1 will fire cue 10. <Event> [4] [/] [1] {Analog Address} [1] [Cue] [1] [0] [Enter] Note: As there is no action softkey, pressing [Cue], [Sub], or [Macro] assumes you are post- ing to the action field.
  • Page 516 submaster On. If the submaster is set to a dwell time of Hold, the second trigger will turn the sub- master Off. Create an analog input event where an input on address 6 will bump Sub 1. <Event> [4] [/] [1] {Address} [6] [Sub] [2] {Bump} [Enter] Fader Acts as if the input is directly controlling the fader on the submaster.
  • Page 517 Relay Outputs Eos Family consoles can trigger relay outputs on Net3 I/O Gateways and on the built-in relay output (when available). Relay outputs are also often called remote triggers, contact closures, or contact out- puts. Relay outputs are controlled by external links in cues and submasters only. Note: You enter relay information in the live or blind displays.
  • Page 518: Sacn Input

    sACN Input Eos Family consoles can receive streaming ACN (sACN) level information from itself and other devices on the lighting control network. Similar to Analog Inputs, these received sACN input levels can then be used by the Event List display to execute certain actions. sACN allows for multiple sources to be present on the network.
  • Page 519 Create a new event list <Event> [8] [/] [Enter] Define the type of input <Event> [8] [/] {Type} {Network} [Enter] Create a new event <Event> [2] [Enter] Assign the sACN address using universe/address format {sACN} [4] [/] [2] [Enter] Add the action to execute. Actions can be either a cue, submaster, or macro {Action} {Sub} [1] {Fader} [Enter] Show Control...
  • Page 520: Midi Show Control

    MIDI Show Control Eos Family consoles can receive MIDI Show Control (MSC) data from Net3 Show Control Gateways and the built-in MIDI ports on a console or programming wing (when available). There can be up to 32 sources, and these sources can be assigned Group IDs between 1 and 32. MIDI Show Control is one of many different types of MIDI signals –...
  • Page 521 When accompanying a MIDI “Go” command, data for the following fields will result in the following actions: Cue Data Field List Data Field Action List Runs the specified cue in the specified cue list Runs the specified cue in cue list 1 List Runs the next cue in the specified list Runs the next cue in cue list 1...
  • Page 522 Fire This command fires a macro. MSC supports macros 1 through 127 only. Therefore a numeric value of 1 through 127 followed by 00 (in hex) would accompany this command. Sending MIDI Show Control When MSC Transmit is enabled in Setup (see Show Control Settings (on page 495)), the console will send MIDI Show Control commands to the specified MSC Transmit Channel (or Device ID) that cor-...
  • Page 523 Set - controls a submaster, playback, or Grandmaster = Command 06 Fire - runs a macro = Command 07 The other parts of the string are standardized. F0 7F and the ending F7 are parts of the standard MIDI System Exclusive message format. The 02 specifies the protocol is MIDI Show Control. Go, Stop, Resume The cue commands can target any available cue on the console.
  • Page 524 3. Playback Masters and Grandmasters – send the fader number, followed by 00 (in hex), and then the level value. You do not need to end the command with 00. For example, setting the grandmaster to 75% would be sent as 7E 03 00 4B For example, sending Device ID 3 a SET command for sub 4 to 0% would be formatted as follows: F0 7F 03 02 01 06 04 00 00 00 7F As a second example, sending Device ID 10 a SET command for the playback master “up”...
  • Page 525: String Interface

    String Interface RS232, UDP serial strings, ACN EPI strings, and OSC commands can be sent and received from the console. Enabling Serial You can configure sending and receiving the various serial protocols supported by the desk in Setup, Show Control Settings (on page 495).
  • Page 526 Note: Command line text needs to use the same language as your console. Language set- tings are found in ECU>General. Event Handler (Non-Command Line) All other text that doesn’t start with a “$” will be sent to the console’s event handler. Here are a few examples: Go 1 - fire cue list 1 Cue 1 2 - run cue 2 from list 1, on the appropriate fader...
  • Page 527 Note: Text requires either a carriage return (hex 0d), “\r”, or “#” to terminate the com- mand line. Receiving UDP Strings UDP strings must be sent to the console’s IP address (unicast) and designated port to be processed. Multicast and broadcast UDP strings are not supported. To find your console’s IP address, clear the command line and press [About].
  • Page 528 For Example: SC Hello# - sends the string “Hello” to the show control display via RS232, UDP, or OSC Strings For OSC commands that are intended to be processed by the Show Control display, the sending device needs to start the string with /eos/sc/ in order for the console to correctly process it. For Example: /eos/sc/Hello –...
  • Page 529 The sending device needs to start the command with /eos/sc/ in order for the console to listen to it. For example, type Hello in the Input String field. On your OSC sending device, have it send /eos/sc/Hello. Type in the string you want the console to listen for. The sending device needs to add “SC”...
  • Page 530 softkey. A {String} softkey will be displayed. When {String} is pressed, the alphanumeric keyboard will display. Enter the desired string, press [Enter] and text entered will be displayed in the external links field of the playback status display. If there is already a string linked to the selected cue, the string will be displayed for editing. When [Cue] [n] {Execute} {String} is on the command line, pressing [Next] / [Last] will step through all the strings used in that show file.
  • Page 531 Note: String MIDI Tx is restricted by {MIDI Cue List} in Setup. See Show Control Settings page 495). Sending UDP Strings UDP strings will be sent from the console on an ephemeral (always changing) port number to the des- tination port specified in Setup. UDP strings sent to multicast IP addresses are not supported. Note: The console can be configured to send either ACN strings or UDP strings, as they share the String Tx IP Address field.
  • Page 532: Midi Raw

    MIDI Raw Also known as MIDI Strings, MIDI Notes, MIDI Messages, or Channelized Event Data. Originally inten- ded for communication between musical instruments, MIDI has been adapted for a variety of uses between devices. Eos Family consoles can send or receive MIDI messages through the built-in MIDI ports (when available).
  • Page 533 Message Structure Note On has a structure of 9A BC DD, where 9 represents the Note On command, A represents the channel number, B represents the octave of the note, C represents the note value, and DD rep- resents the velocity. Note Off has a structure of 8A BC DD, where 8 represents the Note Off command, A represents the channel number, B represents the octave of the note, C represents the note value, and DD rep- resents the velocity.
  • Page 534 Velocity 0, Threshold 50 - The console is looking for an incoming MIDI note with a velocity that is greater than or equal to 50 (hex 32). If the note with a velocity of 0 is received, the event will also fire as it matches the velocity parameter. Velocity 0, Threshold 0 –...
  • Page 535 Control Change commands were designed to represent specific actions on MIDI devices, like pedals actuations and effects. For example, the Damper Pedal on a keyboard is often represented by con- troller number 64 (hex 40). Similar to MIDI Note commands, the MIDI data that is expected to be received is shown in the CIA and changes as you select event parameters.
  • Page 536 Message Structure Please see Hexadecimal and MIDI Show Control Formatting (on page 520) for more information on the show control message structures. Options The following options are available: {Commands} Go, Stop, Resume - represents triggering a cue, stopping a cue, and resuming a cue, respect- ively.
  • Page 537 {Note On} Select the MIDI Note value, for example, Bb (B-flat) {A#/Bb} Select the MIDI Note octave or leave it as Any. In this example, we’ll choose Any. <Octave> {Any} Select the MIDI channel <Channel> {1} Select the velocity <Velocity> {127} Optionally, select the velocity threshold so that the event will be triggered if the message is above this level.
  • Page 538 <Velocity Threshold> {1} Press {OK} to save the event {OK} Specify the action for the event <Event> [2] [Macro] [2] [Enter] Creating a Program Change Event Create a new event and open the MIDI String configuration screen <Event> [3] [More SK] {MIDI String} Select the {Program Change} type {Program Change} Select the MIDI channel...
  • Page 539 {OK} Specify the action for the event <Event> [4] [Sub] [1] {On} [Enter] Sending MIDI MIDI messages can be sent from cues and subs (using {Execute}) or from a Macro. Cues and Submasters After selecting a cue and pushing {Execute}, the {MIDI Raw} softkey becomes available. Notes can either be input using hexadecimal values (00 through FF) or decimal (0 through 255) values depend- ing on the connected device.
  • Page 540 Macros A {MIDI Raw} softkey is available in the macro editor display. Any text entered after the string com- mand in the macro will be sent to all string interfaces when that macro is fired. The same syntax applies in macros as they would in cues – either hexadecimal or decimal values can be entered. Eos Family Operations Manual...
  • Page 541: Open Sound Control (Osc)

    Open Sound Control (OSC) Open Sound Control (OSC) is a protocol that uses network communication (wired or wireless) to communicate between varying audio, video and lighting devices. Using OSC An OSC command contains a method and an optional list of arguments, or additional data for a par- ticular command.
  • Page 542 When using UDP, the appropriate IP address and ports must be configured in the Show Con- trol section of Setup. For systems without specific networking requirements, ETC recommends UDP port assignments in the range 4703 to 4727 or 8000 and 8001.
  • Page 543 OSC Method Arguments Examples/Comments /eos/ping=”abcde” /eos/ping=”abcde”,4 Ping response - see Implicit OSC Output (on page 558) for more information /eos/out/ping /eos/out/ping Same number of arguments that were sent /eos/out/ping=”abcde” /eos/out/ping/=”abcde”,4 Supported OSC Input All OSC commands must begin with “/eos/...” or “/eos/user/<number>/...”. Note: All of the command examples given can also use the “/eos/user/<number>/...”.
  • Page 544 OSC Method Arguments Examples/Comments (optional) Set parameter or DMX information /eos/chan/<number>/dmx number for channel DMX level /eos/chan/1/dmx=255 /eos/chan/<number>/param/ /eos/chan/1/param/pan=90 (useful for map- number for parameter level ping to an OSC slider) <parameter> /eos/chan/1/param/pan/ tilt=90 number for all parameter levels (set channel 1 pan & tilt to 90) /eos/chan/<number>/param/ <parameter 1>/<parameter 2>/...
  • Page 545 OSC Method Arguments Examples/Comments (optional) number for the button edge 1.0=down, 0.0=up /eos/at/-% /eos/at/-% (optional) Set parameter or DMX information /eos/at/dmx/128 (useful for mapping to an /eos/at/dmx number for the DMX level OSC slider) /eos/param/pan=270 (useful for mapping to an /eos/param/<parameter>...
  • Page 546 Arguments Examples/Comments Method Argument 3: Z 0.516 (pink color with 75% saturation) Wheel A wheel can be used to adjust channel levels and parameters. OSC Method Arguments Examples/Comments Argument 1: X (0.0-1.0) Argument 2: Y For 2D Pan/Tilt graph where bottom-left corner is (0.0, /eos/pantilt/xy (0.0-1.0) 0.0) and top-right corner if (1.0, 1.0)
  • Page 547 OSC Method Arguments Examples/Comments /eos/wheel/fine/<parameter 1>/ number for fine wheel ticks (positive or /eos/wheel/fine/pan/tilt=1.0 negative) <parameter 2>/... number for coarse wheel ticks (positive or /eos/wheel/course/<parameter> /eos/wheel/coarse/pan=1.0 nega tive) /eos/wheel/course/<parameter number for coarse wheel ticks (positive or 1>/ /eos/wheel/coarse/pan/ tilt=1.0 negative) <parameter 2>/...
  • Page 548 OSC Method Arguments Examples/Comments Wheel /eos/active/wheel/1=1.0 (increase value) /eos/active/wheel/1=-1.0 (decrease value) number of wheel ticks for the specific /eos/active/wheel/<index> /eos/active/wheel/1=4.0 (increase value rapidly) wheel mode (positive or nega- tive) (defaults to Coarse mode, but wheel mode can be changed with the /eos/wheel command) number of fine wheel ticks (positive or /eos/active/wheel/fine/<index>...
  • Page 549 OSC Method Arguments Examples/Comments /eos/subscribe/param/<parameter> 1=subscribe, 0=unsubscribe /eos/subscribe/param/red=1 /eos/subscribe/param/<parameter 1>/<parameter 2>/... 1=subscribe, 0=unsubscribe /eos/subscribe/param/pan/tilt=1 Direct Selects OSC direct selects are virtual buttons and are mapped separately than direct selects visible on the console. To use direct selects, you must first send one of the direct select creation commands. Direct selects are mapped as a single target type.
  • Page 550 OSC Method Arguments Examples/Comments Direct Select Information sent byEos – see Implicit OSC Output (on page 558) for more information /eos/out/ds/1/1= String argument containing descriptive text for ”Channels [1]” /eos/out/ds/<index> direct select at <index>: target name, page num- /eos/ds/1/1= ber, mode ”Groups [1 –...
  • Page 551 Another example: Create an OSC fader bank with 5 faders per page /eos/fader/1/config/5 OSC Fader 2/1 (Fader 6) is the same as console fader 1/6 (Fader 6) OSC Fader 3/1 (Fader 11) is the same as console fader 2/1 (Fader 11) Note: <index>...
  • Page 552 OSC Method Arguments Examples/Comments /eos/fader/<index>/<fader index>/ full none /eos/fader/1/2/full /eos/fader/<index>/<fader index>/ none /eos/fader/1/2/level level /eos/fader/<index>/<fader index>/ none /eos/fader/1/2/+% /eos/fader/<index>/<fader index>/- none /eos/fader/1/2/-% Fader Status Information – see Implicit OSC Output (on page 558) for more information /eos/out/fader/1/1= “S 1 Label” String argument with fader Sub 1 with a label “Label”...
  • Page 553 OSC Method Arguments Examples/Comments /eos/addr/<address> number for level to set address to (0-100) /eos/addr/513=100 (useful for mapping to an OSC slider) number for DMX level to set address to (0- /eos/addr/513/dmx=255 (useful for mapping to an OSC /eos/addr/<address>/dmx 255) slider) Magic Sheet OSC Method Arguments...
  • Page 554 OSC Method Arguments Examples/Comments (optional) /eos/group/<number>/param/ number for parameter level /eos/group/1/param/pan=90 <parameter> /eos/group/<number>/param/ number(s) for parameter levels /eos/group/1/param/pan/tilt=90,75 <parameter 1>/<parameter 2>/... /eos/group/<number>/param/ number for parameter dmx level /eos/group/1/param/pan=255 <parameter>/dmx /eos/group/<number>/param/ number(s) for dmx parameter levels /eos/group/1/param/pan/tilt/dmx=255 <parameter 1>/<parameter 2>/.../ dmx Macro Selects and fires (executes) macros OSC Method...
  • Page 555 OSC Method Arguments Examples/Comments /eos/preset number of preset to select /eos/preset=1 RecallPreset /eos/preset/fire number of preset to recall /eos/preset/fire=1 /eos/preset/<number>/fire number for button edge: 1.0=down, 0.0=up (optional) /eos/preset/1/fire Intensity Palette OSC Method Arguments Examples/Comments Select IntensityPalette /eos/ip number of intensity palette to select /eos/ip=1 RecallIntensityPalette /eos/ip/fire...
  • Page 556 OSC Method Arguments Examples/Comments /eos/cue number of cue to select /eos/cue=1.5 /eos/cue/<list number> number of cue to select (in the specified cue list) /eos/cue/1=1.5 number of cue part to select (in the specified cue /eos/cue/<list number>/<cue number> /eos/cue/1/1.5=2 list and cue number) Run Cues /eos/cue/fire number of cue to run...
  • Page 557 Cue List Banks Note: <index> is a 1-based index of any number of OSC cue list banks you wish to create. Eos will send the cue list label and cue information for all OSC cue list banks. See Explicit OSC Output (on page 557) for more information.
  • Page 558 Command Line Command line instructions can be sent directly. String substitution with arguments is also allowed. To add a substitution, add %1 (or %2, %3, etc…) where the number given is the argument number where the actual value should be found.
  • Page 559 OSC Method Arguments Examples/Comments /eos/cmd/Chan/1/At/75 /eos/cmd/<text>/<text>/<text>/... in-line command line arguments (optional) /eos/cmd/Chan/%1/At/ %2#=1, 75 Clear command lineeach time Same behavior as /eos/ cmd, but it resets the com- /eos/newcmd mand line first Direct event entry Same behavior as /eos/ cmd, but treated as con- sole /eos/event event Same behavior as /eos/ cmd, but it resets the com-...
  • Page 560 Implicit OSC Output When UDP transmit is enabled, certain OSC commands are sent out as appropriate. These events are typically generated as the target changes or in response to user input. Command Lines “/eos/out/user/<number>/cmd”, <string argument with current command line text for the current console user>...
  • Page 561 OSC Fader Banks “/eos/out/fader/<index>”, <string argument with descriptive text for the OSC fader bank at <index>> “/eos/out/fader/<index>/<fader index>/name”, <string argument with fader label for OSC fader bank at <index> for fader <fader index>> “/eos/fader/<index>/<fader index>”, <floating point number for fader percent: 0.0-1.0> Note: Eos will delay sending fader levels for faders that have been moved via OSC com- mands for 3 seconds.
  • Page 562: Eos Family Show Control Capabilities

    Eos Family Show Control Capabilities Note: Net3 Show Control Gateway has been abbreviated to SC GW for this table. MIDI Show Hardware MIDI MIDI Time Code MIDI Notes SMPTE (MTC) Connections Control (MSC) Local Local Local In/Out Via SC GW In Eos Titanium (Ti) Yes, In/Out In Only Also via SC...
  • Page 563 24 shared circuits- analog or digital *Ion consoles that have a DVI splitter and any Ion RPU have a local RS-232 port that is not enabled.  For questions, please contact ETC Technical Services. See Help from ETC Technical Services (on page 11)
  • Page 564: Advanced Osc

    Advanced OSC OSC List Convention The OSC List convention is used to send OSC commands that may exceed 512 bytes of data. To add an OSC List of items to an OSC Command, append the OSC Command Path with /list/<in- dex>/<count>, where <index> is the zero-based index offset into the entire list and <total> is the total number of elements in the entire list.
  • Page 565 For Example: “1-100” OSC Gel Gels will be represented as strings in the following format: <Gel Manufacturer Abbreviation><Gel Number> For Example: “AP1150” (Apollo 1150) “G101”  (Gam 101) “L2” (Lee 2) “R80”  (Rosco 80) “SG1”  (Rosco Super Gel 1) “E194”  (Rosco E Color 194) “T12”...
  • Page 566 Integrating Your App with Eos: Step 2 - Synchronize Request the number of items of a specific type of data you are interested with one of the following commands: /eos/get/patch/count /eos/get/cuelist/count /eos/get/cue/<cue list number>/count /eos/get/group/count /eos/get/macro/count /eos/get/sub/count /eos/get/preset/count /eos/get/ip/count (ip = Intensity Palette) /eos/get/fp/count (fp = Focus Palette) /eos/get/cp/count (cp = Color Palette) /eos/get/bp/count (bp = Beam Palette)
  • Page 567 /eos/get/patch/index/<index number> /eos/get/cuelist/index/<index number> /eos/get/cue/<cue list number>/index/<index number> /eos/get/group/index/<index number> /eos/get/macro/index/<index number> /eos/get/sub/index/<index number> /eos/get/preset/index/<index number> /eos/get/ip/index/<index number> /eos/get/fp/index/<index number> /eos/get/cp/index/<index number> /eos/get/bp/index/<index number> /eos/get/curve/index/<index number> /eos/get/fx/index/<index number> /eos/get/snap/index/<index number> /eos/get/pixmap/index/<index number> /eos/get/ms/index/<index number> Eos will reply with the matching command: (detailed OSC arguments for each data type listed below) /eos/out/get/patch/<channel number>/<part number>/list/<list index>/<list count>...
  • Page 568 Integrating Your App with Eos: Step 3 – Staying in Sync Your app can now request all of the show data from Eos, but if a user is editing show data, your app would become out of sync.  The solution to this is to subscribe to Eos show data changes with the fol- lowing command: /eos/subscribe = <uint32: X>...
  • Page 569 /eos/get/ip/<ip number> /eos/get/fp/<fp number> /eos/get/cp/<cp number> /eos/get/bp/<bp number> /eos/get/curve/<curve number> /eos/get/fx/<fx number> /eos/get/snap/<snap number> /eos/get/pixmap/<pixmap number> /eos/get/ms/<ms number> Request detailed show data information via UID: /eos/get/patch/uid/<UID> /eos/get/cuelist/uid/<UID> /eos/get/cue/uid/<UID> /eos/get/group/uid/<UID> /eos/get/macro/uid/<UID> /eos/get/sub/uid/<UID> /eos/get/preset/uid/<UID> /eos/get/ip/uid/<UID> /eos/get/fp/uid/<UID> /eos/get/cp/uid/<UID> /eos/get/bp/uid/<UID> /eos/get/curve/uid/<UID> /eos/get/fx/uid/<UID> /eos/get/snap/uid/<UID> /eos/get/pixmap/uid/<UID> /eos/get/ms/uid/<UID>...
  • Page 570 /eos/set/patch/<channel number>/text4 = <string: text> /eos/set/patch/<channel number>/text5 = <string: text> /eos/set/patch/<channel number>/text6 = <string: text> /eos/set/patch/<channel number>/text7 = <string: text> /eos/set/patch/<channel number>/text8 = <string: text> /eos/set/patch/<channel number>/text9 = <string: text> /eos/set/patch/<channel number>/text10 = <string: text> /eos/set/patch/<channel number>/notes = <string: text> /eos/set/patch/<channel number>/gel = <string: text>...
  • Page 571 <uint32: address of intensity parameter> (useful for monitoring streaming output to see live levels) <uint32: current level> <string: OSC Gel> <string: text 1> <string: text 2> <string: text 3> <string: text 4> <string: text 5> <string: text 6> <string: text 7> <string: text 8>...
  • Page 572 <string: fader mode> <bool: independent> <bool: HTP> <bool: assert> <bool: block> <bool: background> <bool: solo mode> <uint32: timecode list> <bool: OOS sync> For Example: /eos/out/get/cuelist/1/list/0/13 = 0, “00000000-0000-0000-0000-000000000000”, “My Cue List One Label”, “Master”, “Proportional”, True, False, True, False, False, False, 1, False CUELIST (2 OF 2): /eos/out /get/cuelist/<cue list number>/links/list/<list index>/<list count>...
  • Page 573 <uint32: color time delay (ms)> <uint32: beam time duration (ms)> <uint32: beam time delay (ms)> <bool: preheat> <OSC Number: curve> <uint32: rate> <string: mark> <string: block> <string: assert> <OSC Number: link> or <string: link> (string if links to a separate cue list) <uint32: follow time (ms)>...
  • Page 574 CUE (3 OF 4): /eos/out /get/cue/<cue list number>/<cue number>/<cue part number>/links/list/<list index>/<list count> = <uint32: index> <string: OSC UID> <OSC Number Range: linked cue lists list> For Example: /eos/out/get/cue/1/1/0/links/list/0/3 = 0, “00000000-0000-0000-0000-000000000000”, 2 CUE (4 OF 4): /eos/out /get/cue/<cue list number>/<cue number>/<cue part number>/actions/list/<list index>/<l- ist count>...
  • Page 575 /eos/out/get/group/1.2/channels/list/0/5 = 0, “00000000-0000-0000-0000- 000000000000”, “1-100”, 200, 300 MACRO (1 OF 2): /eos/get/macro/<macro number>/list/<list index>/<list count> = <uint32: index> <string: OSC UID> <string: label> <string: mode> For Example: /eos/out/get/macro/1/list/0/4 = 0, “00000000-0000-0000-0000-000000000000”, “My Macro One Label”, “” MACRO (2 OF 2): /eos/get/macro/<macro number>/text/list/<list index>/<list count>...
  • Page 576 <string: up time> <string: dwell time> <string: down time> For Example: /eos/out/get/sub/3/list/0/13 = 0, “00000000-0000-0000-0000-000000000000”, “My Sub Three Label”, “Additive”, “Proportional”, True, False, True, False, “”, “0”, “Man”, “0” SUB (2 OF 2): /eos/get/sub/<sub number>/fx/list/<list index>/<list count> = <uint32: index> <string: OSC UID>...
  • Page 577 /eos/out/get/preset/10/channels/list/0/3 = 0, “00000000-0000-0000-0000- 000000000000”, “1-5” PRESET (3 OF 4): /eos/get/preset/<preset number>/byType/list/<list index>/<list count> = <uint32: index> <string: OSC UID> <OSC Number Range: by type channel list> For Example: /eos/out/get/preset/10/byType/list/0/2 = 0, “00000000-0000-0000-0000-000000000000” PRESET (4 OF 4): /eos/get/preset/<preset number>/fx/list/<list index>/<list count> = <uint32: index>...
  • Page 578 <string: OSC UID> <OSC Number Range: channel list> For Example: /eos/out/get/ip/1/channels/list/0/3 = 0, “00000000-0000-0000-0000-000000000000”, 1-5 PALETTE (3 OF 3): /eos/get/<palette type>/<palette number>/byType/list/<list index>/<list count> = <uint32: index> <string: OSC UID> <OSC Number Range: by type channel list> For Example: /eos/out/get/ip/1/byType/list/0/2 = 0, “00000000-0000-0000-0000-000000000000” CURVE (1 OF 1): /eos/get/curve/<curve number>/list/<list index>/<list count>...
  • Page 579 For Example: /eos/out/get/fx/901/list/0/8 = 0, “00000000-0000-0000-0000-000000000000”, “Circle”, “Focus”, “Immediate”, “Immediate”, “Infinite”, 25 SNAPSHOT (1 OF 1): /eos/get/snap/<snap number>/list/<list index>/<list count> = <uint32: index> <string: OSC UID> <string: label> For Example: /eos/out/get/snap/1/list/0/2 = 0, “00000000-0000-0000-0000-000000000000”, “My Snap One Label” PIXEL MAP (1 OF 2): /eos/get/pixmap/<pixmap number>/list/<list index>/<list count>...
  • Page 580 For Example: /eos/out/get/pixmap/1/channels/list/0/3 = 0, “00000000-0000-0000-0000- 000000000000”, “101-105” MAGIC SHEET (1 OF 1): /eos/get/ms/<ms number>/list/<list index>/<list count> = <uint32: index> <string: OSC UID> <string: label> For Example: /eos/out/get/ms/1/list/0/2 = 0, “00000000-0000-0000-0000-000000000000”, “My MS One Label” OSC Troubleshooting In Eos, open the Diagnostics tab (Hold [Tab] and press [9][9]). Click {Incoming OSC} to enable logging of incoming OSC commands and {Outgoing OSC} to log outgoing OSC commands.
  • Page 581: Eos Osc Keys

    Eos OSC Keys The following is a list of the supported key names for use with OSC: /eos/key/ Internal Eos Command CHAN_SUBGROUP_BEGIN CHAN_SUBGROUP_END PLUS MINUS POINT SLASH COLON PLUS10 MINUS10 100_channel_display 100_CHANNEL_DISPLAY _last SLOTLAST _next SLOTNEXT DIMMER_A about ABOUT absolute ABSOLUTE_EFFECT acn_device_disconnect ACN_DEVICE_DISCONNECT action...
  • Page 582 /eos/key/ Internal Eos Command all_workspaces ALL_WORKSPACES allfade ALLFADE allnps ALL_NIPS alternate ALTERNATE always_absolute ABSOLUTE_PALETTE analog ANALOG analog_input ANALOG_INPUT apply EFFECT_PATTERN_APPLY arrow_down ARROW_DOWN arrow_left ARROW_LEFT arrow_right ARROW_RIGHT arrow_up ARROW_UP artnet ARTNET_INTERFACE ascii_case ASCII_CASE ascii_delims ASCII_DELIMS ascii_levels ASCII_LEVELS ascii_manuf ASCII_MANUF assert ASSERT asserttime ASSERT_TIME AT_TEXT...
  • Page 583 /eos/key/ Internal Eos Command beam BEAM_CAT beam_palette BEAM_PALETTE before_sunrise RTC_BEFORE_SUNRISE before_sunset RTC_BEFORE_SUNSET blackout BLACKOUT_BUTTON blackout_enable BLACKOUT_ENABLE blind PREVIEW block BLOCK bounce BOUNCE break_nested BREAK_NESTED break_nested_off BREAK_NESTED_OFF build BUILD bump SC_BUMP bump_1 BUMP01 bump_10 BUMP10 bump_2 BUMP02 bump_3 BUMP03 bump_4 BUMP04 bump_5 BUMP05 bump_6...
  • Page 584 /eos/key/ Internal Eos Command cia_softkey2 CIA_SOFTKEY2 cia_softkey3 CIA_SOFTKEY3 cia_softkey4 CIA_SOFTKEY4 cia_softkey5 CIA_SOFTKEY5 cia_softkey6 CIA_SOFTKEY6 cie_xyy COLOR_FADE_CIE_XYY cleanup CLEANUP_PALETTE clear CLEAR_DATA clear_all CLEAR_ALL clear_all_tabs CLEAR_ALL_TABS clear_all_visible_tabs CLEAR_ALL_VISIBLE_TABS clear_all_workspace_tabs CLEAR_ALL_WORKSPACE_TABS clear_calibration CLEAR_CALIBRATION clear_cmd CLEAR clear_cmdline RESET_COMMAND_LINE clear_effect EFFECT_PATTERN_CLEAR clear_errors DIMRACK_CLR_ERRS clear_filters CLEAR_FILTER_COMMAND clear_hold_color_point_origin CLEAR_HOLD_COLOR_POINT_ORIGIN clear_midi...
  • Page 585 /eos/key/ Internal Eos Command color_path COLOR_PATH color_scrub COLOR_SCRUB color_scrub_replay COLOR_SCRUB_REPLAY column_move_left COLUMN_MOVE_LEFT column_move_right COLUMN_MOVE_RIGHT column_resize_larger COLUMN_RESIZE_LARGER column_resize_smaller COLUMN_RESIZE_SMALLER command_history OPENCMDHISTORY commandline_on_psd CMDLNONPSD complete GOTO_CUE_COMPLETE confirm_command CONFIRMED continuous_run CONTINUOUS_RUN control CONTROL_CAT control_cat CONTROL_FILTER copy_to COPY_TO create_type NEW_EFFECT_TYPE create_virtual_hsb CREATE_VIRTUAL_HSB cue_beam_time SETUP_CUE_BEAM_TIME cue_color_time SETUP_CUE_COLOR_TIME cue_down_time...
  • Page 586 /eos/key/ Internal Eos Command default_mode MACRO_DEFAULT_MODE degrees_per_rev ENCODER_DEGREES_PER_REVOLUTION delay DELAY delete DELETE delete_device DELETE_DEVICE delete_effect DELETE_EFFECT deleteconfirm DELETE_CONFIRM desk_settings DESK_SETTINGS detach DETACH_DEVICE device_clear_errors DEVICE_CLEAR_ERRORS device_dimmers CIAPATCH_DEVICE_DIMMERS device_disconnected DEV_DISCONNECT device_discovered DEV_DISCOVERED device_discovery RDM_DISCOVERY_ENABLED device_errors DEVICE_ERRORS device_ignore_errors DEVICE_IGNORE_ERRORS device_lamp_controls DEVICE_LAMP_CONTROLS device_mode CIAPATCH_DEVICE_MODE device_properties DEVICE_PROPERTIES device_rdm...
  • Page 587 /eos/key/ Internal Eos Command display_presets SS_DISPLAY_PRESETS display_snapshots SS_DISPLAY_SNAPSHOTS display_time_mode_latch DISPLAY_TIME_MODE_LATCH display_timing DISPLAY_TIME_MODE displays DISPLAYS DMX_LEVEL dmx_ DMX_INTERFACE dmx_patch SFF_DMXPATCH done DONE douse DOUSE down DOWN duration EFFECT_DURATION duration DURATION_NUM_CYCLES dwell DWELL earliest EARLIEST earliest_m EARLIEST_MARK_CUE edit EDIT edit_frame EDIT_FRAME edit_mode EDIT_MODE edit_target TARGET_EDIT_EVENT...
  • Page 588 /eos/key/ Internal Eos Command element_bump_14 ELEMENT_BUMP_14 element_bump_15 ELEMENT_BUMP_15 element_bump_16 ELEMENT_BUMP_16 element_bump_17 ELEMENT_BUMP_17 element_bump_18 ELEMENT_BUMP_18 element_bump_19 ELEMENT_BUMP_19 element_bump_2 ELEMENT_BUMP_2 element_bump_20 ELEMENT_BUMP_20 element_bump_21 ELEMENT_BUMP_21 element_bump_22 ELEMENT_BUMP_22 element_bump_23 ELEMENT_BUMP_23 element_bump_24 ELEMENT_BUMP_24 element_bump_25 ELEMENT_BUMP_25 element_bump_26 ELEMENT_BUMP_26 element_bump_27 ELEMENT_BUMP_27 element_bump_28 ELEMENT_BUMP_28 element_bump_29 ELEMENT_BUMP_29 element_bump_3 ELEMENT_BUMP_3 element_bump_30 ELEMENT_BUMP_30 element_bump_31...
  • Page 589 /eos/key/ Internal Eos Command element_bump_50 ELEMENT_BUMP_50 element_bump_51 ELEMENT_BUMP_51 element_bump_52 ELEMENT_BUMP_52 element_bump_53 ELEMENT_BUMP_53 element_bump_54 ELEMENT_BUMP_54 element_bump_55 ELEMENT_BUMP_55 element_bump_56 ELEMENT_BUMP_56 element_bump_57 ELEMENT_BUMP_57 element_bump_58 ELEMENT_BUMP_58 element_bump_59 ELEMENT_BUMP_59 element_bump_6 ELEMENT_BUMP_6 element_bump_60 ELEMENT_BUMP_60 element_bump_7 ELEMENT_BUMP_7 element_bump_8 ELEMENT_BUMP_8 element_bump_9 ELEMENT_BUMP_9 element_pos_1 ELEMENT_POS_1 element_pos_2 ELEMENT_POS_2 element_pos_3 ELEMENT_POS_3 element_pps_4 ELEMENT_POS_4 enable...
  • Page 590 /eos/key/ Internal Eos Command encoder_lockout ENCODER_LOCKOUT encoder_mode_1 ENCODER_MODE_1 encoder_mode_2 ENCODER_MODE_2 encoder_mode_3 ENCODER_MODE_3 encoder_mode_4 ENCODER_MODE_4 encoder_mode_5 ENCODER_MODE_5 encoder_wheel_move ENCODER_WHEEL_MOVE encoders SNAPSHOT_ENCODERS end_query QUERY_COMPLETE enter ENTER entry ENTRY_MODE entrytime ENTRY_TIME escape ESCAPE even EVEN even_effect EFFECT_EVEN event SC_EVENT eventlist SC_EVENT_LIST exclusive EXCLUSIVE execute EXECUTE exit...
  • Page 591 /eos/key/ Internal Eos Command fader_5 FADER05 fader_6 FADER06 fader_7 FADER07 fader_8 FADER08 fader_9 FADER09 fader_ab FADER_AB fader_assert SLIDER_ASSERT fader_control FADER_CONTROLS fader_display FADER_DISPLAY fader_mode FADER_MODE fader_off FADER_OFF fader_page_back FADER_PAGE_BACK fader_pages FADER_PAGES fader_rate FADER_RATE fadermodule_1_connected SLIDER_MODULE1_CONNECTED fadermodule_2_connected SLIDER_MODULE2_CONNECTED fadermodule_3_connected SLIDER_MODULE3_CONNECTED faderpagepress FADER_PAGE_DOWN faderpagerelease FADER_PAGE_UP faders...
  • Page 592 /eos/key/ Internal Eos Command flexi_patch FLEXI_PATCH flexi_selected FLEXI_SEL flexi_show FLEXI_SHOW flexi_time FLEXI_TIME flexichannel_mode FLEXI_MODE flip FLIP flip_h PIXELMAP_FLIP_HORIZONTAL flip_v PIXELMAP_FLIP_VERTICAL focus FOCUS_CAT focus_effect FOCUS_EFFECT focus_palette FOCUS_PALETTE follow FOLLOW force_grandmaster_move FORCE_GRANDMASTER_MOVE foreground_mode MACRO_USER form FORM_CAT format FORMAT forward FORWARD frame_rate FRAME_RATE freeze PLAYBACK_FREEZE friday...
  • Page 593 /eos/key/ Internal Eos Command grouping GROUPING groups SFF_GROUPS hang HANG haptic_encoder_wheel_move HAPTIC_ENCODER_WHEEL_MOVE haptic_level_wheel_move HAPTIC_LEVEL_WHEEL_MOVE haptic_rate_wheel_move HAPTIC_RATE_WHEEL_MOVE hard_poweroff HARD_POWEROFF height PIXEL_HEIGHT help HELP hform HORIZ_FORM hide_cia CIA_HIDE hide_mouse HIDE_MOUSE high_contrast_displays HIGH_CONTRAST_DISPLAYS highlight HIGHLIGHT highlight_append HIGHLIGHT_APPEND highlight_preset HIGHLIGHT_PRESET highlight_remdim HIGHLIGHT_REM_DIM hold HOLD home HOME home_preset...
  • Page 594 /eos/key/ Internal Eos Command insert_channel INSERT_CHANNEL intensity INTENSITY_CAT intensity_block INTENSITY_BLOCK intensity_master INTENSITY_MASTER intensity_palette INTENSITY_PALETTE intensitydown INTENSITY_DOWN intensityup INTENSITY_UP interface INTERFACE interleave FAN_INTERLEAVE internal INTERNAL interpolate INTERPOLATE intime EFFECT_STEP_IN_TIME intime_effect INTIME_EFFECT invert PIXELMAP_SELECT_INVERT invert_pan INVERT_PAN invert_tilt INVERT_TILT ion_encoder_1 ION_ENCODER_1 ion_encoder_2 ION_ENCODER_2 ion_encoder_3 ION_ENCODER_3 ion_encoder_4...
  • Page 595 /eos/key/ Internal Eos Command learn_time_sample_bpm LEARN_TIME left_side_sk_1 LEFT_SIDE_SK_1 left_side_sk_2 LEFT_SIDE_SK_2 left_side_sk_3 LEFT_SIDE_SK_3 left_side_sk_4 LEFT_SIDE_SK_4 left_side_sk_5 LEFT_SIDE_SK_5 left_side_sk_6 LEFT_SIDE_SK_6 left_side_sk_7 LEFT_SIDE_SK_7 less_than LESS_THAN level LEVEL level_ VALUE level_wheel_move LEVEL_WHEEL_MOVE lightwright LW_FIELDS linear LINEAR_EFFECT link LINK list_partition CUE_PARTITION listview LIST_VIEW live LIVE live_ FROM_LIVE live_remdim_level...
  • Page 596 /eos/key/ Internal Eos Command macro_804 MACRO_804 macro_805 MACRO_805 macro_806 MACRO_806 macro_807 MACRO_807 macro_808 MACRO_808 macro_809 MACRO_809 macro_810 MACRO_810 macro_811 MACRO_811 macro_812 MACRO_812 macro_813 MACRO_813 macro_814 MACRO_814 macro_815 MACRO_815 macro_816 MACRO_816 macro_817 MACRO_817 macro_818 MACRO_818 macro_819 MACRO_819 macro_820 MACRO_820 macro_button MACRO_STAR macro_entry_delete MACRO_ENTRY_DELETE macro_loop_begin...
  • Page 597 /eos/key/ Internal Eos Command media SFF_RESOURCELIST midi MIDI midi_cue_list MIDI_CUELIST midi_raw MIDI_STRING miditimecode MIDI_TC minimum RESTORE_MINIMUM minus_links MINUS_LINKS mirror_in FAN_MIRROR_IN mirror_mode MIRROR mirror_out FAN_MIRROR_OUT module_1_connected MODULE1_CONNECTED module_1_disconnected MODULE1_DISCONNECTED module_2_connected MODULE2_CONNECTED module_2_disconnected MODULE2_DISCONNECTED module_3_connected MODULE3_CONNECTED module_3_disconnected MODULE3_DISCONNECTED monday RTC_MONDAY month RTC_MONTH more_softkeys MORE_SOFTKEYS move_to...
  • Page 598 /eos/key/ Internal Eos Command numofchannels NUM_OF_CHANS BUMP_OFF offline OFFLINE offset OFFSET offstate OFF_STATE BUMP_ON only_active ONLY_ACTIVE only_labels ONLY_LABELS only_levels ONLY_LEVELS only_show ONLY_SHOWDATA only_text ONLY_TEXT onstate ON_STATE oos_sync OOS_SYNC open_bp_blind OPEN_BEAM_PALETTE_PREVIEW open_browser OPENBROWSER open_chan_effect_display OPEN_CHAN_EFFECT_DISPLAY open_color_path_blind OPEN_COLOR_PATH_PREVIEW open_color_picker OPENCOLORPICKER open_cp_blind OPEN_COLOR_PALETTE_PREVIEW open_cue_blind OPEN_CUE_LIST_INDEX open_curve_preview...
  • Page 599 /eos/key/ Internal Eos Command ordered_view ORDERED_VIEW OSC_ENABLED osc_rx_port_number OSC_RX_PORT_NUMBER osc_tx_ip_address OSC_TX_IP_ADDRESS osc_tx_port_number OSC_TX_PORT_NUMBER page_column_1 PAGE_COLUMN_1 page_column_2 PAGE_COLUMN_2 page_column_3 PAGE_COLUMN_3 page_column_4 PAGE_COLUMN_4 page_column_5 PAGE_COLUMN_5 page_column_6 PAGE_COLUMN_6 page_column_7 PAGE_COLUMN_7 page_down PAGE_DOWN page_encoders_down PAGE_ENCODERS_DOWN page_encoders_up PAGE_ENCODERS_UP page_mode SCROLL_MODE page_up PAGE_UP palettes SFF_PALETTES paper_size_a2 PAPER_SIZE_A2 paper_size_a3 PAPER_SIZE_A3...
  • Page 600 /eos/key/ Internal Eos Command pattern PATTERN pdv_point PDV_POINT pdv_time PDV_TIME percent_per_rev ENCODER_PERCENT_PER_REVOLUTION pixel_map_apply_check PIXELMAP_APPLY_CHECK pixel_map_column_guides PIXELMAP_COLUMN_GUIDES pixel_map_delete PIXELMAP_DELETE pixel_map_direction PIXELMAP_DIRECTION pixel_map_done PIXELMAP_APPLY pixel_map_edit PIXELMAP_EDIT pixel_map_file PIXELMAP_FILE pixel_map_flash PIXELMAP_FLASH pixel_map_horizontal_order PIXELMAP_HORIZONTAL_ORDER pixel_map_last PIXELMAP_LAST pixel_map_library PIXELMAP_LIBRARY pixel_map_mask PIXELMAP_MASK pixel_map_next PIXELMAP_NEXT pixel_map_overlay PIXELMAP_OVERLAY pixel_map_overwrite PIXELMAP_OVERWRITE pixel_map_reorder_files...
  • Page 601 /eos/key/ Internal Eos Command post_select_softkeys POST_SELECT_SOFTKEYS power_off POWEROFF preheat PREHEAT preheat_off PREHEAT_OFF preheat_time PREHEAT_TIME preserve_blind_cue PRESERVE_BLIND_CUE preserve_native_on_patch_change PRESERVE_NATIVE_ON_PATCH_CHANGE preset PRESET presets SFF_PRESETS prev_channels RESTORE_CHANNEL_LIST previous RESTORE_PREVIOUS print_color_printout PRINT_COLOR_PRINTOUT print_feedback_errors PRINT_FEEDBACK_ERRORS print_file PRINTFILE print_folder PRINTFOLDER print_summary_view PRINT_SUMMARY_VIEW print_tracked_levels PRINT_TRACKED_LEVELS priority SOURCE_PRIORITY properties PROPERTIES proportion...
  • Page 602 /eos/key/ Internal Eos Command ref_only REFERENCES_ONLY relay RELAY relay_output RELAY_OUTPUT release RELEASE_FADER rem_dim REM_DIM remfiltercat REM_FILTER_CAT remfilterparam REM_FILTER_PARAM remove_favorite PATCH_REMOVE_FAVORITE reorder REORDER repeat FAN_REPEAT repeat_last_command REPEAT_LAST_COMMAND repeat_on_go EFFECT_REPEAT replace REPLACE_ADDRESS replace_with REPLACE_WITH request_file REQUESTFILE reset_all_tabs RESET_ALL_TABS reset_columns RESET_COLUMNS reset_desk_settings RESET_DESK_SETTINGS reset_show_settings RESET_SHOW_SETTINGS reset_system...
  • Page 603 /eos/key/ Internal Eos Command rpu_19 RPU_19 rpu_2 RPU_2 rpu_20 RPU_20 rpu_21 RPU_21 rpu_3 RPU_3 rpu_4 RPU_4 rpu_5 RPU_5 rpu_6 RPU_6 rpu_7 RPU_7 rpu_8 RPU_8 rpu_9 RPU_9 rtc_time RTC_TIME run_cue RUN_CUE run_rig_check DIMRACK_RUN_RIG_CHK rvi_settings RVI_SETTINGS sacn sat_adjust COLOR_FADE_SAT saturday RTC_SATURDAY save SAVE save_file SAVEFILE...
  • Page 604 /eos/key/ Internal Eos Command setup SETUP shield SHIELDED_SUB shift SHIFT show_channels SFF_SHOWCHANNELS show_control SFF_SHOWCONTROL show_control_action SC_ACTION show_park_buffer SHOW_PARK_BUFFER show_ref_labels SHOW_REF_LABELS show_reference_labels SHOW_REFERENCE_LABELS show_settings SHOW_SETTINGS show_source_data SHOW_SOURCE_DATA show_stored_data SHOW_STORED_DATA shutdown_fixture SHUTDOWN_LAMP shutdown_macro SHUTDOWN_MACRO shutter SHUTTER_CAT single_param SINGLE_PARAM size SIZE slider_move SLIDER_MOVE smpte SMPTE smptetimecode...
  • Page 605 /eos/key/ Internal Eos Command spreadsheet SPREADSHEET startup_macro STARTUP_MACRO status EFFECT_STATUS step STEP stepbased STEPBASED_EFFECT steptime STEP_TIME stop STOP stop_1 STOP01 stop_10 STOP10 stop_2 STOP02 stop_3 STOP03 stop_4 STOP04 stop_5 STOP05 stop_6 STOP06 stop_7 STOP07 stop_8 STOP08 stop_9 STOP09 stop_all STOP_ALL_EFFECT stop_and_fade STOP_AND_FADE stop_and_hold...
  • Page 606 /eos/key/ Internal Eos Command subrelease SUB_RELEASE subtype SUB_TYPE subup SUB_BUMP_UP sunday RTC_SUNDAY sw_go_1 SW_GO_1 sw_go_10 SW_GO_10 sw_go_11 SW_GO_11 sw_go_12 SW_GO_12 sw_go_13 SW_GO_13 sw_go_14 SW_GO_14 sw_go_15 SW_GO_15 sw_go_16 SW_GO_16 sw_go_17 SW_GO_17 sw_go_18 SW_GO_18 sw_go_19 SW_GO_19 sw_go_2 SW_GO_2 sw_go_20 SW_GO_20 sw_go_21 SW_GO_21 sw_go_22 SW_GO_22 sw_go_23...
  • Page 607 /eos/key/ Internal Eos Command sw_go_6 SW_GO_6 sw_go_7 SW_GO_7 sw_go_8 SW_GO_8 sw_go_9 SW_GO_9 sw_stop_1 SW_STOP_1 sw_stop_10 SW_STOP_10 sw_stop_11 SW_STOP_11 sw_stop_12 SW_STOP_12 sw_stop_13 SW_STOP_13 sw_stop_14 SW_STOP_14 sw_stop_15 SW_STOP_15 sw_stop_16 SW_STOP_16 sw_stop_17 SW_STOP_17 sw_stop_18 SW_STOP_18 sw_stop_19 SW_STOP_19 sw_stop_2 SW_STOP_2 sw_stop_20 SW_STOP_20 sw_stop_21 SW_STOP_21 sw_stop_22 SW_STOP_22 sw_stop_23...
  • Page 608 /eos/key/ Internal Eos Command sw_stop_6 SW_STOP_6 sw_stop_7 SW_STOP_7 sw_stop_8 SW_STOP_8 sw_stop_9 SW_STOP_9 swap SWAP swap_address SWAP_ADDRESS swap_pan/tilt SWAP_FIXTURE system_settings SFF_SYSTEMSETTINGS SHEET tab_down TAB_DOWN tab_up TAB_UP tb_pan_swap TB_PAN_SWAP tb_tilt_swap TB_TILT_SWAP tb_xy_swap TB_XY_SWAP test_fixture TEST_LAMP text1 TEXT1 text10 TEXT10 text2 TEXT2 text3 TEXT3 text4 TEXT4...
  • Page 609 /eos/key/ Internal Eos Command tracking TRACKING_MODE trail TRAIL transmitchan MSC_TRANSMIT_CHAN trckbll_on/off TRACKBALL_PAN_TILT_TOGGLE tuesday RTC_TUESDAY type TYPE undo UNDO undouble DIMMER_UNDOUBLE unown UNOWN unpatch UNPATCH unpatched UNPATCHED_QUERY UP_TIME update UPDATE update_lin UPDATE_LIB update_mode UPDATE_MODE user_id USER_ID utilization_reports SFF_UTILREPORTS vform VERT_FORM view MAGICSHEET_VIEW view_channels FLEXI_VIEW_CHANNELS...
  • Page 610 /eos/key/ Internal Eos Command width PIXEL_WIDTH year RTC_YEAR Eos Family Operations Manual...
  • Page 611: Facepanel Shortcuts

    [About] & [Time] - locks the display to discrete time display. [Data] & [Focus Encoder Page] /[Color Encoder Page] etc - to expand/suppress categories on displays (Ion) [Data] & [Parameter Tiles] - to suppress/display individual parameters from the display when not in summary view (Ion) [Params] &...
  • Page 612: Facepanel

    Left Mouse Button & Scroll - zooms the display in focus on a PC Scroll with two fingers - zooms the display in focus on a Mac [Tab] & [Up/Down Arrow] - cycle workspaces [Tab] & [Left/Right Arrow] - move displays [Tab] &...
  • Page 613 [Shift] & [Enter] - reselects the last command and leaves it unterminated; does a loop of last five commands [Shift] & [Block] - posts Intensity Block to the command line [Shift] & [Clear] - clears the command line [Shift] & [Delay] - posts follow [Shift] &...
  • Page 614: Eos Family Hotkeys

    To enable Eos functions on Mac Function keys: Open Systems Preferences Go into the Keyboard section Enable the “Use all F1, F2,etc... keys as standard function keys” setting. Note: Some international keyboards require “Use Shift Key as Eos Shift” to be disabled in the General section of the ECU Settings.
  • Page 615 ConsoleKey ConsoleKey ConsoleKey Macro 803* Control Alt 3 Record Update Macro 804* Control Alt 4 RecordOnly Control R Virtual Keyboard Control K Macro 805* Control Alt 5 Release Control Alt S Workspace ] or [ Macro 806* Control Alt 6 Rem Dim Macro 807* Control Alt 7...
  • Page 616 Index actions analog inputs active cue list changing address 13, 200 .csv parking in live exporting address check importing allfade 266, 294 analog inputs 494, 512 actions cues events macros submasters about aRFR about ASCII channel 381, 383 exporting color path importing assert cuelist...
  • Page 617 offline console button overlays primary See button module. backup console buttons definition configuration basic manual control by type palettes 225, 234 beam palette editing in blind description updating by type presets blackout 31, 318 updating blind using configuration menu display indicators editing cues in calibrate scroller editing palettes in...
  • Page 618 using about 381, 383 configure CIA. See Central Information Area Eos Ti and Gio DMX ports clear show control ports command line console cue attributes capacities filters cleaning patch geography 20-21, 23-25 submaster conventional fixtures clear functions display conventions clear patch copy clear show fixture...
  • Page 619 active list, changing the external links fader and button fanning time go after loop flags new, recording to allfade using {Record Only} assert using {Record} block mark out of sequence sync preheat ownership go to cue properties modifying record via load from spreadsheet view recording to new from summary view...
  • Page 620 selected, the customizable hardkeys;hardkeys in blind customizable in live settings in setup data (navigation key) storing database settings, in patch selective Default About using Cue Only/Track Parameters in Cue Only mode delay in Track mode effects storing multiparts in blind delay timing timing delete...
  • Page 621 storing palettes to zooming discrete timing display outputting indicators from Eos Ti and Gio mark value on command line display indicators displays attribute, in patch edit (softkey) changing format in cue list index closing editing color indicators cues in blind controlling curves database, in patch...
  • Page 622 (key) editing using in syntax live ETC locations focus ETC Technical Services linear ETCnomad multiple intensity HTP fullscreen editor ethernet ports relative events color analog inputs defining a pattern event list 502, 504 focus MIDI 533-534 linear MIDI note off...
  • Page 623 configuration flags control buttons allfade list block motorized channels/parameters palettes 230, 246 cues parameter filters mark playback controls 317, 320 flash presets flash off rate override flash on release flexichannel ribbon description status display (Element) multicell temporary mapping partitioned virtual module patch views flip from the command line...
  • Page 624 go to cue with multiple cue lists Go To Cue hang timing help system go to cue 0 description & [Load] high See highlight command line highlight playback button rem dim go to cue out temporary level gobo home (hardkey) importing;import encoder softkey gobo...
  • Page 625 live 17, 200 configuration menu display indicators keypad editing effects in navigation editing groups in selecting channels with editing palettes in setting parameters with editing presets in keys modifying cues in backlit park keywords parking addresses in adding in patch preview mode recording cues in recording multipart cues in...
  • Page 626 deleting make null editing about editor display managing show files modes manual control [last] playing [next] stopping address check storing in live advanced using {About} capture using {Learn} copy to magic sheets query about recall from array button modules backgrounds selecting channels with creating channel check...
  • Page 627 allowing live moves receiving AutoMark resume AutoMark timing sending display indicators earliest setup 154, 495 flag 219, 266 show control priority stop referenced marks strings removing referenced marks system events setting referenced mark flags MIDI Notes symbols MIDI Raw timing, referenced marks MIDI Strings mark time 154, 221...
  • Page 628 multipart cues in patch about online forums attributes register for setting OOS Sync changing into standard cues open changing standard cues into fixture editor recording in live Open Sound Control storing in blind opening updating in live displays multiple intensity channels from the browser multiple intensity HTP effects from the hardkeys...
  • Page 629 group implicit output paging intensity palette encoders list convention faders local softkeys macro palettes magic sheet about misc console events as absolute data other beam ping by type 225, 234 pixel map color preset copy to settings deleting show control events editing in blind 230-231 show file information...
  • Page 630 parameter display deleting a channel about dimmer doubling parameters display categories 14, 32 Image display editing display in CIA scrollers homing wheels editor setting fixture editor keypad, using LEDs snap move to Parameters moving channels park moving light about multicell fixtures addresses in live offset, using buffer...
  • Page 631 using {Go} recalling using {stop/back} removing channels from 235, 245 using go to cue rerecording playback status display storing color indicators using {Record Only} configuration using {Record} expanded timeline format storing in live Image updating indicators using about text indicators primary console playing macros definition...
  • Page 632 events release programming Release recall from Release. See Sneak park rem dim. See remainder dim record remainder dim cue list highlight using {Record Only} proportional value using {Record} remote power off cues remote power on in live Remote Processor Unit (RPU) using Record button configuration using Record Only...
  • Page 633 523, 525 managing RS232 523, 525, 527 merging sending 527-528 name 523, 525, 527 bold Services normal ETC Technical settings open existing attribute, in patch print database, in patch quick save patch save as saving existing...
  • Page 634 show setup using record filters {system} string interface shutter control 523, 525 from encoders SMPTE receiving ACN setup 154, 495 RS232 snap parameters 146-147 sending snapshots sending from macros about delete Subgroups edit Groups submasters popup about recall analog inputs record bump button timing with sneak...
  • Page 635 Elo touchscreen tools calibrate table view encoder editing presets in ETC touchscreens modifying cues from calibrate technical services text indicators trace in live/blind with update in playback status display Track mode time deleting cues in...
  • Page 636 references working with a single cue list in cues working with multiple cue lists source cue workspaces styles submasters using trace update dialogue box USB ports user data between different IDs about assigning relation to data sharing with multiconsole multiple 435, 458 User Forums view...
  • Page 637 Service: (DE) techserv-hoki@etcconnect.com Hong Kong Tel +852 2799 1220 Service: (Asia) service@etcasia.com Web: etcconnect.com © 2018 Electronic Theatre Controls, Inc. Product information and specifications subject to change. ETC intends this document to be provided in its entirety. 4250M1210-2.7.0 Rev A Released 2018-05...
  • Page 638 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.
  • Page 639 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.
  • Page 640 Control. 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...
  • Page 641 (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,...
  • Page 642 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.
  • Page 643 b) 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.
  • Page 644 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,...
  • Page 645 NORTON LICENSE AGREEMENT Norton Ghost IMPORTANT: PLEASE READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT (“LICENSE AGREEMENT”) CAREFULLY BEFORE USING THE SOFTWARE (AS DEFINED BELOW). SYMANTEC CORPORATION, IF YOU ARE LOCATED IN THE AMERICAS; OR SYMANTEC ASIA PACIFIC PTE LTD, IF YOU ARE LOCATED IN THE ASIA PACIFIC RIM OR JAPAN; OR SYMANTEC LIMITED, IF YOU ARE LOCATED IN EUROPE, THE MIDDLE EAST OR AFRICA (“SYMANTEC”) IS WILLING TO LICENSE THE SOFTWARE TO YOU AS THE INDIVIDUAL, THE COMPANY, OR THE LEGAL ENTITY THAT WILL BE UTILIZING THE SOFTWARE (REFERENCED BELOW AS “YOU”...
  • Page 646 2. Content Updates: Certain Software uses content that is updated from time to time, including but not limited to the following Software: antivirus and crimeware software use updated virus definitions; antispyware software uses updated spyware definitions; antispam software uses updated antispam rules; content filtering and antiphishing software use updated URL lists;...
  • Page 647  The name given during initial setup to the computer on which the Software is being installed. If collected, the name will be used by Symantec as an account name for such computer under which You may elect to receive additional services and/or under which You may use certain features of the Software.
  • Page 648 7. Disclaimer of Damages: SOME STATES AND COUNTRIES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE BELOW LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW AND REGARDLESS OF WHETHER ANY REMEDY SET FORTH HEREIN FAILS OF ITS ESSENTIAL PURPOSE, IN NO EVENT WILL SYMANTEC OR ITS LICENSORS BE LIABLE TO YOU FOR ANY SPECIAL, CONSEQUENTIAL, INDIRECT, OR SIMILAR DAMAGES, INCLUDING ANY LOST PROFITS OR LOST DATA ARISING...
  • Page 649 Additional Terms and Conditions: In additon to the terms and conditions set forth above, the following terms and conditions will also apply to Your use of the Software: A. You may use the Software on one Device to clone, or apply an image of a hard drive on that Device, or to another hard drive on the same Device, a replacement Device, secondary media, or network drive.

This manual is also suitable for:

Ion xe 20Element 2EosGioEos tiGio @5

Table of Contents