1 \input texinfo @c -*-texinfo-*-
7 @unnumbered New features in 2.3 since 2.2
10 @item The @code{--safe} mode has been revisited: it makes the basic
11 ly: interface available, and stops malicious @TeX{} code.
13 @item Music syntax can now be extended seamlessly. As an example,
14 here is the new implementation @code{\applymusic},
17 applymusic = #(ly:make-music-function
18 (list procedure? ly:music?) ; signature
19 (lambda (where func music) ; the function
23 @item @code{\apply} has been renamed to @code{\applymusic}.
25 @item Music can be used as a markup.
26 When inserting a @code{score} block as part of a @code{\markup},
27 it produces a rendered markup of the music.
30 @c TODO, see input/test/markup-score.ly
34 @item LilyPond expressions can be embedded into Scheme. The syntax for
35 this is @code{#@{ ... #@}}. Within such a block, Scheme forms can be
36 introduced using a @code{$} character (@code{$$} results in a single
37 `$' character). These forms are then printed in the pattern.
40 #(define (textoffset dx dy)
42 #@{ \override Voice.TextScript #'extra-offset = #(cons $dx $dy) #@}))
47 %% the following statement is the same as
48 %% \override Voice.TextScript #'extra-offset = #(cons 2 -3)
55 @item Music lists are allowed at toplevel.
58 \header @{ title = "The Title" @}
65 \header @{ title = "The Title" @}
73 These toplevel forms are handled by
74 @code{default-toplevel-music-handler}. Similarly, a @code{score}
75 block at toplevel is handled by @code{default-toplevel-score-handler}
76 and a @code{book} at toplevel is handled by
77 @code{default-toplevel-book-handler}.
82 These default handlers have the following effect. A Music list at
83 toplevel is encapsulated in a @code{score} block, and a @code{score}
84 block at toplevel is encapsulated in a @code{book} block. A
85 @code{book} block at toplevel generates printed output.
89 @item Start pitch for @code{relative} music is optional for music lists.
90 The default value is one octave below middle C.
92 @c update-me? formal definition of newaddlyrics, once it works
93 @item Combining lyrics with music can be @code{\newlyrics}
102 My first Li -- ly song,
105 Not much can go wrong!
110 Syntactically, @code{\newlyrics} acts like an infix operator.
112 @item The parser is encapsulated in a Scheme function
113 @code{ly:parse-file}, so the following fragment processes two files
116 #(ly:parse-file "another.ly")
117 \score { \notes { c4 }}
120 @item The @code{font-encoding} property can now be used to select
121 differently encoded fonts. The previous default setting
122 @code{TeX-text} has been replaced by latin1. LilyPond requires the
123 @uref{http://www.lilypond.org/download/fonts/,ec-fonts-mftraced}
124 package installed to function properly.
126 @item The encoding of a file can be switched with
127 @code{\encoding}. The strings for markup texts are translated
130 @item The toplevel block @code{book} introduces page layout.
131 A @code{book} groups @code{score} blocks into one page layout entity.
132 Page layout consists of markup titles, headers and footers, and page
133 breaking. Two page breaking algorithms are available, the classic
134 ragged pages (the default), and optimal page breaking
138 %% Select page breaking function.
139 %% #(define page-breaking ly:ragged-page-breaks)
140 #(define page-breaking ly:optimal-page-breaks)
148 The @code{lilypond} program does not generate La@TeX{} titles or page
149 layout. If you need La@TeX{} titles, you can use the
150 @code{lilypond-book} program.
152 @item There is now less of a noticeable ``hook'' at the end of a long slur.
154 @item The meaning of the @code{|} in the input can be redefined, by
155 assigning a music expression to @code{pipeSymbol}.
159 @unnumbered New features in 2.2 since 2.0
163 @item Setting @code{raggedlast = ##t} in the @code{\paper} block
164 causes the last line to be set flush-left instead of justified.
166 @item The @code{Timing_engraver} now sets the @code{Timing} alias on
167 its containing context automatically.
169 @item The code for font selection has been rewritten. In addition to
170 existing font selection properties, the property @code{font-encoding}
171 has been added, which makes the switch between normal @code{text} and
172 other encodings like @code{braces}, @code{music} and @code{math}.
174 @item The pmx2ly script has been removed from the distribution.
176 @item Pedal brackets will now run to the last bar of a piece if they are not
179 @item Context definitions now use the word @code{\context} instead of @code{\translator}.
181 @item Property functions may be used as an argument to @code{set!},
185 (set! (ly:grob-property grob 'beam) ... )
188 @item In anticipation of Emacs 21.4 or 22.1, the info documentation contains
191 @item Cue notes can be quoted directly from the parts that
192 contain them. This will take into account transposition of source and target
193 instrument. For example,
196 \addquote clarinet \notes\relative c' {
202 \notes \relative c'' {
203 c8 d8 \quote 2 oboe es8 gis
208 @item The transposition of an instrument can be specified using the
209 @code{\transposition} command. An
210 E-flat alto saxophone is specified as
216 @item The naming of exported Scheme functions now follows Scheme conventions.
217 Changes be applied to Scheme files with
220 convert-ly -e -n --from=2.1.24 --to=2.1.26 *.scm
224 @item Notes can be excluded from auto-beaming, by marking them with
231 will print two separate eighth notes, and two beamed notes.
233 @item Translators and contexts have been split. The result of this
234 internal cleanup is that @code{Score} no longer is the top context;
235 @code{Score} is contained in the @code{Global} context. Consequently,
236 it is possible to tweak @code{Score} as follows:
239 \context Score \with @{
244 @item The number of staff lines in Tablature notation is now
245 automatically deduced from the @code{stringTunings} property.
247 @item The program reference has been cleaned up and revised.
249 @item The syntax for setting properties has been simplified:
250 the following table lists the differences:
255 \property A.B = #C \set A.B = #C
256 \property A.B \unset \unset A.B
257 \property A.B \set #C = #D \override A.B #C = #D
258 \property A.B \override #C = #D (removed)
259 \property A.B \revert #C \revert A.B #C
262 Furthermore, if @code{A} is left out, the bottommost context is used
263 by default. In other words, it is no longer necessary to explicitly
264 mention @code{Voice}, @code{Lyrics} or @code{ChordNames}.
269 \property Voice.autoBeaming = ##f
270 \property Staff.TimeSignature \set #'style = #'C
276 \set autoBeaming = ##f
277 \override Staff.TimeSignature #'style = #'C
281 @item Tweaks made with @code{\override} and @code{\revert} no longer
282 hide tweaks at higher context levels.
284 @item Melismata in lyrics are also properly handled in the MIDI output.
286 @item The lilypond-book script has been rewritten.
287 It is shorter, cleaner and faster. The special construct
288 @code{mbinclude} has been removed, plain @code{@@include} or
289 @code{\input} can be used now.
291 It now supports running convert-ly on the lilypond snippets,
293 lilypond-book --filter='convert-ly --from=2.0.0' my-book.tely
296 @item The @code{LyricsVoice} context has been removed. Lyrics should only
297 be constructed in @code{Lyrics}.
299 @item The @code{Thread} context has been removed. Note heads and rests
300 are now constructed at @code{Voice} level.
302 @item Harmonic notes can now be entered as
308 @item Drum notation is now supported as a regular feature:
309 percussion may be entered in @code{\drums} mode, and printed or
310 performed in a @code{DrumStaff} context:
314 \drums \new DrumStaff @{ hihat4 cowbell8 @}
318 @item The automatic staff changer was internally rewritten. As a
319 result, the syntax has been simplified as well:
322 \autochange @var{the-music}
325 @item The ergonomic syntax of @code{\markup} now has an equivalent in
326 Scheme. The @code{markup*} macro creates such objects; the following
327 two markup commands are equivalent:
329 f4^#(markup* #:raise 0.2 #:bold "hi")
330 f4^\markup @{ \raise #0.2 \bold hi @}
333 @item Voice names, for vocal lines, have been added. They are similar
334 to instrument names. They can be set by defining @code{vocalName}
337 @item Safe mode has been reinstated for lilypond.
338 When lilypond is invoked with @code{--safe-mode}, @TeX{} and
339 PostScript file output is disallowed, and lilypond-bin is invoked with
340 @code{--safe-mode}, the user's Guile expressions are evaluated in a
341 safe environment and file inclusion is not allowed.
343 Warning: this does not protect against denial-of-service attacks using
344 Guile, @TeX{} or PostScript.
346 (This feature is still experimental.)
348 @item There is now a Scheme macro for defining markup
349 commands. Special mark-up commands can be defined in user-files too.
351 @item Many fixes for dimension scaling have been made,
352 resulting in correct results for scores that mix staves in different
355 @item Improved robustness when layout properties are accidentally removed.
357 @item A more cleanly constructed part combiner has been installed.
358 It is more robust and less buggy. The part-combiner can be used with
360 \partcombine @var{mus1} @var{mus2}
364 See @file{input/regression/new-part-combine.ly} for an example.
366 @item Formatting of rehearsal marks has been improved. The @code{\mark}
367 command now only does automatic incrementing for marks specified as
368 integer. For example, @code{\mark #1} will print an A in the default
369 style. See @file{input/regression/rehearsal-mark-letter.ly},
370 @file{input/regression/rehearsal-mark-number.ly}.
372 @item Formatting of ottava brackets has been much improved.
374 @item Objects in the output can now be documented: the following fragment
375 boxes the note head, and adds the text ``heads or tails?'' three
376 spaces below the box.
379 \context Voice \applyoutput #(add-balloon-text
380 'NoteHead "heads, or tails?"
388 @item Default staff sizes are now scalable. There are two new mechanisms for
389 setting staff sizes. Both are demonstrated in this fragment:
392 #(set-global-staff-size 15)
394 #(paper-set-staff-size (* 15 pt))
400 Both have the same effect on the global layout of a piece. Similarly,
401 the paper size may be changed as follows
404 #(set-default-paper-size "a4")
406 #(set-paper-size "a4")
411 @item Warnings for bar check errors are more cleverly printed. This
412 makes @code{barCheckSynchronize} superfluous, so it is now switched
415 Warning: this will cause problems in scores that use bar checks to
418 @item The black note head was made a little rounder, which causes a less
419 frantic graphic impression.
422 A more concise syntax for checking octaves was introduced. A note may
423 be followed by @code{=}@var{quotes} which indicates what its absolute
424 octave should be. In the following example,
427 \relative c'' @{ c='' b=' d,='' @}
431 the d will generate a warning, because a d'' is
432 expected, but a d' is found.
433 @c @code adds ` ', very confusing.
435 @item There is a new mechanism for putting lyrics to melodies.
436 With this mechanism, @code{Lyrics} lines can be put melodies
437 individually, allowing for different melismatic sections in every
438 @code{Lyrics}. See @file{input/regression/lyric-combine-new.ly}.
440 @item Bar lines may now be dotted.
443 @item The documentation now has links to a wiki, where everyone can
444 add personal comments to the manual.
446 @item Contexts may now be changed locally for an isolated music
447 expression. For example,
451 \consists "Pitch_squash_engraver"
457 @item The syntax for changing staffs has changed. The keyword
458 @code{\change} should now be used, e.g.
464 @item Features of spanner contexts, like @code{Staff}, can now be changed
465 using @code{\set}, eg.
469 \override Staff.StaffSymbol #'line-count = #4
475 puts a quarter note C on a staff with 4 lines.
478 @item Multi measure rests are now truly centered between the
479 clefs/barlines of the staff, their position is independent of symbols
482 @item Collision resolution for dots in chords has been improved greatly.
485 Spacing following barlines was improved for widely stretched lines.
488 Lyric hyphens and extenders now conform to standard typesetting
492 Lyrics are now aligned under note heads conforming to engraving
493 standards. The responsible code has been rewritten, and is drastically
494 simpler from the previous version. To aid this rewrite, the syntactic
495 function of the extender line ( __ ) has been changed: it is now
496 attached to the lyric syllable.
499 When redefining a context, the associated identifier is also
500 updated. For example, after reading
510 the definition of @code{ScoreContext} is updated to include the changed
515 The weight of the stafflines is now heavier at smaller staff sizes.
516 The font has been modified to match this look: at smaller sizes, the
517 font is heavier and the note heads are more rounded.
519 @item Processing scores is now done while parsing the file. New
520 Scheme functions give more flexibility: for example, it is now possible
521 interpret a score, collecting synchronized musical events in a list, and
522 manipulate that information using inline Scheme. For an example, see
523 @file{input/no-notation/recording.ly}.
525 @item Font sizes can now truly be scaled continuously: the @code{font-size}
526 is similar to the old @code{font-relative-size}, but may be set to
527 fractional values; the closest design size will be scaled to achieve
528 the desired size. As a side-effect, there are now no longer
529 limitations in using smaller fonts (eg. grace notes) at small staff
532 @item Stem tips are now also engraved with rounded corners.
535 The placement of accidentals on chords and ledgered notes is improved.
540 @unnumbered New features in 2.0 since 1.8
545 Crescendos can now be drawn dotted or dashed.
548 Quarter tones are now supported. They are entered by suffixing
549 @code{ih} for a half-sharp and @code{eh} for a half-flat. Hence, the
550 following is an ascending list of pitches:
553 ceses ceseh ces ceh c cih cis cisih cisis
557 The following constructs have been removed from the syntax:
560 \duration #SCHEME-DURATION
562 \outputproperty @var{func} @var{symbol} = @var{value}
565 For @code{\outputproperty}, the following may be substituted:
568 \applyoutput #(outputproperty-compatibility @var{func}
569 @var{symbol} @var{value})
573 Clefs may now be transposed arbitrarily, for example
583 The syntax for chords and simultaneous music have changed.
584 Chords are entered as
590 while simultaneous music is entered as
593 <<@var{..music list..}>>
596 In effect, the meanings of both have been swapped relative to their 1.8
597 definition. The syntax for lists in @code{\markup} has changed
598 alongside, but figured bass mode was not changed, i.e.:
601 \markup @{ \center <@var{..list of markups..}> @}
602 \figure @{ <@var{figures}> @}
605 As chords the more often used than simultaneous music, this change will
609 Each music expression can now be tagged, to make different printed
610 versions from the same music expression. In the following example,
611 we see two versions of a piece of music, one for the full score, and
612 one with cue notes for the instrumental part:
616 @{ c4 f2 g4 @} % in the part, we have cue-notes
618 \tag #'score R1 % in the score: only a rest
622 The same can be applied to articulations, texts, etc.: they are
626 -\tag #@var{your-tags}
629 to an articulation, for example,
632 c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
635 This defines a note, which has a conditional fingering and a
636 string-number indication.
639 The settings for chord-fingering are more flexible. You can specify a
640 list where fingerings may be placed, eg.
643 \property Voice.fingeringOrientations = #'(left down)
646 This will put the fingering for the lowest note below the chord, and the
650 The script previously known as @code{ly2dvi} has been renamed to
651 @code{lilypond}. The binary itself is now installed as
655 Markup text (ie. general text formatting) may now be used for lyrics too.
658 Two new commands for grace notes have been added, @code{\acciaccatura}
659 and @code{\appoggiatura},
666 Both reflect the traditional meanings of acciaccatura and appogiatura,
667 and both insert insert a slur from the first grace note to the main
671 Layout options for grace notes are now stored in a context property,
672 and may now be set separately from musical content.
675 The @code{\new} command will create a context with a unique
676 name automatically. Hence, for multi-staff scores, it is no longer
677 necessary to invent arbitrary context names. For example, a two-staff
678 score may be created by
682 \new Staff @{ @var{notes for 1st staff} @}
683 \new Staff @{ @var{notes for 2nd staff} @}
690 Octave checks make octave errors easier to correct.
697 This checks that @var{pitch} (without octave) yields @var{pitch} (with
698 octave) in \relative mode. If not, a warning is printed, and the
702 All articulations must now be entered postfix. For example,
709 is a pair of beamed slurred eighth notes.
712 The definition of @code{\relative} has been simplified. Octaves are
713 now always propagated in the order that music is entered. In the
718 \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 @}
723 the octave of BODY is based on PRE, the starting octave of ALT1 on
724 BODY, the starting octave of ALT2 on ALT1, and the starting octave of
727 The same mechanism is used for all other music expressions, except the
728 chord. Backwards compatibility is retained through a special program option,
732 #(ly:set-option 'old-relative)
736 Windows users can double click a @code{.ly} file to process and view
737 it automagically through the new @code{lily-wins} frontend.
744 @unnumbered New features in 1.8 since 1.6
749 The chord entry code has been completely rewritten. It is now
750 cleaner and more flexible.
753 A new syntax has been added for text entry. This syntax is more
754 friendly than the old mechanism, and it is implemented in a more
755 robust and modular way. For more information, refer to the section on
756 "Text markup" in the notation manual.
759 The integration of the input language and Scheme has been made deeper:
760 you can now use LilyPond identifiers in Scheme, and use Scheme
761 expressions instead of LilyPond identifiers.
764 The internal representation of music has been cleaned up completely
765 and converted to Scheme data structures. The representation may be
769 A new uniform postfix syntax for articulation has been introduced.
770 A beamed slurred pair of eighth notes can be entered as
776 In version 2.0, postfix syntax will be the only syntax
777 available, and the dashes will become optional.
779 This will simplify the language: all articulations can be entered as
780 postfix, in any order.
783 A new syntax has been added for chords:
790 It is not necessary to update files to this syntax, but it will be for
791 using LilyPond version 2.0. In version 2.0, this syntax will be
801 \simultaneous @{ .. @}
804 for simultaneous music.
806 To convert your files from <PITCHES> to <<PITCHES>>, use the script
807 included in buildscripts/convert-new-chords.py
809 This change was introduced for the following reasons
813 It solves the "start score with chord" problem, where you have to
814 state \context Voice explicitly when a chord was the start of a
817 With the new syntax, it is possible to distinguish between
818 articulations (or fingerings) which are for a single chord note,
819 and which are for the entire chord. This allows for per-note
820 fingerings, and is more logical on the whole.
824 User code may now be executed during interpreting. The syntax for
828 \applycontext #SCHEME-FUNCTION
832 User code may now be executed on arbitrary grobs during interpreting.
833 The syntax for this feature is
836 \applyoutput #SCHEME-FUNCTION
840 SCHEME-FUNCTION takes a single argument, and is called for every grob
841 that is created in the current context.
844 New algorithms for chord-name formatting have been installed. They
845 can be tuned and have ergonomic syntax for entering exceptions.
848 Texts may now be put on multimeasure rests, e.g.
851 R1*20^\markup @{ "GP" @}
855 Ancient notation now prints ligatures in Gregorian square neumes
856 notation, roughly following the typographical style of the Liber
857 hymnarius of Solesmes, published in 1983. Ligatures are still printed
858 without the proper line breaking and horizontal spacing.
861 Glissandi can now be printed using the zigzag style.
864 LilyPond can now print clusters. The syntax is
867 \apply #notes-to-clusters @{ NOTE NOTE .. @}
871 For irregular meters, beat grouping marks can be printed. The
875 #(set-time-signature 7 8 '(3 2 2))
880 Nested horizontal brackets for music analysis can now be printed:
889 @item Ottava brackets are now fully supported as a feature. The syntax
897 @item Metronome markings are printed when a \tempo command is processed.
901 @item Fingerings can be put on chords horizontally.
905 @item The appearance of various glyphs has been fine-tuned.
909 @item Different types of percent style repeats may now be nested.
913 @item The emacs support has been extended.
917 The manual has been completely revised and extended.
921 @unnumbered New features in 1.6 since 1.4
927 Support for figured bass and tablature.
930 Completely rewritten beam formatting: provides much better output
935 Completely revised and improved music font.
939 Completely rewritten MIDI import support.
942 Completely rewritten grace note support. Practically speaking this
943 means that grace notes can be slurred to normal normal notes.
947 Improved accidental handling and formatting: styles for producing
948 cautionaries may vary, and complex collisions between accidentals of a
949 chord are handled much better.
952 Better spacing: both globally and locally. This includes subtle
953 details like optical stem spacing.
956 More support for ancient notation: mensural ligatures, ambitus
957 (pitch range) of voices, more shapes, etc.
960 More support for piano notation: bracket pedals, directed arpeggios,
964 Easier music polyphonic music entry.
967 More extensibility, many speedups and bugfixes
970 The manual has been thoroughly revised.
973 Development is now hosted at http://savannah.gnu.org, and sources
974 can be downloaded through anonymous CVS.
977 Support for windows: LilyPond is part of the cygwin distribution,
978 which comes with a user-friendly installer.