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 @c The line width is a bit of a hack to allow space for the
17 @lilypondfile[quote,ragged-right,line-width=14.5\cm,staffsize=16]{staff-headword.ly}
19 This section explains how to influence the appearance of staves,
20 how to print scores with more than one staff, and how to add tempo
21 indications and cue notes to staves.
25 * Modifying single staves::
30 @node Displaying staves
31 @subsection Displaying staves
33 This section describes the different methods of creating and
37 * Instantiating new staves::
39 * Nested staff groups::
40 * Separating systems::
44 @node Instantiating new staves
45 @unnumberedsubsubsec Instantiating new staves
48 @cindex staff initiation
49 @cindex staff instantiation
53 @cindex staff, percussion
55 @cindex percussion staff
56 @cindex Gregorian transcription staff
57 @cindex rhythmic staff
64 @funindex RhythmicStaff
66 @funindex MensuralStaff
67 @funindex VaticanaStaff
68 @funindex GregorianTranscriptionStaff
70 @notation{Staves} (singular: @notation{staff}) are created with
71 the @code{\new} or @code{\context} commands. For details, see
72 @ref{Creating and referencing contexts}.
74 The basic staff context is @code{Staff}:
76 @lilypond[verbatim,quote,relative=2]
77 \new Staff { c4 d e f }
80 The @code{DrumStaff} context creates a five-line staff set up for
81 a typical drum set. Each instrument is shown with a different
82 symbol. The instruments are entered in drum mode following a
83 @code{\drummode} command, with each instrument specified by name.
84 For details, see @ref{Percussion staves}.
86 @lilypond[verbatim,quote]
88 \drummode { cymc hh ss tomh }
92 @code{RhythmicStaff} creates a single-line staff that only
93 displays the rhythmic values of the input. Real durations are
94 preserved. For details, see @ref{Showing melody rhythms}.
96 @lilypond[verbatim,quote,relative=2]
97 \new RhythmicStaff { c4 d e f }
100 @code{TabStaff} creates a tablature with six strings in standard
101 guitar tuning. For details, see @ref{Default tablatures}.
103 @lilypond[verbatim,quote,relative=2]
104 \new TabStaff { c4 d e f }
107 There are two staff contexts specific for the notation of ancient
108 music: @code{MensuralStaff} and @code{VaticanaStaff}. They are
109 described in @ref{Pre-defined contexts}.
111 The @code{GregorianTranscriptionStaff} context creates a staff to
112 notate modern Gregorian chant. It does not show bar lines.
114 @lilypond[verbatim,quote,relative=2]
115 \new GregorianTranscriptionStaff { c4 d e f e d }
118 New single staff contexts may be defined. For details, see
119 @ref{Defining new contexts}.
127 @ref{Creating and referencing contexts},
128 @ref{Percussion staves},
129 @ref{Showing melody rhythms},
130 @ref{Default tablatures},
131 @ref{Pre-defined contexts},
133 @ref{Gregorian chant contexts},
134 @ref{Mensural contexts},
135 @ref{Defining new contexts}.
138 @rlsr{Staff notation}.
142 @rinternals{DrumStaff},
143 @rinternals{GregorianTranscriptionStaff},
144 @rinternals{RhythmicStaff},
145 @rinternals{TabStaff},
146 @rinternals{MensuralStaff},
147 @rinternals{VaticanaStaff},
148 @rinternals{StaffSymbol}.
151 @node Grouping staves
152 @unnumberedsubsubsec Grouping staves
154 @cindex start of system
155 @cindex staff, multiple
156 @cindex staves, multiple
157 @cindex system start delimiters
158 @cindex bracket, vertical
159 @cindex brace, vertical
169 Various contexts exist to group single staves together in order to
170 form multi-stave systems. Each grouping context sets the style of
171 the system start delimiter and the behavior of bar lines.
173 If no context is specified, the default properties will be used:
174 the group is started with a vertical line, and the bar lines are
177 @lilypond[verbatim,quote,relative=2]
184 In the @code{StaffGroup} context, the group is started with a
185 bracket and bar lines are drawn through all the staves.
187 @lilypond[verbatim,quote,relative=2]
194 In a @code{ChoirStaff}, the group starts with a bracket, but bar
195 lines are not connected.
197 @lilypond[verbatim,quote,relative=2]
204 In a @code{GrandStaff}, the group begins with a brace, and bar
205 lines are connected between the staves.
207 @lilypond[verbatim,quote,relative=2]
214 The @code{PianoStaff} is identical to a @code{GrandStaff}, except
215 that it supports printing the instrument name directly. For
216 details, see @ref{Instrument names}.
218 @lilypond[verbatim,quote,relative=2]
220 \set PianoStaff.instrumentName = #"Piano"
226 Each staff group context sets the property
227 @code{systemStartDelimiter} to one of the following values:
228 @code{SystemStartBar}, @code{SystemStartBrace}, or
229 @code{SystemStartBracket}. A fourth delimiter,
230 @code{SystemStartSquare}, is also available, but it must be
231 explicitly specified.
233 New staff group contexts may be defined. For details, see
234 @ref{Defining new contexts}.
239 @lilypondfile[verbatim,quote,texidoc,doctitle]
240 {use-square-bracket-at-the-start-of-a-staff-group.ly}
242 @lilypondfile[verbatim,quote,texidoc,doctitle]
243 {display-bracket-with-only-one-staff-in-a-system.ly}
245 @cindex mensurstriche layout
246 @cindex renaissance music
247 @cindex transcription of mensural music
248 @cindex mensural music, transcription of
250 @lilypondfile[verbatim,quote,texidoc,doctitle]
251 {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 @node Nested staff groups
279 @unnumberedsubsubsec Nested staff groups
281 @cindex staff, nested
282 @cindex staves, nested
283 @cindex nesting of staves
284 @cindex system start delimiters, nested
285 @cindex nested staff brackets
286 @cindex brackets, nesting of
287 @cindex braces, nesting of
289 Staff-group contexts can be nested to arbitrary depths. In this
290 case, each child context creates a new bracket adjacent to the
291 bracket of its parent group.
293 @lilypond[verbatim,quote,relative=2]
295 \new Staff { c2 c | c2 c }
297 \new Staff { g2 g | g2 g }
298 \new StaffGroup \with {
299 systemStartDelimiter = #'SystemStartSquare
302 \new Staff { e2 e | e2 e }
303 \new Staff { c2 c | c2 c }
309 New nested staff group contexts can be defined. For details, see
310 @ref{Defining new contexts}.
315 @lilypondfile[verbatim,quote,texidoc,doctitle]
320 @ref{Grouping staves},
321 @ref{Instrument names},
322 @ref{Defining new contexts}.
325 @rlsr{Staff notation}.
328 @rinternals{StaffGroup},
329 @rinternals{ChoirStaff},
330 @rinternals{SystemStartBar},
331 @rinternals{SystemStartBrace},
332 @rinternals{SystemStartBracket},
333 @rinternals{SystemStartSquare}.
336 @node Separating systems
337 @unnumberedsubsubsec Separating systems
339 @cindex system separator mark
341 If the number of systems per page changes from page to page it is
342 customary to separate the systems by placing a system separator mark
343 between them. By default the system separator is blank, but can be
344 turned on with a @code{\paper} option.
346 @c \book is required here to display the system separator
347 @c ragged-right is required as there are two systems
348 @lilypond[verbatim,quote,ragged-right]
369 system-separator-markup = \slashSeparator
370 % following commands are needed only to format this documentation
372 paper-height = 100\mm
383 @rlsr{Staff notation}.
386 @node Modifying single staves
387 @subsection Modifying single staves
389 This section explains how to change specific attributes of one
390 staff: for example, modifying the number of staff lines or the
391 staff size. Methods to start and stop staves and set ossia
392 sections are also described.
402 @unnumberedsubsubsec Staff symbol
405 @cindex staff lines, stopping and starting
406 @cindex staff lines, modifying
408 @cindex ledger lines, internal
409 @cindex ledger lines, modifying
411 @funindex \startStaff
416 The @code{\stopStaff} and @code{\startStaff} commands can be used to
417 stop or (re)start the staff lines respectively, from being printed at
418 any point witin a score.
420 @lilypond[verbatim,quote,relative=2]
421 \stopStaff f4 d \startStaff g, e
422 f'4 d \stopStaff g, e
423 f'4 d \startStaff g, e
431 The lines of a staff belong to the @code{StaffSymbol} grob (including
432 ledger lines) and can be modified using @code{StaffSymbol} properties, but
433 these modifications must be made before the staff is (re)started.
435 The number of staff lines can be altered:
437 @lilypond[verbatim,quote,relative=2]
439 \override Staff.StaffSymbol.line-count = #2
443 \revert Staff.StaffSymbol.line-count
447 The position of each staff line can also be altered. A list of
448 numbers sets each line's position. @code{0}@tie{}corresponds to the normal
449 center line, and the normal line positions are
450 @code{(-4@tie{}-2@tie{}0@tie{}2@tie{}4)}. A single staff line is
451 printed for every value entered so that the number of staff lines, as
452 well as their position, can be changed with a single override.
454 @lilypond[verbatim,quote,relative=2]
456 \override Staff.StaffSymbol.line-positions = #'(1 3 5 -1 -3)
459 \override Staff.StaffSymbol.line-positions = #'(8 6.5 -6 -8 -0.5)
463 To preserve typical stem directions (in the bottom half of the staff
464 stems point up, in the top half they point down), align the center
465 line (or space) of the customized staff with the position of the
466 normal center line (0). The clef position and the position of
467 middle@tie{}C may need to be adjusted accordingly to fit the new
468 lines. See @ref{Clef}.
470 Staff line thickness can be altered. Ledger lines and note stems, by
471 default, are also affected.
473 @lilypond[verbatim,quote,relative=2]
475 \override StaffSymbol.thickness = #3
480 It is also possible to set ledger line thickness independently of staff
483 @lilypond[verbatim,quote,relative=2]
485 \override StaffSymbol.thickness = #2
486 \override StaffSymbol.ledger-line-thickness = #'(0.5 . 0.4)
492 The first value is multiplied by the staff line thickness, the second by
493 the staff space and then the two values are added together to give the
494 new thickness of the ledger line.
496 The vertical positions of ledger lines can be altered,
498 @lilypond[verbatim,quote,relative=2]
500 \override StaffSymbol.ledger-positions = #'(-3 -2 -1 2 5 6)
505 Additional ledger lines can be made to appear above or below note heads
506 depending on the current position relative to other note heads that
507 also have their own ledger lines.
509 @lilypond[verbatim,quote,relative=2]
511 \override StaffSymbol.ledger-extra = #4
516 Ledger lines can also be made to appear inside the staff where custom
517 staff lines are required. The example shows the default position of
518 ledger lines when the explicit @code{ledger-position} is and is not set.
519 The @code{\stopStaff} is needed in the example to revert the
520 @code{\override} for the whole @code{StaffSymbol}.
522 @lilypond[verbatim,quote,relative=1]
523 \override Staff.StaffSymbol.line-positions = #'(-8 0 2 4)
527 \override Staff.StaffSymbol.ledger-positions = #'(-8 -6 (-4 -2) 0)
531 The distance between staff lines can be altered. This affects ledger
532 line spacing as well.
534 @lilypond[verbatim,quote,relative=2]
536 \override StaffSymbol.staff-space = #1.5
542 @lilypondfile[verbatim,quote,texidoc,doctitle]
543 {making-some-staff-lines-thicker-than-the-others.ly}
555 @rlsr{Staff notation}.
558 @rinternals{StaffSymbol},
559 @rinternals{staff-symbol-interface}.
563 @unnumberedsubsubsec Ossia staves
565 @cindex staff, Frenched
567 @cindex Frenched staves
568 @cindex staff, resizing of
569 @cindex resizing of staves
571 @funindex \startStaff
576 @notation{Ossia} staves can be set by creating a new simultaneous
577 staff in the appropriate location:
579 @lilypond[verbatim,quote]
580 \new Staff \relative {
584 \new Staff { e4 d f e }
591 However, the above example is not what is usually desired. To
592 create ossia staves that are above the original staff, have no
593 time signature or clef, and have a smaller font size, tweaks must
594 be used. The Learning Manual describes a specific technique to
595 achieve this goal, beginning with
596 @rlearning{Nesting music expressions}.
598 The following example uses the @code{alignAboveContext} property
599 to align the ossia staff. This method is most appropriate when
600 only a few ossia staves are needed.
602 @lilypond[verbatim,quote]
603 \new Staff = "main" \relative {
609 \remove "Time_signature_engraver"
610 alignAboveContext = #"main"
620 If many isolated ossia staves are needed, creating an empty
621 @code{Staff} context with a specific @emph{context id} may be more
622 appropriate; the ossia staves may then be created by
623 @emph{calling} this context and using @code{\startStaff} and
624 @code{\stopStaff} at the desired locations. The benefits of this
625 method are more apparent if the piece is longer than the following
628 @lilypond[verbatim,quote,ragged-right]
630 \new Staff = "ossia" \with {
631 \remove "Time_signature_engraver"
637 \new Staff \relative {
641 \context Staff = "ossia" {
642 \startStaff e4 g8 f e2 \stopStaff
649 \context Staff = "ossia" {
650 \startStaff g4 e8 f g2 \stopStaff
659 Using the @code{\Staff \RemoveEmptyStaves} command to create ossia
660 staves may be used as an alternative. This method is most
661 convenient when ossia staves occur immediately following a line
662 break. For more information about
663 @code{\Staff \RemoveEmptyStaves}, see @ref{Hiding staves}.
665 @lilypond[verbatim,quote,ragged-right]
667 \new Staff = "ossia" \with {
668 \remove "Time_signature_engraver"
675 \new Staff \relative {
687 \Staff \RemoveEmptyStaves
688 \override VerticalAxisGroup.remove-first = ##t
696 @lilypondfile[verbatim,quote,texidoc,doctitle]
697 {vertically-aligning-ossias-and-lyrics.ly}
703 @rglos{Frenched staff}.
706 @rlearning{Nesting music expressions},
707 @rlearning{Size of objects},
708 @rlearning{Length and thickness of objects}.
714 @rlsr{Staff notation}.
717 @rinternals{StaffSymbol}.
721 @unnumberedsubsubsec Hiding staves
723 @cindex Frenched score
724 @cindex Frenched staff
725 @cindex staff, hiding
727 @cindex hiding of staves
730 @funindex \RemoveEmptyStaves
731 @funindex Staff_symbol_engraver
736 Staff lines can be hidden by removing the
737 @code{Staff_symbol_engraver} from the @code{Staff} context. As an
738 alternative, @code{\stopStaff} may be used.
740 @lilypond[verbatim,quote]
742 \remove "Staff_symbol_engraver"
744 \relative { a''8 f e16 d c b a2 }
748 Empty staves can be hidden by setting the
749 @code{\Staff \RemoveEmptyStaves} command in the @code{\layout}
750 block. In orchestral scores, this style is known as @q{Frenched
751 Score}. By default, this command hides and removes all empty
752 staves in a score except for those in the first system.
754 @warning{A staff is considered empty when it contains only
755 multi-measure rests, rests, skips, spacer rests, or a combination of these
758 @lilypond[verbatim,quote,ragged-right]
761 \Staff \RemoveEmptyStaves
782 @code{\Staff \RemoveEmptyStaves} can also be used to create ossia
783 sections for a staff. For details, see @ref{Ossia staves}.
785 @cindex hiding ancient staves
786 @cindex hiding rhythmic staves
788 @funindex \RemoveEmptyStaves
790 The @code{\VaticanaStaff \RemoveEmptyStaves} command may be used to
791 hide empty staves in ancient music contexts. Similarly,
792 @code{\RhythmicStaff \RemoveEmptyStaves} may be used to hide empty
793 @code{RhythmicStaff} contexts.
797 @code{\Staff \RemoveEmptyStaves},
798 @code{\VaticanaStaff \RemoveEmptyStaves},
799 @code{\RhythmicStaff \RemoveEmptyStaves}.
805 @lilypondfile[verbatim,quote,texidoc,doctitle]
806 {removing-the-first-empty-line.ly}
810 @rglos{Frenched staff}.
813 @rlearning{Visibility and color of objects}.
816 @ref{Changing context default settings},
820 @ref{Invisible rests},
821 @ref{Visibility of objects}.
824 @rlsr{Staff notation}.
827 @rinternals{ChordNames},
828 @rinternals{FiguredBass},
831 @rinternals{VerticalAxisGroup},
832 @rinternals{Staff_symbol_engraver}.
835 Removing @code{Staff_symbol_engraver} also hides bar lines. If
836 bar line visibility is forced, formatting errors may occur. In
837 this case, use the following overrides instead of removing the
842 \override NoteHead.no-ledgers = ##t
845 For the Known issues and warnings associated with
846 @code{\Staff \RemoveEmptyStaves} see
847 @ref{Changing context default settings}.
851 @subsection Writing parts
853 This section explains how to insert tempo indications and
854 instrument names into a score. Methods to quote other voices and
855 format cue notes are also described.
859 * Quoting other voices::
860 * Formatting cue notes::
863 @node Instrument names
864 @unnumberedsubsubsec Instrument names
866 @cindex instrument names
867 @cindex instrument names, short
869 Instrument names can be printed on the left side of staves in the
870 @code{Staff}, @code{PianoStaff}, @code{StaffGroup}, @code{GrandStaff}
871 and @code{ChoirStaff} contexts. The value of
872 @code{instrumentName} is used for the first staff, and the value
873 of @code{shortInstrumentName} is used for all succeeding staves.
875 @lilypond[verbatim,quote,ragged-right,relative=1]
877 instrumentName = #"Violin "
878 shortInstrumentName = #"Vln. "
880 { c4.. g'16 c4.. g'16 \break | c1 }
883 @cindex instrument names, complex
885 @code{\markup} can be used to create more complex instrument names:
887 @lilypond[verbatim,quote,relative=2]
889 instrumentName = \markup {
890 \column { "Clarinetti"
891 \line { "in B" \smaller \flat }
898 @cindex instrument names, centering
900 When two or more staff contexts are grouped together, the instrument
901 names and short instrument names are centered by default. To center
902 multi-line instrument names, @code{\center-column} must be used:
904 @lilypond[verbatim,quote,indent=1.5\cm,relative=2]
907 instrumentName = #"Flute"
911 instrumentName = \markup {
912 \center-column { "Clarinet"
913 \line { "in B" \smaller \flat }
922 @funindex short-indent
924 However, if the instrument names are longer, the instrument names in a
925 staff group may not be centered unless the @code{indent} and
926 @code{short-indent} settings are increased. For details about these
927 settings, see @ref{paper variables for shifts and indents,,@code{@bs{}paper} variables for shifts and indents}.
929 @lilypond[verbatim,quote,ragged-right]
933 instrumentName = #"Alto Flute in G"
934 shortInstrumentName = #"Flt."
941 instrumentName = #"Clarinet"
942 shortInstrumentName = #"Clar."
953 short-indent = 1.5\cm
957 @cindex instrument names, adding to other contexts
959 To add instrument names to other contexts (such as @code{ChordNames} or
960 @code{FiguredBass}), @code{Instrument_name_engraver} must be added to
961 that context. For details, see @ref{Modifying context plug-ins}.
963 @cindex instrument names, changing
964 @cindex changing instrument names
966 The @code{shortInstrumentName} may be changed in the middle of a piece,
967 along with other settings as needed for the new instrument.
968 However, only the first instance of @code{instrumentName} will be
969 printed and subsequent changes will be ignored:
971 @lilypond[verbatim,quote,ragged-right]
972 prepPiccolo = <>^\markup \italic { muta in Piccolo }
975 \set Staff.instrumentName = #"Piccolo"
976 \set Staff.shortInstrumentName = #"Picc."
977 \set Staff.midiInstrument = #"piccolo"
978 <>^\markup \bold { Piccolo }
982 prepFlute = <>^\markup \italic { muta in Flauto }
985 \set Staff.instrumentName = #"Flute"
986 \set Staff.shortInstrumentName = #"Flt."
987 \set Staff.midiInstrument = #"flute"
988 <>^\markup \bold { Flute }
993 instrumentName = #"Flute"
994 shortInstrumentName = #"Flt."
995 midiInstrument = #"flute"
999 g1 g \prepPiccolo R R \break
1002 g1 g \prepFlute R R \break
1011 @ref{paper variables for shifts and indents,,@code{@bs{}paper} variables for shifts and indents},
1012 @ref{Modifying context plug-ins}.
1015 @rlsr{Staff notation}.
1017 Internals Reference:
1018 @rinternals{InstrumentName},
1019 @rinternals{PianoStaff},
1023 @node Quoting other voices
1024 @unnumberedsubsubsec Quoting other voices
1026 @cindex quote, voices
1027 @cindex voices, quoting
1028 @cindex fragments, quoting
1033 @funindex \quoteDuring
1034 @funindex quoteDuring
1035 @funindex \transposition
1036 @funindex transposition
1038 It is very common for one voice to use the same notes as those from
1039 another voice. For example, first and second violins playing the same
1040 phrase during a particular passage of the music. This is done by
1041 letting one voice @emph{quote} the other, without having to re-enter the
1042 music all over again for the second voice.
1044 The @code{\addQuote} command, used in the top level scope, defines a
1045 stream of music from which fragments can be quoted.
1047 The @code{\quoteDuring} command is used to indicate the point where the
1048 quotation begins. It is followed by two arguments: the name of the
1049 quoted voice, as defined with @code{\addQuote}, and a music expression
1050 for the duration of the quote.
1052 @lilypond[verbatim,quote]
1053 fluteNotes = \relative {
1054 a'4 gis g gis | b4^"quoted" r8 ais\p a4( f)
1057 oboeNotes = \relative {
1058 c''4 cis c b \quoteDuring #"flute" { s1 }
1061 \addQuote "flute" { \fluteNotes }
1065 \new Staff \with { instrumentName = "Flute" } \fluteNotes
1066 \new Staff \with { instrumentName = "Oboe" } \oboeNotes
1071 If the music expression used in @code{\quoteDuring} contains notes
1072 instead of spacer or multimeasure rests then the quote will appear as
1073 polyphony and may produce unexpected results.
1075 @lilypond[verbatim,quote]
1076 fluteNotes = \relative {
1077 a'4 gis g gis | b4^"quoted" r8 ais\p a4( f)
1080 oboeNotes = \relative {
1081 c''4 cis c b \quoteDuring #"flute" { e4 r8 ais b4 a }
1084 \addQuote "flute" { \fluteNotes }
1088 \new Staff \with { instrumentName = "Flute" } \fluteNotes
1089 \new Staff \with { instrumentName = "Oboe" } \oboeNotes
1094 The @code{\quoteDuring} command uses the @code{\transposition} settings
1095 of both quoted and quoting parts to produce notes for the quoting part
1096 that have the same sounding pitch as those in the quoted part.
1098 @lilypond[verbatim,quote]
1099 clarinetNotes = \relative c'' {
1102 b4 ais a ais | cis4^"quoted" r8 bis\p b4( f)
1105 oboeNotes = \relative {
1106 c''4 cis c b \quoteDuring #"clarinet" { s1 }
1109 \addQuote "clarinet" { \clarinetNotes }
1114 \new Staff \with { instrumentName = "Clarinet" } \clarinetNotes
1115 \new Staff \with { instrumentName = "Oboe" } \oboeNotes
1121 @cindex articulation-event
1122 @cindex dynamic-event
1125 @cindex crescendo-event
1127 @funindex quotedEventTypes
1128 @funindex quotedCueEventTypes
1130 By default quoted music will include all articulations, dynamics,
1131 markups, etc., in the quoted expression. It is possible to choose which
1132 of these objects from the quoted music are displayed by using the
1133 @code{quotedEventTypes} context property.
1135 @lilypond[verbatim,quote]
1136 fluteNotes = \relative {
1138 b4\<^"quoted" r8 ais a4\f( c->)
1141 oboeNotes = \relative {
1143 \quoteDuring #"flute" { s1 }
1146 \addQuote "flute" { \fluteNotes }
1150 \set Score.quotedEventTypes = #'(note-event articulation-event
1151 crescendo-event rest-event
1152 slur-event dynamic-event)
1153 \new Staff \with { instrumentName = "Flute" } \fluteNotes
1154 \new Staff \with { instrumentName = "Oboe" } \oboeNotes
1159 Quotes can also be tagged, see @ref{Using tags}.
1163 @ref{Instrument transpositions},
1167 @file{scm/define-event-classes.scm}.
1170 @rlsr{Staff notation}.
1172 Internals Reference:
1173 @rinternals{Music classes},
1174 @rinternals{QuoteMusic},
1178 Only the contents of the first @code{Voice} occurring in an
1179 @code{\addQuote} command will be considered for quotation, so if the music
1180 expression contains @code{\new} or @code{\context Voice}
1181 statements, their contents will not be quoted. Quoting grace notes
1182 is unsupported and may cause LilyPond to crash whereas quoting nested
1183 triplets may result in poor notation.
1186 @node Formatting cue notes
1187 @unnumberedsubsubsec Formatting cue notes
1191 @cindex cue notes, formatting
1192 @cindex formatting, cue notes
1193 @cindex voices, quoting
1196 @funindex \cueDuring
1200 @funindex \cueDuringWithClef
1201 @funindex cueDuringWithClef
1202 @funindex \quoteDuring
1203 @funindex quoteDuring
1205 @cindex notes, smaller
1206 @cindex smaller notes
1209 The simplest way to format cue notes is to explicitly create a
1210 @code{CueVoice} context within the part.
1212 @lilypond[verbatim,relative=1]
1217 \stemUp d'8^"flute" c d e fis2
1223 The @code{\cueClef} command can also be used with an explict
1224 @code{CueVoice} context if a change of clef is required and will print
1225 an appropriately sized clef for the cue notes. The @code{\cueClefUnset}
1226 command can then be used to switch back to the original clef, again with
1227 an appropriately sized clef.
1229 @lilypond[verbatim,noragged-right,relative=1]
1233 { e2\rest r4. \cueClefUnset e,8 }
1235 \cueClef "treble" \stemUp d''8^"flute" c d e fis2
1241 The @code{\cueClef} and @code{\cueClefUnset} command can also be used
1242 without a @code{CueVoice} if required.
1244 @lilypond[verbatim,noragged-right,relative=1]
1248 d'8^"flute" c d e fis2
1253 For more complex cue note placement, e.g including transposition, or
1254 inserting cue notes from multiple music sources the @code{\cueDuring} or
1255 @code{\cueDuringWithClef} commands can be used. These are more
1256 specialized form of @code{\quoteDuring}, see @ref{Quoting other voices}
1257 in the previous section.
1262 \cueDuring #@var{quotename} #@var{direction} #@var{music}
1268 \cueDuringWithClef #@var{quotename} #@var{direction} #@var{clef} #@var{music}
1271 The music from the corresponding measures of the @code{@var{quote name}}
1272 is added as a @code{CueVoice} context and occurs simultaneously with the
1273 @code{@var{music}}, which then creates a polyphonic situation. The
1274 @code{@var{direction}} takes the argument @code{UP} or @code{DOWN}, and
1275 corresponds to the first and second voices respectively, determining how
1276 the cue notes are printed in relation to the other voice.
1278 @lilypond[verbatim,quote]
1279 fluteNotes = \relative {
1280 r2. c''4 | d8 c d e fis2 | g2 d |
1283 oboeNotes = \relative c'' {
1285 <>^\markup \tiny { flute }
1286 \cueDuring #"flute" #UP { R1 }
1290 \addQuote "flute" { \fluteNotes }
1300 It is possible to adjust which aspects of the music are quoted with
1301 @code{\cueDuring} by setting the @code{quotedCueEventTypes}
1302 property. Its default value is @code{'(note-event rest-event
1303 tie-event beam-event tuplet-span-event)}, which means that only
1304 notes, rests, ties, beams and tuplets are quoted, but not
1305 articulations, dynamic marks, markup etc.
1307 @warning{When a @code{Voice} starts with @code{\cueDuring}, as in the
1308 following example, the @code{Voice} context must be explicitly declared,
1309 or else the entire music expression would belong to the @code{CueVoice}
1312 @lilypond[verbatim,quote]
1313 oboeNotes = \relative {
1314 r2 r8 d''16(\f f e g f a)
1317 \addQuote "oboe" { \oboeNotes }
1319 \new Voice \relative c'' {
1320 \set Score.quotedCueEventTypes = #'(note-event rest-event tie-event
1321 beam-event tuplet-span-event
1322 dynamic-event slur-event)
1323 \cueDuring #"oboe" #UP { R1 }
1328 Markup can be used to show the name of the quoted instrument.
1329 If the cue notes require a change in clef,
1330 this can be done manually but the original clef should also be
1331 restored manually at the end of the cue notes.
1333 @lilypond[verbatim,quote]
1334 fluteNotes = \relative {
1335 r2. c''4 d8 c d e fis2 g2 d2
1338 bassoonNotes = \relative c {
1342 <>^\markup \tiny { flute }
1343 \cueDuring #"flute" #UP { R1 }
1348 \addQuote "flute" { \fluteNotes }
1355 Alternatively, the @code{\cueDuringWithClef} function can be used
1356 instead. This command takes an extra argument to specify the change of
1357 clef that needs to be printed for the cue notes but will automatically
1358 print the original clef once the cue notes have finished.
1360 @lilypond[verbatim,quote]
1361 fluteNotes = \relative {
1362 r2. c''4 d8 c d e fis2 g2 d2
1365 bassoonNotes = \relative c {
1368 <>^\markup { \tiny "flute" }
1369 \cueDuringWithClef #"flute" #UP #"treble" { R1 }
1373 \addQuote "flute" { \fluteNotes }
1380 @funindex \transposedCueDuring
1381 @funindex transposedCueDuring
1383 Like @code{\quoteDuring}, @code{\cueDuring} takes instrument
1384 transpositions into account. Cue notes are produced at the
1385 pitches that would be written for the instrument receiving the cue
1386 to produce the sounding pitches of the source instrument.
1388 To transpose cue notes differently, use
1389 @code{\transposedCueDuring}. This command takes an extra argument
1390 to specify (in absolute mode) the printed pitch that you want to
1391 represent the sound of a concert middle C. This is useful for
1392 taking cues from an instrument in a completely different register.
1394 @lilypond[verbatim,quote]
1395 piccoloNotes = \relative {
1402 bassClarinetNotes = \relative c' {
1406 \transposedCueDuring #"piccolo" #UP d { R1 }
1410 \addQuote "piccolo" { \piccoloNotes }
1413 \new Staff \piccoloNotes
1414 \new Staff \bassClarinetNotes
1418 @cindex removing cue notes
1419 @cindex cue notes, removing
1424 The @code{\killCues} command removes cue notes from a music
1425 expression, so the same music expression can be used to produce
1426 the instrument part with cues and the score. The @code{\killCues}
1427 command removes only the notes and events that were quoted by
1428 @code{\cueDuring}. Other markup associated with cues, such as clef
1429 changes and a label identifying the source instrument, can be
1430 tagged for selective inclusion in the score; see @ref{Using tags}.
1432 @lilypond[verbatim,quote]
1433 fluteNotes = \relative {
1434 r2. c''4 d8 c d e fis2 g2 d2
1437 bassoonNotes = \relative c {
1442 <>^\markup \tiny { flute }
1444 \cueDuring #"flute" #UP { R1 }
1445 \tag #'part \clef bass
1449 \addQuote "flute" { \fluteNotes }
1460 \removeWithTag #'part { \killCues { \bassoonNotes } }
1465 Alternatively, Clef changes and instrument labels can be
1466 collected into an instrument definition for repeated use, using
1467 @code{\addInstrumentDefinition} described in @ref{Instrument names}.
1471 @ref{Quoting other voices},
1472 @ref{Instrument transpositions},
1473 @ref{Instrument names},
1479 @rlsr{Staff notation}.
1481 Internals Reference:
1482 @rinternals{CueVoice},
1486 Collisions can occur with rests, when using @code{\cueDuring},
1487 between @code{Voice} and @code{CueVoice} contexts. When using
1488 @code{\cueDuringWithClef} or @code{\transposedCueDuring} the extra
1489 argument required for each case must come after the quote and the