5 @node Tutorial, , , Top
7 * Introduction:: Introduction
8 * The first tune:: The first tune
9 * Lyrics and chords:: Lyrics and chords
10 * Piano music:: Piano music
11 * end of tutorial:: The end
14 @node Introduction, , , Tutorial
18 LilyPond prints music from a specification that you, the user, supply.
19 You have to give that specification using a @emph{language}. This
20 document is a gentle introduction to that language, which is called
21 Mudela, an acronym of Music Definition Language.
23 This tutorial will demonstrate how to use Mudela by presenting
24 examples of input along with resulting output. We will use English
25 terms for notation. In case you are not familiar with those, you may
26 consult the glossary that is distributed with LilyPond.
28 The examples discussed are included in the distribution, in the
29 subdirectory @file{input/tutorial/}. It is recommended that you
30 experiment with writing Mudela input yourself, to get a feel for
33 @node The first tune, , , Tutorial
34 @section The first tune
37 To demonstrate what LilyPond input looks like, we start off with a
38 full fledged, yet simple example. It is a convoluted version
39 of the famous menuet in J. S. Bach's @emph{Klavierbuechlein}.
42 % lines preceded by a percent are comments.
46 \relative c'' \sequential{
51 d4 g,8 a b c d4 g, g |
52 e'4 c8 d e fis g4 g, g |
53 c4 d8()c b a( )b4 c8 b a g |
54 a4 [b8 a] [g fis] g2. |
59 g4 e8 fis g d cis4 b8 cis a4 |
60 a8-. b-. cis-. d-. e-. fis-.
67 % standard settings are too wide for a book
73 Enter it (or copy it, the filename is @file{menuet.ly}), compile it
74 with LilyPond and view the output. Details of this procedure may vary
75 from system to system. To create the output, one would issue the
76 command `@code{ly2dvi menuet}'. @file{ly2dvi} is a program that does
77 the job of running LilyPond and TeX, handling of titles and
78 adjusting of page margins.
80 If all goes well, the file @file{menuet.dvi} will be created.
81 To view this output, issue the command `@code{xdvi menuet}'.
83 Now that we are familiar with the procedure of producing output, we
84 will analyse the input, line by line.
86 Let's try to redo this
89 % lines preceded by a percent are comments.
92 The percent sign, `@code{%}', introduces a line comment. If you want to
93 make larger comments, you can use block comments. These are delimited
94 by `@code{%@{}' and `@code{%@}}'
96 @multitable @columnfractions .60 .39
99 @c @example urg: no tt font
100 @c @exdent % lines preceded by a percent are comments.
101 @exdent @code{% lines preceded by a percent are comments.}
104 The percent sign, `@code{%}', introduces a line comment. If you
105 want to make larger comments, you can use block comments. These
106 are delimited by `@code{%@{}' and `@code{%@}}'
113 By default, LilyPond will use definitions for a 20
114 point@footnote{A point is the standard measure of length for
115 printing. One point is 1/72.27 inch.} high staff. We want smaller
116 output (16 point staff height), so we must import the settings for
117 that size, which is done.@example
122 A mudela file combines music with directions for outputting that
123 music. The music is combined with the output directions by putting
124 them into a @code{\score} block.
130 This makes LilyPond ready for accepting notes.
136 As we will see, pitches are combinations of octave, note name and
137 chromatic alteration. In this scheme, the octave is indicated by
138 using raised quotes (`@code{'}') and ``lowered'' quotes (commas:
139 `@code{,}'). The central C is denoted by @code{c'}. The C one octave
140 higher is @code{c''}. One and two octaves below the central C is
141 denoted by @code{c} and @code{c,} respectively.
143 For pitches in a long piece you might have to type many quotes. To
144 remedy this, LilyPond has a ``relative'' octave entry mode. In this
145 mode, octaves of notes without quotes are chosen such that a note is
146 as close as possible (graphically, on the staff) to the the preceding
147 note. If you add a high-quote an extra octave is added. The lowered
148 quote (a comma) will subtract an extra octave. Because the first note
149 has no predecessor, you have to give the (absolute) pitch of the note
150 to start with.@example
155 What follows is sequential music, i.e.,
156 notes that are to be played and printed after each other.@example
161 This command changes the time signature of the current piece: a 3/4
162 sign is printed. This command is also used to generate bar lines in
163 the right spots.@example
168 This command changes the current key to G-major. Although this
169 command comes after the @code{\time} command, in the output, the key
170 signature comes before the time signature: LilyPond knows about music
171 typesetting conventions. @example
176 This command tells LilyPond that the following piece of music must
177 be played twice; @code{"volta"} volta brackets should be used for
178 alternatives---if there were any.
184 The subject of the repeat is again sequential music. Since
185 @code{\sequential} is such a common construct, a shorthand is provided:
186 just leave off @code{\sequential}, and the result is the same. @example
191 This is a note with pitch @code{d} (determined up to octaves). The
192 relative music was started with a @code{c''}, so the real pitch of this
193 note is @code{d''}. The @code{4} designates the duration of the note
194 (it is a quarter note). @example
199 These are notes with pitch @code{a} and @code{b}. Because their
200 duration is the same as the @code{g}, there is no need to enter the
201 duration (You may enter it anyway, eg. @code{a4 b4}) @example
206 Three more notes. The `@code{|}' character is a `barcheck'. When
207 processing the music, LilyPond will verify that barchecks are found at
208 the start of a measure. This can help you track down errors.
210 So far, no notes were chromatically altered. Here is the first one
211 that is: @code{fis}. Mudela by default uses Dutch note names, and
212 ``Fis'' is the Dutch note name for ``F sharp''. However, there is no
213 sharp sign in the output. The program keeps track of key signatures,
214 and will only print accidentals if they are needed.
220 LilyPond guesses were beams can be added to eighth and shorter notes.
221 In this case, a beam over 4 eighths is added.
224 c4 d8( )c b a( )b4 c8 b a g |
227 The next line shows how to make a slur:
228 the beginning and ending note of the slur is marked with an opening and
229 closing parenthesis respectively. In the line shown above this is
230 done for two slurs. Slur markers (parentheses) are between
236 Automatic beaming can be overridden by inserting beam marks
237 (brackets). Brackets are put around notes you want beamed.@example
242 A duration with augmentation dot is notated
243 with the duration number followed by a period.@example
248 This ends the sequential music to be repeated. LilyPond will typeset
249 a repeat bar. @example
254 This line shows that Lily will print an accidental if that is
255 needed: the first C sharp will be printed with an accidental, the
256 second one without. @example
258 a8-. b-. cis-. d-. e-. fis-.
261 You can enter articulation signs either in a verbose form using a
262 shorthand. Here we demonstrate the shorthand: it is formed by a dash
263 and the the character for the articulation to use, e.g. `@code{-.}' for
264 staccato as shown above. @example
270 Rests are denoted by the special notename `@code{r}'. You can also enter
271 an invisible rest by using the special notename `@code{s}'.
277 All articulations have a verbose form, like @code{\fermata}. The
278 command `@code{\fermata}' is not part of the core of the language (most
279 of the other discussed elements are), but it is a shorthand for a more
280 complicated description of a fermata. @code{\fermata} names that
281 description and is therefore called an @emph{identifier}. @example
295 This specifies a conversion from music to notation output. Most of
296 the details of this conversions (font sizes, dimensions, etc.) have
297 been taken care of, but to fit the output in this document, it has
298 to be smaller. We do this by setting the line width to 14 centimeters
299 (approximately 6 inches).
305 The last brace ends the @code{\score} block.
307 There are two things to note here. The format contains musical
308 concepts like pitches and durations, instead of symbols and positions:
309 the input format tries to capture the meaning of @emph{music}, and not
310 notation. Therefore Second, the format tries to be @emph{context-free}:
311 a note will sound the same regardless of the current time signature,
314 The purpose of LilyPond is explained informally by the term `music
315 typesetter'. This is not a fully correct name: not only does the
316 program print musical symbols, it also makes esthetic decisions. All
317 symbols and their placement is @emph{generated} from a high-level musical
318 description. In other words, LilyPond would be best
319 described by `music compiler' or `music to notation compiler'.
321 @node Lyrics and chords, , , Tutorial
322 @section Lyrics and chords
324 In this section we show how to typeset a song of unknown
325 origin.@footnote{The author would welcome information about the origin
330 title = "The river is flowing";
331 composer = "Traditional (?)";
333 \include "paper16.ly"
334 melody = \notes \relative c' @{
337 c4 c8 d [es () d] c4 | f4 f8 g [es() d] c g |
338 c4 c8 d [es () d] c4 | d4 es8 d c4.
343 The ri -- ver is flo- __ wing, flo -- wing and gro -- wing, the
344 ri -- ver is flo -- wing down to the sea.
347 accompaniment =\chords @{
349 c2-3- f-3-.7 d-min es4 c8-min r8
350 c2-min f-min7 g-7^3.5 c-min @}
355 \context ChordNames \accompaniment
358 \context Staff = mel @{
359 \property Staff.noAutoBeaming = "1"
360 \property Staff.automaticMelismata = "1"
363 \context Lyrics \text
366 \paper @{ linewidth = 10.0\cm; @}
371 The result would look this@footnote{The titling and font size shown
372 may differ, since the titling in this document is not generated by
375 @center @strong{The river is flowing}
380 title = "The river is flowing";
381 composer = "Traditional (?)";
383 \include "paper16.ly"
384 melody = \notes \relative c' {
387 c4 c8 d [es () d] c4 | f4 f8 g [es() d] c g |
388 c4 c8 d [es () d] c4 | d4 es8 d c4.
393 The ri -- ver is flo- __ wing, flo -- wing and gro -- wing, the
394 ri -- ver is flo -- wing down to the sea.
397 accompaniment =\chords {
399 c2-3- f-3-.7 d-min es4 c8-min r8
400 c2-min f-min7 g-7^3.5 c-min }
405 \context ChordNames \accompaniment
408 \context Staff = mel {
409 \property Staff.noAutoBeaming = "1"
410 \property Staff.automaticMelismata = "1"
413 \context Lyrics \text
416 \paper { linewidth = 10.0\cm; }
420 Again, we will dissect the file line by line.@example
425 Information about the music you are about to typeset goes into a
426 @code{\header} block. The information in this block is not used by
427 LilyPond, but it is included in the output. @file{ly2dvi} uses this
428 information to print titles above the music.
431 title = "The river is flowing";
432 composer = "Traditional (?)";
434 the @code{\header} block contains assignments. An assignment starts
435 with a string. (which is unquoted, in this case). Then comes the
436 equal sign `@code{=}'. After the equal sign comes the expression you
437 want to store. In this case, you want to put in strings. The
438 information has to be quoted here, because it contains spaces. The
439 assignment is finished with a semicolon.@example
441 \include "paper16.ly"
444 Smaller size for inclusion in a book.@example
446 melody = \notes \relative c' @{
449 The structure of the file will be the same as the previous one, a
450 @code{\score} block with music in it. To keep things readable, we will
451 give names to the different parts of music, and use the names to
452 construct the music within the score block.
460 The piece starts with an anacrusis of one eighth. @example
462 c4 c8 d [es () d] c4 | f4 f8 g [es() d] c g |
463 c4 c8 d [es () d] c4 | d4 es8 d c4.
467 We use explicit beaming. Since this is a song, we will turn automatic
468 beams off, and use explicit beaming where needed.@example
473 This ends the definition of @code{melody}. Note that there are no
474 semicolons after assignments at top level.@example
479 Another identifier assignment. This one is for the lyrics.
480 Lyrics are formed by syllables that have duration, and not by
481 notes. To make LilyPond parse words as syllables, switch it into
482 lyrics mode with @code{\lyrics}. Again, the brace after @code{\lyrics}
483 is a shorthand for @code{\sequential @{}. @example
485 The4 ri -- ver is flo- __ wing, flo -- wing and gro -- wing, the
486 ri- ver is flo- __ wing down to the sea.
490 The syllables themselves are separated by spaces. You can get syllable
491 extenders by entering `@code{__}', and centered hyphens with
492 `@code{-}@code{-}'. We enter the syllables as if they are all quarter notes
493 in length (hence the @code{4}), and use a feature to align the
494 syllables to the music (which obviously isn't all quarter notes.)
497 accompaniment =\chords @{
500 We'll put chords over the music. There is a special mode (analogous
501 to @code{\lyrics} and @code{\notes} mode) where you can give the names
502 of the chords you want, instead of the notes comprising the chord.
508 There is no accompaniment during the anacrusis.@example
513 A chord is started by the tonic of the chord. The
514 first one lasts a half note. An unadorned note creates a major
515 triad, while a minor triad is wanted. @code{3-} modifies the third to
516 be small. @code{7} modifies (adds) a seventh, which is small by default
517 to create the @code{f a c es} chord. Multiple modifiers must be
518 separated by a dot.@example
523 Some modifiers have predefined names, eg. @code{min} is the same as
524 @code{3-}, so @code{d-min} is a minor @code{d} chord.@example
526 c2-min f-min7 g-7^3.5 c-min @}
529 A named modifier @code{min} and a normal modifier @code{7} do not have
530 to be separated by a dot. Tones from a chord are removed with chord
531 subtractions. Subtractions are started with a caret, and they are
532 also separated by dots. In this example, @code{g-7^3.5} produces a
533 minor seventh. The brace ends the sequential music. @example
539 We assemble the music in the @code{\score} block. Melody, lyrics and
540 accompaniment have to sound at the same time, so they should be
541 @code{\simultaneous}.@example
546 Chord mode generates notes grouped in @code{\simultaneous} music. If
547 you remove the comment sign, you can see the chords in normal
548 notation: they will be printed as note heads on a separate
551 \context ChordNames \accompaniment
554 Normally, the notes that you enter are transformed into note heads.
555 The note heads alone make no sense, they need surrounding information:
556 a key signature, a clef, staff lines, etc. They need @emph{context}. In
557 LilyPond, these symbols are created by objects called `interpretation
558 context'. Interpretation contexts only exist during a run of
559 LilyPond. Interpretation contexts that are for printing music (as
560 opposed to playing music) are called `notation context'.
562 By default, LilyPond will create a Staff contexts for you. If you
563 would remove the @code{%} sign in the previous line, you can see that
566 We don't want default contexts here, because we want names, not note
567 heads. An interpretation context can also created upon explicit
568 request. The keyword for such a request is @code{\context}. It takes
569 two arguments. The first is the name of a interpretation context.
570 The name is a string, it can be quoted with double quotes). The
571 second argument is the music that should be interpreted in this
572 context. For the previous line, we could have written @code{\context
573 Staff \accompaniment}, and get the same effect.@example
578 The lyrics need to be aligned with the melody. This is done by
579 combining both with @code{\addlyrics}. @code{\addlyrics} takes two
580 pieces of music (usually a melody and lyrics, in that order) and
581 aligns the syllables of the second piece under the notes of the
582 first piece. If you would reverse the order, the notes would be
583 aligned on the lyrics, which is not very useful. (Besides, it looks
586 \context Staff = mel @{
589 This is the argument of @code{\addlyrics}. We instantiate a
590 @code{Staff} context explicitly: should you chose to remove comment
591 before the ``note heads'' version of the accompaniment, the
592 accompaniment will be on a nameless staff. The melody has to be on a
593 different staff as the accompaniment. This is accomplished by giving
594 the melody staff a different name.@example
596 \property Staff.noAutoBeaming = "1"
599 An interpretation context has variables that tune its behaviour. One
600 of the variables is @code{noAutoBeaming}. If set and non-zero (i.e.,
601 true) LilyPond will not try to put automatic beaming on the current
604 \property Staff.automaticMelismata = "1"
607 Similarly, we don't want to print a syllable when there is
608 a slur. This sets up the Staff context to signal slurs while
609 @code{\addlyrics} is processed. @example
615 Finally, we put the melody on the current staff. Note that the
616 @code{\property} directives and @code{\melody} are grouped in sequential
617 music, so the property settings are done before the melody is
620 \context Lyrics \text
623 The second argument of @code{\addlyrics} is the text. The text also
624 should not land on a Staff, but on a interpretation context for
625 syllables, extenders, hyphens etc. This context is called
631 This ends @code{\simultaneous}.@example
636 This makes the music go to a MIDI file. MIDI is great for
637 checking music you enter. You listen to the MIDI file: if you hear
638 something unexpected, it's probably a typing error. @code{\midi} is an
639 `output definition', a declaration that specifies how to output music
640 analogous to @code{\paper @{ @}}.@example
642 \paper @{ linewidth = 10.0\cm; @}
645 We also want notation output. The linewidth is short so the piece
646 will be set in two lines. @example
653 @node Piano music, , , Tutorial
656 Our third subject is a piece piano music. The fragment in the input
657 file is a piano reduction of the G major Sinfonia by Giovanni Battista
658 Sammartini. It was composed around 1740.
662 \include "paper16.ly";
664 viola = \notes \relative c' \context Voice = viola {
666 \property Voice.verticalDirection = \down g'8. b,16
671 oboes = \notes \relative c'' \context Voice = oboe {
672 \stemup s4 g8. b,16 c8 r <e'8.-\p g> <f16 a>
673 \grace <e8( g> <d4 f> <c2 e> \times 2/3 { <d8 \< f> <e g> <f a> }
675 { \times 2/3 { a8 g c } \! c2 }
676 \context Voice = oboeTwo {
679 \property Grace.verticalDirection = \down
684 \grace <c,8( e> <)b8. d8.-\trill> <c16 e> |
685 [<d ( f> < )f8. a>] <)b,8 d> r [<d16( f> <f8. )a>] <b,8 d> r |
686 [<c16( e> < )e8. g>] <c8 e,>
689 hoomPah = \notes \transpose c' {
690 c8 \translator Staff = top \stemdown
691 c'8 \translator Staff = bottom \stemup }
693 hoomPahHoomPah = { [\hoomPah \hoomPah] }
695 bassvoices = \notes \relative c' {
697 \hoomPahHoomPah \hoomPahHoomPah \hoomPahHoomPah \hoomPahHoomPah
698 \stemdown [c8 c'8] r4
700 < {\stemup r2 <e4 c'> <c8 g'> }
701 \context Voice = reallyLow {\stemdown g2 ~ | g4 c8 } >
705 \context PianoStaff \notes <
706 \context Staff = top < \time 2/2;
707 \context Voice = viola \viola
710 \context Staff = bottom < \time 2/2; \clef bass;
717 linewidth = 15.0 \cm; }
721 If it looks like incomprehensible gibberish to you@dots{} Then you are
722 right. The author has doctored this example to have as many quirks in
723 one system as possible.@example
724 viola = \notes \relative c' \context Voice = viola @{
726 In this example, you can see multiple parts on a staff. Each part is
727 associated with one notation context. This notation context handles
728 stems and dynamics (among others). The name of this context is
729 @code{Voice}. For each part we have to make sure that there is
730 precisely one Voice context@footnote{If @code{\context} would not
731 have been specified explicitly, three @code{Voice} contexts would be
732 created: one for each note in the first chord.}.@example
735 @code{<} and @code{>} are short hands for @code{\simultaneous @{} and
736 @code{@}}. So the expression enclosed in @code{<} and @code{>} is a
737 chord. @code{\f} places a forte symbol under the chord.@example
738 \property Voice.verticalDirection = \down
740 @code{verticalDirection} is a property of the voice context. It
741 controls the directions of stems, articulations marks and other
743 If @code{verticalDirection} is set to @code{\down}
744 (identifier for the integer -1) the stems go down,
745 @code{\up} (identifier for the integer 1) makes the stems go up.@example
748 Relative octaves work a little differently with chords. The starting
749 point for the note following a chord is the first note of the chord. So
750 the @code{g} gets an octave up quote: it is a fifth above the starting
751 note of the previous chord (the central C).
756 @code{s} is a `spacer' rest. It does not print anything, but it does
757 have the duration of a rest. @example
758 oboes = \notes \relative c'' \context Voice = oboe @{
760 Now comes a part for two oboes. They play homophonically, so we
761 print the notes as one voice that makes chords. Again, we insure that
762 these notes are indeed processed by precisely one context with
763 @code{\context}.@example
764 \stemup s4 g8. b,16 c8 r <e'8.-\p g> <f16 a>
766 @code{\stemup} is an identifier reference. It is shorthand for
767 @code{\property Voice.verticalDirection = \up}. If possible, you
768 should use predefined identifiers like these for setting properties.
769 Your input will be less dependent upon the implementation of LilyPond.
771 \grace <e8( g> < )d4 f> <c2 e>
773 @code{\grace} introduces grace notes. It takes one argument, in this
774 case a chord. The slur started on the @code{e} of the chord
775 will be attached to the next note.@footnote{LilyPond will squirm
776 about unended Slurs. In this case, you can ignore the warning}.
780 Tuplets are made with the @code{\times} keyword. It takes two
781 arguments: a fraction and a piece of music. The duration of the
782 second argument is multiplied by the first argument. Triplets make
783 notes occupy 2/3 of their notated duration, so in this case the
784 fraction is 2/3. @example
785 @{ <d8 \< f> <e g> <f a> @}
787 The piece of music to be `tripletted' is sequential music containing
788 three notes. On the first chord (the @code{d}), a crescendo is started
789 with @code{\<}.@example
792 At this point, the homophonic music splits into two rhythmically
793 different parts. We can't use a sequence of chords to enter this, so
794 we make a `chord' of sequences to do it. We start with the upper
795 voice, which continues with upward stems: @example
796 @{ \times 2/3 @{ a8 g c @} \! c2 @}
798 The crescendo is ended at the half note by the escaped exclamation
799 mark `@code{\!}'. @example
800 \context Voice = oboeTwo @{
803 We can't share stems with the other voice, so we have to create a new
804 @code{Voice} context. We give it the name @code{oboeTwo} to distinguish
805 it from the other context. Stems go down in this voice. @example
808 When a grace section is processed, a @code{Grace} context is
809 created. This context acts like a miniature score of its own. It has
810 its own time bookkeeping, and you can make notes, beams, slurs
811 etc. Here fiddle with a property and make a beam. The argument of
812 @code{\grace} is sequential music.@example
813 \property Grace.verticalDirection = \down
816 Normally, grace notes are always stem up, but in this case, the upper
817 voice interferes. We set the stems down here.
819 As far as relative mode is concerned, the previous note is the
820 @code{c'''2} of the upper voice, so we have to go an octave down for
827 This ends the two-part section. @example
829 \grace <c,8( e> <)b8. d8.-\trill> <c16 e> |
831 @code{\stemboth} ends the forced stem directions. From here, stems are
832 positioned as if it were single part music.
834 The bass has a little hoom-pah melody to demonstrate parts switching
835 between staffs. Since it is repetitive, we use identifiers:@example
836 hoomPah = \notes \transpose c' @{
838 Transposing can be done with @code{\transpose}. It takes two
839 arguments; the first specifies what central C should be transposed to.
840 The second is the to-be-transposed music. As you can see, in this
841 case, the transposition is a no-op. Central C is transposed to
844 The purpose of this no-op is circumventing relative mode. Relative
845 mode can not be used in conjunction with transposition, so relative
846 mode will leave the contents of @code{\hoomPah} alone. We can use it
847 without having to worry about getting the motive in a wrong
848 octave@footnote{@code{hoomPah = \relative @dots{}} would be more
849 intuitive to use, but that would not let me plug @code{\transpose}
851 c8 \translator Staff = top \stemdown
853 We assume that the first note will be put in the lower staff. After
854 that note we switch to the upper staff with @code{\translator}. To be
855 precise, this @code{\translator} entry switches the current voice to a
856 @code{Staff} named @code{top}. So we have to name the upper staff
857 `@code{top}'. Stem directions are set to avoid interfering with the
858 oboe voices. @example
859 c'8 \translator Staff = bottom \stemup @}
861 Then a note is put on the upper staff, and we switch again. We have
862 to name the lower staff `@code{bottom}'. @example
863 hoomPahHoomPah = @{ [\hoomPah \hoomPah] @}
865 Put two of these fragments in sequence, and beam them.@example
866 bassvoices = \notes \relative c' @{
868 \hoomPahHoomPah \hoomPahHoomPah \hoomPahHoomPah
871 Entering the bass part is easy: the hoomPahHoomPah variable is
872 referenced four times.@example
873 \context Voice = reallyLow @{\stemdown g2 ~ | g4 c8 @} >
875 After skipping some lines, we see @code{~}. This mark makes ties.@example
878 For piano music, a special context is needed to get cross staff
879 beaming right. It is called @code{PianoStaff}.@example
880 \context Staff = bottom < \time 2/2; \clef bass;
882 The bottom staff must have a different clef.@example
885 To make some more room on the line, the first (in this case the only)
886 line is not indented. The line still looks is very cramped, but that is due
887 to the format of this tutorial.
889 This example shows a lot of features, but the organisation isn't
890 perfect. For example, it would be less confusing to use a chord
891 containing sequential music than a sequence of chords for the oboe
894 [TODO: demonstrate Hara-Kiri with scores and part extraction.]
896 @node end of tutorial, , , Tutorial
899 That's all folks. From here, you can either try fiddling with input
900 files, or you can read the reference manual.