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.
65 Page numbers may now be printed in roman numerals, by setting the
66 @code{page-number-type} paper variable.
69 It is now possible to use @code{\time} and @code{\partial}
70 together to change the time signature in mid measure.
72 @lilypond[verbatim,quote,relative=1]
73 \override Score.BarNumber.break-visibility = #end-of-line-invisible
74 \partial 4 \time 3/4 f4 | 2 4 | 2 \bar "||"
75 \time 9/8 \partial 4. f8 8 8 | 2. 8 8 8 |
79 It is now possible to override the @code{text} property of
82 @lilypond[verbatim,fragment,quote]
84 \new ChordNames \chordmode {
86 \once \override ChordName.text = #"foo"
93 Improved horizontal alignment when using @code{TextScript},
94 with @code{DynamicText} or @code{LyricText}.
97 A new command @code{\magnifyStaff} has been added which scales staff
98 sizes, staff lines, bar lines, beamlets and horizontal spacing generally
99 at the @code{Staff} context level. Staff lines are prevented from being
100 scaled smaller than the default since the thickness of stems, slurs, and
101 the like are all based on the staff line thickness.
104 @code{InstrumentName} now supports @code{text-interface}.
107 There is now support for controlling the @q{expression level} of
108 MIDI channels using the @code{Staff.midiExpression} context property.
109 This can be used to alter the perceived volume of even sustained notes
110 (albeit in a very @q{low-level} way) and accepts a number value between
111 @code{0.0} and @code{1.0}.
116 midiExpression = #0.6
117 midiInstrument = #"clarinet"
122 \set Staff.midiExpression = #0.7 s4\f\<
123 \set Staff.midiExpression = #0.8 s4
124 \set Staff.midiExpression = #0.9 s4
125 \set Staff.midiExpression = #1.0 s4
127 \set Staff.midiExpression = #0.9 s4\>
128 \set Staff.midiExpression = #0.8 s4
129 \set Staff.midiExpression = #0.7 s4
130 \set Staff.midiExpression = #0.6 s4\!
138 Support for making it easier to use alternative @q{music} fonts other
139 than the default Emmentaler in LilyPond has been added. See
140 @uref{http://fonts.openlilylib.org/} for more information.
143 Grobs and their parents can now be aligned separately allowing
144 more flexibility for grob positions. For example the @q{left} edge of a
145 grob can now be aligned on the @q{center} of its parent.
148 Improvements to the @code{\partial} command have been made to
149 avoid problems when using multiple, parallel contexts.
151 @item @code{\chordmode} can now use @code{< >} and @code{<< >>}
155 The @code{NullVoice} context is now @q{below} @code{Score}.
158 A new command @code{\tagGroup} has now been added. This compliments
159 the existing @code{\keepWithTag} and @code{\removeWithTag} commands.
163 \tagGroup #'(violinI violinII viola cello)
166 declares a list of @q{tags} that belong to a single @q{tag group}.
169 \keepwithTag#'violinI
172 Is now only concerned with @q{tags} from @q{violinI}’s tag group.
174 Any element of the included music tagged with one or more tags from the
175 group, but @emph{not} with @var{violinI}, will be removed.
178 The @code{\addlyrics} function now works with arbitrary contexts
179 incuding @code{Staff}.
182 String numbers can now also be used to print roman numerals
183 (e.g. for unfretted string instruments).
184 @lilypond[verbatim,quote,relative=2]
193 The @code{thin-kern} property of the @code{BarLine} grob has been
194 renamed to @code{segno-kern}.
197 @code{KeyCancellation} grobs now ignore cue clefs (like
198 @code{KeySignature} grobs do).
201 Add support for @code{\once@tie{}\unset}
204 It is now possible to individually color both the dots and parentheses
205 in fret diagrams when using the @code{\fret-diagram-verbose} markup
208 @lilypond[verbatim,quote,relative=1]
211 \override #'(fret-diagram-details . (
212 (finger-code . in-dot))) {
213 \fret-diagram-verbose #'((mute 6)
214 (place-fret 5 3 1 red)
215 (place-fret 4 5 2 inverted)
216 (place-fret 3 5 3 green)
217 (place-fret 2 5 4 blue inverted)
218 (place-fret 1 3 1 violet)
223 \override #'(fret-diagram-details . (
224 (finger-code . below-string))) {
225 \fret-diagram-verbose #'((mute 6)
226 (place-fret 5 3 1 red parenthesized)
227 (place-fret 4 5 2 yellow
230 (place-fret 3 5 3 green)
231 (place-fret 2 5 4 blue )
240 Two new properties have been added for use in
241 @code{fret-diagram-details} when using the @code{\fret-diagram-verbose}
242 markup command; @code{fret-label-horizontal-offset} which affects the
243 @code{fret-label-indication} and @code{paren-padding} which controls the
244 space between the dot and the parentheses surrounding it.
246 @lilypond[verbatim,quote,relative=1]
249 \fret-diagram-verbose #'((mute 6)
253 (place-fret 1 6 4 parenthesized)
258 \override #'(fret-diagram-details . (
259 (fret-label-horizontal-offset . 2)
260 (paren-padding . 0.25))) {
261 \fret-diagram-verbose #'((mute 6)
265 (place-fret 1 6 4 parenthesized)
274 A new markup command @code{\justify-line} has been added. Similar to
275 the @code{\fill-line} markup command except that instead of setting
276 @emph{words} in columns, the @code{\justify-line} command balances the
277 whitespace between them ensuring that when there are three or more
278 words in a markup, the whitespace is always consistent.
280 @lilypond[quote,verbatim,papersize=a6]
281 \markup \fill-line {oooooo oooooo oooooo oooooo}
282 \markup \fill-line {ooooooooo oooooooo oo ooo}
285 @lilypond[quote,verbatim,papersize=a6]
286 \markup \justify-line {oooooo oooooo oooooo oooooo}
287 \markup \justify-line {ooooooooo oooooooo oo ooo}
291 A new command @code{\magnifyMusic} has been added, which allows
292 the notation size to be changed without changing the staff size,
293 while automatically scaling stems, beams, and horizontal spacing.
295 @lilypond[verbatim,quote]
297 \new Voice \relative {
299 <e' e'>4 <f f'>8. <g g'>16 <f f'>8 <e e'>4 r8
301 \new Voice \relative {
304 \override Score.SpacingSpanner.spacing-increment = #(* 1.2 0.63)
305 r32 c'' a c a c a c r c a c a c a c
306 r c a c a c a c a c a c a c a c
313 A new flexible template suitable for a range of choral music, is now
314 provided. This may be used to create simple choral music, with or
315 without piano accompaniment, in two or four staves. Unlike other
316 templates, this template is @q{built-in}, which means it does not
317 need to be copied and edited: instead it is simply @code{\include}'d
318 in the input file. For details, see @rlearning{Built-in templates}.
321 The positioning of tuplet numbers for kneed beams has been significantly
322 improved. Previously, tuplet numbers were placed according to the
323 position of the tuplet bracket, even if it was not printed. This could
324 lead to stranded tuplet numbers. Now they are now positioned
325 closer to the kneed-beam when an appropriate beam segment exists for its
326 placement and when the the bracket is not drawn.
328 Collision detection is also added, offsetting horizontally if too close
329 to an adjoining note column but preserving the number's vertical
330 distance from the kneed beam. If the number itself is too large to
331 fit in the available space the original, bracket-based, positioning
332 system is used instead; and in the event of a collision (e.g. with an
333 accidental) the tuplet number is moved vertically away instead.
335 @lilypond[verbatim,fragment,quote,relative=1]
337 \override Beam.auto-knee-gap = 3
346 The original kneed-beam tuplet behavior is still available through an
347 @code{\override} via a new, @code{knee-to-beam} property.
349 @lilypond[verbatim,fragment,quote,relative=1]
351 \override Beam.auto-knee-gap = 3
352 \override TupletNumber.knee-to-beam = ##f
361 @code{\lyricsto} and @code{\addLyrics} have been @q{harmonized}. Both
362 now accept the same kind of delimited argument list that @code{\lyrics}
363 and @code{\chords} accept. Backward compatibility has been added so
364 music identifiers (i.e. @code{\mus}) are permitted as arguments. A
365 @code{convert-ly} rule has been added that removes redundant uses of
366 @code{\lyricmode} and rearranges combinations with context starters such
367 that @code{\lyricsto} in general is applied last (i.e. like
368 @code{\lyricmode} would be).
371 Scheme functions and identifiers can now be used as output definitions.
374 Scheme expressions can now be used as chord constituents.
377 Improved visual spacing of small and regular @q{MI} Funk and Walker
378 noteheads so they are now the same width as other shaped notes in
379 their respective sets. @code{SOL} noteheads are also now visually
380 improved when used with both the normal Aiken and Sacred Harp heads, as
381 well as with the thin variants.
384 @code{LeftEdge} now has a definable @code{Y-extent} (i.e.vertical). See
385 @rinternals{LeftEdge}.
388 Added a new @code{make-path-stencil} function that supports all
389 @code{path} commands both relative and absolute:
391 @code{lineto}, @code{rlineto}, @code{curveto}, @code{rcurveto},
392 @code{moveto}, @code{rmoveto}, @code{closepath}. The function also
393 supports @q{single-letter} syntax used in standard SVG path commands:
395 @code{L}, @code{l}, @code{C}, @code{c}, @code{M}, @code{m}, @code{Z} and
396 @code{z}. The new command is also backward-compatible with the original
397 @code{make-connected-path-stencil} function. Also see
398 @file{scm/stencil.scm}.
401 Context properties named in the @samp{alternativeRestores} property are
402 restored to their value at the start of the @emph{first} alternative in
403 all subsequent alternatives.
405 Currently the default set restores @q{current meter};
407 @lilypond[verbatim,fragment,quote,relative=2]
409 \repeat volta 2 { c2 e4 | }
418 @q{measure position};
420 @lilypond[verbatim,fragment,quote,relative=2]
422 \repeat volta 2 { c2 e4 | }
425 \set Timing.measurePosition = #(ly:make-moment -1/2)
433 and @q{chord changes};
435 @lilypond[verbatim,fragment,quote]
438 \set chordChanges = ##t
439 \chordmode { c1:m d:m c:m d:m }
442 \repeat volta 2 { \chordmode { c1:m } }
444 { \chordmode { d:m } }
445 { \chordmode { c:m } }
453 Improved MIDI output for breathe marks. After tied notes, breaths take
454 time @emph{only} from the last note of the tie; e.g.
455 @code{@{ c4~ c8 \breathe @}} performs as @code{@{ c4~ c16 r @}} instead
456 of @code{@{ c4 r8 @}}. This is more consistent with articulations and
457 how humans interpret breaths after ties. It now also makes it easier to
458 align simultaneous breathe marks over multiple parts, all with different
462 A new note head style for Tabulature has been added;
463 @code{TabNoteHead.style = #'slash}.
466 Four new Clef glyphs have been added @emph{Double G}, @emph{Tenor G},
467 @emph{Varpercussion} and @emph{varC} and their related tessitura.
468 @lilypond[verbatim,quote,fragment]
469 \override Staff.Clef.full-size-change = ##t
472 \clef "tenorG" c c c c
474 \clef "altovarC" c c c c
475 \clef "tenorvarC" c c c c
476 \clef "baritonevarC" c c c c
477 \clef "varpercussion" c c c c
480 \override Staff.Clef.full-size-change = ##f
483 \clef "tenorG" c c c c
485 \clef "altovarC" c c c c
486 \clef "tenorvarC" c c c c
487 \clef "baritonevarC" c c c
488 \clef "varpercussion" c c c c
492 Isolated durations in music sequences now stand for unpitched
493 notes. This may be useful for specifying rhythms to music or
494 scheme functions. When encountered in the final score, the
495 pitches are provided by the preceding note or chord. Here are two
496 examples where this makes for readable input:
498 @lilypond[verbatim,quote]
499 \new DrumStaff \with { \override StaffSymbol.line-count = 1 }
502 tambourine 8 \tuplet 3/2 { 16 16 16 }
503 8 \tuplet 3/2 { 16 16 16 } 8 8 |
507 @lilypond[verbatim,quote]
508 \new Staff { r16 c'16 ~ 8 ~ 4 ~ 2 | }
512 Beaming exceptions can now be constructed using the
513 @code{\beamExceptions} scheme function. One can now write
515 @lilypond[verbatim,quote,relative=1]
517 \set Timing.beamExceptions =
518 \beamExceptions { 32[ 32] 32[ 32] 32[ 32] }
520 \repeat unfold 6 { c32 } |
524 with multiple exceptions separated with @code{|} bar checks
525 (writing the exception pattern without pitches is convenient but
526 not mandatory). Previously, setting the beam exceptions would
527 have required writing
530 \set Timing.beamExceptions =
532 (end . ;entry for end of beams
533 ( ;start of alist of end points
534 ((1 . 32) . (2 2 2)) ;rule for 1/32 beams -- end each 1/16
539 The most common articulations are now reflected in MIDI output.
540 Accent and marcato make notes louder; staccato, staccatissimo and
541 portato make them shorter. Breath marks shorten the previous
544 This behavior is customizable through the @code{midiLength} and
545 @code{midiExtraVelocity} properties on @code{ArticulationEvent}.
546 See @file{script-init.ly} for examples.
549 The PostScript functionality of stroke adjustment is no longer
550 applied automatically but left to the discretion of the PostScript
551 device (by default, Ghostscript uses it for resolutions up to
552 150dpi when generating raster images). When it is enabled, a more
553 complex drawing algorithm designed to benefit from stroke
554 adjustment is employed mostly for stems and bar lines.
556 Stroke adjustment can be forced by specifying the command line
557 option @samp{-dstrokeadjust} to LilyPond. When generating
558 @code{PDF} files, this will usually result in markedly better
559 looking @code{PDF} previews but significantly larger file size.
560 Print quality at high resolutions will be unaffected.
565 For older news, go to
566 @uref{http://lilypond.org/doc/v2.18/Documentation/changes/},
567 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/},
568 or @uref{../,go back} to the Documentation index.