>> E.g. in this instance, I would have liked to keep the drone notes and
>> the
>> melody notes together (i.e. in the same file) because they both are
>> the
>> bagpipe "content".
>> But that, as we've seen, that makes it difficult to separate the
>> printed
>> from the midi output; hence I had to *separate* contents that belong
>> together (i.e. create the "drone" staff) and then use "\tag"...
> No, that's not true. There's a difference between having them in the
> same file, and having them in the variable. You can have a variable
> drone = {music} and a variable pipes = {music} in the same file.
I had exactly that: 2 _variables_.
> And
> then your score has \new Staff <<\drone \pipes>> or not.
I cannot have that (i.e. it's a personal choice to minimize the number of
changes from one project to another) because the "Staff" is exported from
the "contents" file: Hence at the score level, I just want to see a variable
"\staves" (which is a "StaffGroup"); but no reference to the internal
"drone" or "pipes".
Admittedly, there might be a better way to organize the layout/contents into
multiple files but if I'm not mistaken, there is a huge gap between the
examples in the manual or LSR (where everything is crammed into a single
file) and frameworks for large scale projects. [Some proposals have been
talked about in this ML (e.g. Nicolas Sceaux's) but they are not (yet?)
integral part of LilyPond.]
In-between these extremes, there are many different aproaches, but not one
considered to be the final "normalized" LilyPond template of templates...
Best,
Gilles
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
