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 (@tie{}@code{-}) followed by a symbol
95 signifying the articulation. Predefined shorthands exist for
96 @notation{marcato}, @notation{stopped}, @notation{tenuto},
97 @notation{staccatissimo}, @notation{accent}, @notation{staccato},
98 and @notation{portato}. Their corresponding output appears as
101 @lilypond[verbatim,quote,relative=2]
106 The rules for the default placement of articulations are defined
107 in @file{scm/@/script@/.scm}. Articulations and ornamentations
108 may be manually placed above or below the staff, see
109 @ref{Direction and placement}.
114 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
115 {modifying-default-values-for-articulation-shorthand-notation.ly}
117 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
118 {controlling-the-vertical-ordering-of-scripts.ly}
130 @ref{Direction and placement},
131 @ref{List of articulations}.
134 @file{scm/@/script@/.scm}.
137 @rlsr{Expressive marks}.
141 @rinternals{TextScript}.
146 These signs appear in the printed output but have no effect on the
147 MIDI rendering of the music.
151 @unnumberedsubsubsec Dynamics
153 @cindex absolute dynamics
155 @cindex dynamics, absolute
175 Absolute dynamic marks are specified using a command after a note,
176 such as @code{c4\ff}. The available dynamic marks are
177 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
178 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
179 @code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
180 @code{\spp}, @code{\sfz}, and @code{\rfz}. The dynamic marks may
181 be manually placed above or below the staff, see
182 @ref{Direction and placement}.
184 @lilypond[verbatim,quote,relative=2]
197 A @notation{crescendo} mark is started with @code{\<} and
198 terminated with @code{\!}, an absolute dynamic, or an additional
199 crescendo or decrescendo mark. A @notation{decrescendo} mark is
200 started with @code{\>} and is also terminated with @code{\!}, an
201 absolute dynamic, or another crescendo or decrescendo mark.
202 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
203 @code{\>}. @notation{Hairpins} are engraved by default using this
206 @lilypond[verbatim,quote,relative=2]
216 Spacer rests are needed to engrave multiple marks on one note.
218 @lilypond[verbatim,quote,relative=2]
220 << f1 { s4 s4\< s4\> s4\! } >>
223 @cindex espressivo articulation
225 In some situations the @code{\espressivo} articulation mark may be
226 the appropriate choice to indicate a crescendo and decrescendo on
229 @lilypond[verbatim,quote,relative=2]
238 Crescendos and decrescendos can be engraved as textual markings
239 instead of hairpins. The built-in commands that enable these text
240 modes are @code{\crescTextCresc}, @code{\dimTextDecresc},
241 @code{\dimTextDecr}, and @code{\dimTextDim}. The corresponding
242 @code{\crescHairpin} and @code{\dimHairpin} commands will revert to
245 @lilypond[verbatim,quote,relative=2]
256 To create new absolute dynamic marks or text that should be
257 aligned with dynamics, see @ref{New dynamic marks}.
259 Vertical positioning of dynamics is handled by
260 @rinternals{DynamicLineSpanner}.
267 @funindex \dynamicDown
269 @funindex \dynamicNeutral
270 @code{\dynamicNeutral},
271 @funindex \crescTextCresc
272 @code{\crescTextCresc},
273 @funindex \dimTextDim
275 @funindex \dimTextDecr
277 @funindex \dimTextDecresc
278 @code{\dimTextDecresc},
279 @funindex \crescHairpin
280 @code{\crescHairpin},
281 @funindex \dimHairpin
287 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
288 {setting-hairpin-behavior-at-bar-lines.ly}
290 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
291 {setting-the-minimum-length-of-hairpins.ly}
296 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
297 {printing-hairpins-using-al-niente-notation.ly}
299 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
300 {vertically-aligning-dynamics-across-multiple-notes.ly}
302 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
303 {hiding-the-extender-line-for-text-dynamics.ly}
305 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
306 {changing-text-and-spanner-styles-for-text-dynamics.ly}
311 @c TODO: Add hairpin to glossary.
318 @rlearning{Articulation and dynamics}.
321 @ref{Direction and placement},
322 @ref{New dynamic marks}.
325 @rlsr{Expressive marks}.
328 @rinternals{DynamicText},
329 @rinternals{Hairpin},
330 @rinternals{DynamicLineSpanner}.
333 @node New dynamic marks
334 @unnumberedsubsubsec New dynamic marks
336 @cindex new dynamic marks
337 @cindex dynamic marks, new
339 The easiest way to create dynamic indications is to use
340 @code{\markup} objects.
342 @lilypond[verbatim,quote]
343 moltoF = \markup { molto \dynamic f }
351 @cindex dynamics, editorial
352 @cindex dynamics, parenthesis
354 Markup mode makes possible, for instance, to add
355 editorial dynamics, printed in round parenthesis or square
356 brackets. Its syntax is described in @ref{Formatting text}.
358 @lilypond[verbatim,quote]
359 roundf = \markup { \center-align { \line { \bold { \italic ( }
360 \dynamic f \bold { \italic ) } } } }
361 boxf = \markup { \bracket { \dynamic f } }
368 Markup objects are treated differently from authentic dynamic marks.
369 Defining dynamic objects that will be entered and printed exactly like
370 standard dynamic marks is also possible, using the following function:
372 @cindex make-dynamic-script
374 @lilypond[verbatim,quote]
375 sfzp = #(make-dynamic-script "sfzp")
382 Note that the dynamic font only contains the characters
383 @code{f,m,p,r,s} and @code{z}. To switch to other font families,
384 it is necessary to use markup mode in its Scheme form, as
385 explained in @ref{Markup construction in Scheme}.
387 @lilypond[verbatim,quote]
388 moltoF = #(make-dynamic-script (markup
389 #:normal-text "molto"
398 Font settings in markup mode are described in
399 @ref{Common markup commands}.
405 @ref{Formatting text},
406 @ref{Common markup commands},
407 @ref{Markup construction in Scheme}.
410 @rlsr{Expressive marks}.
416 This section explains how to create various expressive marks that
417 are curved: normal slurs, phrasing slurs, breath marks, falls, and
428 @unnumberedsubsubsec Slurs
432 @notation{Slurs} are entered using parentheses:
434 @lilypond[verbatim,quote,relative=2]
440 Slurs may be manually placed above or below the notes, see
441 @ref{Direction and placement}.
443 @lilypond[verbatim,quote,relative=2]
451 Phrasing slurs must be used to print more than one slur at once.
452 For details, see @ref{Phrasing slurs}.
454 Slurs can be solid, dotted, or dashed. Solid is the default slur
457 @lilypond[verbatim,quote,relative=1]
474 @funindex \slurNeutral
476 @funindex \slurDashed
478 @funindex \slurDotted
486 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
487 {using-double-slurs-for-legato-chords.ly}
496 @ref{Direction and placement},
497 @ref{Phrasing slurs}.
500 @rlsr{Expressive marks}.
507 @unnumberedsubsubsec Phrasing slurs
509 @cindex phrasing slurs
510 @cindex phrasing marks
514 @notation{Phrasing slurs} (or phrasing marks) that indicate a
515 musical sentence are written using the commands @code{\(} and
516 @code{\)} respectively:
518 @lilypond[verbatim,quote,relative=2]
523 Typographically, a phrasing slur behaves almost exactly like a
524 normal slur. However, they are treated as different objects; a
525 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
526 slurs may be manually placed above or below the notes, see
527 @ref{Direction and placement}.
529 @lilypond[verbatim,quote,relative=1]
530 c4\( g' c,( b) | c1\)
532 c4\( g' c,( b) | c1\)
535 Simultaneous phrasing slurs are not permitted.
540 @funindex \phrasingSlurUp
541 @code{\phrasingSlurUp},
542 @funindex \phrasingSlurDown
543 @code{\phrasingSlurDown},
544 @funindex \phrasingSlurNeutral
545 @code{\phrasingSlurNeutral}.
551 @ref{Direction and placement}.
554 @rlsr{Expressive marks}.
557 @rinternals{PhrasingSlur}.
561 @unnumberedsubsubsec Breath marks
566 Breath marks are entered using @code{\breathe}:
568 @lilypond[verbatim,quote,relative=2]
572 Musical indicators for breath marks in ancient notation,
573 divisiones, are supported. For details, see @ref{Divisiones}.
578 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
579 {changing-the-breath-mark-symbol.ly}
582 @cindex railroad tracks
585 @c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
586 @c {inserting-a-caesura.ly}
588 Caesura marks can be created by overriding the @code{'text}
589 property of the @code{BreathingSign} object. A curved caesura
590 mark is also available.
592 @lilypond[verbatim,quote,relative=2]
593 \override BreathingSign #'text =
594 #(make-musicglyph-markup "scripts.caesura.straight")
595 c8 e4. \breathe g8. e16 c4
597 \override BreathingSign #'text =
598 #(make-musicglyph-markup "scripts.caesura.curved")
599 g8 e'4. \breathe g8. e16 c4
609 @rlsr{Expressive marks}.
610 @c @lsr{expressive,breathing-sign.ly}.
613 @rinternals{BreathingSign}.
616 @node Falls and doits
617 @unnumberedsubsubsec Falls and doits
623 @notation{Falls} and @notation{doits} can be added to notes using
624 the @code{\bendAfter} command. The direction of the fall or doit
625 is indicated with a plus or minus (up or down). The number
626 indicates the pitch interval that the fall or doit will extend
627 @emph{beyond} the main note.
629 @lilypond[verbatim,quote,relative=2]
636 The dash (@tie{-}) immediately preceding the @code{\bendAfter}
637 command is @emph{required} when writing falls and doits.
642 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
643 {adjusting-the-shape-of-falls-and-doits.ly}
648 @c TODO: add falls and doits to glossary.
654 @rlsr{Expressive marks}.
660 This section explains how to create various expressive marks that
661 follow a linear path: glissandos, arpeggios, and trills.
670 @unnumberedsubsubsec Glissando
675 A @notation{glissando} is created by attaching @code{\glissando}
678 @lilypond[verbatim,quote,relative=2]
683 Different styles of glissandi can be created. For details, see
688 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
689 {contemporary-glissando.ly}
701 @rlsr{Expressive marks}.
703 @c FIXME: I need to figure out what's up with these. -gp
704 @c @lsr{expressive,glissando.ly},
705 @c @lsr{expressive,line-styles.ly}
708 @rinternals{Glissando}.
713 Printing text over the line (such as @emph{gliss.}) is not
718 @unnumberedsubsubsec Arpeggio
722 @cindex chord, broken
724 An @notation{arpeggio} on a chord (also known as a broken chord)
725 is denoted by appending @code{\arpeggio} to the chord construct:
727 @lilypond[verbatim,quote,relative=1]
731 The direction of an arpeggio is indicated by adding an arrowhead
732 to the wiggly line. The commands @code{\arpeggioArrowUp} and
733 @code{\arpeggioArrowDown} are used for this task.
734 @code{\arpeggioNormal} reverts back to an arrow-less arpeggio:
736 @lilypond[verbatim,quote,relative=1]
745 The command @code{\arpeggioBracket} can be used to create a square
746 bracket on the left of a chord, indicating that the chord should
747 @emph{not} be arpeggiated. @code{\arpeggioNormal} reverts back
748 to a regular arpeggio:
750 @lilypond[verbatim,quote,relative=1]
758 A @emph{parenthesis} style bracket may be attached to a chord
759 construct instead of a square bracket.
761 @c Maybe create a new \arpeggioParen command, or something
764 @lilypond[verbatim,quote,relative=1]
766 \override Arpeggio #'stencil = #ly:arpeggio::brew-chord-slur
767 \override Arpeggio #'X-extent = #ly:grob::stencil-width
773 Arpeggios can be explicitly written out with ties. For more
774 information, see @ref{Ties}.
780 @funindex \arpeggioArrowUp
781 @code{\arpeggioArrowUp},
782 @funindex \arpeggioArrowDown
783 @code{\arpeggioArrowDown},
784 @funindex \arpeggioNormal
785 @code{\arpeggioNormal},
786 @funindex \arpeggioBracket
787 @code{\arpeggioBracket}.
792 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
793 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
795 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
796 {creating-cross-staff-arpeggios-in-other-contexts.ly}
798 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
799 {creating-arpeggios-across-notes-in-different-voices.ly}
811 @rlsr{Expressive marks}.
814 @rinternals{Arpeggio},
815 @rinternals{PianoStaff}.
820 It is not possible to mix connected arpeggios and unconnected
821 arpeggios in one @code{PianoStaff} at the same point in
824 The parenthesis-style arpeggio brackets do not work for
825 cross-staff arpeggios.
829 @unnumberedsubsubsec Trills
834 Short @notation{trills} without an extender line are printed with
835 @code{\trill}; see @ref{Articulations and ornamentations}.
837 Long running trills are made with @code{\startTrillSpan} and
838 @code{\stopTrillSpan}. In the following example, a long running
839 trill is shown combined with grace notes. To achieve precise
840 control of the placement of the grace notes, see @ref{Grace
843 @lilypond[verbatim,quote,relative=2]
845 d1\startTrillSpan { c16[\stopTrillSpan d] }
849 @cindex pitched trills
850 @cindex trills, pitched
852 Trills that should be executed on an explicitly specified pitch
853 can be typeset with the command @code{\pitchedTrill} using the
857 @code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
858 @var{trillnote} @var{endnote} @code{\stopTrillSpan}
861 @lilypond[verbatim,quote,relative=1]
862 \pitchedTrill e2 \startTrillSpan fis
867 The first argument is the main note. The pitch of the second is
868 printed as a stemless note head in parentheses.
873 @code{\startTrillSpan},
874 @funindex \startTrillSpan
875 @code{\stopTrillSpan}.
876 @funindex \stopTrillSpan
885 @ref{Articulations and ornamentations},
889 @rlsr{Expressive marks}.
892 @rinternals{TrillSpanner}.