After updating my Mac Mini 2018 to macOS 13.4.1 every attempt to open second project results in Dorico hanging indefinitely. Just blank panel ‘Activate Project for Playback’.
The only way of continuing to work is to use ‘Force Quit’ for restarting Dorico.
This happens on every attempt with either playback template – HSSE+HSO (Pro) or NotePerformer
So, only one project at a time can be opened and worked on.
Here’s the Diagnostic report. Dorico Diagnostics.zip (1.3 MB)
And while on the subject of kinks, switching between ‘Write’, ‘Setup’, ‘Engrave’ and other modes can not be done with trackpad. Only keyboard shortcuts. But that’s just tiny kink.
I wonder if this is related to a PC issue I’ve noticed here on the forum? Dorico hangs when loading, giving this message “Parsing of online version check failed.”
This drove me nuts till I realized turning off both my antivirus (Defender) and Wi-Fi solved this issue.
(Yeah. I say that now, but watch. I prolly just jinxed myself!)
@IgorBorodin, could you please create, zip up and attach an Apple System Report?
This looks like a graphics driver issue of some kind, so determining what graphics adaptor you have in your computer would be a helpful starting point.
That’s the puzzling thing: while Dorico becomes completely unresponsive (including the possibility to quit) the Force Quit panel does not indicate ‘not responding’. And therefore does not create crash report.
The graphics card: Intel UHD Graphics 630 1536 MB
The only things that can potentially give a hint to what is the culprit - the problem with both panels (‘Activate Project for Playback’ and the Comments panel) appeared only after updating to macOS 13.4.1
Okay, but could you please run the Steinberg Download Assistant once and let it do its update, because along with it another for the common environment important component will get updated. And that will hopefully solve your problem.
@dspreadbury
Bingo!
Daniel, Bravo! You nailed it. ‘Metal’ was the culprit. Perhaps, Apple added something/altered something in that latest update to OS.
Still, puzzling that no other Dorico users have experienced that.
Once again, thank you very much for both the solution and the promptness.
Igor Borodin
I imagine that we will hear from other users with a similar system configuration in due course. I’ll talk to my colleague James about this problem – he may have some alternative things to try.
You’ll need to run Dorico using that Terminal command for the time being, each time you want to start it. You can create a text file containing the command you need to paste into the Terminal and save it with the file extension .command to make it into something you can simply double-click rather than needing to open Terminal and paste it manually.
One more question: while forcing the usage of Open GL did solve the problem, the Terminal shows multiple issues in executing the command.
Do you think the copy of Terminal output may be useful for your engineers?
To investigate this problem further, we would like to ask you if you would please try running Dorico 5 after setting the QSG_INFO environment variable, which will cause Dorico to dump out some more information to the Terminal. This command will run Dorico and then redirect the output to a text file on the Desktop. Please zip up and attach that text file here, or email it to me at d dot spreadbury at steinberg dot de.
