Search Results for 'qu midi protocol'

[AndreasModerator]

Not sure which MIDI implementation you’ve read, but from the Qu MIDI Protocol given by A&H all mutes are controlled via Note ON messages (Page 4, Mute Control) not CC. So sending a 9N 50 7F should turn mute on and 9N 50 3F (all hex) turn off mute group 1. N denotes the system channel of the Qu, not sure if Ableton is 0-based (0..15) or 1 based (1..16).
Maybe you can just record MIDI from the Qu and perform the action you want to automate, so you’ll get exactly the events you want to send.

Hello to all. Just purchased a QU-16 and have been real happy with the purchase. My band uses Ableton Live to play some backing tracks to supplement our sound live. Ableton also has some MIDI automation such as lighting programming along with vocal and guitar processing in time with the backing track. So I am somewhat comfortable with MIDI programming.

I would like to be able to control the QU-16 in the same manner. One instance would be to mute the FX mute group that I have setup when a song ends in Ableton and unmute it at the start of a song. I might want to consider assigning other FX and turning those on and off at appropriate times.

I have read the MIDI protocol documentation. I’ve assigned a MIDI track in Ableton to the QU but for some reason I can’t get a response on the desk. Based on the MIDI Protocol document, Mute Groups 1 to 4 = 50 to 53. I was assuming “50 to 53” is Hex 80 to 83. So by creating a MIDI clip in Ableton live and drawing automation on CC 80 would mute and unmute mute group 1, so I thought. I did assign the MIDI channel on the QU and within Ableton. Still, no such luck.

Hopefully my explanation has been enough. I am connecting the computer to the QU via USB. I have been able to stream audio successfully.

Thanks for any and all suggestions.

Shane

[AndreasModerator]

According to Qu MIDI Implementation (Page 8) scene changes are invoked using Program Change not Note messages.
So with Qu configured on Channel 0, the required sequence is something like (all hex): B0 00 00 B0 20 00 C0 <nn>
where <nn> is the scene to recall.
And beware that some MIDI numbers are 1-based and others are 0-based.

[Nicola A&HKeymaster]

Hi Larry,
Sorry no one got back to you on this one before. As Jeff said in another thread, if you require technical support you should contact our local distributor for assistance or submit a ticket to our UK Support team here: https://www.allen-heath.com/support/productsupport/tech-support-2/

Looking at the MIDI protocol though, channel assignment to a mix is not supported. I can only see channel assignment to the Main mix. However you can control the send level so you could set the send to -inf or 0dB if that’s any good for your application? This would be:
B0 63 20 B0 62 2E B0 06 00 (sets ch 1 send to Aux1 to -inf)
B0 63 20 B0 62 2E B0 06 6B (sets ch 1 send to Aux1 to 0dB)

I’m using B0 since the default MIDI ch on iLive is 1 (from memory).
Also note that 2E corresponds to Aux1 only when using the FOH-LRSub Template Show. The Snd identifier in the MIDI protocol depends on the bus configuration so in your current Show 2E might point to a Group, or a Matrix etc. – see the MIDI protocol for details.

Hope this helps.

[AndreasModerator]

Not sure if Audition allows sending/receiving of control information at all, at least I didn’t find anything about it. Ableton live should be customizable enough to directly communicate with the Qu midi protocol. It just will take some time to setup everything manually.

[AndreasModerator]

sorry, I need to add some minor clarification regarding driver requirement on windows. Drivers are reqired only since Microsoft refuses to support AudioClass2.0 on their Windows platform for a decade now so any hardware developer, who wants to stream more than a few audio channels through USB, needs to deliver drivers. This is an additional work to do for developers like A&H which also need to follow any system update to ensure their drivers still work well. Apple (and several *nix based platforms) provides AudioClass2.0 support, so devices like the Qu work nice without drivers.
DAW control isn’t much magic as well, its just a wrapper from the HUI protocol to the (official) Qu MIDI implementation. Any configurable DAW can nicely be controlled from the Qu (there already are various threads here).
And, finally, the required CPU speed for a DAW only depends on the required audio processing. For recording-only a pretty low-end machine should work well. I also prefer to use a slim application (Reaper in my case, works well on both Mac and PC) for recording and move tracks afterwards into my DAW (on a more advanced machine) for processing.

[AndreasModerator]

Ports/Protocols are Layer 3, VLANs (normally) operate on Layer 2 of the OSI model. To integrate the Qu into a VLAN you’ll need the mac address of your unit resp. the switch port where it is connected to your infrastructure, and setup the switch accordingly.
To finally route the traffic between VLANs you need the ports, correct.
Thought there is a paper available describing the Qu MIDI Protocol which also specifies the ports to use (TCP port 51325). But that’s V1.5 and not focusing the QuPad/QuYou protocol, which are not documented at all. So maybe you need to sniff…

Okay… Still working on assigning an input to a stereo aux via the PL6. Yes, I go through a lot of duct tape to keep my head from exploding…

I know that I can assign a button on a PL6 to send a custom MIDI command. If I use the iLive MIDI protocols, can I send a command via the PL6 that will assign an input to a stereo aux? Would this example work?

(custom midi command entered in PL6 button assign text box in editor)

B1,63,20,B1,62,2E,B1,06,7F

where B1,63,20 assigns channel 1 to B1,62,2E Aux 1 and B1,06,7F turns it on

Any help/suggestions appreciated and welcomed!!

[Nicola A&HKeymaster]

Yes, please read the MIDI specs for details: https://www.allen-heath.com/media/Qu-MIDI-Protocol-V1.5.pdf

[Anonymous]

I and I’m sure many others’ buy the QU range of mixers for live sound 1stly
However A & H do market the QU for “in the studio” as well.
So customers like myself will always want to get as much out of this kind of *controller* as possible.
I mean really, they are a computer underneith, that well designed steel framed structure.
In custom layer mode you can off course assign the faders to various controls which I have done both live and in studio environment.
I suspect the iLive and GLD are the same?
Going back to that custom layer mode where you can assign the faders to midi to control faders ITB (in the box) it would be an added feature in my case to be able to assign the master fader as a master fader within the software on the Mac.
Interestingly I notice that iPad which is midi driven wireless protocol? the master fader is bi- directional. ( I might be incorrect about the midi wireless protocol and will accept being corrected)
So I am assuming that the master fader is a midi driven fader?
Along with Pan controls?

On saying all of this, in a studio environment, I personally use the mouse ‘all of the time’
and that’s including on my GSR24M.
I don’t think we will ever get away from using a mouse-less digital desk system in the studio scenario.
And any way to help bring the best out of the QU I am all for.
Please remember this is just discussion.
cheers

I’m a 2 week veteran of the Qu-16, and I’ve been loving every minute of it! I’ve reached the point where I’ve got all the basics covered, and I’ve got two gigs under my belt that both resulted in great sound. Now I’m ready to reach for some bells & whistles. 🙂

I have an iPad Air that is successfully running the QuPad app. The communication is taking place wirelessly with a Linksys router in between the two hardware devices. I’ve got another iPad app called SetListMaker that can theoretically send MIDI commands, and I’d like to use that app to mute/unmute some vocal effects depending on the current song selection (the FX1 and FX2 returns, specifically).

I’ve figured out the MIDI commands I need to send using the Qu16’s MIDI protocol document, and I’ve got them setup in SetListMaker. But for the life of me, I can’t get the Qu16 to react to the commands. With no serial cable to sniff on, I have no idea if the commands are even making it to the Qu16…

So I guess I’ll start with the most basic question I have… should I be able to use a secondary app to wirelessly send MIDI commands to the Qu16 (through the Ethernet “Network” port) while simultaneously running QuPad on the same iPad? I’ve read some limitations regarding the number of separate QuPad apps that can control the board at once, so I’m wondering if I’m running into some sort of obstacle like that…

[AndreasModerator]

You probably should ensure that the midi connection is only used for the DAW control and that logic does not send anything else to that port.
Channel Mutes, for example, are controlled via Note ON messages. When Logic sends out notes while selecting objects, it is likely that some channels get muted…
Qu MIDI Protocol

[philt80Participant]

Nope.. I’ve been searching everywhere…

I’ve been posting this everywhere.. I’m using Studio one by presonus which I’m just about ready to give up on….

I need some help with device control on my new QU24 by allen and heath. I’ve set up a new keyboard external device and so far (the easy part) I’ve got my faders moving. I’m looking to get things like pan, gates, eq, mutes etc working controlled via MIDI. On learn mode when I move the pan knob I get this in the XML file….
-<Control title=”Control25″ options=”receive public” type=”knob” name=”controlb0063″>
<MidiMessage address=”#63″ channel=”0″ status=”#B0″/>
</Control>
-<Control title=”Control26″ options=”receive public” type=”knob” name=”controlb0062″>
<MidiMessage address=”#62″ channel=”0″ status=”#B0″/>
</Control>
-<Control title=”Control27″ options=”receive public” type=”knob” name=”controlb0006″>
<MidiMessage address=”#6″ channel=”0″ status=”#B0″/>
</Control>
-<Control title=”Control28″ options=”receive public” type=”knob” name=”controlb0026″>
<MidiMessage address=”#26″ channel=”0″ status=”#B0″/>

THIS makes since considering A&H midi protocol documents say this…
(NRPN MSB) (NRPN LSB) (Data MSB) (Data LSB)
BN, 63, CH, BN, 62, ID, BN, 06, VA BN, 26, VX

Pan
(NRPN MSB) BN, 63, CH, (NRPN LSB) BN, 62, 16, (Data MSB) BN, 06, VA (Data LSB) BN, 26, VX
Where VA Full Left = 00 to Centre = 25 to Full Right = 4A
VX 04 , 05, 06, 07 = Mix 5-6, 7-8, 9-10, LR
VX 0C, 0D = MTX1-2, 3-4 (not Qu-16)

In fact any knob other than the faders I use seem to use these 4 variables.. just different numbers..I can’t find any documentation on this and no support is coming from the forums..

Can anyone give some hints as to how I can rewrite the xml file to only read the pan knob and not all 4 variables? I’m no programmer! Hopefully I can compile an xml file that can be distributed for other A&H QU users..

— Nobody has a clue that I can find..

I’ve got DAW control up and running Mackie Control Protocol.
The instructions for DAW control mentions the left square on the bottom right of the pop-up should flicker when I move a fader…the square is flickering.
I assume the right square flickers if the DAW program is sending data…don’t know, but there’s no flicker.
My Qu-24 is not moving faders within the DAW neither is the DAW moving faders on the Qu…
Qu is set up with all faders to MIDI on Custom Layer, Midi Channel 1, MIDI DAW Control Channel set to channel 2.
MIDI monitor within Studio One is not seeing any data.
I can’t figure out the disconnect.
The Qu is getting audio from the DAW no problem.
I’m running latest OS on 2013 iMac.
Anyone guide me through this?
Thanks!

[ClardySoundParticipant]

You should be able to add additional mackie controls in cubase. I added 3 in my case for the qu24. Assign mackie control 1 to DAW control midi 4, then mackie control 2 to DAW control midi 3, mackie control 3 to DAW control midi 2, and so on for the last. I don’t understand why this cant be simpler when opening cubase, and it automatically set midi in/outs automatically based on the template. You have to follow a very specific protocol for new projects to work correctly. I have also found that if the project is setup wrong, then the QU faders will only control the input channels, and not the actual tracks that are recorded.