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{\!}
307 before. A hairpin ending on a downbeat will stop at the preceding bar line.
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 @cindex hairpins at bar lines
451 @lilypondfile[verbatim,quote,texidoc,doctitle]
452 {setting-hairpin-behavior-at-bar-lines.ly}
454 @lilypondfile[verbatim,quote,texidoc,doctitle]
455 {setting-the-minimum-length-of-hairpins.ly}
460 @lilypondfile[verbatim,quote,texidoc,doctitle]
461 {printing-hairpins-using-al-niente-notation.ly}
463 @cindex Ferneyhough hairpins
464 @cindex hairpins, Ferneyhough
465 @cindex flared hairpins
466 @cindex hairpins, flared
467 @cindex constante hairpins
468 @cindex hairpins, constante
470 @lilypondfile[verbatim,quote,texidoc,doctitle]
471 {printing-hairpins-in-various-styles.ly}
473 @lilypondfile[verbatim,quote,texidoc,doctitle]
474 {vertically-aligned-dynamics-and-textscripts.ly}
476 @lilypondfile[verbatim,quote,texidoc,doctitle]
477 {hiding-the-extender-line-for-text-dynamics.ly}
479 @lilypondfile[verbatim,quote,texidoc,doctitle]
480 {changing-text-and-spanner-styles-for-text-dynamics.ly}
490 @rlearning{Articulation and dynamics}.
493 @ref{Direction and placement},
494 @ref{New dynamic marks},
495 @ref{Enhancing MIDI output},
496 @ref{Controlling MIDI dynamics}.
499 @rlsr{Expressive marks}.
502 @rinternals{DynamicText},
503 @rinternals{Hairpin},
504 @rinternals{DynamicLineSpanner},
505 @rinternals{Dynamics}.
508 @node New dynamic marks
509 @unnumberedsubsubsec New dynamic marks
511 @cindex new dynamic marks
512 @cindex dynamic marks, new
514 The easiest way to create dynamic indications is to use
515 @code{\markup} objects.
517 @lilypond[verbatim,quote]
518 moltoF = \markup { molto \dynamic f }
521 <d' e>16_\moltoF <d e>
526 @cindex dynamics, editorial
527 @cindex dynamics, parenthesis
528 @cindex editorial dynamics
532 In markup mode, editorial dynamics (within parentheses or square
533 brackets) can be created. The syntax for markup mode is described
534 in @ref{Formatting text}.
536 @lilypond[verbatim,quote]
538 \center-align \concat { \bold { \italic ( }
539 \dynamic f \bold { \italic ) } } }
540 boxF = \markup { \bracket { \dynamic f } }
547 @cindex make-dynamic-script
548 @funindex make-dynamic-script
550 Simple, centered dynamic marks are easily created with the
551 @code{make-dynamic-script} function.
553 @lilypond[verbatim,quote]
554 sfzp = #(make-dynamic-script "sfzp")
560 In general, @code{make-dynamic-script} takes any markup object as its
561 argument. The dynamic font only contains the characters
562 @code{f,m,p,r,s} and @code{z}, so if a dynamic mark that includes
563 plain text or punctuation symbols is desired, markup commands that
564 reverts font family and font encoding to normal text should be used,
565 for example @code{\normal-text}. The interest of using
566 @code{make-dynamic-script} instead of an ordinary markup is ensuring
567 the vertical alignment of markup objects and hairpins that are
568 attached to the same note head.
570 @lilypond[verbatim,quote]
571 roundF = \markup { \center-align \concat {
572 \normal-text { \bold { \italic ( } }
574 \normal-text { \bold { \italic ) } } } }
575 boxF = \markup { \bracket { \dynamic f } }
576 mfEspress = \markup { \center-align \line {
577 \hspace #3.7 mf \normal-text \italic espress. } }
578 roundFdynamic = #(make-dynamic-script roundF)
579 boxFdynamic = #(make-dynamic-script boxF)
580 mfEspressDynamic = #(make-dynamic-script mfEspress)
582 c'4_\roundFdynamic\< d e f
585 g'1~\mfEspressDynamic
590 The Scheme form of markup mode may be used instead. Its syntax is
591 explained in @rextend{Markup construction in Scheme}.
593 @lilypond[verbatim,quote]
594 moltoF = #(make-dynamic-script
595 (markup #:normal-text "molto"
603 To left-align the dynamic text rather than centering it on a note
606 @lilypond[verbatim,quote]
607 moltoF = \tweak DynamicText.self-alignment-X #LEFT
608 #(make-dynamic-script
609 (markup #:normal-text "molto"
613 <d e>2..\moltoF <d e>1
617 Font settings in markup mode are described in
618 @ref{Selecting font and font size}.
622 @ref{Formatting text},
623 @ref{Selecting font and font size},
624 @ref{Enhancing MIDI output},
625 @ref{Controlling MIDI dynamics}.
628 @rextend{Markup construction in Scheme}.
631 @rlsr{Expressive marks}.
634 @node Expressive marks as curves
635 @subsection Expressive marks as curves
637 This section explains how to create various expressive marks that
638 are curved: normal slurs, phrasing slurs, breath marks, falls, and
649 @unnumberedsubsubsec Slurs
653 @notation{Slurs} are entered using parentheses:
655 @warning{In polyphonic music, a slur must be terminated
656 in the same voice it began.}
658 @lilypond[verbatim,quote]
666 @cindex slurs, manual placement
667 @cindex slurs, below notes
668 @cindex slurs, above notes
670 @funindex \slurNeutral
672 Slurs may be manually placed above or below the staff; see
673 @ref{Direction and placement}.
675 @cindex phrasing slur
676 @cindex multiple slurs
677 @cindex simultaneous slurs
678 @cindex slur, phrasing
679 @cindex slurs, multiple
680 @cindex slurs, simultaneous
683 Simultaneous or overlapping slurs require special attention. Most
684 occurences of outer slurs actually indicate phrasing, and phrasing
685 slurs may overlap a regular slur, see @ref{Phrasing slurs}. When
686 multiple regular slurs are needed in a single @code{Voice},
687 matching slur starts and ends need to be labelled by preceding
688 them with @code{\=} followed by an identifying key (a symbol or
689 non-negative integer).
691 @lilypond[verbatim,quote]
693 <c~ f\=1( g\=2( >2 <c e\=1) a\=2) >
705 @funindex \slurDashed
706 @funindex \slurDotted
709 Slurs can be solid, dotted, or dashed. Solid is the default slur
712 @lilypond[verbatim,quote]
724 @funindex \slurHalfDashed
725 @funindex \slurHalfSolid
726 @cindex slur, half dashed and half solid
728 Slurs can also be made half-dashed (the first half dashed, the
729 second half solid) or half-solid (the first half solid, the second
732 @lilypond[verbatim,quote]
744 @funindex \slurDashPattern
745 @cindex slur, defining dash patterns
747 Custom dash patterns for slurs can be defined:
749 @lilypond[verbatim,quote]
752 \slurDashPattern #0.7 #0.75
754 \slurDashPattern #0.5 #2.0
772 @code{\slurHalfDashed},
773 @code{\slurHalfSolid},
774 @code{\slurDashPattern},
781 @lilypondfile[verbatim,quote,texidoc,doctitle]
782 {using-double-slurs-for-legato-chords.ly}
784 @lilypondfile[verbatim,quote,texidoc,doctitle]
785 {positioning-text-markups-inside-slurs.ly}
787 @lilypondfile[verbatim,quote,texidoc,doctitle]
788 {making-slurs-with-complex-dash-structure.ly}
795 @rlearning{On the un-nestedness of brackets and ties}.
798 @ref{Direction and placement},
799 @ref{Phrasing slurs}.
802 @rlsr{Expressive marks}.
809 @unnumberedsubsubsec Phrasing slurs
811 @cindex phrasing slurs
812 @cindex phrasing marks
813 @cindex slur, phrasing
814 @cindex mark, phrasing
818 @notation{Phrasing slurs} (or phrasing marks) that indicate a
819 musical sentence are written using the commands @code{\(} and
820 @code{\)} respectively:
822 @lilypond[verbatim,quote]
829 @funindex \phrasingSlurUp
830 @funindex \phrasingSlurDown
831 @funindex \phrasingSlurNeutral
833 Typographically, a phrasing slur behaves almost exactly like a
834 normal slur. However, they are treated as different objects; a
835 @code{\slurUp} will have no effect on a phrasing slur. Phrasing
836 may be manually placed above or below the staff; see
837 @ref{Direction and placement}.
839 @cindex simultaneous phrasing slurs
840 @cindex multiple phrasing slurs
841 @cindex slur, simultaneous phrasing
842 @cindex slur, multiple phrasing
843 @cindex phrasing slur, simultaneous
844 @cindex phrasing slur, multiple
846 Simultaneous or overlapping phrasing slurs are entered using
847 @code{\=} as with regular slurs, see @ref{Slurs}.
849 @funindex \phrasingSlurDashed
850 @funindex \phrasingSlurDotted
851 @funindex \phrasingSlurSolid
852 @cindex phrasing slur, dashed
853 @cindex dashed phrasing slur
854 @cindex phrasing slur, dotted
855 @cindex dotted phrasing slurs
856 @cindex slur, dashed phrasing
857 @cindex slur, dotted phrasing
859 Phrasing slurs can be solid, dotted, or dashed. Solid is the default
860 style for phrasing slurs:
862 @lilypond[verbatim,quote]
874 @funindex \phrasingSlurHalfDashed
875 @funindex \phrasingSlurHalfSolid
876 @cindex phrasing slur, half solid and half dashed
877 @cindex slur, half solid and half dashed phrasing
879 Phrasing slurs can also be made half-dashed (the first half dashed, the
880 second half solid) or half-solid (the first half solid, the second
883 @lilypond[verbatim,quote]
886 \phrasingSlurHalfDashed
888 \phrasingSlurHalfSolid
895 @funindex \phrasingSlurDashPattern
896 @cindex phrasing slur, defining dash patterns
897 @cindex slur, phrasing, defining dash patterns
898 @cindex slur, defining dash patterns for phrasing
900 Custom dash patterns for phrasing slurs can be defined:
902 @lilypond[verbatim,quote]
905 \phrasingSlurDashPattern #0.7 #0.75
907 \phrasingSlurDashPattern #0.5 #2.0
914 Dash pattern definitions for phrasing slurs have the same structure
915 as dash pattern definitions for slurs. For more information about
916 complex dash patterns, see the snippets under @ref{Slurs}.
919 @code{\phrasingSlurUp},
920 @code{\phrasingSlurDown},
921 @code{\phrasingSlurNeutral},
922 @code{\phrasingSlurDashed},
923 @code{\phrasingSlurDotted},
924 @code{\phrasingSlurHalfDashed},
925 @code{\phrasingSlurHalfSolid},
926 @code{\phrasingSlurDashPattern},
927 @code{\phrasingSlurSolid}.
932 @rlearning{On the un-nestedness of brackets and ties}.
935 @ref{Direction and placement},
939 @rlsr{Expressive marks}.
942 @rinternals{PhrasingSlur}.
946 @unnumberedsubsubsec Breath marks
952 Breath marks are entered using @code{\breathe}:
954 @lilypond[verbatim,quote]
955 { c''2. \breathe d''4 }
958 Unlike other expressive marks, a breath mark is not associated with
959 the preceding note but is a separate music event. So all the
960 expressive marks which are attached to the preceding note, any square
961 brackets indicating manual beams, and any brackets indicating slurs
962 and phrasing slurs must be placed before @code{\breathe}.
964 A breath mark will end an automatic beam; to override this behavior, see
967 @lilypond[verbatim,quote]
968 \relative { c''8 \breathe d e f g2 }
971 Musical indicators for breath marks in ancient notation,
972 divisiones, are supported. For details, see @ref{Divisiones}.
977 @lilypondfile[verbatim,quote,texidoc,doctitle]
978 {changing-the-breath-mark-symbol.ly}
982 @lilypondfile[verbatim,quote,texidoc,doctitle]
983 {using-a-tick-as-the-breath-mark-symbol.ly}
986 @cindex railroad tracks
988 @lilypondfile[verbatim,quote,texidoc,doctitle]
989 {inserting-a-caesura.ly}
999 @rlsr{Expressive marks}.
1001 Internals Reference:
1002 @rinternals{BreathingEvent},
1003 @rinternals{BreathingSign},
1004 @rinternals{Breathing_sign_engraver}.
1007 @node Falls and doits
1008 @unnumberedsubsubsec Falls and doits
1012 @funindex \bendAfter
1014 @notation{Falls} and @notation{doits} can be added to notes using
1015 the @code{\bendAfter} command. The direction of the fall or doit
1016 is indicated with a plus or minus (up or down). The number
1017 indicates the pitch interval that the fall or doit will extend
1018 @emph{beyond} the main note.
1020 @lilypond[verbatim,quote]
1033 @lilypondfile[verbatim,quote,texidoc,doctitle]
1034 {adjusting-the-shape-of-falls-and-doits.ly}
1042 @rlsr{Expressive marks}.
1045 @node Expressive marks as lines
1046 @subsection Expressive marks as lines
1048 This section explains how to create various expressive marks that
1049 follow a linear path: glissandos, arpeggios, and trills.
1058 @unnumberedsubsubsec Glissando
1061 @funindex \glissando
1063 A @notation{glissando} is created by appending @code{\glissando}
1066 @lilypond[verbatim,quote]
1070 \afterGrace f,1\glissando f'16
1074 A glissando can connect notes across staves:
1076 @lilypond[verbatim,quote]
1078 \new Staff = "right" {
1080 \change Staff = "left"
1082 \change Staff = "right"
1085 \new Staff = "left" {
1092 A glissando can connect notes in chords. If anything other than a
1093 direct one-to-one pairing of the notes in the two chords is required
1094 the connections between the notes are defined by setting
1095 @code{\glissandoMap}, where the notes of a chord are assumed to be
1096 numbered from zero in the order in which they appear in the input
1099 @lilypond[verbatim,quote]
1101 <c' e>1\glissando g' |
1105 \set glissandoMap = #'((0 . 1) (1 . 0))
1106 <c, g'>1\glissando |
1108 \set glissandoMap = #'((0 . 0) (0 . 1) (0 . 2))
1111 \set glissandoMap = #'((2 . 0) (1 . 0) (0 . 1))
1112 <f d a'>1\glissando |
1117 Different styles of glissandi can be created. For details, see
1122 @lilypondfile[verbatim,quote,texidoc,doctitle]
1123 {contemporary-glissando.ly}
1125 @lilypondfile[verbatim,quote,texidoc,doctitle]
1126 {adding-timing-marks-to-long-glissandi.ly}
1128 @lilypondfile[verbatim,quote,texidoc,doctitle]
1129 {making-glissandi-breakable.ly}
1131 @lilypondfile[verbatim,quote,texidoc,doctitle]
1132 {extending-glissandi-across-repeats.ly}
1142 @rlsr{Expressive marks}.
1144 Internals Reference:
1145 @rinternals{Glissando}.
1148 Printing text over the line (such as @notation{gliss.}) is not
1153 @unnumberedsubsubsec Arpeggio
1156 @cindex broken chord
1157 @cindex chord, broken
1160 @funindex \arpeggioArrowUp
1161 @funindex \arpeggioArrowDown
1162 @funindex \arpeggioNormal
1164 An @notation{arpeggio} on a chord (also known as a broken chord)
1165 is denoted by appending @code{\arpeggio} to the chord construct:
1167 @lilypond[verbatim,quote]
1168 \relative { <c' e g c>1\arpeggio }
1171 Different types of arpeggios may be written.
1172 @code{\arpeggioNormal} reverts to a normal arpeggio:
1174 @lilypond[verbatim,quote]
1176 <c' e g c>2\arpeggio
1189 @cindex arpeggio symbols, special
1190 @cindex special arpeggio symbols
1192 @funindex \arpeggioBracket
1193 @funindex \arpeggioParenthesis
1194 @funindex \arpeggioParenthesisDashed
1196 Special @emph{bracketed} arpeggio symbols can be created:
1198 @lilypond[verbatim,quote]
1205 \arpeggioParenthesis
1208 \arpeggioParenthesisDashed
1216 The dash properties of the parenthesis arpeggio are controlled
1217 with the @code{'dash-definition} property, which is described at
1220 Arpeggios can be explicitly written out with ties. For more
1221 information, see @ref{Ties}.
1226 @code{\arpeggioArrowUp},
1227 @code{\arpeggioArrowDown},
1228 @code{\arpeggioNormal},
1229 @code{\arpeggioBracket},
1230 @code{\arpeggioParenthesis},
1231 @code{\arpeggioParenthesisDashed}.
1237 @lilypondfile[verbatim,quote,texidoc,doctitle]
1238 {creating-cross-staff-arpeggios-in-a-piano-staff.ly}
1240 @lilypondfile[verbatim,quote,texidoc,doctitle]
1241 {creating-cross-staff-arpeggios-in-other-contexts.ly}
1243 @lilypondfile[verbatim,quote,texidoc,doctitle]
1244 {creating-arpeggios-across-notes-in-different-voices.ly}
1255 @rlsr{Expressive marks}.
1257 Internals Reference:
1258 @rinternals{Arpeggio},
1260 @rinternals{PianoStaff}.
1263 @cindex cross-staff parenthesis-style arpeggio
1264 @cindex arpeggio, parenthesis-style, cross-staff
1265 @cindex arpeggio, cross-staff parenthesis-style
1267 It is not possible to mix connected arpeggios and unconnected
1268 arpeggios in one @code{PianoStaff} at the same point in
1271 The simple way of setting parenthesis-style arpeggio brackets does not work for
1272 cross-staff arpeggios; see @ref{Cross-staff stems}.
1276 @unnumberedsubsubsec Trills
1281 @funindex \startTrillSpan
1282 @funindex \stopTrillSpan
1284 Short trills without an extender line are printed with
1285 @code{\trill}; see @ref{Articulations and ornamentations}.
1287 Longer trills with an extender line are made with
1288 @code{\startTrillSpan} and @code{\stopTrillSpan}:
1290 @lilypond[verbatim,quote]
1299 A trill spanner crossing a line break will restart exactly above
1300 the first note on the new line.
1302 @lilypond[ragged-right,verbatim,quote]
1312 Consecutive trill spans will work without explicit
1313 @code{\stopTrillSpan} commands, since successive trill spanners will
1314 automatically become the right bound of the previous trill.
1316 @lilypond[verbatim,quote]
1326 Trills can also be combined with grace notes. The syntax of this
1327 construct and the method to precisely position the grace notes are
1328 described in @ref{Grace notes}.
1330 @lilypond[verbatim,quote]
1333 d1\startTrillSpan { c32[ d]\stopTrillSpan }
1338 @cindex pitched trills
1339 @cindex trills, pitched
1340 @funindex \pitchedTrill
1342 Trills that require an auxiliary note with an explicit pitch can
1343 be typeset with the @code{\pitchedTrill} command. The first
1344 argument is the main note, and the second is the @emph{trilled}
1345 note, printed as a stemless note head in parentheses.
1347 @lilypond[verbatim,quote]
1350 d''2\startTrillSpan fis
1357 @cindex pitched trill with accidental
1358 @cindex trill with accidental
1360 Subsequent accidentals of the same note in the same measure will need
1361 to be added manually. Only the accidental of the first pitched trill
1362 in a measure is printed.
1364 @lilypond[verbatim,quote]
1367 eis''4\startTrillSpan fis
1370 eis4\startTrillSpan cis
1373 eis4\startTrillSpan fis
1376 eis4\startTrillSpan fis!
1382 @code{\startTrillSpan},
1383 @code{\stopTrillSpan}.
1391 @ref{Articulations and ornamentations},
1395 @rlsr{Expressive marks}.
1397 Internals Reference:
1398 @rinternals{TrillSpanner}.