Triggering Ques in Qlab from dlive via midi

dLive dLive Troubleshooting
1

Hi. I have this problem.

I have a show where I am triggering scenes on the Dlive from qlab via Midi. With all the correct settings this works great! I set the A&H midi control to surface midi, make a new que list in scenes manger, set it to surface midi and use the “surface ID recall” dialog to set corresponding IDs to the Qlab program change number. So far so good.

At some point I need to reverse the triggering, so instead of triggering the scenes on Dlive from Qlab, I need to trigger ques in Qlab from the Dlive console. Should be pretty simple. Just set the correct settings in the “triggers” section in qlab and when qlab receives the correct midi message it plays the que. I know for a fact that this is working because I have done it several times on other consoles, but then there has been a physical midi 5 pin connection between the console and the computer (through a sound card or whatever) But this is just not working with the A&H Midi control (MIDI over network) I actually get it to trigger sometimes, but just randomly??

This is very frustrating! Am I doing something the wrong way in the setup, or is it just a faulty system thing? Would be very helpful if someone from A&H could answer so I won’t have to spend more time troubleshooting this if its not working…

Hope for some answers in this forum!

Dlive cti1500
cdm48/sometimes dm0
Macbook m1
QLab 5.4.8

1 Like
2

A nice way to achieve this would be by using the Custom MIDI option for each scene. This allows you to send a custom MIDI message (displayed in Hex) on recall of the scene. The benefit being that instead of being linked to the scene recall program change message, you can instead send note on/off or CC messages and do things like have the same message (same QLab trigger) for multiple scenes, or move scenes around without needing to reprogram QLab if you needed to.
As a basic example, you could use a note on message like 90 3C 60, then change the 3C to change the note for each scene.
Hope this helps, Keith.

3

Thank you for your response, Keith! This solution works perfectly. For others working on similar tasks, I would like to point out a couple of important checkpoints to make it work. First, note that Qlab doesn’t move the cursor to the active group cue when Qlab is triggered via network MIDI. To see which cue is being triggered, you need to include a Goto cue in the group, and then you’ll see the cues being triggered, as well as the cursor moving to that cue. Also, check that the A&H MIDI control is set to surface MIDI when using this method. Thanks again for your response :slight_smile: All the best!