V1.2.2 firmware released. It is a maintenance release but shows that A&H are still working on the CQ.
3 Likes
The release notes…
2 Likes
Can anyone get audio into the mixer from their PC via the BT stereo input exposed to WDM by CQ18T?
It’s set to usb source and bt is turned off but I can’t get signal without manually routing it using VB matrix. It works fine for the other two stereo inputs with no external tool needed.
I updated and since then I cannot connect thru wifi. Also bluetooth won’t be discoverable
Can you not use a “-” in channel names anymore?
Wifi and BT is working fine for me (CQ12T).
The only weird thing I noticed, when naming a channel, is that I can’t input a “space” via the CQMixpad (Android and Ipad) while it is possible via the CQ keyboard.
Did they really take away the “-” character? And why are there only 6 colors available and all are quite unsaturated? In the digital realm, colors are free…
According the the CQ virtual keyboard yes, only letters and numbers available.
1 Like
That’s devastating… used it in half my channels.
I’m surprised about the removal of symbols. Other A&H systems allow symbols and I agree that having symbols available is basically a requirement for labeling things. I’ve used - ! * $ etc to help label things and it would be devastating to suddenly have those become invalid.
1 Like
I could not do the firmware update after updating to MixPad 1.2.2. on my iPad. So, I did it via USB stick successfully. Then many unsuccessful attempts to get iPad / MixPad 1.2.2 going. Uninstall, clear the network, etc…It will not connect; not even showing the mixer ssid to connect….After dicking with this most of yesterday, I got MixPad 1.2.2 for MAC to work only after disabling WPA2.
I created a ticket with A&H and they already came back saying they have duplicated the problem on iPad OS 18 (I’m running 18.5). So they are working on it….
I have create a ticket for the special characters and for the spacebar not working via the CQMixpad app.
EDIT, reply from technical support:
…these had to unfortunately be removed due to the fact they were causing an issue when writing to the file names when Multitrack recording on SD. Whereby, it was causing the audio files to become corrupt and in cases unusable.
Note that you can still use them via MS.
(Worth noting that if you choose to use these characters via Mixing Station, you may experience issues later on with your recorded files)
Yes I forgot to mention that.
It is just because I do not use the MT recording so it is OK for me.
Thank you MarkF and thanks again to the support team for the very fast reply I get for my ticket.
2 Likes
As a dev myself, there was surely a better solution than outright removal.
That sounds really anything but professional and would be completely unworthy of a popular mixing console manufacturer in 2025.
And you forgot at least a corresponding note in the Release Notes under “Deteriorations”.
Hopefully we can certainly assume that this was only created due to the increasing pressure for updates here in the forum, and is therefore a short, unfinished interim solution.?
Or should we expect that “-” and spaces will soon be removed from all consoles that can multitrack record because they corrupt correspondingly named files???
2 Likes
There is some way to downgrade the app version to 1.2.1 on ios 18.5?
This has been updated by A&H to v 1.2.3 for iPad. It now connects with OS18+. My iPad now connects properly…
Thanks to A&H for the quick response!
Looks to me like it was an “access local network” issue. On load up of v1.2.3 it asked for permission to access local networks. And it now appears in the local networks section of safety and security…..
I’ve confirmed with support that this feature of the mixer (third stereo input over usb-b) actually does not currently function. Apparently I was somehow the only person to ever discover this.
I really need it for some of my studio work so I’m hopeful that it can be resolved quickly.
They’ve informed me that they will be working on a fix but no timeframe has been provided
1 Like
As far as I can remember that was working before the new firmware.
But I don’t use it so often so I might be wrong.