This is Dorico Elements 5.1.21.20 on Windows 10 Pro using a Roland Quad-Capture with Roland’s drivers.
I’ve tried Exit. I’ve tried Close Project. I’ve tried Close All. I’ve tried the close button at the upper right of the window. No matter what I do, almost every time (but there are rare exceptions, and I cannot find any pattern), the visible window closes instantly, but processes named Dorico and VSTAudioEngine are left running. Unless I terminate them, Dorico will not start again. Unless I terminate VSTAudioEngine, nothing else (such as Pianoteq standalone) can access my ASIO device.
No other software I have fails to let go of the ASIO device when I close it (e.g., Pianoteq, Blue Cat’s Axiom, MusicLab’s RealGuitar, Reaper) except Dorico (ironic, since Steinberg created ASIO and you’d think they’d be the best at it). This makes me think it is almost certainly something odd about Dorico rather than something odd about my system setup.
When I open Dorico after terminating these processes, it complains that it was not shut down properly. (I always save before I close if I want to keep my changes, so I always tell it to discard whatever it thinks might be worth recovering.)
One final oddity: While I was typing this text in Firefox, I opened Dorico to check the exact version number. When I closed Dorico, Firefox was frozen. I opened task manager, terminated the windowless Dorico process, and immediately Firefox unfroze. After that, I double-checked, but the problem described above still happens when Firefox is not running.
Hi @Coises , sorry to hear about your trouble.
Could you please choose from Dorico’s menu Help > Create Diagnostics Report and attach the resulting zip file to a reply here? Thanks.
Additionally, please download the free utility Process Explorer. Then run procexp64.exe and when either Dorico or the VSTAudioEngine processes are stuck, do a right click on them in Process Explorer and choose from the pop-up menu Create > Create mini dump. Save the output, zip it up and also post here please. Thanks
Thank you for your willingness to help. I have the zip file, but I am not comfortable posting it publicly; it appears to contain personal information (for example, a list of all the vst plugins that are on my system).
If you can tell me how to communicate the information privately, I can give you a URL from which you can retrieve it.
Edit: As recommended by @Derrek, below, I sent you a message with a link to a zip file containing all the requested files.
When I disconnected the interface, Dorico switched to using Steinberg built-in ASIO Driver - Version 1.0.0.16 - x64 with BenQ GW2760HL (NVIDIA High Definition Audio) (which is the only other audio device available; motherboard audio is disabled on this computer). As far as I could tell, the problem does not occur in this configuration.
After reconnecting the interface I tried the available drivers. The problem can occur with all the drivers, but the patterns appear to differ. However, none of these patterns seem to be absolute; neither proper functioning nor failure to close is consistently reproducible every time in any configuration. Note that QUAD-CAPTURE is the only driver which results in low enough latency to allow me to play the keyboard to work out parts as I’m writing them (something I need to be able to do).
With the Steinberg built-in ASIO Driver, Dorico and Steinberg Hub shut down OK, but VSTAudioEngine is usually left hanging if and only if I entered notes into the score using the MIDI keyboard. This allows the next attempt to start Dorico to reach the splash screen; then it hangs saying it cannot initialize the audio device.
With the Generic Low-latency audio driver, either Dorico or Steinberg hub, as well as VSTAudioEngine, are usually left hanging when I generate any MIDI input (it can be playing just to hear, without entering any notes into the score); if I only look at the project, play it or edit it without MIDI input, the problem doesn’t occur.
With QUAD-CAPTURE selected as the ASIO Driver, Dorico and VSTAudioEngine are typically left hanging whether I generate MIDI input or not. Occasionally everything closes normally; I haven’t yet discovered whether these occasions are only when I’ve generated no MIDI input, but there definitely are sometimes hangs when I haven’t touched the keyboard (it might still be sending keep-alive messages, though; I didn’t try disconnecting the keyboard from the Quad-Capture).