Mats Bengtsson <mats.bengtsson <at> ee.kth.se> writes:
>
> I hope that you also have tried
> http://lists.gnu.org/archive/html/lilypond-user/2005-03/msg00035.html
That helps in the case where all the rests are staff-wide.
I'll guess an example says more than words:
\version "2.9.19"
\score {
\context Staff {
<<
s4-\markup{LilyPond default, rests in two voices.}
\relative c'' { c4 d e r | r2 e4 g | R1 } \\
\relative c'' { c4 b a r | r a g2 | R1 }
>>
\bar "||"
\break
<<
s4-\markup{Reverting rest direction}
\relative c'' { \revert Rest #'direction
c4 d e r | r2 e4 g | R1 }
\\
\relative c'' { \revert Rest #'direction
c4 b a r | r a g2 | R1 }
>>
\bar "||"
\break
<<
s4-\markup{Typographical convention}
\relative c'' { \voiceOne c4 d e \oneVoice r |
\voiceOne r2 e4 g |
\oneVoice R1 }
\\
\relative c'' { \voiceTwo c4 b a \oneVoice r |
\voiceTwo r a g2 |
\oneVoice R1 }
>>
}
\layout {}
}
The warning messages I get from 2.9.21 look like this:
rest-combine-2.9.21.ly:9:33: warning: Two simultaneous rest events,
junking this one
\relative c'' { c4 b a r |
r a g2 | R1 }
rest-combine-2.9.21.ly:8:33: warning: Previous rest event here
\relative c'' { c4 d e r |
r2 e4 g | R1 } \\
...and "junking this one" is incorrect in the above case. (Which is the bug
here. Combining rests in a staff would be a nice feature and would comply
with typographical convention at least for choral music, but that would be
a feature enhancement.)
Cheers,
--
Arvid
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
