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 @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,quote,texidoc,doctitle]
323 @ref{Grouping staves},
324 @ref{Instrument names},
325 @ref{Defining new contexts}.
328 @rlsr{Staff notation}.
331 @rinternals{StaffGroup},
332 @rinternals{ChoirStaff},
333 @rinternals{SystemStartBar},
334 @rinternals{SystemStartBrace},
335 @rinternals{SystemStartBracket},
336 @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
408 @cindex staff lines, stopping and starting
409 @cindex staff lines, modifying
411 @cindex ledger lines, internal
412 @cindex ledger lines, modifying
414 @funindex \startStaff
419 The @code{\stopStaff} and @code{\startStaff} commands can be used to
420 stop or (re)start the staff lines respectively, from being printed at
421 any point witin a score.
423 @lilypond[verbatim,quote,relative=2]
424 \stopStaff f4 d \startStaff g, e
425 f'4 d \stopStaff g, e
426 f'4 d \startStaff g, e
434 The lines of a staff belong to the @code{StaffSymbol} grob (including
435 ledger lines) and can be modified using @code{StaffSymbol} properties, but
436 these modifications must be made before the staff is (re)started.
438 The number of staff lines can be altered:
440 @lilypond[verbatim,quote,relative=2]
442 \override Staff.StaffSymbol.line-count = #2
446 \revert Staff.StaffSymbol.line-count
450 The position of each staff line can also be altered. A list of
451 numbers sets each line's position. @code{0}@tie{}corresponds to the normal
452 center line, and the normal line positions are
453 @code{(-4@tie{}-2@tie{}0@tie{}2@tie{}4)}. A single staff line is
454 printed for every value entered so that the number of staff lines, as
455 well as their position, can be changed with a single override.
457 @lilypond[verbatim,quote,relative=2]
459 \override Staff.StaffSymbol.line-positions = #'(1 3 5 -1 -3)
462 \override Staff.StaffSymbol.line-positions = #'(8 6.5 -6 -8 -0.5)
466 To preserve typical stem directions (in the bottom half of the staff
467 stems point up, in the top half they point down), align the center
468 line (or space) of the customized staff with the position of the
469 normal center line (0). The clef position and the position of
470 middle@tie{}C may need to be adjusted accordingly to fit the new
471 lines. See @ref{Clef}.
473 Staff line thickness can be altered. Ledger lines and note stems, by
474 default, are also affected.
476 @lilypond[verbatim,quote,relative=2]
478 \override StaffSymbol.thickness = #3
483 However, it is possible to set ledger line thickness independently of
484 staff lines. The two values required multiply the staff line thickness
485 with the staff line spacing and are then added together to give the
486 ledger line thickness.
488 @lilypond[verbatim,quote,relative=2]
490 \override StaffSymbol.thickness = #2
491 \override StaffSymbol.ledger-line-thickness = #'(0.5 . 0.4)
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 c'' {
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 c'' {
609 \remove "Time_signature_engraver"
610 alignAboveContext = #"main"
612 \override StaffSymbol.staff-space = #(magstep -3)
613 \override StaffSymbol.thickness = #(magstep -3)
622 If many isolated ossia staves are needed, creating an empty
623 @code{Staff} context with a specific @emph{context id} may be more
624 appropriate; the ossia staves may then be created by
625 @emph{calling} this context and using @code{\startStaff} and
626 @code{\stopStaff} at the desired locations. The benefits of this
627 method are more apparent if the piece is longer than the following
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)
641 \new Staff \relative c' {
645 \context Staff = "ossia" {
646 \startStaff e4 g8 f e2 \stopStaff
653 \context Staff = "ossia" {
654 \startStaff g4 e8 f g2 \stopStaff
663 Using the @code{\Staff \RemoveEmptyStaves} command to create ossia
664 staves may be used as an alternative. This method is most
665 convenient when ossia staves occur immediately following a line
666 break. For more information about
667 @code{\Staff \RemoveEmptyStaves}, see @ref{Hiding staves}.
669 @lilypond[verbatim,quote,ragged-right]
671 \new Staff = "ossia" \with {
672 \remove "Time_signature_engraver"
673 \override Clef.transparent = ##t
675 \override StaffSymbol.staff-space = #(magstep -3)
676 \override StaffSymbol.thickness = #(magstep -3)
681 \new Staff \relative c' {
693 \Staff \RemoveEmptyStaves
694 \override VerticalAxisGroup.remove-first = ##t
702 @lilypondfile[verbatim,quote,texidoc,doctitle]
703 {vertically-aligning-ossias-and-lyrics.ly}
709 @rglos{Frenched staff}.
712 @rlearning{Nesting music expressions},
713 @rlearning{Size of objects},
714 @rlearning{Length and thickness of objects}.
720 @rlsr{Staff notation}.
723 @rinternals{StaffSymbol}.
727 @unnumberedsubsubsec Hiding staves
729 @cindex Frenched score
730 @cindex Frenched staff
731 @cindex staff, hiding
733 @cindex hiding of staves
736 @funindex \RemoveEmptyStaves
737 @funindex Staff_symbol_engraver
742 Staff lines can be hidden by removing the
743 @code{Staff_symbol_engraver} from the @code{Staff} context. As an
744 alternative, @code{\stopStaff} may be used.
746 @lilypond[verbatim,quote]
748 \remove "Staff_symbol_engraver"
750 \relative c''' { a8 f e16 d c b a2 }
754 Empty staves can be hidden by setting the
755 @code{\Staff \RemoveEmptyStaves} command in the @code{\layout}
756 block. In orchestral scores, this style is known as @q{Frenched
757 Score}. By default, this command hides and removes all empty
758 staves in a score except for those in the first system.
760 @warning{A staff is considered empty when it contains only
761 multi-measure rests, rests, skips, spacer rests, or a combination of these
764 @lilypond[verbatim,quote,ragged-right]
767 \Staff \RemoveEmptyStaves
788 @code{\Staff \RemoveEmptyStaves} can also be used to create ossia
789 sections for a staff. For details, see @ref{Ossia staves}.
791 @cindex hiding ancient staves
792 @cindex hiding rhythmic staves
794 @funindex \RemoveEmptyStaves
796 The @code{\VaticanaStaff \RemoveEmptyStaves} command may be used to
797 hide empty staves in ancient music contexts. Similarly,
798 @code{\RhythmicStaff \RemoveEmptyStaves} may be used to hide empty
799 @code{RhythmicStaff} contexts.
803 @code{\Staff \RemoveEmptyStaves},
804 @code{\VaticanaStaff \RemoveEmptyStaves},
805 @code{\RhythmicStaff \RemoveEmptyStaves}.
811 @lilypondfile[verbatim,quote,texidoc,doctitle]
812 {removing-the-first-empty-line.ly}
816 @rglos{Frenched staff}.
819 @rlearning{Visibility and color of objects}.
822 @ref{Changing context default settings},
826 @ref{Invisible rests},
827 @ref{Visibility of objects}.
830 @rlsr{Staff notation}.
833 @rinternals{ChordNames},
834 @rinternals{FiguredBass},
837 @rinternals{VerticalAxisGroup},
838 @rinternals{Staff_symbol_engraver}.
841 Removing @code{Staff_symbol_engraver} also hides bar lines. If
842 bar line visibility is forced, formatting errors may occur. In
843 this case, use the following overrides instead of removing the
847 \override StaffSymbol.stencil = ##f
848 \override NoteHead.no-ledgers = ##t
851 For the Known issues and warnings associated with
852 @code{\Staff \RemoveEmptyStaves} see
853 @ref{Changing context default settings}.
857 @subsection Writing parts
859 This section explains how to insert tempo indications and
860 instrument names into a score. Methods to quote other voices and
861 format cue notes are also described.
865 * Quoting other voices::
866 * Formatting cue notes::
869 @node Instrument names
870 @unnumberedsubsubsec Instrument names
872 @cindex instrument names
873 @cindex instrument names, short
875 Instrument names can be printed on the left side of staves in the
876 @code{Staff}, @code{PianoStaff}, @code{StaffGroup}, @code{GrandStaff}
877 and @code{ChoirStaff} contexts. The value of
878 @code{instrumentName} is used for the first staff, and the value
879 of @code{shortInstrumentName} is used for all succeeding staves.
881 @lilypond[verbatim,quote,ragged-right,relative=1]
883 instrumentName = #"Violin "
884 shortInstrumentName = #"Vln. "
886 { c4.. g'16 c4.. g'16 \break | c1 }
889 @cindex instrument names, complex
891 @code{\markup} can be used to create more complex instrument names:
893 @lilypond[verbatim,quote,relative=2]
895 instrumentName = \markup {
896 \column { "Clarinetti"
897 \line { "in B" \smaller \flat }
904 @cindex instrument names, centering
906 When two or more staff contexts are grouped together, the instrument
907 names and short instrument names are centered by default. To center
908 multi-line instrument names, @code{\center-column} must be used:
910 @lilypond[verbatim,quote,indent=1.5\cm,relative=2]
913 instrumentName = #"Flute"
917 instrumentName = \markup {
918 \center-column { "Clarinet"
919 \line { "in B" \smaller \flat }
928 @funindex short-indent
930 However, if the instrument names are longer, the instrument names in a
931 staff group may not be centered unless the @code{indent} and
932 @code{short-indent} settings are increased. For details about these
933 settings, see @ref{\paper variables for shifts and indents}.
935 @lilypond[verbatim,quote,ragged-right]
939 instrumentName = #"Alto Flute in G"
940 shortInstrumentName = #"Flt."
947 instrumentName = #"Clarinet"
948 shortInstrumentName = #"Clar."
959 short-indent = 1.5\cm
963 @cindex instrument names, adding to other contexts
965 To add instrument names to other contexts (such as @code{ChordNames} or
966 @code{FiguredBass}), @code{Instrument_name_engraver} must be added to
967 that context. For details, see @ref{Modifying context plug-ins}.
969 @cindex instrument names, changing
970 @cindex changing instrument names
972 The @code{shortInstrumentName} may be changed in the middle of a piece.
973 However, only the first instance of @code{instrumentName} will be
974 printed and subsequent changes will be ignored:
976 @lilypond[verbatim,quote,ragged-right,relative=1]
978 instrumentName = #"Flute"
979 shortInstrumentName = #"Flt."
984 \set Staff.instrumentName = #"Clarinet"
985 \set Staff.shortInstrumentName = #"Clt."
991 @cindex instrument switch
992 @cindex switching instruments
994 @funindex \addInstrumentDefinition
995 @funindex addInstrumentDefinition
996 @funindex \instrumentSwitch
997 @funindex instrumentSwitch
999 If an instrument @emph{switch} is needed,
1000 @code{\addInstrumentDefinition} may be used in combination with
1001 @code{\instrumentSwitch} to create a detailed list of the
1002 necessary changes for the switch. The
1003 @code{\addInstrumentDefinition} command has two arguments: an
1004 identifying string, and an association list of context properties
1005 and values to be used for the instrument. It must be placed in
1006 the toplevel scope. @code{\instrumentSwitch} is used in the music
1007 expression to declare the instrument switch:
1009 @lilypond[verbatim,quote,ragged-right]
1010 \addInstrumentDefinition #"contrabassoon"
1011 #`((instrumentTransposition . ,(ly:make-pitch -1 0 0))
1012 (shortInstrumentName . "Cbsn.")
1013 (clefGlyph . "clefs.F")
1014 (middleCPosition . 6)
1016 (instrumentCueName . ,(make-bold-markup "cbsn."))
1017 (midiInstrument . "bassoon"))
1020 instrumentName = #"Bassoon"
1024 \compressFullBarRests
1027 \instrumentSwitch "contrabassoon"
1035 @ref{\paper variables for shifts and indents},
1036 @ref{Modifying context plug-ins}.
1039 @rlsr{Staff notation}.
1041 Internals Reference:
1042 @rinternals{InstrumentName},
1043 @rinternals{PianoStaff},
1047 @node Quoting other voices
1048 @unnumberedsubsubsec Quoting other voices
1050 @cindex quote, voices
1051 @cindex voices, quoting
1052 @cindex fragments, quoting
1057 @funindex \quoteDuring
1058 @funindex quoteDuring
1059 @funindex \transposition
1060 @funindex transposition
1062 It is very common for one voice to use the same notes as those from
1063 another voice. For example, first and second violins playing the same
1064 phrase during a particular passage of the music. This is done by
1065 letting one voice @emph{quote} the other, without having to re-enter the
1066 music all over again for the second voice.
1068 The @code{\addQuote} command, used in the top level scope, defines a
1069 stream of music from which fragments can be quoted.
1071 The @code{\quoteDuring} command is used to indicate the point where the
1072 quotation begins. It is followed by two arguments: the name of the
1073 quoted voice, as defined with @code{\addQuote}, and a music expression
1074 for the duration of the quote.
1076 @lilypond[verbatim,quote]
1077 fluteNotes = \relative c'' {
1078 a4 gis g gis | b4^"quoted" r8 ais\p a4( f)
1081 oboeNotes = \relative c'' {
1082 c4 cis c b \quoteDuring #"flute" { s1 }
1085 \addQuote "flute" { \fluteNotes }
1089 \new Staff \with { instrumentName = "Flute" } \fluteNotes
1090 \new Staff \with { instrumentName = "Oboe" } \oboeNotes
1095 If the music expression used in @code{\quoteDuring} contains notes
1096 instead of spacer or multimeasure rests then the quote will appear as
1097 polyphony and may produce unexpected results.
1099 @lilypond[verbatim,quote]
1100 fluteNotes = \relative c'' {
1101 a4 gis g gis | b4^"quoted" r8 ais\p a4( f)
1104 oboeNotes = \relative c'' {
1105 c4 cis c b \quoteDuring #"flute" { e4 r8 ais b4 a }
1108 \addQuote "flute" { \fluteNotes }
1112 \new Staff \with { instrumentName = "Flute" } \fluteNotes
1113 \new Staff \with { instrumentName = "Oboe" } \oboeNotes
1118 The @code{\quoteDuring} command uses the @code{\transposition} settings
1119 of both quoted and quoting parts to produce notes for the quoting part
1120 that have the same sounding pitch as those in the quoted part.
1122 @lilypond[verbatim,quote]
1123 clarinetNotes = \relative c'' {
1126 b4 ais a ais | cis4^"quoted" r8 bis\p b4( f)
1129 oboeNotes = \relative c'' {
1130 c4 cis c b \quoteDuring #"clarinet" { s1 }
1133 \addQuote "clarinet" { \clarinetNotes }
1138 \new Staff \with { instrumentName = "Clarinet" } \clarinetNotes
1139 \new Staff \with { instrumentName = "Oboe" } \oboeNotes
1145 @cindex articulation-event
1146 @cindex dynamic-event
1149 @cindex crescendo-event
1151 @funindex quotedEventTypes
1152 @funindex quotedCueEventTypes
1154 By default quoted music will include all articulations, dynamics,
1155 markups, etc., in the quoted expression. It is possible to choose which
1156 of these objects from the quoted music are displayed by using the
1157 @code{quotedEventTypes} context property.
1159 @lilypond[verbatim,quote]
1160 fluteNotes = \relative c'' {
1162 b4\<^"quoted" r8 ais a4\f( c->)
1165 oboeNotes = \relative c'' {
1167 \quoteDuring #"flute" { s1 }
1170 \addQuote "flute" { \fluteNotes }
1174 \set Score.quotedEventTypes = #'(note-event articulation-event
1175 crescendo-event rest-event
1176 slur-event dynamic-event)
1177 \new Staff \with { instrumentName = "Flute" } \fluteNotes
1178 \new Staff \with { instrumentName = "Oboe" } \oboeNotes
1183 Quotes can also be tagged, see @ref{Using tags}.
1187 @ref{Instrument transpositions},
1191 @file{scm/define-event-classes.scm}.
1194 @rlsr{Staff notation}.
1196 Internals Reference:
1197 @rinternals{Music classes},
1198 @rinternals{QuoteMusic},
1202 Only the contents of the first @code{Voice} occurring in an
1203 @code{\addQuote} command will be considered for quotation, so if the music
1204 expression contains @code{\new} or @code{\context Voice}
1205 statements, their contents will not be quoted. Quoting grace notes
1206 is unsupported and may cause LilyPond to crash whereas quoting nested
1207 triplets may result in poor notation.
1210 @node Formatting cue notes
1211 @unnumberedsubsubsec Formatting cue notes
1215 @cindex cue notes, formatting
1216 @cindex formatting, cue notes
1217 @cindex voices, quoting
1220 @funindex \cueDuring
1224 @funindex \cueDuringWithClef
1225 @funindex cueDuringWithClef
1226 @funindex \quoteDuring
1227 @funindex quoteDuring
1229 @cindex notes, smaller
1230 @cindex smaller notes
1233 The simplest way to format cue notes is to explicitly create a
1234 @code{CueVoice} context within the part.
1236 @lilypond[verbatim,relative=1]
1241 \stemUp d'8^"flute" c d e fis2
1247 The @code{\cueClef} command can also be used with an explict
1248 @code{CueVoice} context if a change of clef is required and will print
1249 an appropriately sized clef for the cue notes. The @code{\cueClefUnset}
1250 command can then be used to switch back to the original clef, again with
1251 an appropriately sized clef.
1253 @lilypond[verbatim,noragged-right,relative=1]
1257 { e2\rest r4. \cueClefUnset e,8 }
1259 \cueClef "treble" \stemUp d''8^"flute" c d e fis2
1265 The @code{\cueClef} and @code{\cueClefUnset} command can also be used
1266 without a @code{CueVoice} if required.
1268 @lilypond[verbatim,noragged-right,relative=1]
1272 d'8^"flute" c d e fis2
1277 For more complex cue note placement, e.g including transposition, or
1278 inserting cue notes from multiple music sources the @code{\cueDuring} or
1279 @code{\cueDuringWithClef} commands can be used. These are more
1280 specialized form of @code{\quoteDuring}, see @ref{Quoting other voices}
1281 in the previous section.
1286 \cueDuring #@var{quotename} #@var{direction} #@var{music}
1292 \cueDuringWithClef #@var{quotename} #@var{direction} #@var{clef} #@var{music}
1295 The music from the corresponding measures of the @code{@var{quote name}}
1296 is added as a @code{CueVoice} context and occurs simultaneously with the
1297 @code{@var{music}}, which then creates a polyphonic situation. The
1298 @code{@var{direction}} takes the argument @code{UP} or @code{DOWN}, and
1299 corresponds to the first and second voices respectively, determining how
1300 the cue notes are printed in relation to the other voice.
1302 @lilypond[verbatim,quote]
1303 fluteNotes = \relative c'' {
1304 r2. c4 | d8 c d e fis2 | g2 d |
1307 oboeNotes = \relative c'' {
1309 \new CueVoice { \set instrumentCueName = "flute" }
1310 \cueDuring #"flute" #UP { R1 }
1314 \addQuote "flute" { \fluteNotes }
1324 It is possible to adjust which aspects of the music are quoted with
1325 @code{\cueDuring} by setting the @code{quotedCueEventTypes}
1326 property. Its default value is @code{'(note-event rest-event
1327 tie-event beam-event tuplet-span-event)}, which means that only
1328 notes, rests, ties, beams and tuplets are quoted, but not
1329 articulations, dynamic marks, markup etc.
1331 @warning{When a @code{Voice} starts with @code{\cueDuring}, as in the
1332 following example, the @code{Voice} context must be explicitly declared,
1333 or else the entire music expression would belong to the @code{CueVoice}
1336 @lilypond[verbatim,quote]
1337 oboeNotes = \relative c'' {
1338 r2 r8 d16(\f f e g f a)
1341 \addQuote "oboe" { \oboeNotes }
1343 \new Voice \relative c'' {
1344 \set Score.quotedCueEventTypes = #'(note-event rest-event tie-event
1345 beam-event tuplet-span-event
1346 dynamic-event slur-event)
1347 \cueDuring #"oboe" #UP { R1 }
1352 The name of the instrument playing the cue can be printed by setting
1353 the @code{instrumentCueName} property in a temporary @code{CueVoice}
1354 context. The placement and style of the @code{instrumentCueName} is
1355 controlled by the @code{\instrumentSwitch} object, see
1356 @ref{Instrument names}. If the cue notes require a change in clef,
1357 this can be done manually but the original clef should also be
1358 restored manually at the end of the cue notes.
1360 @lilypond[verbatim,quote]
1361 fluteNotes = \relative c'' {
1362 r2. c4 d8 c d e fis2 g2 d2
1365 bassoonNotes = \relative c {
1369 \new CueVoice { \set instrumentCueName = "flute" }
1370 \cueDuring #"flute" #UP { R1 }
1375 \addQuote "flute" { \fluteNotes }
1382 Alternatively, the @code{\cueDuringWithClef} function can be used
1383 instead. This command takes an extra argument to specify the change of
1384 clef that needs to be printed for the cue notes but will automatically
1385 print the original clef once the cue notes have finished.
1387 @lilypond[verbatim,quote]
1388 fluteNotes = \relative c'' {
1389 r2. c4 d8 c d e fis2 g2 d2
1392 bassoonNotes = \relative c {
1395 \new CueVoice { \set instrumentCueName = "flute" }
1396 \cueDuringWithClef #"flute" #UP #"treble" { R1 }
1400 \addQuote "flute" { \fluteNotes }
1407 @funindex \transposedCueDuring
1408 @funindex transposedCueDuring
1410 Like @code{\quoteDuring}, @code{\cueDuring} takes instrument
1411 transpositions into account. Cue notes are produced at the
1412 pitches that would be written for the instrument receiving the cue
1413 to produce the sounding pitches of the source instrument.
1415 To transpose cue notes differently, use
1416 @code{\transposedCueDuring}. This command takes an extra argument
1417 to specify (in absolute mode) the printed pitch that you want to
1418 represent the sound of a concert middle C. This is useful for
1419 taking cues from an instrument in a completely different register.
1421 @lilypond[verbatim,quote]
1422 piccoloNotes = \relative c''' {
1429 bassClarinetNotes = \relative c' {
1433 \transposedCueDuring #"piccolo" #UP d { R1 }
1437 \addQuote "piccolo" { \piccoloNotes }
1440 \new Staff \piccoloNotes
1441 \new Staff \bassClarinetNotes
1445 @cindex removing cue notes
1446 @cindex cue notes, removing
1450 @funindex \addInstrumentDefinition
1451 @funindex addInstrumentDefinition
1453 The @code{\killCues} command removes cue notes from a music
1454 expression, so the same music expression can be used to produce
1455 the instrument part with cues and the score. The @code{\killCues}
1456 command removes only the notes and events that were quoted by
1457 @code{\cueDuring}. Other markup associated with cues, such as clef
1458 changes and a label identifying the source instrument, can be
1459 tagged for selective inclusion in the score; see @ref{Using tags}.
1461 @lilypond[verbatim,quote]
1462 fluteNotes = \relative c'' {
1463 r2. c4 d8 c d e fis2 g2 d2
1466 bassoonNotes = \relative c {
1471 \new CueVoice { \set instrumentCueName = "flute" }
1473 \cueDuring #"flute" #UP { R1 }
1474 \tag #'part \clef bass
1478 \addQuote "flute" { \fluteNotes }
1489 \removeWithTag #'part { \killCues { \bassoonNotes } }
1494 Alternatively, Clef changes and instrument labels can be
1495 collected into an instrument definition for repeated use, using
1496 @code{\addInstrumentDefinition} described in @ref{Instrument names}.
1500 @ref{Quoting other voices},
1501 @ref{Instrument transpositions},
1502 @ref{Instrument names},
1508 @rlsr{Staff notation}.
1510 Internals Reference:
1511 @rinternals{CueVoice},
1515 Collisions can occur with rests, when using @code{\cueDuring},
1516 between @code{Voice} and @code{CueVoice} contexts. When using
1517 @code{\cueDuringWithClef} or @code{\transposedCueDuring} the extra
1518 argument required for each case must come after the quote and the