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
51 @cindex organ pedal marks
52 @cindex pedal marks, organ
72 A variety of symbols that denote articulations, ornamentations,
73 and other performance indications can be attached to a note using
80 The possible values for @var{name} are listed in @ref{List of
81 articulations}. For example:
83 @lilypond[verbatim,quote,relative=2]
84 c4\staccato c\mordent b2\turn
95 Some of these articulations have shorthands for easier entry.
96 Shorthands are appended to the note name, and their syntax
97 consists of a dash @code{-} followed by a symbol signifying the
98 articulation. Predefined shorthands exist for @notation{marcato},
99 @notation{stopped}, @notation{tenuto}, @notation{staccatissimo},
100 @notation{accent}, @notation{staccato}, and @notation{portato}.
101 Their corresponding output appears as follows:
103 @lilypond[verbatim,quote,relative=2]
108 The rules for the default placement of articulations are defined
109 in @file{scm/@/script@/.scm}. Articulations and ornamentations
110 may be manually placed above or below the staff, see
111 @ref{Direction and placement}.
116 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
117 {modifying-default-values-for-articulation-shorthand-notation.ly}
119 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
120 {controlling-the-vertical-ordering-of-scripts.ly}
122 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
123 {creating-a-delayed-turn.ly}
133 @ref{Direction and placement},
134 @ref{List of articulations},
138 @file{scm/@/script@/.scm}.
141 @rlsr{Expressive marks}.
145 @rinternals{TextScript}.
149 @unnumberedsubsubsec Dynamics
151 @cindex absolute dynamics
153 @cindex dynamics, absolute
192 Absolute dynamic marks are specified using a command after a note,
193 such as @code{c4\ff}. The available dynamic marks are
194 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
195 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
196 @code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
197 @code{\spp}, @code{\sfz}, and @code{\rfz}. The dynamic marks may
198 be manually placed above or below the staff, see
199 @ref{Direction and placement}.
201 @lilypond[verbatim,quote,relative=2]
220 A @notation{crescendo} mark is started with @code{\<} and
221 terminated with @code{\!}, an absolute dynamic, or an additional
222 crescendo or decrescendo mark. A @notation{decrescendo} mark is
223 started with @code{\>} and is also terminated with @code{\!}, an
224 absolute dynamic, or another crescendo or decrescendo mark.
225 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
226 @code{\>}. @notation{Hairpins} are engraved by default using this
229 @lilypond[verbatim,quote,relative=2]
239 Spacer rests are needed to engrave multiple marks on one note.
241 @cindex multiple dynamic marks on one note
242 @cindex dynamic marks, multiple on one note
244 @lilypond[verbatim,quote,relative=2]
246 << f1 { s4 s4\< s4\> s4\! } >>
249 @cindex espressivo articulation
251 @funindex \espressivo
254 In some situations the @code{\espressivo} articulation mark may be
255 the appropriate choice to indicate a crescendo and decrescendo on
258 @lilypond[verbatim,quote,relative=2]
264 @funindex \crescTextCresc
265 @funindex crescTextCresc
266 @funindex \dimTextDecresc
267 @funindex dimTextDecresc
268 @funindex \dimTextDecr
269 @funindex dimTextDecr
270 @funindex \dimTextDim
272 @funindex \crescHairpin
273 @funindex crescHairpin
274 @funindex \dimHairpin
277 Crescendos and decrescendos can be engraved as textual markings
278 instead of hairpins. Dashed lines are printed to indicate their
279 extent. The built-in commands that enable these text modes are
280 @code{\crescTextCresc}, @code{\dimTextDecresc},
281 @code{\dimTextDecr}, and @code{\dimTextDim}. The corresponding
282 @code{\crescHairpin} and @code{\dimHairpin} commands will revert
285 @lilypond[verbatim,quote,relative=2]
297 To create new absolute dynamic marks or text that should be
298 aligned with dynamics, see @ref{New dynamic marks}.
300 @cindex dynamics, vertical positioning
301 @cindex vertical positioning of dynamics
303 @funindex DynamicLineSpanner
306 Vertical positioning of dynamics is handled by
307 @rinternals{DynamicLineSpanner}.
310 @funindex \dynamicDown
311 @funindex dynamicDown
312 @funindex \dynamicNeutral
313 @funindex dynamicNeutral
319 @code{\dynamicNeutral},
320 @code{\crescTextCresc},
323 @code{\dimTextDecresc},
324 @code{\crescHairpin},
331 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
332 {setting-hairpin-behavior-at-bar-lines.ly}
334 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
335 {setting-the-minimum-length-of-hairpins.ly}
340 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
341 {printing-hairpins-using-al-niente-notation.ly}
343 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
344 {vertically-aligned-dynamics-and-textscripts.ly}
346 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
347 {hiding-the-extender-line-for-text-dynamics.ly}
349 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
350 {changing-text-and-spanner-styles-for-text-dynamics.ly}
361 @rlearning{Articulation and dynamics}.
364 @ref{Direction and placement},
365 @ref{New dynamic marks},
366 @ref{What goes into the MIDI output?},
367 @ref{Controlling MIDI dynamics}.
370 @rlsr{Expressive marks}.
373 @rinternals{DynamicText},
374 @rinternals{Hairpin},
375 @rinternals{DynamicLineSpanner}.
378 @node New dynamic marks
379 @unnumberedsubsubsec New dynamic marks
381 @cindex new dynamic marks
382 @cindex dynamic marks, new
384 The easiest way to create dynamic indications is to use
385 @code{\markup} objects.
387 @lilypond[verbatim,quote]
388 moltoF = \markup { molto \dynamic f }
391 <d e>16_\moltoF <d e>
396 @cindex dynamics, editorial
397 @cindex dynamics, parenthesis
398 @cindex editorial dynamics
404 In markup mode, editorial dynamics (within parentheses or square
405 brackets) can be created. The syntax for markup mode is described
406 in @ref{Formatting text}.
408 @lilypond[verbatim,quote]
409 roundF = \markup { \center-align \concat { \bold { \italic ( }
410 \dynamic f \bold { \italic ) } } }
411 boxF = \markup { \bracket { \dynamic f } }
418 @cindex make-dynamic-script
419 @funindex make-dynamic-script
421 Simple, centered dynamic marks are easily created with the
422 @code{make-dynamic-script} function. The dynamic font only
423 contains the characters @code{f,m,p,r,s} and @code{z}.
425 @lilypond[verbatim,quote]
426 sfzp = #(make-dynamic-script "sfzp")
432 In general, @code{make-dynamic-script} takes any markup object as
433 its argument. In the following example, using
434 @code{make-dynamic-script} ensures the vertical alignment of
435 markup objects and hairpins that are attached to the same note
438 @lilypond[verbatim,quote]
439 roundF = \markup { \center-align \concat {
440 \normal-text { \bold { \italic ( } }
442 \normal-text { \bold { \italic ) } } } }
443 boxF = \markup { \bracket { \dynamic f } }
444 roundFdynamic = #(make-dynamic-script roundF)
445 boxFdynamic = #(make-dynamic-script boxF)
447 c4_\roundFdynamic\< d e f
452 The Scheme form of markup mode may be used instead. Its syntax is
453 explained in @ref{Markup construction in Scheme}.
455 @lilypond[verbatim,quote]
456 moltoF = #(make-dynamic-script
457 (markup #:normal-text "molto"
465 Font settings in markup mode are described in
466 @ref{Selecting font and font size}.
471 @ref{Formatting text},
472 @ref{Selecting font and font size},
473 @ref{Markup construction in Scheme},
474 @ref{What goes into the MIDI output?},
475 @ref{Controlling MIDI dynamics}.
478 @rlsr{Expressive marks}.
484 This section explains how to create various expressive marks that
485 are curved: normal slurs, phrasing slurs, breath marks, falls, and
496 @unnumberedsubsubsec Slurs
500 @notation{Slurs} are entered using parentheses:
502 @lilypond[verbatim,quote,relative=2]
508 @cindex slurs, manual placement
509 @cindex slurs, below notes
510 @cindex slurs, above notes
513 @funindex \slurNeutral
514 @funindex slurNeutral
516 Slurs may be manually placed above or below the notes, see
517 @ref{Direction and placement}.
519 @lilypond[verbatim,quote,relative=2]
527 @cindex phrasing slur
528 @cindex multiple slurs
529 @cindex simultaneous slurs
530 @cindex slur, phrasing
531 @cindex slurs, multiple
532 @cindex slurs, simultaneous
534 Simultaneous or overlapping slurs are not permitted, but a phrasing
535 slur can overlap a slur. This permits two slurs to be printed at
536 once. For details, see @ref{Phrasing slurs}.
549 @funindex \slurDashed
551 @funindex \slurDotted
556 Slurs can be solid, dotted, or dashed. Solid is the default slur
559 @lilypond[verbatim,quote,relative=1]
585 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
586 {using-double-slurs-for-legato-chords.ly}
588 @c TODO remove ignores after LSR update
590 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
591 {positioning-text-markups-inside-slurs}
599 @rlearning{On the un-nestedness of brackets and ties}.
602 @ref{Direction and placement},
603 @ref{Phrasing slurs}.
606 @rlsr{Expressive marks}.
613 @unnumberedsubsubsec Phrasing slurs
615 @cindex phrasing slurs
616 @cindex phrasing marks
617 @cindex slur, phrasing
618 @cindex mark, phrasing
622 @notation{Phrasing slurs} (or phrasing marks) that indicate a
623 musical sentence are written using the commands @code{\(} and
624 @code{\)} respectively:
626 @lilypond[verbatim,quote,relative=2]
631 @funindex \phrasingSlurUp
632 @funindex phrasingSlurUp
633 @funindex \phrasingSlurDown
634 @funindex phrasingSlurDown
635 @funindex \phrasingSlurNeutral
636 @funindex phrasingSlurNeutral
637 @funindex phrasingSlurDashed
638 @funindex \phrasingSlurDashed
639 @funindex \phrasingSlurDotted
640 @funindex phrasingSlurDotted
641 @funindex \phrasingSlurSolid
642 @funindex phrasingSlurSolid
644 Typographically, a phrasing slur behaves almost exactly like a
645 normal slur. However, they are treated as different objects; a
646 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
647 slurs may be manually placed above or below the notes, see
648 @ref{Direction and placement}.
650 @lilypond[verbatim,quote,relative=1]
651 c4\( g' c,( b) | c1\)
653 c4\( g' c,( b) | c1\)
656 @cindex simultaneous phrasing slurs
657 @cindex multiple phrasing slurs
658 @cindex slurs, simultaneous phrasing
659 @cindex slurs, multiple phrasing
660 @cindex phrasing slurs, simultaneous
661 @cindex phrasing slurs, multiple
663 Simultaneous or overlapping phrasing slurs are not permitted.
665 Phrasing slurs can be solid, dotted, or dashed. Solid is the default
666 style for phrasing slurs:
668 @lilypond[verbatim,quote,relative=1]
680 @code{\phrasingSlurUp},
681 @code{\phrasingSlurDown},
682 @code{\phrasingSlurNeutral},
683 @code{\phrasingSlurDashed},
684 @code{\phrasingSlurDotted},
685 @code{\phrasingSlurSolid}.
691 @rlearning{On the un-nestedness of brackets and ties}.
694 @ref{Direction and placement}.
697 @rlsr{Expressive marks}.
700 @rinternals{PhrasingSlur}.
704 @unnumberedsubsubsec Breath marks
711 Breath marks are entered using @code{\breathe}:
713 @lilypond[verbatim,quote,relative=2]
717 Musical indicators for breath marks in ancient notation,
718 divisiones, are supported. For details, see @ref{Divisiones}.
723 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
724 {changing-the-breath-mark-symbol.ly}
727 @cindex railroad tracks
729 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
730 {inserting-a-caesura.ly}
741 @rlsr{Expressive marks}.
744 @rinternals{BreathingSign}.
747 @node Falls and doits
748 @unnumberedsubsubsec Falls and doits
755 @notation{Falls} and @notation{doits} can be added to notes using
756 the @code{\bendAfter} command. The direction of the fall or doit
757 is indicated with a plus or minus (up or down). The number
758 indicates the pitch interval that the fall or doit will extend
759 @emph{beyond} the main note.
761 @lilypond[verbatim,quote,relative=2]
768 The dash @code{-} immediately preceding the @code{\bendAfter}
769 command is @emph{required} when writing falls and doits.
774 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
775 {adjusting-the-shape-of-falls-and-doits.ly}
784 @rlsr{Expressive marks}.
790 This section explains how to create various expressive marks that
791 follow a linear path: glissandos, arpeggios, and trills.
800 @unnumberedsubsubsec Glissando
806 A @notation{glissando} is created by attaching @code{\glissando}
809 @lilypond[verbatim,quote,relative=2]
814 Different styles of glissandi can be created. For details, see
819 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
820 {contemporary-glissando.ly}
831 @rlsr{Expressive marks}.
834 @rinternals{Glissando}.
839 Printing text over the line (such as @notation{gliss.}) is not
844 @unnumberedsubsubsec Arpeggio
848 @cindex chord, broken
852 @funindex \arpeggioArrowUp
853 @funindex arpeggioArrowUp
854 @funindex \arpeggioArrowDown
855 @funindex arpeggioArrowDown
856 @funindex \arpeggioNormal
857 @funindex arpeggioNormal
859 An @notation{arpeggio} on a chord (also known as a broken chord)
860 is denoted by appending @code{\arpeggio} to the chord construct:
862 @lilypond[verbatim,quote,relative=1]
866 Different types of arpeggios may be written.
867 @code{\arpeggioNormal} reverts to a normal arpeggio:
869 @lilypond[verbatim,quote,relative=1]
879 @cindex arpeggio symbols, special
880 @cindex special arpeggio symbols
882 @funindex \arpeggioBracket
883 @funindex arpeggioBracket
884 @funindex \arpeggioParenthesis
885 @funindex arpeggioParenthesis
887 Special @emph{bracketed} arpeggio symbols can be created:
889 @lilypond[verbatim,quote,relative=1]
899 Arpeggios can be explicitly written out with ties. For more
900 information, see @ref{Ties}.
905 @code{\arpeggioArrowUp},
906 @code{\arpeggioArrowDown},
907 @code{\arpeggioNormal},
908 @code{\arpeggioBracket},
909 @code{\arpeggioParenthesis}.
915 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
916 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
918 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
919 {creating-cross-staff-arpeggios-in-other-contexts.ly}
921 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
922 {creating-arpeggios-across-notes-in-different-voices.ly}
933 @rlsr{Expressive marks}.
936 @rinternals{Arpeggio},
937 @rinternals{PianoStaff}.
942 @cindex cross-staff parenthesis-style arpeggio
943 @cindex arpeggio, parenthesis-style, cross-staff
944 @cindex arpeggio, cross-staff parenthesis-style
946 It is not possible to mix connected arpeggios and unconnected
947 arpeggios in one @code{PianoStaff} at the same point in
950 The parenthesis-style arpeggio brackets do not work for
951 cross-staff arpeggios.
955 @unnumberedsubsubsec Trills
961 @funindex \startTrillSpan
962 @funindex startTrillSpan
963 @funindex \stopTrillSpan
964 @funindex stopTrillSpan
966 Short @notation{trills} without an extender line are printed with
967 @code{\trill}; see @ref{Articulations and ornamentations}.
969 Longer trills with an extender line are made with
970 @code{\startTrillSpan} and @code{\stopTrillSpan}:
972 @lilypond[verbatim,quote,relative=2]
978 In the following example, a trill is combined with grace notes.
979 The syntax of this construct and the method to precisely position
980 the grace notes are described in @ref{Grace notes}.
982 @lilypond[verbatim,quote,relative=2]
984 d1\startTrillSpan { c32[ d]\stopTrillSpan }
988 @cindex pitched trills
989 @cindex trills, pitched
990 @funindex \pitchedTrill
991 @funindex pitchedTrill
993 Trills that require an auxiliary note with an explicit pitch can
994 be typeset with the @code{\pitchedTrill} command. The first
995 argument is the main note, and the second is the @emph{trilled}
996 note, printed as a stemless note head in parentheses.
998 @lilypond[verbatim,quote,relative=1]
999 \pitchedTrill e2\startTrillSpan fis
1003 @cindex pitched trill with forced accidental
1004 @cindex trill, pitched with forced accidental
1005 @cindex accidental, forced for pitched trill
1007 In the following example, the second pitched trill is ambiguous;
1008 the accidental of the trilled note is not printed. As a
1009 workaround, the accidentals of the trilled notes can be forced.
1010 The second measure illustrates this method:
1012 @lilypond[verbatim,quote,relative=2]
1013 \pitchedTrill eis4\startTrillSpan fis
1015 \pitchedTrill eis4\startTrillSpan fis
1017 \pitchedTrill eis4\startTrillSpan fis
1019 \pitchedTrill eis4\startTrillSpan fis!
1025 @code{\startTrillSpan},
1026 @code{\stopTrillSpan}.
1035 @ref{Articulations and ornamentations},
1039 @rlsr{Expressive marks}.
1041 Internals Reference:
1042 @rinternals{TrillSpanner}.