Is there a way to limit the area of a manual condensing change so it doesn’t effect what comes after it? I tried selecting a few notes note but that doesn’t seem to work. At this point I am having to cancel each manual change with yet another manual condensing change after it.
I think you’ve got the right approach – like tempo changes, meter changes, note spacing changes, etc., a condensing change needs to be reset to return to the default behavior.
Thank you @asherber I’m glad to hear I am not doing this needlessly, but it means that I am basically reformatting all the condensed parts.
Whenever I need to create a condensing change, I like to create the reset/cancellation first so it doesn’t recalculate twice to the end of the flow. Particularly helpful in big projects.
Thanks for that great hint @ArianaConstantino I will do that next time; much better approach than what I am doing now.
(This is the same approach that many people take with things like Note Spacing changes.)
(Maybe you should give @ArianaConstantino the solution check mark for her great hint?)
Thanks asheber, I had intended to, but checked the wrong box. It’s corrected above.
Yes, its what I do for spacing changes thanks to someone else’s great hint quite a while ago! Hopefully I gave them proper credit.
And I’d prefer to select an area to apply a spacing change to, as well. I don’t like having to stop Dorico from doing this or that, but rather having Dorico do what I tell it to.
Another place where I think this method is crucial: manual staff visibility overrides.
Thanks, hrnbouma. “Crucial” is the operative word. I had no idea when I started doing the manual changes that they would affect everything that follows unless there was another manual change to stop it. Or at least that’s what it seems to do.
That’s exactly right. The software can and will automate many things for you but the moment you ‘know better’ and do any manual intervention it relinquishes all responsibility until further notice.
It would be nice, as you originally suggest, if there were a way to select a region and apply a change just to that region. Presumably Dorico would then insert the change and the reset itself, all in one step.
@hrnbouma I’m afraid that Dorico and I may be philosophically and temperamentally opposed to one another in the responsibility dept.
That system is actually what I had expected. And the same with the note spacing changes. I never seem to learn.
It’s probably because I think differently than Dorico. I want to just do something. It wants to do it for me, and then have me correct what it has done.
That latter seems to be particularly the case with condensing. I feel like I have lost all control over the score and am spending my time trying to second guess why Dorico did this or that so I can force it to do simple things like put two parts together on one staff.
Right now I am looking at the opening system of the 2 oboe parts which are on two staves despite condensing and the fact that the staves are empty but for three notes in Oboe 2. And the two oboe parts are together on the next system.
The only case I can think of where Dorico behaves like that — override and reset in a single action on a selected area, with two signposts at once — is ossias**. And I really like it 
Not working this way for Add/Remove Staff, nor for any of the cases you mentioned, unfortunately.
**Edit: it works for manual cutaways as well.
Can you share your project file here, or just the first part of it? Someone will be able to figure out what’s going on.
Clef changes (and octave lines) also. That’s probably completely different behind the scenes but not so different from a logical/semantical perspective, IMHO (i.e. applying a change to a specific range of music and automatically getting the reversal at the end).
True – and much appreciated as well!
Thank you very much, asherber. It wasn’t a big problem and easily solved with normal manual condensing. Just another head scratcher as to why it was happening and slight worry that I wouldn’t be able to fix it.
I did run into a real issue shortly after this one and posted it a few minutes ago: Missing note in Condensed Score, I think I called it. I posted a Dorico file of the passage. But it was a relief to at least get the note back into the score.
Later: Janus found a a hidden note that I had left there from an earlier experiment and that prevented proper condensing. Case solved. Mea culpa.
Thanks for pointing that out. Selecting something and applying a process to it seems like such a natural way to do things, at least to me.