bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 760 in lilypond: Feature request: polyphony shortcut could be


From: James E. Bailey
Subject: Re: Issue 760 in lilypond: Feature request: polyphony shortcut could be better
Date: Fri, 6 Mar 2009 14:10:20 +0100


El 06.03.2009, a las 13:54, Valentin Villenave escribió:

2009/3/6 James E. Bailey <address@hidden>:

\version "2.12.2"
musOne = \context Voice = upperOne \relative f' { f4 <<{g a}\\{e d} >>f }
musTwo = \context Voice = upperTwo \relative f' { f4 <<{\voiceOne g
a}\context Voice = lowerTwo {\voiceTwo e d}>>\oneVoice f }
lyr = \lyricmode { This text splits here. }

\score {
       <<
               \new Staff \musOne
               \new Lyrics \lyricsto upperOne \lyr
       >>
}
\score {
       <<
               \new Staff \musTwo
               \new Lyrics \lyricsto upperTwo \lyr
       >>
}


I'm not sure how such an example could be handled automatically, since
you're using manual Voice naming for your \lyricsto instructions.

I should try again and search for Mats' example I mentioned.

I'm of the opinion anything Mats does is better than anything I do. The goal is that <<{}\\{}>> doesn't create two new voice contexts, but rather keeps the first one active, and just creates a second new voice context. Remember that the goal here is that one voice is consistent throughout. I guess I could have used the \voiceOneStyle, in which case, the example would be:
\version "2.12.2"
musOne = \context Voice = upperOne \relative f' { \voiceOneStyle f4 << {g a}\\{e d}>>f } musTwo = \context Voice = upperTwo \relative f' { \voiceOneStyle f4 << {\voiceOne g a}\context Voice = lowerTwo {\voiceTwo e d}>>\oneVoice f }

\score {
       <<
               \new Staff \musOne
       >>
}
\score {
       <<
               \new Staff \musTwo
       >>
}



reply via email to

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