[FedaRootsParticipant]

Hi, any news on this? I own a QU-32 and after upgrading to CATALINA I lost the surface control on LOGIC X PRO.

[FedaRootsParticipant]

One important thing I forgot to mention …

The MIDI order coming out from the QU32 is being executed from the console layer (not the CUSTOM LAYER), so be aware that if you had selected TRACK #1 on the console when assigning the PAN order to the DAW, then YOU MUST SELECT TRACK#1 in the console mode BEFORE moving into the CUSTOM LAYER MODE for the pan order to work. Otherwise the DAW won’t be receiving any instruction when you move the selected super-strip knob (in my case I use the Compression knob because is the one I could make it work!).

[FedaRootsParticipant]

HEY GUYS!

After a few months…haha..I could make PANNING WORK! over midi to control LOGIC’s Selected Track over my QU32.

I have attached an image that describes how i did the setup of the LEARNING MIDI ORDER on Logic’s Advanced MIDI Controlling setup. Also, you have to double check that the check box “TRACK LOCK” is not selected in your DAW CONTROL MIDI setup.

It works fine! and I can now pan my selected track on logic using QU32’s COMPRESSION KNOB (which is useless when you use the console for controlling your daw).

Hope it helps.
FEDA

Attachments:

You must be logged in to view attached files.

[FedaRootsParticipant]

Hey gus, did you find a way to do this? I am trying to find a workaround for it too .. .but I couldn’t find one yet…

[FedaRootsParticipant]

HI DMarin, did you find a way to control DAW’s pan over QU Console?
It’s crazy nobody has find a way to do it already 🙂

[FedaRootsParticipant]

Thanks guys for your swift reply.

After trying several times…and doing nothing different one time of the other … today I could made QU32 and Apollo8p work together on Logic X using an aggregated interface control. I set QU32 as managing clock control and clicked on Drift Correction for the Apollo.

BUT the what’s is more strange is that it has not work on Pro Tools 12. When I select AGGREGATED PROTOOLS IO on Protools, in can receive input signals from the QU32 but not for the Apollo. Could it be the 32 restriction that Protools has when it comes to inputs? I tried on every single input available on the I/O settings panel trying to get mic signal from Apollo’s input #1 … but couldn’t make it …. what do you think could be happening?

I have attached 2 images for your review.

FEDE

Attachments:

You must be logged in to view attached files.

[Author]

Posts