Hi all,
I’m trying to right indent the first system of a flow (which is meant to have one bar in it), and I’m trying to use frame breaks to do it in all in one flow, which is giving me some confusing results. I can work around by using separate flows, which has some other benefits, so it’s fine, but I want to document the behavior I’m seeing.
For context: this is a piece for solo multi-percussionist. I’ve set up the project with 5 different ‘players’ (one for each instrument) instead of one, mostly to allow me to make simpler flows if I do have to split up the piece into different flows.
When I make the frame for the first bar in the flow, I can’t seem to convince it that the correct number of systems to put in the frame is 1. I would expect to be able to do this by limiting the height of the frame, but whatever height I give it, the frame produces two systems, often with the second going below the bottom of the frame (which allows collisions with the frame below). I’ve attached a screenshot (it doesn’t show the collisions or the shortened frame, apologies; I can re-make that if desired).
I would expect that at this point frame breaks would come to my rescue. But when I insert the frame break I don’t get my expected behavior (the second bar going down to the next frame). I get the first bar disappearing out of the first frame entirely. The two bars do use different instruments, but apart from that I can’t figure out why this is happening. Trying to use the “make into one system/frame” options doesn’t seem to help either. I’ve attached a screenshot of this as well.
What I did get to work was making a different flow for just the first bar, allowing frames to pick up the next flow on the same page, and just letting Dorico’s automatic handling of a tailing bar at the end of a flow handle my right indent. This is a functioning workaround. I’ve attached a screenshot of this as well, including the measure numbers starting over at each new flow.
If I’m missing how to make frame breaks do what I want them to do, I’d be grateful for advice. If this is helpful documentation of a behavior, I’m glad it’s useful. Either way - thanks for both the advice and the great software.
