Well, looking at the data, resp. the absence of some data, it appears to me that you have the same problem as Marvin had, namely a corrupted SteinbergMediaBayServer.
Please go to /Library/Application Support/Steinberg/MediaBay and try to start the SteinbergMediaBayServer.app from there. Does it linger on or crash immediately? If it crashes, try to reinstall it, you can get it from the Steinberg website on the Support page in the Download area. One needs to take a close look but it is there.
Btw, it’s late here in Europe and I go to bed now, but will check here in the early morning again.
Hi @WimLas, I’m glad to hear your case is solved. That leaves the question, how could the MediaBayServer get stale? To be honest, i have no clue on that. What strikes me even more : Why do i suddenly have 2 the same cases basically right after another. I hope it’s not going to become more.
No coincidence this happens after latest Dorico update… ?
Although it worked fine for two days.
It must have been triggered by Halion. Normally I only use VSL and noteperformer. Right before opening Dorico this time, I loaded up one Halion Saxophone in Vienna Ensemble Pro. Possible?
Hey @Ulf can you please help me as well?
I have the same issue described here, Dorico 5 won’t start and waiting for audio engine to initialize. I attach the diagnostic file (I also tried reinstalling Halion with no effect)
Many thanks!!
Thanks for the data @madAlone .
There are no crash files contained so we need to find out step by step.
Please go to /Library/Audio/Plug-ins and temporarily rename the contained folders VST and VST3 to something else.
The same also do with the folder /Library/Application Support/Steinberg/Components .
Before starting up Dorico again, have a look at ActivityMonitor.app and make sure that no VST Audio Engine process is running. Then start up Dorico and see how it is behaving.
If it does start up properly, then it must be a “rotten” component or plug-in that is making trouble. Then we have to find out which one it is. Therefore, do it one by one by one, rename those folders to their original names and start up Dorico again. When it fails again, you know the folder where to look further.
I suspect it will be an old Steinberg component. If that is the case, take out all components out of that folder and put them one by one back and try to restart Dorico. That should identify the trouble maker.
Thanks so much @Ulf !!!
This was quick… I mean… since I was suspecting something about Halion (due to some other posts here) I started by removing the component “Halion Sonic SE.vst3” (from 2022) and it worked at the first attempt! At least… Dorico5 is correctly starting now… but I’m new to the program so I didn’t actually used it so far…
Any other suggestion at this point?
Thanks again!
Andrea
Hi @madAlone, good, so you only moved the old HALion Sonic SE 3.5 out, right?
From the diagnostics I can see that you already have the new HALion Sonic 7.0.20 installed, which is the successor to the old HALion Sonic SE 3.5.
If you now start in Dorico a new project from piano template and enter some notes, does it also play back correctly if you push the Play button?
Cool, then I guess everything is fine now. Should you find suspicious or odd behaviour in the future, please come back to the forum and we will find out.
Hi I have the same problem, on D 5.1.5 waiting to connect to the audio engine. I am on Windows, the diagnostics report does not run for me. Is there a new one for the latest version? some crash reports were sent to you automatically. I start Dorico, wait, then it gets terminated. When I start Dorico I get VSTaudioengine in the Task Manager. Dorico cannot start audio engine is what I get after a long wait. Dorico then closes and the VST entry is gone from Task Manager. Any suggestion what I can do please? I have diagnstics folders on my desktop - how can I send them if they are of any help?
Hi Ulf,
I recently installed Dorico Elements 5, and I also have the dreaded “Wait for audio engine initialization…” problem, so I can’t run Dorico.
My computer is a 6 year old Windows 10 PC.
Steinberg support have not been helpful. After sending the requested info he simply suggested updating the ASIO and GTX1080 drivers. I updated ASIO, but no joy. I’m unable to update the GTX1080. But as the problem is clearly linked to the audio system, I doubt updating the video drivers would help.
I’ve attached the info. I hope it helps.
Many thanks in advance!
Chris
Hi @cwright , welcome to the forum.
What exact version of Windows do you have? If it is older than Windows 10, version 1803 , then you need to update to at least that one. If you do, that error about SetThreadDPI… will go away.
Hi Ulf,
Thanks very much for the quick reply.
I have a very old version of Windows 10.
System Information gives:
Version 10.0.15063 Build 15063
I use an essential program (CryEngine 3). 5 years ago it stopped working because of a Windows update. Fortunately I was able to remove the update and CE3 worked again. Since then I have updates disabled to stop this happening again.
So, for now, I’m unable to update Windows because it will almost certainly kill CE3 again. If anyone has any ideas how to make Cry Engine 3 work on current Windows 10 or 11 I would be very grateful.
So, do you think there might be a way of fixing this Dorico problem without updating Windows?
Many thanks,
Chris
in theory, yes, one could find some workaround, but it would be sooooo hard and tedious. and would not justify the effort, especially because also the system requirements for Dorico 5 clearly state that you need at least the above mentioned Windows version. So from our side - sorry to say, but you will not get any further updates regarding your issue. We hope for your understanding.
Best regards
Ulf
yesssss! You’re the man! Thanks again 