lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: More questions on beam properties


From: David Nalesnik
Subject: Re: More questions on beam properties
Date: Fri, 15 Jul 2016 15:10:11 -0500

On Fri, Jul 15, 2016 at 9:48 AM, Andrew Bernard
<address@hidden> wrote:
> What does the property Beam.positions actually represent? I have seen code
> that treats it as the y position coordinates of the end points of the beam,

If I recall correctly, in the case of Beam, 'positions represents the
Y-coordinate of the vertical midpoint of the "0" beam, the beam which
touches the endpoints of the outermost stems.

Thankfully, in the case of Beam, this info is usable to get
measurements of the beam you see.  In the case of Slur, the positions
numbers are instead used to select the closest "trial curve" out of a
range of pre-calculated possibilities which Lilypond scores for
appropriateness.  Thus, they don't correlate with, say,
control-points.

What on earth is ‘beam::place-broken-parts-individually’ in the
> context of beam start end vertical positioning? Dear me.

When Beams are broken across systems there are several options for
handling the slope and relative alignment of the Beam bits.  I believe
this oddly named callback has its origin in a attempt to support
several distinguishable traditions of dealing with this: an Edition
Peters style, and several others.  You could check the issue tracker
for more info.

>
> [I hate to continually complain about the IR manuals, and I dearly wish I
> was in a position to understand this material enough to rewrite these
> unclear sections, but I apologise, I don’t.]
>

Unfortunately, it is a matter of studying the code yourself, doing
simple experiments, or asking on the lists where you likely be
answered by someone who did just that to get whatever knowledge they
have.  (That includes me.)

David



reply via email to

[Prev in Thread] Current Thread [Next in Thread]