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}
23 @node Attached to notes
24 @subsection Attached to notes
27 * Articulations and ornamentations::
32 @node Articulations and ornamentations
33 @subsubsection Articulations and ornamentations
43 @cindex organ pedal marks
61 A variety of symbols that denote articulations, ornamentations,
62 and other performance indications can be attached to a note using
69 The possible values for @var{name} are listed in @ref{List of
70 articulations}. For example:
72 @lilypond[verbatim,quote,relative=2]
73 c4\staccato c\mordent b2\turn
85 Some of these articulations have shorthands for easier entry.
86 Shorthands are appended to the note name, and their syntax
87 consists of a dash (@tie{}@code{-}) followed by a symbol
88 signifying the articulation. Predefined shorthands exist for
89 @notation{marcato}, @notation{stopped}, @notation{tenuto},
90 @notation{staccatissimo}, @notation{accent}, @notation{staccato},
91 and @notation{portato}. Their corresponding output appears as
94 @lilypond[verbatim,quote,relative=2]
99 The rules for the default placement of articulations are defined
100 in @file{scm/@/script@/.scm}. Articulations and ornamentations
101 may be manually placed above or below the staff, see
102 @ref{Direction and placement}.
107 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
108 {modifying-default-values-for-articulation-shorthand-notation.ly}
110 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
111 {controlling-the-vertical-ordering-of-scripts.ly}
123 @ref{Direction and placement}.
126 @file{scm/@/script@/.scm}.
129 @rlsr{Expressive marks}.
133 @rinternals{TextScript}.
138 These signs appear in the printed output but have no effect on the
139 MIDI rendering of the music.
143 @subsubsection Dynamics
145 @cindex absolute dynamics
147 @cindex dynamics, absolute
167 Absolute dynamic marks are specified using a command after a note,
168 such as @code{c4\ff}. The available dynamic marks are
169 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
170 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
171 @code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
172 @code{\spp}, @code{\sfz}, and @code{\rfz}. The dynamic marks may
173 be manually placed above or below the staff, see
174 @ref{Direction and placement}.
176 @lilypond[verbatim,quote,relative=2]
189 A @notation{crescendo} mark is started with @code{\<} and
190 terminated with @code{\!}, an absolute dynamic, or an additional
191 @notation{crescendo} or @notation{decrescendo} mark. A
192 @notation{decrescendo} mark is started with @code{\>} and is also
193 terminated with @code{\!}, an absolute dynamic, or another
194 @notation{crescendo} or @notation{decrescendo} mark. @code{\cr}
195 and @code{\decr} may be used instead of @code{\<} and @code{\>}.
196 @notation{Hairpins} are engraved by default using this notation.
198 @lilypond[verbatim,quote,relative=2]
208 Spacer notes are needed to engrave multiple marks on one note.
210 @lilypond[verbatim,quote,relative=2]
212 << f1 { s4 s4\< s4\> s4\! } >>
215 @cindex espressivo articulation
217 In some situations the @code{\espressivo} articulation mark may be
218 the appropriate choice to indicate a @notation{crescendo} and
219 @notation{decrescendo} on one note:
221 @lilypond[verbatim,quote,relative=2]
229 @funindex \setTextCresc
230 @funindex \setTextDim
231 @funindex \setTextDecr
232 @funindex \setTextDecresc
233 @funindex \setHairpinCresc
234 @funindex \setHairpinDim
235 @funindex \setHairpinDecresc
237 @notation{Crescendos} and @notation{decrescendos} can be engraved
238 as textual markings instead of hairpins. The built-in commands
239 that enable these text modes are @code{\setTextCresc},
240 @code{\setTextDecresc}, @code{\setTextDecr}, and
241 @code{\setTextDim}. The corresponding @code{\setHairpinCresc},
242 @code{\setHairpinDim}, and @code{\setHairpinDecresc} commands will
243 revert to hairpins again:
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}.
275 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
276 {setting-hairpin-behavior-at-bar-lines.ly}
278 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
279 {setting-the-minimum-length-of-hairpins.ly}
284 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
285 {printing-hairpins-using-al-niente-notation.ly}
287 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
288 {vertically-aligning-dynamics-across-multiple-notes.ly}
290 @c I can't figure this one out. Consider removing this. -pm
292 @notation{Crescendi} and @notation{decrescendi} that cross a line
293 break will be continued on the second line. If they end on the
294 first note of a new line, nothing will be printed on that line.
295 To change this behavior, use
298 \override Score.Hairpin #'after-line-breaking = ##t
301 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
302 {hiding-the-extender-line-for-text-dynamics.ly}
304 @c The following snippet goes in input/new/
305 @c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
306 @c {changing-text-and-spanner-styles-for-text-dynamics.ly}
308 The text used for @notation{crescendos} and
309 @notation{decrescendos} can be changed by modifying the context
310 properties @code{crescendoText} and @code{decrescendoText}. The
311 style of the spanner line can be changed by modifying the
312 @code{'style} property of @code{DynamicTextSpanner}. The default
313 value is @code{'hairpin}, and other possible values include
314 @code{'line}, @code{'dashed-line}, and @code{'dotted-line}:
316 @lilypond[verbatim,quote,relative=2]
317 \set crescendoText = \markup { \italic "cresc. poco" }
318 \set crescendoSpanner = #'text
319 \override DynamicTextSpanner #'style = #'dotted-line
329 @c TODO: Add hairpin to glossary.
336 @rlearning{Articulation and dynamics}.
339 @ref{Direction and placement}.
342 @rlsr{Expressive marks}.
345 @rinternals{DynamicText},
346 @rinternals{Hairpin},
347 @rinternals{DynamicLineSpanner}.
350 @node New dynamic marks
351 @subsubsection New dynamic marks
353 @cindex new dynamic marks
354 @cindex dynamic marks, new
356 The easiest way to create dynamic indications is to use
357 @code{\markup} objects.
359 @lilypond[verbatim,quote]
360 moltoF = \markup { molto \dynamic f }
368 @cindex dynamics, editorial
369 @cindex dynamics, parenthesis
371 Markup mode makes possible, for instance, to add
372 editorial dynamics, printed in round parenthesis or square
373 brackets. Its syntax is described in @ref{Formatting text}.
375 @lilypond[verbatim,quote]
376 rndf = \markup { \center-align { \line { \bold { \italic ( }
377 \dynamic f \bold { \italic ) } } } }
378 boxf = \markup { \bracket { \dynamic f } }
385 Markup objects are treated differently from authentic dynamic marks.
386 Defining dynamic objects that will be entered and printed exactly like
387 standard dynamic marks is also possible, using the following function:
389 @cindex make-dynamic-script
391 @lilypond[verbatim,quote]
392 sfzp = #(make-dynamic-script "sfzp")
399 Note that the dynamic font only contains the characters
400 @code{f,m,p,r,s} and @code{z}. To switch to other font families,
401 it is necessary to use markup mode in its Scheme form, as
402 explained in @ref{Markup construction in Scheme}.
404 @lilypond[verbatim,quote]
405 moltoF = #(make-dynamic-script (markup
406 #:normal-text "molto"
415 Font settings in markup mode are described in
416 @ref{Common markup commands}.
422 @ref{Formatting text},
423 @ref{Common markup commands},
424 @ref{Markup construction in Scheme}.
427 @rlsr{Expressive marks}.
445 A @notation{slur} indicates that notes are to be played bound or
446 @emph{legato}. They are entered using parentheses:
448 @lilypond[verbatim,quote,relative=2]
449 f( g a) a8 b( a4 g2 f4)
453 Just as with ties, the direction of a slur can be specified with
454 @code{\slur@emph{DIR}}, where @code{@emph{DIR}} is either
455 @code{Up}, @code{Down}, or @code{Neutral} (@code{Neutral} is the
456 default). Slurs may be manually placed above or below the staff,
457 see @ref{Direction and placement}.
459 @lilypond[verbatim,quote,relative=2]
463 Using this method, only one slur can be printed at once. To print
464 a long slur over a few small slurs, see @ref{Phrasing slurs}.
473 @funindex \slurNeutral
475 @funindex \slurDashed
477 @funindex \slurDotted
485 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
486 {using-double-slurs-for-legato-chords.ly}
495 @ref{Direction and placement}.
498 @rlsr{Expressive marks}.
505 @subsubsection Phrasing slurs
507 @cindex phrasing slurs
508 @cindex phrasing marks
512 A phrasing slur (or phrasing mark) connects notes and is used to
513 indicate a musical sentence. It is written using @code{\(} and
514 @code{\)} respectively:
516 @lilypond[verbatim,quote,relative=2]
517 \time 6/4 c\( d( e) f( e) d\)
520 Typographically, the phrasing slur behaves almost exactly like a
521 normal slur. However, they are treated as different objects. A
522 @code{\slurUp} will have no effect on a phrasing slur; instead,
523 use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
524 @code{\phrasingSlurNeutral}. Phrasing slurs may be manually
525 placed above or below the staff, see @ref{Direction
528 You cannot have simultaneous phrasing slurs.
533 @funindex \phrasingSlurUp
534 @code{\phrasingSlurUp},
535 @funindex \phrasingSlurDown
536 @code{\phrasingSlurDown},
537 @funindex \phrasingSlurNeutral
538 @code{\phrasingSlurNeutral}.
544 @ref{Direction and placement}.
547 @rlsr{Expressive marks}.
550 @rinternals{PhrasingSlur}.
554 @subsubsection Breath marks
559 Breath marks are entered using @code{\breathe}:
561 @lilypond[verbatim,quote,relative=2]
568 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
569 {changing-the-breath-mark-symbol.ly}
575 @rlsr{Expressive marks}.
576 @c @lsr{expressive,breathing-sign.ly}.
579 @rinternals{BreathingSign}.
582 @node Falls and doits
583 @subsubsection Falls and doits
589 @notation{Falls} and @notation{doits} can be added to notes using
590 the @code{\bendAfter} command:
592 @lilypond[verbatim,quote,relative=2]
599 The dash (@tie{-}) following the note name is @emph{required} when
600 writing @notation{falls} and @notation{doits}.
605 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
606 {adjusting-the-shape-of-falls-and-doits.ly}
611 @c TODO: add falls and doits to glossary.
617 @rlsr{Expressive marks}.
630 @subsubsection Glissando
635 A @notation{glissando} is a smooth change in pitch. It is denoted
636 by a line or a wavy line between two notes. A
637 @notation{glissando} is created by attaching @code{\glissando} to
640 @lilypond[verbatim,quote,relative=2]
642 \override Glissando #'style = #'zigzag
649 @c Modify, add description, and put in input/new/
650 @c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
651 @c {suppressing-warnings-for-clashing-note-columns.ly}
653 @lilypond[verbatim,quote]
654 I = \once \override NoteColumn #'ignore-collision = ##t
657 { \oneVoice \stemDown f2 \glissando \stemNeutral a } \\
658 { \oneVoice \I c2 \glissando \I d, }
669 @rlsr{Expressive marks}.
671 @c FIXME: I need to figure out what's up with these. -gp
672 @c @lsr{expressive,glissando.ly},
673 @c @lsr{expressive,line-styles.ly}
676 @rinternals{Glissando}.
681 Printing text over the line (such as @emph{gliss.}) is not
686 @subsubsection Arpeggio
690 @cindex chord, broken
692 @c Add documentation for new 'parenthesis' style arpeggio. Maybe
693 @c create a new \arpeggioParen command, or something similar. -pm
695 You can specify an @notation{arpeggio} (also known as a
696 @notation{broken chord}) on a chord by attaching an
697 @code{\arpeggio} to the chord:
699 @lilypond[verbatim,quote,relative=1]
703 A square bracket on the left, denoted by @code{\arpeggioBracket},
704 is used to indicate that the chord should @emph{not} be
707 @lilypond[verbatim,quote,relative=1]
712 The direction of the arpeggio can be denoted by adding an
713 arrowhead to the wiggly line. This is done with the commands
714 @code{arpeggioUp} and @code{arpeggioDown}. @code{arpeggioNeutral}
715 reverts to the arrow-less version:
717 @lilypond[verbatim,quote,relative=1]
728 @notation{Arpeggios} can be explicitly written out using
729 @notation{ties}. For more information, see @ref{Ties}.
735 @funindex \arpeggioUp
737 @funindex \arpeggioDown
738 @code{\arpeggioDown},
739 @funindex \arpeggioNeutral
740 @code{\arpeggioNeutral},
741 @funindex \arpeggioBracket
742 @code{\arpeggioBracket}.
747 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
748 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
750 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
751 {creating-cross-staff-arpeggios-in-other-contexts.ly}
753 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
754 {creating-arpeggios-across-notes-in-different-voices.ly}
759 @c TODO: Add 'broken chord' to glossary.
768 @rlsr{Expressive marks}.
771 @rinternals{Arpeggio},
772 @rinternals{PianoStaff}.
777 It is not possible to mix connected arpeggios and unconnected
778 arpeggios in one @code{PianoStaff} at the same point in
783 @subsubsection Trills
788 Short @notation{trills} are printed with @code{\trill} like normal
789 articulation; see @ref{Articulations and ornamentations}.
791 Long running @notation{trills} are made with
792 @code{\startTrillSpan} and @code{\stopTrillSpan}. In the
793 following example, a long running @notation{trill} is shown
794 combined with grace notes. To achieve precise control of the
795 placement of the grace notes, see @ref{Grace notes}.
797 @lilypond[verbatim,quote,relative=2]
799 d1\startTrillSpan { c16[\stopTrillSpan d] }
803 @cindex pitched trills
804 @cindex trills, pitched
806 @notation{Trills} that should be executed on an explicitly
807 specified pitch can be typeset with the command
808 @code{\pitchedTrill} using the following syntax:
811 @code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
812 @var{trillnote} @var{endnote} @code{\stopTrillSpan}
815 @lilypond[verbatim,quote,relative=1]
816 \pitchedTrill e2 \startTrillSpan fis
821 The first argument is the main note. The pitch of the second is
822 printed as a stemless note head in parentheses.
827 @code{\startTrillSpan},
828 @funindex \startTrillSpan
829 @code{\stopTrillSpan}.
830 @funindex \stopTrillSpan
839 @rlsr{Expressive marks}.
842 @rinternals{TrillSpanner}.