Dorico cannot connect to the audio engine

Dorico
62

Hi @ivanbfowler , welcome to the forum.

Thanks for the data, contained are plenty of audio engine crash dumps, and they point at HALion Sonic as the culprit.
But I can also see that you are slightly outdated. You have Dorico 5.1.51 but the most recent one is 5.1.81. Also your HALion Sonic is a bit outdated; you have 7.1.0 but available is 7.1.20.
It’s no guarantee, but I’d say that if you bring those two to the latest version , the crashes will be gone.
So please launch the Steinberg Download Assistant, in there go to the Dorico section and install the first 2 items you’ll see in the list of components. And then let’s see how Dorico behaves.

1 Like
63

Thanks for your answer. I’ve tried to launch it several times, but it gives me the following message:

image
image624×234 21.3 KB

However, my internet connection is working fine. Not sure how to procede.

64

It’s likely that your Steinberg download assistant software is also out of date. Update it here:

65

I get the same alert, and the only time I can get the application to work is when I remove all vst3 plugins apart from the Steinberg plugs from the common files/vst3 folder. There’s something in my vst3 folder causing the conflict, and no, it’s not an early version of Halion Sonic SE.
Is there a way to block all 3rd party plugins without running the scan process. i.e. The Blacklist xml file, but without actually typing every single plugin name? If so, what would the wildcard and/or syntax look like in such a script?

Cheers

66

Hi @bossa , sorry to hear about your trouble.
Unfortunately we don’t have such mechanism, yet, though I’m planning to implement something like that (finally).
But until then we have to find the culprit among the plugs. It’s a bit tedious but in the end quite quick; I don’t know exact term for it, but I’ll call it the half-half method. So you cleared out the VST3 folder (except for the Steinberg folder), now you take half of the other plug-ins and put them into the VST3 folder and start Dorico again. If it is successful, then you again take half of the remaining plug-ins and do the next round of iteration. When Dorico does choke again then you know that you added the bad plug with the latest iteration. In that case you take half of the last iteration out again and continue with the next iteration.
You see, with this half-half approach you will quite quickly find the culprit, even if you have hundreds of plug-ins. Makes sense?