Hi. When I turn on my computer and then open a Dorico project, Dorico responds very slowly for every click I make. It is so slow that the program shows “Not responding.” The solution to this issue is to quit Dorico and reopen the project.
Does anyone know any other solution to my issue?
Next time you run into this, please make a note of the time at which you first ran Dorico and experience this slowness, then restart Dorico, and then do Help > Create Diagnostic Report. Each run of the application will produce a log that will be included in the diagnostic zip file, and which might possibly give us a clue as to what is going on.
If you start a brand new empty project, does that behave in the same slow way as the existing project you’re working on? If the problem appears to be localised to a specific project, that would also be useful to know.
Dorico Diagnostics.zip (842.0 KB)
Thanks for your response. Please find the attachment for the diagnostic file. I imported a musicxml file to an existing project, and then Dorico started to behave slowly. I closed Dorico and restarted it, Dorico said that the audio engine died and cannot connect to the audio engine and created the diagnostic report for me.
The issue occurs when I import musicxml or midi and when I create a new project, but it does not occur if I save the project, exit Dorico, and reopen the project.
Dorico will not behave slowly when I scroll the staff or save the project. I think it only behaves slowly when I click the notes, so it may be related to the vst engine.
Thanks for the diagnostics. I’ve had a quick look through the logs for the last 10 runs of the application (which are all that is included in the diagnostics) and I can’t see any evidence of any commands taking a particularly long time.
Can you keep track of exactly what time you next encounter this problem, and then create a fresh set of diagnostics after continuing to work with Dorico for a few more minutes at that point, and attach it here?
Also, can you provide any details about your computer hardware?
Thanks for your help. I am using Windows 11 on an i3-10100T CPU with 16 GB memory and 1 TB hard drive. I use the motherboard’s onboard audio interface.
Another piece of information I can offer is that this issue did not occur when I used Dorico SE. It happens after I upgraded to Element.
Your computer is not especially powerful, but unless you’re working on very large projects, it should be sufficient.
Please keep track of the exact time you next encounter very slow behaviour, and provide a new set of diagnostics together with the time you noted down.
Dorico Diagnostics.zip (904.6 KB)
It seems to be the VST problem. Please kindly check the attached diagnostics file.
You haven’t provided much in the way of information that would help me to diagnose your problem. You haven’t said what became slow, for example, or at precisely what time the slowness began. I’ve had a look at the logs for the last couple of runs of the application, and can’t see anything especially problematic.
One thing I can see is that the most recent time you ran Dorico, the audio engine wasn’t able to start correctly. That’s because you quit Dorico and then immediately restarted it less than a second later. If you do that, the audio engine will not have enough time to shut down cleanly before Dorico asks it to start up again. So if you quit Dorico and want to restart it, wait a few seconds before you try running Dorico again, so that the audio engine has time to shut down completely.
A wake lock issue? On the FInale forum, a particularly tech-knowledgy commenter notes “Many of us do not use USB 2/3 external drives for this reason—they sometimes don’t wake from sleep.” This can include a USB2 iLok - and also drives and hubs.
Caveat: I know nothing about the dragonedison’s sytem so this may not be the problem. But it is mine and I need to make sure I close all my audio apps before I turn off the lights for the night.