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.
424 @lilypond[verbatim,quote]
425 sfzp = #(make-dynamic-script "sfzp")
431 In general, @code{make-dynamic-script} takes any markup object as its
432 argument. The dynamic font only contains the characters
433 @code{f,m,p,r,s} and @code{z}, so if a dynamic mark that includes
434 plain text or punctuation symbols is desired, markup commands that
435 reverts font family and font encoding to normal text should be used,
436 for example @code{\normal-text}. The interest of using
437 @code{make-dynamic-script} instead of an ordinary markup is ensuring
438 the vertical alignment of markup objects and hairpins that are
439 attached to the same note head.
441 @lilypond[verbatim,quote]
442 roundF = \markup { \center-align \concat {
443 \normal-text { \bold { \italic ( } }
445 \normal-text { \bold { \italic ) } } } }
446 boxF = \markup { \bracket { \dynamic f } }
447 mfEspress = \markup { \center-align \line {
448 \hspace #3.7 mf \normal-text \italic espress. } }
449 roundFdynamic = #(make-dynamic-script roundF)
450 boxFdynamic = #(make-dynamic-script boxF)
451 mfEspressDynamic = #(make-dynamic-script mfEspress)
453 c4_\roundFdynamic\< d e f
461 The Scheme form of markup mode may be used instead. Its syntax is
462 explained in @ref{Markup construction in Scheme}.
464 @lilypond[verbatim,quote]
465 moltoF = #(make-dynamic-script
466 (markup #:normal-text "molto"
474 Font settings in markup mode are described in
475 @ref{Selecting font and font size}.
480 @ref{Formatting text},
481 @ref{Selecting font and font size},
482 @ref{Markup construction in Scheme},
483 @ref{What goes into the MIDI output?},
484 @ref{Controlling MIDI dynamics}.
487 @rlsr{Expressive marks}.
493 This section explains how to create various expressive marks that
494 are curved: normal slurs, phrasing slurs, breath marks, falls, and
505 @unnumberedsubsubsec Slurs
509 @notation{Slurs} are entered using parentheses:
511 @lilypond[verbatim,quote,relative=2]
517 @cindex slurs, manual placement
518 @cindex slurs, below notes
519 @cindex slurs, above notes
522 @funindex \slurNeutral
523 @funindex slurNeutral
525 Slurs may be manually placed above or below the notes, see
526 @ref{Direction and placement}.
528 @lilypond[verbatim,quote,relative=2]
536 @cindex phrasing slur
537 @cindex multiple slurs
538 @cindex simultaneous slurs
539 @cindex slur, phrasing
540 @cindex slurs, multiple
541 @cindex slurs, simultaneous
543 Simultaneous or overlapping slurs are not permitted, but a phrasing
544 slur can overlap a slur. This permits two slurs to be printed at
545 once. For details, see @ref{Phrasing slurs}.
558 @funindex \slurDashed
560 @funindex \slurDotted
565 Slurs can be solid, dotted, or dashed. Solid is the default slur
568 @lilypond[verbatim,quote,relative=1]
578 @funindex \slurHalfDashed
579 @funindex slurHalfDashed
580 @funindex \slurHalfSolid
581 @funindex slurHalfSolid
583 Slurs can also be made half-dashed (the first half dashed, the
584 second half solid) or half-solid (the first half solid, the second
587 @lilypond[verbatim,quote,relative=1]
596 Custom dash patterns for slurs can be defined:
598 @lilypond[verbatim,quote,relative=1]
599 \slurDashPattern #0.7 #0.75
601 \slurDashPattern #0.5 #2.0
619 @code{\slurHalfDashed},
620 @code{\slurHalfSolid},
621 @code{\slurDashPattern},
628 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
629 {using-double-slurs-for-legato-chords.ly}
631 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
632 {positioning-text-markups-inside-slurs.ly}
634 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
635 {making-slurs-with-complex-dash-structure.ly}
642 @rlearning{On the un-nestedness of brackets and ties}.
645 @ref{Direction and placement},
646 @ref{Phrasing slurs}.
649 @rlsr{Expressive marks}.
656 @unnumberedsubsubsec Phrasing slurs
658 @cindex phrasing slurs
659 @cindex phrasing marks
660 @cindex slur, phrasing
661 @cindex mark, phrasing
665 @notation{Phrasing slurs} (or phrasing marks) that indicate a
666 musical sentence are written using the commands @code{\(} and
667 @code{\)} respectively:
669 @lilypond[verbatim,quote,relative=2]
674 @funindex \phrasingSlurUp
675 @funindex phrasingSlurUp
676 @funindex \phrasingSlurDown
677 @funindex phrasingSlurDown
678 @funindex \phrasingSlurNeutral
679 @funindex phrasingSlurNeutral
681 Typographically, a phrasing slur behaves almost exactly like a
682 normal slur. However, they are treated as different objects; a
683 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
684 slurs may be manually placed above or below the notes, see
685 @ref{Direction and placement}.
687 @lilypond[verbatim,quote,relative=1]
688 c4\( g' c,( b) | c1\)
690 c4\( g' c,( b) | c1\)
693 @cindex simultaneous phrasing slurs
694 @cindex multiple phrasing slurs
695 @cindex slurs, simultaneous phrasing
696 @cindex slurs, multiple phrasing
697 @cindex phrasing slurs, simultaneous
698 @cindex phrasing slurs, multiple
700 Simultaneous or overlapping phrasing slurs are not permitted.
702 @funindex phrasingSlurDashed
703 @funindex \phrasingSlurDashed
704 @funindex \phrasingSlurDotted
705 @funindex phrasingSlurDotted
706 @funindex \phrasingSlurSolid
707 @funindex phrasingSlurSolid
709 Phrasing slurs can be solid, dotted, or dashed. Solid is the default
710 style for phrasing slurs:
712 @lilypond[verbatim,quote,relative=1]
722 @funindex phrasingSlurHalfDashed
723 @funindex \phrasingSlurHalfDashed
724 @funindex \phrasingSlurHalfSolid
725 @funindex phrasingSlurHalfSolid
727 Phrasing slurs can also be made half-dashed (the first half dashed, the
728 second half solid) or half-solid (the first half solid, the second
731 @lilypond[verbatim,quote,relative=1]
732 \phrasingSlurHalfDashed
734 \phrasingSlurHalfSolid
740 @funindex \phrasingSlurDashPattern
741 @funindex phrasingSlurDashPattern
744 Custom dash patterns for phrasing slurs can be defined:
746 @lilypond[verbatim,quote,relative=1]
747 \phrasingSlurDashPattern #0.7 #0.75
749 \phrasingSlurDashPattern #0.5 #2.0
755 Dash pattern definitions for phrasing slurs have the same structure
756 as dash pattern definitions for slurs. For more information about
757 complex dash patterns, see the snippets under @ref{Slurs}.
760 @code{\phrasingSlurUp},
761 @code{\phrasingSlurDown},
762 @code{\phrasingSlurNeutral},
763 @code{\phrasingSlurDashed},
764 @code{\phrasingSlurDotted},
765 @code{\phrasingSlurHalfDashed},
766 @code{\phrasingSlurHalfSolid},
767 @code{\phrasingSlurDashPattern},
768 @code{\phrasingSlurSolid}.
774 @rlearning{On the un-nestedness of brackets and ties}.
777 @ref{Direction and placement},
781 @rlsr{Expressive marks}.
784 @rinternals{PhrasingSlur}.
788 @unnumberedsubsubsec Breath marks
795 Breath marks are entered using @code{\breathe}:
797 @lilypond[verbatim,quote,relative=2]
801 Musical indicators for breath marks in ancient notation,
802 divisiones, are supported. For details, see @ref{Divisiones}.
807 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
808 {changing-the-breath-mark-symbol.ly}
811 @cindex railroad tracks
813 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
814 {inserting-a-caesura.ly}
825 @rlsr{Expressive marks}.
828 @rinternals{BreathingSign}.
831 @node Falls and doits
832 @unnumberedsubsubsec Falls and doits
839 @notation{Falls} and @notation{doits} can be added to notes using
840 the @code{\bendAfter} command. The direction of the fall or doit
841 is indicated with a plus or minus (up or down). The number
842 indicates the pitch interval that the fall or doit will extend
843 @emph{beyond} the main note.
845 @lilypond[verbatim,quote,relative=2]
852 The dash @code{-} immediately preceding the @code{\bendAfter}
853 command is @emph{required} when writing falls and doits.
858 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
859 {adjusting-the-shape-of-falls-and-doits.ly}
868 @rlsr{Expressive marks}.
874 This section explains how to create various expressive marks that
875 follow a linear path: glissandos, arpeggios, and trills.
884 @unnumberedsubsubsec Glissando
890 A @notation{glissando} is created by attaching @code{\glissando}
893 @lilypond[verbatim,quote,relative=2]
898 Different styles of glissandi can be created. For details, see
903 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
904 {contemporary-glissando.ly}
915 @rlsr{Expressive marks}.
918 @rinternals{Glissando}.
923 Printing text over the line (such as @notation{gliss.}) is not
928 @unnumberedsubsubsec Arpeggio
932 @cindex chord, broken
936 @funindex \arpeggioArrowUp
937 @funindex arpeggioArrowUp
938 @funindex \arpeggioArrowDown
939 @funindex arpeggioArrowDown
940 @funindex \arpeggioNormal
941 @funindex arpeggioNormal
943 An @notation{arpeggio} on a chord (also known as a broken chord)
944 is denoted by appending @code{\arpeggio} to the chord construct:
946 @lilypond[verbatim,quote,relative=1]
950 Different types of arpeggios may be written.
951 @code{\arpeggioNormal} reverts to a normal arpeggio:
953 @lilypond[verbatim,quote,relative=1]
963 @cindex arpeggio symbols, special
964 @cindex special arpeggio symbols
966 @funindex \arpeggioBracket
967 @funindex arpeggioBracket
968 @funindex \arpeggioParenthesis
969 @funindex arpeggioParenthesis
971 Special @emph{bracketed} arpeggio symbols can be created:
973 @lilypond[verbatim,quote,relative=1]
983 Arpeggios can be explicitly written out with ties. For more
984 information, see @ref{Ties}.
989 @code{\arpeggioArrowUp},
990 @code{\arpeggioArrowDown},
991 @code{\arpeggioNormal},
992 @code{\arpeggioBracket},
993 @code{\arpeggioParenthesis}.
999 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1000 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
1002 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1003 {creating-cross-staff-arpeggios-in-other-contexts.ly}
1005 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1006 {creating-arpeggios-across-notes-in-different-voices.ly}
1017 @rlsr{Expressive marks}.
1019 Internals Reference:
1020 @rinternals{Arpeggio},
1021 @rinternals{PianoStaff}.
1026 @cindex cross-staff parenthesis-style arpeggio
1027 @cindex arpeggio, parenthesis-style, cross-staff
1028 @cindex arpeggio, cross-staff parenthesis-style
1030 It is not possible to mix connected arpeggios and unconnected
1031 arpeggios in one @code{PianoStaff} at the same point in
1034 The parenthesis-style arpeggio brackets do not work for
1035 cross-staff arpeggios.
1039 @unnumberedsubsubsec Trills
1045 @funindex \startTrillSpan
1046 @funindex startTrillSpan
1047 @funindex \stopTrillSpan
1048 @funindex stopTrillSpan
1050 Short @notation{trills} without an extender line are printed with
1051 @code{\trill}; see @ref{Articulations and ornamentations}.
1053 Longer trills with an extender line are made with
1054 @code{\startTrillSpan} and @code{\stopTrillSpan}:
1056 @lilypond[verbatim,quote,relative=2]
1062 In the following example, a trill is combined with grace notes.
1063 The syntax of this construct and the method to precisely position
1064 the grace notes are described in @ref{Grace notes}.
1066 @lilypond[verbatim,quote,relative=2]
1068 d1\startTrillSpan { c32[ d]\stopTrillSpan }
1072 @cindex pitched trills
1073 @cindex trills, pitched
1074 @funindex \pitchedTrill
1075 @funindex pitchedTrill
1077 Trills that require an auxiliary note with an explicit pitch can
1078 be typeset with the @code{\pitchedTrill} command. The first
1079 argument is the main note, and the second is the @emph{trilled}
1080 note, printed as a stemless note head in parentheses.
1082 @lilypond[verbatim,quote,relative=1]
1083 \pitchedTrill e2\startTrillSpan fis
1087 @cindex pitched trill with forced accidental
1088 @cindex trill, pitched with forced accidental
1089 @cindex accidental, forced for pitched trill
1091 In the following example, the second pitched trill is ambiguous;
1092 the accidental of the trilled note is not printed. As a
1093 workaround, the accidentals of the trilled notes can be forced.
1094 The second measure illustrates this method:
1096 @lilypond[verbatim,quote,relative=2]
1097 \pitchedTrill eis4\startTrillSpan fis
1099 \pitchedTrill eis4\startTrillSpan fis
1101 \pitchedTrill eis4\startTrillSpan fis
1103 \pitchedTrill eis4\startTrillSpan fis!
1109 @code{\startTrillSpan},
1110 @code{\stopTrillSpan}.
1119 @ref{Articulations and ornamentations},
1123 @rlsr{Expressive marks}.
1125 Internals Reference:
1126 @rinternals{TrillSpanner}.