Re: wrong beam positions in LilyPond

[address@hidden]

On 31 août 2012, at 20:47, Jan Nieuwenhuizen <address@hidden> wrote:

> Han-Wen Nienhuys writes:
> 
>> That is a testament to the regtest's usefulness, and it was certainly
>> intended to be like that.
> 
> Ha, yes.  It indeed helps keeping things perfectly the same [even if
> they are obviously wrong], and that's what it's intended for.
> I guess it's only obvious once you see it, and Janek prepared
> very nice and intstructive examples, for easy comparison with Ross.
> 
>> fixing things is always good. The beaming code is pretty generic, so I
>> expect that this will mostly be about tweaking scoring functions, and
>> making sure existing situations stay the same.
> 
> I remember we had some text balloon debugging code that would show
> all scores, giving some insight as to why the scoring system made
> certain choices?
> 
> Jan
> 
> -- 
> Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  
> 
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel

You can set debug-beam-scoring = ##t in the paper bloc.

Cheers,
MS