I’m in an orchestral project with 30 flows now. The next ballet scene requires me to duplicate an early flow (#4) and use it to start flow #30. Dorico is having a hell of a time with this task. It seems re-ordering the flows causes it to bog down. On a new Mac Studio (86gb ram), it took close to 3 minutes of spinning ball, and that’s after a crash.
Creating new flows at the end is no problem - but whenever I need to re-sequence, it takes forever or crashes Dorico. Is this a known issue?
Issue #2
Also, I need to rename the Flows (in addition to just the Flow number) so I can identify them easily in Setup. That’s another thing that Dorico seems to struggle with, causing a wait and a spinning ball on a fast new machine. And, whenever I rename a flow (by pasting its Title into its name field in the list on the left, so it shows up named in Setup Mode>Properties), that causes the focus to revert to the Project rather than the Flow currently in process. I wonder why the Flow Title doesn’t automatically populate the Flow name as it appears in Properties? And why changing its name in the Info panel causes Dorico to bog down?
This is known issue with Dorico. The best option so far is to deselect any flow that you are not working with so the memory is devoted to just what you are currently working on. Dorico has this tendency to keep track of collisions all the time and it makes it slow. If Condensing is on, turn it off too. Leave it all off until you are ready to make final adjustments
I’m already aware of this, and manage it by working on Custom Score Layouts (one with my prefs for working on it, the other a delivery score with condensing etc active, which I use to export to the client) with only the current Flow active - but, as I build the project, more than once I’ve needed to re-order the Flows in the Info window, and that’s where the issue arises. In that view, Dorico is only “looking at” the Flow list.
I’ve seen things slow a bit, but not had crashes moving flows or renaming them.
What playback template are you using? Large expression maps can actually have an effect on the speed of layout, because it has to recalculate all the changes of expression.
So these calculations are done on the entire project with every change in Flow order, not stored with the Flow?
So having all the Flows active in the Full Score layout will cause these delays no matter if you’re working on a Custom Layout?
I’m using an Automatic template with a few minor additions. It’s just regular orchestral stuff.
I don’t know what triggers a recalculation – certainly, adding notation will do it, obvs. But it’s certainly true that heavy expression maps can affect speed. If you’re using the Auto, then it’s probably not a factor in this case.
If you have got crash logs, or Diagnostic Reports, you should upload them so the team can see what’s going on, and identify the problem if it’s a local issue; or make a fix in a future version, if needed.
