Honestly, I think linked parts are very close to be good enough. What's lacking is
1. Unlinkable mid-measure clef positioning 2. Unlinkable vertical rest positioning 3. Special Tools for voice parts I haven't used voice parts enough (at all) to know what else may be lacking there. Cues are still a PITA no matter what, even in a separate parts file. But with the items listed above I think I could probably get by with just the two types of staff styles I described and never have to resort to phony expressions. On Wed, Jul 25, 2018 at 2:57 PM, David Froom <[email protected]> wrote: > Robert, > > Thank you!!!!!! This really solves my problems (as this score is large > chamber music piece, no staves with two to a part). This note is a > keeper!!! I KNEW there had to be a way! > > Sure would be nice if, after all these years of linked parts, Finale would > fix this. The Dorico competition on parts/cues is pretty impressive — > though they haven’t yet solved the two to a staff issue (and they have some > other half-baked things that prevent me from switching). They say they are > working on it. Let’s hope the fact that there is competition will jump > start some serious addressing of long-standing problems. > > Best, > David > > > On 25 Jul 2018, at 1:00 PM, Robert Patterson wrote: > > > > David, > > > > I switched to having a single document for score and parts several years > > ago. It requires a little more time, but I think it is worth it. To > address > > the issues you raised: > > > > 1. Do not use "Blank notation with rests: Layer 4". This staff style can > > occasionally be useful for partial measures (often for measures that > have a > > cue overlapping with a pickup note). But otherwise it isn't an ideal > > choice. Instead create a new staff style of Blank Notation with Rests for > > Layer 1. Then uncheck everything in "Other Layers: Show". In my files I > > name this staff style "Hide Cues". > > > > 2. For clef changes you'll need to create a separate staff style with the > > same transposition as the score (or lack thereof) but with a forced clef > to > > the clef you want in the score. You then apply that as needed in the > score. > > In my files I give them names like "Force Bass Clef" or "Force F Treble > > Clef" (if it were for a transposed horn staff). > > > > There are still occasional edge cases where even these two techniques > > aren't sufficient and you have to resort to using expressions for either > > rests or clefs. Often you can simply opt for a different cue. But me > being > > me, I sometimes soldier through with expressions when there is a > > complicated cue I think is really important. > > > > Another way to hide clef changes in the score is with a "Hide Clefs" > staff > > style. This is often a perfectly acceptable alternative to a forced > > transposition clef, if the cue is entirely contained on a single score > > system. There are occasionally situations where this is preferable to > > forced transposition clefs. (Since forced transposition clefs must be > > applied to full measure whereas hide clefs can be applied to a partial > > measure.) > > > > Christopher Smith is correct about voiced parts. They are not usable, and > > not just because of the problems with cues. Their inability to be edited > > with Special Tools is an unacceptable limitation by itself. Thus for > large > > orchestra scores I continue to maintain two files, but with a difference. > > The staves that do not split into multiple parts (frequently Timpani on > > down) reside with the score. The parts that do split (e..g, winds and > > brass) reside in a separate "distributed parts" file. Each file has *only > > those parts* defined. That is, the score file contains a Violin I part > > while the distributed-parts file does not. The distributed parts file > > contains a Clarinet 1 part but the score file does not. Of course both > > files have a score since there is no avoiding that. I ignore the score in > > the distributed parts file, except as a means for editing multiple > > distributed parts at once. > > > > Finally there are occasionally situations where a cue that shows in one > > part can cause another part not to create a multimeaure rest as you would > > like. It is for this that I created the Force option in my multimeasure > > rest plugin. The Force option places a multimeasure rest exactly where > you > > select, without regard to anything that might break it otherwise. (So use > > with caution!) > > > > Robert > > _______________________________________________ > Finale mailing list > [email protected] > https://lists.shsu.edu/mailman/listinfo/finale > > To unsubscribe from finale send a message to: > [email protected] > _______________________________________________ Finale mailing list [email protected] https://lists.shsu.edu/mailman/listinfo/finale To unsubscribe from finale send a message to: [email protected]
