Am 17.12.2013 11:16, schrieb Trevor Daniels:
Urs Liska wrote Tuesday, December 17, 2013 9:01 AM
However I noticed a behaviour I wouldn't have expected:
Try out the following snippet:
soprano = \relative c' { c e g c }
verse = \lyricmode { This is my song }
\score {
\new Staff <<
%\soprano
{ \oneVoice r4. r4 r4. }
\new NullVoice = "aligner" \soprano
\new Lyrics \lyricsto "aligner" \verse
>>
\layout {}
}
The rests are placed wrongly, obviously avoiding _something_.
NullVoice has had a checkered history, and has never worked
perfectly in all situations. The current implementation is the best
so far, but still has a restriction which I quote from the NR:
"The NullVoice context must be inside a Staff context, and should
only contain notes that are already being displayed in that staff, and
in the same octave. Otherwise the NullVoice may interact with the
printed voices in unexpected ways. For example, arbitrary notes in
the NullVoice may cause accidentals to appear (or disappear) on the
staff."
and implied, I think, "at the same musical moment".
See
http://www.lilypond.org/doc/v2.17/Documentation/notation/techniques-specific-to-lyrics#index-NullVoice
It looks like you have found a further restriction relating to rests.
Trevor
What about changing that to
"For example, arbitrary notes in the NullVoice may arbitrarily move
rests or cause accidentals to appear (or disappear) on the staff."
?
Urs
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
