Le Fri, 1 Jan 2010 17:30:19 -0800 (PST), mike99 <mike.br...@gmail.com> a écrit :
> Fair enough, but there are the lyrics, set here to the soprano voice,
> which, unintended by myself, skips the fourth beat in the second
> measure. In the documentation's first example on divisi lyrics
> (Notation Reference, 2.1.4, version 2.12), it does not, because the
> authors have explicitly created a new voice.
Yes, this is clearly a limitation of the << \\ >> construct: voices
within that construct are considered as voices both different as the
voice outside this construct.
This is not the case with
<< { \voiceOne ... }
\new Voice { \voiceTwo ... } >>
since the first voice in this construct is considered as the
continuation of the voice outside the construct.
> If such a technique is required for all exceptions to the chord
> structure, it seems as if the "chord method" could become patchwork
> if many exceptions are needed in a piece. Ten exceptions might be
> common on a one-page hymn, requiring the creation of as many new
> voices.
You can use \context Voice = "splitapart" for the second "exception"
voice (instead of \new ...). So you have only 2 voices created. ;-)
> With consistent technique it should be doable; for commonly occurring
> exceptions it should even be possible to define some clever commands
> that reduce clutter. Extra work in any case.
Actually there is a project to rewrite << \\ >> so it behaves like with
"explicitly created voice construction".
http://lists.gnu.org/archive/html/lilypond-devel/2009-09/msg00096.html
Let's hope this will be done, so for cases like this one explicitly
created voice construction won't be necessary. And << \\ >> is a
considerably reduced clutter for that. ;-p
> Enter my question: What is your opinion to the two methods, given the
> direction of the project and in terms of readability and
> complications that it would cause in the score?
I'm not used to write vocal scores, sorry.
Cheers,
Xavier
--
Xavier Scheuer <x.sche...@gmail.com>
signature.asc
Description: PGP signature
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
