There is some information on our wiki page on doing this. In short, you will need a Net3 Show Control gateway in the system, and it's MIDI Out group ID must match that of the Eos's MIDI TX ID in Setup -> Show Settings -> Show Control. MSC Transmit must also be enabled in the same screen.
In order to get MIDI out you need to have a Show Control Gateway on your network, Also make sure that MSC transmit is enabled in your Show Control settings.
I'm not sure when this post was written if there were the the settings for ACN MIDI Tx ID that there is now in 1.9.12. How does this setting relate to using the Show Control Gateway and MSC?
"ACN MIDI Tx ID" and "ACN MIDI Rx ID" are the way you choose which physical Show Control Gateway you want to transmit the actual MIDI out of, or receive MIDI from.
The setting in Eos needs to match the setting of the Show Control Gateway.
They are purely for routing on the ACN network, and have no bearing on MSC itself.
Thank you. Just out of curiosity, where would this be used? If you have more than one Gateway on the network and they have separate ACN MIDI Tx IDs then the only way to talk to both Gateways would be to have more than one transmitter (console) on the network. Couldn't you just change the actual MSC Channel ID on each and accomplish the same split?
You can have multiple timecodes coming in from different sources, and create different lists to deal with them. For example, in a theme park, you might have the overall 24H timecode to trigger various events, but a different timecode signal from a given attraction's show time. These would be likely to be triggering different cue lists/subs/macros.
Another (similar) example would be an awards show, with overall show time (taking into account crying divas and extended speeches from best supporting dog handlers) as one event list, but individual performances in another.
Sorry to be a pain, but I don't get it. The console can only listen to one MSC ID at a time so how could multiple ACN MSC IDs help with multiple lists?
In some deployments of Eos systems, there are multiple master consoles and multiple Show Control Gateways on the same network. By setting Master 1 and Show Control Gateway 1 to ACN MSC ID 1, and setting Master 2 and Show Control Gateway 2 to ACN MSC ID 2, you can have these two systems operating at the same time.
In some deployments of Eos systems, there are multiple master consoles and multiple Show Control Gateways on the same network. By setting Master 1 and Show Control Gateway 1 to ACN MSC ID 1, and setting Master 2 and Show Control Gateway 2 to ACN MSC ID 2, you can have these two systems operating at the same time.
~P
I understand this. My point was that you could accomplish the same thing by separating the actual MSC Device IDs. You don't need a whole new identification system. That is all.
The ACN MIDI ID identifies a MIDI cable, while Device ID is to identify a particular device on the cable.
It's necessary to offer the ACN MIDI ID because there are more things in MIDI than are dreamt of in your philosophy MIDI Show Control.
For example, a given MIDI cable can only transport one timecode. (MTC is Broadcast SysEx) So what do you do if you need more than one MTC on the network? - Eg two shows both using Timecode, or one show where Video and Lighting need different timecodes?
Even just within MSC, two or more shows that happen to need more than 16 MSC IDs in total could never coexist on one MIDI 'cable'.
Aside from all that, is it better to reprogram the (touring) show controller to change device IDs, or to use a 'different' MIDI cable?
Just like with DMX, you may have the choice to readdress a few devices or to run another DMX cable/sACN Universe. Which is better depends on the situation.
[edited by: Richard at 7:35 AM (GMT -6) on Sun, Feb 10 2013]
