Midi out problems

The Eos family transmits MIDI Show Control (MSC) not MIDI Note. You may find this Wiki article useful.

I usually trigger the other way around, with QLab in control but the converse should work too. Make sure your MIDI I/O is patched in QLab.

The Wiki article says that Eos can trigger five different commands: Go cue, and Pause cue and more. How do I set which one I send?

And also I am used to setting which kind of device to trig: Light or sound. Is all this not nessesary to specify?

Hi Anders,

You don't chose what to send, Eos just sends those commands when the appropriate action happens on the desk for the cue list/s you specify in setup.

The configuration is done at the listening end, so you need to tell QLab to listen for say Cue 1/1 Go on Lighting and when that cue is run on the Eos it will be triggered in QLab.

There are literally just four things to set on Eos,

MSC Transmit: Enabled

MSC Transmit Channel: Match this this with who you are triggering

ACN MSC Tx ID: The ID of the transmitting gateway, or if you're doing it locally whatever you have set that to in the shell

MIDI Cue LIst: One ore more cue lists you wish to send.

Hope that helps

Dan

Hi Anders,

You don't chose what to send, Eos just sends those commands when the appropriate action happens on the desk for the cue list/s you specify in setup.

The configuration is done at the listening end, so you need to tell QLab to listen for say Cue 1/1 Go on Lighting and when that cue is run on the Eos it will be triggered in QLab.

There are literally just four things to set on Eos,

MSC Transmit: Enabled

MSC Transmit Channel: Match this this with who you are triggering

ACN MSC Tx ID: The ID of the transmitting gateway, or if you're doing it locally whatever you have set that to in the shell

MIDI Cue LIst: One ore more cue lists you wish to send.

Hope that helps

Dan