1 \input texinfo @c -*-texinfo-*-
7 @unnumbered New features in 2.3 since 2.2
11 @item Support ambituses has been rewritten. The Ambitus object is now
12 a grouping object, composed of @code{AmbitusLine},
13 @code{AmbitusAccidental} and @code{AmbitusNoteHead}. These objects may
14 be tuned similar to accidentals and note heads.
16 @item Ledger lines are now shortened to prevent them from colliding.
18 @item Slur formatting has been rewritten. The new slur code
19 works similar to the Beam formatter: scores are assigned for all
20 esthetic components of a slur. A large number of combinations for
21 begin and end points is then tried out. Slurs will now also take into
22 account collisions with staff lines, scripts (like staccato and
23 accent) and accidentals.
26 @item In the LilyPond emacs mode, the @code{|} will now display the
27 current beat within the measure.
29 @item Colliding notes are now correctly aligned relative to notes in other staves.
31 @item An experimental GNOME output backend is available for developers.
32 It depends on several unreleased packages such as gnome-guile TLA and
33 Pango CVS. The output interface coverage is sparse, but it already
34 does support point-and-click on the GNOME Canvas. See also
35 @file{scm/output-gnome.scm}.
37 @item Context definitions are now stored in identifiers that match the
38 context name, in other words, to modify a @code{Staff} context, the
39 following code may be used.
48 @item A new block, @code{\bookpaper} has been introduced to
49 hold settings for paper size and output scaling. Further options
50 include @code{raggedbottom} (if set, systems are not vertically filled
51 to reach the bottom of the page), and @code{raggedlastbottom}.
55 @item Support for fret diagrams has been contributed by Carl
56 D. Sorensen. @file{input/test/fret-diagram.ly} contains an example.
58 @item The @code{--safe-mode} has been revisited: GUILE evaluation
59 is done in the R5RS safe module, with only the basic @code{ly:}
60 interface available and malicious @TeX{} code is stopped. However, to
61 be reasonably safe, you are advised to use the PostScript backend
62 rather than the @TeX{} backend anyway; and if possible use an UML
63 sandbox to run gs or latex.
65 @item Music syntax can now be extended seamlessly. As an example,
66 here is the new implementation @code{\applymusic},
69 applymusic = #(ly:make-music-function
70 (list procedure? ly:music?) ; signature
71 (lambda (where func music) ; the function
75 @item @code{\apply} has been renamed to @code{\applymusic}.
77 @item Music can be used as a markup.
78 When inserting a @code{score} block as part of a @code{\markup}, it
79 produces a rendered markup of the music. An example is in
80 @file{input/test/markup-score.ly}.
82 @item LilyPond expressions can be embedded into Scheme. The syntax for
83 this is @code{#@{ ... #@}}. Within such a block, Scheme forms can be
84 introduced using a @code{$} character (@code{$$} results in a single
85 `$' character). These forms are then inserted in the pattern.
88 #(define (textoffset dx dy)
90 #@{ \override Voice.TextScript #'extra-offset = #(cons $dx $dy) #@}))
94 %% The following embedded scheme call is the same as
95 %% \override Voice.TextScript #'extra-offset = #(cons 2 -3)
101 @item A music list at toplevel is interpreted as implicit @code{\score}
102 a @code{\score} block at toplevel is interpreted as an implicit
103 @code{\book} and @code{\notes} mode is the default lexer mode. The
107 \header @{ title = "The Title" @}
114 \header @{ title = "The Title" @}
122 This is handled by the function defined in
123 @code{toplevel-music-handler}. Similarly, @code{\score} and
124 @code{\book} are handled by @code{toplevel-score-handler} and a
125 @code{toplevel-book-handler}. By changing these variables, different
126 results can be obtained.
129 @item Start pitch for @code{relative} music is optional for music lists.
130 The default value is middle C.
132 @c update-me? formal definition of newaddlyrics, once it works
133 @item Combining lyrics with music can be done with @code{\newlyrics}
138 d2 d c4 bes a2 \break
141 My first Li -- ly song,
144 Not much can go wrong!
148 Syntactically, @code{\newlyrics} acts like an infix operator.
150 @item The parser is encapsulated in a Scheme function
151 @code{ly:parse-file}, so the following fragment processes two files
154 #(ly:parse-file "another.ly")
155 \score { \notes { c4 }}
158 @item The @code{font-encoding} property can now be used to select
159 differently encoded fonts. The previous default setting
160 @code{TeX-text} has been replaced by latin1. LilyPond requires the
161 @uref{http://www.lilypond.org/download/fonts/,ec-fonts-mftraced}
162 package installed to function properly.
164 @item The encoding of a file can be switched with
165 @code{\encoding}. The strings for markup texts are translated
168 @item The toplevel block @code{\book} introduces page layout.
169 A @code{\book} groups @code{\score} blocks into one page layout
170 entity. For example, two scores are combined in one book with
179 Titling and page breaks are handled by LilyPond. For automatic page
180 breaking, two algorithms are available, the classic ragged pages (the
181 default), and optimal page breaking.
182 Page breaks may be inserted manually with
188 The @code{lilypond} program does not generate La@TeX{} titles or page
189 layout. If you need La@TeX{} titles, you can use the
190 @code{lilypond-book} program.
192 @item There is now less of a noticeable ``hook'' at the end of a long slur.
194 @item The meaning of the @code{|} in the input can be redefined, by
195 assigning a music expression to @code{pipeSymbol}.
199 @unnumbered New features in 2.2 since 2.0
203 @item Setting @code{raggedlast = ##t} in the @code{\paper} block
204 causes the last line to be set flush-left instead of justified.
206 @item The @code{Timing_engraver} now sets the @code{Timing} alias on
207 its containing context automatically.
209 @item The code for font selection has been rewritten. In addition to
210 existing font selection properties, the property @code{font-encoding}
211 has been added, which makes the switch between normal @code{text} and
212 other encodings like @code{braces}, @code{music} and @code{math}.
214 @item The pmx2ly script has been removed from the distribution.
216 @item Pedal brackets will now run to the last bar of a piece if they are not
219 @item Context definitions now use the word @code{\context} instead of @code{\translator}.
221 @item Property functions may be used as an argument to @code{set!},
225 (set! (ly:grob-property grob 'beam) ... )
228 @item In anticipation of Emacs 21.4 or 22.1, the info documentation contains
231 @item Cue notes can be quoted directly from the parts that
232 contain them. This will take into account transposition of source and target
233 instrument. For example,
236 \addquote clarinet \notes\relative c' {
242 \notes \relative c'' {
243 c8 d8 \quote 2 oboe es8 gis
248 @item The transposition of an instrument can be specified using the
249 @code{\transposition} command. An
250 E-flat alto saxophone is specified as
256 @item The naming of exported Scheme functions now follows Scheme conventions.
257 Changes be applied to Scheme files with
260 convert-ly -e -n --from=2.1.24 --to=2.1.26 *.scm
264 @item Notes can be excluded from auto-beaming, by marking them with
271 will print two separate eighth notes, and two beamed notes.
273 @item Translators and contexts have been split. The result of this
274 internal cleanup is that @code{Score} no longer is the top context;
275 @code{Score} is contained in the @code{Global} context. Consequently,
276 it is possible to tweak @code{Score} as follows:
279 \context Score \with @{
284 @item The number of staff lines in Tablature notation is now
285 automatically deduced from the @code{stringTunings} property.
287 @item The program reference has been cleaned up and revised.
289 @item The syntax for setting properties has been simplified:
290 the following table lists the differences:
295 \property A.B = #C \set A.B = #C
296 \property A.B \unset \unset A.B
297 \property A.B \set #C = #D \override A.B #C = #D
298 \property A.B \override #C = #D (removed)
299 \property A.B \revert #C \revert A.B #C
302 Furthermore, if @code{A} is left out, the bottommost context is used
303 by default. In other words, it is no longer necessary to explicitly
304 mention @code{Voice}, @code{Lyrics} or @code{ChordNames}.
309 \property Voice.autoBeaming = ##f
310 \property Staff.TimeSignature \set #'style = #'C
316 \set autoBeaming = ##f
317 \override Staff.TimeSignature #'style = #'C
321 @item Tweaks made with @code{\override} and @code{\revert} no longer
322 hide tweaks at higher context levels.
324 @item Melismata in lyrics are also properly handled in the MIDI output.
326 @item The lilypond-book script has been rewritten.
327 It is shorter, cleaner and faster. The special construct
328 @code{mbinclude} has been removed, plain @code{@@include} or
329 @code{\input} can be used now.
331 It now supports running convert-ly on the lilypond snippets,
333 lilypond-book --filter='convert-ly --from=2.0.0' my-book.tely
336 @item The @code{LyricsVoice} context has been removed. Lyrics should only
337 be constructed in @code{Lyrics}.
339 @item The @code{Thread} context has been removed. Note heads and rests
340 are now constructed at @code{Voice} level.
342 @item Harmonic notes can now be entered as
348 @item Drum notation is now supported as a regular feature:
349 percussion may be entered in @code{\drums} mode, and printed or
350 performed in a @code{DrumStaff} context:
354 \drums \new DrumStaff @{ hihat4 cowbell8 @}
358 @item The automatic staff changer was internally rewritten. As a
359 result, the syntax has been simplified as well:
362 \autochange @var{the-music}
365 @item The ergonomic syntax of @code{\markup} now has an equivalent in
366 Scheme. The @code{markup*} macro creates such objects; the following
367 two markup commands are equivalent:
369 f4^#(markup* #:raise 0.2 #:bold "hi")
370 f4^\markup @{ \raise #0.2 \bold hi @}
373 @item Voice names, for vocal lines, have been added. They are similar
374 to instrument names. They can be set by defining @code{vocalName}
377 @item Safe mode has been reinstated for lilypond.
378 When lilypond is invoked with @code{--safe-mode}, @TeX{} and
379 PostScript file output is disallowed, and lilypond-bin is invoked with
380 @code{--safe-mode}, the user's Guile expressions are evaluated in a
381 safe environment and file inclusion is not allowed.
383 Warning: this does not protect against denial-of-service attacks using
384 Guile, @TeX{} or PostScript.
386 (This feature is still experimental.)
388 @item There is now a Scheme macro for defining markup
389 commands. Special mark-up commands can be defined in user-files too.
391 @item Many fixes for dimension scaling have been made,
392 resulting in correct results for scores that mix staves in different
395 @item Improved robustness when layout properties are accidentally removed.
397 @item A more cleanly constructed part combiner has been installed.
398 It is more robust and less buggy. The part-combiner can be used with
400 \partcombine @var{mus1} @var{mus2}
404 See @file{input/regression/new-part-combine.ly} for an example.
406 @item Formatting of rehearsal marks has been improved. The @code{\mark}
407 command now only does automatic incrementing for marks specified as
408 integer. For example, @code{\mark #1} will print an A in the default
409 style. See @file{input/regression/rehearsal-mark-letter.ly},
410 @file{input/regression/rehearsal-mark-number.ly}.
412 @item Formatting of ottava brackets has been much improved.
414 @item Objects in the output can now be documented: the following fragment
415 boxes the note head, and adds the text ``heads or tails?'' three
416 spaces below the box.
419 \context Voice \applyoutput #(add-balloon-text
420 'NoteHead "heads, or tails?"
428 @item Default staff sizes are now scalable. There are two new mechanisms for
429 setting staff sizes. Both are demonstrated in this fragment:
432 #(set-global-staff-size 15)
434 #(paper-set-staff-size (* 15 pt))
440 Both have the same effect on the global layout of a piece. Similarly,
441 the paper size may be changed as follows
444 #(set-default-paper-size "a4")
446 #(set-paper-size "a4")
451 @item Warnings for bar check errors are more cleverly printed. This
452 makes @code{barCheckSynchronize} superfluous, so it is now switched
455 Warning: this will cause problems in scores that use bar checks to
458 @item The black note head was made a little rounder, which causes a less
459 frantic graphic impression.
462 A more concise syntax for checking octaves was introduced. A note may
463 be followed by @code{=}@var{quotes} which indicates what its absolute
464 octave should be. In the following example,
467 \relative c'' @{ c='' b=' d,='' @}
471 the d will generate a warning, because a d'' is
472 expected, but a d' is found.
473 @c @code adds ` ', very confusing.
475 @item There is a new mechanism for putting lyrics to melodies.
476 With this mechanism, @code{Lyrics} lines can be put melodies
477 individually, allowing for different melismatic sections in every
478 @code{Lyrics}. See @file{input/regression/lyric-combine-new.ly}.
480 @item Bar lines may now be dotted.
483 @item The documentation now has links to a wiki, where everyone can
484 add personal comments to the manual.
486 @item Contexts may now be changed locally for an isolated music
487 expression. For example,
491 \consists "Pitch_squash_engraver"
497 @item The syntax for changing staffs has changed. The keyword
498 @code{\change} should now be used, e.g.
504 @item Features of spanner contexts, like @code{Staff}, can now be changed
505 using @code{\set}, eg.
509 \override Staff.StaffSymbol #'line-count = #4
515 puts a quarter note C on a staff with 4 lines.
518 @item Multi measure rests are now truly centered between the
519 clefs/barlines of the staff, their position is independent of symbols
522 @item Collision resolution for dots in chords has been improved greatly.
525 Spacing following barlines was improved for widely stretched lines.
528 Lyric hyphens and extenders now conform to standard typesetting
532 Lyrics are now aligned under note heads conforming to engraving
533 standards. The responsible code has been rewritten, and is drastically
534 simpler from the previous version. To aid this rewrite, the syntactic
535 function of the extender line ( __ ) has been changed: it is now
536 attached to the lyric syllable.
539 When redefining a context, the associated identifier is also
540 updated. For example, after reading
550 the definition of @code{ScoreContext} is updated to include the changed
555 The weight of the stafflines is now heavier at smaller staff sizes.
556 The font has been modified to match this look: at smaller sizes, the
557 font is heavier and the note heads are more rounded.
559 @item Processing scores is now done while parsing the file. New
560 Scheme functions give more flexibility: for example, it is now possible
561 interpret a score, collecting synchronized musical events in a list, and
562 manipulate that information using inline Scheme. For an example, see
563 @file{input/no-notation/recording.ly}.
565 @item Font sizes can now truly be scaled continuously: the @code{font-size}
566 is similar to the old @code{font-relative-size}, but may be set to
567 fractional values; the closest design size will be scaled to achieve
568 the desired size. As a side-effect, there are now no longer
569 limitations in using smaller fonts (eg. grace notes) at small staff
572 @item Stem tips are now also engraved with rounded corners.
575 The placement of accidentals on chords and ledgered notes is improved.
580 @unnumbered New features in 2.0 since 1.8
585 Crescendos can now be drawn dotted or dashed.
588 Quarter tones are now supported. They are entered by suffixing
589 @code{ih} for a half-sharp and @code{eh} for a half-flat. Hence, the
590 following is an ascending list of pitches:
593 ceses ceseh ces ceh c cih cis cisih cisis
597 The following constructs have been removed from the syntax:
600 \duration #SCHEME-DURATION
602 \outputproperty @var{func} @var{symbol} = @var{value}
605 For @code{\outputproperty}, the following may be substituted:
608 \applyoutput #(outputproperty-compatibility @var{func}
609 @var{symbol} @var{value})
613 Clefs may now be transposed arbitrarily, for example
623 The syntax for chords and simultaneous music have changed.
624 Chords are entered as
630 while simultaneous music is entered as
633 <<@var{..music list..}>>
636 In effect, the meanings of both have been swapped relative to their 1.8
637 definition. The syntax for lists in @code{\markup} has changed
638 alongside, but figured bass mode was not changed, i.e.:
641 \markup @{ \center <@var{..list of markups..}> @}
642 \figure @{ <@var{figures}> @}
645 As chords the more often used than simultaneous music, this change will
649 Each music expression can now be tagged, to make different printed
650 versions from the same music expression. In the following example,
651 we see two versions of a piece of music, one for the full score, and
652 one with cue notes for the instrumental part:
656 @{ c4 f2 g4 @} % in the part, we have cue-notes
658 \tag #'score R1 % in the score: only a rest
662 The same can be applied to articulations, texts, etc.: they are
666 -\tag #@var{your-tags}
669 to an articulation, for example,
672 c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
675 This defines a note, which has a conditional fingering and a
676 string-number indication.
679 The settings for chord-fingering are more flexible. You can specify a
680 list where fingerings may be placed, eg.
683 \property Voice.fingeringOrientations = #'(left down)
686 This will put the fingering for the lowest note below the chord, and the
690 The script previously known as @code{ly2dvi} has been renamed to
691 @code{lilypond}. The binary itself is now installed as
695 Markup text (ie. general text formatting) may now be used for lyrics too.
698 Two new commands for grace notes have been added, @code{\acciaccatura}
699 and @code{\appoggiatura},
706 Both reflect the traditional meanings of acciaccatura and appogiatura,
707 and both insert insert a slur from the first grace note to the main
711 Layout options for grace notes are now stored in a context property,
712 and may now be set separately from musical content.
715 The @code{\new} command will create a context with a unique
716 name automatically. Hence, for multi-staff scores, it is no longer
717 necessary to invent arbitrary context names. For example, a two-staff
718 score may be created by
722 \new Staff @{ @var{notes for 1st staff} @}
723 \new Staff @{ @var{notes for 2nd staff} @}
730 Octave checks make octave errors easier to correct.
737 This checks that @var{pitch} (without octave) yields @var{pitch} (with
738 octave) in \relative mode. If not, a warning is printed, and the
742 All articulations must now be entered postfix. For example,
749 is a pair of beamed slurred eighth notes.
752 The definition of @code{\relative} has been simplified. Octaves are
753 now always propagated in the order that music is entered. In the
758 \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 @}
763 the octave of BODY is based on PRE, the starting octave of ALT1 on
764 BODY, the starting octave of ALT2 on ALT1, and the starting octave of
767 The same mechanism is used for all other music expressions, except the
768 chord. Backwards compatibility is retained through a special program option,
772 #(ly:set-option 'old-relative)
776 Windows users can double click a @code{.ly} file to process and view
777 it automagically through the new @code{lily-wins} frontend.
784 @unnumbered New features in 1.8 since 1.6
789 The chord entry code has been completely rewritten. It is now
790 cleaner and more flexible.
793 A new syntax has been added for text entry. This syntax is more
794 friendly than the old mechanism, and it is implemented in a more
795 robust and modular way. For more information, refer to the section on
796 "Text markup" in the notation manual.
799 The integration of the input language and Scheme has been made deeper:
800 you can now use LilyPond identifiers in Scheme, and use Scheme
801 expressions instead of LilyPond identifiers.
804 The internal representation of music has been cleaned up completely
805 and converted to Scheme data structures. The representation may be
809 A new uniform postfix syntax for articulation has been introduced.
810 A beamed slurred pair of eighth notes can be entered as
816 In version 2.0, postfix syntax will be the only syntax
817 available, and the dashes will become optional.
819 This will simplify the language: all articulations can be entered as
820 postfix, in any order.
823 A new syntax has been added for chords:
830 It is not necessary to update files to this syntax, but it will be for
831 using LilyPond version 2.0. In version 2.0, this syntax will be
841 \simultaneous @{ .. @}
844 for simultaneous music.
846 To convert your files from <PITCHES> to <<PITCHES>>, use the script
847 included in @file{buildscripts/convert-new-chords.py}.
849 This change was introduced for the following reasons
853 It solves the "start score with chord" problem, where you have to
854 state \context Voice explicitly when a chord was the start of a
857 With the new syntax, it is possible to distinguish between
858 articulations (or fingerings) which are for a single chord note,
859 and which are for the entire chord. This allows for per-note
860 fingerings, and is more logical on the whole.
864 User code may now be executed during interpreting. The syntax for
868 \applycontext #SCHEME-FUNCTION
872 User code may now be executed on arbitrary grobs during interpreting.
873 The syntax for this feature is
876 \applyoutput #SCHEME-FUNCTION
880 SCHEME-FUNCTION takes a single argument, and is called for every grob
881 that is created in the current context.
884 New algorithms for chord-name formatting have been installed. They
885 can be tuned and have ergonomic syntax for entering exceptions.
888 Texts may now be put on multimeasure rests, e.g.
891 R1*20^\markup @{ "GP" @}
895 Ancient notation now prints ligatures in Gregorian square neumes
896 notation, roughly following the typographical style of the Liber
897 hymnarius of Solesmes, published in 1983. Ligatures are still printed
898 without the proper line breaking and horizontal spacing.
901 Glissandi can now be printed using the zigzag style.
904 LilyPond can now print clusters. The syntax is
907 \apply #notes-to-clusters @{ NOTE NOTE .. @}
911 For irregular meters, beat grouping marks can be printed. The
915 #(set-time-signature 7 8 '(3 2 2))
920 Nested horizontal brackets for music analysis can now be printed:
929 @item Ottava brackets are now fully supported as a feature. The syntax
937 @item Metronome markings are printed when a \tempo command is processed.
941 @item Fingerings can be put on chords horizontally.
945 @item The appearance of various glyphs has been fine-tuned.
949 @item Different types of percent style repeats may now be nested.
953 @item The emacs support has been extended.
957 The manual has been completely revised and extended.
961 @unnumbered New features in 1.6 since 1.4
967 Support for figured bass and tablature.
970 Completely rewritten beam formatting: provides much better output
975 Completely revised and improved music font.
979 Completely rewritten MIDI import support.
982 Completely rewritten grace note support. Practically speaking this
983 means that grace notes can be slurred to normal normal notes.
987 Improved accidental handling and formatting: styles for producing
988 cautionaries may vary, and complex collisions between accidentals of a
989 chord are handled much better.
992 Better spacing: both globally and locally. This includes subtle
993 details like optical stem spacing.
996 More support for ancient notation: mensural ligatures, ambitus
997 (pitch range) of voices, more shapes, etc.
1000 More support for piano notation: bracket pedals, directed arpeggios,
1004 Easier music polyphonic music entry.
1007 More extensibility, many speedups and bugfixes
1010 The manual has been thoroughly revised.
1013 Development is now hosted at http://savannah.gnu.org, and sources
1014 can be downloaded through anonymous CVS.
1017 Support for windows: LilyPond is part of the cygwin distribution,
1018 which comes with a user-friendly installer.