Help - ASIO - Stop Sudio Engine

[tillhout]

Hi, First let me say I love matrix/Coconut - What a great piece of software.

A few months ago I got a Zoom H6 essential 32 float hand held recorder from ZOOM Corp. (not ZOOM video conferencing). I use it as an audio interface through Coconut to supplement my main interface a MOTU MK5 which I use as my Master. I am running a sample rate of 48,000 Hz with a sample size of 64.

Everything works fine except for one fatal problem.....

Every once in a while the Coconut audio engine needs to restart and if that happens during recording I get about a second of dead space before the engine automatically starts up again and recording resumes (I am using REAPER for my DAW). The error in the log in Coconut reads:

#0016 - 2025 AUG 16 - 10:32:56 | ASIO - Stop Audio Engine - ASIO Reset required
#0017 - 2025 AUG 16 - 10:32:57 | USER - Start Audio Engine (in:155 / out:152 / master:ASIO32 / SR:48000 Hz / buffer: 64 smp).

This drop out occurs when reaper is not even running.

I suspect it is an issue with ASIO driver for the Zoom recorder because when I disconnect the zoom recorder I never get drop outs.

I have tried different sample rates and differnt sample sizes nothing seems to make a difference.

I have tried reaching out to ZOOM Corp. but that turned into a dead end.

My solution has been to not use the Zoom recorder as a supplemental interface but now I would like to give it another try.

Any suggestions or comments would be greatly appreciated.

Thank you.

[Vincent Burel]

well, Matrix run while all device are running and are not requesting for a RESET.

[tillhout]

Thanks vincent but I do not understand your response. Is there a RESET command? What are you suggesting?
Thanks

[Vincent Burel]

did you install the latest Matrix version to see if the problem remains ?

[tillhout]

Thank you.
Yes I just did that and it seemed to help. It did not reset for hours and now just 5 minutes ago it did a reset.
I was hopeful for a minute.
Thanks

[Vincent Burel]

could you post the log (LOG/CLI in menu) that could help us to understand the reset reason ?