I just tried the example again with the latest git version and
the beam is slanted upwards (not much but still clearly visible
if you look carefully).
I have attached a png with debug-beam-scoring and another one
where I also set inspect-quants. The corresponding input file is repeated
here for completeness.
\version "2.11.7"
\layout{
% line-width = 5\cm % Gives expected beam slanted downwards
line-width = 10\cm % Gives unexpected beam slanted upwards
debug-beam-scoring = ##t
}
\relative c'''{
\time 2/4
\override Beam #'inspect-quants = #'(1 . 2)
fis16 dis b ais cis4
}
/Mats
[EMAIL PROTECTED] wrote:
Issue 190: Unexpected beam slanting in the opposite direction
http://code.google.com/p/lilypond/issues/detail?id=190
Comment #1 by hanwenn:
Unfortutaly, can't reproduce.
It's helpful for this to provide a png with
debug-beam-scoring = ##t
in the \layout{} block, and to use
\override Beam #'inspect-quants = #'(1 . 2)
to see why the better configuration doesn't score well.
Issue attribute updates:
Status: Invalid
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
