Hi Everyone! I am having an issue where Dorico gets stuck in the audio engine initialization phase upon launch. This morning I tried it, and after 20 seconds it asked if I wanted to continue to wait or terminate. I chose wait. It asked again after 60 seconds; I waited once more. The third time, I terminated the session. Then, I tried Dorico once more and it did the same thing, but after the first time I clicked “Wait” it finished launching and I can use the program. This also happened yesterday. I can’t figure out what is causing this issue. Any thoughts?
I tried to attach the diagnostic report here, but it says it is too big.
I’ve had similar issues, usually after I close Dorico, open another audio program and return. Force quitting the VST audio engine if it hangs almost always fixes it.
On Windows you use the Task Manager app for this. In the list of background processes find VSTAudioEngine, do a right click on it and from the pop-up choose End Task.
I’m still not sure though, what is causing the audio engine to get stuck during start up with you. Especially because sometimes it does succeed to do that successfully. When it gets stuck it appears to me it does so during scanning of the VST3 plug-ins.
In the list of plug-ins I can see that you have the EastWest Spaces II plug-in. Just recently another customer had also problems with that particular one and an update of Spaces II was the solution. This is something that you could also try.
Furthermore, you are also not up to date with the Groove Agent SE plug-in. You have version 5.1 whereas 5.2 is already available for download. So I would update that as well and see if things get better.
And when the VSTAudioEngine gets stuck during startup, please have a look in the Task Manager, do you see other processes in the background list with the name vstscannermaster or vstscanner?
Sorry, no immediate solution to your problem, but sooner or later we will tackle it, trust me. If you wish me maybe can also have a remote screen sharing session. That would speed things up immensely.
Hi Ulf, thanks for responding! I looked to see if East West Spaces II had an update available, but it seems I am on the latest version. I did, however, update the groove agent SE plug-in.
I don’t see any other processes in background processes with the name vstscanermaster or vstscanner when trying to launch Dorico.
I would be open to a remote screensharing session.
I would also like to mention, since you brought up the EW Spaces II plug-in, that I do not see the OPUS playback engine as an option anymore. I had it in previous versions of Dorico. But now, with 5.1, I no longer see it listed as an option. I have it whitelisted, so I am not sure why it is not appearing anymore.
Hi Justin, I’ve sent you a private message via this forum, please check. To the private message box you get by clicking on your avatar on the right top of the browser window.
Hi Ulf, I tried your suggestion to Stephane on his thread out of curiosity to see if it would improve my issue. I didn’t have the shared Components folder, but I renamed the VST2 and VST3 folders, and Dorico booted up. I then renamed the VST2 back to the original, and it booted up. Last, I renamed the VST3 back to the original, and it took maybe 20-30 seconds, but it booted up without giving me the message that it is “stuck.”
I suppose so! I still don’t have the East West OPUS Engine appearing as a possible template under Playback Templates. I am not sure why this disappeared with version 5.1 of Dorico.
And what if you just type %appdata% and hit enter and then into the search (field right to the address bar) playbacktemplatespec.xml and hit enter, what does Windows find then? It might take a bit time, so please be patient.
