Re: wierd beamlet behaviour

[Vaughan McAlley]

On 12 November 2016 at 14:34, Kieren MacMillan
<address@hidden> wrote:
>
> Hello all,
>
> In the following screenshot, you will notice some odd beamlet behaviour:
> The following minimal snippet does NOT show this problem:
>
> %%%%  SNIPPET ENDS
> \version "2.19.49"
> \language "english"
>
> beamtest = {
>   <af'' g'''>16([ bf''8)] <g'' f'''>16([ af''8)] <f'' ef'''>16([ g''8]) <ef'' 
> d'''>16([ f''8)] <d'' c'''>16([ ef''8)]
> }
>
> \score { \beamtest }
> %%%%  SNIPPET ENDS
>
> Any thoughts what this might be? I’m pretty sure it’s not the PDF viewer 
> (because the minimal example looks fine in the same viewer).
>
> The number of stylesheet layers involved in the score I’m engraving is pretty 
> high, so it would be nice to have at least an idea of which haystack to look 
> in to find this particular needle...
>
> Thanks,
> Kieren.
> ________________________________
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: address@hidden
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

Hi Kieran,

It looks like the beamlets are getting their slope from the slope of
the top note to the quaver, but the beams proper are getting their
slope from the bottom note (or interval, really). If there is
beam-sloping code in your stylesheets, maybe the slope is calculated
twice. The beam proper has to connect with the next note so the slope
gets overidden, but the beamlet is not connected to another note so it
stays as it was.

Or something like that?

Vaughan