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
38 @node Top, Fixes and changes after 2.16.0, (dir), (dir)
39 @top New features in 2.16
42 * Fixes and changes after 2.16.0::
43 * New features in 2.16 since 2.14::
47 @allowcodebreaks false
49 @node Fixes and changes after 2.16.0, New features in 2.16 since 2.14, Top, Top
50 @section Fixes and changes after 2.16.0
53 Please refer to the bug tracker for
54 @uref{http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1,
55 issues fixed in 2.16.1}.
58 @node New features in 2.16 since 2.14, , Fixes and changes after 2.16.0, Top
59 @section New features in 2.16 since 2.14
66 * add new items at the top
68 * only show verbatim input for syntax/input changes
70 * try to be as brief possible in those cases
72 * don't try to provide real-world examples, they often get too big,
73 which scares away people.
75 * Write complete sentences.
77 * only show user-visible changes.
81 Support for cross-staff stems on chords, using @code{crossStaff}
82 and the @code{Span_stem_engraver}. This calculates the length of
83 cross-staff stems automatically.
85 {cross-staff-stems.ly}
88 The syntax of words (character sequences recognized without enclosing
89 quotes) and commands (now always a backslash @samp{\} followed by a
90 word) has been unified across all modes: it now consists of alphabetic
91 characters, possibly enclosing isolated dashes @samp{-} and underlines
94 As one consequence, using unquoted text scripts like (literally!)
96 @{ c-script c\f_script @}
98 will now tend to result in invalid music. Omitting quote marks
99 for arbitrary text rather than keywords has never been good practice or
100 even documented, and it is unlikely to have seen significant use.
102 Staying with established conventions (like not using dashes or
103 underlines for command names intended to be used inside of music)
104 remains advisable. The reason for this change is more robust
105 recognition of LilyPond's lexical units for LilyPond itself as well as
106 external tools interpreting its syntax.
109 Support for Kievan square notation:
110 @lilypond[quote,relative=1,verbatim]
119 Augmentation dots now avoid the other voice in two-voice polyphony
120 so that users can move the @code{Dot_column_engraver} to set dots
121 independently for each @code{Voice}.
126 \remove Dot_column_engraver
129 \consists Dot_column_engraver
134 <d f g>4. <d f g> <f, g> b
136 <f g b>4. <g b d> <b d> <e, g>
141 A Scheme function to adjust the control points of curves such as slurs
142 and ties, developed by several users, is now included in LilyPond.
143 @lilypond[quote,verbatim,relative=2]
145 \shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0))
150 Use of @code{\tempo} specifications in @code{\midi} blocks (removed in
151 2.9.16 in favor of explicit @code{tempoWholesPerMinute} settings) has
152 seen a revival: now any kind of property-setting music is turned into
153 context definitions within output specifications, allowing for
156 \layout @{ \accidentalStyle modern @}
157 \midi @{ \tempo 4. = 66 @}
161 The LilyPond G clef has been redesigned - upper loop is now more balanced,
162 bottom crook sticks out less and the "spine" (main vertical line) is more
163 evenly curved. The old and new versions can be compared by looking at the
165 @uref{http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs, old version},
166 @uref{http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs, new version}.
169 Lilypond's stencil commands have been simplified to allow for less code
170 duplication and better height approximations of graphical objects. The
171 following stencil commands have been eliminated:
174 @item @code{bezier-sandwich}
176 @item @code{dashed-slur}
179 @item @code{repeat-slash}
180 @item @code{zigzag-line}
184 Flags are now treated as separate objects rather than as stem parts.
185 @lilypond[fragment,quote,relative=2]
186 \override Flag #'color = #red
191 Two alternative methods for bar numbering can be set, especially for
192 when using repeated music;
194 @lilypond[fragment,quote,relative=1,noragged-right]
196 \set Score.alternativeNumberingStyle = #'numbers
197 \repeat volta 3 { c4 d e f | }
199 { c4 d e f | c2 d \break }
200 { f4 g a b | f4 g a b | f2 a | \break }
204 \set Score.alternativeNumberingStyle = #'numbers-with-letters
205 \repeat volta 3 { c,4 d e f | }
207 { c4 d e f | c2 d \break }
208 { f4 g a b | f4 g a b | f2 a | \break }
216 The following is a fundamental change in LilyPond's music
217 representation: Rhythmic events like @code{LyricEvent} and
218 @code{NoteEvent} are no longer wrapped in @code{EventChord} unless they
219 have been actually entered as part of a chord in the input. If you
220 manipulate music expressions in Scheme, the new behavior may require
221 changes in your code. Calling the music function @code{\eventChords} or
222 the Scheme function @code{event-chord-wrap!} converts to the old
223 representation; using one of those might be easiest for keeping legacy
226 The following three items are consequences of this change.
229 The repetitive chord entry aid @code{q} has been reimplemented.
230 Repeated chords are now replaced right before interpreting a music
231 expression. In case the user wants to retain some events of the
232 original chord, he can run the repeat chord replacement function
233 @code{\chordRepeats} manually.
236 String numbers and right hand fingerings on single notes now appear
237 without having to be written inside of chord brackets.
240 Music functions now work the same when used inside or outside of chords,
241 including all the possibilities of argument parsing. Music variables
242 can be used inside of chords: a construct like
243 @lilypond[verbatim,quote,ragged-right]
245 { <\tonic \transpose c g \tonic> }
248 now works as expected. One can use @code{#@{@dots{}#@}} for
249 constructing chord constituents. @code{\tweak} now works on single
250 notes without needing to wrap them in a chord. Using it on command
251 events and lyrics is now possible, but not likely to give results yet.
254 @code{\tweak} now takes an optional layout object specification. It can
255 be used for tweaking layout objects that are only indirectly caused by
256 the tweaked event, like accidentals, stems, and flags:
258 @lilypond[verbatim,quote,ragged-right,relative=2]
259 <\tweak Accidental #'color #red cis4
260 \tweak Accidental #'color #green es
265 Scheme expressions inside of embedded Lilypond (@code{#@{@dots{}#@}})
266 are now executed in lexical closure of the surrounding Scheme code.
267 @code{$} is no longer special in embedded Lilypond. It can be used
268 unconditionally in Lilypond code for immediate evaluation of Scheme
269 expressions, similar to how @code{ly:export} could previously be used.
270 @code{ly:export} has been removed. As a consequence, @code{#} is now
271 free to delay evaluation of its argument until the parser actually
272 reduces the containing expression, greatly reducing the potential for
273 premature evaluation. There are also @q{splicing} operators @code{$@@}
274 and @code{#@@} for interpreting the members of a list individually.
277 To reduce the necessity for using @code{$}, Scheme expressions written
278 with @code{#} are interpreted as music inside of music lists, and as
279 markups or markup lists inside of markups.
282 Support for jazz-like chords has been improved: Lydian and altered
283 chords are recognised; separators between chord modifiers are now
284 treated independently of separators between ``slash'' chords and their
285 bass notes (and by default, slashes are now only used for the latter
286 type of separator); additional pitches are no longer prefixed with
287 ``add'' by default; and the ``m'' in minor chords can be customized.
288 @ruser{Customizing chord names} for more information.
291 The @code{\markuplines} command has been renamed to @code{\markuplist}
292 for a better match with its semantics and general Lilypond
296 The interface for specifying string tunings in tablature has been
297 simplified considerably and employs the scheme function
298 @code{\stringTuning} for most purposes.
301 Beams can now have their slopes preserved over line breaks.
302 @lilypond[fragment,quote,relative=2]
303 \override Beam #'breakable = ##t
304 a8[ b c d e f g \bar "" \break f e d c b a]
305 \once \override Beam #'positions = #beam::align-with-broken-parts
306 a8[ b c d e f g \bar "" \break f e d c b a]
307 \once \override Beam #'positions = #beam::slope-like-broken-parts
308 a8[ b c d e f g \bar "" \break f e d c b a]
310 To do this, several callback functions are now deprecated.
312 @item @code{ly:beam::calc-least-squares-positions}
313 @item @code{ly:beam::slope-damping}
314 @item @code{ly:beam::shift-region-to-valid}
316 Furthermore, @code{ly:beam::quanting} now takes an additional argument
317 to help calculations over line breaks. All of these functions are now
318 automatically called when setting the @code{positions} parameter.
321 In function arguments music, markups and Scheme expressions (as well as
322 several other syntactic entities) have become mostly interchangeable and
323 are told apart only by evaluating the respective predicate. In several
324 cases, the predicate is consulted by the parser, like when deciding
325 whether to interpret @code{-3} as a number or a fingering event.
328 Music functions (and their close relatives) can now be defined with
332 For defining commands executed only for their side-effects,
333 @code{define-void-function} is now available.
336 There is a new @code{define-event-function} command in analogy to
337 @code{define-music-function} that can be used for defining music
338 functions acting as post events without requiring a direction specifier
339 (@code{-}, @code{^}, or @code{_}) placed before them.
340 @lilypond[quote,verbatim,ragged-right]
341 dyn=#(define-event-function (parser location arg) (markup?)
342 (make-dynamic-script arg))
343 \relative c' { c\dyn pfsss }
347 A list of ASCII aliases for special characters can be included.
348 @lilypond[quote,verbatim]
350 #(include-special-characters)
352 \markup "• † ©right; &OE; &ss; ¶"
356 There is a new @code{define-scheme-function} command in analogy to
357 @code{define-music-function} that can be used to define functions
358 evaluating to Scheme expressions while accepting arguments in Lilypond
362 The construct @code{#@{ @dots{} #@}} can now be used not just for
363 constructing sequential music lists, but also for pitches (distinguished
364 from single note events by the absence of a duration or other
365 information that can't be part of a pitch), single music events, void
366 music expressions, post events, markups (mostly freeing users from
367 having to use the @code{markup} macro), markup lists, number
368 expressions, context definitions and modifications, and a few other
369 things. If it encloses nothing or only a single music event, it no
370 longer returns a sequential music list but rather a void music
371 expression or just the music event itself, respectively.
374 Pitches can be used on the right side of assignments. They are
375 distinguished from single note events by the absence of a duration or
376 other information that can't be part of a pitch.
379 New command-line option @option{--loglevel=@var{level}} to control how much output
380 LilyPond creates. Possible values are ERROR, WARN, BASIC_PROGRESS, PROGRESS, DEBUG.
383 @code{\once \set} now correctly resets the property value to the previous value.
384 @lilypond[fragment,quote,relative=2]
385 \set fingeringOrientations = #'(left)
387 \once \set fingeringOrientations = #'(right)
393 The alignment of dynamic spanners (hairpins, text crescendo, etc.) is now
394 automatically broken if a different direction is explicitly given.
395 @lilypond[fragment,quote,relative=2]
401 Appoggiaturas and acciaccaturas now also work inside a slur, not only inside
402 a phrasing slur. Also, a function @code{\slashedGrace} was added that does
403 not use a slur from the acciaccatura note.
404 @lilypond[fragment,quote,relative=2]
405 c4( \appoggiatura e8 d4 \acciaccatura e8 d4 \slashedGrace e8 c4)
410 To suppress the line on a crescendo text spanner (and other similar spanners),
411 LilyPond now fully supports the @code{#'style = #'none} property.
412 @lilypond[fragment,quote,relative=2]
413 \override DynamicTextSpanner #'style = #'none
418 LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz!
421 Glissandi can now span multiple lines.
426 For older news, go to
427 @uref{http://lilypond.org/doc/v2.14/Documentation/changes/},
428 @uref{http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html},
429 or @uref{../,go back} to the Documentation index.