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.16 since 2.14
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 Support for Kievan square notation:
65 @lilypond[quote,relative=1,verbatim]
74 Augmentation dots now avoid the other voice in two-voice polyphony
75 so that users can move the @code{Dot_column_engraver} to set dots
76 independently for each @code{Voice}.
81 \remove Dot_column_engraver
84 \consists Dot_column_engraver
89 <d f g>4. <d f g> <f, g> b
91 <f g b>4. <g b d> <b d> <e, g>
96 A Scheme function to adjust the control points of curves such as slurs
97 and ties, developed by several users, is now included in LilyPond.
98 @lilypond[quote,verbatim,relative=2]
100 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0))
105 Use of @code{\tempo} specifications in @code{\midi} blocks (removed in
106 2.9.16 in favor of explicit @code{tempoWholesPerMinute} settings) has
107 seen a revival: now any kind of property-setting music is turned into
108 context definitions within output specifications, allowing for
111 \layout @{ \accidentalStyle modern @}
112 \midi @{ \tempo 4. = 66 @}
116 The LilyPond G clef has been redesigned - upper loop is now more balanced,
117 bottom crook sticks out less and the "spine" (main vertical line) is more
118 evenly curved. The old and new versions can be compared by looking at the
120 @uref{http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs, old version},
121 @uref{http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs, new version}.
124 Lilypond's stencil commands have been simplified to allow for less code
125 duplication and better height approximations of graphical objects. The
126 following stencil commands have been eliminated:
129 @item @code{bezier-sandwich}
131 @item @code{dashed-slur}
134 @item @code{repeat-slash}
135 @item @code{zigzag-line}
139 Flags are now treated as separate objects rather than as stem parts.
140 @lilypond[fragment,quote,relative=2]
141 \override Flag #'color = #red
146 Two alternative methods for bar numbering can be set, especially for
147 when using repeated music;
149 @lilypond[fragment,quote,relative=1,noragged-right]
151 \set Score.alternativeNumberingStyle = #'numbers
152 \repeat volta 3 { c4 d e f | }
154 { c4 d e f | c2 d \break }
155 { f4 g a b | f4 g a b | f2 a | \break }
159 \set Score.alternativeNumberingStyle = #'numbers-with-letters
160 \repeat volta 3 { c,4 d e f | }
162 { c4 d e f | c2 d \break }
163 { f4 g a b | f4 g a b | f2 a | \break }
171 The following is a fundamental change in LilyPond's music
172 representation: Rhythmic events like @code{LyricEvent} and
173 @code{NoteEvent} are no longer wrapped in @code{EventChord} unless they
174 have been actually entered as part of a chord in the input. If you
175 manipulate music expressions in Scheme, the new behavior may require
176 changes in your code. Calling the music function @code{\eventChords} or
177 the Scheme function @code{event-chord-wrap!} converts to the old
178 representation; using one of those might be easiest for keeping legacy
181 The following three items are consequences of this change.
184 The repetitive chord entry aid @code{q} has been reimplemented.
185 Repeated chords are now replaced right before interpreting a music
186 expression. In case the user wants to retain some events of the
187 original chord, he can run the repeat chord replacement function
188 @code{\chordRepeats} manually.
191 String numbers and right hand fingerings on single notes now appear
192 without having to be written inside of chord brackets.
195 Music functions now work the same when used inside or outside of chords,
196 including all the possibilities of argument parsing. Music variables
197 can be used inside of chords: a construct like
198 @lilypond[verbatim,quote,ragged-right]
200 { <\tonic \transpose c g \tonic> }
203 now works as expected. One can use @code{#@{@dots{}#@}} for
204 constructing chord constituents. @code{\tweak} now works on single
205 notes without needing to wrap them in a chord. Using it on command
206 events and lyrics is now possible, but not likely to give results yet.
209 @code{\tweak} now takes an optional layout object specification. It can
210 be used for tweaking layout objects that are only indirectly caused by
211 the tweaked event, like accidentals, stems, and flags:
213 @lilypond[verbatim,quote,ragged-right,relative=2]
214 <\tweak Accidental #'color #red cis4
215 \tweak Accidental #'color #green es
220 Scheme expressions inside of embedded Lilypond (@code{#@{@dots{}#@}})
221 are now executed in lexical closure of the surrounding Scheme code.
222 @code{$} is no longer special in embedded Lilypond. It can be used
223 unconditionally in Lilypond code for immediate evaluation of Scheme
224 expressions, similar to how @code{ly:export} could previously be used.
225 @code{ly:export} has been removed. As a consequence, @code{#} is now
226 free to delay evaluation of its argument until the parser actually
227 reduces the containing expression, greatly reducing the potential for
228 premature evaluation. There are also @q{splicing} operators @code{$@@}
229 and @code{#@@} for interpreting the members of a list individually.
232 Support for jazz-like chords has been improved: Lydian and altered
233 chords are recognised; separators between chord modifiers are now
234 treated independently of separators between ``slash'' chords and their
235 bass notes (and by default, slashes are now only used for the latter
236 type of separator); additional pitches are no longer prefixed with
237 ``add'' by default; and the ``m'' in minor chords can be customized.
238 @ruser{Customizing chord names} for more information.
241 The @code{\markuplines} command has been renamed to @code{\markuplist}
242 for a better match with its semantics and general Lilypond
246 The interface for specifying string tunings in tablature has been
247 simplified considerably and employs the scheme function
248 @code{\stringTuning} for most purposes.
251 Beams can now have their slopes preserved over line breaks.
252 @lilypond[fragment,quote,relative=2]
253 \override Beam #'breakable = ##t
254 a8[ b c d e f g \bar "" \break f e d c b a]
255 \once \override Beam #'positions = #beam::align-with-broken-parts
256 a8[ b c d e f g \bar "" \break f e d c b a]
257 \once \override Beam #'positions = #beam::slope-like-broken-parts
258 a8[ b c d e f g \bar "" \break f e d c b a]
260 To do this, several callback functions are now deprecated.
262 @item @code{ly:beam::calc-least-squares-positions}
263 @item @code{ly:beam::slope-damping}
264 @item @code{ly:beam::shift-region-to-valid}
266 Furthermore, @code{ly:beam::quanting} now takes an additional argument
267 to help calculations over line breaks. All of these functions are now
268 automatically called when setting the @code{positions} parameter.
271 In function arguments music, markups and Scheme expressions (as well as
272 several other syntactic entities) have become mostly interchangeable and
273 are told apart only by evaluating the respective predicate. In several
274 cases, the predicate is consulted by the parser, like when deciding
275 whether to interpret @code{-3} as a number or a fingering event.
278 Music functions (and their close relatives) can now be defined with
282 For defining commands executed only for their side-effects,
283 @code{define-void-function} is now available.
286 There is a new @code{define-event-function} command in analogy to
287 @code{define-music-function} that can be used for defining music
288 functions acting as post events without requiring a direction specifier
289 (@code{-}, @code{^}, or @code{_}) placed before them.
290 @lilypond[quote,verbatim,ragged-right]
291 dyn=#(define-event-function (parser location arg) (markup?)
292 (make-dynamic-script arg))
293 \relative c' { c\dyn pfsss }
297 A list of ASCII aliases for special characters can be included.
298 @lilypond[quote,verbatim]
300 #(include-special-characters)
302 \markup "• † ©right; &OE; &ss; ¶"
306 There is a new @code{define-scheme-function} command in analogy to
307 @code{define-music-function} that can be used to define functions
308 evaluating to Scheme expressions while accepting arguments in Lilypond
312 The construct @code{#@{ @dots{} #@}} can now be used not just for
313 constructing sequential music lists, but also for pitches (distinguished
314 from single note events by the absence of a duration or other
315 information that can't be part of a pitch), single music events, void
316 music expressions, post events, markups (mostly freeing users from
317 having to use the @code{markup} macro), markup lists, number
318 expressions, context definitions and modifications, and a few other
319 things. If it encloses nothing or only a single music event, it no
320 longer returns a sequential music list but rather a void music
321 expression or just the music event itself, respectively.
324 Pitches can be used on the right side of assignments. They are
325 distinguished from single note events by the absence of a duration or
326 other information that can't be part of a pitch.
329 New command-line option @option{--loglevel=@var{level}} to control how much output
330 LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG.
333 @code{\once \set} now correctly resets the property value to the previous value.
334 @lilypond[fragment,quote,relative=2]
335 \set fingeringOrientations = #'(left)
337 \once \set fingeringOrientations = #'(right)
343 The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now
344 automatically broken if a different direction is explicitly given.
345 @lilypond[fragment,quote,relative=2]
351 Appoggiaturas and acciaccaturas now also work inside a slur, not only inside
352 a phrasing slur. Also, a function @code{\slashedGrace} was added that does
353 not use a slur from the acciaccatura note.
354 @lilypond[fragment,quote,relative=2]
355 c4( \appoggiatura e8 d4 \acciaccatura e8 d4 \slashedGrace e8 c4)
360 To suppress the line on a crescendo text spanner (and other similar spanners),
361 LilyPond now fully supports the @code{#'style = #'none} property.
362 @lilypond[fragment,quote,relative=2]
363 \override DynamicTextSpanner #'style = #'none
368 LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz!
371 Glissandi can now span multiple lines.
376 For older news, go to
377 @uref{http://lilypond.org/doc/v2.14/Documentation/changes/},
378 @uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html},
379 or @uref{../,go back} to the Documentation index.