Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

[Joe Neeman]

On Thursday 16 August 2007 08:19, Wilbert Berendsen wrote:
> Op dinsdag 7 augustus 2007, schreef Joe Neeman:
> > Does the problem still exist in the jneeman branch of git? If it does,
> > I'd be particularly interested in seeing examples with stems in the wrong
> > order.
>
> git master as of today still shows the same too tight spacing choice as in
> my previous mail with the results of git 4 august.

That's strange because I merged jneeman into master a little while ago. 
Does 'git log master' show that commit 2a6bf54a5ebf426 is part of master?

> after that I tested the jneeman branch of my file. This one makes the PDF 4
> pages long instead of 3, with a much more open spacing. and the stems in
> the kneed beams are at nice even distances:
> http://www.xs4all.nl/~wbsoft/p78jneeman.pdf
>
> I have to say, I like the slightly tighter spacing better (resulting in 3
> pages), but of course not the too tight spacing in the kneed beams.

This is not entirely unexpected, since part of the bug was that lilypond was 
too willing to compress kneed beams. If the piece was tight on 3 pages 
before, the bug fix could easily have pushed it over to 4. Do the standard 
methods of tightening spacing (section 11.6.3) work?

Joe