Hi,
I have this strange behaviour:
I start Acoustica, open a file and press "play". I always get the error "Device didn't start correctly". I confirm with "OK".
Then, if I press "play" again, everything works fine.
After opening a new file, it starts all over again.
I run Acoustica 7.5.5 on Windows 10 (64 bit) using a MOTU UltraLitemk3 Hybrid interface. I have no problems with my interface using Ableton Live.
Acoustica Error: "Device didn't start correctly" is shown on every first playback attempt of each file
-
- KVRer
- 23 posts since 27 Apr, 2008
Using a MOTU Ultralight mk5 with Big Sur on an Intel Mac Mini here. I get the same message, and have for a long time even if the interface is currently set at the sample rate of the audio file I’m playing in Acoustica.
I’m pretty sure the fault is on Motu’s side. Can Ableton reliably change your Ultralite’s sample rate or do you have to use the Motu cue mix drive to change sample rates? The message in Acoustica started for me at some CueMix update a while back that broke the ability of programs to change the sample rate of the interface automatically.
I’m pretty sure the fault is on Motu’s side. Can Ableton reliably change your Ultralite’s sample rate or do you have to use the Motu cue mix drive to change sample rates? The message in Acoustica started for me at some CueMix update a while back that broke the ability of programs to change the sample rate of the interface automatically.
-
- KVRer
- Topic Starter
- 21 posts since 8 Jun, 2021
Hi,
Yesterday, it seemed, at least in the Ableton Live 12 trial, switching the sample rate worked. But I remember having those issues before, yes.
Also not sure whether that is usual behavior of interfaces, but switching sample rate takes several seconds.
Concerning the error above, I got a very quick reply from Acon Digital support. Thanks again!
They suggested to use Asio4All.org driver and it worked for me.
I did not test whether this affects the interaction with CueMix or how performance is, but as I have both drivers installed, I can choose which one to use. Ableton Live still runs with the MOTU Asio driver.
So you see any issues with this approach?
Yesterday, it seemed, at least in the Ableton Live 12 trial, switching the sample rate worked. But I remember having those issues before, yes.
Also not sure whether that is usual behavior of interfaces, but switching sample rate takes several seconds.
Concerning the error above, I got a very quick reply from Acon Digital support. Thanks again!
They suggested to use Asio4All.org driver and it worked for me.
I did not test whether this affects the interaction with CueMix or how performance is, but as I have both drivers installed, I can choose which one to use. Ableton Live still runs with the MOTU Asio driver.
So you see any issues with this approach?
-
- KVRer
- 23 posts since 27 Apr, 2008
Glad you made some progress. Acon has good support. I’ve just accepted this behavior and have yet to reach out to them. I probably should ha
Yeah, in my experience it takes some small amount of time to switch sample rates, seems normal.
As far as the two driver situation, I do not know anything about that. My system is Mac based and I only have ancient out of date experience with windows.
Yeah, in my experience it takes some small amount of time to switch sample rates, seems normal.
As far as the two driver situation, I do not know anything about that. My system is Mac based and I only have ancient out of date experience with windows.
-
- KVRer
- Topic Starter
- 21 posts since 8 Jun, 2021
Since somehow my ASIO4all stopped working without an apparent reason 
I tried again the native MOTO ASIO driver.
I can force the error "Device didn't start correctly" by setting a different buffer size in the settings of Acoustica than are set in the native driver's control panel.
I had 192 sample there, but in Acousitca, 128 was set. At least now, when I set it to 192, no error occurs.
centipus, did you check that?
I tried again the native MOTO ASIO driver.I can force the error "Device didn't start correctly" by setting a different buffer size in the settings of Acoustica than are set in the native driver's control panel.
I had 192 sample there, but in Acousitca, 128 was set. At least now, when I set it to 192, no error occurs.
centipus, did you check that?