Hello.
I’m having trouble with trying to open Dorico 6 Pro in the first place.
Once the software gets into the Audio engine process, it seems to get stuck there forever, and I have to eventually “terminate” the process (one of the two options I’m given, the other being to wait).
I’ve attached the Dorico Diagnostics to this message.
Thank you in advance for your help.
Dorico Diagnostics.zip (534,9 Ko)
Welcome to the forum, @Allegretto
something seems to go wrong during VST3 plug-in scanning.
First thing to try is, go to C:/Program Files/Common Files and in there is the folder VST3. Now, just temporarily, rename that folder to _VST3
By that you hide away all VST3 plug-ins from Dorico’s audio engine. If you do that, does Dorico then start up?
Of course, just renaming is not the solution, but a first step in trying to find the real cause. What you can also check if you are already there, in that VST3 folder are quite likely other subfolders, is there maybe another VST3 subfolder in there? And possibly, is that a symbolic link the top level VST3 folder?
Thank you very much for your help, @Ulf , I appreciate it.
After renaming the VST3 folder as _VST3, Dorico doesn’t get stuck on Audio engine anymore but I get the following message appearing at the end of the process: “An essential component used by Dorico for playback has not been found. Please run the Steinberg Download Assistant and install the following: Halion Sonic 7 - Instrument; Groove Agent SE 5 - Instrument”
I’ve already tried to reinstall those 2 times since then, but this message still appears.
There is no other VST3 subfolder in my VST3 folder, however there is a number of subfolders that have “.vst3” in their names such as “HALion Sonic.vst3” or “Serum.vst3”, most of the subfolders are named like that.
Renaming that folder to _VST3 was not supposed to be the solution, just a first step to try something out. But it shows clearly that one of the VST3 plug-ins is the culprit. I don’t know how many plug-ins you have, but if it is only a few try the following strategy. Create a new VST3 folder and move from the other, previously renamed folder one plug-in to the new VST3 folder and start Dorico again. If it does not hang, fine, stop Dorico, move the next plug-in and start again. So you see you do this in circles until Dorico hangs again at startup, then you have found the culprit. If you have a huge number of plug-ins, you can use the same approach with groups of plug-ins. If Dorico hangs you know that the culprit is a plug-in from the last group you added and you take them one by one out again.
It’s a bit tedious: move, start, observe, stop,… but that’s the way to find out. You got it?
Thank you very much once again for the help and thorough answer, @Ulf.
I have a huge number of plugins so this took a bit of time, but it seems like the culprits are a few Native Instruments plugins, namely “Battery 4”, “Guitar Rig 7”, “Komplete Kontrol” and “Kontakt 8”.
Adding any of these to the VST3 folder seems to cause Dorico to get stuck on Audio engine.
That’s interesting - I’ve never had a problem with any of these (though I don’t use Guitar Rig)
This is interesting indeed, as I’ve never had any problem with those either when using them in Cubase – only when trying to open up Dorico.
I use Kontakt frequently with Dorico (on Windows).
Once or twice I’ve had a sudden crash (Kontakt failed and Dorico just shutdown), but never had a problem with start up.
Interesting. This does appears on start up on my end indeed, and what’s even more strange is that I don’t have this issue with “Kontakt”, but “Kontakt 8” is one of the cause of this problem.
Similarly, a number of other plugins I have from Native Instruments’ Komplete Standard bundle isn’t causing any issue with starting up Dorico, so it almost seems like those 4 plugins that does cause the Audio Engine to get stuck on VST3 scanning forever to be kind of random. They have in common the fact that they’re all Native Instruments plugins, but a number of plugins from the same company seems to work fine with Dorico’s audio engine on my end, so I’m rather puzzled.
I’ve used various incarnations of Kontakt with Dorico - all stress free. IIRC older versions used to appear as just Kontakt? On my current machine I have Battery 4, Kontakt 7 and 8 . Though I only use 7 for projects.
Have you tried removing and reinstalling Kontakt?
You’re most probably right that older versions of Kontakt just appears as “Kontakt”. I haven’t upgraded to Kontakt 8 until fairly recently so I skipped Kontakt 7 and went straight with Kontakt 8 – and only because a few plugins I have only work with Kontakt 7 onwards. As such, I still use what is Kontakt 6 (if memory serves me right), as a matter of habits, and occasionally use Kontakt 8 for the plugins that doesn’t work with Kontakt 6.
I’ve recently made some big updates through Native Access, and I believe Kontakt 8 was part of the plugins that had some update available. I will try to reinstall the 4 plugins that are causing the issue I have with Dorico, thank you very much.
Would you please also try and run the vstscanner manually on those plug-ins. Please have a look at my posting here of how to do that. You just need to exchange the HALion Sonic path to that of Kontakt and the other plug-ins. And then tell me the error levels for all of them. Thanks a lot
Thank you very much. Strangely enough, after reinstalling Kontakt 8 and rebooting my computer, Dorico now seems to only have trouble with Komplete Kontrol. I’ve done the whole process of moving plugins from a _VST3 to the VST3 folder again in order to see how Dorico behaves on startup, and Kontakt 8, Battery 4 and Guitar Rig 7 now seems to work fine… Only Komplete Kontrol is causing Dorico to get stuck on audio engine.
Anyway, I’ve tried your suggestion of running the vstscanner on those plugins. Here are the results for each of them:
<?xml version="1.0" encoding="UTF-8"?>
<plugin><path>C:/Program Files/Common Files/VST3/Kontakt 8.vst3</path><vendor>Native Instruments</vendor><url>http://www.native-instruments.com</url><email>mailto:info@native-instruments.com</email><flags>16</flags><codesigned>false</codesigned></plugin><?xml version="1.0" encoding="UTF-8"?>
<classInfos><class><cid>5653544E694B386B6F6E74616B742038</cid><cardinality>2147483647</cardinality><category>Audio Module Class</category><name>Kontakt 8</name><classFlags>0</classFlags><subCategories>Instrument</subCategories><vendor>Native Instruments</vendor><version>8.10.0</version><sdkVersion>VST 3.8.0</sdkVersion><compatibility><compatUID>5653544E694B376B6F6E74616B742037</compatUID><compatUID>5653544E6924446B6F6E74616B740000</compatUID><compatUID>5653544E694F376B6F6E74616B742035</compatUID><compatUID>5653544E694F366B6F6E74616B742035</compatUID><compatUID>5653544E694F356B6F6E74616B742035</compatUID><compatUID>5653544E696B366B6F6E74616B742034</compatUID><compatUID>5653544E696B356B6F6E74616B742034</compatUID><compatUID>5653544E696B346B6F6E74616B742034</compatUID><compatUID>5653544E694B356B6F6E74616B742033</compatUID><compatUID>5653544E694B346B6F6E74616B742033</compatUID><compatUID>5653544E694B336B6F6E74616B742033</compatUID><compatUID>5653544E6953346B6F6E74616B74325F</compatUID><compatUID>5653544E6953336B6F6E74616B74325F</compatUID><compatUID>5653544E6953326B6F6E74616B743200</compatUID><compatUID>5653544E6953536B6F6E74616B740000</compatUID></compatibility></class><class><cid>000000F400000066000000170000002A</cid><cardinality>2147483647</cardinality><category>Plugin Compatibility Class</category><name>Kontakt 8Compatibility</name><classFlags>0</classFlags><subCategories /><vendor>Native Instruments</vendor><version /><sdkVersion /></class></classInfos>
cannot resolve resource: application_FRA
<?xml version="1.0" encoding="UTF-8"?>
<plugin><path>C:/Program Files/Common Files/VST3/Komplete Kontrol.vst3</path><vendor>Native Instruments</vendor><url>http://www.native-instruments.com</url><email>mailto:info@native-instruments.com</email><flags>16</flags><codesigned>false</codesigned></plugin><?xml version="1.0" encoding="UTF-8"?>
<classInfos><class><cid>5653544E694B4B6B6F6D706C65746520</cid><cardinality>2147483647</cardinality><category>Audio Module Class</category><name>Komplete Kontrol</name><classFlags>0</classFlags><subCategories>Instrument</subCategories><vendor>Native Instruments</vendor><version>3.5.3 (R0)</version><sdkVersion>VST 3.7.11</sdkVersion></class></classInfos>
cannot resolve resource: application_FRA
cannot resolve resource: LanguageNames
<?xml version="1.0" encoding="UTF-8"?>
<plugin><path>C:/Program Files/Common Files/VST3/Battery 4.vst3</path><vendor>Native Instruments</vendor><url>https://www.native-instruments.com</url><email>mailto:info@native-instruments.com</email><flags>16</flags><codesigned>false</codesigned></plugin><?xml version="1.0" encoding="UTF-8"?>
<classInfos><class><cid>5653544E426134626174746572792034</cid><cardinality>2147483647</cardinality><category>Audio Module Class</category><name>Battery 4</name><classFlags>0</classFlags><subCategories>Instrument</subCategories><vendor>Native Instruments</vendor><version>4.3</version><sdkVersion>VST 3.7.8</sdkVersion></class></classInfos>
cannot resolve resource: application_FRA
<?xml version="1.0" encoding="UTF-8"?>
<plugin><path>C:/Program Files/Common Files/VST3/Guitar Rig 7.vst3</path><vendor>Native Instruments</vendor><url>http://www.native-instruments.com</url><email>mailto:info@native-instruments.com</email><flags>16</flags><codesigned>false</codesigned></plugin><?xml version="1.0" encoding="UTF-8"?>
<classInfos><class><cid>5653544E692454677569746172207269</cid><cardinality>2147483647</cardinality><category>Audio Module Class</category><name>Guitar Rig 7</name><classFlags>0</classFlags><subCategories>Fx</subCategories><vendor>Native Instruments</vendor><version>7.0.2 (R0)</version><sdkVersion>VST 3.7.8</sdkVersion></class></classInfos>
EDIT: I just realized I forgot to check for the errors levels for all of them, I apologize. I’m doing those right away.
The error levels for all of them is 0.
Thanks very much @Allegretto .
And yes, error level 0 means no error, so finally I expect all of them making no trouble anymore during startup, right?
As to how it comes that they made trouble and now suddenly not anymore, I honestly don’t know. I’m just glad to hear that your case has dissolved itself now…
I’m the one thanking you, I’m truly grateful for your help.
Despite the error level being 0, I still had trouble opening up Dorico whenever the Komplete Kontrol file was in my VST3 folder. So I’ve uninstalled it, rebooted my computer, then deleted the .vst3 file and reinstalled Komplete Kontrol again through Native Access, as a way for it to generate a new Komplete Kontrol file in my VST3 folder.
Since then, Dorico is opening up just fine, with all my plugins into the VST3 folder, including Komplete Kontrol.
Once again, I’m thankful for your help. Have a nice day and take care.
You are more than welcome.