I just wanted to know if someone have found efficient workarounds about Dorico slowness.
In fact, there is some irritating latency (between each note you enter) with a simple Modern Orchestra template.
I’d would like to know why because I’m abble to orchestrate in a decent way in MuseScore : full score in front of me with no latency.
Is there a performance boost planned for the next update ?
Condensing turned off.
Tested on two computers, same result.
One is a 12-core 2,66 with 32 Go RAM and SSD.
Again, I dont think the computer is the problem since MuseScore 3.6.2 runs without laggy interface…
Latency (about 0.25s) increase with smaller note values and more staves.
Change the pitch of a note (in the Rite of Spring posted on this forum) and latency becomes a problem.
I’ve seen other posts / reviews speaking about Dorico slowness then I think I’m not alone.
I search for solutions…
Any tips appart from writing for each section at a time after having saved the layout and restarted Dorico ?
I’m just going to quote Paul, as I can’t put it better:
From what I understand, you’re trying to run Dorico on a machine that was powerful, what, eight years ago? I can’t find an exact comparison at Mac Benchmarks - Geekbench Browser but the fact of the matter is that things have come along quite a way in computing terms in the past decade.
…and things have improved since Dorico 3.0, certainly, and Dorico 3.0 had performance improvements over 2.0 (with the exception of condensing). There’s a limit to what Dorico can improve in speed without compromising in terms of what appears on the page/screen.
You should find Galley View faster than Page View, for editing notes, I believe.
If you’re working on a file with multiple flows, at least historically Dorico was faster if the Layout Option was set to have each flow starting on a new page.
And if you have multiple tabs (different layouts) open, close the ones you’re not using.
Same thing with oboe 4 part only.
I think the “save layout and restart to boost performance” could be solutionned by the team. No ?
In that scenario editing string section would only recalculate local gallery section score … Is there another solution ? Fingers crossed !
After entering more and more notes, restarted Dorico with oboe4 part on the screen latency becomes ok.
I dont understand … But it seems to work. Maybe not with 400 bars completed… who know ? Very strange…