Slurs

From LilyPond Wiki

Slurs are a very important feature of music notation, and LilyPond highly excels at engraving them. However, LilyPond's slur code often seems inaccessible due to its complicated, penalty-based formatting algorithms; the plethora of workarounds and "ugh" code comments are hints that the slur code needs a big makeover.

Matters are complicated from having two different slur engravers, Slur_engraver and Phrasing_slur_engraver, that are almost identical. If we use the same logic, we would also need a Grace_slur_engraver and possibly a Tablature_bend_engraver to fix various limitations in the slur code. But these limitations should not exist.

For now, let's just document the "details" subproperties for slurs. Pnorcks 22:24, 17 October 2009 (UTC)

[edit] Documentation of slur details

• region-size

• head-encompass-penalty

• stem-encompass-penalty

• closeness-factor

• edge-attraction-factor

• same-slope-penalty

• steeper-slope-factor

• non-horizontal-penalty

• max-slope

• max-slope-factor

• free-head-distance

• absolute-closeness-measure

• extra-object-collision-penalty

• accidental-collision

• extra-encompass-free-distance

• extra-encompass-collision-distance

• head-slur-distance-factor

• head-slur-distance-max-ratio

• free-slur-distance

• edge-slope-exponent