Qu24 and daw control (Sonar/Cakewalk)

[Dirk PHC]

Dear all,
First of all my current setup: QU24 with WIN10 PC and DAW Sonar / Cakewalk. I also use a Ipad. In my studio, monitoring thru Dynaudio / SPL controller. Several analog and digital synths, guitars, bas, accoustic, etc
Recently I replaced my “old” Tascam DM3200 (fully integrated with my daw), with the QU24.

The QU24 works great, including usb/audio streaming from and to my PC/DAW.
But I do not get dawcontrol working (ie, flying faders, transport controls), I have installed all latest versions of driver, midicontrol. Read and followed the help/instructions….

My question: is this daw control function actually support on a WIN PC ?. Any help appreciated

[Dirk PHC]

It works 👍
All working now, after reading the A&H midicontrol instructions again (and now thoroughly 😉)

The “midi control” app from Allen&Heath (download from the A&H site) translates the midi data sent from the QU to Mackie control midi data as input for the DAW.
For this the app generates 4 virtual midi devices (to support 4 times 8 faders), ie daw control 1, daw control 2, daw control 3, and daw control 4.

The “real” Qu midi devices: QU-24 midi in and QU-midi out get the non-translated data.

Creating a “control surface” in my daw, using the virtual midi devices makes it all happen 👍

It is actually well described in the document, but I know that more people did not get it working correct

[kahollm]

Dirk PHC: Can you provided detailed description of how you got your Qu to hook up with Cakewalk as a DAW?

I’ve been messing with this for a while now and i can’t seem to get it….

Thanks,
Keith

[Dirk PHC]

Did you download the AH midi control “app” and run this app everytime you startup your PC ?

[kahollm]

Thank you Dirk for responding. Yes, i am runnning the AH midi control app 2.0. I have it set up with Mixer: Qu Series, MIDI Channel: 2, Protocol: Mackie Control, MIDI Ports Input Port: Qu-24 MIDI In, Output Port: Qu-24 MIDI Out

Last night when moving the Qu’s faders the left box would light up indicating signal. Havent gotten the right one to light up. Now for whatever reason I can get either to light???

Again, I know it will be time consuming but some simple step by step instructions would be great/appreciated.
Thanks,
Keith

[Dirk PHC]

I believe it is all ready described in my earlier post …

—————
The “midi control” app from Allen&Heath (download from the A&H site) translates the midi data sent from the QU to Mackie control midi data as input for the DAW.
For this the app generates 4 virtual midi devices (to support 4 times 8 faders), ie daw control 1, daw control 2, daw control 3, and daw control 4.

The “real” Qu midi devices: QU-24 midi in and QU-midi out get the non-translated data.

Creating a “control surface” in my daw, using the virtual midi devices makes it all happen 👍

It is actually well described in the document, but I know that more people did not get it working correct

——————-

So in Sonar you create a control service with the virtual midi devices:
QU16:
– daw control 1 for faders 1-8
– daw control 2 for faders 9-16

QU24: add
– daw control 3 for faders 17-24

QU32: add
– daw control 4 for faders 25-32

[Dirk PHC]

Did you read the “midi control help” file ?
I assume you know how to create a “control surfce” in Sonar ?

[kahollm]

Thanks Dirk for your responses.
Yes – I’ve read the midi control help.
I have set up three DAW Control MIDI Surfaces and the software shows them with three different colors.
Now when moving a Qu fader my A&H MIDI Control software window flashes the left box.
Now when moving the Cakewalk fader the A&H MIDI Control software window flashes the right box.
THings are talking BUT is still don’t have one driving the other???

[Dirk PHC]

Connection between cakewalk and your QU seems established. Did you configure “control surface” in Cakewalk …
At the moment, I have no access to my “QU 24 setup”. Might be able to check tonight, will make few pictures of my setup and share with you

[Dirk PHC]

Ok, I am now on a friend’s system. He has a behringer X touch one (universal control surface).

Naming is different off course, but principle is the same.

In cakewalk edit/preference you will need to do following:
Go to midi devices, and make sure to check (make active) the A&H midi devices (inputs and outputs)
– daw control 1 (fader 1-8)
– daw control 2 (fader 9-16)
– etc in case of qu24 or qu32

In case of my friends system, I checked midi device “X-touch One” both in input and output

Now go to midi / control surface:
– click on the yellow + sign
A box opens “controller/Surface setting”, here you specify:
– Controller surface : Mackie control
– input port: daw control 1
– output port: daw control 1

Click OK

Now you should see the control surface “mackie control” with the “daw control 1” in “in port” and “out port”

Click bottom of screen “Toepassen”

Repeat above for the daw control 2 etc

[Dirk PHC]

There is not much more I can say about this, the process is quite straightforward.

If this is not working for you, might be other issue with your system

“I have set up three DAW Control MIDI Surfaces and the software shows them with three different colors”: is this in Cakewalk or in the A&H midi control app ?

[kahollm]

Thanks Dirk. I have all that you state and still no go. gotta be a setting somewhere… still looking. thx

[Dirk PHC]

I run W10 on my PC. Have SONAR ultimate (last version) and bandlab Cakewalk installed, both work fine with the QU
Do hot know whether you have many other usb/midi devices connected, might be idea to clean (remove) all midi devices in your cakewalk, and after reboot reconfigure the QU in cakewalk.

I have multiple other usb/midi devices connected, synths etc. In my experience only Korg is causing problems. The Korg usb/midi driver does not handle more then 10 (0-9) different devices properly, and causes all kind of midi connectivity problems with my other devices. So I do not use the korg usb/midi driver (my beuatifull Korg Kronos is connected via din midi)

All my other brands (roland, yamaha, nord, access, moog, prophet, motu …) work flawlessly together.

The korg problem since windows support more then 10 midi devices (many years ago). Allthough many efforts from me and others, no proper response from Korg to solve this. Very annoying.

[Author]

Posts