Re: The built-in template satb.ly fails in 2.19.16

[Trevor Daniels]

David Kastrup wrote Saturday, March 14, 2015 7:28 AM


> "Trevor Daniels" <address@hidden> writes:
> 
>> I've just noticed that the examples of using the built-in template, satb.ly, 
>> in the Learning Manual, see
>> http://www.lilypond.org/doc/v2.19/Documentation/learning/built_002din-templates
>> are not correct in 2.19.16.
>> Does anyone recognise any changes in 2.19.16 which might have affected this 
>> macro?
>> (There have been minor changes to this in current master, but both fail the 
>> same way.)
> 
> Pretty likely issue 2010
> <URL:https://code.google.com/p/lilypond/issues/detail?id=2010>.
> 
> I think it requires associated voices to either be in the same << >>
> block as their lyrics.  Or something like that (if they are not
> accompanied by any non-associated context in the << >> I think that's
> also ok).

That seems to be it, sort of.  Below I've simulated the
rather bizarre structure the satb.ly template generates.
This causes the last three notes of the Soprano line and
all the lyrics to vanish, although no error is generated.
If the \dynamicUp command is removed or the double nesting
is removed (the latter by commenting the two lines
indicated) it works correctly.

\version "2.19.16"

\score {
  \new ChoirStaff <<
    { <<
      \new Staff = "Descant" {
        \new Voice = "Descant" <<
          \dynamicUp % remove to fix
        >>
      }
      \new Lyrics \lyricsto "Descant" { }
    >> } % remove to fix
    { <<  % remove to fix
      \new Staff = "Soprano" {
        \new Voice = "Soprano" \relative { a' a a a }
      }
      \new Lyrics \lyricsto "Soprano" { A B C D }
    >> }   
  >>
}

I'm not sure I'd call this a bug, the structure required
to expose it being so bizarre.  As I'm currently looking
into reworking this template completely I hope a simplified
structure will bypass the problem.

Trevor