ETC Eos v1.3 - Manual (Page 284)

270 Eos Operations Manual
About Show Control
The Eos Show Control system consists of MIDI Show Control plus any number of time code event
lists (MIDI or SMPTE). There can be more than one event list of each type, but only one MIDI Show
Control is available. For instance there can be multiple SMPTE Time Code lists, each with its own
timing source, frame rate and event list. All can be running simultaneously.
Each event list has a label, data source and status. The status information depends on the list type
and is detailed below.
Setup
Eos provides user-definable settings for show control which can be accessed by pressing
[Displays]>{Setup}>{Show}>{Show Control}. For more information, see
Show Control, page 87 .
MIDI Show Control
Data Sources
MIDI Show Control (MSC) receives data from a MIDI input source. There are 32 available MIDI
sources, numbered 1-32. MIDI consists of many types of data, but MSC looks only at MSC data.
Other MIDI transmitted data is ignored by MSC.
MIDI Show Control Devices
MIDI Show Control data carries a device ID within the data packet. MSC setup allows for the
specification of two device IDs: one for reception and one for transmission.
Only MSC data with the correct receive device ID, or an ALL CALL ID, will be interpreted by Eos.
All outgoing MSC data contains the specified transmit device ID within.
Eos Command Interpretation
When Eos receives a command from a MIDI source, it will look for and support the following MIDI
commands in the following ways:
• Go Runs a cue
• Stop Pauses a Cue
• Resume Resumes a paused cue
• Set Controls a submaster, playback, or grandmaster
• Fire Runs a macro
The cue-related commands (go, stop, resume) affect Eos based on the cue and list fields also
contained within the MSC data. Cue and list fields will correspond directly to the Eos cues and cue
lists. In the command/effect tables below, if a field is present in the MSC data, the name is indicated
(such as “Cue” or “List”). If it is not present in the data, a “-” is indicated. For example, “Cue -”
implies that a cue is specified in the data, but not a list.