Re: Adjusting beam slope with cross-staff notes

[Javier Ruiz-Alma]

From: David Nalesnik
>
>
>Hi Javier,
>
>
>On Tue, Jan 29, 2013 at 11:45 PM, Javier Ruiz-Alma <address@hidden> wrote:
>
>>I have first beamed note in the bass, and 3 more in the treble staff.  I wish 
>>to adjust the beam slope using "\override Beam #'positions", as the 
>>automatically-calculated beam slope is overinfluenced by the lone cross-staff 
>>note.
>>
>>However, the adjustment values are anchored relative to the centerline of the 
>>(starting) bass staff.  I wish to have the override values anchored to the 
>>treble staff. Is it possible?
>
>
>I don't know of any automatic way to do this.
>
>
>I've attached a function which may or may not be of help to you.  Rather than 
>specifying the absolute values for positions, it allows you to indicate 
>displacements from the values LilyPond would use by default.  I use your 
>example to show how it works in practice.
>
>
>You can also use it to offset other properties of other grobs, including 
>separate offsets for pieces of grobs across staff breaks.
>
>
>(On a side note, this is fairly old, and I see that I should update the 
>function "offset" to deal more elegantly with names of grobs in other 
>contexts.  This version assumes that you specify them like so: "Staff.Clef".)
>
>
>Hope this proves helpful.
>
>
>Best,
>David
>
Great function for my toolkit.  I will try it. Thank You!

An alternative way to resolve my issue would be if an override/tweak was 
available to exclude specific beamed notes from influencing the automatic 
beam-slope calculation done by Lilypond.  Something like:

\staffDown g8[\noBeamSlopeInfluence \staffUp e'd c]


As I look at the manually-typeset music I'm transcribing, I have several of 
these four-quaver beamed groups with the initial quaver starting on the lower 
staff.  The beam slope is set same as Lilypond would automatically calculate if 
considering only the three following notes that rest on the upper staff.