I recently got Dorico se, but it won’t run. I’m using Windows 11.
There are a number of problems.
Halion sonic also seems to have problems with folder setting.
At first, audio engine loading was the problem, but now the audio engine issue passes, but it seems that the program automatically turns off after loading.
I’m writing again as I don’t seem to have permission to edit or delete posts.
Dorico shuts down automatically. When I run Dorico, it waits for about 30 seconds at the audio engine loading screen (initially it got stuck here, but after installing and uninstalling a few programs, the issue was resolved. However, I’m not exactly sure why). Once everything is loaded, nothing remains in the taskbar, and the program doesn’t run as if nothing happened.
I am using Windows 11.
I am a Cubase user, and I have no issues running Cubase.
I’ve tried several things. I moved the VST3 folder, closed the VSTAudioEngine, waited and then tried running Dorico again. I also stopped processes related to audio and disabled audio-related devices in the Device Manager before attempting to run the program again, but all of these failed. Then I installed Dorico 4, and surprisingly, Dorico SE 4 runs without issues. I wanted to try the free version first because I was interested during the sale period, but there’s an issue. I’m even more disappointed that it stopped working after an upgrade, but I suppose I should be glad that I can still use Dorico.
In Dorico 5, the fewer plugins I had in the VST, the faster the loading was, but regardless of that, the program automatically shut down after all loading was completed, so I couldn’t get any report.
@B.Lab, if Dorico 4 runs on your computer but Dorico 5 does not, there’s a good chance that the issue is caused by a change in the way the underlying Qt framework is addressing the graphics card in your system, which has changed between Dorico 4 and Dorico 5.
Can you tell me what specific make and model of graphics card you have in your PC?
When you unzip it, a single file called CreateDoricoDiagnosticsReport.bat will be created. Double-click that file, and a zip file called DoricoDiagnosticsReport.zip should be created on your desktop. Attach that here.
I disagree with Daniel’s assumptions about a graphical driver issue. Looking at the audio engine logs, it appears that the audio engine deadlocks itself somehow. So I would investigate into that direction.
Therefore, please rename the folder
C:\Program Files\Common Files\VST3
to something else like e.g. _VST3 thus making the folder invisible for Dorico.
What happens when you then start Dorico?
Your suggestion is to change the path from ‘C:\Program Files\Common Files\VST3’ to something like ‘C:\Program Files\Common Files_VST3’, right? When I do that and run the program, I get a message saying Halion Sonic installation is required, and then it closes.
Right, the window that pops up there is just an alert; Dorico shall function even if HALion Sonic is not around. So you click on the OK button there and then everything disappears? Can you open the Activity Monitor and in the process list check if either Dorico or VST Audio Engine processes are listed and if so, what status they have?
Okay, so Dorico crashes but the audio engine lingers on.
The diagnostics you’ve posted before don’t contain any crash dump files.
Could you please have a look in your Documents folder, there should be a Steinberg folder inside and in there a folder called CrashDumps. Is it there and is there anything inside? Please zip up that folder and also post here.
Thanks.
And a note in general: When Dorico crashes and an audio engine process remains running, you better kill that off before running Dorico anew.
Hello, I finally solved the problem.
The cause was in a place I hadn’t expected, and it was resolved so easily that I feel a bit anticlimactic.
Recently, one of the HDDs I was using failed, and coincidentally, my document folder had been assigned to that HDD. When the HDD failed, the folder path got messed up, and even after reinstalling Windows, the path didn’t reset properly, so the problem persisted. I simply changed the document folder location in File Explorer, and that fixed everything.
Although you didn’t find the direct cause, I really appreciate your effort in helping me figure it out. Thank you Ulf!