[QLab] Fwd: Running an ETC Ion with Qlab
The upshot is that if you send this SysEx string to an Ion with the
default Device ID of 1 it will GO the next cue in the default cue list:
F0 7F 01 02 01 01 F7
In a QLab SysEx cue you won't need the F0 or F7 - or, if you have the
appropriate license, you can use the handy MSC Cue to build this
string for you.
The below is the definitive list of steps you need to get an Ion to
talk to QLab and QLab to talk to an Ion.
Can someone put this on the wiki?
1) Connect hardware. With the USB interface the obvious lable applies
In->Out, Out->In
2) Make sure that the MIDI ports are enabled in the Local/IO section of
the settings menu outside the Ion software. Make a note of the ACN
channel numbers, these range from 1-32 and the Ion should default to 1.
3) Start the Ion software and go to the 'Show' settings. Go to the
remote settings then:
- Make sure the ACN MIDI Tx ID matches the ID configured in the
Local/IO section outside the software.
- Enable MSC Rx if you want control the desk from outside and MSC Tx if
you want to control something else from the desk.
- Configure the channel numbers for Rx and Tx. These actually configure
the MSC 'Device ID' and range from 0-126, 127 is the all-call ie
broadcast ID.
- If you want to control QLab from the Ion then make sure that the MIDI
Show control is enabled in the Remote section of the workspace
prefernces and that the device ID configured in QLab matches that
configured in the Ion.
- I *think* if you want GO's with cue numbers attached then you need to
enable MIDI String Tx as well otherwise the cue numbers don't get
attached to the MSC GO command but I'm not sure.
- Cue numbers in QLab must exactly match the Cure numbers in the Ion
that is to say 1 and 1.00 are *not* the same.
-p
--
Paul Gotch