Once the part is optimized, you can edit the staff name for individual staves and not affect the others. Or is that group names? I can't remember, but you will be able to change the labels so they are correct.
M. Perticone wrote: > hello list, > > i need to solve something closely related to this thread. > > i would put two parts in a single staff, say, flutes I/II. but some passages > are too way polyphonic and complex, so sharing the same staff would result > in a messy layout. i know i can write those parts in two different staves, > and at last, optimizing would hide the the non-used staff. but as you can > see, i would have to accomodate those parts in a single page, and a problem > with staves names remains, as the first staff will say flutes I - II, and > the other one, flute II. is there a better choice or procedure? > thanks in advance for any advice, > > regards, > marcelo > > > > ----- Original Message ----- > From: David H. Bailey <[EMAIL PROTECTED]> > To: Alain Mayrand <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Friday, July 12, 2002 8:15 AM > Subject: Re: [Finale] orchestral efficiency > > > >>Orchestral instrumental parts are not always printed on separate staves, >>so perhaps you need to rethink your modus operandi. >> >>Often Flutes 1 and 2 are on the same staff on a single part, same with >>most woodwind and brass parts. So the horn parts are often Horn I/II >>and III/IV in newer works and Horn I/III and II/IV in older works, >>making two staves in the score and only two printed parts (with copies, >>of course so each player gets a part to practice from.) >> >>My opinion as a conductor, is that I can work most easily and quickly >>when my score shows EXACTLY what the instrumentalists see, so if my >>score is horn I/II on a single staff, the instrumentalists should see >>the same on their parts. That way I can more clearly be sure we all >>understand which part should play which notes. >> >>That should make your inputting job much easier. >> >>If for any reason you feel the parts need their own staves, and maybe >>even their own separate pieces of paper, what you would do would be to >>create your score the way you want it (i.e. multiple parts on single >>staves) and then extract the parts to their own files. >> >>Then, to keep on with the horn I/II example, you would open the part >>file and then you would explode the music so that each horn part was on >>its own staff and from here you would extract the second staff to its >>own file and then delete the second staff from the hornI/II file. >> >>But by all means get the score to look exactly as you want it -- it has >>been my experience that it is far easier to work with extracted parts >>than to create a score to extract parts from and then from that score to >>attempt to force it into my desired end result. >> >>Others may feel completely different on this issue, and I do hope others >>chime in with different working methods. >> >> >> >>Alain Mayrand wrote: >> >> >>>Hello all, >>> >>> >>> >>>I have been trying to develop a better working method when it comes to >>>inputing orchestral scores. I have been using lots of keyboard shortcuts >>>and macros (thanks to Tobias' tools) and whatever can make the job >>> > easier... > >>> >>> >>>I am, however, still unsure about what is the best layout for my score >>>from which to extract parts. I am currently writing the score with each >>>instrument getting its own part, so that extracting the parts will be no >>>problem. But then my score has an unusual format since it has four horn >>>lines, 3 trumpet and trombone lines and, well, you get the picture. I >>>can then (with some noodling) combine these parts unto one staff to make >>>a more readable score, but I am not sure this is the most elegant >>> > solution. > >>> >>> >>>I hope I explained my dilemma succinctly enough but with clarity. >>> >>> >>> >>>I hope we can share working methods for inputing orchestral scores. >>> >>> >>> >>> >>> >>>Alain Mayrand, composer >>> >>>www.alainmayrand.com <http://www.alainmayrand.com> >>> >>> >>> >> >>-- >>David H. Bailey >>[EMAIL PROTECTED] >> >>_______________________________________________ >>Finale mailing list >>[EMAIL PROTECTED] >>http://mail.shsu.edu/mailman/listinfo/finale >> > > > _______________________________________________ > Finale mailing list > [EMAIL PROTECTED] > http://mail.shsu.edu/mailman/listinfo/finale > > -- David H. Bailey [EMAIL PROTECTED] _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://mail.shsu.edu/mailman/listinfo/finale
