Hello Knute, you if you check out the internals for Slur (also Tie) you'll find that you have quite a lot of control over the demerits and penalties used for calculating the Slur shape in the details property, as well options like height-limit, rate, excentricity and stuff.
This means that many times instead of using shape it can be better to simply tweak a small parameter. Sadly there is little documentation for this. Valentin 11.02.2022 16:33:27 Knute Snortum <ksnor...@gmail.com>: > Thanks Valentin and Kieren. I didn't know you could control this kind > of thing with grob parameters! I'll try out both suggestions. I was > always using \shape to change the shape of the slur, but now I'll look > for parameters to tweak. > > -- > Knute Snortum > > > On Fri, Feb 11, 2022 at 4:55 AM Valentin Petzel <valen...@petzel.at> wrote: >> >> Hello Knute, >> >> this is a common issue with big slurs. To allow a better shape for the slur >> increase the height limit of the slur (grob path Slur.height-limit). >> >> The problem here is that having a single height limit is not able to handle >> each possible situation well. What we might try to do is to heuristically >> try to guess a good value, depending on the length of the passage, the curve >> of the note heads and such. >> >> Cheers, >> Valentin >> >> 11.02.2022 01:53:45 Knute Snortum <ksnor...@gmail.com>: >> >>> Hi all, >>> >>> I have what I guess is a request for comment on how close this slur is >>> to the topmost note. If you engrave this input file... >>> >>> %%% >>> \version "2.23" >>> \language "english" >>> >>> \relative { >>> \clef bass >>> \key c \minor >>> c,16( g' c d ef g c d ef d c g ef d c g) | >>> } >>> %%% >>> >>> ...you get a slur that to my eye is much too close to the "ef" in the >>> third beat (see attached). What do others think? Is this just a case >>> of "LilyPond sometimes doesn't render perfect slurs" or is there an >>> algorithm that can be tweaked? >>> >>> -- >>> Knute Snortum