[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Beams in 1.5 CVS
From: |
Jan Nieuwenhuizen |
Subject: |
Re: Beams in 1.5 CVS |
Date: |
Fri, 31 May 2002 23:02:17 +0200 |
User-agent: |
Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-debian-linux-gnu) |
Vassily Checkin <address@hidden> writes:
> Couple of problems found in today's CVS:
>
> 1. Beam touches the middle B in the following snippet. 1.4 used to
> handle similar things well.
>
> \score {
> \context Staff = up {
> \notes{
> \clef bass \stemDown [b,8 b,, b,] r8 r2
> }
> }
> }
Thanks. This can be fixed by increasing the REGION_SIZE to 4 in
lily/beam.cc. Problem is, that doubling the REGION_SIZE results in a
significant lengthening of processing time. We really must find a
better way to determine a sane region, or at least to decrease the
search space. It seems to me that in this example, the region is not
centered about the correct position...
> 2. Tuplet brackets are not aligned with the beam.
>
> \score {
> \context Staff = up {
> \notes{
> \relative f { \key b \major \time 6/4
> [fis8. gis16
> \times 4/6 {ais b cis dis e fis}
> \times 4/6 {gis ais b cis dis e}]
> [ \times 4/7 {fis gis ais b cis dis e}
> \times 4/6 {fis gis ais b cis dis} ]
> e8 r8
> }
> }
> }
> }
Sorry, what is it exactly that is wrong here?
http://lilypond.org/~jan/b2.ps
I see that LilyPond now defaults to showing brackets, whereas 1.4 only
shows the tuplet number, which in this case, with the tuplets being of
a different size than the beam, seems ok (a new feature of 1.5).
> PS I've just started to play around with 1.5 series and I must say
> I'm impressed. The output looks much nicer (aside from the two issues
> above and places where input is over-tuned for 1.4 :)
> and the memory consumption is almost twice less (45Megs vs 80 for Listz'
> second ballade)
Thanks, that's good to hear,
Greetings,
Jan.
--
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org