(solved) CQ20B ASIO error with new firmware 1.2.2

Cantabile
1

Solved - you can put the mixer in stereo or multitrack mode when used as an interface. Either through finger trouble or as a result of upgrade it was set to stereo. Putting back to multitrack fixed it.

Hi @brad

Upgraded the mixer to the latest firmware 1.2.2 - ASIO doesn’t work any more. I get an error with the following log entries. Cubase works fine. Thanks!

00165152 0 [07028:2]: CoreEngine - Starting audio driver
00165152 0 [07028:2]: asio - ASIO Driver: CQ ASIO Driver
00165152 0 [07028:2]: asio - Starting on thread 7028…
00165152 0 [07028:2]: asio - Input Channel #0 - #1: Main L - Disabled
00165152 0 [07028:2]: asio - Input Channel #1 - #2: Main R - Disabled
00165152 0 [07028:2]: asio - Output Channel #0 - #1: USB L - Disabled
00165152 0 [07028:2]: asio - Output Channel #1 - #2: USB R - Disabled
00165152 0 [07028:2]: asio - Creating buffers, count: 0, size: 128
00165152 0 [07028:2]: asio - Stopped.
00165152 0 ! [07028:0]: asio - Failed to create buffers - ASE_InvalidParameter (0xfffffc1a)
00165152 0 ! [07028:0]: CoreEngine - Failed to start audio driver (error 13101, failed to create audio buffers)
00165152 0 [07028:2]: CoreEngine - Stopping
00165152 0 [07028:2]: CoreEngine - Unpreparing audio driver
00165152 0 [07028:2]: CoreEngine - Parallel executor stopping
00165152 0 [13516:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165152 0 [01464:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165152 0 [18516:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165152 0 [18472:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165152 0 [09988:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165152 0 [19932:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165152 0 [21336:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165153 1 [07028:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165153 0 [07028:2]: CoreEngine - Parallel executor stopped
00165153 0 [07028:2]: CoreEngine - Stopping task pool
00165157 4 [07028:2]: CoreEngine - Stopped
00165157 0 [07028:2]: Heap Stats
00165157 0 [07028:2]: total allocations: 6909
00165157 0 [07028:2]: total frees: 2162
00165157 0 [07028:2]: created tanks: 2
00165157 0 [07028:2]: destroyed tanks: 0
00165157 0 [07028:2]: same thread frees: 2162
00165157 0 [07028:2]: inter thread frees: 0
00165157 0 [07028:2]: allocs in tank: 5370
00165157 0 [07028:2]: allocs from tank: 5370
00165157 0 [07028:2]: allocs from free list: 1539
00165157 0 [07028:2]: returned allocations: 0
00165157 0 [07028:2]: blocking allocs: 0
00165157 0 [07028:2]: blocking frees: 0
00165157 0 [07028:2]: context resets: 0
00165157 0 [07028:2]: blocking tank allocs: 0
00165157 0 [07028:2]: reserve tank claims: 1
00165157 0 [07028:2]: destroyed contexts: 0
00165157 0 [07028:2]: End heap stats
00165212 55 [07028:2]: CoreEngine - Reverting power plan to ‘Balanced’
00165450 238 [07028:2]: Engine stopping
00165450 0 [07028:2]: CoreEngine - Stopping
00165450 0 [07028:2]: CoreEngine - Parallel executor stopping
00165450 0 [07028:2]: Parallel Thread: exec:0 wakes:0 soft:0 hard:0 locks:0 lockrate:-nan(ind)
00165450 0 [07028:2]: CoreEngine - Parallel executor stopped
00165450 0 [07028:2]: CoreEngine - Stopping task pool
00165450 0 [07028:2]: CoreEngine - Stopped
00165450 0 [07028:2]: Heap Stats
00165450 0 [07028:2]: total allocations: 6909
00165450 0 [07028:2]: total frees: 2162
00165450 0 [07028:2]: created tanks: 2
00165450 0 [07028:2]: destroyed tanks: 0
00165450 0 [07028:2]: same thread frees: 2162
00165450 0 [07028:2]: inter thread frees: 0
00165450 0 [07028:2]: allocs in tank: 5370
00165450 0 [07028:2]: allocs from tank: 5370
00165450 0 [07028:2]: allocs from free list: 1539
00165450 0 [07028:2]: returned allocations: 0
00165450 0 [07028:2]: blocking allocs: 0
00165450 0 [07028:2]: blocking frees: 0
00165450 0 [07028:2]: context resets: 0
00165450 0 [07028:2]: blocking tank allocs: 0
00165450 0 [07028:2]: reserve tank claims: 1
00165450 0 [07028:2]: destroyed contexts: 0
00165450 0 [07028:2]: End heap stats
00165450 0 [07028:2]: Engine stopped
00165460 10 [07028:2]: asio - Releasing asio driver
00165460 0 ! [07028:0]: Failed to start engine
#=z9ie$zskrE$xScQBajbKP6K$W4dj1: Failed to start audio driver (error 13101, failed to create audio buffers)
at #=ztSkTC3QbzD$NnKiztNmtXkCDaamS.#=zAhJOC0c=()
at #=zWK7p$5wyf$rjJENlMScXeyc=.#=zAhJOC0c=()
at #=zOwfawAjbVAyxvWCtI8qfFw6D05H2btckGg==.#=zT1CZZw4=()

2

Hi @johncarter

If this started failing after an update to the device then this suggests an issue with the driver. I’d recommend reporting this to the hardware vendor and see if they have a solution. Be sure to mention it worked before the update.

Failing that I’ll probably need to either reproduce the issue or get in touch with a developer on the driver side to figure out what their driver is upset about.

I’m away from my main dev PC for the next few weeks but let me know if you hear anything from the driver vendor.

Brad

3

Hello,
I’m using this mixer, but only as stéréo USB output. This means after the firmware update this will not work anymore ?

Frédéric

4

I’ve no idea, it might be that cantabile gets confused when the “spec” of this mixer changes. You could do some experiments to see what the behaviour is with current version moving from stereo to multi track and back (back up the settings file first). Alternatively, the upgrade doesn’t seem to be essential, so if you’re happy then maybe don’t upgrade (yet).

5

It doesn’t seem to be easy to downgrade the firmware back. So I will avoid to test as is because I need the stereo USB output !
The firmware brings an update regarding the gain settings, which are not recalled from a previous scene with the previous firmware. This allone is worth the update, but not at the price of no USB !!
Thanks for your feedback !
Frederic