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 LilyPond functions defined with @code{define-music-function},
66 @code{define-event-function}, @code{define-scheme-function} and
67 @code{define-void-function} can now be directly called from Scheme
68 as if they were genuine Scheme procedures. Argument checking and
69 matching will still be performed in the same manner as when
70 calling the function through LilyPond input. This includes the
71 insertion of defaults for optional arguments not matching their
72 predicates. Instead of using @code{\default} in the actual
73 argument list for explicitly skipping a sequence of optional
74 arguments, @code{*unspecified*} can be employed.
77 The definition of LilyPond functions with
78 @code{define-music-function}, @code{define-event-function},
79 @code{define-scheme-function} and @code{define-void-function} no
80 longer requires specification of @code{parser} and @code{location}
81 arguments. Current parser and input location are part of the
82 current dynamic state and can be accessed with the function calls
83 @code{(*parser*)} and @code{(*location*)} when required.
85 LilyPond makes a best-faith attempt of recognizing legacy use of
86 @code{parser} and @code{location} arguments and will provide
87 backwards-compatible semantics for some time.
90 In the "english" notename language, the long notenames for pitches
91 with accidentals now contain a hyphen for better readability. You
96 instead of the previous
101 Double accidentals do not get another hyphen, so the Dutch
102 @code{cisis} has the long English notename @code{c-sharpsharp}.
105 The visual style of tremolo slashes (shape, style and slope)
106 is now more finely controlled.
107 @lilypond[quote,relative=2]
109 \override StemTremolo.shape = #'beam-like
111 \override StemTremolo.style = #'constant
118 Multi-measure rests have length according to their total duration,
119 under the control of @code{MultiMeasureRest.space-increment}.
121 { \compressFullBarRests
122 \override Staff.MultiMeasureRest.space-increment = 3.0
127 Page numbers may now be printed in roman numerals, by setting the
128 @code{page-number-type} paper variable.
131 It is now possible to use @code{\time} and @code{\partial}
132 together to change the time signature in mid measure.
134 @lilypond[verbatim,quote,relative=1]
135 \override Score.BarNumber.break-visibility = #end-of-line-invisible
136 \partial 4 \time 3/4 f4 | 2 4 | 2 \bar "||"
137 \time 9/8 \partial 4. f8 8 8 | 2. 8 8 8 |
141 It is now possible to override the @code{text} property of
144 @lilypond[verbatim,fragment,quote]
146 \new ChordNames \chordmode {
148 \once \override ChordName.text = #"foo"
155 Improved horizontal alignment when using @code{TextScript},
156 with @code{DynamicText} or @code{LyricText}.
159 A new command @code{\magnifyStaff} has been added which scales staff
160 sizes, staff lines, bar lines, beamlets and horizontal spacing generally
161 at the @code{Staff} context level. Staff lines are prevented from being
162 scaled smaller than the default since the thickness of stems, slurs, and
163 the like are all based on the staff line thickness.
166 @code{InstrumentName} now supports @code{text-interface}.
169 There is now support for controlling the @q{expression level} of
170 MIDI channels using the @code{Staff.midiExpression} context property.
171 This can be used to alter the perceived volume of even sustained notes
172 (albeit in a very @q{low-level} way) and accepts a number value between
173 @code{0.0} and @code{1.0}.
178 midiExpression = #0.6
179 midiInstrument = #"clarinet"
184 \set Staff.midiExpression = #0.7 s4\f\<
185 \set Staff.midiExpression = #0.8 s4
186 \set Staff.midiExpression = #0.9 s4
187 \set Staff.midiExpression = #1.0 s4
189 \set Staff.midiExpression = #0.9 s4\>
190 \set Staff.midiExpression = #0.8 s4
191 \set Staff.midiExpression = #0.7 s4
192 \set Staff.midiExpression = #0.6 s4\!
200 Support for making it easier to use alternative @q{music} fonts other
201 than the default Emmentaler in LilyPond has been added. See
202 @uref{http://fonts.openlilylib.org/} for more information.
205 Grobs and their parents can now be aligned separately allowing
206 more flexibility for grob positions. For example the @q{left} edge of a
207 grob can now be aligned on the @q{center} of its parent.
210 Improvements to the @code{\partial} command have been made to
211 avoid problems when using multiple, parallel contexts.
213 @item @code{\chordmode} can now use @code{< >} and @code{<< >>}
217 The @code{NullVoice} context is now @q{below} @code{Score}.
220 A new command @code{\tagGroup} has now been added. This compliments
221 the existing @code{\keepWithTag} and @code{\removeWithTag} commands.
225 \tagGroup #'(violinI violinII viola cello)
228 declares a list of @q{tags} that belong to a single @q{tag group}.
231 \keepwithTag#'violinI
234 Is now only concerned with @q{tags} from @q{violinI}’s tag group.
236 Any element of the included music tagged with one or more tags from the
237 group, but @emph{not} with @var{violinI}, will be removed.
240 The @code{\addlyrics} function now works with arbitrary contexts
241 incuding @code{Staff}.
244 String numbers can now also be used to print roman numerals
245 (e.g. for unfretted string instruments).
246 @lilypond[verbatim,quote,relative=2]
255 The @code{thin-kern} property of the @code{BarLine} grob has been
256 renamed to @code{segno-kern}.
259 @code{KeyCancellation} grobs now ignore cue clefs (like
260 @code{KeySignature} grobs do).
263 Add support for @code{\once@tie{}\unset}
266 It is now possible to individually color both the dots and parentheses
267 in fret diagrams when using the @code{\fret-diagram-verbose} markup
270 @lilypond[verbatim,quote,relative=1]
273 \override #'(fret-diagram-details . (
274 (finger-code . in-dot))) {
275 \fret-diagram-verbose #'((mute 6)
276 (place-fret 5 3 1 red)
277 (place-fret 4 5 2 inverted)
278 (place-fret 3 5 3 green)
279 (place-fret 2 5 4 blue inverted)
280 (place-fret 1 3 1 violet)
285 \override #'(fret-diagram-details . (
286 (finger-code . below-string))) {
287 \fret-diagram-verbose #'((mute 6)
288 (place-fret 5 3 1 red parenthesized)
289 (place-fret 4 5 2 yellow
292 (place-fret 3 5 3 green)
293 (place-fret 2 5 4 blue )
302 Two new properties have been added for use in
303 @code{fret-diagram-details} when using the @code{\fret-diagram-verbose}
304 markup command; @code{fret-label-horizontal-offset} which affects the
305 @code{fret-label-indication} and @code{paren-padding} which controls the
306 space between the dot and the parentheses surrounding it.
308 @lilypond[verbatim,quote,relative=1]
311 \fret-diagram-verbose #'((mute 6)
315 (place-fret 1 6 4 parenthesized)
320 \override #'(fret-diagram-details . (
321 (fret-label-horizontal-offset . 2)
322 (paren-padding . 0.25))) {
323 \fret-diagram-verbose #'((mute 6)
327 (place-fret 1 6 4 parenthesized)
336 A new markup command @code{\justify-line} has been added. Similar to
337 the @code{\fill-line} markup command except that instead of setting
338 @emph{words} in columns, the @code{\justify-line} command balances the
339 whitespace between them ensuring that when there are three or more
340 words in a markup, the whitespace is always consistent.
342 @lilypond[quote,verbatim,papersize=a6]
343 \markup \fill-line {oooooo oooooo oooooo oooooo}
344 \markup \fill-line {ooooooooo oooooooo oo ooo}
347 @lilypond[quote,verbatim,papersize=a6]
348 \markup \justify-line {oooooo oooooo oooooo oooooo}
349 \markup \justify-line {ooooooooo oooooooo oo ooo}
353 A new command @code{\magnifyMusic} has been added, which allows
354 the notation size to be changed without changing the staff size,
355 while automatically scaling stems, beams, and horizontal spacing.
357 @lilypond[verbatim,quote]
359 \new Voice \relative {
361 <e' e'>4 <f f'>8. <g g'>16 <f f'>8 <e e'>4 r8
363 \new Voice \relative {
366 \override Score.SpacingSpanner.spacing-increment = #(* 1.2 0.63)
367 r32 c'' a c a c a c r c a c a c a c
368 r c a c a c a c a c a c a c a c
375 A new flexible template suitable for a range of choral music, is now
376 provided. This may be used to create simple choral music, with or
377 without piano accompaniment, in two or four staves. Unlike other
378 templates, this template is @q{built-in}, which means it does not
379 need to be copied and edited: instead it is simply @code{\include}'d
380 in the input file. For details, see @rlearning{Built-in templates}.
383 The positioning of tuplet numbers for kneed beams has been significantly
384 improved. Previously, tuplet numbers were placed according to the
385 position of the tuplet bracket, even if it was not printed. This could
386 lead to stranded tuplet numbers. Now they are now positioned
387 closer to the kneed-beam when an appropriate beam segment exists for its
388 placement and when the the bracket is not drawn.
390 Collision detection is also added, offsetting horizontally if too close
391 to an adjoining note column but preserving the number's vertical
392 distance from the kneed beam. If the number itself is too large to
393 fit in the available space the original, bracket-based, positioning
394 system is used instead; and in the event of a collision (e.g. with an
395 accidental) the tuplet number is moved vertically away instead.
397 @lilypond[verbatim,fragment,quote,relative=1]
399 \override Beam.auto-knee-gap = 3
408 The original kneed-beam tuplet behavior is still available through an
409 @code{\override} via a new, @code{knee-to-beam} property.
411 @lilypond[verbatim,fragment,quote,relative=1]
413 \override Beam.auto-knee-gap = 3
414 \override TupletNumber.knee-to-beam = ##f
423 @code{\lyricsto} and @code{\addLyrics} have been @q{harmonized}. Both
424 now accept the same kind of delimited argument list that @code{\lyrics}
425 and @code{\chords} accept. Backward compatibility has been added so
426 music identifiers (i.e. @code{\mus}) are permitted as arguments. A
427 @code{convert-ly} rule has been added that removes redundant uses of
428 @code{\lyricmode} and rearranges combinations with context starters such
429 that @code{\lyricsto} in general is applied last (i.e. like
430 @code{\lyricmode} would be).
433 Scheme functions and identifiers can now be used as output definitions.
436 Scheme expressions can now be used as chord constituents.
439 Improved visual spacing of small and regular @q{MI} Funk and Walker
440 noteheads so they are now the same width as other shaped notes in
441 their respective sets. @code{SOL} noteheads are also now visually
442 improved when used with both the normal Aiken and Sacred Harp heads, as
443 well as with the thin variants.
446 @code{LeftEdge} now has a definable @code{Y-extent} (i.e.vertical). See
447 @rinternals{LeftEdge}.
450 Added a new @code{make-path-stencil} function that supports all
451 @code{path} commands both relative and absolute:
453 @code{lineto}, @code{rlineto}, @code{curveto}, @code{rcurveto},
454 @code{moveto}, @code{rmoveto}, @code{closepath}. The function also
455 supports @q{single-letter} syntax used in standard SVG path commands:
457 @code{L}, @code{l}, @code{C}, @code{c}, @code{M}, @code{m}, @code{Z} and
458 @code{z}. The new command is also backward-compatible with the original
459 @code{make-connected-path-stencil} function. Also see
460 @file{scm/stencil.scm}.
463 Context properties named in the @samp{alternativeRestores} property are
464 restored to their value at the start of the @emph{first} alternative in
465 all subsequent alternatives.
467 Currently the default set restores @q{current meter};
469 @lilypond[verbatim,fragment,quote,relative=2]
471 \repeat volta 2 { c2 e4 | }
480 @q{measure position};
482 @lilypond[verbatim,fragment,quote,relative=2]
484 \repeat volta 2 { c2 e4 | }
487 \set Timing.measurePosition = #(ly:make-moment -1/2)
495 and @q{chord changes};
497 @lilypond[verbatim,fragment,quote]
500 \set chordChanges = ##t
501 \chordmode { c1:m d:m c:m d:m }
504 \repeat volta 2 { \chordmode { c1:m } }
506 { \chordmode { d:m } }
507 { \chordmode { c:m } }
515 Improved MIDI output for breathe marks. After tied notes, breaths take
516 time @emph{only} from the last note of the tie; e.g.
517 @code{@{ c4~ c8 \breathe @}} performs as @code{@{ c4~ c16 r @}} instead
518 of @code{@{ c4 r8 @}}. This is more consistent with articulations and
519 how humans interpret breaths after ties. It now also makes it easier to
520 align simultaneous breathe marks over multiple parts, all with different
524 A new note head style for Tabulature has been added;
525 @code{TabNoteHead.style = #'slash}.
528 Four new Clef glyphs have been added @emph{Double G}, @emph{Tenor G},
529 @emph{Varpercussion} and @emph{varC} and their related tessitura.
530 @lilypond[verbatim,quote,fragment]
531 \override Staff.Clef.full-size-change = ##t
534 \clef "tenorG" c c c c
536 \clef "altovarC" c c c c
537 \clef "tenorvarC" c c c c
538 \clef "baritonevarC" c c c c
539 \clef "varpercussion" c c c c
542 \override Staff.Clef.full-size-change = ##f
545 \clef "tenorG" c c c c
547 \clef "altovarC" c c c c
548 \clef "tenorvarC" c c c c
549 \clef "baritonevarC" c c c
550 \clef "varpercussion" c c c c
554 Isolated durations in music sequences now stand for unpitched
555 notes. This may be useful for specifying rhythms to music or
556 scheme functions. When encountered in the final score, the
557 pitches are provided by the preceding note or chord. Here are two
558 examples where this makes for readable input:
560 @lilypond[verbatim,quote]
561 \new DrumStaff \with { \override StaffSymbol.line-count = 1 }
564 tambourine 8 \tuplet 3/2 { 16 16 16 }
565 8 \tuplet 3/2 { 16 16 16 } 8 8 |
569 @lilypond[verbatim,quote]
570 \new Staff { r16 c'16 ~ 8 ~ 4 ~ 2 | }
574 @code{\displayLilyMusic} and its underlying Scheme functions no
575 longer omit redundant note durations. This makes it easier to
576 reliably recognize and format standalone durations in expressions
583 Beaming exceptions can now be constructed using the
584 @code{\beamExceptions} scheme function. One can now write
586 @lilypond[verbatim,quote,relative=1]
588 \set Timing.beamExceptions =
589 \beamExceptions { 32[ 32] 32[ 32] 32[ 32] }
591 \repeat unfold 6 { c32 } |
595 with multiple exceptions separated with @code{|} bar checks
596 (writing the exception pattern without pitches is convenient but
597 not mandatory). Previously, setting the beam exceptions would
598 have required writing
601 \set Timing.beamExceptions =
603 (end . ;entry for end of beams
604 ( ;start of alist of end points
605 ((1 . 32) . (2 2 2)) ;rule for 1/32 beams -- end each 1/16
610 The most common articulations are now reflected in MIDI output.
611 Accent and marcato make notes louder; staccato, staccatissimo and
612 portato make them shorter. Breath marks shorten the previous
615 This behavior is customizable through the @code{midiLength} and
616 @code{midiExtraVelocity} properties on @code{ArticulationEvent}.
617 See @file{script-init.ly} for examples.
620 The PostScript functionality of stroke adjustment is no longer
621 applied automatically but left to the discretion of the PostScript
622 device (by default, Ghostscript uses it for resolutions up to
623 150dpi when generating raster images). When it is enabled, a more
624 complex drawing algorithm designed to benefit from stroke
625 adjustment is employed mostly for stems and bar lines.
627 Stroke adjustment can be forced by specifying the command line
628 option @samp{-dstrokeadjust} to LilyPond. When generating
629 @code{PDF} files, this will usually result in markedly better
630 looking @code{PDF} previews but significantly larger file size.
631 Print quality at high resolutions will be unaffected.
636 For older news, go to
637 @uref{http://lilypond.org/doc/v2.18/Documentation/changes/},
638 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/},
639 or @uref{../,go back} to the Documentation index.