Multimeasure rests - how to keep them splitting in parts

[blueshift]

Split measures and rehearsal numbers are turning large portions of tacet measures into a mush of varying numbers - is there a way to make Finale ignore these (without messing up measure numbers)? The split measures are a standard organ convention for versified music - so #3 should look like #2

Finale 25.5
Mac OS El Cap

[motet]

The split-measure plug-in makes one measure into two measures with different (hidden) time signatures and a hidden barline, which will break multimeasure rests, so you may be out of luck. But why are you splitting the measures? Normally one would only do that if a measure is going to span two systems or you want to have a mid-measure key change. (I am ignorant of the organ convention you mention--say more.)

[motet]

Or do you mean you're just showing a whole and a half rest in the measure (as opposted to splitting it with the plug-in)?

[blueshift]

In the choral / organ world splitting measures is standard procedure. Pick up any hymnal, or an anthem book, and you will see that many (if not most) employ split measures, which helps with phrasing. (eg, you might find a 4/4 setting of an anthem starts with a one beat pickup, and ends on a dotted half - the next phrase then starts with the pickup, but the measure is split - sometimes for da capo, other times for a page break or system break.)

In the past, I usually resort to using extracted (unlinked) parts, which I can grok into final form, but this means any update to a score means going back and repeating the process. It's maddening and time-consuming. Been doing it this way in FInale since 1993.

[Peter Thomsen]

blueshift,

Instead of splitting the measures (using the plug-in Split Measure), have you tried using Horizontal Split Points?

As you know, the Split Measure plug-in changes one measure into two measures.

When using Horizontal Split Points, the measure remains one measure.
This means that you can have a multimeasure rest that “straddles” the measure with Horizontal Split Point.

[blueshift]

Pushing the split into the next system discombobulated pagination in the score in a way I couldn't seem to fix, though it worked in the parts.

But here's a grok (or an undocumented feature) that did work: In a split measure, I put out-of-range hidden notes in each measure then connected to a ligature. (eg, in a split 3/2, a whole note tied to a half note.) Then in the part, they could be combined with the rest. (I also removed a couple extra splits from my original example - only one was needed.)

The hidden ligature trick


The result

[Peter Thomsen]

Pushing the split into the next system discombobulated pagination in the score …

By your word “pagination” you mean Page Numbers, right?

I do not understand how pushing a split into the next system could affect Page Numbers - a Page Number is a Text Insert.

[motet]

Is there any way with this feature to see which measures have them and where they are in the measure?

[blueshift]

By pagination, I mean after using the split points, then pushing the segment to the next system resulted in each individual measure following the receiving system each spanned an entire page. Up arrowing (to force measures back) at that point had no effect. After a few minutes, I decided that grokking was more effective than debugging - so I tried the ligature.

Motet - I used the split measure as normal, then did the hidden ligature trick. It lays out in the score and on your screen just like a split measure (only now it has that weird thing i created), but now can be included in an unbroken multimeasure rest.

[motet]

The pagination problem is because you have a hardwired page break attached to the following measure.

[blueshift]

Motet, I was struck by your avatar - this is the piece I am making an arrangement of