1 \input texinfo @c -*-texinfo-*-
8 @chapter New features in 2.1 since 2.0
20 @item A new part combiner which is more cleanly constructed, more
21 robust and less buggy. The
22 part-combiner can be used with
24 \newpartcombine @var{mus1} @var{mus2}
28 In this case, both musics are put into @code{Voice} contexts called
29 @code{one} and @code{two} automatically.
31 (This feature is still experimental.)
33 @item Formatting of rehearsal marks has been improved. The @code{\mark}
34 command now only does automatic incrementing for marks specified as
35 integer. For example, @code{\mark #1} will print an A in the default
36 style. See @file{input/regression/rehearsal-mark-letter.ly},
37 @file{input/regression/rehearsal-mark-number.ly}.
39 @item Formatting of ottava brackets has been much improved.
41 @item Objects in the output can now be documented: the following fragment
42 boxes the note head, and adds the text ``heads or tails?'' three
46 \context Voice \applyoutput #(add-balloon-text
47 'NoteHead "heads, or tails?"
55 @item Default staff sizes are now scalable. There are two new mechanisms for
56 setting staff sizes. Both are demonstrated in this fragment:
59 #(set-global-staff-size 15)
61 #(paper-set-staff-size (* 15 pt))
67 Both have the same effect on the global layout of a
68 piece. Similarly, the paper size may be changed as follows
71 #(set-paper-size "a4")
75 @item Warnings for bar check errors are more cleverly printed. This
76 makes @code{barCheckSynchronize} superfluous, so it is now switched
79 Warning: this will cause problems in scores that use bar checks to
82 @item The black note head was made a little rounder, which causes a less
83 frantic graphic impression.
86 A more concise syntax for checking octaves was introduced. A note may
87 be followed by @code{=}@var{quotes} which indicates what its absolute
88 octave should be. In the following example,
91 \relative c'' @{ c='' b=' d,='' @}
95 the d will generate a warning, because a d'' is
96 expected, but a d' is found.
97 @c @code adds ` ' very confusing.
99 @item There is a new mechanism for putting lyrics to melodies.
100 With this mechanism, @code{LyricVoice}s can be put melodies
101 individually, allowing for different melismatic sections in every
102 @code{LyricVoice}. See @file{input/regression/lyric-combine-new.ly}.
104 @item Bar lines may now be dotted.
107 @item The documentation now has links to a wiki, where everyone can
108 add personal comments to the manual.
110 @item Contexts may now be changed locally for an isolated music
111 expression. For example,
115 \consists "Pitch_squash_engraver"
121 @item The syntax for changing staffs has changed. The keyword
122 @code{\change} should now be used, e.g.
128 @item Features of spanner contexts, like @code{Staff}, can now be changed
129 using @code{\property}, eg.
133 \property Staff.StaffSymbol \set #'line-count = #4
139 puts a quarter note C on a staff with 4 lines.
142 @item Multi measure rests are now truly centered between the
143 clefs/barlines of the staff, their position is independent of symbols
146 @item Collision resolution for dots in chords has been improved greatly.
149 Spacing following barlines was improved for widely stretched lines.
152 Lyric hyphens and extenders now conform to standard typesetting
156 Lyrics are now aligned under note heads conforming to engraving
157 standards. The responsible code has been rewritten, and is drastically
158 simpler from the previous version. To aid this rewrite, the syntactic
159 function of the extender line ( __ ) has been changed: it is now
160 attached to the lyric syllable.
163 When redefining a context, the associated identifier is also
164 updated. For example, after reading the following snippet,
171 the definition of @code{ScoreContext} is updated to include the changed
176 The weight of the stafflines is now heavier at smaller staff sizes.
177 The font has been modified to match this look: at smaller sizes, the
178 font is heavier and the note heads are more rounded.
180 @item Processing scores is now done while parsing the file. New
181 Scheme functions give more flexibility: for example, it is now possible
182 interpret a score, collecting synchronized musical events in a list, and
183 manipulate that information using inline Scheme. For an example, see
184 @file{input/no-notation/recording.ly}.
186 @item Font sizes can now truly be scaled continuously: the @code{font-size}
187 is similar to the old @code{font-relative-size}, but may be set to
188 fractional values; the closest design size will be scaled to achieve
189 the desired size. As a side-effect, there are now no longer
190 limitations in using smaller fonts (eg. grace notes) at small staff
193 @item The appearance of stem tips is now also engraved with rounded corners.
196 The placement of accidentals on chords and ledgered notes is improved.
201 @chapter New features in 2.0 since 1.8
206 Crescendos can now be drawn dotted or dashed.
209 Quarter tones are now supported. They are entered by suffixing
210 @code{ih} for a half-sharp and @code{eh} for a half-flat. Hence, the
211 following is an ascending list of pitches:
214 ceses ceseh ces ceh c cih cis cisih cisis
218 The following constructs have been removed from the syntax:
221 \duration #SCHEME-DURATION
223 \outputproperty @var{func} @var{symbol} = @var{value}
226 For @code{\outputproperty}, the following may be substituted:
229 \applyoutput #(outputproperty-compatibility @var{func}
230 @var{symbol} @var{value})
234 Clefs may now be transposed arbitrarily, for example
244 The syntax for chords and simultaneous music have changed.
245 Chords are entered as
251 while simultaneous music is entered as
254 <<@var{..music list..}>>
257 In effect, the meanings of both have been swapped relative to their 1.8
258 definition. The syntax for lists in @code{\markup} has changed
259 alongside, but figured bass mode was not changed, i.e.:
262 \markup @{ \center <@var{..list of markups..}> @}
263 \figure @{ <@var{figures}> @}
266 As chords the more often used than simultaneous music, this change will
270 Each music expression can now be tagged, to make different printed
271 versions from the same music expression. In the following example,
272 we see two versions of a piece of music, one for the full score, and
273 one with cue notes for the instrumental part:
277 @{ c4 f2 g4 @} % in the part, we have cue-notes
279 \tag #'score R1 % in the score: only a rest
283 The same can be applied to articulations, texts, etc.: they are
287 -\tag #@var{your-tags}
290 to an articulation, for example,
293 c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
296 This defines a note, which has a conditional fingering and a
297 string-number indication.
300 The settings for chord-fingering are more flexible. You can specify a
301 list where fingerings may be placed, eg.
304 \property Voice.fingeringOrientations = #'(left down)
307 This will put the fingering for the lowest note below the chord, and the
311 The script previously known as @code{ly2dvi} has been renamed to
312 @code{lilypond}. The binary itself is now installed as
316 Markup text (ie. general text formatting) may now be used for lyrics too.
319 Two new commands for grace notes have been added, @code{\acciaccatura}
320 and @code{\appoggiatura},
327 Both reflect the traditional meanings of acciaccatura and appogiatura,
328 and both insert insert a slur from the first grace note to the main
332 Layout options for grace notes are now stored in a context property,
333 and may now be set separately from musical content.
336 The @code{\new} command will create a context with a unique
337 name automatically. Hence, for multi-staff scores, it is no longer
338 necessary to invent arbitrary context names. For example, a two-staff
339 score may be created by
343 \new Staff @{ @var{notes for 1st staff} @}
344 \new Staff @{ @var{notes for 2nd staff} @}
351 Octave checks make octave errors easier to correct.
358 This checks that @var{pitch} (without octave) yields @var{pitch} (with
359 octave) in \relative mode. If not, a warning is printed, and the
363 All articulations must now be entered postfix. For example,
370 is a pair of beamed slurred eighth notes.
373 The definition of @code{\relative} has been simplified. Octaves are
374 now always propagated in the order that music is entered. In the
379 \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 @}
384 the octave of BODY is based on PRE, the starting octave of ALT1 on
385 BODY, the starting octave of ALT2 on ALT1, and the starting octave of
388 The same mechanism is used for all other music expressions, except the
389 chord. Backwards compatibility is retained through a special program option,
393 #(ly:set-option 'old-relative)
397 Windows users can double click a @code{.ly} file to process and view
398 it automagically through the new @code{lily-wins} frontend.
405 @chapter New features in 1.8 since 1.6
410 The chord entry code has been completely rewritten. It is now
411 cleaner and more flexible.
414 A new syntax has been added for text entry. This syntax is more
415 friendly than the old mechanism, and it is implemented in a more
416 robust and modular way. For more information, refer to the section on
417 "Text markup" in the notation manual.
420 The integration of the input language and Scheme has been made deeper:
421 you can now use LilyPond identifiers in Scheme, and use Scheme
422 expressions instead of LilyPond identifiers.
425 The internal representation of music has been cleaned up completely
426 and converted to Scheme data structures. The representation may be
430 A new uniform postfix syntax for articulation has been introduced.
431 A beamed slurred pair of eighth notes can be entered as
437 In version 2.0, postfix syntax will be the only syntax
438 available, and the dashes will become optional.
440 This will simplify the language: all articulations can be entered as
441 postfix, in any order.
444 A new syntax has been added for chords:
451 It is not necessary to update files to this syntax, but it will be for
452 using LilyPond version 2.0. In version 2.0, this syntax will be
462 \simultaneous @{ .. @}
465 for simultaneous music.
467 To convert your files from <PITCHES> to <<PITCHES>>, use the script
468 included in buildscripts/convert-new-chords.py
470 This change was introduced for the following reasons
474 It solves the "start score with chord" problem, where you have to
475 state \context Voice explicitly when a chord was the start of a
478 With the new syntax, it is possible to distinguish between
479 articulations (or fingerings) which are for a single chord note,
480 and which are for the entire chord. This allows for per-note
481 fingerings, and is more logical on the whole.
485 User code may now be executed during interpreting. The syntax for
489 \applycontext #SCHEME-FUNCTION
493 User code may now be executed on arbitrary grobs during interpreting.
494 The syntax for this feature is
497 \applyoutput #SCHEME-FUNCTION
501 SCHEME-FUNCTION takes a single argument, and is called for every grob
502 that is created in the current context.
505 New algorithms for chord-name formatting have been installed. They
506 can be tuned and have ergonomic syntax for entering exceptions.
509 Texts may now be put on multimeasure rests, e.g.
512 R1*20^\markup @{ "GP" @}
516 Ancient notation now prints ligatures in Gregorian square neumes
517 notation, roughly following the typographical style of the Liber
518 hymnarius of Solesmes, published in 1983. Ligatures are still printed
519 without the proper line breaking and horizontal spacing.
522 Glissandi can now be printed using the zigzag style.
525 LilyPond can now print clusters. The syntax is
528 \apply #notes-to-clusters @{ NOTE NOTE .. @}
532 For irregular meters, beat grouping marks can be printed. The
536 #(set-time-signature 7 8 '(3 2 2))
541 Nested horizontal brackets for music analysis can now be printed:
550 @item Ottava brackets are now fully supported as a feature. The syntax
558 @item Metronome markings are printed when a \tempo command is processed.
562 @item Fingerings can be put on chords horizontally.
566 @item The appearance of various glyphs has been fine-tuned.
570 @item Different types of percent style repeats may now be nested.
574 @item The emacs support has been extended.
578 The manual has been completely revised and extended.
582 @chapter New features in 1.6 since 1.4
588 Support for figured bass and tablature.
591 Completely rewritten beam formatting: provides much better output
596 Completely revised and improved music font.
600 Completely rewritten MIDI import support.
603 Completely rewritten grace note support. Practically speaking this
604 means that grace notes can be slurred to normal normal notes.
608 Improved accidental handling and formatting: styles for producing
609 cautionaries may vary, and complex collisions between accidentals of a
610 chord are handled much better.
613 Better spacing: both globally and locally. This includes subtle
614 details like optical stem spacing.
617 More support for ancient notation: mensural ligatures, ambitus
618 (pitch range) of voices, more shapes, etc.
621 More support for piano notation: bracket pedals, directed arpeggios,
625 Easier music polyphonic music entry.
628 More extensibility, many speedups and bugfixes
631 The manual has been thoroughly revised.
634 Development is now hosted at http://savannah.gnu.org, and sources
635 can be downloaded through anonymous CVS.
638 Support for windows: LilyPond is part of the cygwin distribution,
639 which comes with a user-friendly installer.