version that you are working on. See TRANSLATION for details.
@end ignore
+@c \version "2.11.38"
+
@node Expressive marks
@section Expressive marks
@node Attached to notes
@subsection Attached to notes
-
@menu
* Articulations and ornamentations::
* Dynamics::
+* New dynamic marks::
@end menu
@node Articulations and ornamentations
@cindex articulations
@cindex scripts
@cindex ornaments
+@cindex espressivo
+@cindex fermata
+@cindex upbow
+@cindex downbow
+@cindex foot marks
+@cindex organ pedal marks
+@cindex turn
+@cindex open
+@cindex stopped
+@cindex flageolet
+@cindex reverseturn
+@cindex trill
+@cindex prall
+@cindex mordent
+@cindex prallprall
+@cindex prallmordent
+@cindex prall, up
+@cindex prall, down
+@cindex thumb marking
+@cindex segno
+@cindex coda
+@cindex varcoda
-A variety of symbols can appear above and below notes to indicate
-different characteristics of the performance. All these symbols
-can be attached to a note using the syntax
-@var{note}@tie{}@code{\}@var{name}.
+A variety of symbols that denote articulations, ornamentations,
+and other performance indications can be attached to a note using
+this syntax:
-@c Add a LilyPond example here soon. -pm
+@example
+@var{note}\@var{name}
+@end example
The possible values for @var{name} are listed in @ref{List of
-articulations}.
+articulations}. For example:
+
+@lilypond[verbatim,quote,relative=2]
+c4\staccato c\mordent b2\turn
+c1\fermata
+@end lilypond
@cindex marcato
@cindex stopped
and @notation{portato}. Their corresponding output appears as
follows:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c4-^ c-+ c-- c-|
c-> c-. c-_
@end lilypond
-The marks are placed automatically by default (either above or
-below the note), but their positions can be manually @q{forced}
-above or below notes as well. For details, see
-@ref{Controlling direction and placement}.
-
-@cindex espressivo
-@cindex fermata
-@cindex upbow
-@cindex downbow
-@cindex foot marks
-@cindex organ pedal marks
-@cindex turn
-@cindex open
-@cindex stopped
-@cindex flageolet
-@cindex reverseturn
-@cindex trill
-@cindex prall
-@cindex mordent
-@cindex prallprall
-@cindex prallmordent
-@cindex prall, up
-@cindex prall, down
-@cindex thumb marking
-@cindex segno
-@cindex coda
-@cindex varcoda
+The rules for the default placement of articulations are defined
+in @file{scm/@/script@/.scm}. Articulations and ornamentations
+may be manually placed above or below the staff, see
+@ref{Direction and placement}.
@snippets
-@c Send these snippets to Valentin for the LSR.
-
-The shorthands are defined in @file{ly/@/script@/-init@/.ly},
-where the variables @code{dashHat}, @code{dashPlus},
-@code{dashDash}, @code{dashBar}, @code{dashLarger},
-@code{dashDot}, and @code{dashUnderscore} are assigned default
-values. The default values for the shorthands can be modified.
-For example, to associate the @code{-+} (@code{dashPlus})
-shorthand with the @notation{trill} symbol instead of the default
-@notation{+} symbol, assign the value @code{trill} to the variable
-@code{dashPlus}:
-
-@lilypond[verbatim,quote,ragged-right]
-\relative c'' { c-+ }
-dashPlus = "trill"
-\relative c'' { c-+ }
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{modifying-default-values-for-articulation-shorthand-notation.ly}
-The vertical ordering of scripts is controlled with the
-@code{script-priority} property. The lower this number, the
-closer it will be put to the note. In this example, the
-@code{TextScript} (the sharp symbol) first has the lowest
-priority, so it is put lowest in the first example. In the
-second, the @notation{prall trill} (the @code{Script}) has the
-lowest, so it is on the inside. When two objects have the same
-priority, the order in which they are entered decides which one
-comes first.
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=3]
-\once \override TextScript #'script-priority = #-100
-a4^\prall^\markup { \sharp }
-
-\once \override Script #'script-priority = #-100
-a4^\prall^\markup { \sharp }
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{controlling-the-vertical-ordering-of-scripts.ly}
@seealso
-Music Glossary: @rglos{marcato}, @rglos{stopped}, @rglos{tenuto},
-@rglos{staccatissimo}, @rglos{accent}, @rglos{staccato},
+Music Glossary:
+@rglos{tenuto},
+@rglos{accent},
+@rglos{staccato},
@rglos{portato}.
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Notation Reference:
+@ref{Direction and placement}.
+
+Installed Files:
+@file{scm/@/script@/.scm}.
-Internals Reference: @internalsref{Script},
-@internalsref{TextScript}.
+Snippets:
+@rlsr{Expressive marks}.
+
+Internals Reference:
+@rinternals{Script},
+@rinternals{TextScript}.
@knownissues
@node Dynamics
@subsubsection Dynamics
+@cindex absolute dynamics
@cindex dynamics
+@cindex dynamics, absolute
+@funindex \ppppp
@funindex \pppp
@funindex \ppp
@funindex \pp
@funindex \rfz
Absolute dynamic marks are specified using a command after a note,
-like @code{c4\ff}. The available dynamic marks are @code{\ppppp},
-@code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p}, @code{\mp},
-@code{\mf}, @code{\f}, @code{\ff}, @code{\fff}, @code{\ffff},
-@code{\fp}, @code{\sf}, @code{\sff}, @code{\sp}, @code{\spp},
-@code{\sfz}, and @code{\rfz}. The dynamic marks can be placed
-above or below the staff: For details, see
-@ref{Controlling direction and placement}.
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+such as @code{c4\ff}. The available dynamic marks are
+@code{\ppppp}, @code{\pppp}, @code{\ppp}, @code{\pp}, @code{\p},
+@code{\mp}, @code{\mf}, @code{\f}, @code{\ff}, @code{\fff},
+@code{\ffff}, @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp},
+@code{\spp}, @code{\sfz}, and @code{\rfz}. The dynamic marks may
+be manually placed above or below the staff, see
+@ref{Direction and placement}.
+
+@lilypond[verbatim,quote,relative=2]
c2\ppp c\mp
c\rfz c^\mf
-c_\spp c_\staccato^\ff
+c_\spp c^\ff
@end lilypond
@cindex hairpin
@funindex \decr
A @notation{crescendo} mark is started with @code{\<} and
-terminated with @code{\!} or an absolute dynamic. A
-@notation{decrescendo} is started with @code{\>} and is also
-terminated with @code{\!} or an absolute dynamic. @code{\cr} and
-@code{\decr} may be used instead of @code{\<} and @code{\>}. They
-can be engraved either using a graphical sign (a
-@notation{hairpin}), or with textual signs.
-
-Because these marks are bound to notes, you must use spacer notes
-if multiple marks are needed during one note.
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c\< c\! d\> e\!
-<< f1 { s4 s4\< s4\! \> s4\! } >>
+terminated with @code{\!}, an absolute dynamic, or an additional
+@notation{crescendo} or @notation{decrescendo} mark. A
+@notation{decrescendo} mark is started with @code{\>} and is also
+terminated with @code{\!}, an absolute dynamic, or another
+@notation{crescendo} or @notation{decrescendo} mark. @code{\cr}
+and @code{\decr} may be used instead of @code{\<} and @code{\>}.
+@notation{Hairpins} are engraved by default using this notation.
+
+@lilypond[verbatim,quote,relative=2]
+c2\< c\!
+d2\< d\f
+e2\< e\>
+f2\> f\!
+e2\> e\mp
+d2\> d\>
+c1\!
@end lilypond
-This may give rise to very short hairpins. To lengthen them, use
-for example @code{minimum-length} in
-@internalsref{Voice}.@internalsref{Hairpin}:
+Spacer notes are needed to engrave multiple marks on one note.
-@example
-\override Voice.Hairpin #'minimum-length = #5
-@end example
-
-@noindent
-A @notation{hairpin} normally starts at the left edge of the
-beginning note and ends on the right edge of the ending note. If
-the ending note falls on the downbeat, the @notation{hairpin} ends
-on the immediately preceding bar line. This may be modified by
-setting the @code{hairpinToBarline} property:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-e4\< e2. e1\!
-\set hairpinToBarline = ##f
-e4\< e2. e1\!
+@lilypond[verbatim,quote,relative=2]
+c4\< c\! d\> e\!
+<< f1 { s4 s4\< s4\> s4\! } >>
@end lilypond
-@cindex espressivo, articulation
+@cindex espressivo articulation
In some situations the @code{\espressivo} articulation mark may be
-suitable to indicate a crescendo and decrescendo on the one note:
+the appropriate choice to indicate a @notation{crescendo} and
+@notation{decrescendo} on one note:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-c2 b4 a g1\espressivo
-@end lilypond
-
-@cindex al niente
-@cindex niente, al
-
-Hairpins may be printed with a circled tip (al niente notation) by
-setting the @code{circled-tip} property:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\override Hairpin #'circled-tip = ##t
-c2\< c\!
-c4\> c\< c2\!
+@lilypond[verbatim,quote,relative=2]
+c2 b4 a
+g1\espressivo
@end lilypond
@cindex crescendo
@cindex diminuendo
@funindex \setTextCresc
@funindex \setTextDim
+@funindex \setTextDecr
@funindex \setTextDecresc
@funindex \setHairpinCresc
@funindex \setHairpinDim
@funindex \setHairpinDecresc
-You can use text saying @emph{cresc.}, @emph{decr.}, or
-@emph{dim.} instead of hairpins with the commands
-@code{\setTextCresc}, @code{\setTextDim}, and
-@code{\setTextDecresc}. The corresponding
-@code{\setHairpinCresc}, @code{\setHairpinDim}, and
-@code{\setHairpinDecresc} will revert to hairpins again:
+@notation{Crescendos} and @notation{decrescendos} can be engraved
+as textual markings instead of hairpins. The built-in commands
+that enable these text modes are @code{\setTextCresc},
+@code{\setTextDecresc}, @code{\setTextDecr}, and
+@code{\setTextDim}. The corresponding @code{\setHairpinCresc},
+@code{\setHairpinDim}, and @code{\setHairpinDecresc} commands will
+revert to hairpins again:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\setTextCresc
+@lilypond[verbatim,quote,relative=2]
c\< d e f\!
-\setHairpinCresc
e\> d c b\!
+\setTextCresc
+c\< d e f\!
\setTextDecresc
-e\> d e f\!
-\setTextDecr
-c\> d e f\!
-\setTextDim
e\> d c b\!
+\setHairpinCresc
+c\< d e f\!
@end lilypond
-You can also supply your own texts and change the style of the
-spanner line with the properties @code{\crescendoText},
-@code{\crescendoSpanner}, @code{\decrescendoText}, and
-@code{\decrescendoSpanner}. Available values for the spanner
-properties are @code{hairpin}, @code{line}, @code{dashed-line},
-and @code{dotted-line}. If unset, a hairpin crescendo is used:
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\set crescendoText = \markup { \italic "cresc. poco" }
-\set crescendoSpanner = #'dotted-line
-a'2\< a a a a a a a\!\mf
-@end lilypond
-
-To create new dynamic marks or text that should be aligned with
-dynamics, see @ref{New dynamic marks}.
+To create new absolute dynamic marks or text that should be
+aligned with dynamics, see @ref{New dynamic marks}.
Vertical positioning of dynamics is handled by
-@internalsref{DynamicLineSpanner}.
+@rinternals{DynamicLineSpanner}.
@predefined
@snippets
-Dynamics that occur at, begin on, or end on the same note will be
-vertically aligned. If you want to ensure that dynamics are
-aligned when they do not occur on the same note, you can increase
-the @code{staff-padding} property.
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{setting-hairpin-behavior-at-bar-lines.ly}
-@example
-\override DynamicLineSpanner #'staff-padding = #4
-@end example
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{setting-the-minimum-length-of-hairpins.ly}
-@noindent
-You may also use this property if the dynamics are colliding with
-other notation.
+@cindex al niente
+@cindex niente, al
+
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{printing-hairpins-using-al-niente-notation.ly}
+
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{vertically-aligning-dynamics-across-multiple-notes.ly}
+
+@c I can't figure this one out. Consider removing this. -pm
-Crescendi and decrescendi that cross a line break will be
-continued on the second line. If they end on the first note of a
-new line, nothing will be printed on that line. To change this
-behavior, use
+@notation{Crescendi} and @notation{decrescendi} that cross a line
+break will be continued on the second line. If they end on the
+first note of a new line, nothing will be printed on that line.
+To change this behavior, use
@example
\override Score.Hairpin #'after-line-breaking = ##t
@end example
-Text style dynamic changes (such as @emph{cresc.} and @emph{dim.})
-are printed with a dashed line showing their extent. To surpress
-printing this line, use
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{hiding-the-extender-line-for-text-dynamics.ly}
-@example
-\override DynamicTextSpanner #'dash-period = #-1.0
-@end example
+@c The following snippet goes in input/new/
+@c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@c {changing-text-and-spanner-styles-for-text-dynamics.ly}
+
+The text used for @notation{crescendos} and
+@notation{decrescendos} can be changed by modifying the context
+properties @code{crescendoText} and @code{decrescendoText}. The
+style of the spanner line can be changed by modifying the
+@code{'style} property of @code{DynamicTextSpanner}. The default
+value is @code{'hairpin}, and other possible values include
+@code{'line}, @code{'dashed-line}, and @code{'dotted-line}:
+
+@lilypond[verbatim,quote,relative=2]
+\set crescendoText = \markup { \italic "cresc. poco" }
+\set crescendoSpanner = #'text
+\override DynamicTextSpanner #'style = #'dotted-line
+a2\< a
+a2 a
+a2 a
+a2 a\mf
+@end lilypond
@seealso
-Music Glossary: @rglos{hairpin}, @rglos{crescendo},
+@c TODO: Add hairpin to glossary.
+
+Music Glossary:
+@rglos{crescendo},
@rglos{decrescendo}.
-Learning Manual: @rlearning{Articulation and dynamics}.
+Learning Manual:
+@rlearning{Articulation and dynamics}.
+
+Notation Reference:
+@ref{Direction and placement}.
+
+Snippets:
+@rlsr{Expressive marks}.
+
+Internals Reference:
+@rinternals{DynamicText},
+@rinternals{Hairpin},
+@rinternals{DynamicLineSpanner}.
+
+
+@node New dynamic marks
+@subsubsection New dynamic marks
+
+@cindex new dynamic marks
+@cindex dynamic marks, new
+
+It is possible to print new dynamic marks or text that should be
+aligned with dynamics. Use @code{make-dynamic-script} to create
+these marks. Note that the dynamic font only contains the
+characters @code{f,m,p,r,s} and @code{z}.
+
+Some situations (such as dynamic marks) have preset font-related
+properties. If you are creating text in such situations, it is
+advisable to cancel those properties with @code{normal-text}. See
+@ref{Text markup commands} for more details.
+
+@cindex make-dynamic-script
+
+@lilypond[verbatim,quote]
+sfzp = #(make-dynamic-script "sfzp")
+\relative c' {
+ c4 c c\sfzp c
+}
+@end lilypond
+
+@cindex dynamics, editorial
+@cindex dynamics, parenthesis
-Snippets: @lsrdir{Expressive,Expressive-marks}
+It is also possible to print dynamics in round parenthesis or
+square brackets. These are often used for adding editorial
+dynamics.
+
+@lilypond[verbatim,quote]
+rndf = \markup { \center-align { \line { \bold { \italic ( }
+ \dynamic f \bold { \italic ) } } } }
+boxf = \markup { \bracket { \dynamic f } }
+\relative c' {
+ c1_\rndf
+ c1_\boxf
+}
+@end lilypond
+
+
+@seealso
-Internals Reference: @internalsref{DynamicText},
-@internalsref{Hairpin}. Vertical positioning of these symbols is
-handled by @internalsref{DynamicLineSpanner}.
+Snippets:
+@rlsr{Expressive marks}.
@node Curves
A @notation{slur} indicates that notes are to be played bound or
@emph{legato}. They are entered using parentheses:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
f( g a) a8 b( a4 g2 f4)
<c e>2( <b d>2)
@end lilypond
Just as with ties, the direction of a slur can be specified with
@code{\slur@emph{DIR}}, where @code{@emph{DIR}} is either
@code{Up}, @code{Down}, or @code{Neutral} (@code{Neutral} is the
-default). The shorthands are also available: For details, see
-@ref{Controlling direction and placement}.
+default). Slurs may be manually placed above or below the staff,
+see @ref{Direction and placement}.
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c4_( c) c^( c)
@end lilypond
@snippets
-Some composers write two slurs when they want legato chords. This
-can be achieved in LilyPond by setting @code{doubleSlurs},
-
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\set doubleSlurs = ##t
-<c e>4 ( <d f> <c e> <d f> )
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{using-double-slurs-for-legato-chords.ly}
@seealso
-Music Glossary: @rglos{slur}
+Music Glossary:
+@rglos{slur}.
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Notation Reference:
+@ref{Direction and placement}.
-Internals Reference: @internalsref{Slur}.
+Snippets:
+@rlsr{Expressive marks}.
+
+Internals Reference:
+@rinternals{Slur}.
@node Phrasing slurs
indicate a musical sentence. It is written using @code{\(} and
@code{\)} respectively:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\time 6/4 c'\( d( e) f( e) d\)
+@lilypond[verbatim,quote,relative=2]
+\time 6/4 c\( d( e) f( e) d\)
@end lilypond
Typographically, the phrasing slur behaves almost exactly like a
normal slur. However, they are treated as different objects. A
@code{\slurUp} will have no effect on a phrasing slur; instead,
use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
-@code{\phrasingSlurNeutral}. The shorthands work for phrasing
-slurs as well: For details, see @ref{Controlling direction and placement}.
+@code{\phrasingSlurNeutral}. Phrasing slurs may be manually
+placed above or below the staff, see @ref{Direction
+and placement}.
You cannot have simultaneous phrasing slurs.
@seealso
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Notation Reference:
+@ref{Direction and placement}.
+
+Snippets:
+@rlsr{Expressive marks}.
-Internals Reference: @internalsref{PhrasingSlur}
+Internals Reference:
+@rinternals{PhrasingSlur}.
@node Breath marks
Breath marks are entered using @code{\breathe}:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-c'4 \breathe d4
+@lilypond[verbatim,quote,relative=2]
+c4 \breathe d4
@end lilypond
@snippets
-The glyph of the breath mark can be tuned by overriding the
-@code{text} property of the @code{BreathingSign} layout object
-with any markup text. For example,
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{changing-the-breath-mark-symbol.ly}
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-c'4
-\override BreathingSign #'text
- = #(make-musicglyph-markup "scripts.rvarcomma")
-\breathe
-d4
-@end lilypond
@seealso
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
@c @lsr{expressive,breathing-sign.ly}.
-Internals Reference: @internalsref{BreathingSign}
+Internals Reference:
+@rinternals{BreathingSign}.
@node Falls and doits
@funindex \bendAfter
@notation{Falls} and @notation{doits} can be added to notes using
-the @code{\bendAfter} command,
+the @code{\bendAfter} command:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\override Score.SpacingSpanner #'shortest-duration-space = #3.0
-c4-\bendAfter #+5
-c4-\bendAfter #-3
+@lilypond[verbatim,quote,relative=2]
+c2-\bendAfter #+4
+c-\bendAfter #-4
+c-\bendAfter #+8
+c-\bendAfter #-8
@end lilypond
+The dash (@tie{-}) following the note name is @emph{required} when
+writing @notation{falls} and @notation{doits}.
+
+
+@snippets
+
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{adjusting-the-shape-of-falls-and-doits.ly}
+
@seealso
-Music Glossary: @rglos{falls}, @rglos{doits}.
+@c TODO: add falls and doits to glossary.
+@c Music Glossary:
+@c @rglos{falls},
+@c @rglos{doits}.
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
@node Lines
@notation{glissando} is created by attaching @code{\glissando} to
a note:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c2\glissando c'
\override Glissando #'style = #'zigzag
c2\glissando c,
@snippets
-@lilypond[verbatim,quote,ragged-right]
+@c Modify, add description, and put in input/new/
+@c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@c {suppressing-warnings-for-clashing-note-columns.ly}
+
+@lilypond[verbatim,quote]
I = \once \override NoteColumn #'ignore-collision = ##t
\relative c' <<
@seealso
-Music Glossary: @rglos{glissando}
+Music Glossary:
+@rglos{glissando}.
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
@c FIXME: I need to figure out what's up with these. -gp
@c @lsr{expressive,glissando.ly},
@c @lsr{expressive,line-styles.ly}
-Internals Reference: @internalsref{Glissando}
+Internals Reference:
+@rinternals{Glissando}.
@knownissues
@cindex arpeggio
@cindex broken chord
-@funindex \arpeggio
+@cindex chord, broken
+
+@c Add documentation for new 'parenthesis' style arpeggio. Maybe
+@c create a new \arpeggioParen command, or something similar. -pm
You can specify an @notation{arpeggio} (also known as a
@notation{broken chord}) on a chord by attaching an
@code{\arpeggio} to the chord:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
+@lilypond[verbatim,quote,relative=1]
<c e g c>\arpeggio
@end lilypond
is used to indicate that the chord should @emph{not} be
arpeggiated:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
+@lilypond[verbatim,quote,relative=1]
\arpeggioBracket
<c e g c>\arpeggio
@end lilypond
@code{arpeggioUp} and @code{arpeggioDown}. @code{arpeggioNeutral}
reverts to the arrow-less version:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
+@lilypond[verbatim,quote,relative=1]
\new Voice {
\arpeggioUp
<c e g c>\arpeggio
}
@end lilypond
+@notation{Arpeggios} can be explicitly written out using
+@notation{ties}. For more information, see @ref{Ties}.
@predefined
+@funindex \arpeggio
+@code{\arpeggio},
@funindex \arpeggioUp
@code{\arpeggioUp},
@funindex \arpeggioDown
@snippets
-In a @code{PianoStaff}, it is possible to let an arpeggio cross
-between the staves by setting the property
-@code{PianoStaff}.@code{connectArpeggios}.
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-cross-staff-arpeggios-in-a-piano-staff.ly}
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
-\new PianoStaff <<
- \set PianoStaff.connectArpeggios = ##t
- \new Staff { <c' e g c>\arpeggio }
- \new Staff { \clef bass <c,, e g>\arpeggio }
->>
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-cross-staff-arpeggios-in-other-contexts.ly}
-The same can be accomplished in contexts other than
-@code{PianoStaff} if the @code{Span_arpeggio_engraver} is included
-in the Score context.
-
-@lilypond[verbatim,quote,ragged-right]
-\score {
- \new StaffGroup {
- \set Score.connectArpeggios = ##t
- <<
- \new Voice \relative c' {
- <e g>4\arpeggio
- }
- \new Voice \relative c {
- \clef bass
- <c e>4\arpeggio
- }
- >>
- }
- \layout {
- \context {
- \Score
- \consists "Span_arpeggio_engraver"
- }
- }
-}
-@end lilypond
-
-Similarly, an arpeggio can be drawn across notes in different
-voices on the same staff if the @code{Span_arpeggio_engraver} is
-moved to the Staff context:
-
-@lilypond[verbatim,quote,ragged-right]
-\new Staff
-\with {
- \consists "Span_arpeggio_engraver"
-} \relative c' {
- \set Staff.connectArpeggios = ##t
- <<
- {<e' g>4\arpeggio <d f> <d f>2 }
- \\
- {<d, f>2\arpeggio <g b>2 }
- >>
-}
-@end lilypond
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{creating-arpeggios-across-notes-in-different-voices.ly}
@seealso
-Music Glossary: @rglos{arpeggio}, @rglos{broken chord}.
+@c TODO: Add 'broken chord' to glossary.
-Notation Reference: @ref{Ties}, for writing out arpeggios.
+Music Glossary:
+@rglos{arpeggio}.
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Notation Reference:
+@ref{Ties}.
-Internals Reference: @internalsref{Arpeggio},
-@internalsref{PianoStaff}.
+Snippets:
+@rlsr{Expressive marks}.
+
+Internals Reference:
+@rinternals{Arpeggio},
+@rinternals{PianoStaff}.
@knownissues
Short @notation{trills} are printed with @code{\trill} like normal
articulation; see @ref{Articulations and ornamentations}.
-Long running trills are made with @code{\startTrillSpan} and
-@code{\stopTrillSpan}. In the following example, it is shown in
-the common combination with grace notes. If a more precise
-control of the placement of the grace notes is needed, see
-@ref{Grace notes}.
+Long running @notation{trills} are made with
+@code{\startTrillSpan} and @code{\stopTrillSpan}. In the
+following example, a long running @notation{trill} is shown
+combined with grace notes. To achieve precise control of the
+placement of the grace notes, see @ref{Grace notes}.
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c1 \afterGrace
d1\startTrillSpan { c16[\stopTrillSpan d] }
c4
@end lilypond
@cindex pitched trills
+@cindex trills, pitched
+
+@notation{Trills} that should be executed on an explicitly
+specified pitch can be typeset with the command
+@code{\pitchedTrill} using the following syntax:
-Trills that should be executed on an explicitly specified pitch
-can be typeset with the command @code{\pitchedTrill}, and the
-syntax @code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
-@var{trillnote} @var{endnote} @code{\stopTrillSpan}.
+@example
+@code{\pitchedTrill} @var{mainnote} @code{\startTrillSpan}
+@var{trillnote} @var{endnote} @code{\stopTrillSpan}
+@end example
-@lilypond[verbatim,quote,ragged-right,fragment,relative=1]
+@lilypond[verbatim,quote,relative=1]
\pitchedTrill e2 \startTrillSpan fis
d\stopTrillSpan
@end lilypond
@seealso
-Music Glossary: @rglos{trill}
+Music Glossary:
+@rglos{trill}.
-Snippets: @lsrdir{Expressive,Expressive-marks}
+Snippets:
+@rlsr{Expressive marks}.
-Internals Reference: @internalsref{TrillSpanner}
+Internals Reference:
+@rinternals{TrillSpanner}.
projects / lilypond.git / blobdiff