Re: \RemoveEmptyStaffContext and cross-staff beams

2009-10-29 Thread Valentin Villenave
On Wed, Sep 23, 2009 at 9:54 PM, Neil Puttock n.putt...@gmail.com wrote: 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. OK, since I can't decide whether to remove it or not, I've just

Re: \RemoveEmptyStaffContext and cross-staff beams

2009-09-23 Thread Mats Bengtsson
I can see the problem you report with version 2.12, but with the latest 2.13 version (compiled from todays GIT), it's even worse, since the beam stays flat also if you don't have \RemoveEmptyStaffContext. I haven't tracked down exactly what has changed, but I had to reduce the setting of the

Re: \RemoveEmptyStaffContext and cross-staff beams

2009-09-23 Thread Neil Puttock
2009/9/23 Mats Bengtsson mats.bengts...@ee.kth.se: 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

\RemoveEmptyStaffContext and cross-staff beams

2009-09-22 Thread Jonathan Wilkes
Hello, In the following code, the beam goes between the staves when \RemoveEmptyStaffContext is commented out but goes above the top staff when it's used. This means you have to explicitly state all the stem directions to get the beam to go in the middle of the staves when using