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. For details, see the Contributors'
7 Guide, node Updating translation committishes..
12 @node Expressive marks
13 @section Expressive marks
15 @lilypondfile[quote]{expressive-headword.ly}
17 This section lists various expressive marks that can be
21 * Expressive marks attached to notes::
22 * Expressive marks as curves::
23 * Expressive marks as lines::
27 @node Expressive marks attached to notes
28 @subsection Expressive marks attached to notes
30 This section explains how to create expressive marks that are
31 attached to notes: articulations, ornamentations, and dynamics.
32 Methods to create new dynamic markings are also discussed.
35 * Articulations and ornamentations::
40 @node Articulations and ornamentations
41 @unnumberedsubsubsec Articulations and ornamentations
52 @cindex organ pedal marks
53 @cindex pedal marks, organ
75 @funindex \staccatissimo
91 @funindex \snappizzicato
93 @funindex \reverseturn
98 @funindex \prallmordent
102 @funindex \downmordent
106 @funindex \signumcongruentiae
107 @funindex \shortfermata
109 @funindex \longfermata
110 @funindex \verylongfermata
111 @funindex \fermataMarkup
119 A variety of symbols that denote articulations, ornamentations,
120 and other performance indications can be attached to a note using
124 @var{note}\@var{name}
127 The possible values for @code{@var{name}} are listed in
128 @ref{List of articulations}. For example:
130 @lilypond[verbatim,quote]
132 c''4\staccato c\mordent b2\turn
139 @cindex staccatissimo
144 Some of these articulations have shorthands for easier entry.
145 Shorthands are appended to the note name, and their syntax
146 consists of a dash @code{-} followed by a symbol signifying the
147 articulation. Predefined shorthands exist for @notation{marcato},
148 @notation{stopped}, @notation{tenuto}, @notation{staccatissimo},
149 @notation{accent}, @notation{staccato}, and @notation{portato}.
150 Their corresponding output appears as follows:
152 @lilypond[verbatim,quote]
159 The rules for the default placement of articulations are defined
160 in @file{scm/script.scm}. Articulations and ornamentations
161 may be manually placed above or below the staff; see
162 @ref{Direction and placement}.
164 Articulations are @code{Script} objects. Their properties are
165 described more fully in @rinternals{Script}.
167 Articulations can be attached to rests as well as notes but they
168 cannot be attached to multi-measure rests. A special predefined
169 command, @code{\fermataMarkup}, is available for attaching a fermata
170 to a multi-measure rest (and only a multi-measure rest). This
171 creates a @code{MultiMeasureRestText} object.
173 @lilypond[verbatim,quote,fragment]
174 \override Script.color = #red
175 \override MultiMeasureRestText.color = #blue
176 a'2\fermata r\fermata
180 In addition to articulations, text and markups can be attached to
181 notes. See @ref{Text scripts}.
183 For more information about the ordering of Scripts and TextScripts that
184 are attached to the notes, see @rlearning{Placement of objects}.
188 @lilypondfile[verbatim,quote,texidoc,doctitle]
189 {modifying-default-values-for-articulation-shorthand-notation.ly}
191 @lilypondfile[verbatim,quote,texidoc,doctitle]
192 {controlling-the-vertical-ordering-of-scripts.ly}
194 @lilypondfile[verbatim,quote,texidoc,doctitle]
195 {creating-a-delayed-turn.ly}
205 @rlearning{Placement of objects}.
209 @ref{Direction and placement},
210 @ref{List of articulations},
214 @file{scm/script.scm}.
217 @rlsr{Expressive marks}.
221 @rinternals{TextScript}.
225 @unnumberedsubsubsec Dynamics
227 @cindex absolute dynamics
229 @cindex dynamics, absolute
251 Absolute dynamic marks are specified using a command after a note,
252 such as @code{c4\ff}. The available dynamic marks are
253 @code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
254 @code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
255 @code{\ffff}, @code{\fffff}, @code{\fp}, @code{\sf}, @code{\sff},
256 @code{\sp}, @code{\spp}, @code{\sfz}, and @code{\rfz}. Dynamic
257 marks may be manually placed above or below the staff; see
258 @ref{Direction and placement}.
260 @lilypond[verbatim,quote]
279 A @notation{crescendo} mark is started with @code{\<} and
280 terminated with @code{\!}, an absolute dynamic, or an additional
281 crescendo or decrescendo mark. A @notation{decrescendo} mark is
282 started with @code{\>} and is also terminated with @code{\!}, an
283 absolute dynamic, or another crescendo or decrescendo mark.
284 @code{\cr} and @code{\decr} may be used instead of @code{\<} and
285 @code{\>}. @notation{Hairpins} are engraved by default using this
288 @lilypond[verbatim,quote]
300 A hairpin that is terminated with @code{\!} will end at the
301 right edge of the note that has the @code{\!} assigned to it. In the
302 case where it is terminated with the start of another @notation{crescendo}
303 or @notation{decrescendo} mark, it will end at the centre of the note
304 that has the next @code{\<} or @code{\>} assigned to it. The next
305 hairpin will then start at the right edge of the same note
306 instead of the usual left edge had it been terminated with @code{\!}
309 @lilypond[verbatim,quote]
311 c''1\< | c4 a c\< a | c4 a c\! a\< | c4 a c a\!
315 Hairpins that are terminated with absolute dynamic marks instead of
316 @code{\!} will also be engraved in a similar way. However, the length
317 of the absolute dynamic itself can alter where the preceding hairpin
320 @lilypond[verbatim,quote]
322 c''1\< | c4 a c\mf a | c1\< | c4 a c\ffff a
326 @cindex multiple dynamic marks on one note
327 @cindex dynamic marks, multiple on one note
328 Spacer rests are needed to engrave multiple marks on one note.
329 This is particularly useful when adding a @notation{crescendo} and
330 @notation{decrescendo} to the same note:
332 @lilypond[verbatim,quote]
335 << f1 { s4 s4\< s4\> s4\! } >>
339 @cindex espressivo articulation
341 @funindex \espressivo
343 The @code{\espressivo} command can be used to indicate a crescendo
344 and decrescendo on the same note. However, be warned that this is
345 implemented as an articulation, not a dynamic.
347 @lilypond[verbatim,quote]
357 Textual crescendo marks begin with @code{\cresc}.
358 Textual decrescendos begin with @code{\decresc} or @code{\dim}.
359 Extender lines are engraved as required.
361 @lilypond[verbatim,quote]
363 g'8\cresc a b c b c d e\mf |
364 f8\decresc e d c e\> d c b |
370 @funindex \crescTextCresc
371 @funindex \dimTextDecresc
372 @funindex \dimTextDecr
373 @funindex \dimTextDim
374 @funindex \crescHairpin
375 @funindex \dimHairpin
377 Textual marks for dynamic changes can also replace hairpins:
378 @lilypond[verbatim,quote]
395 To create new absolute dynamic marks or text that should be
396 aligned with dynamics, see @ref{New dynamic marks}.
398 @cindex dynamics, vertical positioning
399 @cindex vertical positioning of dynamics
401 @funindex DynamicLineSpanner
404 Vertical positioning of dynamics is handled by
405 @rinternals{DynamicLineSpanner}.
407 @funindex \dynamicDown
408 @funindex \dynamicNeutral
410 A @code{Dynamics} context is available to engrave dynamics on
411 their own horizontal line. Use spacer rests to indicate timing.
412 (Notes in a @code{Dynamics} context will also take up
413 musical time, but will not be engraved.)
414 The @code{Dynamics} context can usefully contain some other
415 items such as text scripts, text spanners, and piano pedal marks.
417 @lilypond[verbatim,quote]
419 \new Staff \relative {
437 @code{\dynamicNeutral},
438 @code{\crescTextCresc},
441 @code{\dimTextDecresc},
442 @code{\crescHairpin},
449 @lilypondfile[verbatim,quote,texidoc,doctitle]
450 {setting-hairpin-behavior-at-bar-lines.ly}
452 @lilypondfile[verbatim,quote,texidoc,doctitle]
453 {setting-the-minimum-length-of-hairpins.ly}
458 @lilypondfile[verbatim,quote,texidoc,doctitle]
459 {printing-hairpins-using-al-niente-notation.ly}
461 @cindex Ferneyhough hairpins
462 @cindex hairpins, Ferneyhough
463 @cindex flared hairpins
464 @cindex hairpins, flared
465 @cindex constante hairpins
466 @cindex hairpins, constante
468 @lilypondfile[verbatim,quote,texidoc,doctitle]
469 {printing-hairpins-in-various-styles.ly}
471 @lilypondfile[verbatim,quote,texidoc,doctitle]
472 {vertically-aligned-dynamics-and-textscripts.ly}
474 @lilypondfile[verbatim,quote,texidoc,doctitle]
475 {hiding-the-extender-line-for-text-dynamics.ly}
477 @lilypondfile[verbatim,quote,texidoc,doctitle]
478 {changing-text-and-spanner-styles-for-text-dynamics.ly}
488 @rlearning{Articulation and dynamics}.
491 @ref{Direction and placement},
492 @ref{New dynamic marks},
493 @ref{Enhancing MIDI output},
494 @ref{Controlling MIDI dynamics}.
497 @rlsr{Expressive marks}.
500 @rinternals{DynamicText},
501 @rinternals{Hairpin},
502 @rinternals{DynamicLineSpanner},
503 @rinternals{Dynamics}.
506 @node New dynamic marks
507 @unnumberedsubsubsec New dynamic marks
509 @cindex new dynamic marks
510 @cindex dynamic marks, new
512 The easiest way to create dynamic indications is to use
513 @code{\markup} objects.
515 @lilypond[verbatim,quote]
516 moltoF = \markup { molto \dynamic f }
519 <d' e>16_\moltoF <d e>
524 @cindex dynamics, editorial
525 @cindex dynamics, parenthesis
526 @cindex editorial dynamics
530 In markup mode, editorial dynamics (within parentheses or square
531 brackets) can be created. The syntax for markup mode is described
532 in @ref{Formatting text}.
534 @lilypond[verbatim,quote]
536 \center-align \concat { \bold { \italic ( }
537 \dynamic f \bold { \italic ) } } }
538 boxF = \markup { \bracket { \dynamic f } }
545 @cindex make-dynamic-script
546 @funindex make-dynamic-script
548 Simple, centered dynamic marks are easily created with the
549 @code{make-dynamic-script} function.
551 @lilypond[verbatim,quote]
552 sfzp = #(make-dynamic-script "sfzp")
558 In general, @code{make-dynamic-script} takes any markup object as its
559 argument. The dynamic font only contains the characters
560 @code{f,m,p,r,s} and @code{z}, so if a dynamic mark that includes
561 plain text or punctuation symbols is desired, markup commands that
562 reverts font family and font encoding to normal text should be used,
563 for example @code{\normal-text}. The interest of using
564 @code{make-dynamic-script} instead of an ordinary markup is ensuring
565 the vertical alignment of markup objects and hairpins that are
566 attached to the same note head.
568 @lilypond[verbatim,quote]
569 roundF = \markup { \center-align \concat {
570 \normal-text { \bold { \italic ( } }
572 \normal-text { \bold { \italic ) } } } }
573 boxF = \markup { \bracket { \dynamic f } }
574 mfEspress = \markup { \center-align \line {
575 \hspace #3.7 mf \normal-text \italic espress. } }
576 roundFdynamic = #(make-dynamic-script roundF)
577 boxFdynamic = #(make-dynamic-script boxF)
578 mfEspressDynamic = #(make-dynamic-script mfEspress)
580 c'4_\roundFdynamic\< d e f
583 g'1~\mfEspressDynamic
588 The Scheme form of markup mode may be used instead. Its syntax is
589 explained in @rextend{Markup construction in Scheme}.
591 @lilypond[verbatim,quote]
592 moltoF = #(make-dynamic-script
593 (markup #:normal-text "molto"
601 To left-align the dynamic text rather than centering it on a note
604 @lilypond[verbatim,quote]
605 moltoF = \tweak DynamicText.self-alignment-X #LEFT
606 #(make-dynamic-script
607 (markup #:normal-text "molto"
611 <d e>2..\moltoF <d e>1
615 Font settings in markup mode are described in
616 @ref{Selecting font and font size}.
620 @ref{Formatting text},
621 @ref{Selecting font and font size},
622 @ref{Enhancing MIDI output},
623 @ref{Controlling MIDI dynamics}.
626 @rextend{Markup construction in Scheme}.
629 @rlsr{Expressive marks}.
632 @node Expressive marks as curves
633 @subsection Expressive marks as curves
635 This section explains how to create various expressive marks that
636 are curved: normal slurs, phrasing slurs, breath marks, falls, and
647 @unnumberedsubsubsec Slurs
651 @notation{Slurs} are entered using parentheses:
653 @warning{In polyphonic music, a slur must be terminated
654 in the same voice it began.}
656 @lilypond[verbatim,quote]
664 @cindex slurs, manual placement
665 @cindex slurs, below notes
666 @cindex slurs, above notes
668 @funindex \slurNeutral
670 Slurs may be manually placed above or below the staff; see
671 @ref{Direction and placement}.
673 @cindex phrasing slur
674 @cindex multiple slurs
675 @cindex simultaneous slurs
676 @cindex slur, phrasing
677 @cindex slurs, multiple
678 @cindex slurs, simultaneous
681 Simultaneous or overlapping slurs require special attention. Most
682 occurences of outer slurs actually indicate phrasing, and phrasing
683 slurs may overlap a regular slur, see @ref{Phrasing slurs}. When
684 multiple regular slurs are needed in a single @code{Voice},
685 matching slur starts and ends need to be labelled by preceding
686 them with @code{\=} followed by an identifying number or string.
688 @lilypond[verbatim,quote]
690 <c~ f\=1( g\=2( >2 <c e\=1) a\=2) >
702 @funindex \slurDashed
703 @funindex \slurDotted
706 Slurs can be solid, dotted, or dashed. Solid is the default slur
709 @lilypond[verbatim,quote]
721 @funindex \slurHalfDashed
722 @funindex \slurHalfSolid
723 @cindex slur, half dashed and half solid
725 Slurs can also be made half-dashed (the first half dashed, the
726 second half solid) or half-solid (the first half solid, the second
729 @lilypond[verbatim,quote]
741 @funindex \slurDashPattern
742 @cindex slur, defining dash patterns
744 Custom dash patterns for slurs can be defined:
746 @lilypond[verbatim,quote]
749 \slurDashPattern #0.7 #0.75
751 \slurDashPattern #0.5 #2.0
769 @code{\slurHalfDashed},
770 @code{\slurHalfSolid},
771 @code{\slurDashPattern},
778 @lilypondfile[verbatim,quote,texidoc,doctitle]
779 {using-double-slurs-for-legato-chords.ly}
781 @lilypondfile[verbatim,quote,texidoc,doctitle]
782 {positioning-text-markups-inside-slurs.ly}
784 @lilypondfile[verbatim,quote,texidoc,doctitle]
785 {making-slurs-with-complex-dash-structure.ly}
792 @rlearning{On the un-nestedness of brackets and ties}.
795 @ref{Direction and placement},
796 @ref{Phrasing slurs}.
799 @rlsr{Expressive marks}.
806 @unnumberedsubsubsec Phrasing slurs
808 @cindex phrasing slurs
809 @cindex phrasing marks
810 @cindex slur, phrasing
811 @cindex mark, phrasing
815 @notation{Phrasing slurs} (or phrasing marks) that indicate a
816 musical sentence are written using the commands @code{\(} and
817 @code{\)} respectively:
819 @lilypond[verbatim,quote]
826 @funindex \phrasingSlurUp
827 @funindex \phrasingSlurDown
828 @funindex \phrasingSlurNeutral
830 Typographically, a phrasing slur behaves almost exactly like a
831 normal slur. However, they are treated as different objects; a
832 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
833 may be manually placed above or below the staff; see
834 @ref{Direction and placement}.
836 @cindex simultaneous phrasing slurs
837 @cindex multiple phrasing slurs
838 @cindex slur, simultaneous phrasing
839 @cindex slur, multiple phrasing
840 @cindex phrasing slur, simultaneous
841 @cindex phrasing slur, multiple
843 Simultaneous or overlapping phrasing slurs are entered using
844 @code{\=} as with regular slurs, see @ref{Slurs}.
846 @funindex \phrasingSlurDashed
847 @funindex \phrasingSlurDotted
848 @funindex \phrasingSlurSolid
849 @cindex phrasing slur, dashed
850 @cindex dashed phrasing slur
851 @cindex phrasing slur, dotted
852 @cindex dotted phrasing slurs
853 @cindex slur, dashed phrasing
854 @cindex slur, dotted phrasing
856 Phrasing slurs can be solid, dotted, or dashed. Solid is the default
857 style for phrasing slurs:
859 @lilypond[verbatim,quote]
871 @funindex \phrasingSlurHalfDashed
872 @funindex \phrasingSlurHalfSolid
873 @cindex phrasing slur, half solid and half dashed
874 @cindex slur, half solid and half dashed phrasing
876 Phrasing slurs can also be made half-dashed (the first half dashed, the
877 second half solid) or half-solid (the first half solid, the second
880 @lilypond[verbatim,quote]
883 \phrasingSlurHalfDashed
885 \phrasingSlurHalfSolid
892 @funindex \phrasingSlurDashPattern
893 @cindex phrasing slur, defining dash patterns
894 @cindex slur, phrasing, defining dash patterns
895 @cindex slur, defining dash patterns for phrasing
897 Custom dash patterns for phrasing slurs can be defined:
899 @lilypond[verbatim,quote]
902 \phrasingSlurDashPattern #0.7 #0.75
904 \phrasingSlurDashPattern #0.5 #2.0
911 Dash pattern definitions for phrasing slurs have the same structure
912 as dash pattern definitions for slurs. For more information about
913 complex dash patterns, see the snippets under @ref{Slurs}.
916 @code{\phrasingSlurUp},
917 @code{\phrasingSlurDown},
918 @code{\phrasingSlurNeutral},
919 @code{\phrasingSlurDashed},
920 @code{\phrasingSlurDotted},
921 @code{\phrasingSlurHalfDashed},
922 @code{\phrasingSlurHalfSolid},
923 @code{\phrasingSlurDashPattern},
924 @code{\phrasingSlurSolid}.
929 @rlearning{On the un-nestedness of brackets and ties}.
932 @ref{Direction and placement},
936 @rlsr{Expressive marks}.
939 @rinternals{PhrasingSlur}.
943 @unnumberedsubsubsec Breath marks
949 Breath marks are entered using @code{\breathe}:
951 @lilypond[verbatim,quote]
952 { c''2. \breathe d''4 }
955 Unlike other expressive marks, a breath mark is not associated with
956 the preceding note but is a separate music event. So all the
957 expressive marks which are attached to the preceding note, any square
958 brackets indicating manual beams, and any brackets indicating slurs
959 and phrasing slurs must be placed before @code{\breathe}.
961 A breath mark will end an automatic beam; to override this behavior, see
964 @lilypond[verbatim,quote]
965 \relative { c''8 \breathe d e f g2 }
968 Musical indicators for breath marks in ancient notation,
969 divisiones, are supported. For details, see @ref{Divisiones}.
974 @lilypondfile[verbatim,quote,texidoc,doctitle]
975 {changing-the-breath-mark-symbol.ly}
979 @lilypondfile[verbatim,quote,texidoc,doctitle]
980 {using-a-tick-as-the-breath-mark-symbol.ly}
983 @cindex railroad tracks
985 @lilypondfile[verbatim,quote,texidoc,doctitle]
986 {inserting-a-caesura.ly}
996 @rlsr{Expressive marks}.
999 @rinternals{BreathingEvent},
1000 @rinternals{BreathingSign},
1001 @rinternals{Breathing_sign_engraver}.
1004 @node Falls and doits
1005 @unnumberedsubsubsec Falls and doits
1009 @funindex \bendAfter
1011 @notation{Falls} and @notation{doits} can be added to notes using
1012 the @code{\bendAfter} command. The direction of the fall or doit
1013 is indicated with a plus or minus (up or down). The number
1014 indicates the pitch interval that the fall or doit will extend
1015 @emph{beyond} the main note.
1017 @lilypond[verbatim,quote]
1030 @lilypondfile[verbatim,quote,texidoc,doctitle]
1031 {adjusting-the-shape-of-falls-and-doits.ly}
1039 @rlsr{Expressive marks}.
1042 @node Expressive marks as lines
1043 @subsection Expressive marks as lines
1045 This section explains how to create various expressive marks that
1046 follow a linear path: glissandos, arpeggios, and trills.
1055 @unnumberedsubsubsec Glissando
1058 @funindex \glissando
1060 A @notation{glissando} is created by appending @code{\glissando}
1063 @lilypond[verbatim,quote]
1067 \afterGrace f,1\glissando f'16
1071 A glissando can connect notes across staves:
1073 @lilypond[verbatim,quote]
1075 \new Staff = "right" {
1077 \change Staff = "left"
1079 \change Staff = "right"
1082 \new Staff = "left" {
1089 A glissando can connect notes in chords. If anything other than a
1090 direct one-to-one pairing of the notes in the two chords is required
1091 the connections between the notes are defined by setting
1092 @code{\glissandoMap}, where the notes of a chord are assumed to be
1093 numbered from zero in the order in which they appear in the input
1096 @lilypond[verbatim,quote]
1098 <c' e>1\glissando g' |
1102 \set glissandoMap = #'((0 . 1) (1 . 0))
1103 <c, g'>1\glissando |
1105 \set glissandoMap = #'((0 . 0) (0 . 1) (0 . 2))
1108 \set glissandoMap = #'((2 . 0) (1 . 0) (0 . 1))
1109 <f d a'>1\glissando |
1114 Different styles of glissandi can be created. For details, see
1119 @lilypondfile[verbatim,quote,texidoc,doctitle]
1120 {contemporary-glissando.ly}
1122 @lilypondfile[verbatim,quote,texidoc,doctitle]
1123 {adding-timing-marks-to-long-glissandi.ly}
1125 @lilypondfile[verbatim,quote,texidoc,doctitle]
1126 {making-glissandi-breakable.ly}
1128 @lilypondfile[verbatim,quote,texidoc,doctitle]
1129 {extending-glissandi-across-repeats.ly}
1139 @rlsr{Expressive marks}.
1141 Internals Reference:
1142 @rinternals{Glissando}.
1145 Printing text over the line (such as @notation{gliss.}) is not
1150 @unnumberedsubsubsec Arpeggio
1153 @cindex broken chord
1154 @cindex chord, broken
1157 @funindex \arpeggioArrowUp
1158 @funindex \arpeggioArrowDown
1159 @funindex \arpeggioNormal
1161 An @notation{arpeggio} on a chord (also known as a broken chord)
1162 is denoted by appending @code{\arpeggio} to the chord construct:
1164 @lilypond[verbatim,quote]
1165 \relative { <c' e g c>1\arpeggio }
1168 Different types of arpeggios may be written.
1169 @code{\arpeggioNormal} reverts to a normal arpeggio:
1171 @lilypond[verbatim,quote]
1173 <c' e g c>2\arpeggio
1186 @cindex arpeggio symbols, special
1187 @cindex special arpeggio symbols
1189 @funindex \arpeggioBracket
1190 @funindex \arpeggioParenthesis
1191 @funindex \arpeggioParenthesisDashed
1193 Special @emph{bracketed} arpeggio symbols can be created:
1195 @lilypond[verbatim,quote]
1202 \arpeggioParenthesis
1205 \arpeggioParenthesisDashed
1213 The dash properties of the parenthesis arpeggio are controlled
1214 with the @code{'dash-definition} property, which is described at
1217 Arpeggios can be explicitly written out with ties. For more
1218 information, see @ref{Ties}.
1223 @code{\arpeggioArrowUp},
1224 @code{\arpeggioArrowDown},
1225 @code{\arpeggioNormal},
1226 @code{\arpeggioBracket},
1227 @code{\arpeggioParenthesis}
1228 @code{\arpeggioParenthesisDashed}.
1234 @lilypondfile[verbatim,quote,texidoc,doctitle]
1235 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
1237 @lilypondfile[verbatim,quote,texidoc,doctitle]
1238 {creating-cross-staff-arpeggios-in-other-contexts.ly}
1240 @lilypondfile[verbatim,quote,texidoc,doctitle]
1241 {creating-arpeggios-across-notes-in-different-voices.ly}
1252 @rlsr{Expressive marks}.
1254 Internals Reference:
1255 @rinternals{Arpeggio},
1257 @rinternals{PianoStaff}.
1260 @cindex cross-staff parenthesis-style arpeggio
1261 @cindex arpeggio, parenthesis-style, cross-staff
1262 @cindex arpeggio, cross-staff parenthesis-style
1264 It is not possible to mix connected arpeggios and unconnected
1265 arpeggios in one @code{PianoStaff} at the same point in
1268 The simple way of setting parenthesis-style arpeggio brackets does not work for
1269 cross-staff arpeggios; see @ref{Cross-staff stems}.
1273 @unnumberedsubsubsec Trills
1278 @funindex \startTrillSpan
1279 @funindex \stopTrillSpan
1281 Short trills without an extender line are printed with
1282 @code{\trill}; see @ref{Articulations and ornamentations}.
1284 Longer trills with an extender line are made with
1285 @code{\startTrillSpan} and @code{\stopTrillSpan}:
1287 @lilypond[verbatim,quote]
1296 A trill spanner crossing a line break will restart exactly above
1297 the first note on the new line.
1299 @lilypond[ragged-right,verbatim,quote]
1309 Consecutive trill spans will work without explicit
1310 @code{\stopTrillSpan} commands, since successive trill spanners will
1311 automatically become the right bound of the previous trill.
1313 @lilypond[verbatim,quote]
1323 Trills can also be combined with grace notes. The syntax of this
1324 construct and the method to precisely position the grace notes are
1325 described in @ref{Grace notes}.
1327 @lilypond[verbatim,quote]
1330 d1\startTrillSpan { c32[ d]\stopTrillSpan }
1335 @cindex pitched trills
1336 @cindex trills, pitched
1337 @funindex \pitchedTrill
1339 Trills that require an auxiliary note with an explicit pitch can
1340 be typeset with the @code{\pitchedTrill} command. The first
1341 argument is the main note, and the second is the @emph{trilled}
1342 note, printed as a stemless note head in parentheses.
1344 @lilypond[verbatim,quote]
1347 d''2\startTrillSpan fis
1354 @cindex pitched trill with accidental
1355 @cindex trill with accidental
1357 Subsequent accidentals of the same note in the same measure will need
1358 to be added manually. Only the accidental of the first pitched trill
1359 in a measure is printed.
1361 @lilypond[verbatim,quote]
1364 eis''4\startTrillSpan fis
1367 eis4\startTrillSpan cis
1370 eis4\startTrillSpan fis
1373 eis4\startTrillSpan fis!
1379 @code{\startTrillSpan},
1380 @code{\stopTrillSpan}.
1388 @ref{Articulations and ornamentations},
1392 @rlsr{Expressive marks}.
1394 Internals Reference:
1395 @rinternals{TrillSpanner}.