[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: better beam direction algorithm (again)
From: |
Kristof Bastiaensen |
Subject: |
Re: better beam direction algorithm (again) |
Date: |
Wed, 31 Aug 2005 10:53:41 +0200 |
User-agent: |
Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (Sanjō) APEL/10.6 MULE XEmacs/21.4 (patch 17) (Jumbo Shrimp) (i386-debian-linux) |
At Wed, 31 Aug 2005 07:47:37 +0200 (CEST),
Werner LEMBERG wrote:
>
> > > Lilypond still uses a non-optimal beam direction algorithm. Again
> > > I suggest to simply check for the note under the beam which has
> > > the greatest distance from the staff's middle line, and to use its
> > > natural direction for the whole beam.
> >
> > But what happens if there are a lot of those notes with the same
> > maximum?
>
> Example, please.
>
Time = {\time 6/8}
Musicone = \relative c'''{
\time 6/8
\clef violin
e16 e e e e,, e''
\stemUp
e16 e e e e,, e''}
\score
{
\new Staff {
\Musicone
}
\layout {}
}
> > We'd get a beam with a lot of (too) long stems. Wouldn't it be
> > better to take the direction which minimizes the total deviation
> > from the standard stemlength?
>
> IMHO it is better to make the beam always stay near the staff lines.
>
It should be a trade-off between having an optimal structure of the
group and an optimal coverage of the staf by the stems.
Kristof Bastiaensen