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)
608 \new Staff \relative c' {
620 \RemoveEmptyStaffContext
621 \override VerticalAxisGroup #'remove-first = ##t
629 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
630 {vertically-aligning-ossias-and-lyrics.ly}
637 @rglos{Frenched staff}.
640 @rlearning{Nesting music expressions},
641 @rlearning{Size of objects},
642 @rlearning{Length and thickness of objects}.
648 @rlsr{Staff notation}.
651 @rinternals{StaffSymbol}.
655 @unnumberedsubsubsec Hiding staves
657 @cindex Frenched score
658 @cindex Frenched staff
659 @cindex staff, hiding
661 @cindex hiding of staves
664 @funindex \RemoveEmptyStaffContext
665 @funindex RemoveEmptyStaffContext
666 @funindex Staff_symbol_engraver
671 Staff lines can be hidden by removing the
672 @code{Staff_symbol_engraver} from the @code{Staff} context. As an
673 alternative, @code{\stopStaff} may be used.
675 @lilypond[verbatim,quote]
677 \remove "Staff_symbol_engraver"
679 \relative c''' { a8 f e16 d c b a2 }
683 Empty staves can be hidden by setting the
684 @code{\RemoveEmptyStaffContext} command in the @code{\layout}
685 block. In orchestral scores, this style is known as @q{Frenched
686 Score}. By default, this command hides and removes all empty
687 staves in a score except for those in the first system.
689 @warning{A staff is considered empty when it contains only
690 multi-measure rests, skips, spacer rests, or a combination of these
693 @lilypond[verbatim,quote,ragged-right]
696 \RemoveEmptyStaffContext
717 @code{\RemoveEmptyStaffContext} can also be used to create ossia
718 sections for a staff. For details, see @ref{Ossia staves}.
720 @cindex hiding ancient staves
721 @cindex hiding rhythmic staves
723 @funindex \RemoveEmptyStaffContext
724 @funindex RemoveEmptyStaffContext
725 @funindex \AncientRemoveEmptyStaffContext
726 @funindex AncientRemoveEmptyStaffContext
727 @funindex \RemoveEmptyRhythmicStaffContext
728 @funindex RemoveEmptyRhythmicStaffContext
730 The @code{\AncientRemoveEmptyStaffContext} command may be used to
731 hide empty staves in ancient music contexts. Similarly,
732 @code{\RemoveEmptyRhythmicStaffContext} may be used to hide empty
733 @code{RhythmicStaff} contexts.
737 @code{\RemoveEmptyStaffContext},
738 @code{\AncientRemoveEmptyStaffContext},
739 @code{\RemoveEmptyRhythmicStaffContext}.
745 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
746 {removing-the-first-empty-line.ly}
751 @rglos{Frenched staff}.
758 @rlsr{Staff notation}.
761 @rinternals{ChordNames},
762 @rinternals{FiguredBass},
765 @rinternals{VerticalAxisGroup},
766 @rinternals{Staff_symbol_engraver}.
771 Removing @code{Staff_symbol_engraver} also hides bar lines. If
772 bar line visibility is forced, formatting errors may occur. In
773 this case, use the following overrides instead of removing the
777 \override StaffSymbol #'stencil = ##f
778 \override NoteHead #'no-ledgers = ##t
783 @subsection Writing parts
785 This section explains how to insert tempo indications and
786 instrument names into a score. Methods to quote other voices and
787 format cue notes are also described.
792 * Quoting other voices::
793 * Formatting cue notes::
797 @node Metronome marks
798 @unnumberedsubsubsec Metronome marks
801 @cindex beats per minute
802 @cindex metronome mark
803 @cindex metronome marking with text
808 A basic metronome mark is simple to write:
810 @lilypond[verbatim,quote,relative=1]
816 Tempo indications with text can be used instead:
818 @lilypond[verbatim,quote,relative=2]
824 Combining a metronome mark and text will automatically place the
825 metronome mark within parentheses:
827 @lilypond[verbatim,quote,relative=2]
828 \tempo "Allegro" 4 = 160
833 In general, the text can be any markup object:
835 @lilypond[verbatim,quote,relative=2]
836 \tempo \markup { \italic Faster } 4 = 132
837 a8-. r8 b-. r gis-. r a-. r
840 A parenthesized metronome mark with no textual indication may be
841 written by including an empty string in the input:
843 @lilypond[verbatim,quote,relative=2]
851 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
852 {printing-metronome-and-rehearsal-marks-below-the-staff.ly}
854 @c perhaps also an example of how to move it horizontally?
856 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
857 {changing-the-tempo-without-a-metronome-mark.ly}
859 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
860 {creating-metronome-marks-in-markup-mode.ly}
862 For more details, see @ref{Formatting text}.
868 @rglos{metronomic indication},
869 @rglos{tempo indication},
870 @rglos{metronome mark}.
873 @ref{Formatting text},
877 @rlsr{Staff notation}.
880 @rinternals{MetronomeMark}.
883 @node Instrument names
884 @unnumberedsubsubsec Instrument names
886 @cindex instrument names
887 @cindex instrument names, short
889 Instrument names can be printed on the left side of staves in the
890 @code{Staff} and @code{PianoStaff} contexts. The value of
891 @code{instrumentName} is used for the first staff, and the value
892 of @code{shortInstrumentName} is used for all succeeding staves.
894 @lilypond[verbatim,quote,ragged-right,relative=1]
895 \set Staff.instrumentName = #"Violin "
896 \set Staff.shortInstrumentName = #"Vln "
902 Markup mode can be used to create more complicated instrument
905 @lilypond[verbatim,quote,relative=2]
906 \set Staff.instrumentName = \markup {
907 \column { "Clarinetti"
908 \line { "in B" \smaller \flat } } }
912 @cindex instrument names, centering
914 When two or more staff contexts are grouped together, the
915 instrument names and short instrument names are centered by
916 default. To center multi-line instrument names,
917 @code{\center-column} must be used:
919 @lilypond[verbatim,quote,indent=1.5\cm,relative=2]
922 \set Staff.instrumentName = #"Flute"
926 \set Staff.instrumentName = \markup \center-column {
928 \line { "in B" \smaller \flat }
936 @funindex short-indent
938 However, if the instrument names are longer, the instrument names
939 in a staff group may not be centered unless the @code{indent} and
940 @code{short-indent} settings are increased. For details about
941 these settings, see @ref{Horizontal dimensions}.
943 @lilypond[verbatim,quote,ragged-right]
946 short-indent = 1.5\cm
951 \set Staff.instrumentName = #"Alto Flute in G"
952 \set Staff.shortInstrumentName = #"Fl."
957 \set Staff.instrumentName = #"Clarinet"
958 \set Staff.shortInstrumentName = #"Clar."
965 @cindex instrument names, adding to other contexts
967 To add instrument names to other contexts (such as
968 @code{GrandStaff}, @code{ChoirStaff}, or @code{StaffGroup}),
969 @code{Instrument_name_engraver} must be added to that context.
970 For details, see @ref{Modifying context plug-ins}.
972 @cindex instrument names, changing
973 @cindex changing instrument names
975 Instrument names may be changed in the middle of a piece:
977 @lilypond[verbatim,quote,ragged-right,relative=1]
978 \set Staff.instrumentName = #"First"
979 \set Staff.shortInstrumentName = #"one"
982 \set Staff.instrumentName = #"Second"
983 \set Staff.shortInstrumentName = #"two"
988 @cindex instrument switch
989 @cindex switching instruments
991 @funindex \addInstrumentDefinition
992 @funindex addInstrumentDefinition
993 @funindex \instrumentSwitch
994 @funindex instrumentSwitch
996 If an instrument @emph{switch} is needed,
997 @code{\addInstrumentDefinition} may be used in combination with
998 @code{\instrumentSwitch} to create a detailed list of the
999 necessary changes for the switch. The
1000 @code{\addInstrumentDefinition} command has two arguments: an
1001 identifying string, and an association list of context properties
1002 and values to be used for the instrument. It must be placed in
1003 the toplevel scope. @code{\instrumentSwitch} is used in the music
1004 expression to declare the instrument switch:
1006 @lilypond[verbatim,quote,ragged-right]
1007 \addInstrumentDefinition #"contrabassoon"
1008 #`((instrumentTransposition . ,(ly:make-pitch -1 0 0))
1009 (shortInstrumentName . "Cbsn.")
1010 (clefGlyph . "clefs.F")
1011 (middleCPosition . 6)
1013 (instrumentCueName . ,(make-bold-markup "cbsn."))
1014 (midiInstrument . "bassoon"))
1017 instrumentName = #"Bassoon"
1021 \compressFullBarRests
1024 \instrumentSwitch "contrabassoon"
1033 @ref{Horizontal dimensions},
1034 @ref{Modifying context plug-ins}.
1037 @rlsr{Staff notation}.
1039 Internals Reference:
1040 @rinternals{InstrumentName},
1041 @rinternals{PianoStaff},
1045 @node Quoting other voices
1046 @unnumberedsubsubsec Quoting other voices
1049 @cindex quoting other voices
1055 @funindex \quoteDuring
1056 @funindex quoteDuring
1057 @funindex \transposition
1058 @funindex transposition
1060 It is very common for one voice to double some of the music from
1061 another voice. For example, the first and second violins may play the
1062 same notes during a passage of music. In LilyPond this is accomplished
1063 by letting one voice @emph{quote} the other voice without having to
1066 Before a part can be quoted, the @code{\addQuote} command must be used
1067 to initialize the quoted fragment. This command must be used in the
1068 toplevel scope. The first argument is an identifying string, and the
1069 second is a music expression:
1072 flute = \relative c'' @{
1075 \addQuote "flute" @{ \flute @}
1078 The @code{\quoteDuring} command is used to indicate the point where the
1079 quotation begins. It is followed by two arguments: the name of the
1080 quoted voice, as defined with @code{\addQuote}, and a music expression
1081 that indicates the duration of the quote, usually spacer rests or
1082 multi-measure rests. The corresponding music from the quoted voice is
1083 inserted into the music expression:
1085 @lilypond[verbatim,quote]
1086 flute = \relative c'' {
1089 \addQuote "flute" { \flute }
1092 c4 cis \quoteDuring #"flute" { s2 }
1096 If the music expression used for @code{\quoteDuring} contains
1097 anything but a spacer rest or multi-measure rest, a polyphonic
1098 situation is created, which is often not desirable:
1100 @lilypond[verbatim,quote]
1101 flute = \relative c'' {
1104 \addQuote "flute" { \flute }
1107 c4 cis \quoteDuring #"flute" { c4 b }
1111 Quotations recognize instrument transposition settings for both
1112 the source and target instruments if the @code{\transposition}
1113 command is used. For details about @code{\transposition}, see
1114 @ref{Instrument transpositions}.
1116 @lilypond[verbatim,quote]
1117 clarinet = \relative c'' {
1121 \addQuote "clarinet" { \clarinet }
1124 c4 cis \quoteDuring #"clarinet" { s2 }
1128 It is possible to tag quotations with unique names in order to
1129 process them in different ways. For details about this procedure,
1130 see @ref{Using tags}.
1135 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1136 {quoting-another-voice-with-transposition.ly}
1139 @cindex articulation-event
1140 @cindex dynamic-event
1143 @funindex quotedEventTypes
1145 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1146 {quoting-another-voice.ly}
1151 @ref{Instrument transpositions},
1155 @rlsr{Staff notation}.
1157 Internals Reference:
1158 @rinternals{QuoteMusic},
1164 Only the contents of the first @code{Voice} occurring in an
1165 @code{\addQuote} command will be considered for quotation, so
1166 @var{music} cannot contain @code{\new} and @code{\context Voice}
1167 statements that would switch to a different Voice.
1169 Quoting grace notes is broken and can even cause LilyPond to
1172 Quoting nested triplets may result in poor notation.
1174 In earlier versions of LilyPond (pre 2.11), @code{addQuote} was
1175 written entirely in lower-case letters: @code{\addquote}.
1178 @node Formatting cue notes
1179 @unnumberedsubsubsec Formatting cue notes
1183 @cindex cue notes, formatting
1185 @cindex quoting other voices
1186 @cindex cues, formatting
1188 @funindex \cueDuring
1190 @funindex \quoteDuring
1191 @funindex quoteDuring
1193 The previous section explains how to create quotations. The
1194 @code{\cueDuring} command is a more specialized form of
1195 @code{\quoteDuring}, being particularly useful for inserting cue
1196 notes into a part. The syntax is as follows:
1199 \cueDuring #@var{partname} #@var{voice} @var{music}
1202 This command copies the corresponding measures from @var{partname}
1203 into a @code{CueVoice} context. The @code{CueVoice} is created
1204 implicitly, and occurs simultaneously with @var{music}, which
1205 creates a polyphonic situation. The @var{voice} argument
1206 determines whether the cue notes should be notated as a first or
1207 second voice; @code{UP} corresponds to the first voice, and
1208 @code{DOWN} corresponds to the second.
1210 @lilypond[verbatim,quote]
1211 oboe = \relative c'' {
1215 \addQuote "oboe" { \oboe }
1217 \new Voice \relative c'' {
1218 \cueDuring #"oboe" #UP { R1 }
1224 In the above example, the @code{Voice} context had to be
1225 explicitly declared, or else the entire music expression would
1226 belong to the @code{CueVoice} context.
1228 The name of the cued instrument can be printed by setting the
1229 @code{instrumentCueName} property in the @code{CueVoice} context.
1231 @lilypond[verbatim,quote]
1232 oboe = \relative c''' {
1235 \addQuote "oboe" { \oboe }
1237 \new Staff \relative c'' <<
1238 \new CueVoice \with {
1239 instrumentCueName = "ob."
1242 \cueDuring #"oboe" #UP { R1 }
1248 @cindex removing cues
1249 @cindex removing cue notes
1250 @cindex cue notes, removing
1254 @funindex \transposedCueDuring
1255 @funindex transposedCueDuring
1257 In addition to printing the name of the cued instrument, when cue
1258 notes end, the name of the original instrument should be printed,
1259 and any other changes introduced by the cued part should be
1260 undone. This can be accomplished by using
1261 @code{\addInstrumentDefinition} and @code{\instrumentSwitch}. For
1262 an example and explanation, see @ref{Instrument names}.
1264 The @code{\killCues} command removes cue notes from a music
1265 expression. This can be useful if cue notes need to be removed
1266 from a part but may be restored at a later time.
1268 @lilypond[verbatim,quote]
1269 flute = \relative c''' {
1272 \addQuote "flute" { \flute }
1274 \new Voice \relative c'' {
1276 \cueDuring #"flute" #UP { R1 }
1282 The @code{\transposedCueDuring} command is useful for adding
1283 instrumental cues from a completely different register. The
1284 syntax is similar to @code{\cueDuring}, but it requires one extra
1285 argument to specify the transposition of the cued instrument. For
1286 more information about transposition, see
1287 @ref{Instrument transpositions}.
1289 @lilypond[verbatim,quote]
1290 piccolo = \relative c''' {
1296 \addQuote "piccolo" { \piccolo }
1298 cbassoon = \relative c, {
1301 \transposedCueDuring #"piccolo" #UP c,, { R1 }
1306 \new Staff = "piccolo" \piccolo
1307 \new Staff = "cbassoon" \cbassoon
1311 It is possible to tag cued parts with unique names in order to
1312 process them in different ways. For details about this procedure,
1313 see @ref{Using tags}.
1318 @ref{Instrument transpositions},
1319 @ref{Instrument names},
1323 @rlsr{Staff notation}.
1325 Internals Reference:
1326 @rinternals{CueVoice},
1332 Collisions can occur with rests, when using @code{\cueDuring},
1333 between @code{Voice} and @code{CueVoice} contexts.