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..
13 @section Staff notation
15 @lilypondfile[quote]{staff-headword.ly}
17 This section explains how to influence the appearance of staves,
18 how to print scores with more than one staff, and how to add tempo
19 indications and cue notes to staves.
23 * Modifying single staves::
28 @node Displaying staves
29 @subsection Displaying staves
31 This section describes the different methods of creating and
35 * Instantiating new staves::
37 * Nested staff groups::
38 * Separating systems::
42 @node Instantiating new staves
43 @unnumberedsubsubsec Instantiating new staves
46 @cindex staff initiation
47 @cindex staff instantiation
51 @cindex staff, percussion
53 @cindex percussion staff
54 @cindex Gregorian transcription staff
55 @cindex rhythmic staff
62 @funindex RhythmicStaff
64 @funindex MensuralStaff
65 @funindex VaticanaStaff
66 @funindex GregorianTranscriptionStaff
68 @notation{Staves} (singular: @notation{staff}) are created with
69 the @code{\new} or @code{\context} commands. For details, see
70 @ref{Creating contexts}.
72 The basic staff context is @code{Staff}:
74 @lilypond[verbatim,quote,relative=2]
75 \new Staff { c4 d e f }
78 The @code{DrumStaff} context creates a five-line staff set up for
79 a typical drum set. Each instrument is shown with a different
80 symbol. The instruments are entered in drum mode following a
81 @code{\drummode} command, with each instrument specified by name.
82 For details, see @ref{Percussion staves}.
84 @lilypond[verbatim,quote]
86 \drummode { cymc hh ss tomh }
90 @code{RhythmicStaff} creates a single-line staff that only
91 displays the rhythmic values of the input. Real durations are
92 preserved. For details, see @ref{Showing melody rhythms}.
94 @lilypond[verbatim,quote,relative=2]
95 \new RhythmicStaff { c4 d e f }
98 @code{TabStaff} creates a tablature with six strings in standard
99 guitar tuning. For details, see @ref{Default tablatures}.
101 @lilypond[verbatim,quote,relative=2]
102 \new TabStaff { c4 d e f }
105 There are two staff contexts specific for the notation of ancient
106 music: @code{MensuralStaff} and @code{VaticanaStaff}. They are
107 described in @ref{Pre-defined contexts}.
109 The @code{GregorianTranscriptionStaff} context creates a staff to
110 notate modern Gregorian chant. It does not show bar lines.
112 @lilypond[verbatim,quote,relative=2]
113 \new GregorianTranscriptionStaff { c4 d e f e d }
116 New single staff contexts may be defined. For details, see
117 @ref{Defining new contexts}.
126 @ref{Creating contexts},
127 @ref{Percussion staves},
128 @ref{Showing melody rhythms},
129 @ref{Default tablatures},
130 @ref{Pre-defined contexts},
132 @ref{Gregorian chant contexts},
133 @ref{Mensural contexts},
134 @ref{Defining new contexts}.
137 @rlsr{Staff notation}.
141 @rinternals{DrumStaff},
142 @rinternals{GregorianTranscriptionStaff},
143 @rinternals{RhythmicStaff},
144 @rinternals{TabStaff},
145 @rinternals{MensuralStaff},
146 @rinternals{VaticanaStaff},
147 @rinternals{StaffSymbol}.
150 @node Grouping staves
151 @unnumberedsubsubsec Grouping staves
153 @cindex start of system
154 @cindex staff, multiple
155 @cindex staves, multiple
156 @cindex system start delimiters
157 @cindex bracket, vertical
158 @cindex brace, vertical
168 Various contexts exist to group single staves together in order to
169 form multi-stave systems. Each grouping context sets the style of
170 the system start delimiter and the behavior of bar lines.
172 If no context is specified, the default properties will be used:
173 the group is started with a vertical line, and the bar lines are
176 @lilypond[verbatim,quote,relative=2]
183 In the @code{StaffGroup} context, the group is started with a
184 bracket and bar lines are drawn through all the staves.
186 @lilypond[verbatim,quote,relative=2]
193 In a @code{ChoirStaff}, the group starts with a bracket, but bar
194 lines are not connected.
196 @lilypond[verbatim,quote,relative=2]
203 In a @code{GrandStaff}, the group begins with a brace, and bar
204 lines are connected between the staves.
206 @lilypond[verbatim,quote,relative=2]
213 The @code{PianoStaff} is identical to a @code{GrandStaff}, except
214 that it supports printing the instrument name directly. For
215 details, see @ref{Instrument names}.
217 @lilypond[verbatim,quote,relative=2]
219 \set PianoStaff.instrumentName = #"Piano"
225 Each staff group context sets the property
226 @code{systemStartDelimiter} to one of the following values:
227 @code{SystemStartBar}, @code{SystemStartBrace}, or
228 @code{SystemStartBracket}. A fourth delimiter,
229 @code{SystemStartSquare}, is also available, but it must be
230 explicitly specified.
232 New staff group contexts may be defined. For details, see
233 @ref{Defining new contexts}.
238 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
239 {use-square-bracket-at-the-start-of-a-staff-group.ly}
241 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
242 {display-bracket-with-only-one-staff-in-a-system.ly}
244 @cindex mensurstriche layout
245 @cindex renaissance music
246 @cindex transcription of mensural music
247 @cindex mensural music, transcription of
249 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
250 {mensurstriche-layout-bar-lines-between-the-staves.ly}
260 @ref{Instrument names},
261 @ref{Defining new contexts}.
264 @rlsr{Staff notation}.
268 @rinternals{StaffGroup},
269 @rinternals{ChoirStaff},
270 @rinternals{GrandStaff},
271 @rinternals{PianoStaff},
272 @rinternals{SystemStartBar},
273 @rinternals{SystemStartBrace},
274 @rinternals{SystemStartBracket},
275 @rinternals{SystemStartSquare}.
278 @code{PianoStaff} does not, by default, accept @code{ChordNames}.
281 @node Nested staff groups
282 @unnumberedsubsubsec Nested staff groups
284 @cindex staff, nested
285 @cindex staves, nested
286 @cindex nesting of staves
287 @cindex system start delimiters, nested
288 @cindex nested staff brackets
289 @cindex brackets, nesting of
290 @cindex braces, nesting of
292 Staff-group contexts can be nested to arbitrary depths. In this
293 case, each child context creates a new bracket adjacent to the
294 bracket of its parent group.
296 @lilypond[verbatim,quote,relative=2]
298 \new Staff { c2 c | c2 c }
300 \new Staff { g2 g | g2 g }
301 \new StaffGroup \with {
302 systemStartDelimiter = #'SystemStartSquare
305 \new Staff { e2 e | e2 e }
306 \new Staff { c2 c | c2 c }
312 New nested staff group contexts can be defined. For details, see
313 @ref{Defining new contexts}.
318 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
324 @ref{Grouping staves},
325 @ref{Instrument names},
326 @ref{Defining new contexts}.
329 @rlsr{Staff notation}.
332 @rinternals{StaffGroup},
333 @rinternals{ChoirStaff},
334 @rinternals{SystemStartBar},
335 @rinternals{SystemStartBrace},
336 @rinternals{SystemStartBracket},
337 @rinternals{SystemStartSquare}.
339 @node Separating systems
340 @unnumberedsubsubsec Separating systems
342 @cindex system separator mark
344 If the number of systems per page changes from page to page it is
345 customary to separate the systems by placing a system separator mark
346 between them. By default the system separator is blank, but can be
347 turned on with a @code{\paper} option.
349 @c \book is required here to display the system separator
350 @c ragged-right is required as there are two systems
351 @lilypond[verbatim,quote,ragged-right]
372 system-separator-markup = \slashSeparator
373 % following commands are needed only to format this documentation
375 paper-height = 100\mm
386 @rlsr{Staff notation}.
389 @node Modifying single staves
390 @subsection Modifying single staves
392 This section explains how to change specific attributes of one
393 staff: for example, modifying the number of staff lines or the
394 staff size. Methods to start and stop staves and set ossia
395 sections are also described.
405 @unnumberedsubsubsec Staff symbol
407 @cindex adjusting staff symbol
408 @cindex drawing staff symbol
409 @cindex staff symbol, setting of
410 @cindex staff symbol, drawing
411 @cindex stop staff lines
412 @cindex start staff lines
413 @cindex staff lines, amount of
414 @cindex staff lines, number of
415 @cindex staff line, thickness of
416 @cindex amount of staff lines
417 @cindex thickness of staff lines
418 @cindex ledger lines, setting
419 @cindex setting of ledger lines
420 @cindex spacing of ledger lines
421 @cindex number of staff lines
423 The lines of a staff belong to the @code{StaffSymbol} grob.
424 @code{StaffSymbol} properties can be modified to change the
425 appearance of a staff, but they must be modified before the staff
428 The number of staff lines may be changed. The clef position and
429 the position of middle C may need to be modified to fit the new
430 staff. For an explanation, refer to the snippet section in
433 @lilypond[verbatim,quote,relative=2]
435 \override StaffSymbol #'line-count = #3
440 Staff line thickness can be modified. The thickness of ledger
441 lines and stems are also affected, since they depend on staff line
444 @lilypond[verbatim,quote,relative=1]
446 \override StaffSymbol #'thickness = #3
451 Ledger line thickness can be set independently of staff line
452 thickness. In the example the two numbers are factors multiplying
453 the staff line thickness and the staff line spacing. The two
454 contributions are added to give the ledger line thickness.
456 @lilypond[verbatim,quote,relative=1]
458 \override StaffSymbol #'ledger-line-thickness = #'(1 . 0.2)
463 The distance between staff lines can be changed. This setting
464 affects the spacing of ledger lines as well.
466 @lilypond[verbatim,quote,relative=1]
468 \override StaffSymbol #'staff-space = #1.5
473 Further details about the properties of @code{StaffSymbol} can be
474 found in @rinternals{staff-symbol-interface}.
476 @cindex stopping a staff
477 @cindex starting a staff
478 @cindex staff, starting
479 @cindex staff, stopping
481 @funindex \startStaff
486 Modifications to staff properties in the middle of a score can be
487 placed between @code{\stopStaff} and @code{\startStaff}:
489 @lilypond[verbatim,quote,relative=2]
492 \override Staff.StaffSymbol #'line-count = #2
496 \revert Staff.StaffSymbol #'line-count
502 In general, @code{\startStaff} and @code{\stopStaff} can be used
503 to stop or start a staff in the middle of a score.
505 @lilypond[verbatim,quote,relative=2]
522 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
523 {making-some-staff-lines-thicker-than-the-others.ly}
536 @rlsr{Staff notation}.
539 @rinternals{StaffSymbol},
540 @rinternals{staff-symbol-interface}.
544 @unnumberedsubsubsec Ossia staves
546 @cindex staff, Frenched
548 @cindex Frenched staves
549 @cindex staff, resizing of
550 @cindex resizing of staves
552 @funindex \startStaff
557 @notation{Ossia} staves can be set by creating a new simultaneous
558 staff in the appropriate location:
560 @lilypond[verbatim,quote]
561 \new Staff \relative c'' {
565 \new Staff { e4 d f e }
572 However, the above example is not what is usually desired. To
573 create ossia staves that are above the original staff, have no
574 time signature or clef, and have a smaller font size, tweaks must
575 be used. The Learning Manual describes a specific technique to
576 achieve this goal, beginning with
577 @rlearning{Nesting music expressions}.
579 The following example uses the @code{alignAboveContext} property
580 to align the ossia staff. This method is most appropriate when
581 only a few ossia staves are needed.
583 @lilypond[verbatim,quote]
584 \new Staff = main \relative c'' {
590 \remove "Time_signature_engraver"
591 alignAboveContext = #"main"
593 \override StaffSymbol #'staff-space = #(magstep -3)
594 \override StaffSymbol #'thickness = #(magstep -3)
603 If many isolated ossia staves are needed, creating an empty
604 @code{Staff} context with a specific @emph{context id} may be more
605 appropriate; the ossia staves may then be created by
606 @emph{calling} this context and using @code{\startStaff} and
607 @code{\stopStaff} at the desired locations. The benefits of this
608 method are more apparent if the piece is longer than the following
611 @lilypond[verbatim,quote,ragged-right]
613 \new Staff = ossia \with {
614 \remove "Time_signature_engraver"
615 \override Clef #'transparent = ##t
617 \override StaffSymbol #'staff-space = #(magstep -3)
618 \override StaffSymbol #'thickness = #(magstep -3)
622 \new Staff \relative c' {
626 \context Staff = ossia {
627 \startStaff e4 g8 f e2 \stopStaff
634 \context Staff = ossia {
635 \startStaff g4 e8 f g2 \stopStaff
644 Using the @code{\Staff \RemoveEmptyStaves} command to create ossia
645 staves may be used as an alternative. This method is most
646 convenient when ossia staves occur immediately following a line
647 break. For more information about
648 @code{\Staff \RemoveEmptyStaves}, see @ref{Hiding staves}.
650 @lilypond[verbatim,quote,ragged-right]
652 \new Staff = ossia \with {
653 \remove "Time_signature_engraver"
654 \override Clef #'transparent = ##t
656 \override StaffSymbol #'staff-space = #(magstep -3)
657 \override StaffSymbol #'thickness = #(magstep -3)
662 \new Staff \relative c' {
674 \Staff \RemoveEmptyStaves
675 \override VerticalAxisGroup #'remove-first = ##t
683 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
684 {vertically-aligning-ossias-and-lyrics.ly}
691 @rglos{Frenched staff}.
694 @rlearning{Nesting music expressions},
695 @rlearning{Size of objects},
696 @rlearning{Length and thickness of objects}.
702 @rlsr{Staff notation}.
705 @rinternals{StaffSymbol}.
709 @unnumberedsubsubsec Hiding staves
711 @cindex Frenched score
712 @cindex Frenched staff
713 @cindex staff, hiding
715 @cindex hiding of staves
718 @funindex \RemoveEmptyStaves
719 @funindex Staff_symbol_engraver
724 Staff lines can be hidden by removing the
725 @code{Staff_symbol_engraver} from the @code{Staff} context. As an
726 alternative, @code{\stopStaff} may be used.
728 @lilypond[verbatim,quote]
730 \remove "Staff_symbol_engraver"
732 \relative c''' { a8 f e16 d c b a2 }
736 Empty staves can be hidden by setting the
737 @code{\Staff \RemoveEmptyStaves} command in the @code{\layout}
738 block. In orchestral scores, this style is known as @q{Frenched
739 Score}. By default, this command hides and removes all empty
740 staves in a score except for those in the first system.
742 @warning{A staff is considered empty when it contains only
743 multi-measure rests, rests, skips, spacer rests, or a combination of these
746 @lilypond[verbatim,quote,ragged-right]
749 \Staff \RemoveEmptyStaves
770 @code{\Staff \RemoveEmptyStaves} can also be used to create ossia
771 sections for a staff. For details, see @ref{Ossia staves}.
773 @cindex hiding ancient staves
774 @cindex hiding rhythmic staves
776 @funindex \RemoveEmptyStaves
778 The @code{\VaticanaStaff \RemoveEmptyStaves} command may be used to
779 hide empty staves in ancient music contexts. Similarly,
780 @code{\RhythmicStaff \RemoveEmptyStaves} may be used to hide empty
781 @code{RhythmicStaff} contexts.
785 @code{\Staff \RemoveEmptyStaves},
786 @code{\VaticanaStaff \RemoveEmptyStaves},
787 @code{\RhythmicStaff \RemoveEmptyStaves}.
793 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
794 {removing-the-first-empty-line.ly}
799 @rglos{Frenched staff}.
802 @rlearning{Visibility and color of objects}.
805 @ref{Changing context default settings},
809 @ref{Invisible rests},
810 @ref{Visibility of objects}.
813 @rlsr{Staff notation}.
816 @rinternals{ChordNames},
817 @rinternals{FiguredBass},
820 @rinternals{VerticalAxisGroup},
821 @rinternals{Staff_symbol_engraver}.
826 Removing @code{Staff_symbol_engraver} also hides bar lines. If
827 bar line visibility is forced, formatting errors may occur. In
828 this case, use the following overrides instead of removing the
832 \override StaffSymbol #'stencil = ##f
833 \override NoteHead #'no-ledgers = ##t
836 For the Known issues and warnings associated with
837 @code{\Staff \RemoveEmptyStaves} see
838 @ref{Changing context default settings}.
841 @subsection Writing parts
843 This section explains how to insert tempo indications and
844 instrument names into a score. Methods to quote other voices and
845 format cue notes are also described.
849 * Quoting other voices::
850 * Formatting cue notes::
853 @node Instrument names
854 @unnumberedsubsubsec Instrument names
856 @cindex instrument names
857 @cindex instrument names, short
859 Instrument names can be printed on the left side of staves in the
860 @code{Staff} and @code{PianoStaff} contexts. The value of
861 @code{instrumentName} is used for the first staff, and the value
862 of @code{shortInstrumentName} is used for all succeeding staves.
864 @lilypond[verbatim,quote,ragged-right,relative=1]
865 \set Staff.instrumentName = #"Violin "
866 \set Staff.shortInstrumentName = #"Vln "
872 Markup mode can be used to create more complicated instrument
875 @lilypond[verbatim,quote,relative=2]
876 \set Staff.instrumentName = \markup {
877 \column { "Clarinetti"
878 \line { "in B" \smaller \flat } } }
882 @cindex instrument names, centering
884 When two or more staff contexts are grouped together, the
885 instrument names and short instrument names are centered by
886 default. To center multi-line instrument names,
887 @code{\center-column} must be used:
889 @lilypond[verbatim,quote,indent=1.5\cm,relative=2]
892 \set Staff.instrumentName = #"Flute"
896 \set Staff.instrumentName = \markup \center-column {
898 \line { "in B" \smaller \flat }
906 @funindex short-indent
908 However, if the instrument names are longer, the instrument names
909 in a staff group may not be centered unless the @code{indent} and
910 @code{short-indent} settings are increased. For details about
911 these settings, see @ref{\paper variables for shifts and indents}.
913 @lilypond[verbatim,quote,ragged-right]
916 short-indent = 1.5\cm
921 \set Staff.instrumentName = #"Alto Flute in G"
922 \set Staff.shortInstrumentName = #"Fl."
927 \set Staff.instrumentName = #"Clarinet"
928 \set Staff.shortInstrumentName = #"Clar."
935 @cindex instrument names, adding to other contexts
937 To add instrument names to other contexts (such as
938 @code{GrandStaff}, @code{ChoirStaff}, or @code{StaffGroup}),
939 @code{Instrument_name_engraver} must be added to that context.
940 For details, see @ref{Modifying context plug-ins}.
942 @cindex instrument names, changing
943 @cindex changing instrument names
945 Instrument names may be changed in the middle of a piece.
946 However, remember that @code{instrumentName} will not be
947 displayed in the middle of the piece, as it only appears
950 @lilypond[verbatim,quote,ragged-right,relative=1]
951 \set Staff.instrumentName = #"First"
952 \set Staff.shortInstrumentName = #"one"
955 \set Staff.instrumentName = #"Second"
956 \set Staff.shortInstrumentName = #"two"
961 @cindex instrument switch
962 @cindex switching instruments
964 @funindex \addInstrumentDefinition
965 @funindex addInstrumentDefinition
966 @funindex \instrumentSwitch
967 @funindex instrumentSwitch
969 If an instrument @emph{switch} is needed,
970 @code{\addInstrumentDefinition} may be used in combination with
971 @code{\instrumentSwitch} to create a detailed list of the
972 necessary changes for the switch. The
973 @code{\addInstrumentDefinition} command has two arguments: an
974 identifying string, and an association list of context properties
975 and values to be used for the instrument. It must be placed in
976 the toplevel scope. @code{\instrumentSwitch} is used in the music
977 expression to declare the instrument switch:
979 @lilypond[verbatim,quote,ragged-right]
980 \addInstrumentDefinition #"contrabassoon"
981 #`((instrumentTransposition . ,(ly:make-pitch -1 0 0))
982 (shortInstrumentName . "Cbsn.")
983 (clefGlyph . "clefs.F")
984 (middleCPosition . 6)
986 (instrumentCueName . ,(make-bold-markup "cbsn."))
987 (midiInstrument . "bassoon"))
990 instrumentName = #"Bassoon"
994 \compressFullBarRests
997 \instrumentSwitch "contrabassoon"
1006 @ref{\paper variables for shifts and indents},
1007 @ref{Modifying context plug-ins}.
1010 @rlsr{Staff notation}.
1012 Internals Reference:
1013 @rinternals{InstrumentName},
1014 @rinternals{PianoStaff},
1018 @node Quoting other voices
1019 @unnumberedsubsubsec Quoting other voices
1022 @cindex quoting other voices
1028 @funindex \quoteDuring
1029 @funindex quoteDuring
1030 @funindex \transposition
1031 @funindex transposition
1033 It is very common for one voice to double some of the music from
1034 another voice. For example, the first and second violins may play the
1035 same notes during a passage of music. In LilyPond this is accomplished
1036 by letting one voice @emph{quote} the other voice without having to
1039 Before a part can be quoted, the @code{\addQuote} command must be used
1040 to initialize the quoted fragment. This command must be used in the
1041 toplevel scope. The first argument is an identifying string, and the
1042 second is a music expression:
1045 flute = \relative c'' @{
1048 \addQuote "flute" @{ \flute @}
1051 The @code{\quoteDuring} command is used to indicate the point where the
1052 quotation begins. It is followed by two arguments: the name of the
1053 quoted voice, as defined with @code{\addQuote}, and a music expression
1054 that indicates the duration of the quote, usually spacer rests or
1055 multi-measure rests. The corresponding music (including all articulations,
1056 dynamics, markup, etc.) from the quoted voice is inserted into the music
1059 @lilypond[verbatim,quote]
1060 flute = \relative c'' {
1061 a4 gis g->\f gis^\markup{quoted}
1063 \addQuote "flute" { \flute }
1066 c4 cis \quoteDuring #"flute" { s2 }
1070 If the music expression used for @code{\quoteDuring} contains
1071 anything but a spacer rest or multi-measure rest, a polyphonic
1072 situation is created, which is often not desirable:
1074 @lilypond[verbatim,quote]
1075 flute = \relative c'' {
1078 \addQuote "flute" { \flute }
1081 c4 cis \quoteDuring #"flute" { c4 b }
1085 Quotations recognize instrument transposition settings for both
1086 the source and target instruments if the @code{\transposition}
1087 command is used. For details about @code{\transposition}, see
1088 @ref{Instrument transpositions}.
1090 @lilypond[verbatim,quote]
1091 clarinet = \relative c'' {
1095 \addQuote "clarinet" { \clarinet }
1098 c4 cis \quoteDuring #"clarinet" { s2 }
1102 It is possible to tag quotations with unique names in order to
1103 process them in different ways. For details about this procedure,
1104 see @ref{Using tags}.
1106 It is also possible to adjust which objects from the original voice are quoted
1107 by changing the @code{quotedEventTypes} property. By default, its value is
1108 @code{#'(StreamEvent)}, which means that everything is quoted. Setting it
1109 to e.g. @code{#'(note-event rest-event tie-event)} causes lilypond to quote
1110 only notes, rests and ties, but no articulations, markup or dynamics.
1112 @lilypond[verbatim,quote]
1113 clarinet = \relative c'' {
1114 a4 gis g->\f gis^\markup{quoted}
1116 \addQuote "clarinet" { \clarinet }
1119 \set Score.quotedEventTypes = #'(note-event rest-event tie-event)
1120 c4 cis \quoteDuring #"clarinet" { s2 }
1126 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1127 {quoting-another-voice-with-transposition.ly}
1130 @cindex articulation-event
1131 @cindex dynamic-event
1134 @funindex quotedEventTypes
1135 @funindex quotedCueEventTypes
1137 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1138 {quoting-another-voice.ly}
1143 @ref{Instrument transpositions},
1147 @rlsr{Staff notation}.
1149 Internals Reference:
1150 @rinternals{QuoteMusic},
1156 Only the contents of the first @code{Voice} occurring in an
1157 @code{\addQuote} command will be considered for quotation, so
1158 @code{@var{music}} cannot contain @code{\new} and
1159 @code{\context Voice} statements that would switch to a different
1162 Quoting grace notes is broken and can even cause LilyPond to
1165 Quoting nested triplets may result in poor notation.
1167 In earlier versions of LilyPond (pre 2.11), @code{addQuote} was
1168 written entirely in lower-case letters: @code{\addquote}.
1171 @node Formatting cue notes
1172 @unnumberedsubsubsec Formatting cue notes
1176 @cindex cue notes, formatting
1178 @cindex quoting other voices
1179 @cindex cues, formatting
1181 @funindex \cueDuring
1183 @funindex \quoteDuring
1184 @funindex quoteDuring
1186 The previous section explains how to create quotations. The
1187 @code{\cueDuring} command is a more specialized form of
1188 @code{\quoteDuring}, being particularly useful for inserting cue
1189 notes into a part. The syntax is as follows:
1192 \cueDuring #@var{partname} #@var{voice} @var{music}
1195 This command copies only the notes and rests from the
1196 corresponding measures from @code{@var{partname}} into a
1197 @code{CueVoice} context. The @code{CueVoice} is created
1198 implicitly, and occurs simultaneously with @code{@var{music}},
1199 which creates a polyphonic situation. The @code{@var{voice}}
1200 argument determines whether the cue notes should be notated as a
1201 first or second voice; @code{UP} corresponds to the first voice,
1202 and @code{DOWN} corresponds to the second.
1204 @lilypond[verbatim,quote]
1205 oboe = \relative c'' {
1206 r2 r8 d16(\f f e g f a)
1209 \addQuote "oboe" { \oboe }
1211 \new Voice \relative c'' {
1212 \cueDuring #"oboe" #UP { R1 }
1218 In the above example, the @code{Voice} context had to be
1219 explicitly declared, or else the entire music expression would
1220 belong to the @code{CueVoice} context.
1222 It is possible to adjust which aspects of the music are quoted with
1223 @code{\cueDuring} by setting the @code{quotedCueEventTypes}
1224 property. Its default value is @code{#'(note-event rest-event
1225 tie-event beam-event tuplet-span-event)}, which means that only
1226 notes, rests, ties, beams and tuplets are quoted, but not
1227 articulations, dynamic marks, markup etc.
1229 @lilypond[verbatim,quote]
1230 oboe = \relative c'' {
1231 r2 r8 d16(\f f e g f a)
1234 \addQuote "oboe" { \oboe }
1236 \new Voice \relative c'' {
1237 \set Score.quotedCueEventTypes = #'(note-event rest-event tie-event
1238 beam-event tuplet-span-event
1239 dynamic-event slur-event)
1240 \cueDuring #"oboe" #UP { R1 }
1245 Markup can be used to show the name of the quoted instrument. Also,
1246 if the cue notes require a change in clef, the original clef should
1247 be restored at the end of the cue notes.
1249 @lilypond[verbatim,quote]
1250 flute = \relative c'' {
1251 r2. c4 d8 c d e fis2 g2 d2
1253 bassoon = \relative c {
1257 s1*0^\markup { \tiny "flute" }
1258 \cueDuring #"flute" #UP { R1 }
1262 \addQuote "flute" { \flute }
1268 @cindex removing cues
1269 @cindex removing cue notes
1270 @cindex cue notes, removing
1275 The @code{\killCues} command removes cue notes from a music
1276 expression, so the same music expression can be used to produce
1277 the instrument part with cues and the score. The @code{\killCues}
1278 command removes only the notes and events that were quoted by
1279 @code{\cueDuring}. Other markup associated with cues, such as clef
1280 changes and a label identifying the source instrument, can be
1281 tagged for selective inclusion in the score; see @ref{Using tags}.
1283 @lilypond[verbatim,quote]
1284 flute = \relative c'' {
1285 r2. c4 d8 c d e fis2 g2 d2
1287 bassoon = \relative c {
1292 s1*0^\markup { \tiny "flute" }
1294 \cueDuring #"flute" #UP { R1 }
1295 \tag #'part \clef bass
1298 \addQuote "flute" { \flute }
1308 \removeWithTag #'part { \killCues { \bassoon } }
1313 Alternatively, Clef changes and instrument labels can be
1314 collected into an instrument definition for repeated use, using
1315 @code{\addInstrumentDefinition} described in
1316 @ref{Instrument names}.
1318 @funindex \transposedCueDuring
1319 @funindex transposedCueDuring
1321 Like @code{\quoteDuring}, @code{\cueDuring} takes instrument
1322 transpositions into account. Cue notes are produced at the
1323 pitches that would be written for the instrument receiving the cue
1324 to produce the sounding pitches of the source instrument.
1326 To transpose cue notes differently, use
1327 @code{\transposedCueDuring}. This command takes an extra argument
1328 to specify (in absolute mode) the printed pitch that you want to
1329 represent the sound of a concert middle C. This is useful for
1330 taking cues from an instrument in a completely different register.
1332 @lilypond[verbatim,quote]
1333 piccolo = \relative c''' {
1339 bassClarinet = \relative c' {
1343 \transposedCueDuring #"piccolo" #UP d { R1 }
1347 \addQuote "piccolo" { \piccolo }
1351 \new Staff \bassClarinet
1355 @cindex notes, smaller
1356 @cindex smaller notes
1358 A @code{CueVoice} context may be created explicitly if notes of a
1359 smaller size are required, for example to set an alternative
1360 sequence of notes more suitable for a higher or lower voice.
1362 @lilypond[verbatim,relative=2]
1379 @ref{Instrument transpositions},
1380 @ref{Instrument names},
1385 @rlsr{Staff notation}.
1387 Internals Reference:
1388 @rinternals{CueVoice},
1394 Collisions can occur with rests, when using @code{\cueDuring},
1395 between @code{Voice} and @code{CueVoice} contexts.