lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Keep alive together - call for use cases


From: Malte Meyn
Subject: Re: Keep alive together - call for use cases
Date: Thu, 18 Aug 2016 15:33:25 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0



Am 18.08.2016 um 15:10 schrieb David Kastrup:
Malte Meyn <address@hidden> writes:

Am 18.08.2016 um 14:16 schrieb Mark Knoop:
Could you both take a look at this and see (a) if it helps, and (b)
what else needs to be achieved.

I didn’t read the whole thread but how to deal with different clefs?
For example, in a choir a tenor is notated with \clef "treble_8" but a
tenor/bass combined staff with \clef "bass". This case isn’t a problem
because lilypond uses the clef of the bass voice (two \clef events at
the same time, second one is used). But maybe there are cases where
you would want have the clef of the upper voice (f. e. horns in
octaves, one in treble, one in bass clef, combined in treble clef with
ledger lines for the lower horn)?

So?  The whole point of the layers is that you (more or less fully)
prepare both a split and a combined version and LilyPond then picks the
right layer.  Split and combined layer don't need to have the same
source and/or overrides: you can use an alto clef for the combined
version and violin/bass clefs for the split version if you want to.

Of course you will _largely_ want to share the same source, and tags,
variables, and parallel music expressions will help with that.

Hmja, so weit hätt ich mal denken können …



reply via email to

[Prev in Thread] Current Thread [Next in Thread]