Eos to Q-Lab Midi Trigger

I am trying to set-up a Midi network in order to trigger Audio's Q-Lab rig. Device settings are listed below. From the very few articles I have been able to find, I believe what I need to do is to set up a secondary cue list (Q1/ is generics, Q11/ is movers, Q16/ is midi) with cue numbers that match the audio cues (Q16/100 should trigger Audio Q 100). I believe I need the secondary cue list because the audio cues do not line up with the LX cues trigger cues (i.e. I need LX Q5 to trigger Audio Q100).

1st Problem: the box that audio has connected to the Show Control Gateway is not indicating Midi activity. (The gateway is online)

2nd Problem: is this the best way for me to be sending midi triggers?

3rd Problem: why is the top hit on the support website an article written in 1992?

Thanks!

AUDIO/Q-Lab

-listening to ch. 16

EOS Ti (2.2.0.9.0.66)

-MSC Transmit Channel: 16

-ACN Midi Tx ID: 1

-String Midi Tx: Enabled

-Midi Cue List: 16

Midi Show Control Gateway

-ACN SMPTE Rx ID: 1

-ACN Midi Rx ID: 1

-ACN Midi Tx ID: 16

Parents

0 ueliriegg over 10 years ago

in Setup > Show > ShowControl disable everything but MSC Transmit. you don't need midi strings. the ACN Midi Tx ID in setup needs to match the number in the gateway, that's how the midi is routed through the network. i don't think MSC transmit channel has anything to do with qlab listening to channel 16. if i'm wrong, you might want to try setting one of the two to 15. Midi spec starts counting at 0, so does Eos, but other programs start at 1, that's why sometimes you end up with an offset of 1.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 ueliriegg over 10 years ago

in Setup > Show > ShowControl disable everything but MSC Transmit. you don't need midi strings. the ACN Midi Tx ID in setup needs to match the number in the gateway, that's how the midi is routed through the network. i don't think MSC transmit channel has anything to do with qlab listening to channel 16. if i'm wrong, you might want to try setting one of the two to 15. Midi spec starts counting at 0, so does Eos, but other programs start at 1, that's why sometimes you end up with an offset of 1.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 thomash35 over 10 years ago in reply to ueliriegg

Thanks. I have now learned that there is a THIRD location where midi needs to be configured, the Local I/O. God forbid everything be in one place. Once I set the Group Tx to "1", I was able to at least get Midi to the Audio desk. We are now troubleshooting two different ways of sending the Midi trigger, either through the dedicated cue list as described above or through Exectue Midi Raw. The Audio guys have "recorded" the midi signals that they have received from the EOS and are working on decoding them so that we can figure out what commands I need to programme the EOS to send to Q-Lab.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ueliriegg over 10 years ago in reply to thomash35

local i/o only applies if you plug your midi cable at the back of your console (n/a for eos classic). that's why it's located in the shell and not the software itself.

to understand MSC messages i suggest reading this ETC support article: http://www.etcconnect.com/Support/Articles/Understanding-the-MSC-Commands-Eos-Family-Receives-and-Transmits.aspx

last but not least: if you prefer the execute method, you should consider MIDI Notes. if your audio guys can handle that, it's much less typing for you as they only use 3 times 2 digits, instead of at least 10 times 2 with MSC.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thomash35 over 10 years ago in reply to ueliriegg

thanks. i was only able to find this article on the old wiki and it was not as informative.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel