Here's a somewhat reduced example that still shows the problem.
Stems down, the accidental and the manual beam are essential.

{
 \new PianoStaff <<
   \new Staff = "PianoRH1" {
     \repeat unfold 19 { b'1 }
   }
   \new Staff = "PianoLH" {
     \clef "bass"
     \repeat unfold 4 { d1 }
     a,2 \stemDown d8 [ f8 aes8
     \change Staff = "PianoRH1"  d'8 ]
     \change Staff = "PianoLH"
     \repeat unfold 14 { d1 }
   }
 >>
}

Trevor

----- Original Message ----- From: <[email protected]>
To: <[email protected]>
Sent: Tuesday, March 15, 2011 10:59 AM
Subject: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems


Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Critical Regression

New issue 1565 by [email protected]: Changing staff with manual beaming can give very long stems
http://code.google.com/p/lilypond/issues/detail?id=1565

In the code below, the music in the left hand changes from the bass clef line to the treble clef line. The quavers are manually beamed. There is a key sign with 6 sharps and the notes have naturals. In this case, the beamed stems stretch to below the system under their proper system (In my real example, they actually go even further, to the top of the system below that). This does not happen in 2.12.3 and was introduced between 2.13.51 and 2.13.52.

{
  <<
    \new PianoStaff
    <<
      \new Staff = "PianoRH1"
      <<
        {
          \key fis\major
          \time 4/4
          \repeat unfold 4 { b'1 }
ais'2 \voiceOne fis'8 ( [ a8 dis'8 fis'8 ) ] \oneVoice
          \repeat unfold 14 { b'1 }
        }
      >>
      \new Staff = "PianoLH"
      <<
        {
          \clef "bass"
          \key fis\major
          \time 4/4
          \repeat unfold 4 { dis1 }
a,2 \voiceFour d8 ( [ fis8 a8 \change Staff = "PianoRH1" d'8 ) ] \change Staff = "PianoLH" \oneVoice
          \repeat unfold 14 { dis1 }
        }
      >>
    >>
  >>
}


Attachments:
LongStems2.13.52.png  17.9 KB
LongStems2.12.3.png  18.1 KB


_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond





_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to