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.
65 Lilypond's stencil commands have been simplified to allow for less code
66 duplication and better height approximations of graphical objects. The
67 following stencil commands have been eliminated:
70 @item @code{bezier-sandwich}
72 @item @code{dashed-slur}
75 @item @code{repeat-slash}
76 @item @code{zigzag-line}
80 Flags are now treated as separate objects rather than as stem parts.
81 @lilypond[fragment,quote,relative=2]
82 \override Flag #'color = #red
87 Two alternative methods for bar numbering can be set, especially for
88 when using repeated music;
90 @lilypond[fragment,quote,relative=1,noragged-right]
92 \set Score.alternativeNumberingStyle = #'numbers
93 \repeat volta 3 { c4 d e f | }
95 { c4 d e f | c2 d \break }
96 { f4 g a b | f4 g a b | f2 a | \break }
100 \set Score.alternativeNumberingStyle = #'numbers-with-letters
101 \repeat volta 3 { c,4 d e f | }
103 { c4 d e f | c2 d \break }
104 { f4 g a b | f4 g a b | f2 a | \break }
112 The following is a fundamental change in LilyPond's music
113 representation: Rhythmic events like @code{LyricEvent} and
114 @code{NoteEvent} are no longer wrapped in @code{EventChord} unless they
115 have been actually entered as part of a chord in the input. If you
116 manipulate music expressions in Scheme, the new behavior may require
117 changes in your code. The advantages of making input and music match
118 more closely are numerous: music functions previously worked differently
119 when used inside or outside of chords. Now they are the same, including
120 all the possibilities of argument parsing. You can now use music
121 variables inside of chords: a construct like
122 @lilypond[verbatim,quote,ragged-right]
124 { <\tonic \transpose c g \tonic> }
127 would have been unthinkable previously. You can use
128 @code{#@{@dots{}#@}} for constructing chord constituents. Music
129 functions inside of chords are no longer specially treated and thus
130 accept the same arguments as outside of chords. @code{\tweak} now works
131 on single notes without needing to wrap them in a chord. In theory, it
132 can also work on command events and lyrics now. Since that was not
133 possible before, it depends on luck on a case-by-case basis whether the
134 tweak internals are already receiving the necessary information. Users
135 are asked to report those cases where they find @code{\tweak} not
136 working according to reasonable expectations.
139 As one consequence, it was possible to reimplement the repetitive chord
140 entry aid @code{q}. Repeated chords are now replaced right before
141 interpreting a music expression. In case the user wants to retain
142 some events of the original chord, he can run the repeat chord
143 replacement function @code{\chordRepeats} manually.
146 Scheme expressions inside of embedded Lilypond (@code{#@{@dots{}#@}})
147 are now executed in lexical closure of the surrounding Scheme code.
148 @code{$} is no longer special in embedded Lilypond. It can be used
149 unconditionally in Lilypond code for immediate evaluation, similar to
150 how @code{ly:export} could previously be used. @code{ly:export} has
151 been removed. As a consequence, @code{#} is now free to delay
152 evaluation of its argument until the parser actually reduces the
153 containing expression, greatly reducing the potential for premature
157 Support for jazz-like chords has been improved: Lydian and altered
158 chords are recognised; separators between chord modifiers are now
159 treated independently of separators between ``slash'' chords and their
160 bass notes (and by default, slashes are now only used for the latter
161 type of separator); additional pitches are no longer prefixed with
162 ``add'' by default; and the ``m'' in minor chords can be customized.
163 @ruser{Customizing chord names} for more information.
166 The @code{\markuplines} command has been renamed to @code{\markuplist}
167 for a better match with its semantics and general Lilypond
171 The interface for specifying string tunings in tablature has been
172 simplified considerably and employs the scheme function
173 @code{\stringTuning} for most purposes.
176 Beams can now have their slopes preserved over line breaks.
177 @lilypond[fragment,quote,relative=2]
178 \override Beam #'breakable = ##t
179 a8[ b c d e f g \bar "" \break f e d c b a]
180 \once \override Beam #'positions = #beam::align-with-broken-parts
181 a8[ b c d e f g \bar "" \break f e d c b a]
182 \once \override Beam #'positions = #beam::slope-like-broken-parts
183 a8[ b c d e f g \bar "" \break f e d c b a]
185 To do this, several callback functions are now deprecated.
187 @item @code{ly:beam::calc-least-squares-positions}
188 @item @code{ly:beam::slope-damping}
189 @item @code{ly:beam::shift-region-to-valid}
191 Furthermore, @code{ly:beam::quanting} now takes an additional argument
192 to help calculations over line breaks. All of these functions are now
193 automatically called when setting the @code{positions} parameter.
196 In function arguments music, markups and Scheme expressions (as well as
197 several other syntactic entities) have become mostly interchangeable and
198 are told apart only by evaluating the respective predicate. In several
199 cases, the predicate is consulted by the parser, like when deciding
200 whether to interpret @code{-3} as a number or a fingering event.
203 Music functions (and their close relatives) can now be defined with
207 For defining commands executed only for their side-effects,
208 @code{define-void-function} is now available.
211 There is a new @code{define-event-function} command in analogy to
212 @code{define-music-function} that can be used for defining music
213 functions acting as post events without requiring a direction specifier
214 (@code{-}, @code{^}, or @code{_}) placed before them.
215 @lilypond[quote,verbatim,ragged-right]
216 dyn=#(define-event-function (parser location arg) (markup?)
217 (make-dynamic-script arg))
218 \relative c' { c\dyn pfsss }
222 A list of ASCII aliases for special characters can be included.
223 @lilypond[quote,verbatim]
225 #(include-special-characters)
227 \markup "• † ©right; &OE; &ss; ¶"
231 There is a new @code{define-scheme-function} command in analogy to
232 @code{define-music-function} that can be used to define functions
233 evaluating to Scheme expressions while accepting arguments in Lilypond
237 The construct @code{#@{ @dots{} #@}} can now be used not just for
238 constructing sequential music lists, but also for pitches (distinguished
239 from single note events by the absence of a duration or other
240 information that can't be part of a pitch), single music events, void
241 music expressions, post events, markups (mostly freeing users from
242 having to use the @code{markup} macro), markup lists, number
243 expressions, context definitions and modifications, and a few other
244 things. If it encloses nothing or only a single music event, it no
245 longer returns a sequential music list but rather a void music
246 expression or just the music event itself, respectively.
249 Pitches can be used on the right side of assignments. They are
250 distinguished from single note events by the absence of a duration by
251 the absence of a duration or other information that can't be part of a
255 New command-line option @option{--loglevel=@var{level}} to control how much output
256 LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG.
259 @code{\once \set} now correctly resets the property value to the previous value.
260 @lilypond[fragment,quote,relative=2]
261 \set fingeringOrientations = #'(left)
263 \once \set fingeringOrientations = #'(right)
269 The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now
270 automatically broken if a different direction is explicitly given.
271 @lilypond[fragment,quote,relative=2]
277 Appoggiaturas and acciaccaturas now also work inside a slur, not only inside
278 a phrasing slur. Also, a function @code{\slashedGrace} was added that does
279 not use a slur from the acciaccatura note.
280 @lilypond[fragment,quote,relative=2]
281 c4( \appoggiatura e8 d4 \acciaccatura e8 d4 \slashedGrace e8 c4)
286 To suppress the line on a crescendo text spanner (and other similar spanners),
287 LilyPond now fully supports the @code{#'style = #'none} property.
288 @lilypond[fragment,quote,relative=2]
289 \override DynamicTextSpanner #'style = #'none
294 LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz!
297 Glissandi can now span multiple lines.
302 For older news, go to
303 @uref{http://lilypond.org/doc/v2.14/Documentation/changes/},
304 @uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html},
305 or @uref{../,go back} to the Documentation index.