1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. See TRANSLATION for details.
11 @node Expressive marks
12 @section Expressive marks
14 @lilypondfile[quote]{expressive-headword.ly}
16 This section lists various expressive marks that can be
26 @node Attached to notes
27 @subsection Attached to notes
29 This section explains how to create expressive marks that are
30 attached to notes: articulations, ornamentations, and dynamics.
31 Methods to create new dynamic markings are also discussed.
34 * Articulations and ornamentations::
39 @node Articulations and ornamentations
40 @unnumberedsubsubsec Articulations and ornamentations
50 @cindex organ pedal marks
68 A variety of symbols that denote articulations, ornamentations,
69 and other performance indications can be attached to a note using
76 The possible values for @var{name} are listed in @ref{List of
77 articulations}. For example:
79 @lilypond[verbatim,quote,relative=2]
80 c4\staccato c\mordent b2\turn
92 Some of these articulations have shorthands for easier entry.
93 Shorthands are appended to the note name, and their syntax
94 consists of a dash @code{-} followed by a symbol signifying the
95 articulation. Predefined shorthands exist for @notation{marcato},
96 @notation{stopped}, @notation{tenuto}, @notation{staccatissimo},
97 @notation{accent}, @notation{staccato}, and @notation{portato}.
98 Their corresponding output appears as follows:
100 @lilypond[verbatim,quote,relative=2]
105 The rules for the default placement of articulations are defined
106 in @file{scm/@/script@/.scm}. Articulations and ornamentations
107 may be manually placed above or below the staff, see
108 @ref{Direction and placement}.
113 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
114 {modifying-default-values-for-articulation-shorthand-notation.ly}
116 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
117 {controlling-the-vertical-ordering-of-scripts.ly}
129 @ref{Direction and placement},
130 @ref{List of articulations}.
133 @file{scm/@/script@/.scm}.
136 @rlsr{Expressive marks}.
140 @rinternals{TextScript}.
144 @unnumberedsubsubsec Dynamics
146 @cindex absolute dynamics
148 @cindex dynamics, absolute
168 Absolute dynamic marks are specified using a command after a note,
169 such as @code{c4\ff}. The available dynamic marks are
170 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
171 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
172 @code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
173 @code{\spp}, @code{\sfz}, and @code{\rfz}. The dynamic marks may
174 be manually placed above or below the staff, see
175 @ref{Direction and placement}.
177 @lilypond[verbatim,quote,relative=2]
190 A @notation{crescendo} mark is started with @code{\<} and
191 terminated with @code{\!}, an absolute dynamic, or an additional
192 crescendo or decrescendo mark. A @notation{decrescendo} mark is
193 started with @code{\>} and is also terminated with @code{\!}, an
194 absolute dynamic, or another crescendo or decrescendo mark.
195 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
196 @code{\>}. @notation{Hairpins} are engraved by default using this
199 @lilypond[verbatim,quote,relative=2]
209 Spacer rests are needed to engrave multiple marks on one note.
211 @lilypond[verbatim,quote,relative=2]
213 << f1 { s4 s4\< s4\> s4\! } >>
216 @cindex espressivo articulation
218 In some situations the @code{\espressivo} articulation mark may be
219 the appropriate choice to indicate a crescendo and decrescendo on
222 @lilypond[verbatim,quote,relative=2]
231 Crescendos and decrescendos can be engraved as textual markings
232 instead of hairpins. The built-in commands that enable these text
233 modes are @code{\crescTextCresc}, @code{\dimTextDecresc},
234 @code{\dimTextDecr}, and @code{\dimTextDim}. The corresponding
235 @code{\crescHairpin} and @code{\dimHairpin} commands will revert to
238 @lilypond[verbatim,quote,relative=2]
249 To create new absolute dynamic marks or text that should be
250 aligned with dynamics, see @ref{New dynamic marks}.
252 Vertical positioning of dynamics is handled by
253 @rinternals{DynamicLineSpanner}.
260 @funindex \dynamicDown
262 @funindex \dynamicNeutral
263 @code{\dynamicNeutral},
264 @funindex \crescTextCresc
265 @code{\crescTextCresc},
266 @funindex \dimTextDim
268 @funindex \dimTextDecr
270 @funindex \dimTextDecresc
271 @code{\dimTextDecresc},
272 @funindex \crescHairpin
273 @code{\crescHairpin},
274 @funindex \dimHairpin
280 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
281 {setting-hairpin-behavior-at-bar-lines.ly}
283 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
284 {setting-the-minimum-length-of-hairpins.ly}
289 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
290 {printing-hairpins-using-al-niente-notation.ly}
292 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
293 {vertically-aligning-dynamics-across-multiple-notes.ly}
295 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
296 {hiding-the-extender-line-for-text-dynamics.ly}
298 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
299 {changing-text-and-spanner-styles-for-text-dynamics.ly}
304 @c TODO: Add hairpin to glossary.
311 @rlearning{Articulation and dynamics}.
314 @ref{Direction and placement},
315 @ref{New dynamic marks}.
318 @rlsr{Expressive marks}.
321 @rinternals{DynamicText},
322 @rinternals{Hairpin},
323 @rinternals{DynamicLineSpanner}.
326 @node New dynamic marks
327 @unnumberedsubsubsec New dynamic marks
329 @cindex new dynamic marks
330 @cindex dynamic marks, new
332 The easiest way to create dynamic indications is to use
333 @code{\markup} objects.
335 @lilypond[verbatim,quote]
336 moltoF = \markup { molto \dynamic f }
344 @cindex dynamics, editorial
345 @cindex dynamics, parenthesis
347 In markup mode, editorial dynamics (within parentheses or square
348 brackets) can be created. The syntax for markup mode is described
349 in @ref{Formatting text}.
351 @lilypond[verbatim,quote]
352 roundf = \markup { \center-align { \line { \bold { \italic ( }
353 \dynamic f \bold { \italic ) } } } }
354 boxf = \markup { \bracket { \dynamic f } }
361 By default, markup objects are aligned to the left side of a note
362 head, but authentic dynamic marks are always centered on the note
363 head. New, centered dynamic marks can be created using the
366 @cindex make-dynamic-script
368 @lilypond[verbatim,quote]
369 sfzp = #(make-dynamic-script "sfzp")
376 The dynamic font only contains the characters @code{f,m,p,r,s} and
377 @code{z}. In order to use other font families, it is necessary to
378 use markup mode in its Scheme form, as explained in
379 @ref{Markup construction in Scheme}.
381 @lilypond[verbatim,quote]
382 moltoF = #(make-dynamic-script (markup
383 #:normal-text "molto"
392 Font settings in markup mode are described in
393 @ref{Common markup commands}.
399 @ref{Formatting text},
400 @ref{Common markup commands},
401 @ref{Markup construction in Scheme}.
404 @rlsr{Expressive marks}.
410 This section explains how to create various expressive marks that
411 are curved: normal slurs, phrasing slurs, breath marks, falls, and
422 @unnumberedsubsubsec Slurs
426 @notation{Slurs} are entered using parentheses:
428 @lilypond[verbatim,quote,relative=2]
434 Slurs may be manually placed above or below the notes, see
435 @ref{Direction and placement}.
437 @lilypond[verbatim,quote,relative=2]
445 Phrasing slurs must be used to print more than one slur at once.
446 For details, see @ref{Phrasing slurs}.
448 Slurs can be solid, dotted, or dashed. Solid is the default slur
451 @lilypond[verbatim,quote,relative=1]
468 @funindex \slurNeutral
470 @funindex \slurDashed
472 @funindex \slurDotted
480 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
481 {using-double-slurs-for-legato-chords.ly}
490 @ref{Direction and placement},
491 @ref{Phrasing slurs}.
494 @rlsr{Expressive marks}.
501 @unnumberedsubsubsec Phrasing slurs
503 @cindex phrasing slurs
504 @cindex phrasing marks
508 @notation{Phrasing slurs} (or phrasing marks) that indicate a
509 musical sentence are written using the commands @code{\(} and
510 @code{\)} respectively:
512 @lilypond[verbatim,quote,relative=2]
517 Typographically, a phrasing slur behaves almost exactly like a
518 normal slur. However, they are treated as different objects; a
519 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
520 slurs may be manually placed above or below the notes, see
521 @ref{Direction and placement}.
523 @lilypond[verbatim,quote,relative=1]
524 c4\( g' c,( b) | c1\)
526 c4\( g' c,( b) | c1\)
529 Simultaneous phrasing slurs are not permitted.
534 @funindex \phrasingSlurUp
535 @code{\phrasingSlurUp},
536 @funindex \phrasingSlurDown
537 @code{\phrasingSlurDown},
538 @funindex \phrasingSlurNeutral
539 @code{\phrasingSlurNeutral}.
545 @ref{Direction and placement}.
548 @rlsr{Expressive marks}.
551 @rinternals{PhrasingSlur}.
555 @unnumberedsubsubsec Breath marks
560 Breath marks are entered using @code{\breathe}:
562 @lilypond[verbatim,quote,relative=2]
566 Musical indicators for breath marks in ancient notation,
567 divisiones, are supported. For details, see @ref{Divisiones}.
572 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
573 {changing-the-breath-mark-symbol.ly}
576 @cindex railroad tracks
578 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
579 {inserting-a-caesura.ly}
588 @rlsr{Expressive marks}.
589 @c @lsr{expressive,breathing-sign.ly}.
592 @rinternals{BreathingSign}.
595 @node Falls and doits
596 @unnumberedsubsubsec Falls and doits
602 @notation{Falls} and @notation{doits} can be added to notes using
603 the @code{\bendAfter} command. The direction of the fall or doit
604 is indicated with a plus or minus (up or down). The number
605 indicates the pitch interval that the fall or doit will extend
606 @emph{beyond} the main note.
608 @lilypond[verbatim,quote,relative=2]
615 The dash @code{-} immediately preceding the @code{\bendAfter}
616 command is @emph{required} when writing falls and doits.
621 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
622 {adjusting-the-shape-of-falls-and-doits.ly}
627 @c TODO: add falls and doits to glossary.
633 @rlsr{Expressive marks}.
639 This section explains how to create various expressive marks that
640 follow a linear path: glissandos, arpeggios, and trills.
649 @unnumberedsubsubsec Glissando
654 A @notation{glissando} is created by attaching @code{\glissando}
657 @lilypond[verbatim,quote,relative=2]
662 Different styles of glissandi can be created. For details, see
667 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
668 {contemporary-glissando.ly}
680 @rlsr{Expressive marks}.
682 @c FIXME: I need to figure out what's up with these. -gp
683 @c @lsr{expressive,glissando.ly},
684 @c @lsr{expressive,line-styles.ly}
687 @rinternals{Glissando}.
692 Printing text over the line (such as @emph{gliss.}) is not
697 @unnumberedsubsubsec Arpeggio
701 @cindex chord, broken
703 An @notation{arpeggio} on a chord (also known as a broken chord)
704 is denoted by appending @code{\arpeggio} to the chord construct:
706 @lilypond[verbatim,quote,relative=1]
710 Different types of arpeggios may be written.
711 @code{\arpeggioNormal} reverts to a normal arpeggio:
713 @lilypond[verbatim,quote,relative=1]
723 Special @emph{bracketed} arpeggio symbols can be created:
725 @lilypond[verbatim,quote,relative=1]
735 Arpeggios can be explicitly written out with ties. For more
736 information, see @ref{Ties}.
742 @funindex \arpeggioArrowUp
743 @code{\arpeggioArrowUp},
744 @funindex \arpeggioArrowDown
745 @code{\arpeggioArrowDown},
746 @funindex \arpeggioNormal
747 @code{\arpeggioNormal},
748 @funindex \arpeggioBracket
749 @code{\arpeggioBracket},
750 @funindex \arpeggioParenthesis
751 @code{\arpeggioParenthesis}.
756 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
757 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
759 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
760 {creating-cross-staff-arpeggios-in-other-contexts.ly}
762 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
763 {creating-arpeggios-across-notes-in-different-voices.ly}
775 @rlsr{Expressive marks}.
778 @rinternals{Arpeggio},
779 @rinternals{PianoStaff}.
784 It is not possible to mix connected arpeggios and unconnected
785 arpeggios in one @code{PianoStaff} at the same point in
788 The parenthesis-style arpeggio brackets do not work for
789 cross-staff arpeggios.
793 @unnumberedsubsubsec Trills
798 Short @notation{trills} without an extender line are printed with
799 @code{\trill}; see @ref{Articulations and ornamentations}.
801 Longer trills with an extender line are made with
802 @code{\startTrillSpan} and @code{\stopTrillSpan}. In the
803 following example, the trill is combined with grace notes. To
804 achieve precise control over the placement of the grace notes, see
807 @lilypond[verbatim,quote,relative=2]
809 d1\startTrillSpan { c32[ d]\stopTrillSpan }
813 @cindex pitched trills
814 @cindex trills, pitched
816 Trills that require an auxiliary note with an explicit pitch can
817 be typeset with the @code{\pitchedTrill} command. The first
818 argument is the main note, and the second is the @emph{trilled}
819 note, printed as a stemless note head in parentheses.
821 @c This syntax example doesn't look nice. -pm
824 @c @code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
825 @c @var{trillnote} @var{endnote} @code{\stopTrillSpan}
828 @lilypond[verbatim,quote,relative=1]
829 \pitchedTrill e2\startTrillSpan fis
833 In the following example, the second pitched trill is ambiguous;
834 the accidental of the trilled note is not printed. As a
835 workaround, the accidentals of the trilled notes can be forced.
836 The second measure illustrates this method:
838 @lilypond[verbatim,quote,relative=2]
839 \pitchedTrill eis4\startTrillSpan fis
841 \pitchedTrill eis4\startTrillSpan fis
843 \pitchedTrill eis4\startTrillSpan fis
845 \pitchedTrill eis4\startTrillSpan fis!
852 @funindex \startTrillSpan
853 @code{\startTrillSpan},
854 @funindex \stopTrillSpan
855 @code{\stopTrillSpan}.
864 @ref{Articulations and ornamentations},
868 @rlsr{Expressive marks}.
871 @rinternals{TrillSpanner}.