I’ve been experiencing some severe slowdowns with Dorico Pro since updating to 5.1.51. Switching from Engrave to Write mode and back is glacial, as is switching from one instrument/score tab to another. This is happening on multiple projects, but I’m uploading the main one on which I’m having issues. Can you please help me with this? Thanks!
SymNo2_Mvt1_02_001n.dorico (3.8 MB)
The goods news is that there’s nothing wrong with your project file on my computer.
That means there’s something causing it on your setup specifically. You’ll need to attach a diagnostic report, so that the team can delve into the innards of what’s going on on your system.
Diagnostic report attached.
Dorico Diagnostics.zip (2.3 MB)
Fast here on a 2015 MacBook Pro.
Jesper
Fast on my M2 Mac Mini - but my Pro version did load as SE then, with Option held, as Elements until I’d done a restart.
The old saying goes, “It always starts working once the repairman takes a look at it.” For some reason, it’s sped up on me now after spending most of the day moving about as fast as a Snuffleupagus.
Still, I’d appreciate it if @dspreadbury or someone else at Steinberg would take a look at my diagnostic report and see if something was causing the slowdown earlier. Is there any chance of a repeat? Please advise, and thanks again!
It’s a macro-effect of quantum mechanics, in which the behaviour of an object changes by being observed.
It also happens in the other direction – things stop working when large numbers observe them. Most frequently with AV equipment in conferences.
I can indeed see that some commands, like switching mode, were very slow, but unfortunately the diagnostics don’t really give me any clues as to why that might have been the case. If you run into a problem like this again, you could try taking a spindump via Activity Monitor, zip that up, and attach it here. It’s possible that we would then be able to see what Dorico is doing when it takes so long to switch modes.
Not sure if to could be a reason for your temporarily slow down, but after some new installation or some changes in the system (new drive, new files in the drive, etc…) , MacOS needs to rebuild/actualise the Spotlight index. During that period of time (that can be very short or can take some time) the responsiveness of the System/Apps may be influenced.
(Just an idea…)
Okay, how would I do that? I’m on Win11. It started doing it again, and I had no clue as to how to do a spindump.
Ah, on Windows it’s a little different. I don’t recall exactly how to do this on Windows, as it’s many years since I’ve used that platform in anger (and it generally was in anger…). But I think you can use the Sysinternals utility Process Explorer, which you can download from the Microsoft web site, and you can sample a process by right-clicking it in the list of running processes to create a minidump file.