Re: \RemoveEmptyStaffContext and cross-staff beams

[Neil Puttock]

2009/9/23 Mats Bengtsson <address@hidden>:

> I haven't tracked down exactly what has changed, but I had to reduce the
> setting of the auto-knee-gap property of Beam from the default value 5.5 to
> \override Score.Beam #'auto-knee-gap = #4.75
> to get the kneed beam that was obtained in earlier versions.
> Regression bug!(?)

The staves are slightly closer together due to Joe's new spacing code,
so it's probably just a case of tweaking the default value for
'auto-knee-gap.

> On the other hand, the problem you report has been in LilyPond for a very
> long time and seems to date back to
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=17332ae36b238193723983455a91366be4e88e0b
> I'm not sure why Han-Wen added this setting in the definition of
> \RemoveEmptyStaffContext, but he probably had a good reason.

There's a message in the deleted bug snippet harakiri-autoknee.ly
which suggests there used to be a problem:

Autoknee-ing triggers hara-kiri too early.

Here's the same snippet updated, which compiles fine under current master:

\version "2.13.4"
\score {
  \relative c''' {
    \new PianoStaff <<
      \context Staff = up {
        c4 c c c \break
        c4 c c c
      }
      \context Staff = mid {
        c4 c c c \break
        s1
      }
      \context Staff = down {
        c8
        \change Staff = mid
        c8
        \change Staff = down
        c8 c c4 c
        c4 c c c
      }
    >>
  }
  \layout {
    \context {
      \RemoveEmptyStaffContext
      \revert Beam #'auto-knee-gap
    }
  }
}

Regards,
Neil