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 A new page breaking function @code{ly:one-line-auto-height-breaking}
66 places a whole score on a single line and changes the page width
67 to match, just like @code{ly:one-line-breaking}. The difference is that
68 it also automatically modifies the height of the page to fit the height
72 Markup-command @code{\draw-squiggle-line} is now available.
73 Customizing is possible with overrides of @code{thickness}, @code{angularity},
74 @code{height} and @code{orientation}
75 @lilypond[quote,verbatim]
78 \draw-squiggle-line #0.5 #'(3 . 3) ##t
81 \override #'(thickness . 4)
82 \draw-squiggle-line #0.5 #'(3 . -3) ##t
85 \override #'(angularity . -5)
86 \draw-squiggle-line #0.5 #'(-3 . -3) ##t
89 \override #'(angularity . 2)
90 \override #'(height . 0.3)
91 \override #'(orientation . -1)
92 \draw-squiggle-line #0.2 #'(-3 . 3) ##t
97 A new command, @code{\RemoveAllEmptyStaves}, has been made available, which
98 acts exactly like @code{\RemoveEmptyStaves}, except for also removing empty
99 staves on the first system in a score.
102 Markup-commands @code{\undertie} and @code{\overtie} are now available, as well
103 as the generic markup-command @code{\tie}.
104 @lilypond[quote,verbatim]
106 \undertie "undertied"
111 c''1 \prall -\tweak text \markup \tie "131" -1
114 { \voiceOne \m \voiceTwo \m }
118 @code{TabStaff} is now able to print micro-tones for bendings etc.
119 @lilypond[quote,verbatim]
123 supportNonIntegerFret = ##t
127 mus = \relative { c'4 cih d dih }
130 \new Staff << \clef "G_8" \mus >>
136 Two new styles of whiteout are now available. The @code{outline} style
137 approximates the contours of a glyph's outline, and its shape is
138 produced from multiple displaced copies of the glyph. The
139 @code{rounded-box} style produces a rounded rectangle shape. For all
140 three styles, including the default @code{box} style, the whiteout
141 shape's @code{thickness}, as a multiple of staff-line thickness, can be
144 @lilypond[verbatim,quote]
147 \filled-box #'(-1 . 15) #'(-3 . 4) #1
148 \override #'(thickness . 3)
149 \whiteout whiteout-box
153 \filled-box #'(-1 . 24) #'(-3 . 4) #1
154 \override #'(style . rounded-box)
155 \override #'(thickness . 3)
156 \whiteout whiteout-rounded-box
160 \filled-box #'(-1 . 18) #'(-3 . 4) #1
161 \override #'(style . outline)
162 \override #'(thickness . 3)
163 \whiteout whiteout-outline
166 \override Staff.Clef.whiteout-style = #'outline
167 \override Staff.Clef.whiteout = 3
173 All of @code{\override}, @code{\revert}, @code{\set}, and
174 @code{\unset} now work with the @code{\once} prefix for making
176 @lilypond[quote,verbatim]
179 \override NoteHead.color = #red
181 \once \override NoteHead.color = #green
183 \once \revert NoteHead.color
185 \revert NoteHead.color
191 When outputting MIDI, LilyPond will now store the @code{title}
192 defined in a score's @code{\header} block (or, if there is no
193 such definition on the @code{\score} level, the first such
194 definition found in a @code{\header} block of the score's
195 enclosing @code{\bookpart}, @code{\book}, or top-level scope)
196 as the name of the MIDI sequence in the MIDI file. Optionally,
197 the name of the MIDI sequence can be overridden using the new
198 @code{midititle} @code{\header} field independently of
199 @code{title} (for example, in case @code{title} contains markup
200 code which does not render as plain text in a satisfactory way
204 Music (and scheme and void) functions and markup commands that
205 just supply the final parameters to a chain of overrides, music
206 function and markup command calls can now be defined in the form
207 of just writing the expression cut short with @code{\etc}.
209 @lilypond[verbatim,quote]
210 bold-red-markup = \markup \bold \with-color #red \etc
211 highlight = \tweak font-size 3 \tweak color #red \etc
213 \markup \bold-red "text"
214 \markuplist \column-lines \bold-red { One Two }
216 { c' \highlight d' e'2-\highlight -! }
220 LilyPond functions defined with @code{define-music-function},
221 @code{define-event-function}, @code{define-scheme-function} and
222 @code{define-void-function} can now be directly called from Scheme
223 as if they were genuine Scheme procedures. Argument checking and
224 matching will still be performed in the same manner as when
225 calling the function through LilyPond input. This includes the
226 insertion of defaults for optional arguments not matching their
227 predicates. Instead of using @code{\default} in the actual
228 argument list for explicitly skipping a sequence of optional
229 arguments, @code{*unspecified*} can be employed.
232 Current input location and parser are now stored in GUILE fluids
233 and can be referenced via the function calls @code{(*location*)}
234 and @code{(*parser*)}. Consequently, a lot of functions
235 previously taking an explicit @code{parser} argument no longer do
238 Functions defined with @code{define-music-function},
239 @code{define-event-function}, @code{define-scheme-function} and
240 @code{define-void-function} no longer use @code{parser} and
241 @code{location} arguments.
243 With those particular definitions, LilyPond will try to recognize
244 legacy use of @code{parser} and @code{location} arguments,
245 providing backwards-compatible semantics for some time.
248 In the "english" notename language, the long notenames for pitches
249 with accidentals now contain a hyphen for better readability. You
254 instead of the previous
259 Double accidentals do not get another hyphen, so the Dutch
260 @code{cisis} has the long English notename @code{c-sharpsharp}.
263 The visual style of tremolo slashes (shape, style and slope)
264 is now more finely controlled.
265 @lilypond[quote,relative=2]
267 \override StemTremolo.shape = #'beam-like
269 \override StemTremolo.style = #'constant
276 Multi-measure rests have length according to their total duration,
277 under the control of @code{MultiMeasureRest.space-increment}.
279 { \compressFullBarRests
280 \override Staff.MultiMeasureRest.space-increment = 3.0
285 Page numbers may now be printed in roman numerals, by setting the
286 @code{page-number-type} paper variable.
289 It is now possible to use @code{\time} and @code{\partial}
290 together to change the time signature in mid measure.
292 @lilypond[verbatim,quote,relative=1]
293 \override Score.BarNumber.break-visibility = #end-of-line-invisible
294 \partial 4 \time 3/4 f4 | 2 4 | 2 \bar "||"
295 \time 9/8 \partial 4. f8 8 8 | 2. 8 8 8 |
299 It is now possible to override the @code{text} property of
302 @lilypond[verbatim,fragment,quote]
304 \new ChordNames \chordmode {
306 \once \override ChordName.text = #"foo"
313 Improved horizontal alignment when using @code{TextScript},
314 with @code{DynamicText} or @code{LyricText}.
317 A new command @code{\magnifyStaff} has been added which scales staff
318 sizes, staff lines, bar lines, beamlets and horizontal spacing generally
319 at the @code{Staff} context level. Staff lines are prevented from being
320 scaled smaller than the default since the thickness of stems, slurs, and
321 the like are all based on the staff line thickness.
324 @code{InstrumentName} now supports @code{text-interface}.
327 There is now support for controlling the @q{expression level} of
328 MIDI channels using the @code{Staff.midiExpression} context property.
329 This can be used to alter the perceived volume of even sustained notes
330 (albeit in a very @q{low-level} way) and accepts a number value between
331 @code{0.0} and @code{1.0}.
336 midiExpression = #0.6
337 midiInstrument = #"clarinet"
342 \set Staff.midiExpression = #0.7 s4\f\<
343 \set Staff.midiExpression = #0.8 s4
344 \set Staff.midiExpression = #0.9 s4
345 \set Staff.midiExpression = #1.0 s4
347 \set Staff.midiExpression = #0.9 s4\>
348 \set Staff.midiExpression = #0.8 s4
349 \set Staff.midiExpression = #0.7 s4
350 \set Staff.midiExpression = #0.6 s4\!
358 Support for making it easier to use alternative @q{music} fonts other
359 than the default Emmentaler in LilyPond has been added. See
360 @uref{http://fonts.openlilylib.org/} for more information.
363 Grobs and their parents can now be aligned separately allowing
364 more flexibility for grob positions. For example the @q{left} edge of a
365 grob can now be aligned on the @q{center} of its parent.
368 Improvements to the @code{\partial} command have been made to
369 avoid problems when using multiple, parallel contexts.
371 @item @code{\chordmode} can now use @code{< >} and @code{<< >>}
375 A new command @code{\tagGroup} has now been added. This complements
376 the existing @code{\keepWithTag} and @code{\removeWithTag} commands.
380 \tagGroup #'(violinI violinII viola cello)
383 declares a list of @q{tags} that belong to a single @q{tag group}.
386 \keepWithTag #'violinI
389 Is now only concerned with @q{tags} from @q{violinI}’s tag group.
391 Any element of the included music tagged with one or more tags from the
392 group, but @emph{not} with @var{violinI}, will be removed.
395 The @code{\addlyrics} function now works with arbitrary contexts
396 incuding @code{Staff}.
399 String numbers can now also be used to print roman numerals
400 (e.g. for unfretted string instruments).
401 @lilypond[verbatim,quote,relative=2]
410 The @code{thin-kern} property of the @code{BarLine} grob has been
411 renamed to @code{segno-kern}.
414 @code{KeyCancellation} grobs now ignore cue clefs (like
415 @code{KeySignature} grobs do).
418 Add support for @code{\once@tie{}\unset}
421 It is now possible to individually color both the dots and parentheses
422 in fret diagrams when using the @code{\fret-diagram-verbose} markup
425 @lilypond[verbatim,quote,relative=1]
428 \override #'(fret-diagram-details . (
429 (finger-code . in-dot))) {
430 \fret-diagram-verbose #'((mute 6)
431 (place-fret 5 3 1 red)
432 (place-fret 4 5 2 inverted)
433 (place-fret 3 5 3 green)
434 (place-fret 2 5 4 blue inverted)
435 (place-fret 1 3 1 violet)
440 \override #'(fret-diagram-details . (
441 (finger-code . below-string))) {
442 \fret-diagram-verbose #'((mute 6)
443 (place-fret 5 3 1 red parenthesized)
444 (place-fret 4 5 2 yellow
447 (place-fret 3 5 3 green)
448 (place-fret 2 5 4 blue )
457 Two new properties have been added for use in
458 @code{fret-diagram-details} when using the @code{\fret-diagram-verbose}
459 markup command; @code{fret-label-horizontal-offset} which affects the
460 @code{fret-label-indication} and @code{paren-padding} which controls the
461 space between the dot and the parentheses surrounding it.
463 @lilypond[verbatim,quote,relative=1]
466 \fret-diagram-verbose #'((mute 6)
470 (place-fret 1 6 4 parenthesized)
475 \override #'(fret-diagram-details . (
476 (fret-label-horizontal-offset . 2)
477 (paren-padding . 0.25))) {
478 \fret-diagram-verbose #'((mute 6)
482 (place-fret 1 6 4 parenthesized)
491 A new markup command @code{\justify-line} has been added. Similar to
492 the @code{\fill-line} markup command except that instead of setting
493 @emph{words} in columns, the @code{\justify-line} command balances the
494 whitespace between them ensuring that when there are three or more
495 words in a markup, the whitespace is always consistent.
497 @lilypond[quote,verbatim,papersize=a6]
498 \markup \fill-line {oooooo oooooo oooooo oooooo}
499 \markup \fill-line {ooooooooo oooooooo oo ooo}
502 @lilypond[quote,verbatim,papersize=a6]
503 \markup \justify-line {oooooo oooooo oooooo oooooo}
504 \markup \justify-line {ooooooooo oooooooo oo ooo}
508 A new command @code{\magnifyMusic} has been added, which allows
509 the notation size to be changed without changing the staff size,
510 while automatically scaling stems, beams, and horizontal spacing.
512 @lilypond[verbatim,quote]
514 \new Voice \relative {
516 <e' e'>4 <f f'>8. <g g'>16 <f f'>8 <e e'>4 r8
518 \new Voice \relative {
521 \override Score.SpacingSpanner.spacing-increment = #(* 1.2 0.63)
522 r32 c'' a c a c a c r c a c a c a c
523 r c a c a c a c a c a c a c a c
530 A new flexible template suitable for a range of choral music, is now
531 provided. This may be used to create simple choral music, with or
532 without piano accompaniment, in two or four staves. Unlike other
533 templates, this template is @q{built-in}, which means it does not
534 need to be copied and edited: instead it is simply @code{\include}'d
535 in the input file. For details, see @rlearning{Built-in templates}.
538 The positioning of tuplet numbers for kneed beams has been significantly
539 improved. Previously, tuplet numbers were placed according to the
540 position of the tuplet bracket, even if it was not printed. This could
541 lead to stranded tuplet numbers. Now they are now positioned
542 closer to the kneed-beam when an appropriate beam segment exists for its
543 placement and when the the bracket is not drawn.
545 Collision detection is also added, offsetting horizontally if too close
546 to an adjoining note column but preserving the number's vertical
547 distance from the kneed beam. If the number itself is too large to
548 fit in the available space the original, bracket-based, positioning
549 system is used instead; and in the event of a collision (e.g. with an
550 accidental) the tuplet number is moved vertically away instead.
552 @lilypond[verbatim,fragment,quote,relative=1]
554 \override Beam.auto-knee-gap = 3
563 The original kneed-beam tuplet behavior is still available through an
564 @code{\override} via a new, @code{knee-to-beam} property.
566 @lilypond[verbatim,fragment,quote,relative=1]
568 \override Beam.auto-knee-gap = 3
569 \override TupletNumber.knee-to-beam = ##f
578 @code{\lyricsto} and @code{\addLyrics} have been @q{harmonized}. Both
579 now accept the same kind of delimited argument list that @code{\lyrics}
580 and @code{\chords} accept. Backward compatibility has been added so
581 music identifiers (i.e. @code{\mus}) are permitted as arguments. A
582 @code{convert-ly} rule has been added that removes redundant uses of
583 @code{\lyricmode} and rearranges combinations with context starters such
584 that @code{\lyricsto} in general is applied last (i.e. like
585 @code{\lyricmode} would be).
588 Scheme functions and identifiers can now be used as output definitions.
591 Scheme expressions can now be used as chord constituents.
594 Improved visual spacing of small and regular @q{MI} Funk and Walker
595 noteheads so they are now the same width as other shaped notes in
596 their respective sets. @code{SOL} noteheads are also now visually
597 improved when used with both the normal Aiken and Sacred Harp heads, as
598 well as with the thin variants.
601 @code{LeftEdge} now has a definable @code{Y-extent} (i.e.vertical). See
602 @rinternals{LeftEdge}.
605 Added a new @code{make-path-stencil} function that supports all
606 @code{path} commands both relative and absolute:
608 @code{lineto}, @code{rlineto}, @code{curveto}, @code{rcurveto},
609 @code{moveto}, @code{rmoveto}, @code{closepath}. The function also
610 supports @q{single-letter} syntax used in standard SVG path commands:
612 @code{L}, @code{l}, @code{C}, @code{c}, @code{M}, @code{m}, @code{Z} and
613 @code{z}. The new command is also backward-compatible with the original
614 @code{make-connected-path-stencil} function. Also see
615 @file{scm/stencil.scm}.
618 Context properties named in the @samp{alternativeRestores} property are
619 restored to their value at the start of the @emph{first} alternative in
620 all subsequent alternatives.
622 Currently the default set restores @q{current meter};
624 @lilypond[verbatim,fragment,quote,relative=2]
626 \repeat volta 2 { c2 e4 | }
635 @q{measure position};
637 @lilypond[verbatim,fragment,quote,relative=2]
639 \repeat volta 2 { c2 e4 | }
642 \set Timing.measurePosition = #(ly:make-moment -1/2)
650 and @q{chord changes};
652 @lilypond[verbatim,fragment,quote]
655 \set chordChanges = ##t
656 \chordmode { c1:m d:m c:m d:m }
659 \repeat volta 2 { \chordmode { c1:m } }
661 { \chordmode { d:m } }
662 { \chordmode { c:m } }
670 Improved MIDI output for breathe marks. After tied notes, breaths take
671 time @emph{only} from the last note of the tie; e.g.
672 @code{@{ c4~ c8 \breathe @}} performs as @code{@{ c4~ c16 r @}} instead
673 of @code{@{ c4 r8 @}}. This is more consistent with articulations and
674 how humans interpret breaths after ties. It now also makes it easier to
675 align simultaneous breathe marks over multiple parts, all with different
679 A new note head style for Tabulature has been added;
680 @code{TabNoteHead.style = #'slash}.
683 Four new Clef glyphs have been added @emph{Double G}, @emph{Tenor G},
684 @emph{Varpercussion} and @emph{varC} and their related tessitura.
685 @lilypond[verbatim,quote,fragment]
686 \override Staff.Clef.full-size-change = ##t
689 \clef "tenorG" c c c c
691 \clef "altovarC" c c c c
692 \clef "tenorvarC" c c c c
693 \clef "baritonevarC" c c c c
694 \clef "varpercussion" c c c c
697 \override Staff.Clef.full-size-change = ##f
700 \clef "tenorG" c c c c
702 \clef "altovarC" c c c c
703 \clef "tenorvarC" c c c c
704 \clef "baritonevarC" c c c
705 \clef "varpercussion" c c c c
709 Isolated durations in music sequences now stand for unpitched
710 notes. This may be useful for specifying rhythms to music or
711 scheme functions. When encountered in the final score, the
712 pitches are provided by the preceding note or chord. Here are two
713 examples where this makes for readable input:
715 @lilypond[verbatim,quote]
716 \new DrumStaff \with { \override StaffSymbol.line-count = 1 }
719 tambourine 8 \tuplet 3/2 { 16 16 16 }
720 8 \tuplet 3/2 { 16 16 16 } 8 8 |
724 @lilypond[verbatim,quote]
725 \new Staff { r16 c'16 ~ 8 ~ 4 ~ 2 | }
729 @code{\displayLilyMusic} and its underlying Scheme functions no
730 longer omit redundant note durations. This makes it easier to
731 reliably recognize and format standalone durations in expressions
738 Beaming exceptions can now be constructed using the
739 @code{\beamExceptions} scheme function. One can now write
741 @lilypond[verbatim,quote,relative=1]
743 \set Timing.beamExceptions =
744 \beamExceptions { 32[ 32] 32[ 32] 32[ 32] }
746 \repeat unfold 6 { c32 } |
750 with multiple exceptions separated with @code{|} bar checks
751 (writing the exception pattern without pitches is convenient but
752 not mandatory). Previously, setting the beam exceptions would
753 have required writing
756 \set Timing.beamExceptions =
758 (end . ;entry for end of beams
759 ( ;start of alist of end points
760 ((1 . 32) . (2 2 2)) ;rule for 1/32 beams -- end each 1/16
765 The most common articulations are now reflected in MIDI output.
766 Accent and marcato make notes louder; staccato, staccatissimo and
767 portato make them shorter. Breath marks shorten the previous
770 This behavior is customizable through the @code{midiLength} and
771 @code{midiExtraVelocity} properties on @code{ArticulationEvent}.
772 See @file{script-init.ly} for examples.
775 The PostScript functionality of stroke adjustment is no longer
776 applied automatically but left to the discretion of the PostScript
777 device (by default, Ghostscript uses it for resolutions up to
778 150dpi when generating raster images). When it is enabled, a more
779 complex drawing algorithm designed to benefit from stroke
780 adjustment is employed mostly for stems and bar lines.
782 Stroke adjustment can be forced by specifying the command line
783 option @samp{-dstrokeadjust} to LilyPond. When generating
784 @code{PDF} files, this will usually result in markedly better
785 looking @code{PDF} previews but significantly larger file size.
786 Print quality at high resolutions will be unaffected.
791 For older news, go to
792 @uref{http://lilypond.org/doc/v2.18/Documentation/changes/},
793 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/},
794 or @uref{../,go back} to the Documentation index.