lilypond-user
[Top][All Lists]
Advanced

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

Re: Cross-staff beam slope - can it be specified?


From: Ben
Subject: Re: Cross-staff beam slope - can it be specified?
Date: Sat, 28 Oct 2017 08:49:11 -0400
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 10/27/2017 1:33 PM, David Sumbler wrote:
In the above rather silly example, the beam between the 2 cross-staff
notes slopes slightly upwards.  If I add a dynamic, say \f , after <c'
g>2. in line 7, the staves are forced further apart, and the beam
slopes slightly downwards.

If I now add a further dynamic, say ^\p , to the lower staff after <e
c>2. in line 9, the staves are forced still further apart and the beam
now has a large downward slope.

The problem I have is that, in "real life", I don't know how far apart
the staves will be because of the space requirements of other parts of
the music.  Generally I would prefer to allow Lilypond to determine
where line ends etc. should be, so I don't even know which bits of the
music will affect the slope of the beam.  And even if I did know, an
alteration to the music in the closely preceding and following bars
might well affect the spacing of the staves and hence the slope of the
beam.

Is there any way of ensuring that the beam always has a predetermined
slope - say 10° downwards - and that the stem lengths will
automatically be adjusted to allow for this?

David

Hello,

Check out this older post here, it deals with cross beam slopes:
http://lilypond.1069038.n5.nabble.com/Adjusting-beam-slope-with-cross-staff-notes-td140283.html

David Nalesnik wrote a function where instead of specifying the absolute values for positions, it allows you to indicate displacements from the values LilyPond would use by default.

It sounds like that's what you are looking for, does this help?


Attachment: beam-slopes.ly
Description: Text Data


reply via email to

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