Setup 135
{MSC Rx Device ID}
This setting allows you to choose the devices from which the console will receive MSC. When
set, the console will respond to MSC data from any Net3 gateway that has a matching “ACN
MSC Rx ID.” Gateways will send the MIDI data over an ACN connection. When built-in MIDI
ports are available, the setting needs to match or at least contain the MSC Rx ID.
Example:
{MSC Rx Source ID} [2] [5] [Enter]
{MSC Rx Source ID} [1] [Thru] [1][0] [Enter]
{MSC Tx Device ID}
This setting allows you to choose the devices which the console will send MSC to.
{MIDI Cue List}
MIDI Cue List specifies the cue list that the console will use to send MSC data. If left blank and
MSC Tx is enabled, all cue lists will generate MSC events. Otherwise, only the particular list (or
lists) selected will fire MSC events.
MIDI - Network
{MIDI Rx Device ID}
Also known as a “device ID” this setting configures the MIDI channel for the console to receive
MIDI Show Control information. Only MSC data with the same device ID will be received. A
device ID can be from 0-126. MSC commands can be sent to ID 127, which is the All Call device
ID. While Eos cannot be set to ID 127, it will respond to commands sent to the All Call device ID.
Example:
{MSC Rx Device ID} [5] [0] [Enter]
{MIDI Rx 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).
Example:
{MSC Rx Device ID} [5] [0] [Enter]
{MIDI Tx Source ID}
This setting allows you to choose the devices through which the console will send MIDI data.
When set, the console will transmit MSC data from any Net3 gateway that has a matching
“ACN MIDI Tx ID.” The console will then send the MIDI data over an ACN connection to the
gateways. When built-in MIDI ports are available, the setting needs to match or at least contain
the MIDI Tx ID.
To Next Page
Loading...
