bug-lilypond
[Top][All Lists]
Advanced

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

Re: Possible bug with \oneVoice involving rests


From: Phil Holmes
Subject: Re: Possible bug with \oneVoice involving rests
Date: Mon, 2 Jun 2014 08:49:40 +0100

"Urs Liska" <address@hidden> wrote in message news:address@hidden
Am 02.06.2014 09:33, schrieb Brian Eve:
{
\clef bass
\compressFullBarRests
\override Rest #'staff-position = #0
   R1*6
<<
{
   \voiceOne g4. f e4 }
   \new Voice {
   \voiceTwo e4. d d4 }
>>
\oneVoice  a1
   R1*6
<<
{
   \voiceOne b8 }
   \new Voice {
   \voiceTwo e8 }
>>
   r8 r4 r2
   R1*6
   R1
   r
   R
}

No, it's because in that form of temporary polyphonc section the first of the parallel voices is continued after the >>

In your example that's \voiceOne.

So you have to provide a \oneVoice after the >>
That's intended and documented behaviour.

Best
Urs

It's probably worth mentioning that using

\override Rest #'staff-position = #0

is disguising the problem with the non whole measure rests. It would probably be better to get the voicing right than use this override. However, it's also worth mentioning that the override does not apply to whole measure rests. For this you need MultiMeasureRest.staff-position : see http://lilypond.org/doc/v2.19/Documentation/notation/writing-rests#full-measure-rests for more details.

--
Phil Holmes





reply via email to

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