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

with MSC you don't have to specify what you're sending, because the console transmits what you're doing. so you don't execute the command but it is executed by the console itself. i have a show where an Element triggers Qlab. we just used the same cue numbers in qlab like we did in the Element, so if Qlab has a cue with the same number that the Element is reporting, then it's triggered.

 you have to make sure, that the numbers in the shell setting for MIDI TX and Rx Group in the Shell match the numbers you put into the Show Control Settings of Setup. try using the numbers from the shell in the setup fields called ACN Tx ID (i think). i know, it's counter intuitive to use a setting called ACN when your're outputting from your direct midi outs, but give it a go. and make sure, that the two numbers in the shell are different from each other...

ps: you could also give your first try a go and send MIDI Notes. you would do that with Cue x Executed MIDI_Raw D 144 65 127, or something like that. if you want to try that, tell me what exactly you're trying to send (On/off, channel, note, octave, velocity) and i will give you the number sequence.

but as dan wrote before, with MSC it would be much more straight forward...

I have found a setting in Local I/O called Show control gateway: Midi Rx group id: 1 and MIDI Tx Group ID 2. And in Show settings I have set ACN MIDI Rx ID: 1 and ACN MDI Tx ID: 2.

But it still does not work.

What about The MIDI cue list setting (in show control). Does that specify what cuelist that will transmit MSC? 

And are there any of the other settings that has to be enabled or disabled? Eg Analog inputs, String MIDI TX 

You don't need to put anything in the [MIDI Cue List] box - if it is empty, it will send the appropriate MSC commands for all cue lists.

I'll ask a silly question! You do have two MIDI cables, right? One in from the QLab Mac and one out to it? I only ask because you said the cable is good...

I know of a few good MIDI sniffer programs for PC, but none for Mac - but there are bound to be some good ones.

Luke

We remembered to move the cable from in to out and back(Unfortunately..... I'm up for any silly solution)

Maybe I will try to find a MIDI sniffer.

IN QLab you have to set it to Listen to MSC.  I am not at QLab right now but i believe you find it by clicking the light switch settings icon.  We trigger it all the time again it is MSC not midi note.  

Qlab is set to listen to MSC> Device ID 1 and the GIO tranmit on channel 1.

I am wondering about the cue numbering: I send cue 1 from cuelist one what Qlab number will be triggered? cue 1 or 1.1 or? Or schould the name of the Qlab cuelist be 1? 

Anders Kjems

Qlab is set to listen to MSC> Device ID 1 and the GIO tranmit on channel 1.

I am wondering about the cue numbering: I send cue 1 from cuelist one what Qlab number will be triggered? cue 1 or 1.1 or? Or schould the name of the Qlab cuelist be 1? 

Anders Kjems

I just remembered that Figure53 have a bit about how to set up this exact thing:

http://wiki.figure53.com/QLab+Hints+and+Tips#x-Controlling%20QLab%20using%20MSC%20from%20an%20ETC%20ION

You might need to have QLab set to receive "Cue 1.00" - sorry, I don't have Mac here to test it.

Yes I have read the article unfortunately it does not tell me how to name the cues i either Eos or Qlab so thats just one more variable that has to be tested for each new idea :(

It would be so nice to have a window that tells you exactly what is being transmitted thru the MIDI out port (Like the MA2 has) then I would be able to find out if the problem is at my end. And the wiki article on "understanding the MSC commands...." would be more helpfull because you would be able to see what cue number and command you are actually sending and if you are sending anything at all.

And another small question: I seems weird that there is setup for Midi Rx/Tx Group ID in both Local I/O and in show control with in the software? Why is that so?

The Eos Diagnostics display shows what Eos is sending out via MIDI.

it triigers the same number as eos fires.  If you want cue 2 to fire QLab then Cue 2 is the number in QLab.

if you want to fire 1.1 the eos and QLab need to have that number to trigger.  Contact me offline if you like and i can help you trough it.  

The Diagnostics windows helps!

I can see now that I am not sending out any MIDI when I press GO. When I press stop I send out a STOP RAW command. I don´t know what I have to do to fix that.

Anders Kjems