I am currently Sibelius user and want to test Dorico. When launching on Win Pro 11, RME UFX+ Thunderbolt sound card. Dorico can not get past “Wait for audio engine initialization” All other programs function (CUBASE 13, Wavelab 11, Nuendo 12 etc). I have found a thread saying to stop VSTAudioEngine and that does not solve issue. I would like to buy while sale is going on but need it to function prior.
Is there a Safe mode start for this?
Is there a way to ignore audio engine during start up?
Any help is appreciated
No, in Dorico we do not have such safe start mode (yet), but you could do something similar, namely go to C:/Program Files/Common Files/ and rename temporarily the two folders VST and VST3 to something else. Then start Dorico and see how it behaves. If still bad, then also try to rename the folder C:/Program Files/Common Files/Steinberg/Components and see how that goes.
Thank you, both files renamed and then changed each back individually. It seems the VST 3 folder is cause for error. Is there a way to solve this without permanently renaming folder?
Then move half of all the plug-ins from _VST3 to VST3 and start and stop Dorico again
If it started fine, you continue with step 3.
If it did not start, you move half of the plug-ins you just moved to the VST3 out again and check Dorico’s start-up behaviour.
Do you get the principle? By always moving a half you can relatively quickly find the offending item even if you have lots of plug-ins.
Please also share with us your final findings.
Thanks for the info and sorry took so long to respond as had sessions all week. I moved VST3 plugins and alphabetically added them back. The following VST3 caused the issue (RHODES V8) It did not cause an issue on my M2 Mac though. See attached link to plugin. I do use this VST though can you please suggest a best method of adding it back to Cubase 12-13 and Nuendo 12?
I’m not sure either. See, that plug-in behaves in Dorico so badly, that it can’t be even loaded for scanning somehow, therefore crashe the audio engine and nothing works at all. Now, how exactly does it behave with you in Cubase/Nuendo? Does it crash Cubendo and you can’t use it at all?
The Plug-in Manager in Cubendo has the possibility to unblock plug-ins at the risk of the user. Yet I wonder, Cubendo you can start despite that plug-in being around, right?
@kzarider, thank you for this post! I’ve done my best to address this issue by following all of your advice, as well as the guidance from @Ulf — thank you for your effort too!
Unfortunately, I’m still encountering the same problem. Here’s my situation:
After starting up my MacBook (2017, Ventura 13.7) and attempting to open Dorico Pro 5, it fails to launch successfully about four out of five times, showing the same error described in @kzarider 's article. Then, inexplicably, it works almost every time after multiple attempts.
I checked all my VST3 plugins, as they seem to be causing the issue, but I haven’t identified the problematic one yet.
Welcome to the forum @Robert_V and thanks for the data.
Unfortunately that does give me not enough information.
If you have that situation where Dorico is hanging, please open the Activity Monitor.app sort the process list by name. If you then watch out for the VST Audio Engine process are there any other processes with vst in the name?
Is there a vstscannermaster and two vstscanner?
In the Activity Monitor.app at the top of the main window is a round icon with 3 dots inside. Clickk on that and from the pop-up menu choose Create Spin Dump (or similar). The output of that please save to a text file, zip it up and post here. Thank you very much
Thank you so much for your reply.
Yes when Dorico is hanging there is vstscannermaster and VST Audio Engine.
There is spindump of both. Spindump.zip (582.3 KB)
Additionally I saw WardaSyntheseizer_X86_64 running
I’ll check if it’s some VST, as I’ve never used a program/vst with that name. And I’ll get back to you as soon as I can.
(EDIT)
That’s some Apple Intel stuff, as far as I could check.
And there were no vstscanner processes?
Because then the VSTAudioEngine is waiting for the vstscannermaster process, but the vstscannermaster seems stuck. Because it does not return any results to the VSTAudioEngine and therefore that one is also hanging and you get that alert.
So there must be something wrong with the vstscannermaster. I will discuss this with the programmer of the master scanner.
If you kill Dorico, the VSTAudioEngine and the vstscannermaster via the Activity Monitor and then start up again, does it get stuck again?
No there was no vstscanner processes.
I killed it and both vstscannermaster and VST Audio Engine it’s turned off.
Now on second time I wanted to run Dorico (After 20 min) it’s turning on normally. It’s very unpredictable. Also on seccond time vstscannermaster didn’t turned on.
Okay, now let’s try something different… Please open a command window by clicking on the windows button on your taskbar, then type the 3 letters C, M and D, then Enter/Return and into the now popping-up window copy and paste the following line
Please make sure you really get everything from the first quotation mark until the last one. Then press Enter or Return.
How does that then behave, is the vstscannermaster running for some time and then disappears? How about vstcanner processes, are they coming and going ?
Apologies again, I thought it would be easier to find out the culprit,
But up until now I still don’t know how to formulate the command line for the scannermaster, I need to ask the guy who wrote the scannermaster on Monday. So some more patient please. Thank you
After that please select the whole output from the Terminal window, copy and paste into a text file and send me. Likewise send me the zipped test folder wihtin your download folder.
Thanks a lot
