Hi,
NR 1.3.2 on slurs
<https://lilypond.org/doc/v2.25/Documentation/notation/slurs> gives this as
the second example on what slurs can do:
%%% EXAMPLE 1 %%%
\version "2.25.19"
{
<c' ~ f' \=1 ( g' \=2 ( >2
<c' e' \=1 ) a' \=2 ) >2
|
}
%%% END %%%
With the docs' default staff size, this produces good output:
[image: 1-correct-at-default-staff-size.png]
But a bug appears if the global staff size is set to any value less than 20.
%%% EXAMPLE 2 %%%
\version "2.25.19"
#(set-global-staff-size 16)
{
<c' ~ f' \=1 ( g' \=2 ( >2
<c' e' \=1 ) a' \=2 ) >2
|
}
%%% END %%%
[image: incorrect-at-staff-size-16.png]
%%% EXAMPLE 3 %%%
\version "2.25.19"
#(set-global-staff-size 14)
{
<c' ~ f' \=1 ( g' \=2 ( >2
<c' e' \=1 ) a' \=2 ) >2
|
}
%%% END %%%
[image: incorrect-at-staff-size-14.png]
Note that staff sizes larger than 20 points render well. The bug only
appears at smaller staff sizes.
Looking through the tracker, it's possible this is a clue for #5616
Slurring individual notes in chords yields ugly results
<https://gitlab.com/lilypond/lilypond/-/issues/5616>. It's also possible
this is a separate bug.
Trevor.
--
Trevor Bača
www.trevorbaca.com
soundcloud.com/trevorbaca
