bug-lilypond
[Top][All Lists]
Advanced

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

Re: Spacing/collision behaviour of NullVoice


From: Trevor Daniels
Subject: Re: Spacing/collision behaviour of NullVoice
Date: Tue, 17 Dec 2013 10:16:32 -0000

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



reply via email to

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