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 - first pass complete
16 @c cross-staff stems - first pass complete
17 @c pedals - first pass complete
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]
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}.
120 @c TODO Find out status of the dynamics engravers
122 @node Changing staff manually
123 @subsubsection Changing staff manually
125 @cindex changing staff manually
126 @cindex manual staff changes
127 @cindex staff changes, manual
128 @cindex cross-staff notes
129 @cindex notes, cross-staff
130 @cindex cross-staff beams
131 @cindex beams, cross-staff
134 Voices can be switched between staves manually, using the command
137 \change Staff = @var{staffname}
141 The string @var{staffname} is the name of the staff. It switches
142 the current voice from its current staff to the Staff called
143 @var{staffname}. Typical values for @var{staffname} are
144 @code{"up"} and @code{"down"}, or @code{"RH"} and @code{"LH"}.
146 Cross-staff notes are beamed automatically:
148 @lilypond[verbatim,quote,ragged-right]
160 \new Staff = "down" {
162 s1 % keep staff alive
167 If the beaming needs to be tweaked, make any changes to the stem
168 directions first. The beam positions are then measured from the
169 center of the staff that is closest to the beam. For a simple
170 example of beam tweaking, see @rlearning{Fixing overlapping
176 @rlearning{Fixing overlapping notation}.
180 @ref{Automatic beams}.
189 @node Changing staff automatically
190 @subsubsection Changing staff automatically
192 @cindex changing staff automatically
193 @cindex automatic staff changes
194 @cindex staff changes, automatic
195 @funindex \autochange
197 Voices can be made to switch automatically between the top and the
198 bottom staff. The syntax for this is
201 \autochange @dots{}@var{music}@dots{}
205 This will create two staves inside the current staff group
206 (usually a @code{PianoStaff}), called @code{"up"} and
207 @code{"down"}. The lower staff will be in bass clef by default.
208 The autochanger switches on basis of the pitch (middle C is the
209 turning point), and it looks ahead skipping over rests to switch
212 @lilypond[quote,verbatim,ragged-right]
220 A @code{\relative} section that is outside of @code{\autochange}
221 has no effect on the pitches of the music, so if necessary, put
222 @code{\relative} inside @code{\autochange}.
224 If additional control is needed over the individual staves, they
225 can be created manually with the names @code{"up"} and
226 @code{"down"}. The @code{\autochange} command will then switch
227 its voice between the existing staves. For example, this is
228 necessary to place a key signature in the lower staff:
230 @lilypond[quote,verbatim,ragged-right]
233 \new Voice = "melOne" {
235 \autochange \relative c' {
241 \new Staff = "down" {
251 @ref{Changing staff manually}.
257 @rinternals{AutoChangeMusic}.
261 The staff switches may not end up in optimal places. For high
262 quality output, staff switches should be specified manually.
264 Chords will not be split across the staves; the staff will be
265 chosen by the first note named in the chord.
268 @node Staff-change lines
269 @subsubsection Staff-change lines
271 @cindex staff-change lines
272 @cindex cross-staff lines
273 @cindex lines, staff-change follower
275 @cindex staff switching
277 @funindex followVoice
279 Whenever a voice switches to another staff, a line connecting the
280 notes can be printed automatically:
282 @lilypond[quote,ragged-right,fragment,relative=1,verbatim]
290 \new Staff = "two" { \clef bass s1*2 }
296 @funindex \showStaffSwitch
297 @funindex \hideStaffSwitch
298 @code{\showStaffSwitch}, @code{\hideStaffSwitch}.
306 @rinternals{VoiceFollower}.
309 @node Cross-staff stems
310 @subsubsection Cross-staff stems
312 @cindex cross-staff notes
313 @cindex notes, cross-staff
314 @cindex cross-staff stems
315 @cindex stems, cross-staff
317 Chords that cross staves may be produced by increasing the length
318 of the stem in the lower staff, so it reaches the stem in the upper
319 staff, or vice versa.
321 @lilypond[ragged-right,verbatim,quote]
323 \new Staff \relative c' {
326 \new Staff \relative c' {
330 \override Stem #'length = #12
331 \override Stem #'cross-staff = ##t
332 \override Stem #'flag-style = #'no-flag
342 @c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
343 @c {indicating-cross-staff-chords-with-arpeggio-bracket.ly}
362 @subsubsection Piano pedals
365 Pianos have pedals that alter the way sound is produced. Generally, a
366 piano has three pedals, sustain, una corda, and sostenuto.
369 Piano pedal instruction can be expressed by attaching
370 @code{\sustainDown}, @code{\sustainUp}, @code{\unaCorda},
371 @code{\treCorde}, @code{\sostenutoDown} and @code{\sostenutoUp} to a
374 @lilypond[quote,ragged-right,fragment,verbatim]
375 c'4\sustainDown c'4\sustainUp
378 What is printed can be modified by setting @code{pedal@var{X}Strings},
379 where @var{X} is one of the pedal types: @code{Sustain},
380 @code{Sostenuto} or @code{UnaCorda}. Refer to
381 @rinternals{SustainPedal} in the program reference for more
384 Pedals can also be indicated by a sequence of brackets, by setting the
385 @code{pedalSustainStyle} property to bracket objects
387 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
388 \set Staff.pedalSustainStyle = #'bracket
390 b\sustainUp\sustainDown
391 b g \sustainUp a \sustainDown \bar "|."
394 A third style of pedal notation is a mixture of text and brackets,
395 obtained by setting the @code{pedalSustainStyle} property to
398 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
399 \set Staff.pedalSustainStyle = #'mixed
401 b\sustainUp\sustainDown
402 b g \sustainUp a \sustainDown \bar "|."
405 The default @q{*Ped.} style for sustain and damper pedals corresponds to
406 style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
409 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
410 c\sostenutoDown d e c, f g a\sostenutoUp
413 For fine-tuning the appearance of a pedal bracket, the properties
414 @code{edge-width}, @code{edge-height}, and @code{shorten-pair} of
415 @code{PianoPedalBracket} objects (see
416 @rinternals{PianoPedalBracket} in the Internals Reference) can be
417 modified. For example, the bracket may be extended to the right edge
420 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
421 \override Staff.PianoPedalBracket #'shorten-pair = #'(0 . -1.0)
422 c\sostenutoDown d e c, f g a\sostenutoUp
426 Note that overrides must be placed before the note at which the
427 pedal bracket starts.
429 @c TODO Check relative positions of the sustain pedal and
430 @c dynamics are correct (they collided in 2.11.44).
431 @c Give example showing this.
435 Notation Reference: @ref{Ties} (laissez vibrer).
438 @subsection Accordion
444 @node Discant symbols
445 @subsubsection Discant symbols
447 @c TODO Add text from -user and lsr 194