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..
12 @node Keyboard and other multi-staff instruments
13 @section Keyboard and other multi-staff instruments
15 @lilypondfile[quote]{keyboard-headword.ly}
17 This section discusses several aspects of music notation that are
18 unique to keyboard instruments and other instruments notated on
19 many staves, such as harps and vibraphones. For the purposes of
20 this section this entire group of multi-staff instruments is called
21 @qq{keyboards} for short, even though some of them do not have a
25 * Common notation for keyboards::
31 @node Common notation for keyboards
32 @subsection Common notation for keyboards
34 This section discusses notation issues that may arise for most
38 * References for keyboards::
39 * Changing staff manually::
40 * Changing staff automatically::
41 * Staff-change lines::
45 @node References for keyboards
46 @unnumberedsubsubsec References for keyboards
50 @cindex staves, keyboard instruments
51 @cindex staves, keyed instruments
52 @cindex keyboard instrument staves
53 @cindex keyed instrument staves
54 @cindex keyboard music, centering dynamics
55 @cindex dynamics, centered in keyboard music
56 @cindex piano music, centering dynamics
57 @cindex centered dynamics in piano music
61 Keyboard instruments are usually notated with Piano staves. These
62 are two or more normal staves coupled with a brace. The same
63 notation is also used for other keyed instruments.
64 Organ music is normally written with two staves inside a
65 @code{PianoStaff} group and third, normal staff for the pedals.
67 The staves in keyboard music are largely independent, but
68 sometimes voices can cross between the two staves. This
69 section discusses notation techniques particular to keyboard
72 Several common issues in keyboard music are covered elsewhere:
76 @item Keyboard music usually contains multiple voices and the
77 number of voices may change regularly; this is described in
78 @ref{Collision resolution}.
80 @item Keyboard music can be written in parallel, as described in
81 @ref{Writing music in parallel}.
83 @item Dynamics may be placed in a @code{Dynamics} context,
84 between the two @code{Staff} contexts
85 to align the dynamic marks on a horizontal line
86 centered between the staves; see @ref{Dynamics}.
88 @item Fingerings are indicated with @ref{Fingering instructions}.
90 @item Organ pedal indications are inserted as articulations, see
91 @ref{List of articulations}.
93 @item Vertical grid lines can be shown with @ref{Grid lines}.
95 @item Keyboard music often contains @notation{Laissez vibrer} ties
96 as well as ties on arpeggios and tremolos, described in
99 @item Placing arpeggios across multiple voices and staves is
100 covered in @ref{Arpeggio}.
102 @item Tremolo marks are described in @ref{Tremolo repeats}.
104 @item Several of the tweaks that can occur in keyboard music are
105 demonstrated in @rlearning{Real music example}.
107 @item Hidden notes can be used to produce ties that cross voices,
108 as shown in @rlearning{Other uses for tweaks}.
113 @c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
114 @c {forcing-visibility-of-systems-with-multi-bar-rests-when-using-\RemoveEmptyStaffContext.ly}
115 @c http://lsr.dsi.unimi.it/LSR/Item?u=1&id=312
119 @rlearning{Real music example},
120 @rlearning{Other uses for tweaks}.
123 @ref{Grouping staves},
124 @ref{Instrument names},
125 @ref{Collision resolution},
126 @ref{Writing music in parallel},
127 @ref{Fingering instructions},
128 @ref{List of articulations},
132 @ref{Tremolo repeats}.
135 @rinternals{PianoStaff}.
140 @node Changing staff manually
141 @unnumberedsubsubsec Changing staff manually
143 @cindex changing staff manually
144 @cindex manual staff changes
145 @cindex staff changes, manual
146 @cindex cross-staff notes
147 @cindex notes, cross-staff
148 @cindex cross-staff beams
149 @cindex beams, cross-staff
154 Voices can be switched between staves manually, using the command
157 \change Staff = @var{staffname}
161 The string @var{staffname} is the name of the staff. It switches
162 the current voice from its current staff to the staff called
163 @var{staffname}. Typical values for @var{staffname} are
164 @code{"up"} and @code{"down"}, or @code{"RH"} and @code{"LH"}.
166 The staff to which the voice is being switched must exist at the
167 time of the switch. If necessary, staves should be @qq{kept alive},
168 see @ref{Keeping contexts alive}.
170 Cross-staff notes are beamed automatically:
172 @lilypond[verbatim,quote]
176 \change Staff = "down"
180 \change Staff = "down"
184 \new Staff = "down" {
192 If the beaming needs to be tweaked, make any changes to the stem
193 directions first. The beam positions are then measured from the
194 center of the staff that is closest to the beam. For a simple
195 example of beam tweaking, see @rlearning{Fixing overlapping
198 @cindex cross-staff collisions
199 @cindex collisions, cross-staff voices
201 Overlapping notation can result when voices cross staves:
203 @lilypond[verbatim,quote]
207 % Make space for fingering in the cross-staff voice
208 \once\override DynamicLineSpanner #'staff-padding = #3.4
209 e''2\p\< d''\> s1*0\!
211 \new Staff = "down" <<
214 s4. e,8\rest g,2\rest
224 The stem and slur overlap the intervening line of dynamics
225 because automatic collision resolution is suspended for beams, slurs
226 and other spanners that connect notes on different staves,
227 as well as for stems and articulations if their placement is
228 affected by a cross-staff spanner.
229 The resulting collisions must be resolved manually, where necessary,
230 using the methods in @rlearning{Fixing overlapping notation}.
234 @rlearning{Fixing overlapping notation}.
238 @ref{Automatic beams},
239 @ref{Keeping contexts alive}.
246 @rinternals{ContextChange}.
249 @node Changing staff automatically
250 @unnumberedsubsubsec Changing staff automatically
252 @cindex changing staff automatically
253 @cindex automatic staff changes
254 @cindex staff changes, automatic
256 @funindex \autochange
260 Voices can be made to switch automatically between the top and the
261 bottom staff. The syntax for this is
264 \autochange @dots{}@var{music}@dots{}
268 This will create two staves inside the current staff group
269 (usually a @code{PianoStaff}), called @code{"up"} and
270 @code{"down"}. The lower staff will be in the bass clef by default.
271 The autochanger switches on the basis of the pitch (middle@tie{}C is the
272 turning point), and it looks ahead skipping over rests to switch
275 @lilypond[quote,verbatim]
284 @cindex relative music and autochange
285 @cindex autochange and relative music
290 A @code{\relative} section that is outside of @code{\autochange}
291 has no effect on the pitches of the music, so if necessary, put
292 @code{\relative} inside @code{\autochange}.
294 If additional control is needed over the individual staves, they
295 can be created manually with the names @code{"up"} and
296 @code{"down"}. The @code{\autochange} command will then switch
297 its voice between the existing staves.
299 @warning{If staves are created manually, they @emph{must} be named
300 @code{"up"} and @code{"down"}.}
302 For example, staves must be created manually in order to place a
303 key signature in the lower staff:
305 @lilypond[quote,verbatim]
308 \new Voice = "melOne" {
310 \autochange \relative c' {
316 \new Staff = "down" {
326 @ref{Changing staff manually}.
332 @rinternals{AutoChangeMusic}.
337 @cindex chords, splitting across staves with \autochange
339 The staff switches may not end up in optimal places. For high
340 quality output, staff switches should be specified manually.
342 Chords will not be split across the staves; they will be assigned to a
343 staff based on the first note named in the chord construct.
345 @node Staff-change lines
346 @unnumberedsubsubsec Staff-change lines
348 @cindex staff-change line
349 @cindex staff change line
350 @cindex cross-staff line
351 @cindex cross staff line
352 @cindex line, staff-change follower
353 @cindex line, cross-staff
354 @cindex line, staff-change
356 @cindex voice, following
357 @cindex staff switching
360 @funindex followVoice
361 @funindex \showStaffSwitch
362 @funindex showStaffSwitch
363 @funindex \hideStaffSwitch
364 @funindex hideStaffSwitch
366 Whenever a voice switches to another staff, a line connecting the
367 notes can be printed automatically:
369 @lilypond[quote,verbatim,relative=1]
374 \change Staff = "two"
386 @code{\showStaffSwitch},
387 @code{\hideStaffSwitch}.
396 @rinternals{Note_head_line_engraver},
397 @rinternals{VoiceFollower}.
400 @node Cross-staff stems
401 @unnumberedsubsubsec Cross-staff stems
403 @cindex cross-staff notes
404 @cindex cross staff notes
405 @cindex notes, cross-staff
406 @cindex cross-staff stems
407 @cindex cross staff stems
408 @cindex stems, cross-staff
409 @cindex chords, cross-staff
410 @cindex cross-staff chords
411 @cindex cross staff chords
414 @funindex cross-staff
418 Chords that cross staves may be produced:
420 @lilypond[verbatim,quote]
431 % stems may overlap the other staff
432 \override Stem #'cross-staff = ##t
433 % extend the stems to reach the other staff
434 \override Stem #'length = #12
435 % do not print extra flags
436 \override Stem #'flag-style = #'no-flag
437 % prevent beaming as needed
438 a8 g4 f8 f bes\noBeam g4
450 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
451 {indicating-cross-staff-chords-with-arpeggio-bracket.ly}
465 This section discusses notation issues that relate most directly to the
473 @unnumberedsubsubsec Piano pedals
476 @cindex pedals, piano
477 @cindex sustain pedal
478 @cindex pedal, sustain
479 @cindex sostenuto pedal
480 @cindex pedal, sostenuto
488 @funindex \sustainOff
490 @funindex \sostenutoOn
491 @funindex sostenutoOn
492 @funindex \sostenutoOff
493 @funindex sostenutoOff
499 Pianos generally have three pedals that alter the way sound is
500 produced: @notation{sustain}, @notation{sostenuto}
501 (@notation{sos.}), and @notation{una corda} (@notation{U.C.}).
502 Sustain pedals are also found on vibraphones and celestas.
504 @lilypond[quote,verbatim,relative=2]
507 c4\sostenutoOn e g c,
508 <bes d f>1\sostenutoOff
513 @cindex pedal indication styles
514 @cindex pedal indication, text
515 @cindex pedal indication, bracket
516 @cindex pedal indication, mixed
517 @cindex pedal sustain style
518 @cindex sustain pedal style
520 @funindex pedalSustainStyle
525 There are three styles of pedal indications: text, bracket, and mixed.
526 The sustain pedal and the una corda pedal use the text style by default
527 while the sostenuto pedal uses mixed by default.
529 @lilypond[quote,verbatim,relative=2]
530 c4\sustainOn g c2\sustainOff
531 \set Staff.pedalSustainStyle = #'mixed
533 d\sustainOff\sustainOn g, c2\sustainOff
534 \set Staff.pedalSustainStyle = #'bracket
536 d\sustainOff\sustainOn g, c2
540 The placement of the pedal commands matches the physical movement of the
541 sustain pedal during piano performance. Pedalling to the final bar line
542 is indicated by omitting the final pedal off command.
544 Pedal indications may be placed in a @code{Dynamics} context,
545 which aligns them on a horizontal line.
555 @rinternals{SustainPedal},
556 @rinternals{SustainPedalLineSpanner},
557 @rinternals{SustainEvent},
558 @rinternals{SostenutoPedal},
559 @rinternals{SostenutoPedalLineSpanner},
560 @rinternals{SostenutoEvent},
561 @rinternals{UnaCordaPedal},
562 @rinternals{UnaCordaPedalLineSpanner},
563 @rinternals{UnaCordaEvent},
564 @rinternals{PianoPedalBracket},
565 @rinternals{Piano_pedal_engraver}.
569 @subsection Accordion
573 This section discusses notation that is unique to the accordion.
579 @node Discant symbols
580 @unnumberedsubsubsec Discant symbols
582 @cindex accordion discant symbols
583 @cindex discant symbols, accordion
584 @cindex accordion shifts
585 @cindex accordion shift symbols
587 Accordions are often built with more than one set of reeds that may be
588 in unison with, an octave above, or an octave below the written pitch.
589 Each accordion maker has different names for the @notation{shifts} that
590 select the various reed combinations, such as @notation{oboe},
591 @notation{musette}, or @notation{bandonium}, so a system of symbols has
592 come into use to simplify the performance instructions.
596 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
597 {accordion-discant-symbols.ly}
608 This section discusses notation issues that are unique to the harp.
611 * References for harps::
615 @node References for harps
616 @unnumberedsubsubsec References for harps
620 Some common characteristics of harp music are covered elsewhere:
624 @item The glissando is the most characteristic harp technique,
627 @item A @notation{bisbigliando} is written as a tremelo @ref{Tremolo
630 @item Natural harmonics are covered under @ref{Harmonics}.
632 @item For directional arpeggios and non-arpeggios, see @ref{Arpeggio}.
638 @ref{Tremolo repeats},
644 @unnumberedsubsubsec Harp pedals
647 @cindex harp pedal diagrams
649 @cindex pedal diagrams, harp
651 Harps have seven strings per octave that may be sounded at the natural,
652 flattened, or sharpened pitch. In lever harps, each string is adjusted
653 individually, but in pedal harps every string with the same pitch name
654 is controlled by a single pedal. From the player's left to right, the
655 pedals are D, C, and B on the left and E, F, G, and A on the right.
656 The position of the pedals may be indicated with text marks:
658 @lilypond[quote,verbatim,relative=2]
660 cis1_\markup \concat \vcenter {
661 [D \flat C \sharp B|E \sharp F \sharp G A \flat] }
662 c!1_\markup \concat \vcenter {
668 @lilypond[quote,verbatim,relative=2]
670 cis1_\markup { \harp-pedal #"^v-|vv-^" }
671 c!1_\markup { \harp-pedal #"^o--|vv-^" }
674 The @code{\harp-pedal} command accepts a string of characters, where
675 @code{^} is the highest pedal position (flattened pitch), @code{-} is
676 the middle pedal position (natural pitch), @code{v} is the lowest pedal
677 position (sharpened pitch), and @code{|} is the divider. A prefixed
678 @code{o} will circle the following pedal symbol.
683 @ref{Instrument Specific Markup}.