version that you are working on. See TRANSLATION for details.
@end ignore
-@c \version "2.11.61"
+@c \version "2.12.0"
@node Keyboard and other multi-staff instruments
@section Keyboard and other multi-staff instruments
@subsection Common notation for keyboards
This section discusses notation issues that may arise for most
-many-stringed instruments.
+keyboard instruments.
@menu
* References for keyboards::
@end itemize
-@seealso
+@c @snippets
+@c @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@c {forcing-visibility-of-systems-with-multi-bar-rests-when-using-\RemoveEmptyStaffContext.ly}
+@c http://lsr.dsi.unimi.it/LSR/Item?u=1&id=312
+@seealso
Learning Manual:
@rlearning{Real music example},
@rlearning{Other uses for tweaks}.
Snippets:
@rlsr{Keyboards}.
+
@knownissues
@cindex keyboard music, centering dynamics
@var{staffname}. Typical values for @var{staffname} are
@code{"up"} and @code{"down"}, or @code{"RH"} and @code{"LH"}.
+The staff to which the voice is being switched must exist at the
+time of the switch. If necessary, staves should be @qq{kept alive},
+see @ref{Keeping contexts alive}.
+
Cross-staff notes are beamed automatically:
@lilypond[verbatim,quote]
example of beam tweaking, see @rlearning{Fixing overlapping
notation}.
-@seealso
+@seealso
Learning Manual:
@rlearning{Fixing overlapping notation}.
Notation Reference:
@ref{Stems},
-@ref{Automatic beams}.
+@ref{Automatic beams},
+@ref{Keeping contexts alive}.
Snippets:
@rlsr{Keyboards}.
If additional control is needed over the individual staves, they
can be created manually with the names @code{"up"} and
@code{"down"}. The @code{\autochange} command will then switch
-its voice between the existing staves. For example, this is
-necessary to place a key signature in the lower staff:
+its voice between the existing staves.
+
+@warning{If staves are created manually, they @emph{must} be named
+@code{"up"} and @code{"down"}.}
+
+For example, staves must be created manually in order to place a
+key signature in the lower staff:
@lilypond[quote,verbatim]
\new PianoStaff <<
>>
@end lilypond
-@seealso
+@seealso
Notation Reference:
@ref{Changing staff manually}.
Internals Reference:
@rinternals{AutoChangeMusic}.
+
@knownissues
@cindex chords, splitting across staves with \autochange
@seealso
-
Snippets:
@rlsr{Keyboards}.
@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
{indicating-cross-staff-chords-with-arpeggio-bracket.ly}
-@seealso
+@seealso
Snippets:
@rlsr{Keyboards}.
Internals Reference:
@rinternals{Stem}.
+
@node Piano
@subsection Piano
The placement of the pedal commands matches the physical movement of the
sustain pedal during piano performance. Pedalling to the final bar line
-is indicated by omitting the final pedal up command.
+is indicated by omitting the final pedal off command.
-@seealso
+@seealso
Notation Reference:
@ref{Ties}.
@rinternals{PianoPedalBracket},
@rinternals{Piano_pedal_engraver}.
+
@node Accordion
@subsection Accordion
@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
{accordion-discant-symbols.ly}
-@seealso
+@seealso
Snippets:
@rlsr{Keyboards}.
@node Harp
@subsection Harp
-TBC
+This section discusses notation issues that are unique to the harp.
-@ignore
-Some possibilities:
-- glissandi
-- tremolo (for bisbigliando)
-- natural harmonics
-- directional arpeggio and non-arpeggio
-- workaroung for keeping both staves visible in an orchestral
- score,
-http://lists.gnu.org/archive/html/lilypond-user/2007-08/msg00386.html
-and http://lsr.dsi.unimi.it/LSR/Item?u=1&id=312
-
-An LSR snippet could be used to demonstrate the main items; in the
-case of glissandi, it would be desirable to have a demonstration
-of different styles.
+@menu
+* References for harps::
+* Harp pedals::
+@end menu
-@end ignore
+@node References for harps
+@unnumberedsubsubsec References for harps
+@cindex harps
+@cindex bisbiglando
+
+Some common characteristics of harp music are covered elsewhere:
+
+@itemize
+
+@item The glissando is the most characterisic harp technique,
+@ref{Glissando}.
+
+@item A @notation{bisbigliando} is written as a tremelo @ref{Tremolo
+repeats}
+@item Natural harmonics are covered under @ref{Harmonics}.
+
+@item For directional arpeggios and non-arpeggios, see @ref{Arpeggio}.
+
+@end itemize
+
+@seealso
+Notation Reference:
+@ref{Tremolo repeats}
+@ref{Glissando}
+@ref{Arpeggio}
+@ref{Harmonics}
+
+@node Harp pedals
+@unnumberedsubsubsec Harp pedals
+
+@cindex harp pedals
+@cindex harp pedal diagrams
+@cindex pedals, harp
+@cindex pedal diagrams, harp
+
+Harps have seven strings per octave that may be sounded at the natural,
+flattened, or sharpened pitch. In lever harps, each string is adjusted
+individually, but in pedal harps every string with the same pitch name
+is controlled by a single pedal. From the player's left to right, the
+pedals are D, C, and B on the left and E, F, G, and A on the right.
+The position of the pedals may be indicated with text marks:
+
+@lilypond[quote,verbatim,relative=2]
+\textLengthOn
+cis1_\markup \concat \vcenter { [D \flat C \sharp B|E \sharp F \sharp G A \flat] }
+c!1_\markup \concat \vcenter {[ C \natural ]}
+@end lilypond
+
+or pedal diagrams:
+
+@lilypond[quote,verbatim,relative=2]
+\textLengthOn
+cis1_\markup { \harp-pedal #"^v-|vv-^" }
+c!1_\markup { \harp-pedal #"^o--|vv-^" }
+@end lilypond
+
+The @code{\harp-pedal} command accepts a string of characters, where
+@code{^} is the highest pedal position (flattened pitch), @code{-} is
+the middle pedal postion (natural pitch), @code{v} is the lowest pedal
+position (sharpened pitch), and @code{|} is the divider. A prefixed
+@code{o} will circle the following pedal symbol.
+
+@seealso
+Notation Reference:
+@ref{Text scripts}
+@ref{Instrument Specific Markup}
projects / lilypond.git / blobdiff