On 7/13/2018 2:25 PM, Kieren MacMillan wrote:
Hi Ben,
I probably confused you with my wording, sorry! I just meant it's above the
staff when it's supposed to be (in rare situations where dynamics are
technically different between the same instrument parts)...and then it's below
for the part 'extraction' single staff file. ;) Right?
Correct! In the score: dynamics unique to Flute 1 appear above the staff,
dynamics unique to Flute 2 appear below the staff, and shared dynamics appear
[once only] below the score; in the parts: dynamics appear below the staff.
Magic. =)
K.
________________________________
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: [email protected]
Question please:
Say you have a large orchestral piece, and for the majority of one
movement the flutes 1 & 2 share the same music. Suppose they have only
about 5-10 measures out of several hundred measures in the movement that
are different, requiring separate voices.
I know you can simplify and reduce typing of the music by using
variables and such, however I am wondering: how would you go about
setting up the instrument for Flutes 1/2, as well as Flute 1 and Flute
2? If you use temporary \\ backslash polyphony in those measures, that
won't translate to partcombine of course (because they would 'live' in
the same variable, so I can't do \partcombine fluteone and have it
work)...The only way to use partcombine then, would be to have two
variables correct?
So, how can you *not* re-type or copy-paste the music into the other
flute variable for partcombine? I'm looking at this the wrong way I
know, perhaps one of you could straighten me out.
I'd like to use partcombine throughout this piece so ideally I'd like to
keep the variables separate, but one movement out of the many do not
have the need for polyphony so I am unsure how to proceed. But is it
sometimes not advisable to use partcombine if the ratio of polyphony is
low? I'm wondering what the common consensus is of when to use
partcombine vs. when to manually single-variable input everything << >>
inline.
Thank you!
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
