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 staff appearance, print
17 scores with more than one staff, and how to apply specific
18 performance marks to single staves.
22 * Modifying single staves::
27 @node Displaying staves
28 @subsection Displaying staves
30 This section describes the different methods of creating and
31 grouping staves, which are marked at the beginning of each line
32 with either a bracket or a brace.
35 * Instantiating new staves::
37 * Nested staff groups::
41 @node Instantiating new staves
42 @unnumberedsubsubsec Instantiating new staves
45 @cindex staff initiation
46 @cindex staff instantiation
50 @cindex percussion staff
51 @cindex Gregorian transcription staff
52 @cindex rhythmic staff
56 @notation{Staves} (singular: @notation{staff}) are created with
57 the @code{\new} or @code{\context} commands. For details, see
58 @ref{Creating contexts}.
60 The basic staff context is @code{Staff}:
62 @lilypond[verbatim,quote,relative=2]
63 \new Staff { c4 d e f }
66 @code{DrumStaff} creates a five-line staff set up for a
67 typical drum set. It uses different names for each instrument.
68 The instrument names are set using the @code{\drummode} command.
69 For details, see @ref{Percussion staves}.
71 @lilypond[verbatim,quote]
73 \drummode { cymc hh ss tomh }
77 @c FIXME: remove when mentioned in NR 2.8
78 @code{GregorianTranscriptionStaff} creates a staff to notate
79 modern Gregorian chant. It does not show bar lines.
81 @lilypond[verbatim,quote,relative=2]
82 \new GregorianTranscriptionStaff { c4 d e f }
85 @code{RhythmicStaff} creates a single-line staff that only
86 displays the rhythmic values of the input. Real durations are
87 preserved. For details, see @ref{Showing melody rhythms}.
89 @lilypond[verbatim,quote,relative=2]
90 \new RhythmicStaff { c4 d e f }
93 @code{TabStaff} creates a tablature with six strings in standard
94 guitar tuning. For details, see @ref{Default tablatures}.
96 @lilypond[verbatim,quote,relative=2]
97 \new TabStaff { c4 d e f }
100 There are two staff contexts specific for the notation of ancient
101 music: @code{MensuralStaff} and @code{VaticanaStaff}. They are
102 described in @ref{Pre-defined contexts}.
104 New single staff contexts may be defined. For details, see
105 @ref{Defining new contexts}.
115 @ref{Creating contexts},
116 @ref{Percussion staves},
117 @ref{Showing melody rhythms},
118 @ref{Default tablatures},
119 @ref{Pre-defined contexts},
121 @ref{Gregorian chant contexts},
122 @ref{Mensural contexts},
123 @ref{Defining new contexts}.
126 @rlsr{Staff notation}.
130 @rinternals{DrumStaff},
131 @rinternals{GregorianTranscriptionStaff},
132 @rinternals{RhythmicStaff},
133 @rinternals{TabStaff},
134 @rinternals{MensuralStaff},
135 @rinternals{VaticanaStaff},
136 @rinternals{StaffSymbol}.
139 @node Grouping staves
140 @unnumberedsubsubsec Grouping staves
142 @cindex start of system
143 @cindex staff, multiple
144 @cindex staves, multiple
145 @cindex system start delimiters
146 @cindex bracket, vertical
147 @cindex brace, vertical
156 Various contexts exist to group single staves together in order to
157 form multi-stave systems. Each grouping context sets the style of
158 the system start delimiter and the behavior of bar lines.
160 If no context is specified, the default properties will be used:
161 the group is started with a vertical line, and the bar lines are
164 @lilypond[verbatim,quote,relative=2]
171 In the @code{StaffGroup} context, the group is started with a
172 bracket and bar lines are drawn through all the staves.
174 @lilypond[verbatim,quote,relative=2]
181 In a @code{ChoirStaff}, the group starts with a bracket, but bar
182 lines are not connected.
184 @lilypond[verbatim,quote,relative=2]
191 In a @code{GrandStaff}, the group begins with a brace, and bar
192 lines are connected between the staves.
194 @lilypond[verbatim,quote,relative=2]
201 The @code{PianoStaff} is identical to a @code{GrandStaff}, except
202 that it supports printing the instrument name directly. For
203 details, see @ref{Instrument names}.
205 @lilypond[verbatim,quote,relative=2]
207 \set PianoStaff.instrumentName = "Piano"
213 Each staff group context sets the property
214 @code{systemStartDelimiter} to one of the following values:
215 @code{SystemStartBar}, @code{SystemStartBrace}, or
216 @code{SystemStartBracket}. A fourth delimiter,
217 @code{SystemStartSquare}, is also available, but it must be
218 explicitly specified.
220 New staff group contexts may be defined. For details, see
221 @ref{Defining new contexts}.
226 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
227 {use-square-bracket-at-the-start-of-a-staff-group.ly}
229 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
230 {display-bracket-with-only-one-staff-in-a-system.ly}
232 @cindex mensurstriche layout
233 @cindex renaissance music
234 @cindex transcription of mensural music
235 @cindex mensural music, transcription of
237 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
238 {mensurstriche-layout-bar-lines-between-the-staves.ly}
239 @c FIXME: move to NR 2.8.x when sectioning is ready
250 @ref{Instrument names},
251 @ref{Defining new contexts}.
254 @rlsr{Staff notation}.
258 @rinternals{StaffGroup},
259 @rinternals{ChoirStaff},
260 @rinternals{GrandStaff},
261 @rinternals{PianoStaff},
262 @rinternals{SystemStartBar},
263 @rinternals{SystemStartBrace},
264 @rinternals{SystemStartBracket},
265 @rinternals{SystemStartSquare}.
268 @node Nested staff groups
269 @unnumberedsubsubsec Nested staff groups
271 @cindex staff, nested
272 @cindex staves, nested
273 @cindex nesting of staves
274 @cindex system start delimiters, nested
275 @cindex nested staff brackets
276 @cindex brackets, nesting of
277 @cindex braces, nesting of
278 @cindex inner staff group
279 @cindex inner choir staff group
281 Two additional staff-group contexts are available that can be
282 nested within a @code{StaffGroup} or @code{ChoirStaff} context:
283 @code{InnerStaffGroup} and @code{InnerChoirStaff}. These contexts
284 create a new bracket adjacent to the bracket of their parent staff
287 An @code{InnerStaffGroup} is treated similarly to a
288 @code{StaffGroup}; bar lines are connected between each staff
291 @lilypond[verbatim,quote,relative=2]
293 \new Staff { c2 c | c2 c }
294 \new InnerStaffGroup <<
295 \new Staff { g2 g | g2 g }
296 \new Staff { e2 e | e2 e }
301 Bar lines are @emph{not} connected between staves of an
302 @code{InnerChoirStaff}, just like a @code{ChoirStaff}:
304 @lilypond[verbatim,quote,relative=2]
306 \new Staff { c2 c | c2 c }
307 \new InnerChoirStaff <<
308 \new Staff { g2 g | g2 g }
309 \new Staff { e2 e | e2 e }
311 \new Staff { c1 | c1 }
315 New nested staff group contexts can be defined. For details, see
316 @ref{Defining new contexts}.
321 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
328 @ref{Grouping staves},
329 @ref{Instrument names},
330 @ref{Defining new contexts}.
333 @rlsr{Staff notation}.
336 @rinternals{InnerStaffGroup},
337 @rinternals{StaffGroup},
338 @rinternals{InnerChoirStaff},
339 @rinternals{ChoirStaff},
340 @rinternals{SystemStartBar},
341 @rinternals{SystemStartBrace},
342 @rinternals{SystemStartBracket},
343 @rinternals{SystemStartSquare}.
346 @node Modifying single staves
347 @subsection Modifying single staves
349 This section explains how to change specific attributes of one
350 staff: for example, modifying the number of staff lines or the
351 staff size. Methods to start and stop staves and set ossia
352 sections are also described.
362 @unnumberedsubsubsec Staff symbol
364 @cindex adjusting staff symbol
365 @cindex drawing staff symbol
366 @cindex staff symbol, setting of
367 @cindex stop staff lines
368 @cindex start staff lines
369 @cindex staff lines, amount of
370 @cindex staff lines, number of
371 @cindex staff line, thickness of
372 @cindex amount of staff lines
373 @cindex thickness of staff lines
374 @cindex ledger lines, setting
375 @cindex setting of ledger lines
376 @cindex spacing of ledger lines
377 @cindex number of staff lines
379 The lines of a staff belong to the @code{StaffSymbol} grob.
380 @code{StaffSymbol} properties can be modified to change the
381 appearance of a staff, but they must be modified before the staff
384 The number of staff lines may be changed. The clef position and
385 the position of middle C may need to be modified to fit the new
386 staff. For an explanation, refer to the snippet section in
389 @lilypond[verbatim,quote,relative=2]
391 \override StaffSymbol #'line-count = #3
396 The vertical position of staff lines and the number of staff lines
397 can be defined at the same time. As the following example shows,
398 note positions are not influenced by the staff line positions.
400 @warning{The @code{'line-positions} property overrides the
401 @code{'line-count} property. The number of staff lines is
402 implicitly defined by the number of elements in the list of values
403 for @code{'line-positions}.}
405 @lilypond[verbatim,quote,relative=1]
407 \override StaffSymbol #'line-positions = #'(7 3 0 -4 -6 -7)
412 Staff line thickness can be modified. The thickness of ledger
413 lines and stems are also affected, since they depend on staff line
416 @lilypond[verbatim,quote,relative=1]
418 \override StaffSymbol #'thickness = #3
423 Ledger line thickness can be set independently of staff line
426 @lilypond[verbatim,quote,relative=1]
428 \override StaffSymbol #'ledger-line-thickness = #'(1 . 0.2)
433 The distance between staff lines can be changed. This setting
434 affects the spacing of ledger lines as well.
436 @lilypond[verbatim,quote,relative=1]
438 \override StaffSymbol #'staff-space = #1.5
443 The width of a staff can be modified. The units are staff
444 spaces. The spacing of objects inside the staff is not affected by
447 @lilypond[verbatim,quote,relative=1]
449 \override StaffSymbol #'width = #23
454 Further details about the properties of @code{StaffSymbol} can be
455 found in @rinternals{staff-symbol-interface}.
457 @funindex \startStaff
460 Modifications to staff properties in the middle of a score can be
461 placed between @code{\stopStaff} and @code{\startStaff}:
463 @lilypond[verbatim,quote,relative=2]
466 \override Staff.StaffSymbol #'line-count = #2
470 \revert Staff.StaffSymbol #'line-count
475 @cindex stopping a staff
478 In general, @code{\startStaff} and @code{\stopStaff} can be used
479 to stop or start a staff in the middle of a score.
481 @lilypond[verbatim,quote,relative=2]
498 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
499 {making-some-staff-lines-thicker-than-the-others.ly}
513 @rlsr{Staff notation}.
516 @rinternals{StaffSymbol},
517 @rinternals{staff-symbol-interface}.
522 When setting vertical staff line positions manually, bar lines are
523 always centered on position 0, so the maximum distance between the
524 outermost bar lines in either direction must be equal.
528 @unnumberedsubsubsec Ossia staves
530 @cindex staff, Frenched
532 @cindex Frenched staves
533 @cindex staff, resizing of
534 @cindex resizing of staves
536 @notation{Ossia} staves can be set by creating a new simultaneous
537 staff in the appropriate location:
539 @lilypond[verbatim,quote]
540 \new Staff \relative c'' {
544 \new Staff { e4 d f e }
551 However, the above example is usually not the desired result. To
552 create ossia staves that are above the original staff, have no
553 time signature or clef, and have a smaller font size, tweaks must
554 be used. The Learning Manual describes a specific technique to
555 achieve this goal, beginning with
556 @rlearning{Nesting music expressions}.
558 The following example uses the @code{alignAboveContext} property
559 to align the ossia staff. This method is most appropriate when
560 only a few ossia staves are needed.
562 @lilypond[verbatim,quote]
563 \new Staff = main \relative c'' {
569 \remove "Time_signature_engraver"
570 alignAboveContext = #"main"
572 \override StaffSymbol #'staff-space = #(magstep -3)
573 \override StaffSymbol #'thickness = #(magstep -3)
582 If many isolated ossia staves are needed, creating an empty
583 @code{Staff} context with a specific @emph{context id} may be more
584 appropriate; the ossia staves may then be created by
585 @emph{calling} this context and using @code{\startStaff} and
586 @code{\stopStaff} at the desired locations. The benefits of this
587 method are more apparent if the piece is longer than the following
590 @lilypond[verbatim,quote,ragged-right]
592 \new Staff = ossia \with {
593 \remove "Time_signature_engraver"
594 \override Clef #'transparent = ##t
596 \override StaffSymbol #'staff-space = #(magstep -3)
597 \override StaffSymbol #'thickness = #(magstep -3)
601 \new Staff \relative c' {
605 \context Staff = ossia {
606 \startStaff e4 g8 f e2 \stopStaff
613 \context Staff = ossia {
614 \startStaff g4 e8 f g2 \stopStaff
622 Using the @code{\RemoveEmptyStaffContext} command to create ossia
623 staves may be used as an alternative. This method is most
624 convenient when ossia staves occur immediately following a line
625 break. In this case, spacer rests do not need to be used at all;
626 only @code{\startStaff} and @code{\stopStaff} are necessary. For
627 more information about @code{\RemoveEmptyStaffContext}, see
630 @lilypond[verbatim,quote,ragged-right]
632 \new Staff = ossia \with {
633 \remove "Time_signature_engraver"
634 \override Clef #'transparent = ##t
636 \override StaffSymbol #'staff-space = #(magstep -3)
637 \override StaffSymbol #'thickness = #(magstep -3)
639 \new Staff \relative c' {
645 \context Staff = ossia {
646 c4 e8 d c2 \stopStaff
656 \RemoveEmptyStaffContext
657 \override VerticalAxisGroup #'remove-first = ##t
665 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
666 {vertically-aligning-ossias-and-lyrics.ly}
674 @rglos{Frenched staff}.
677 @rlearning{Nesting music expressions},
678 @rlearning{Size of objects},
679 @rlearning{Length and thickness of objects}.
685 @rlsr{Staff notation}.
688 @rinternals{StaffSymbol}.
692 @unnumberedsubsubsec Hiding staves
694 @cindex Frenched score
695 @cindex Frenched staff
696 @cindex staff, hiding
698 @cindex hiding of staves
701 Staff lines can be hidden by removing the
702 @code{Staff_symbol_engraver} from the @code{Staff} context. As an
703 alternative, @code{\stopStaff} may be used.
705 @lilypond[verbatim,quote]
707 \remove "Staff_symbol_engraver"
709 \relative c''' { a8 f e16 d c b a2 }
712 @funindex \RemoveEmptyStaffContext
714 Empty staves can be hidden by setting the
715 @code{\RemoveEmptyStaffContext} command in the @code{\layout}
716 block. In orchestral scores, this style is known as @q{Frenched
717 Score}. By default, this command hides and removes all empty
718 staves in a score except for those in the first system.
720 @warning{An empty staff may only include multi-measure rests,
721 skips, spacer rests, or a combination of these elements.}
723 @lilypond[verbatim,quote,ragged-right]
726 \RemoveEmptyStaffContext
747 @code{\RemoveEmptyStaffContext} can also be used to create ossia
748 sections for a staff. For details, see @ref{Ossia staves}.
750 @cindex hiding ancient staves
751 @cindex hiding rhythmic staves
752 @funindex \AncientRemoveEmptyStaffContext
753 @funindex \RemoveEmptyRhythmicStaffContext
755 The @code{\AncientRemoveEmptyStaffContext} command may be used to
756 hide empty staves in ancient music contexts. Similarly,
757 @code{\RemoveEmptyRhythmicStaffContext} may be used to hide empty
758 @code{RhythmicStaff} contexts.
763 @code{\RemoveEmptyStaffContext},
764 @code{\AncientRemoveEmptyStaffContext},
765 @code{\RemoveEmptyRhythmicStaffContext}.
770 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
771 {removing-the-first-empty-line.ly}
777 @rglos{Frenched staff}.
784 @rlsr{Staff notation}.
787 @rinternals{ChordNames},
788 @rinternals{FiguredBass},
791 @rinternals{VerticalAxisGroup},
792 @rinternals{Staff_symbol_engraver}.
797 Removing @code{Staff_symbol_engraver} also hides bar lines. If
798 bar line visibility is forced, formatting errors may occur. In
799 this case, use the following overrides instead of removing the
803 \override StaffSymbol #'stencil = ##f
804 \override NoteHead #'no-ledgers = ##t
809 @subsection Writing parts
811 This section explains how to insert tempo indications and
812 instrument names into a score. Methods to quote other voices and
813 format cue notes are also described.
818 * Quoting other voices::
819 * Formatting cue notes::
823 @node Metronome marks
824 @unnumberedsubsubsec Metronome marks
827 @cindex beats per minute
828 @cindex metronome marking
829 @cindex metronome marking with text
832 A basic metronome mark is simple to write:
834 @lilypond[verbatim,quote,relative=1]
840 Tempo indications with text can be used instead:
842 @lilypond[verbatim,quote,relative=2]
848 Combining a metronome mark and text will automatically place the
849 metronome mark within parentheses:
851 @lilypond[verbatim,quote,relative=2]
852 \tempo "Allegro" 4 = 160
857 In general, the text can be any markup object:
859 @lilypond[verbatim,quote,relative=2]
860 \tempo \markup { \italic Faster } 4 = 132
861 a8-. r8 b-. r gis-. r a-. r
864 A parenthesized metronome mark with no textual indication may be
865 written by including an empty string in the input:
867 @lilypond[verbatim,quote,relative=2]
875 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
876 {printing-metronome-and-rehearsal-marks-below-the-staff.ly}
878 @c perhaps also an example of how to move it horizontally?
880 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
881 {changing-the-tempo-without-a-metronome-mark.ly}
883 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
884 {creating-metronome-marks-in-markup-mode.ly}
886 For more details, see @ref{Formatting text}.
893 @rglos{metronomic indication},
894 @rglos{tempo indication},
895 @rglos{metronome mark}.
898 @ref{Formatting text},
902 @rlsr{Staff notation}.
905 @rinternals{MetronomeMark}.
908 @node Instrument names
909 @unnumberedsubsubsec Instrument names
911 @cindex instrument names
912 @cindex instrument names, short
914 Instrument names can be printed on the left side of staves in the
915 @code{Staff} and @code{PianoStaff} contexts. The value of
916 @code{instrumentName} is used for the first staff, and the value
917 of @code{shortInstrumentName} is used for all succeeding staves.
919 @lilypond[verbatim,quote,ragged-right,relative=1]
920 \set Staff.instrumentName = "Violin "
921 \set Staff.shortInstrumentName = "Vln "
927 Markup mode can be used to create more complicated instrument
930 @lilypond[verbatim,quote,relative=2]
931 \set Staff.instrumentName = \markup {
932 \column { "Clarinetti"
933 \line { "in B" \smaller \flat } } }
937 @cindex instrument names, centering
939 When two or more staff contexts are grouped together, the
940 instrument names and short instrument names are centered by
941 default. To center multi-line instrument names,
942 @code{\center-column} must be used:
944 @lilypond[verbatim,quote,indent=1.5\cm,relative=2]
947 \set Staff.instrumentName = "Flute"
951 \set Staff.instrumentName = \markup \center-column {
953 \line { "in B" \smaller \flat }
963 However, if the instrument names are longer, the instrument names
964 in a staff group may not be centered unless the @code{indent} and
965 @code{short-indent} settings are increased. For details about
966 these settings, see @ref{Horizontal dimensions}.
968 @lilypond[verbatim,quote,ragged-right]
971 short-indent = 1.5\cm
976 \set Staff.instrumentName = "Alto Flute in G"
977 \set Staff.shortInstrumentName = "Fl."
982 \set Staff.instrumentName = "Clarinet"
983 \set Staff.shortInstrumentName = "Clar."
990 To add instrument names to other contexts (such as
991 @code{GrandStaff}, @code{ChoirStaff}, or @code{StaffGroup}),
992 @code{Instrument_name_engraver} must be added to that context.
993 For details, see @ref{Modifying context plug-ins}.
995 @cindex instrument names, changing
997 Instrument names may be changed in the middle of a piece:
999 @lilypond[verbatim,quote,ragged-right,relative=1]
1000 \set Staff.instrumentName = "First"
1001 \set Staff.shortInstrumentName = "one"
1004 \set Staff.instrumentName = "Second"
1005 \set Staff.shortInstrumentName = "two"
1010 @cindex instrument switch
1011 @cindex switching instruments
1013 If an instrument @emph{switch} is needed,
1014 @code{\addInstrumentDefinition} may be used in combination with
1015 @code{\instrumentSwitch} to create a detailed list of the
1016 necessary changes for the switch. The
1017 @code{\addInstrumentDefinition} command has two arguments: an
1018 identifying string, and an association list of context properties
1019 and values to be used for the instrument. It must be placed in
1020 the toplevel scope. @code{\instrumentSwitch} is used in the music
1021 expression to declare the instrument switch:
1023 @lilypond[verbatim,quote,ragged-right]
1024 \addInstrumentDefinition #"contrabassoon"
1025 #`((instrumentTransposition . ,(ly:make-pitch -1 0 0))
1026 (shortInstrumentName . "Cbsn.")
1027 (clefGlyph . "clefs.F")
1028 (middleCPosition . 6)
1030 (instrumentCueName . ,(make-bold-markup "cbsn."))
1031 (midiInstrument . "bassoon"))
1034 instrumentName = "Bassoon"
1038 \compressFullBarRests
1041 \instrumentSwitch "contrabassoon"
1051 @ref{Horizontal dimensions},
1052 @ref{Modifying context plug-ins}.
1055 @rlsr{Staff notation}.
1057 Internals Reference:
1058 @rinternals{InstrumentName},
1059 @rinternals{PianoStaff},
1063 @node Quoting other voices
1064 @unnumberedsubsubsec Quoting other voices
1067 @cindex quoting other voices
1071 It is very common for one voice to double the some of the music from
1072 another voice. For example, the first and second violins may play the
1073 same notes during a passage of music. In LilyPond this is accomplished
1074 by letting one voice @emph{quote} the other voice without having to
1077 Before a part can be quoted, the @code{\addQuote} command must be used
1078 to initialize the quoted fragment. This command must be used in the
1079 toplevel scope. The first argument is an identifying string, and the
1080 second is a music expression:
1083 flute = \relative c'' @{
1086 \addQuote "flute" @{ \flute @}
1089 The @code{\quoteDuring} command is used to indicate the point where the
1090 quotation begins. It is followed by two arguments: the name of the
1091 quoted voice, as defined with @code{\addQuote}, and a music expression
1092 that indicates the duration of the quote, usually spacer rests or
1093 multi-measure rests. The corresponding music from the quoted voice is
1094 inserted into the music expression:
1096 @lilypond[verbatim,quote]
1097 flute = \relative c'' {
1100 \addQuote "flute" { \flute }
1103 c4 cis \quoteDuring #"flute" { s2 }
1107 If the music expression used for @code{\quoteDuring} contains
1108 anything but a spacer rest or multi-measure rest, a polyphonic
1109 situation is created, which is often not desirable:
1111 @lilypond[verbatim,quote]
1112 flute = \relative c'' {
1115 \addQuote "flute" { \flute }
1118 c4 cis \quoteDuring #"flute" { c4 b }
1122 Quotations recognize instrument transposition settings for both
1123 the source and target instruments if the @code{\transposition}
1124 command is used. For details about @code{\transposition}, see
1125 @ref{Instrument transpositions}.
1127 @lilypond[verbatim,quote]
1128 clarinet = \relative c'' {
1132 \addQuote "clarinet" { \clarinet }
1135 c4 cis \quoteDuring #"clarinet" { s2 }
1139 It is possible to tag quotations with unique names in order to
1140 process them in different ways. For details about this procedure,
1141 see @ref{Using tags}.
1146 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1147 {quoting-another-voice-with-transposition.ly}
1150 @cindex articulation-event
1151 @cindex dynamic-event
1153 @funindex quotedEventTypes
1155 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
1156 {quoting-another-voice.ly}
1162 @ref{Instrument transpositions},
1166 @rlsr{Staff notation}.
1168 Internals Reference:
1169 @rinternals{QuoteMusic},
1175 Only the contents of the first @code{Voice} occurring in an
1176 @code{\addQuote} command will be considered for quotation, so
1177 @var{music} cannot contain @code{\new} and @code{\context Voice}
1178 statements that would switch to a different Voice.
1180 Quoting grace notes is broken and can even cause LilyPond to
1183 Quoting nested triplets may result in poor notation.
1185 In earlier versions of LilyPond (pre 2.11), @code{addQuote} was
1186 written entirely in lower-case letters: @code{\addquote}.
1189 @node Formatting cue notes
1190 @unnumberedsubsubsec Formatting cue notes
1194 @cindex cue notes, formatting
1196 @cindex quoting other voices
1197 @cindex cues, formatting
1199 The previous section explains how to create quotations. The
1200 @code{\cueDuring} command is a more specialized form of
1201 @code{\quoteDuring}, being particularly useful for inserting cue
1202 notes into a part. The syntax is as follows:
1205 \cueDuring #@var{partname} #@var{voice} @var{music}
1208 This command copies the corresponding measures from @var{partname}
1209 into a @code{CueVoice} context. The @code{CueVoice} is created
1210 implicitly, and occurs simultaneously with @var{music}, which
1211 creates a polyphonic situation. The @var{voice} argument
1212 determines whether the cue notes should be notated as a first or
1213 second voice; @code{UP} corresponds to the first voice, and
1214 @code{DOWN} corresponds to the second.
1216 @lilypond[verbatim,quote]
1217 oboe = \relative c'' {
1221 \addQuote "oboe" { \oboe }
1223 \new Voice \relative c'' {
1224 \cueDuring #"oboe" #UP { R1 }
1230 In the above example, the @code{Voice} context had to be
1231 explicitly declared, or else the entire music expression would
1232 belong to the @code{CueVoice} context.
1234 The name of the cued instrument can be printed by setting the
1235 @code{instrumentCueName} property in the @code{CueVoice} context.
1237 @lilypond[verbatim,quote]
1238 oboe = \relative c''' {
1241 \addQuote "oboe" { \oboe }
1243 \new Staff \relative c'' <<
1244 \new CueVoice \with {
1245 instrumentCueName = "ob."
1248 \cueDuring #"oboe" #UP { R1 }
1254 In addition to printing the name of the cued instrument, when cue
1255 notes end, the name of the original instrument should be printed,
1256 and any other changes introduced by the cued part should be
1257 undone. This can be accomplished by using
1258 @code{\addInstrumentDefinition} and @code{\instrumentSwitch}. For
1259 an example and explanation, see @ref{Instrument names}.
1261 The @code{\killCues} command removes cue notes from a music
1262 expression. This can be useful if cue notes need to be removed
1263 from a part but may be restored at a later time.
1265 @lilypond[verbatim,quote]
1266 flute = \relative c''' {
1269 \addQuote "flute" { \flute }
1271 \new Voice \relative c'' {
1273 \cueDuring #"flute" #UP { R1 }
1279 The @code{\transposedCueDuring} command is useful for adding
1280 instrumental cues from a completely different register. The
1281 syntax is similar to @code{\cueDuring}, but it requires one extra
1282 argument to specify the transposition of the cued instrument. For
1283 more information about transposition, see
1284 @ref{Instrument transpositions}.
1286 @lilypond[verbatim,quote]
1287 piccolo = \relative c''' {
1293 \addQuote "piccolo" { \piccolo }
1295 cbassoon = \relative c, {
1298 \transposedCueDuring #"piccolo" #UP c,, { R1 }
1303 \new Staff = "piccolo" \piccolo
1304 \new Staff = "cbassoon" \cbassoon
1308 It is possible to tag cued parts with unique names in order to
1309 process them in different ways. For details about this procedure,
1310 see @ref{Using tags}.
1316 @ref{Instrument transpositions},
1317 @ref{Instrument names},
1321 @rlsr{Staff notation}.
1323 Internals Reference:
1324 @rinternals{CueVoice},
1330 Collisions can occur with rests, when using @code{\cueDuring},
1331 between @code{Voice} and @code{CueVoice} contexts.