1 \input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
2 @setfilename lilypond-changes.info
3 @settitle LilyPond Changes
8 @macro inputfileref{DIR,NAME}
9 @uref{../../\DIR\/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
11 @macro usermanref{NAME}
12 @inforef{\NAME\,,../user/lilypond/lilypond}@c
17 @macro inputfileref{DIR,NAME}
20 @macro usermanref{NAME}
21 See user manual, \NAME\
25 @macro textanchor{NAME}
32 @documentencoding utf-8
39 @top New features in 2.20 since 2.18
41 @allowcodebreaks false
49 * add new items at the top
51 * only show verbatim input for syntax/input changes
53 * try to be as brief possible in those cases
55 * don't try to provide real-world examples, they often get too big,
56 which scares away people.
58 * Write complete sentences.
60 * only show user-visible changes.
64 A new flexible template suitable for a range of choral music, is now
65 provided. This may be used to create simple choral music, with or
66 without piano accompaniment, in two or four staves. Unlike other
67 templates, this template is @q{built-in}, which means it does not
68 need to be copied and edited: instead it is simply @code{\include}'d
69 in the input file. For details, see @rlearning{Built-in templates}.
72 The positioning of tuplet numbers for kneed beams has been significantly
73 improved. Previously, tuplet numbers were placed according to the
74 position of the tuplet bracket, even if it was not printed. This could
75 lead to stranded tuplet numbers. Now they are now positioned
76 closer to the kneed-beam when an appropriate beam segment exists for its
77 placement and when the the bracket is not drawn.
79 Collision detection is also added, offsetting horizontally if too close
80 to an adjoining note column but preserving the number's vertical
81 distance from the kneed beam. If the number itself is too large to
82 fit in the available space the original, bracket-based, positioning
83 system is used instead; and in the event of a collision (e.g. with an
84 accidental) the tuplet number is moved vertically away instead.
86 @lilypond[verbatim,fragment,quote,relative=1]
88 \override Beam.auto-knee-gap = 3
97 The original kneed-beam tuplet behavior is still available through an
98 @code{\override} via a new, @code{knee-to-beam} property.
100 @lilypond[verbatim,fragment,quote,relative=1]
102 \override Beam.auto-knee-gap = 3
103 \override TupletNumber.knee-to-beam = ##f
112 @code{\lyricsto} and @code{\addLyrics} have been @q{harmonized}. Both
113 now accept the same kind of delimited argument list that @code{\lyrics}
114 and @code{\chords} accept. Backward compatibility has been added so
115 music identifiers (i.e. @code{\mus}) are permitted as arguments. A
116 @code{convert-ly} rule has been added that removes redundant uses of
117 @code{\lyricmode} and rearranges combinations with context starters such
118 that @code{\lyricsto} in general is applied last (i.e. like
119 @code{\lyricmode} would be).
122 Scheme functions and identifiers can now be used as output definitions.
125 Scheme expressions can now be used as chord constituents.
128 Improved visual spacing of small and regular @q{MI} Funk and Walker
129 noteheads so they are now the same width as other shaped notes in
130 their respective sets. @code{SOL} noteheads are also now visually
131 improved when used with both the normal Aiken and Sacred Harp heads, as
132 well as with the thin variants.
135 @code{LeftEdge} now has a definable @code{Y-extent} (i.e.vertical). See
136 @rinternals{LeftEdge}.
139 Added a new @code{make-path-stencil} function that supports all
140 @code{path} commands both relative and absolute:
142 @code{lineto}, @code{rlineto}, @code{curveto}, @code{rcurveto},
143 @code{moveto}, @code{rmoveto}, @code{closepath}. The function also
144 supports @q{single-letter} syntax used in standard SVG path commands:
146 @code{L}, @code{l}, @code{C}, @code{c}, @code{M}, @code{m}, @code{Z} and
147 @code{z}. The new command is also backward-compatible with the original
148 @code{make-connected-path-stencil} function. Also see
149 @file{scm/stencil.scm}.
152 Context properties named in the @samp{alternativeRestores} property are
153 restored to their value at the start of the @emph{first} alternative in
154 all subsequent alternatives.
156 Currently the default set restores @q{current meter};
158 @lilypond[verbatim,fragment,quote,relative=2]
160 \repeat volta 2 { c2 e4 | }
169 @q{measure position};
171 @lilypond[verbatim,fragment,quote,relative=2]
173 \repeat volta 2 { c2 e4 | }
176 \set Timing.measurePosition = #(ly:make-moment -1/2)
184 and @q{chord changes};
186 @lilypond[verbatim,fragment,quote]
189 \set chordChanges = ##t
190 \chordmode { c1:m d:m c:m d:m }
193 \repeat volta 2 { \chordmode { c1:m } }
195 { \chordmode { d:m } }
196 { \chordmode { c:m } }
204 Improved MIDI output for breathe marks. After tied notes, breaths take
205 time @emph{only} from the last note of the tie; e.g.
206 @code{@{ c4~ c8 \breathe @}} performs as @code{@{ c4~ c16 r @}} instead
207 of @code{@{ c4 r8 @}}. This is more consistent with articulations and
208 how humans interpret breaths after ties. It now also makes it easier to
209 align simultaneous breathe marks over multiple parts, all with different
213 A new note head style for Tabulature has been added;
214 @code{TabNoteHead.style = #'slash}.
217 Four new Clefs have been added. @emph{Double G}, @emph{Tenor G},
218 @emph{Varpercussion} and @emph{varC}.
219 @lilypond[verbatim,quote,fragment]
220 \override Staff.Clef.full-size-change = ##t
223 \clef "tenorG" c c c c
225 \clef "varpercussion" c c c c
228 \override Staff.Clef.full-size-change = ##f
231 \clef "tenorG" c c c c
233 \clef "varpercussion" c c c c
237 Isolated durations in music sequences now stand for unpitched
238 notes. This may be useful for specifying rhythms to music or
239 scheme functions. When encountered in the final score, the
240 pitches are provided by the preceding note or chord. Here are two
241 examples where this makes for readable input:
243 @lilypond[verbatim,quote]
244 \new DrumStaff \with { \override StaffSymbol.line-count = 1 }
247 tambourine 8 \tuplet 3/2 { 16 16 16 }
248 8 \tuplet 3/2 { 16 16 16 } 8 8 |
252 @lilypond[verbatim,quote]
253 \new Staff { r16 c'16 ~ 8 ~ 4 ~ 2 | }
257 Beaming exceptions can now be constructed using the
258 @code{\beamExceptions} scheme function. One can now write
260 @lilypond[verbatim,quote,relative=1]
262 \set Timing.beamExceptions =
263 \beamExceptions { 32[ 32] 32[ 32] 32[ 32] }
265 \repeat unfold 6 { c32 } |
269 with multiple exceptions separated with @code{|} bar checks
270 (writing the exception pattern without pitches is convenient but
271 not mandatory). Previously, setting the beam exceptions would
272 have required writing
275 \set Timing.beamExceptions =
277 (end . ;entry for end of beams
278 ( ;start of alist of end points
279 ((1 . 32) . (2 2 2)) ;rule for 1/32 beams -- end each 1/16
284 The most common articulations are now reflected in MIDI output.
285 Accent and marcato make notes louder; staccato, staccatissimo and
286 portato make them shorter. Breath marks shorten the previous
289 This behavior is customizable through the @code{midiLength} and
290 @code{midiExtraVelocity} properties on @code{ArticulationEvent}.
291 See @file{script-init.ly} for examples.
294 The PostScript functionality of stroke adjustment is no longer
295 applied automatically but left to the discretion of the PostScript
296 device (by default, Ghostscript uses it for resolutions up to
297 150dpi when generating raster images). When it is enabled, a more
298 complex drawing algorithm designed to benefit from stroke
299 adjustment is employed mostly for stems and bar lines.
301 Stroke adjustment can be forced by specifying the command line
302 option @samp{-dstrokeadjust} to LilyPond. When generating
303 @code{PDF} files, this will usually result in markedly better
304 looking @code{PDF} previews but significantly larger file size.
305 Print quality at high resolutions will be unaffected.
310 For older news, go to
311 @uref{http://lilypond.org/doc/v2.18/Documentation/changes/},
312 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/},
313 or @uref{../,go back} to the Documentation index.