MIDI

Ion supports MIDI Show Control (MSC) input and output. You can trigger cues, macros and set submaster levels using MSC.

From their web sites, it looks like both QLab and SFX support MSC.

Yes this is true. But this is not what I want to do. I just want to be able to send a MIDI GO, STOP, PAUSE . . . ect. Like I said the ION works very well in a time code situation were you have an event list that fires events bases on a clock that is ether external or internaly generated.

I am not sure what you want.

Ion will respond to a MIDI Show Control Go, Stop or Resume command.

DV

On the Ion -> Setup -> Show -> Show Control. Make sure that MSC Receive is enabled and that MSC Receive Channel is set to 0.

In Qlab, under the "Cues" Menu, you can select MSC (Command-8). Then fill in the appropriate information for the desired action and cue. Make sure your cables are going the right direction and you should be good to go.

I will work more on this. I have only been able to make the ION function with the event list. And recieve a go command at a given time form QLab. I have not been able to just send a globle GO MIDI comand and have the ION take it. Sorry for not being clear on what I need. I will work more on it.

We have had a lot of success running MIDI Show Control to trigger effects, bumps and other on the EOS. And with a little creativity we have had a lot of fun with it. It was a little tricky in the start getting all the commands right but with a good MIDI commander and so experimenting we manage to do what we wanted. So we have used to trigger a lot of effects on stage from pyro to take flash commands from a drum kit.

It is also worth checking what ACN MIDI Group/ID is set in the Setup Menu (where you enable/disable MSC) as well as what ACN MIDI Group/ID the ports are set to in the Shell. I don't thave a desk in front of me, but this is under Settings and then Ion, I believe.

-luke-

Could someone talk me through how to set up triggering Go on the Ion via Qlab.

Step by step if you wouldn't mind as I seem to have tried everything I've read on the forums and still can't seem to get it to work.

Many thanks.

Having just done this over the weekend for my wedding...  :)

First, you'll want to check this out:

http://figure53.com/qlab/documentation/msccue.php

You'll need to make sure that the MIDI device was patched.

The Ion console supports GO, STOP, RESUME, FIRE (for macros), and SET.

Set command format to Lighting.

The Device ID should be the MSC Receive Channel on Ion.

Use the Q Number and Q List fields -- we don't use Q Path.

On the Ion -

Make sure that in the Shell (Exit Ion -> Settings -> Local I/O) that the Midi In group matches the setting in the console (Primary -> Displays) -> Setup -> Show -> Show Control -> ACN Midi Rx ID.

While you're in Setup, also check that MSC Receive is enabled.

You'll have to build each Go that you'd need, but these are the things to check.   

Thanks Hans,

Turns out I was doing everything right but just hadn't updated the drivers for the USB-Midi Port.

There seems to be a slight delay when pressing Go on Qlab, is there something I can do to help with this or do I start looking towards Timecode and syncing? I'm new to Midi so all tips are very helpful.

I have successfully set up Qlab to trigger midi cues on the ion manually quite easily. Is it possible to do the reverse and link Qlab, via midi from the ion cue to trigger a specific sound cue, without knowing the time code?

Hans, Congratulations on your wedding!!

Yes. This page on QLab's site mentions control via MSC -- but it does require a Pro license.

http://figure53.com/qlab/documentation/preferences.php

There are a few approaches -- there's a bit of information below, let me know if any of it is unclear.  

First, when enabled, the Ion will transmit MSC commands based on its current actions. Any Go, Stop/Back, or Macro fire will be sent as a command.  For more granularity, you can specify a MIDI Cue List, which will filter outbound commands to when actions happen on that cue list only.  This is particularly useful when you don't want to have a go for every cue, but can create a "dummy" cue in an alternate cue list that is linked to your master list via an Execute command.  Remember that an Execute command can trigger a specific cue with another cue, or act on a list executing another list basis (matching cue numbers).

Second, with the release of 1.9.8 software, the console supports the transmission of specific MIDI strings.  This is on a cue-by-cue basis, and is set using the Execute function.  The syntax is as follows:

[Cue] x {Execute} {MIDI String} (your string here. For example:) F0 7F 01 02 01 01 00 01 F7 [Enter]

This sets Cue x to send a MIDI String, in this case, a Show Control message telling Lighting Device #1 to Go on Cue 1 in List 1.  As the QLab documentation specifies, it will respond to the Lighting command code, just as well as it will to the Sound category (more options are listed on the QLab page).  

The MIDI String interface lets you send it in decimal format as well (0-9 versus 0-F).  To specify it in this way, preface your string with a 'd'.

[Cue] x {Execute} {MIDI String} d (your string here. For example:)240 127 01 02 01 01 00 01 255 [Enter]

EDIT: Thanks Gern and all for the well wishes!