1 \input texinfo @c -*-texinfo-*-
8 @chapter New features in 2.1 since 2.0
12 Lyrics are now aligned under note heads conforming engraving
13 standards. The responsible code has been rewritten, and is drastically
14 simpler from the previous version. To aid this rewrite, the syntactic
15 function of the extender line ( __ ) is been changed: it is now attached
16 to the lyric syllable.
19 When redefining a context, the associated identifier is also
20 updated. For example, after reading following the snippet,
27 the definition of @code{ScoreContext} is updated to include the changed
32 The weight of the stafflines is now heavier at smaller staff sizes.
33 The font has been modified to match this look: at smaller sizes, the
34 font is heavier and the note heads are more rounded.
36 @item Processing scores is now done while parsing the file. New
37 Scheme functions give more flexibility: for example, it is now possible
38 interpret a score, collecting synchronized musical events in a list, and
39 manipulate that information using inline Scheme. For an example, see
40 @file{input/no-notation/recording.ly}.
42 @item Font sizes can now truly be scaled continuously: the @code{font-size}
43 is similar to the old @code{font-relative-size}, but may be set to
44 fractional values; the closest design size will be scaled to achieve
45 the desired size. As a side-effect, there are now no longer
46 limitations in using smaller fonts (eg. grace notes) at small staff
49 @item The appearance of stem tips is now also engraved with rounded corners.
52 The placement of accidentals on chords and ledgered notes is improved.
57 @chapter New features in 2.0 since 1.8
62 Crescendos can now be drawn dotted or dashed.
65 Quarter tones are now supported. They are entered by suffixing
66 @code{ih} for a half-sharp and @code{eh} for a half-flat. Hence, the
67 following is an ascending list of pitches:
70 ceses ceseh ces ceh c cih cis cisih cisis
74 The following constructs have been removed from the syntax:
77 \duration #SCHEME-DURATION
79 \outputproperty @var{func} @var{symbol} = @var{value}
82 For @code{\outputproperty}, the following may be substituted:
85 \applyoutput #(outputproperty-compatibility @var{func}
86 @var{symbol} @var{value})
90 Clefs may now be transposed arbitrarily, for example
100 The syntax for chords and simultaneous music have changed.
101 Chords are entered as
107 while simultaneous music is entered as
110 <<@var{..music list..}>>
113 In effect, the meanings of both have been swapped relative to their 1.8
114 definition. The syntax for lists in @code{\markup} has changed
115 alongside, but figured bass mode was not changed, i.e.:
118 \markup @{ \center <@var{..list of markups..}> @}
119 \figure @{ <@var{figures}> @}
122 As chords the more often used than simultaneous music, this change will
126 Each music expression can now be tagged, to make different printed
127 versions from the same music expression. In the following example,
128 we see two versions of a piece of music, one for the full score, and
129 one with cue notes for the instrumental part:
133 @{ c4 f2 g4 @} % in the part, we have cue-notes
135 \tag #'score R1 % in the score: only a rest
139 The same can be applied to articulations, texts, etc.: they are
143 -\tag #@var{your-tags}
146 to an articulation, for example,
149 c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
152 This defines a note, which has a conditional fingering and a
153 string-number indication.
156 The settings for chord-fingering are more flexible. You can specify a
157 list where fingerings may be placed, eg.
160 \property Voice.fingeringOrientations = #'(left down)
163 This will put the fingering for the lowest note below the chord, and the
167 The script previously known as @code{ly2dvi} has been renamed to
168 @code{lilypond}. The binary itself is now installed as
172 Markup text (ie. general text formatting) may now be used for lyrics too.
175 Two new commands for grace notes have been added, @code{\acciaccatura}
176 and @code{\appoggiatura},
183 Both reflect the traditional meanings of acciaccatura and appogiatura,
184 and both insert insert a slur from the first grace note to the main
188 Layout options for grace notes are now stored in a context property,
189 and may now be set separately from musical content.
192 The @code{\new} command will create a context with a unique
193 name automatically. Hence, for multi-staff scores, it is no longer
194 necessary to invent arbitrary context names. For example, a two-staff
195 score may be created by
199 \new Staff @{ @var{notes for 1st staff} @}
200 \new Staff @{ @var{notes for 2nd staff} @}
207 Octave checks make octave errors easier to correct.
214 This checks that @var{pitch} (without octave) yields @var{pitch} (with
215 octave) in \relative mode. If not, a warning is printed, and the
219 All articulations must now be entered postfix. For example,
226 is a pair of beamed slurred eighth notes.
229 The definition of @code{\relative} has been simplified. Octaves are
230 now always propagated in the order that music is entered. In the
235 \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 @}
240 the octave of BODY is based on PRE, the starting octave of ALT1 on
241 BODY, the starting octave of ALT2 on ALT1, and the starting octave of
244 The same mechanism is used for all other music expressions, except the
245 chord. Backwards compatibility is retained through a special program option,
249 #(ly:set-option 'old-relative)
253 Windows users can double click a @code{.ly} file to process and view
254 it automagically through the new @code{lily-wins} frontend.
261 @chapter New features in 1.8 since 1.6
266 The chord entry code has been completely rewritten. It is now
267 cleaner and more flexible.
270 A new syntax has been added for text entry. This syntax is more
271 friendly than the old mechanism, and it is implemented in a more
272 robust and modular way. For more information, refer to the section on
273 "Text markup" in the notation manual.
276 The integration of the input language and Scheme has been made deeper:
277 you can now use LilyPond identifiers in Scheme, and use Scheme
278 expressions instead of LilyPond identifiers.
281 The internal representation of music has been cleaned up completely
282 and converted to Scheme data structures. The representation may be
286 A new uniform postfix syntax for articulation has been introduced.
287 A beamed slurred pair of eighth notes can be entered as
293 In version 2.0, postfix syntax will be the only syntax
294 available, and the dashes will become optional.
296 This will simplify the language: all articulations can be entered as
297 postfix, in any order.
300 A new syntax has been added for chords:
307 It is not necessary to update files to this syntax, but it will be for
308 using LilyPond version 2.0. In version 2.0, this syntax will be
318 \simultaneous @{ .. @}
321 for simultaneous music.
323 To convert your files from <PITCHES> to <<PITCHES>>, use the script
324 included in buildscripts/convert-new-chords.py
326 This change was introduced for the following reasons
330 It solves the "start score with chord" problem, where you have to
331 state \context Voice explicitly when a chord was the start of a
334 With the new syntax, it is possible to distinguish between
335 articulations (or fingerings) which are for a single chord note,
336 and which are for the entire chord. This allows for per-note
337 fingerings, and is more logical on the whole.
341 User code may now be executed during interpreting. The syntax for
345 \applycontext #SCHEME-FUNCTION
349 User code may now be executed on arbitrary grobs during interpreting.
350 The syntax for this feature is
353 \applyoutput #SCHEME-FUNCTION
357 SCHEME-FUNCTION takes a single argument, and is called for every grob
358 that is created in the current context.
361 New algorithms for chord-name formatting have been installed. They
362 can be tuned and have ergonomic syntax for entering exceptions.
365 Texts may now be put on multimeasure rests, e.g.
368 R1*20^\markup @{ "GP" @}
372 Ancient notation now prints ligatures in Gregorian square neumes
373 notation, roughly following the typographical style of the Liber
374 hymnarius of Solesmes, published in 1983. Ligatures are still printed
375 without the proper line breaking and horizontal spacing.
378 Glissandi can now be printed using the zigzag style.
381 LilyPond can now print clusters. The syntax is
384 \apply #notes-to-clusters @{ NOTE NOTE .. @}
388 For irregular meters, beat grouping marks can be printed. The
392 #(set-time-signature 7 8 '(3 2 2))
397 Nested horizontal brackets for music analysis can now be printed:
406 @item Ottava brackets are now fully supported as a feature. The syntax
414 @item Metronome markings are printed when a \tempo command is processed.
418 @item Fingerings can be put on chords horizontally.
422 @item The appearance of various glyphs has been fine-tuned.
426 @item Different types of percent style repeats may now be nested.
430 @item The emacs support has been extended.
434 The manual has been completely revised and extended.
438 @chapter New features in 1.6 since 1.4
444 Support for figured bass and tablature.
447 Completely rewritten beam formatting: provides much better output
452 Completely revised and improved music font.
456 Completely rewritten MIDI import support.
459 Completely rewritten grace note support. Practically speaking this
460 means that grace notes can be slurred to normal normal notes.
464 Improved accidental handling and formatting: styles for producing
465 cautionaries may vary, and complex collisions between accidentals of a
466 chord are handled much better.
469 Better spacing: both globally and locally. This includes subtle
470 details like optical stem spacing.
473 More support for ancient notation: mensural ligatures, ambitus
474 (pitch range) of voices, more shapes, etc.
477 More support for piano notation: bracket pedals, directed arpeggios,
481 Easier music polyphonic music entry.
484 More extensibility, many speedups and bugfixes
487 The manual has been thoroughly revised.
490 Development is now hosted at http://savannah.gnu.org, and sources
491 can be downloaded through anonymous CVS.
494 Support for windows: LilyPond is part of the cygwin distribution,
495 which comes with a user-friendly installer.