lilypond-user
[Top][All Lists]
Advanced

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

Re: Strange space between beam and slur


From: Thomas Morley
Subject: Re: Strange space between beam and slur
Date: Sun, 23 Jun 2019 11:59:01 +0200

Am So., 23. Juni 2019 um 10:54 Uhr schrieb Andrew Bernard
<address@hidden>:
>
> Hi Lukas,
>
> May be a bug, but I always use explicit voices, not '//' constructs. I
> find it is just better but.
>
> You play with the rests, but this works:
>
>
> \new Staff
> <<
>    {
>      \voiceOne
>      R1
>      a''8( b'' b'' a'')
>    }
>    \new Voice {
>      \voiceTwo
>      R1
>      r2
>    }
>  >>
>
>
> I'm aware this does not address the issue of whether your code shows a
> bug or not. Could be something to do with your rests running out, inside
> the '//' construct. Sorry I don't have more time to look at it now.
>
> Andrew

\new Staff
<<
   {
     \voiceOne
     R1
     a''8( b'' b'' a'')
   }
   \new Voice {
     \voiceTwo
     r4 r r r
     r r r r
   }
 >>

exposes the problem as well.

I can confirm Lukas-Fabian's finding about first bad commit.

87eb2f9fe1be3a532675fe4b7322bbba5a60ba5c
patches `overdone_headsĀ“ in feta-params.mf

So adding
\override NoteHead.font-size = 0.0001
to the examples fixes them in recent lily-versions

Interestingly 2.18.2 can be forced to return same bad output by
setting NoteHead.font-size accordingly:

\version "2.18.2"

\new Staff \with { \override NoteHead.font-size = 0.00005 }
 <<
   { R1 a''8( b'' b'' a'') } \\ { r4 }
 >>

\new Staff \with { \override NoteHead.font-size = -0.0001 }
 <<
   { \voiceOne R1 a''8( b'' b'' a'') }
   \new Voice { \voiceTwo r4 r r r r r r r }
 >>

Cheers,
  Harm



reply via email to

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