Hello,
Same problem here. I found just one more thing, if I deactivate Link Inputs 1&2, I have no problem (Config - Inputs - Disable Stereo Link)
This might be a Mac and Sequoia issue. Mac and USB seem to have “flakey” moments, but being Apple you don’t hear too much about “hardware” issues. Could try quizzing the users on Apple support forums re USB stability.
Ive had non A&H related USB and Audio streaming issues in the past.
David
Hello there,
Subscribe to this thread. For me, the solution—if it can even be called a solution—was to stop using the USB connection on the CQ-12T. Basically, I only use it as a DSP and send the output to the RME Babyface Pro FS, where I have zero USB connectivity issues. I’d like to use only the AH CQ-12T to simplify my setup, but that’s out of the question. It constantly freezes, apps stop responding, and I’m forced to restart the AH CQ-12T. It’s a fantastic product for what I do with it, but incredibly frustrating when used with a Mac.
Model Identifier: Mac16,1
Chip: Apple M4
Total Number of Cores: 10 (4 performance and 6 efficiency)
Memory: 16 GB
System Firmware Version: 11881.81.4
OS Loader Version: 11881.81.4
OS: Sequoia 15.3.1
AH CQ12
Firmware: 1.2.1 r4213
I’m keeping it only as a DSP. Otherwise, I would have given up on this product. I hope AH fixes these issues with a firmware upgrade. I have zero problems with other audio interfaces.
Daniel
Any updates on this one?
Received my CQ-12T previous week and can also confirm this issue when using an iPhone 15 Pro Max giving a loud hum/ looses USB connection after a while….
Edit 19-03-2025 can’t reproduce the issue on an older iPhone X. So it seems iOS or Apple chipset related perhaps…
I’ve experienced something similar with iPad. Loud buzz suddenly appeared after some time of streaming audio a few times.
Also I get it with Mac. If I disconnect Mac while it’s playing CQ produces static buzzy noise on those channels. I get the same problem with iPad and iPhone.
The same issue now also occurred on my iPhone X… no USB audio possible anymore. mixer als hangs in shutdown…
@rafaela any official words from A&H?
I’ve found the CQ20b USB driver to be a bit finicky. I’m having some issues with my CQ20b playing multitrack audio over USB with a 10m long cable connected to my iPad pro, I know this length could be problematic but I made sure to choose a good quality cable, and with my other mixer, a Behringer Wing Rack as well as my old Behringer X 32 there’s absolutely no problem with that cable, however with the Allen&Heath sometimes it works perfectly and other times I get a really nasty beeping noise and the iPad stops playing until I reset the USB audio on the mixer.
Hi @Keith I saw you replied on another topic concerning this issue, any updates on this one? Rafaela did not reply.
I’m still in the right to return period and want to check if this is as is or a future firmware update will fix it?
Edit: Ticket ID: 900592
@SVV do you also charge your iPhone while connected to the mixer?
@joseph7 That is indeed the case.
Well I mean the iPhone is not being charged by the mixer btw but through a USB C hub or IPhone Camera connection kit.
I’ve also get random dropouts and noise if using some hubs with power delivery. But when using apple’s original adapter its seems to be fine.
@joseph7 that’s interesting. And by adapter you mean the Apple Power Adapter or camera connection kit and so?
Hi there, this may not be the same issue others are experiencing, but there is an issue with the CQ-12T on the current firmware not maintaining a solid USB connection with a Mac (may be the same for iOS?). A&H are aware of the issue and looking into it. This only applies to the CQ-12T (the CQ-18T is fine), the workaround is to downgrade the firmware to 1.2.0. Obviously make sure you back up your files etc on the CQ-12T first if you try this.
Hi! I bought 4 days ago the cq12t and I had the same issue. After downgrading the firmaware to 1.2.0 I resolved the problem. It’s a firmaware bug not a mac bug!
Hi. I had the same issue as all the above and below owners. After downgrading the firmaware to 1.2.0 (from 1.2.1) i didn’t experience the problem anymore. Please resolve the bug of the last firmaware.
Downgrade to 1.2.0. and it will work perfectly. It’s a firmaware bug.
