1 \input texinfo @c -*-texinfo-*-
8 @chapter New features in 2.1 since 2.0
21 @item Safe mode has been reinstated for lilypond.
22 When lilypond is invoked with @{--safe-mode}, @TeX{} and PostScript
23 file output is disallowed, and lilypond-bin is invoked with
24 @code{--safe-mode}, the user's Guile expressions are evaluated in a
25 safe environment and file inclusion is not allowed.
27 Be warned that a DOS attack using @TeX{} or PostScript is rather easy.
28 (This feature is still experimental.)
30 @item There is now a Scheme macro for defining markup
31 commands. Special mark-up commands can be defined in user-files too.
33 @item Many fixes for dimension scaling have been made,
34 resulting in correct results for scores that mix staves in different
37 @item Improved robustness when layout properties are accidentally removed.
39 @item A more cleanly constructed part combiner has been installed.
40 It is more robust and less buggy. The part-combiner can be used with
42 \newpartcombine @var{mus1} @var{mus2}
46 See @file{input/regression/new-part-combine.ly} for an example.
48 (This feature is still experimental.)
50 @item Formatting of rehearsal marks has been improved. The @code{\mark}
51 command now only does automatic incrementing for marks specified as
52 integer. For example, @code{\mark #1} will print an A in the default
53 style. See @file{input/regression/rehearsal-mark-letter.ly},
54 @file{input/regression/rehearsal-mark-number.ly}.
56 @item Formatting of ottava brackets has been much improved.
58 @item Objects in the output can now be documented: the following fragment
59 boxes the note head, and adds the text ``heads or tails?'' three
63 \context Voice \applyoutput #(add-balloon-text
64 'NoteHead "heads, or tails?"
72 @item Default staff sizes are now scalable. There are two new mechanisms for
73 setting staff sizes. Both are demonstrated in this fragment:
76 #(set-global-staff-size 15)
78 #(paper-set-staff-size (* 15 pt))
84 Both have the same effect on the global layout of a
85 piece. Similarly, the paper size may be changed as follows
88 #(set-paper-size "a4")
92 @item Warnings for bar check errors are more cleverly printed. This
93 makes @code{barCheckSynchronize} superfluous, so it is now switched
96 Warning: this will cause problems in scores that use bar checks to
99 @item The black note head was made a little rounder, which causes a less
100 frantic graphic impression.
103 A more concise syntax for checking octaves was introduced. A note may
104 be followed by @code{=}@var{quotes} which indicates what its absolute
105 octave should be. In the following example,
108 \relative c'' @{ c='' b=' d,='' @}
112 the d will generate a warning, because a d'' is
113 expected, but a d' is found.
114 @c @code adds ` ' very confusing.
116 @item There is a new mechanism for putting lyrics to melodies.
117 With this mechanism, @code{LyricVoice}s can be put melodies
118 individually, allowing for different melismatic sections in every
119 @code{LyricVoice}. See @file{input/regression/lyric-combine-new.ly}.
121 @item Bar lines may now be dotted.
124 @item The documentation now has links to a wiki, where everyone can
125 add personal comments to the manual.
127 @item Contexts may now be changed locally for an isolated music
128 expression. For example,
132 \consists "Pitch_squash_engraver"
138 @item The syntax for changing staffs has changed. The keyword
139 @code{\change} should now be used, e.g.
145 @item Features of spanner contexts, like @code{Staff}, can now be changed
146 using @code{\property}, eg.
150 \property Staff.StaffSymbol \set #'line-count = #4
156 puts a quarter note C on a staff with 4 lines.
159 @item Multi measure rests are now truly centered between the
160 clefs/barlines of the staff, their position is independent of symbols
163 @item Collision resolution for dots in chords has been improved greatly.
166 Spacing following barlines was improved for widely stretched lines.
169 Lyric hyphens and extenders now conform to standard typesetting
173 Lyrics are now aligned under note heads conforming to engraving
174 standards. The responsible code has been rewritten, and is drastically
175 simpler from the previous version. To aid this rewrite, the syntactic
176 function of the extender line ( __ ) has been changed: it is now
177 attached to the lyric syllable.
180 When redefining a context, the associated identifier is also
181 updated. For example, after reading the following snippet,
188 the definition of @code{ScoreContext} is updated to include the changed
193 The weight of the stafflines is now heavier at smaller staff sizes.
194 The font has been modified to match this look: at smaller sizes, the
195 font is heavier and the note heads are more rounded.
197 @item Processing scores is now done while parsing the file. New
198 Scheme functions give more flexibility: for example, it is now possible
199 interpret a score, collecting synchronized musical events in a list, and
200 manipulate that information using inline Scheme. For an example, see
201 @file{input/no-notation/recording.ly}.
203 @item Font sizes can now truly be scaled continuously: the @code{font-size}
204 is similar to the old @code{font-relative-size}, but may be set to
205 fractional values; the closest design size will be scaled to achieve
206 the desired size. As a side-effect, there are now no longer
207 limitations in using smaller fonts (eg. grace notes) at small staff
210 @item The appearance of stem tips is now also engraved with rounded corners.
213 The placement of accidentals on chords and ledgered notes is improved.
218 @chapter New features in 2.0 since 1.8
223 Crescendos can now be drawn dotted or dashed.
226 Quarter tones are now supported. They are entered by suffixing
227 @code{ih} for a half-sharp and @code{eh} for a half-flat. Hence, the
228 following is an ascending list of pitches:
231 ceses ceseh ces ceh c cih cis cisih cisis
235 The following constructs have been removed from the syntax:
238 \duration #SCHEME-DURATION
240 \outputproperty @var{func} @var{symbol} = @var{value}
243 For @code{\outputproperty}, the following may be substituted:
246 \applyoutput #(outputproperty-compatibility @var{func}
247 @var{symbol} @var{value})
251 Clefs may now be transposed arbitrarily, for example
261 The syntax for chords and simultaneous music have changed.
262 Chords are entered as
268 while simultaneous music is entered as
271 <<@var{..music list..}>>
274 In effect, the meanings of both have been swapped relative to their 1.8
275 definition. The syntax for lists in @code{\markup} has changed
276 alongside, but figured bass mode was not changed, i.e.:
279 \markup @{ \center <@var{..list of markups..}> @}
280 \figure @{ <@var{figures}> @}
283 As chords the more often used than simultaneous music, this change will
287 Each music expression can now be tagged, to make different printed
288 versions from the same music expression. In the following example,
289 we see two versions of a piece of music, one for the full score, and
290 one with cue notes for the instrumental part:
294 @{ c4 f2 g4 @} % in the part, we have cue-notes
296 \tag #'score R1 % in the score: only a rest
300 The same can be applied to articulations, texts, etc.: they are
304 -\tag #@var{your-tags}
307 to an articulation, for example,
310 c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
313 This defines a note, which has a conditional fingering and a
314 string-number indication.
317 The settings for chord-fingering are more flexible. You can specify a
318 list where fingerings may be placed, eg.
321 \property Voice.fingeringOrientations = #'(left down)
324 This will put the fingering for the lowest note below the chord, and the
328 The script previously known as @code{ly2dvi} has been renamed to
329 @code{lilypond}. The binary itself is now installed as
333 Markup text (ie. general text formatting) may now be used for lyrics too.
336 Two new commands for grace notes have been added, @code{\acciaccatura}
337 and @code{\appoggiatura},
344 Both reflect the traditional meanings of acciaccatura and appogiatura,
345 and both insert insert a slur from the first grace note to the main
349 Layout options for grace notes are now stored in a context property,
350 and may now be set separately from musical content.
353 The @code{\new} command will create a context with a unique
354 name automatically. Hence, for multi-staff scores, it is no longer
355 necessary to invent arbitrary context names. For example, a two-staff
356 score may be created by
360 \new Staff @{ @var{notes for 1st staff} @}
361 \new Staff @{ @var{notes for 2nd staff} @}
368 Octave checks make octave errors easier to correct.
375 This checks that @var{pitch} (without octave) yields @var{pitch} (with
376 octave) in \relative mode. If not, a warning is printed, and the
380 All articulations must now be entered postfix. For example,
387 is a pair of beamed slurred eighth notes.
390 The definition of @code{\relative} has been simplified. Octaves are
391 now always propagated in the order that music is entered. In the
396 \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 @}
401 the octave of BODY is based on PRE, the starting octave of ALT1 on
402 BODY, the starting octave of ALT2 on ALT1, and the starting octave of
405 The same mechanism is used for all other music expressions, except the
406 chord. Backwards compatibility is retained through a special program option,
410 #(ly:set-option 'old-relative)
414 Windows users can double click a @code{.ly} file to process and view
415 it automagically through the new @code{lily-wins} frontend.
422 @chapter New features in 1.8 since 1.6
427 The chord entry code has been completely rewritten. It is now
428 cleaner and more flexible.
431 A new syntax has been added for text entry. This syntax is more
432 friendly than the old mechanism, and it is implemented in a more
433 robust and modular way. For more information, refer to the section on
434 "Text markup" in the notation manual.
437 The integration of the input language and Scheme has been made deeper:
438 you can now use LilyPond identifiers in Scheme, and use Scheme
439 expressions instead of LilyPond identifiers.
442 The internal representation of music has been cleaned up completely
443 and converted to Scheme data structures. The representation may be
447 A new uniform postfix syntax for articulation has been introduced.
448 A beamed slurred pair of eighth notes can be entered as
454 In version 2.0, postfix syntax will be the only syntax
455 available, and the dashes will become optional.
457 This will simplify the language: all articulations can be entered as
458 postfix, in any order.
461 A new syntax has been added for chords:
468 It is not necessary to update files to this syntax, but it will be for
469 using LilyPond version 2.0. In version 2.0, this syntax will be
479 \simultaneous @{ .. @}
482 for simultaneous music.
484 To convert your files from <PITCHES> to <<PITCHES>>, use the script
485 included in buildscripts/convert-new-chords.py
487 This change was introduced for the following reasons
491 It solves the "start score with chord" problem, where you have to
492 state \context Voice explicitly when a chord was the start of a
495 With the new syntax, it is possible to distinguish between
496 articulations (or fingerings) which are for a single chord note,
497 and which are for the entire chord. This allows for per-note
498 fingerings, and is more logical on the whole.
502 User code may now be executed during interpreting. The syntax for
506 \applycontext #SCHEME-FUNCTION
510 User code may now be executed on arbitrary grobs during interpreting.
511 The syntax for this feature is
514 \applyoutput #SCHEME-FUNCTION
518 SCHEME-FUNCTION takes a single argument, and is called for every grob
519 that is created in the current context.
522 New algorithms for chord-name formatting have been installed. They
523 can be tuned and have ergonomic syntax for entering exceptions.
526 Texts may now be put on multimeasure rests, e.g.
529 R1*20^\markup @{ "GP" @}
533 Ancient notation now prints ligatures in Gregorian square neumes
534 notation, roughly following the typographical style of the Liber
535 hymnarius of Solesmes, published in 1983. Ligatures are still printed
536 without the proper line breaking and horizontal spacing.
539 Glissandi can now be printed using the zigzag style.
542 LilyPond can now print clusters. The syntax is
545 \apply #notes-to-clusters @{ NOTE NOTE .. @}
549 For irregular meters, beat grouping marks can be printed. The
553 #(set-time-signature 7 8 '(3 2 2))
558 Nested horizontal brackets for music analysis can now be printed:
567 @item Ottava brackets are now fully supported as a feature. The syntax
575 @item Metronome markings are printed when a \tempo command is processed.
579 @item Fingerings can be put on chords horizontally.
583 @item The appearance of various glyphs has been fine-tuned.
587 @item Different types of percent style repeats may now be nested.
591 @item The emacs support has been extended.
595 The manual has been completely revised and extended.
599 @chapter New features in 1.6 since 1.4
605 Support for figured bass and tablature.
608 Completely rewritten beam formatting: provides much better output
613 Completely revised and improved music font.
617 Completely rewritten MIDI import support.
620 Completely rewritten grace note support. Practically speaking this
621 means that grace notes can be slurred to normal normal notes.
625 Improved accidental handling and formatting: styles for producing
626 cautionaries may vary, and complex collisions between accidentals of a
627 chord are handled much better.
630 Better spacing: both globally and locally. This includes subtle
631 details like optical stem spacing.
634 More support for ancient notation: mensural ligatures, ambitus
635 (pitch range) of voices, more shapes, etc.
638 More support for piano notation: bracket pedals, directed arpeggios,
642 Easier music polyphonic music entry.
645 More extensibility, many speedups and bugfixes
648 The manual has been thoroughly revised.
651 Development is now hosted at http://savannah.gnu.org, and sources
652 can be downloaded through anonymous CVS.
655 Support for windows: LilyPond is part of the cygwin distribution,
656 which comes with a user-friendly installer.