Dorico Adding Flows (not intended)

I’m sitting here watching the spinning ball, trying to manage Flows in Dorico.
I’m setting up a project. 11 Flows. I added the first one, set up the template, etc.
Then, I added 10 more Flows in the Info pane. Dorico gave the spinning ball, and when it stopped, there were 20 flows. Having learned from past experience to rename flows from the Setup>Properties panel, I renamed the desired 11, then undertook to delete the excess created flows. It took several attempts to get rid of them all. Spinning ball, big delay. Dorico struggles with this. Why?
#bugreport

Deleting a Flow is going to cause the entire Layout to be recalculated.

If there isn’t any music in it yet, then that shouldn’t cause any notable delay.

As ever, you’ll need to share the project file, or at least the Diagnostic Report, otherwise it’s not much of a bug report.

Dorico Diagnostics.zip (2.4 MB)
Steps to replicate:

  1. Create a new file
  2. Add 10 Flows by clicking the + in the Info panel 10 times - before adding any music.
  3. Spinning ball and chaos ensues.

Is it forum policy to respond to forum posts with insults and minimization?
Dorico is too perfect to be criticized?
This might be why Dorico gets a bad reputation for its forum culture and “better-than-thou” attitude.

I’m sure that Ben didn’t mean to be insulting or minimizing. He was just pointing out that it was hard to see what was going on without more information.

FWIW, when I follow your steps, everything works as expected, using Dorico 6.2.30 on Windows. I think you’re on Mac, so maybe there’s a difference there.

I followed your instructions literally and added the flows before even adding any players. Did you do the same, or did you add players first?

Yes. And, Dorico added 20 flows after 10 clicks…

Okay, so what players did you add? Or can you upload a new project with players that reproduces the issue when you add flows to it?

Double choir, deleted BB, added choir reduction for layout, 1 synth player holding 2 instruments (Omnisphere, 2 instances). piano also “holding” electric pieno pop rhythm section (g,b,d), string sketch staff. No music in the score, just started by adding what I’d be needing for the project. Am I not supposed to do this? Not long ago I did a multi-flow orchestral transcription project for a ballet and had lots of lag and problems dealing with the creation of flows after the fact, also experiencing that multiple flows were added when the intention was only one.
I’m on a deadline (as usual), so I don’t have time to create files and see when it happens and when it doesn’t. It’s just annoying as hell, and happens every time I have to deal with multiple flows and large scores.

I don’t think this is a common experience. Maybe the dev team can see something in your diagnostics.

I usually add and delete flows, not in the Project Info pane, but in the lower zone when in Setup mode. Clicking on this icon
Add Flow icon
will add a flow. Clicking on the trash can icon (or pressing Delete) will delete any flows which are selected. I found deleting flows this way to be very quick, especially when compared to deleting them from within the Project Info pane. No spinning ball, no big delay.

I was not able to reproduce the behaviour you experienced with unwanted extra flows being added, either in the Project Info pane or in the lower zone.

Apologies. Perhaps I was a bit curt, but I was trying to say that more information is required before we can help you get around the problem, and for the developers to identify and fix any bug.

I was certainly not implying that Dorico has no bugs, and I wasn’t trying to insult you.

This may very well be a dumb question but I have to ask it: have you checked whether your mouse might be acting up and registering single-clicks as double-clicks? If it’s producing rogue inputs that might also explain the spinning beach ball.

@jonburr the way @StevenJones01 describes lets you follow exactly what happens with each click. If you use that method and 1 click produces 2 additional flows than there probably is indeed an issue with the mouse. setting.

With so few instruments deleting a flow should be fast. So it really needs a bit of time for troubkeshooting.

Assuming that you already loaded your instruments in the rack and connected them with the players when you deleted the unneeded flows, try deconnecting them before deleting starting with the two Omnisphere instances and check if the deletion goes faster. In this manner you might find the culprit.

Much appreciated. I came in with a bit more steam than usual, I guess..kind of at the end of it with the difference in behavior between Setup and the Info window, among other things…

No, because I’m not getting the behavior anywhere else…