To make it short: LilyPond has a totally different approach to
"extracting" parts. And I'm sure it will serve you well.
Basically you store your music in variables (e.g. one variable for each
"part", say "violin 1" or "soprano").
Then you put them together in a \score { } expression, stacking and
nesting staves and putting (one or more) voices in staves.
And then you can put them in another \score { } expression in another
file to produce the single part.
Of course there is some practicing involved, but in the end I'm sure
this is much more reliable and versatile than with GUI programs where
you write a score and "extract" the parts.
HTH
Urs
Am 08.01.2015 um 22:10 schrieb Matthew James Briggs:
Hello, I just joined this list because I was searching unsuccessfully
for information about Lilypond's features for extracting and producing
individual parts from a score. Does Lilypond have features akin to
Finale's linked-parts?
I suspect my searching was unsuccessful since the work "part" is used
so frequently in the english language. Any urls to point me in the
right direction would be great.
Background: composer using Finale since the early 1990's. In the past
several years I have learned some code, C#, C++, SQL, tiny bits of
bash. I don't know Python yet but it's on my to-do list.
The idea of controlling music notation with the precision of an
interpreted text language is highly appealing and I plan to learn
Lilypond soon (unless it has, like, zero support for creating parts).
Thank you!
Matt
.mjb
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
