The protocol used for Qu-You is significantly different from the public MIDI protocol. It is subject to continual rapid change and improvement as the code develops. I’m afraid that for this reason we do not intend to publish a spec document.
We will continue to support the public MIDI code and its documentation.
An updated MIDI protocol document would be perfect. To get a netowrk dump I would need an iPhone which is not the case 🙁 All our band members use Android phones (as the majority of smartphone users do). That’s why I wanted to have a look at the protocol to see if I can do something by myself until A&H decides to support the major mobile platform as many forum members here are requesting (if this is ever the case).
It would be pretty consequent to just update the MIDI protocol document to V1.6 including Qu-You specs. Correct, Nicola? 😉
I guess all required information can be found in the MIDI protocol documentation for the Qu…
…lacking knowledge about Qu-You connection, maybe UDP (guessing…)…
“DAW Control” is (IMO) an ambiguously named program developed by A&H that takes Midi messages sent by the console over USB and translates them to Mackie Control/HUI protocol (and takes the Mackie Control/HUI commands sent from the DAW and translates them back to Midi.) This allows the Qu to control/be controlled by DAWs that use Mackie Control/HUI instead of Midi. The caveat is that this “DAW Control” (Midi translation) program is only available on OSX, not Windows.
Bottom line:
Bi-directional multitrack audio streaming over USB: Windows and OSX
“Controlling a DAW” via Midi over USB: Windows and OSX
“Controlling a DAW” that can’t use midi but can use Mackie Control/HUI: OSX only via the “DAW Control” program. However if the DAW is running on Windows it can still stream audio to/from the Qu, you just can’t use the Qu’s faders/buttons to control the DAW, you have to use your kb+m.
AFAIK, Cubase uses midi, so if installed on Windows or OSX it can be controlled by/can control the Qu (provided long as the Qu is running a recent firmware version and you set it up correctly.)
HTH
Hi,
I’m an user of GLD80 but a lot of musicians which i’m working with use android tablet in stage. They have already ask for a android version of iMix but you have already answer that the android platform may have a lot of different device, which complexify the developement.
All my musicians have samsung 10.1 tablet, so I’m developping an custom iMix equivalent for theses devices.
I’ve looked at you midi over TCP protocol described in your documentation and I can correctly set some data (like aux fader) from an android device. I can also receive midi event, to update the android device.
It’s missing some features in midi over TCP functionnalities, features presents in gld editor (specially initial state of faders and assignment of aux). So to understand, I’ve captured the network traffic between GLD80 and the computer which run GLD editor. I can see that the used port is different (51321) and that the protocol seems to be close from this described in midi over TCP.
Before doing reverse engineering of this port, in order to develop my iMix equivalent application, I ask you if any documentation are available about this protocol.
Could you indicate me, where I can find the documentation about that ?
Note: As thanks, I’m free and OK to give you the development (as is when it will be finished) or to publish on github (or any other platform) “as is” if others customers of GLD 80 are interested in.
Best regards,
Ludovic SMADJA
Hi Jeff,
You can use a Xone:K1 as a controller for iLive Editor (not GLD), and map the faders to any Input, Mix or DCA. As you said this relies on Editor running on a computer (and the correct Mix being active in Editor) which is not ideal in fixed installs.
With an iLive I would definitely recommend a PL remote controller or instead: PL6 or PL10 if you need multiple faders / knobs or a simple PL4 for in-room level control / source selection.
GLD Editor doesn’t support MIDI control.
MIDI control of Editor is not to be confused with the iLive / GLD MIDI and TCP protocols, which connect to the mixer directly and don’t have anything to do with Editor. You can use these protocols to program third party controllers such as Crestron or AMX (with some luck you might be able to program a generic MIDI controller like the BCF2000 to send / receive the required NRPN messages but I haven’t tried this).
Hope this helps.
here an answer from A&H-England.
That makes things more tricky, the QU MIDI is NRPN messages which is more difficult to configure. The DAW control app for Mac translates the NRPN messages to HUI/Mackie Control but we don’t offer this level of support for Windows based systems.
If Cubase doesn’t support NRPN then something like Bomes to translate in to a more friendly protocol might be an option but it’s not something we offer directly unfortunately.
You say guys there is MIDI over USB for Windows computers?
To be precise I need DAW Control not for Sequoia, but RME TotalMix, say Mackie Control protocol.
I have no time to make DIY MIDI with translating anything, and endless debugging it.
I’m 59 too Dhak, and still learning hard, but prefer to spend time on music score during recording sessions, or work on recorded music, than on troubles connecting two digital boxes with really simple MIDI protocol.
Have you friends any good experience with MIDI on Qu on Windows, and possibility to work in Mackie Control mode?
Regards!
Tomek
If you decide give MIDI a shot, this document might be useful https://www.allen-heath.com/media/Qu-MIDI-Protocol-V1.5.pdf
Hi Tom,
Did you have a look at the Qu MIDI protocol?
This should give you all the information you need.
should be possible with MIDI
The DAW Control driver allows a Qu mixer to control a DAW using popular HUI or Mackie Control protocols. It can be used as an alternative to, or on top of, the set of standard MIDI messages.
so standard MIDI should be the way on Windows at this time… I guess it’s a mess to configure it 🙁
EuCon Protocol could be a solution…
The “special” driver still has to translate the control data to MIDI, HUI, Mackie Control or EuCon since the software only supports these…
Qu mixers talk MIDI over Ethernet by default…
Nicola, does the Qu now deal with multiple TCP/IP connections talking MIDI, or does the Qu-You use some other means of communication?
I’m afraid Qu is still limited to 1 MIDI TCP connection at a time, as detailed in the Release Notes. Qu-You uses an ad-hoc lightweight protocol.
According to the A&H Qu Mixer MIDI Protocol V1.5
Active Sensing
Qu supports MIDI Active Sensing over its TCP/IP Ethernet connection to detect connection status. Qu will send an initial Active Sense byte (FE) once an Ethernet connection is established, and then once every 300ms or so during any period of inactivity.
In other words, the mixer needs to see a message from the connected device every 1/3 of a second or it will disconnect.
When you switch apps, QuPad is inactive and cannot send anything to the mixer. So, in a word, no. There is nothing you can do.
You could buy another iPad if you have the dough. That might be the easiest solution.
