version that you are working on. See TRANSLATION for details.
@end ignore
-@c \version "2.11.38"
+@c \version "2.11.51"
@node Fretted string instruments
@section Fretted string instruments
@node References for fretted strings
@subsubsection References for fretted strings
-@c TODO Add refs
-TBC
+@itemize
+@item Fingerings are indicated with @ref{Fingering instructions}.
+
+@item Instructions for @notation{Laissez vibrer} ties
+as well as ties on arpeggios and tremolos is described in
+@ref{Ties}.
+
+@item Instructions on handling multiple voices is described
+in @ref{Collision resolution}.
+
+@end itemize
+
+@seealso
+
+Notation Reference:
+@ref{Instrument names},
+@ref{Writing music in parallel},
+@ref{Fingering instructions},
+@ref{Ties},
+@ref{Arpeggio},
+@ref{List of articulations},
+@ref{Clef}.
@node String number indications
@subsubsection String number indications
@cindex String numbers
-String numbers can be added to chords, by indicating the string number
-with @code{\}@var{number},
+The string on which a note should be played may be indicated by
+appending @code{\@var{number}} to a note inside a chord construct
+@code{<>}.
+
+@warning{String numbers @strong{must} be defined inside a chord
+construct even if there is only a single note.}
-@lilypond[relative,relative=1,ragged-right,fragment]
-<c\1 e\2 g\3>
+@lilypond[verbatim,quote,relative=1]
+<c\5>4 <e\4> <g\3>2
+<c,\5 e\4 g\3>1
@end lilypond
+When fingerings and string indications are used together, their
+placement is controlled by the order in which the two items appear
+in the code:
+
+@lilypond[verbatim,quote,relative=2]
+<g\3-0>2
+<g-0\3>
+@end lilypond
+
+@snippets
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{controlling-the-placement-of-chord-fingerings.ly}
+
+@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+{allowing-fingerings-to-be-printed-inside-the-staff.ly}
@seealso
-Internals Reference: @rinternals{StringNumber},
-@c @lsr{guitar/,string-number.ly}.
+Snippets:
+@rlsr{Fretted strings}.
+
+Notation Reference:
+@ref{Fingering instructions}.
+
+Internals Reference:
+@rinternals{StringNumber},
+@rinternals{Fingering}.
+
@node Default tablatures
Tablature notation is used for notating music for plucked string
instruments. Pitches are not denoted with note heads, but by
-numbers indicating on which string and fret a note must be played. LilyPond
-offers limited support for tablature.
+numbers indicating on which string and fret a note must be played.
+LilyPond offers limited support for tablature.
-The string number associated to a note is given as a backslash
-followed by a number, e.g., @code{c4\3} for a C quarter on the third
-string. By default, string 1 is the highest one, and the tuning
-defaults to the standard guitar tuning (with 6 strings). The notes
-are printed as tablature, by using @rinternals{TabStaff} and
-@rinternals{TabVoice} contexts
+The string number associated with a note is given as a backslash
+followed by a number. By default, string 1 is the highest,
+and the tuning defaults to the standard guitar tuning (with 6 strings).
+The notes are printed as tablature, by using @code{TabStaff} and
+@code{TabVoice} contexts
@lilypond[quote,ragged-right,fragment,verbatim]
\new TabStaff {
@funindex minimumFret
@cindex fret
-When no string is specified, the first string that does not give a
-fret number less than @code{minimumFret} is selected. The default
-value for @code{minimumFret} is 0
+When no string is specified for a note, the note is assigned to the lowest string
+that can generate the note with a fret number greater than or equal to
+@code{minimumFret} is selected. The default value for @code{minimumFret} is 0.
-@example
-e16 fis gis a b4
-\set TabStaff.minimumFret = #8
-e16 fis gis a b4
-@end example
-@lilypond[quote,ragged-right]
-frag = {
- \key e \major
- e16 fis gis a b4
- \set TabStaff.minimumFret = #8
- e16 fis gis a b4
-}
- \new StaffGroup <<
- \new Staff { \clef "G_8" \frag }
- \new TabStaff { \frag }
- >>
-@end lilypond
+@lilypond[quote,ragged-right,verbatim]
+\new StaffGroup <<
+ \new Staff \relative c' {
+ c16 d e f g4
+ c,16 d e f g4
+ }
+ \new TabStaff \relative c {
+ c16 d e f g4
+ \set TabStaff.minimumFret = #5
+ c,16 d e f g4
+ }
+>>
+@end lilypond
@snippets
-To print tablatures with stems down and horizontal beams,
-initialize the @code{TabStaff} with this code:
+The direction of stems is controlled the same way in tablature as
+in traditional notation. Beams can be made horizontal:
-@example
-\stemDown
-\override Beam #'damping = #100000
-@end example
+@lilypond[quote,ragged-right,verbatim]
+\new TabStaff {
+ \relative c {
+ g16 b d g
+ b d g b
+ \stemDown
+ \override Beam #'damping = #100000
+ g,,16 b d g
+ b d g b
+ }
+}
+@end lilypond
@seealso
-Internals Reference: @rinternals{TabNoteHead}, @rinternals{TabStaff}, @rinternals{TabVoice}.
+Snippets:
+@rlsr{Fretted strings}.
+
+Notation Reference:
+@ref{Stems}
+
+Internals Reference:
+@rinternals{TabNoteHead},
+
+@rinternals{TabStaff},
+
+@rinternals{TabVoice},
+
+@rinternals{Beam}.
@knownissues
Chords are not handled in a special way, and hence the automatic
-string selector may easily select the same string to two notes in a
+string selector may easily select the same string for two notes in a
chord.
In order to handle @code{\partcombine}, a @code{TabStaff} must use
@seealso
+Snippets:
+@rlsr{Fretted strings}.
+
The file @file{scm/@/output@/-lib@/.scm} contains the predefined string
tunings.
Internals Reference: @rinternals{Tab_note_heads_engraver}.
@cindex fret diagrams
@cindex chord diagrams
-Fret diagrams can be added to music as a markup to the desired note. The
-markup contains information about the desired fret diagram, as shown in the
-following example
+Fret diagrams can be added to music as a markup to the desired note.
+The markup contains information about the desired fret diagram.
+There are three different fret-diagram markup interfaces: standard, terse,
+and verbose. The three interfaces produce equivalent markups, but have
+varying amounts of information in the markup string. Details about the
+markup interfaces are found at @ref{Text markup commands}.
+
+The following example shows the three fret-diagram markup interfaces,
+along with examples of common tweaks. For example, the size of the verbose
+fret diagram is reduced to 0.75, and the finger indications are specified
+to appear below the diagram. The terse diagram includes tweaks to
+specify placement of finger code and color of dots.
@lilypond[verbatim, ragged-right, quote]
\new Voice {
fis'^\markup \override #'(size . 0.75) {
\override #'(finger-code . below-string) {
\fret-diagram-verbose #'((place-fret 6 2 1) (barre 6 1 2)
- (place-fret 5 4 3) (place-fret 4 4 4)
- (place-fret 3 3 2) (place-fret 2 2 1)
+ (place-fret 5 4 3)
+ (place-fret 4 4 4)
+ (place-fret 3 3 2)
+ (place-fret 2 2 1)
(place-fret 1 2 1))
}
}
}
@end lilypond
-
-There are three different fret-diagram markup interfaces: standard, terse,
-and verbose. The three interfaces produce equivalent markups, but have
-varying amounts of information in the markup string. Details about the
-markup interfaces are found at @ref{Text markup commands}.
-
You can set a number of graphical properties according to your preference.
Details about the property interface to fret diagrams are found at
@rinternals{fret-diagram-interface}.
@seealso
-
+Snippets:
+@rlsr{Fretted strings}.
@node Right hand fingerings
@subsubsection Right hand fingerings
-Right hand fingerings in chords can be entered using
-@code{@var{note}-\rightHandFinger @var{finger}}
+Right-hand fingerings @var{p-i-m-a} can be entered using
+@code{<@var{note}-\rightHandFinger @var{finger} >}.
+The right-hand fingering indication must occur within a @code{<>} chord
+construct for it to be printed in the score, even if it is a single note.
+There must be a hyphen after the note and a space before the closing @code{>}.
-@lilypond[verbatim,fragment,relative=2]
- <c-\rightHandFinger #1 e-\rightHandFinger #2 >
+
+@lilypond[quote,ragged-right,fragment,verbatim]
+\relative c' {
+ <c-\rightHandFinger #1 >4
+ <e-\rightHandFinger #2 >
+ <g-\rightHandFinger #3 >
+ <c-\rightHandFinger #4 >
+ <c,-\rightHandFinger #1 e-\rightHandFinger #2 g-\rightHandFinger #3 c-\rightHandFinger #4 >1
+}
@end lilypond
-for brevity, you can abbreviate @code{\rightHandFinger} to something
+For convenience, you can abbreviate @code{\rightHandFinger} to something
short, for example @code{RH},
@example
@snippets
-You may exercise greater control over right handing fingerings by
-setting @code{strokeFingerOrientations},
+You may exercise greater control over the placement of right-hand
+fingerings by setting @code{strokeFingerOrientations},
@lilypond[quote,verbatim,ragged-right,fragment,relative=1]
#(define RH rightHandFinger)
\override StrokeFinger #'digit-names = ##("x" "y" "z" "!" "@")
<c-\RH #5 >4
<c-\RH "@">4
+ <c-\RH #2 >4
+ <c-\RH "z">4
+}
+@end lilypond
+
+This example combines left-hand fingering, string indication, and
+right-hand fingering
+
+@lilypond[quote,ragged-right,fragment,verbatim]
+#(define RH rightHandFinger)
+\relative c' {
+ <c-3\5-\RH #1 >4
+ <e-2\4-\RH #2 >
+ <g-0\3-\RH #3 >
+ <c-1\2-\RH #4 >
}
@end lilypond
@seealso
-Internals Reference: @rinternals{StrokeFinger}
+Snippets:
+@rlsr{Fretted strings}.
+
+Internals Reference:
+@rinternals{StrokeFinger}.
@node Guitar
pitch. It is notated with cross note heads; this is
demonstrated in @ref{Special note heads}.
+@seealso
+
+Snippets:
+@rlsr{Fretted strings}.
@node Banjo
@subsection Banjo
@seealso
+Snippets:
+@rlsr{Fretted strings}.
+
The file @file{scm/@/output@/-lib@/.scm} contains predefined banjo tunings.
projects / lilypond.git / blobdiff