Fw: best practices for volta (was Re: Problem with repeat alternative endings that contain lyrics andleading rests)

[Trevor Daniels]

From: "Trevor Daniels" <address@hidden>
To: "Kieren MacMillan" <address@hidden>
Sent: Wednesday, April 22, 2015 10:55 AM
Subject: Re: best practices for volta (was Re: Problem with repeat alternative 
endings that contain lyrics andleading rests)
 
 Kieren MacMillan wrote Tuesday, April 21, 2015 3:19 PM
 
 Hi Kieren,
 
> You mean Lilypond can’t handle << \global \lyrics >>, where \global contains 
> the repeat structure?
 
 Depends.  Imposing a \global repeat structure on all staff and lyrics 
 contexts works fine, even with alternatives, if all you want is the
 printed output with the repeats not unfolded.  So this works,
 (as long as the alternatives don't start with a rest):
 
 \version "2.19.18"
 
 Time = {
  \repeat volta 2 {
    s4 s s s
  }
  \alternative {
    { s s s s }
    { s s s s }
  }
  s s s s
 }
 
 <<
  \new Staff <<
    \new Voice = "sop"
    \relative {
      a'4 a a a
      b b b b
      c c c c
      d d d d
    }
    \Time
  >>
  \new Lyrics \lyricsto "sop" <<
    { 
      a a a a 
      b b b b 
      c c c c
      d d d d
    }
    \Time
  >>
>>
 
 But there are three issues:
 
 a) the alternative sections are not delineated in the source of both music and 
lyrics;
 
 b) if the alternative sections start with rests the volta brackets screw up, 
as we've seen;
 
 c) there is no way to make \unfoldRepeats work, so the MIDI output is 
incorrect.
 
To avoid these issues the repeat structure must be inserted explicitly in every 
context,
 and a work-around is needed to handle rests, as we've previously seen.  See
 http://www.lilypond.org/doc/v2.19/Documentation/notation/repeats-in-midi and
 https://code.google.com/p/lilypond/issues/detail?id=3149.
 
 Trevor