On 10/12/09 1:41 PM, "Andrew Hawryluk" <[email protected]> wrote:
> Attached is the output of LilyPond 2.7, which was benchmarked as a
> near match against Baerenreiter BA320. The current beam positions do
> not match: the stems are now shorter, on average. (The third measure
> also has a beaming error of another kind: the first two beats should
> be grouped separately from each other.)
I cannot see where the stems are shorter on average. I can see that the
beamlets are a little bit shorter, but every stem I check between the two
appears to me to be the same length (except the difference caused by the
beaming error).
The beaming error in measure 3 is the result of a known bug; the autobeamer
can't look ahead to see the 1/16 notes on the second beat and end the beam
after the first beat.
See issue 638
http://code.google.com/p/lilypond/issues/detail?id=638
>
> \relative c {
> \clef "bass"
> \key d \minor
> \time 3/4
> \mergeDifferentlyDottedOn
> << {\slurDashed d8.-\flageolet( e16) e4.-\trill( d16 e)}
> \\ {d4_2 a2}
>>>
> \slurDashed
> <f' a, d,>4. e8( d c)
> \slurSolid
> bes g' f e16( f g_1 a_2 bes_3 d,_2)
> \slurDashed
> cis4.-\trill b8_3( a g)
> << {\slurDashed d'8.( e16) e4.-\trill( d16 e)}
> \\ {<f, a>4 a2}
>>>
> }
>
> Andrew
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
