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.
12 @section Staff notation
14 @lilypondfile[quote]{staff-headword.ly}
16 This section explains how to influence the appearance of staves,
17 how to print scores with more than one staff, and how to add tempo
18 indications and cue notes to staves.
22 * Modifying single staves::
27 @node Displaying staves
28 @subsection Displaying staves
30 This section describes the different methods of creating and
34 * Instantiating new staves::
36 * Nested staff groups::
40 @node Instantiating new staves
41 @unnumberedsubsubsec Instantiating new staves
44 @cindex staff initiation
45 @cindex staff instantiation
49 @cindex staff, percussion
51 @cindex percussion staff
52 @cindex Gregorian transcription staff
53 @cindex rhythmic staff
60 @funindex RhythmicStaff
62 @funindex MensuralStaff
63 @funindex VaticanaStaff
64 @funindex GregorianTranscriptionStaff
66 @notation{Staves} (singular: @notation{staff}) are created with
67 the @code{\new} or @code{\context} commands. For details, see
68 @ref{Creating contexts}.
70 The basic staff context is @code{Staff}:
72 @lilypond[verbatim,quote,relative=2]
73 \new Staff { c4 d e f }
76 The @code{DrumStaff} context creates a five-line staff set up for
77 a typical drum set. Each instrument is shown with a different
78 symbol. The instruments are entered in drum mode following a
79 @code{\drummode} command, with each instrument specified by name.
80 For details, see @ref{Percussion staves}.
82 @lilypond[verbatim,quote]
84 \drummode { cymc hh ss tomh }
88 @code{RhythmicStaff} creates a single-line staff that only
89 displays the rhythmic values of the input. Real durations are
90 preserved. For details, see @ref{Showing melody rhythms}.
92 @lilypond[verbatim,quote,relative=2]
93 \new RhythmicStaff { c4 d e f }
96 @code{TabStaff} creates a tablature with six strings in standard
97 guitar tuning. For details, see @ref{Default tablatures}.
99 @lilypond[verbatim,quote,relative=2]
100 \new TabStaff { c4 d e f }
103 There are two staff contexts specific for the notation of ancient
104 music: @code{MensuralStaff} and @code{VaticanaStaff}. They are
105 described in @ref{Pre-defined contexts}.
107 The @code{GregorianTranscriptionStaff} context creates a staff to
108 notate modern Gregorian chant. It does not show bar lines.
110 @lilypond[verbatim,quote,relative=2]
111 \new GregorianTranscriptionStaff { c4 d e f e d }
114 New single staff contexts may be defined. For details, see
115 @ref{Defining new contexts}.
124 @ref{Creating contexts},
125 @ref{Percussion staves},
126 @ref{Showing melody rhythms},
127 @ref{Default tablatures},
128 @ref{Pre-defined contexts},
130 @ref{Gregorian chant contexts},
131 @ref{Mensural contexts},
132 @ref{Defining new contexts}.
135 @rlsr{Staff notation}.
139 @rinternals{DrumStaff},
140 @rinternals{GregorianTranscriptionStaff},
141 @rinternals{RhythmicStaff},
142 @rinternals{TabStaff},
143 @rinternals{MensuralStaff},
144 @rinternals{VaticanaStaff},
145 @rinternals{StaffSymbol}.
148 @node Grouping staves
149 @unnumberedsubsubsec Grouping staves
151 @cindex start of system
152 @cindex staff, multiple
153 @cindex staves, multiple
154 @cindex system start delimiters
155 @cindex bracket, vertical
156 @cindex brace, vertical
166 Various contexts exist to group single staves together in order to
167 form multi-stave systems. Each grouping context sets the style of
168 the system start delimiter and the behavior of bar lines.
170 If no context is specified, the default properties will be used:
171 the group is started with a vertical line, and the bar lines are
174 @lilypond[verbatim,quote,relative=2]
181 In the @code{StaffGroup} context, the group is started with a
182 bracket and bar lines are drawn through all the staves.
184 @lilypond[verbatim,quote,relative=2]
191 In a @code{ChoirStaff}, the group starts with a bracket, but bar
192 lines are not connected.
194 @lilypond[verbatim,quote,relative=2]
201 In a @code{GrandStaff}, the group begins with a brace, and bar
202 lines are connected between the staves.
204 @lilypond[verbatim,quote,relative=2]
211 The @code{PianoStaff} is identical to a @code{GrandStaff}, except
212 that it supports printing the instrument name directly. For
213 details, see @ref{Instrument names}.
215 @lilypond[verbatim,quote,relative=2]
217 \set PianoStaff.instrumentName = #"Piano"
223 Each staff group context sets the property
224 @code{systemStartDelimiter} to one of the following values:
225 @code{SystemStartBar}, @code{SystemStartBrace}, or
226 @code{SystemStartBracket}. A fourth delimiter,
227 @code{SystemStartSquare}, is also available, but it must be
228 explicitly specified.
230 New staff group contexts may be defined. For details, see
231 @ref{Defining new contexts}.
236 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
237 {use-square-bracket-at-the-start-of-a-staff-group.ly}
239 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
240 {display-bracket-with-only-one-staff-in-a-system.ly}
242 @cindex mensurstriche layout
243 @cindex renaissance music
244 @cindex transcription of mensural music
245 @cindex mensural music, transcription of
247 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
248 {mensurstriche-layout-bar-lines-between-the-staves.ly}
258 @ref{Instrument names},
259 @ref{Defining new contexts}.
262 @rlsr{Staff notation}.
266 @rinternals{StaffGroup},
267 @rinternals{ChoirStaff},
268 @rinternals{GrandStaff},
269 @rinternals{PianoStaff},
270 @rinternals{SystemStartBar},
271 @rinternals{SystemStartBrace},
272 @rinternals{SystemStartBracket},
273 @rinternals{SystemStartSquare}.
276 @node Nested staff groups
277 @unnumberedsubsubsec Nested staff groups
279 @cindex staff, nested
280 @cindex staves, nested
281 @cindex nesting of staves
282 @cindex system start delimiters, nested
283 @cindex nested staff brackets
284 @cindex brackets, nesting of
285 @cindex braces, nesting of
287 Staff-group contexts can be nested to arbitrary depths. In this
288 case, each child context creates a new bracket adjacent to the
289 bracket of its parent group.
291 @lilypond[verbatim,quote,relative=2]
293 \new Staff { c2 c | c2 c }
295 \new Staff { g2 g | g2 g }
296 \new StaffGroup \with {
297 systemStartDelimiter = #'SystemStartSquare
300 \new Staff { e2 e | e2 e }
301 \new Staff { c2 c | c2 c }
307 New nested staff group contexts can be defined. For details, see
308 @ref{Defining new contexts}.
313 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
319 @ref{Grouping staves},
320 @ref{Instrument names},
321 @ref{Defining new contexts}.
324 @rlsr{Staff notation}.
327 @rinternals{StaffGroup},
328 @rinternals{ChoirStaff},
329 @rinternals{SystemStartBar},
330 @rinternals{SystemStartBrace},
331 @rinternals{SystemStartBracket},
332 @rinternals{SystemStartSquare}.
335 @node Modifying single staves
336 @subsection Modifying single staves
338 This section explains how to change specific attributes of one
339 staff: for example, modifying the number of staff lines or the
340 staff size. Methods to start and stop staves and set ossia
341 sections are also described.
351 @unnumberedsubsubsec Staff symbol
353 @cindex adjusting staff symbol
354 @cindex drawing staff symbol
355 @cindex staff symbol, setting of
356 @cindex staff symbol, drawing
357 @cindex stop staff lines
358 @cindex start staff lines
359 @cindex staff lines, amount of
360 @cindex staff lines, number of
361 @cindex staff line, thickness of
362 @cindex amount of staff lines
363 @cindex thickness of staff lines
364 @cindex ledger lines, setting
365 @cindex setting of ledger lines
366 @cindex spacing of ledger lines
367 @cindex number of staff lines
369 The lines of a staff belong to the @code{StaffSymbol} grob.
370 @code{StaffSymbol} properties can be modified to change the
371 appearance of a staff, but they must be modified before the staff
374 The number of staff lines may be changed. The clef position and
375 the position of middle C may need to be modified to fit the new
376 staff. For an explanation, refer to the snippet section in
379 @lilypond[verbatim,quote,relative=2]
381 \override StaffSymbol #'line-count = #3
386 Staff line thickness can be modified. The thickness of ledger
387 lines and stems are also affected, since they depend on staff line
390 @lilypond[verbatim,quote,relative=1]
392 \override StaffSymbol #'thickness = #3
397 Ledger line thickness can be set independently of staff line
398 thickness. In the example the two numbers are factors multiplying
399 the staff line thickness and the staff line spacing. The two
400 contributions are added to give the ledger line thickness.
402 @lilypond[verbatim,quote,relative=1]
404 \override StaffSymbol #'ledger-line-thickness = #'(1 . 0.2)
409 The distance between staff lines can be changed. This setting
410 affects the spacing of ledger lines as well.
412 @lilypond[verbatim,quote,relative=1]
414 \override StaffSymbol #'staff-space = #1.5
419 Further details about the properties of @code{StaffSymbol} can be
420 found in @rinternals{staff-symbol-interface}.
422 @cindex stopping a staff
423 @cindex starting a staff
424 @cindex staff, starting
425 @cindex staff, stopping
427 @funindex \startStaff
432 Modifications to staff properties in the middle of a score can be
433 placed between @code{\stopStaff} and @code{\startStaff}:
435 @lilypond[verbatim,quote,relative=2]
438 \override Staff.StaffSymbol #'line-count = #2
442 \revert Staff.StaffSymbol #'line-count
448 In general, @code{\startStaff} and @code{\stopStaff} can be used
449 to stop or start a staff in the middle of a score.
451 @lilypond[verbatim,quote,relative=2]
468 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
469 {making-some-staff-lines-thicker-than-the-others.ly}
482 @rlsr{Staff notation}.
485 @rinternals{StaffSymbol},
486 @rinternals{staff-symbol-interface}.
490 @unnumberedsubsubsec Ossia staves
492 @cindex staff, Frenched
494 @cindex Frenched staves
495 @cindex staff, resizing of
496 @cindex resizing of staves
498 @funindex \startStaff
503 @notation{Ossia} staves can be set by creating a new simultaneous
504 staff in the appropriate location:
506 @lilypond[verbatim,quote]
507 \new Staff \relative c'' {
511 \new Staff { e4 d f e }
518 However, the above example is not what is usually desired. To
519 create ossia staves that are above the original staff, have no
520 time signature or clef, and have a smaller font size, tweaks must
521 be used. The Learning Manual describes a specific technique to
522 achieve this goal, beginning with
523 @rlearning{Nesting music expressions}.
525 The following example uses the @code{alignAboveContext} property
526 to align the ossia staff. This method is most appropriate when
527 only a few ossia staves are needed.
529 @lilypond[verbatim,quote]
530 \new Staff = main \relative c'' {
536 \remove "Time_signature_engraver"
537 alignAboveContext = #"main"
539 \override StaffSymbol #'staff-space = #(magstep -3)
540 \override StaffSymbol #'thickness = #(magstep -3)
549 If many isolated ossia staves are needed, creating an empty
550 @code{Staff} context with a specific @emph{context id} may be more
551 appropriate; the ossia staves may then be created by
552 @emph{calling} this context and using @code{\startStaff} and
553 @code{\stopStaff} at the desired locations. The benefits of this
554 method are more apparent if the piece is longer than the following
557 @lilypond[verbatim,quote,ragged-right]
559 \new Staff = ossia \with {
560 \remove "Time_signature_engraver"
561 \override Clef #'transparent = ##t
563 \override StaffSymbol #'staff-space = #(magstep -3)
564 \override StaffSymbol #'thickness = #(magstep -3)
568 \new Staff \relative c' {
572 \context Staff = ossia {
573 \startStaff e4 g8 f e2 \stopStaff
580 \context Staff = ossia {
581 \startStaff g4 e8 f g2 \stopStaff
590 Using the @code{\RemoveEmptyStaffContext} command to create ossia
591 staves may be used as an alternative. This method is most
592 convenient when ossia staves occur immediately following a line
593 break. For more information about
594 @code{\RemoveEmptyStaffContext}, see @ref{Hiding staves}.
596 @lilypond[verbatim,quote,ragged-right]
598 \new Staff = ossia \with {
599 \remove "Time_signature_engraver"
600 \override Clef #'transparent = ##t
602 \override StaffSymbol #'staff-space = #(magstep -3)
603 \override StaffSymbol #'thickness = #(magstep -3)
609 \new Staff \relative c' {
621 \RemoveEmptyStaffContext
622 \override VerticalAxisGroup #'remove-first = ##t
630 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
631 {vertically-aligning-ossias-and-lyrics.ly}
638 @rglos{Frenched staff}.
641 @rlearning{Nesting music expressions},
642 @rlearning{Size of objects},
643 @rlearning{Length and thickness of objects}.
649 @rlsr{Staff notation}.
652 @rinternals{StaffSymbol}.
656 @unnumberedsubsubsec Hiding staves
658 @cindex Frenched score
659 @cindex Frenched staff
660 @cindex staff, hiding
662 @cindex hiding of staves
665 @funindex \RemoveEmptyStaffContext
666 @funindex RemoveEmptyStaffContext
667 @funindex Staff_symbol_engraver
672 Staff lines can be hidden by removing the
673 @code{Staff_symbol_engraver} from the @code{Staff} context. As an
674 alternative, @code{\stopStaff} may be used.
676 @lilypond[verbatim,quote]
678 \remove "Staff_symbol_engraver"
680 \relative c''' { a8 f e16 d c b a2 }
684 Empty staves can be hidden by setting the
685 @code{\RemoveEmptyStaffContext} command in the @code{\layout}
686 block. In orchestral scores, this style is known as @q{Frenched
687 Score}. By default, this command hides and removes all empty
688 staves in a score except for those in the first system.
690 @warning{A staff is considered empty when it contains only
691 multi-measure rests, skips, spacer rests, or a combination of these
694 @lilypond[verbatim,quote,ragged-right]
697 \RemoveEmptyStaffContext
718 @code{\RemoveEmptyStaffContext} can also be used to create ossia
719 sections for a staff. For details, see @ref{Ossia staves}.
721 @cindex hiding ancient staves
722 @cindex hiding rhythmic staves
724 @funindex \RemoveEmptyStaffContext
725 @funindex RemoveEmptyStaffContext
726 @funindex \AncientRemoveEmptyStaffContext
727 @funindex AncientRemoveEmptyStaffContext
728 @funindex \RemoveEmptyRhythmicStaffContext
729 @funindex RemoveEmptyRhythmicStaffContext
731 The @code{\AncientRemoveEmptyStaffContext} command may be used to
732 hide empty staves in ancient music contexts. Similarly,
733 @code{\RemoveEmptyRhythmicStaffContext} may be used to hide empty
734 @code{RhythmicStaff} contexts.
738 @code{\RemoveEmptyStaffContext},
739 @code{\AncientRemoveEmptyStaffContext},
740 @code{\RemoveEmptyRhythmicStaffContext}.
746 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
747 {removing-the-first-empty-line.ly}
752 @rglos{Frenched staff}.
759 @rlsr{Staff notation}.
762 @rinternals{ChordNames},
763 @rinternals{FiguredBass},
766 @rinternals{VerticalAxisGroup},
767 @rinternals{Staff_symbol_engraver}.
772 Removing @code{Staff_symbol_engraver} also hides bar lines. If
773 bar line visibility is forced, formatting errors may occur. In
774 this case, use the following overrides instead of removing the
778 \override StaffSymbol #'stencil = ##f
779 \override NoteHead #'no-ledgers = ##t
784 @subsection Writing parts
786 This section explains how to insert tempo indications and
787 instrument names into a score. Methods to quote other voices and
788 format cue notes are also described.
793 * Quoting other voices::
794 * Formatting cue notes::
798 @node Metronome marks
799 @unnumberedsubsubsec Metronome marks
802 @cindex beats per minute
803 @cindex metronome mark
804 @cindex metronome marking with text
809 A basic metronome mark is simple to write:
811 @lilypond[verbatim,quote,relative=1]
817 Tempo indications with text can be used instead:
819 @lilypond[verbatim,quote,relative=2]
825 Combining a metronome mark and text will automatically place the
826 metronome mark within parentheses:
828 @lilypond[verbatim,quote,relative=2]
829 \tempo "Allegro" 4 = 160
834 In general, the text can be any markup object:
836 @lilypond[verbatim,quote,relative=2]
837 \tempo \markup { \italic Faster } 4 = 132
838 a8-. r8 b-. r gis-. r a-. r
841 A parenthesized metronome mark with no textual indication may be
842 written by including an empty string in the input:
844 @lilypond[verbatim,quote,relative=2]
852 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
853 {printing-metronome-and-rehearsal-marks-below-the-staff.ly}
855 @c perhaps also an example of how to move it horizontally?
857 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
858 {changing-the-tempo-without-a-metronome-mark.ly}
860 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
861 {creating-metronome-marks-in-markup-mode.ly}
863 For more details, see @ref{Formatting text}.
869 @rglos{metronomic indication},
870 @rglos{tempo indication},
871 @rglos{metronome mark}.
874 @ref{Formatting text},
878 @rlsr{Staff notation}.
881 @rinternals{MetronomeMark}.
884 @node Instrument names
885 @unnumberedsubsubsec Instrument names
887 @cindex instrument names
888 @cindex instrument names, short
890 Instrument names can be printed on the left side of staves in the
891 @code{Staff} and @code{PianoStaff} contexts. The value of
892 @code{instrumentName} is used for the first staff, and the value
893 of @code{shortInstrumentName} is used for all succeeding staves.
895 @lilypond[verbatim,quote,ragged-right,relative=1]
896 \set Staff.instrumentName = #"Violin "
897 \set Staff.shortInstrumentName = #"Vln "
903 Markup mode can be used to create more complicated instrument
906 @lilypond[verbatim,quote,relative=2]
907 \set Staff.instrumentName = \markup {
908 \column { "Clarinetti"
909 \line { "in B" \smaller \flat } } }
913 @cindex instrument names, centering
915 When two or more staff contexts are grouped together, the
916 instrument names and short instrument names are centered by
917 default. To center multi-line instrument names,
918 @code{\center-column} must be used:
920 @lilypond[verbatim,quote,indent=1.5\cm,relative=2]
923 \set Staff.instrumentName = #"Flute"
927 \set Staff.instrumentName = \markup \center-column {
929 \line { "in B" \smaller \flat }
937 @funindex short-indent
939 However, if the instrument names are longer, the instrument names
940 in a staff group may not be centered unless the @code{indent} and
941 @code{short-indent} settings are increased. For details about
942 these settings, see @ref{Horizontal dimensions}.
944 @lilypond[verbatim,quote,ragged-right]
947 short-indent = 1.5\cm
952 \set Staff.instrumentName = #"Alto Flute in G"
953 \set Staff.shortInstrumentName = #"Fl."
958 \set Staff.instrumentName = #"Clarinet"
959 \set Staff.shortInstrumentName = #"Clar."
966 @cindex instrument names, adding to other contexts
968 To add instrument names to other contexts (such as
969 @code{GrandStaff}, @code{ChoirStaff}, or @code{StaffGroup}),
970 @code{Instrument_name_engraver} must be added to that context.
971 For details, see @ref{Modifying context plug-ins}.
973 @cindex instrument names, changing
974 @cindex changing instrument names
976 Instrument names may be changed in the middle of a piece:
978 @lilypond[verbatim,quote,ragged-right,relative=1]
979 \set Staff.instrumentName = #"First"
980 \set Staff.shortInstrumentName = #"one"
983 \set Staff.instrumentName = #"Second"
984 \set Staff.shortInstrumentName = #"two"
989 @cindex instrument switch
990 @cindex switching instruments
992 @funindex \addInstrumentDefinition
993 @funindex addInstrumentDefinition
994 @funindex \instrumentSwitch
995 @funindex instrumentSwitch
997 If an instrument @emph{switch} is needed,
998 @code{\addInstrumentDefinition} may be used in combination with
999 @code{\instrumentSwitch} to create a detailed list of the
1000 necessary changes for the switch. The
1001 @code{\addInstrumentDefinition} command has two arguments: an
1002 identifying string, and an association list of context properties
1003 and values to be used for the instrument. It must be placed in
1004 the toplevel scope. @code{\instrumentSwitch} is used in the music
1005 expression to declare the instrument switch:
1007 @lilypond[verbatim,quote,ragged-right]
1008 \addInstrumentDefinition #"contrabassoon"
1009 #`((instrumentTransposition . ,(ly:make-pitch -1 0 0))
1010 (shortInstrumentName . "Cbsn.")
1011 (clefGlyph . "clefs.F")
1012 (middleCPosition . 6)
1014 (instrumentCueName . ,(make-bold-markup "cbsn."))
1015 (midiInstrument . "bassoon"))
1018 instrumentName = #"Bassoon"
1022 \compressFullBarRests
1025 \instrumentSwitch "contrabassoon"
1034 @ref{Horizontal dimensions},
1035 @ref{Modifying context plug-ins}.
1038 @rlsr{Staff notation}.
1040 Internals Reference:
1041 @rinternals{InstrumentName},
1042 @rinternals{PianoStaff},
1046 @node Quoting other voices
1047 @unnumberedsubsubsec Quoting other voices
1050 @cindex quoting other voices
1056 @funindex \quoteDuring
1057 @funindex quoteDuring
1058 @funindex \transposition
1059 @funindex transposition
1061 It is very common for one voice to double some of the music from
1062 another voice. For example, the first and second violins may play the
1063 same notes during a passage of music. In LilyPond this is accomplished
1064 by letting one voice @emph{quote} the other voice without having to
1067 Before a part can be quoted, the @code{\addQuote} command must be used
1068 to initialize the quoted fragment. This command must be used in the
1069 toplevel scope. The first argument is an identifying string, and the
1070 second is a music expression:
1073 flute = \relative c'' @{
1076 \addQuote "flute" @{ \flute @}
1079 The @code{\quoteDuring} command is used to indicate the point where the
1080 quotation begins. It is followed by two arguments: the name of the
1081 quoted voice, as defined with @code{\addQuote}, and a music expression
1082 that indicates the duration of the quote, usually spacer rests or
1083 multi-measure rests. The corresponding music from the quoted voice is
1084 inserted into the music expression:
1086 @lilypond[verbatim,quote]
1087 flute = \relative c'' {
1090 \addQuote "flute" { \flute }
1093 c4 cis \quoteDuring #"flute" { s2 }
1097 If the music expression used for @code{\quoteDuring} contains
1098 anything but a spacer rest or multi-measure rest, a polyphonic
1099 situation is created, which is often not desirable:
1101 @lilypond[verbatim,quote]
1102 flute = \relative c'' {
1105 \addQuote "flute" { \flute }
1108 c4 cis \quoteDuring #"flute" { c4 b }
1112 Quotations recognize instrument transposition settings for both
1113 the source and target instruments if the @code{\transposition}
1114 command is used. For details about @code{\transposition}, see
1115 @ref{Instrument transpositions}.
1117 @lilypond[verbatim,quote]
1118 clarinet = \relative c'' {
1122 \addQuote "clarinet" { \clarinet }
1125 c4 cis \quoteDuring #"clarinet" { s2 }
1129 It is possible to tag quotations with unique names in order to
1130 process them in different ways. For details about this procedure,
1131 see @ref{Using tags}.
1136 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1137 {quoting-another-voice-with-transposition.ly}
1140 @cindex articulation-event
1141 @cindex dynamic-event
1144 @funindex quotedEventTypes
1146 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1147 {quoting-another-voice.ly}
1152 @ref{Instrument transpositions},
1156 @rlsr{Staff notation}.
1158 Internals Reference:
1159 @rinternals{QuoteMusic},
1165 Only the contents of the first @code{Voice} occurring in an
1166 @code{\addQuote} command will be considered for quotation, so
1167 @var{music} cannot contain @code{\new} and @code{\context Voice}
1168 statements that would switch to a different Voice.
1170 Quoting grace notes is broken and can even cause LilyPond to
1173 Quoting nested triplets may result in poor notation.
1175 In earlier versions of LilyPond (pre 2.11), @code{addQuote} was
1176 written entirely in lower-case letters: @code{\addquote}.
1179 @node Formatting cue notes
1180 @unnumberedsubsubsec Formatting cue notes
1184 @cindex cue notes, formatting
1186 @cindex quoting other voices
1187 @cindex cues, formatting
1189 @funindex \cueDuring
1191 @funindex \quoteDuring
1192 @funindex quoteDuring
1194 The previous section explains how to create quotations. The
1195 @code{\cueDuring} command is a more specialized form of
1196 @code{\quoteDuring}, being particularly useful for inserting cue
1197 notes into a part. The syntax is as follows:
1200 \cueDuring #@var{partname} #@var{voice} @var{music}
1203 This command copies the corresponding measures from @var{partname}
1204 into a @code{CueVoice} context. The @code{CueVoice} is created
1205 implicitly, and occurs simultaneously with @var{music}, which
1206 creates a polyphonic situation. The @var{voice} argument
1207 determines whether the cue notes should be notated as a first or
1208 second voice; @code{UP} corresponds to the first voice, and
1209 @code{DOWN} corresponds to the second.
1211 @lilypond[verbatim,quote]
1212 oboe = \relative c'' {
1216 \addQuote "oboe" { \oboe }
1218 \new Voice \relative c'' {
1219 \cueDuring #"oboe" #UP { R1 }
1225 In the above example, the @code{Voice} context had to be
1226 explicitly declared, or else the entire music expression would
1227 belong to the @code{CueVoice} context.
1229 The name of the cued instrument can be printed by setting the
1230 @code{instrumentCueName} property in the @code{CueVoice} context.
1232 @lilypond[verbatim,quote]
1233 oboe = \relative c''' {
1236 \addQuote "oboe" { \oboe }
1238 \new Staff \relative c'' <<
1239 \new CueVoice \with {
1240 instrumentCueName = "ob."
1243 \cueDuring #"oboe" #UP { R1 }
1249 @cindex removing cues
1250 @cindex removing cue notes
1251 @cindex cue notes, removing
1255 @funindex \transposedCueDuring
1256 @funindex transposedCueDuring
1258 In addition to printing the name of the cued instrument, when cue
1259 notes end, the name of the original instrument should be printed,
1260 and any other changes introduced by the cued part should be
1261 undone. This can be accomplished by using
1262 @code{\addInstrumentDefinition} and @code{\instrumentSwitch}. For
1263 an example and explanation, see @ref{Instrument names}.
1265 The @code{\killCues} command removes cue notes from a music
1266 expression. This can be useful if cue notes need to be removed
1267 from a part but may be restored at a later time.
1269 @lilypond[verbatim,quote]
1270 flute = \relative c''' {
1273 \addQuote "flute" { \flute }
1275 \new Voice \relative c'' {
1277 \cueDuring #"flute" #UP { R1 }
1283 The @code{\transposedCueDuring} command is useful for adding
1284 instrumental cues from a completely different register. The
1285 syntax is similar to @code{\cueDuring}, but it requires one extra
1286 argument to specify the transposition of the cued instrument. For
1287 more information about transposition, see
1288 @ref{Instrument transpositions}.
1290 @lilypond[verbatim,quote]
1291 piccolo = \relative c''' {
1297 \addQuote "piccolo" { \piccolo }
1299 cbassoon = \relative c, {
1302 \transposedCueDuring #"piccolo" #UP c,, { R1 }
1307 \new Staff = "piccolo" \piccolo
1308 \new Staff = "cbassoon" \cbassoon
1312 It is possible to tag cued parts with unique names in order to
1313 process them in different ways. For details about this procedure,
1314 see @ref{Using tags}.
1319 @ref{Instrument transpositions},
1320 @ref{Instrument names},
1324 @rlsr{Staff notation}.
1326 Internals Reference:
1327 @rinternals{CueVoice},
1333 Collisions can occur with rests, when using @code{\cueDuring},
1334 between @code{Voice} and @code{CueVoice} contexts.