ukdeveloper Posted November 29, 2012 Posted November 29, 2012 I have a Macbook Pro running Qlab software. I also have an LS9 mixer Qlab midi controlled by USBLS9 midi controlled by regular midiIs there a way to control Scene Advance on the LS9 (or any other midi function) using the Akai MPD18 controller AS WELL AS using the Akai to control Qlab? If I purchased a usb to midi interface that (I guess) would get me a midi signal to the LS9 but how would I control which route the midi signal from the Akai would go to? (either the midi interface, or USB straight to the mac) Sorry if this sounds a little convoluted, but im pretty new to the midi thang UKD.
dbuckley Posted November 29, 2012 Posted November 29, 2012 If this were Windows I'd say download MIDI Ox and use it to route the MPD18 to both Qlab and out through a MIDI interface. So, fanbois, whats the Mac equivalent of MIDI Ox?
neilalexrose Posted November 29, 2012 Posted November 29, 2012 So, fanbois, whats the Mac equivalent of MIDI Ox? Midi Patchbay To the OP. I don't think there is a midi message that will step through the scenes on the LS9, and I suspect the Akai will only spit out Midi note messages and/or midi CC messages. (I am willing to be corrected on these points, but from what I remember of Yamaha midi protocal, note on/off messages turn things on or off, and CC messages will move faders. Changing scenes/snapshots requires program change messages.) The way this setup would normally be done is to assign unique program change messages to each of the snapshots/scenes on the LS9, and then fire the appropriate program change message from Qlab to get the LS9 into the right scene, eg. program change 1 = scene 1 . For this you would need a usb -> midi device to get the midi out from Qlab and into the LS9. Then you could use the pads on the Akai to send out a midi note/cc message that triggers the 'go' command in Qlab, advancing down the Qlab cue list, triggering SFX and Midi messages. You would need a Qlab pro midi license, or Pro bundle license to use midi functionality. Worth mentioning that the LS9 will need to be assigned to a midi channel, 1 - 16 in the setup menu, and the program changes will need to be on the corresponding midi channel. And also from memory, some digital desks are one number out when it comes to program changes, but I can't remember if it applies to the LS9. (E.g. program change 2 recalls scene 3 on the digital desk.) Thinking about it, you could probably use midi show control commands from Qlab to advance the scene recall on the LS9, 'recall +' and 'recall -' , but I've not really used much midi show control to be able to comment further. If you wanted 2 separate pads on the Akai to control SFX and scene recall, you could create 2 cue lists in Qlab, and assign a midi trigger (from the Akai) to each list. Eg, list one was SFX, triggered by one pad sending out a note on message, and list 2 could be a list of program changes (or midi show control commands), triggered by the 2nd pad sending out a CC message. Any help? Neil
ukdeveloper Posted November 30, 2012 Author Posted November 30, 2012 So, fanbois, whats the Mac equivalent of MIDI Ox? Midi Patchbay To the OP. I don't think there is a midi message that will step through the scenes on the LS9, and I suspect the Akai will only spit out Midi note messages and/or midi CC messages. (I am willing to be corrected on these points, but from what I remember of Yamaha midi protocal, note on/off messages turn things on or off, and CC messages will move faders. Changing scenes/snapshots requires program change messages.) The way this setup would normally be done is to assign unique program change messages to each of the snapshots/scenes on the LS9, and then fire the appropriate program change message from Qlab to get the LS9 into the right scene, eg. program change 1 = scene 1 . For this you would need a usb -> midi device to get the midi out from Qlab and into the LS9. Then you could use the pads on the Akai to send out a midi note/cc message that triggers the 'go' command in Qlab, advancing down the Qlab cue list, triggering SFX and Midi messages. You would need a Qlab pro midi license, or Pro bundle license to use midi functionality. Worth mentioning that the LS9 will need to be assigned to a midi channel, 1 - 16 in the setup menu, and the program changes will need to be on the corresponding midi channel. And also from memory, some digital desks are one number out when it comes to program changes, but I can't remember if it applies to the LS9. (E.g. program change 2 recalls scene 3 on the digital desk.) Thinking about it, you could probably use midi show control commands from Qlab to advance the scene recall on the LS9, 'recall +' and 'recall -' , but I've not really used much midi show control to be able to comment further. If you wanted 2 separate pads on the Akai to control SFX and scene recall, you could create 2 cue lists in Qlab, and assign a midi trigger (from the Akai) to each list. Eg, list one was SFX, triggered by one pad sending out a note on message, and list 2 could be a list of program changes (or midi show control commands), triggered by the 2nd pad sending out a CC message. Any help? Neil Great help! Thanks. The way this setup would normally be done is to assign unique program change messages to each of the snapshots/scenes on the LS9, and then fire the appropriate program change message from Qlab to get the LS9 into the right scene, eg. program change 1 = scene 1 . For this you would need a usb -> midi device to get the midi out from Qlab and into the LS9. Then you could use the pads on the Akai to send out a midi note/cc message that triggers the 'go' command in Qlab, advancing down the Qlab cue list, triggering SFX and Midi messages. You would need a Qlab pro midi license, or Pro bundle license to use midi functionality. Just to mention, there are 127 scene/snapshot changes in this show. Would that make a difference? UKD
neilalexrose Posted November 30, 2012 Posted November 30, 2012 Just to mention, there are 127 scene/snapshot changes in this show. Would that make a difference? Just checked, you can send program change message 0 - 127. So you're just inside the limit! Neil
Recommended Posts
Archived
This topic is now archived and is closed to further replies.