• Date
    soph0nax
  • Date
  • Replies 4 replies
  • Subscribers 185 subscribers
  • Views 11039 views
  • Users 0 members are here

MSC Transmit from ION

Hey Everyone,

I'm primarily and audio guy, but had some down time in the theatre today so I thought I'd try and tackle the ION and the EOS. I am currently sitting in my small space trying to link together a QLab Audio Computer and an ION desk. I currently have QLab taking control over the ION - I have run a few shows like this so sending to the ION is nothing new to me!

My current problem is trying to get the ION to send commands to QLab. I understand that you can send timecode, but I want to send straight up "GO" and "STOP" events to QLab from the ION. I have read and re-read the manual and can't find anything directing me to transmit a GO command from the ION. 

My Equipment:

ETC ION

Mac Pro 10.4 running QLab 2.2.8

Edirol by Roland UM-3ex Midi Interface

------

The computer is transmitting on Channel 1, Receiving on Channel 2. The Ion has MSC Transmit and Receive enabled and is receiving on Channel 1 and Sending on Channel 2. QLab has a device ID of 5. 

-----

Anyone have any tips on sending MSC commands like GO and STOP from the ION?

 

My next task is to go into the big theatre and link 10 faders from my Yamaha LS9-32 soundboard into the 10 motorized faders on the ETC EOS...anyone have any pointers for that next! :P

Parents

  • Hey soph0nax,

    The Eos/Ion family will send Midi Show Control, but it will only send out what it is doing.

    EDIT: (i.e., when you press "GO", it will send out that action across the network, specifying that it (Device ID) just hit GO for cue 1).

    It seems to be fairly simple to have QLab or any other MSC capable program listen for these events, instead of having the Ion send out particular messages. It was also suggested that you could create a phantom cuelist specifically for QLab, and program it to follow MSC GO instructions from this list.

    About the Eos and the LS9-32 -- I've never used that sound console, so I am not sure on its Midi implementation, or the best way to go about that. I would think that it may revolve around the Set command in MSC, as it is capable of reporting level information. 

    Hans



    [edited by: Hans.Hinrichsen at 8:58 AM (GMT -6) on Mon, Oct 18 2010]
  • in reply to Hans.Hinrichsen

    Could you direct me on how to output MSC commands at all? The manual for the Ion offers no such guidance and after poking around the Ion for several hours nothing has proven effective. I don't want QLab to "go" every time a light cue is fired, the phantom qlist seems to be the way to go, but I still have no idea how anything would output from the Ion without specifying a Device ID to send to.

  • in reply to soph0nax

    Soph0nax,

    The Ion will only send commands based on what it is doing, and it does this by default when MSC is enabled.   The Device ID is the Ion's MSC Transmit ID.  

    Keep in mind that the Go command contains a string about the cue list and number that was just fired, not just a plain "GO" command.  We just confirmed this in the Tech Support lab via MIDI packet sniffing.

    When we hit the GO button for Cue 1/1, we saw the command : F0 7F 01 02 01 01 31 00 31 F7, which, if you follow the link below, means that the Ion send the command GO to Device 1 on Cue 1/1. 

    David Hilton wrote a fantastic article in the wiki about MSC and the way that the Eos family responds to it -- check it out, and please keep asking more questions if you have any.  

    http://community.etcconnect.com/wikis/products/understanding-the-msc-commands-eos-family-receives-transmits.aspx

    Hans

     

     

     

     

Reply Children
Related

www.etcconnect.com