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 @c references - first pass complete
13 @c manual changes - first pass complete
14 @c automatic changes - first pass complete
15 @c staff-change lines - started
18 @c accordian discant symbols
20 @node Keyboard instruments
21 @section Keyboard instruments
24 * Common notation for keyboards::
29 @node Common notation for keyboards
30 @subsection Common notation for keyboards
33 * References for keyboards::
34 * Changing staff manually::
35 * Changing staff automatically::
36 * Staff-change lines::
40 @node References for keyboards
41 @subsubsection References for keyboards
43 Keyboard instruments are usually notated with Piano staves. These
44 are two or more normal staves coupled with a brace. The same
45 notation is also used for harps and other keyed instruments.
46 Organ music is normally written with two staves inside a
47 @code{PianoStaff} group and third, normal staff for the pedals.
49 The staves in keyboard music are largely independent, but
50 sometimes voices can cross between the two staves. In this
51 section we discuss some notation techniques particular to keyboard
54 Several common issues in keyboard music are covered elsewhere:
57 @item Keyboard music usually contains multiple voices and the
58 number of voices may change regularly; this is described in
59 @ref{Collision resolution}.
61 @item Keyboard music can be written in parallel, as described in
62 @ref{Writing music in parallel}.
64 @item Fingerings are indicated with @ref{Fingering instructions}.
66 @item Organ pedal indications are inserted as articulations, see
67 @ref{List of articulations}.
69 @item Vertical grid lines can be shown with @ref{Grid lines}.
71 @item Keyboard music often contains @notation{Laissez vibrer} ties
72 as well as ties on arpeggios and tremelos, described in
75 @item Placing arpeggios across multiple voices and staves is
76 covered in @ref{Arpeggio}.
78 @item Tremolo marks are described in @ref{Tremolo repeats}.
80 @item Several of the tweaks that can occur in keyboard music are
81 demonstrated in @rlearning{Real music example}.
83 @item Hidden notes can be used to produce ties that cross voices,
84 as shown in @rlearning{Other uses for tweaks}.
89 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
90 @c {creating-slurs-across-voices.ly}
95 @rlearning{Real music example},
96 @rlearning{Other uses for tweaks}.
99 @ref{Grouping staves},
100 @ref{Instrument names},
101 @ref{Writing music in parallel},
102 @ref{Fingering instructions},
106 @ref{Tremolo repeats},
107 @ref{List of articulations}.
110 @rinternals{PianoStaff}.
117 Dynamics are not centered, but workarounds do exist. See the
118 @q{piano centered dynamics} template in @rlearning{Piano templates}.
121 @node Changing staff manually
122 @subsubsection Changing staff manually
124 @cindex changing staff manually
125 @cindex manual staff changes
126 @cindex staff changes, manual
127 @cindex cross-staff notes
128 @cindex notes, cross-staff
129 @cindex cross-staff beams
130 @cindex beams, cross-staff
133 Voices can be switched between staves manually, using the command
136 \change Staff = @var{staffname}
140 The string @var{staffname} is the name of the staff. It switches
141 the current voice from its current staff to the Staff called
142 @var{staffname}. Typical values for @var{staffname} are
143 @code{"up"} and @code{"down"}, or @code{"RH"} and @code{"LH"}.
145 Cross-staff notes are beamed automatically:
147 @lilypond[verbatim,quote,ragged-right]
159 \new Staff = "down" {
161 s1 % keep staff alive
166 If the beaming needs to be tweaked, make any changes to the stem
167 directions first. The beam positions are then measured from the
168 center of the staff that is closest to the beam. For a simple
169 example of beam tweaking, see @rlearning{Fixing overlapping
175 @rlearning{Fixing overlapping notation}.
179 @ruser{Automatic beams}.
188 @node Changing staff automatically
189 @subsubsection Changing staff automatically
191 @cindex changing staff automatically
192 @cindex automatic staff changes
193 @cindex staff changes, automatic
194 @funindex \autochange
196 Voices can be made to switch automatically between the top and the
197 bottom staff. The syntax for this is
200 \autochange @dots{}@var{music}@dots{}
204 This will create two staves inside the current staff group
205 (usually a @code{PianoStaff}), called @code{"up"} and
206 @code{"down"}. The lower staff will be in bass clef by default.
207 The autochanger switches on basis of the pitch (middle C is the
208 turning point), and it looks ahead skipping over rests to switch
211 @lilypond[quote,verbatim,ragged-right]
219 A @code{\relative} section that is outside of @code{\autochange}
220 has no effect on the pitches of the music, so if necessary, put
221 @code{\relative} inside @code{\autochange}.
223 If additional control is needed over the individual staves, they
224 can be created manually with the names @code{"up"} and
225 @code{"down"}. The @code{\autochange} command will then switch
226 its voice between the existing staves. For example, this is
227 necessary to place a key signature in the lower staff:
229 @lilypond[quote,verbatim,ragged-right]
232 \new Voice = "melOne" {
234 \autochange \relative c' {
240 \new Staff = "down" {
249 Notation Reference: @ref{Changing staff manually}.
251 Internals Reference: @rinternals{AutoChangeMusic}.
255 The staff switches may not end up in optimal places. For high
256 quality output, staff switches should be specified manually.
258 Chords will not be split across the staves; the staff will be
259 chosen by the first note named in the chord.
262 @node Staff-change lines
263 @subsubsection Staff-change lines
265 @cindex staff-change lines
266 @cindex cross-staff lines
267 @cindex lines, staff-change follower
269 @cindex staff switching
271 @funindex followVoice
273 Whenever a voice switches to another staff, a line connecting the
274 notes can be printed automatically. This is switched on by
275 setting @code{followVoice} to true, or by the shorthand commands
276 @code{\showStaffSwitch} and @code{\hideStaffSwitch}.
278 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
286 \new Staff="two" { \clef bass s1*2 }
292 Internals Reference: @rinternals{VoiceFollower}.
296 @funindex \showStaffSwitch
297 @code{\showStaffSwitch},
298 @funindex \hideStaffSwitch
299 @code{\hideStaffSwitch}.
302 @node Cross-staff stems
303 @subsubsection Cross-staff stems
305 Chords that cross staves may be produced by increasing the length
306 of the stem in the lower staff, so it reaches the stem in the upper
307 staff, or vice versa.
309 @lilypond[ragged-right,verbatim,quote]
311 \once \override Stem #'length = #10
312 \once \override Stem #'cross-staff = ##t
314 noFlag = \once \override Stem #'flag-style = #'no-flag
317 \stemDown \stemExtend
337 @subsubsection Piano pedals
340 Pianos have pedals that alter the way sound is produced. Generally, a
341 piano has three pedals, sustain, una corda, and sostenuto.
344 Piano pedal instruction can be expressed by attaching
345 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
346 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
349 @lilypond[quote,ragged-right,fragment,verbatim]
350 c'4\sustainDown c'4\sustainUp
353 What is printed can be modified by setting @code{pedal@var{X}Strings},
354 where @var{X} is one of the pedal types: @code{Sustain},
355 @code{Sostenuto} or @code{UnaCorda}. Refer to
356 @rinternals{SustainPedal} in the program reference for more
359 Pedals can also be indicated by a sequence of brackets, by setting the
360 @code{pedalSustainStyle} property to bracket objects
362 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
363 \set Staff.pedalSustainStyle = #'bracket
365 b\sustainUp\sustainDown
366 b g \sustainUp a \sustainDown \bar "|."
369 A third style of pedal notation is a mixture of text and brackets,
370 obtained by setting the @code{pedalSustainStyle} property to
373 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
374 \set Staff.pedalSustainStyle = #'mixed
376 b\sustainUp\sustainDown
377 b g \sustainUp a \sustainDown \bar "|."
380 The default @q{*Ped.} style for sustain and damper pedals corresponds to
381 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
384 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
385 c\sostenutoDown d e c, f g a\sostenutoUp
388 For fine-tuning the appearance of a pedal bracket, the properties
389 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
390 @code{PianoPedalBracket} objects (see
391 @rinternals{PianoPedalBracket} in the Internals Reference) can be
392 modified. For example, the bracket may be extended to the right edge
395 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
396 \override Staff.PianoPedalBracket #'shorten-pair = #'(0 . -1.0)
397 c\sostenutoDown d e c, f g a\sostenutoUp
401 Note that overrides must be placed before the note at which the
402 pedal bracket starts.
404 @c TODO Check relative positions of the sustain pedal and
405 @c dynamics are correct (they collided in 2.11.44).
406 @c Give example showing this.
410 Notation Reference: @ref{Ties} (laissez vibrer).
413 @subsection Accordion
419 @node Discant symbols
420 @subsubsection Discant symbols
422 @c TODO Add text from -user and lsr 194