25 Using Show Control 301
Analog Inputs and Relay Outputs
Analog Inputs
Analog inputs come from an I/O gateway. Each analog event in the event list consists of a port
address and an action. There is a global enable for all analog inputs in Setup, see Show Control,
page 96.
Analog Input Events
Analog Input events fire when the analog input passes a certain level. Action types supported are
the same as Time Code; run a cue, control a submaster, and fire a macro.
Create an Analog Input Event where an input on address 1 will fire Cue 10.
• <Event> [4] [/] [1] {Address} [1] [Cue] [1] [0] [Enter]
If you select the submaster option, you will have an additional option of fader, which will map the 0-
10v input to the level of a specified submaster.
Relay Outputs
Relay outputs are possible using an I/O gateway. Relay outputs are also often called remote
triggers, contact closures, or contact outputs. Relay outputs are controlled by external links in cues.
See Using the Execute List, page 178.
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.
To Next Page
Loading...
