> From: Han-Wen Nienhuys <[EMAIL PROTECTED]>
> Date: Mon, 10 Jul 2000 23:14:22 +0200 (CEST)
> [EMAIL PROTECTED] writes:
> >
> > That reminds me to tell from two experiences I made with MusiXTeX
> > and PMX.
> >
> > MusiXTeX provides two spacing methods \arithmeticskipscale and
> > \geometricskipscale. I think the names tell all. One of the methods
>
> way way back , we used to have a geometric scale (distances increase
> multiplicatively, a halfnote gets 1.5 times the distance of a quarter
> note), and it looked awful: the short notes don't get enough space,
> the long ones too much. We changed to arithmetic spacing in 0.1.9
way way back :-)
It's pretty good to have both. And the factor must not be 1.5; and
it can be changed whereever you want.
And it's good to be able to define the "factors" for both types freely.
> > Don Simons, the author of PMX added another aspect: if the notes
> > do not fit well into a line - i.e. if a mimimum distance for
> > short notes cannot be kept - then the distance for longer notes
> > is decreased until the notes fit or until all notes are spaced
> > with this minimum distance. This feature helps much in slow movements.
>
> Interesting feature. It would be difficult to implement within the
> context of LilyPond right now, though.
If you want to know more details, ask Don Simons. He has implemented
it into PMX especially to deal with many n-tuplets in different
staffs with completely different n in combination with MusiXTeX's
"spacing-engine".
-- Werner
