I'm trying to get ETC to receive the "GO"-message from QLab via MSC. In the diagnostics i can see the console is receiving the message "Raw MIDI: 7F 00" as I send the GO message from QLab, but cues don't fire. I'm not familiar with the hexadecimal midi codes and don't know if that's the correct message. What's the problem?
I'm using Qlab 3. I did the latest software update in Element (before the update the console didn't receive any messages from Qlab)
It doesn't look like it's receiving a full MSC packet (see this article: https://www.etcconnect.com/Support/Articles/Understanding-the-MSC-Commands-Eos-Family-Receives-and-Transmits.aspx)
I'd try setting the device ID to be non-zero. Also, clear the MIDI Cue List field, as it's only limiting the MSC the console responds to. In QLab, be sure you're sending MSC to Lighting-General (01).
Thank you for the quick answer! I'll try these tomorrow
Tried these, no luck. After reading the article I tried sending a custom SysEx message (F0 7F 01 02 01 01 F7) which sends the command GO to device ID 1, but the console still receives only F0 7F.
I tried midi voice message (Note On/Off, Program Change etc.) and when I send them, the console receives different midi messages. Curious!
if you have another USB-MIDI device (different make or model) or can borrow one i would try replacing the one you have. sometimes thos USB-MIDI things can only do the short MIDI stuff like notes, but fail when it comes the SysEx (which MSC essentially is) or Midi Time Code.
this might be it, because voice messages came through. thanks, i'll try another device or a regular midi cable, the theatre has an audio interface with midi output.