@node Writing pitches
@subsection Writing pitches
-Into text.
+Intro text.
@menu
-* Normal pitches::
+* Absolute octave entry::
+* Relative octave entry::
* Accidentals::
-* Cautionary accidentals::
-* Micro tones::
* Note names in other languages::
@end menu
-@node Normal pitches
-@unnumberedsubsubsec Normal pitches
+@node Absolute octave entry
+@unnumberedsubsubsec Absolute octave entry
@cindex Pitch names
@cindex pitches
c d e f g a b c'
@end lilypond
-The note name @code{c} is engraved one octave below middle C.
+There are two different ways to enter these note names with regard
+to octave placement: absolute and relative. The relative mode
+will in most cases be the most convenient, but the absolute mode
+is more fundamental and will be presented first.
+
+@cindex Absolute
+@cindex Absolute octave specification
+
+In absolute mode, every note is placed explicitly in a certain
+octave. The note names @code{c} to @code{b} are engraved in the
+octave below middle C, as in the previous example.
@lilypond[quote,fragment,verbatim,ragged-right]
\clef treble
@funindex '
@funindex ,
-The optional octave specification takes the form of a series of
-single quote (@samp{'}) characters or a series of comma (@samp{,})
-characters. Each @samp{'} raises the pitch by one octave; each
-@samp{,} lowers the pitch by an octave.
+If a note should be in another octave than this, an octave
+specification must be given. It takes the form of a series of
+single quote (@samp{'}) or comma (@samp{,}) characters. Each
+@samp{'} raises the pitch by one octave; each @samp{,} lowers the
+pitch by an octave.
@lilypond[quote,ragged-right,fragment,verbatim]
\clef treble
c, c,, e, g d,, d, d c
@end lilypond
-An alternate method may be used to declare which octave to engrave
-a pitch; this method does not require as many octave
-specifications (@code{'} and @code{,}). See @ref{Relative
-octaves}.
+
+@node Relative octave entry
+@unnumberedsubsubsec Relative octaves entry
+
+@cindex Relative
+@cindex Relative octave specification
+@funindex \relative
+
+The absolute mode requires a lot of octave specifications, which
+not only becomes tedious but also easily leads to errors.
+Therefore, it is usually more convenient to let notes be entered
+relative to the previous note. This is done with the relative
+mode.
+
+@example
+\relative @var{startpitch} @var{musicexpr}
+@end example
+
+In relative mode, each note is assumed to be as close to the
+previous note as possible. This means that the octave of notes
+that appear in @var{musicexpr} are calculated as follows:
+
+@itemize
+@item
+The pitch of the first note is relative to @code{\relative
+@var{startpitch} }.
+
+@item
+If no octave changing marks are used, the basic interval between a
+note and the one that precedes it is always taken to be a fourth
+or less.
+
+@item
+This distance is determined without regarding alterations or the
+actual sounding pitches; a @code{fisis} following a @code{ceses}
+will be put above the @code{ceses}. In other words, a
+doubly-augmented fourth is considered a smaller interval than a
+diminished fifth, even though the doubly-augmented fourth spans
+seven semitones while the diminished fifth only spans six
+semitones.
+
+@item
+The octave changing marks @code{'} and @code{,} can be added to
+raise or lower the pitch by an extra octave from the basic
+interval.
+
+@item
+Multiple octave changing marks can be used. @code{''} will raise
+the pitch by two octaves.
+
+@end itemize
+
+Here is the relative mode shown in action:
+
+@lilypond[quote,fragment,ragged-right,verbatim]
+\relative c'' {
+ b c d c b c bes a
+}
+@end lilypond
+
+Octave changing marks are used for intervals greater than a
+fourth:
+
+@lilypond[quote,ragged-right,fragment,verbatim]
+\relative c'' {
+ c g c f, c' a, e''
+}
+@end lilypond
+
+A note sequence without a single octave mark can nevertheless span
+large intervals:
+
+@lilypond[quote,ragged-right,fragment,verbatim]
+\relative c {
+ c f b e a d g
+}
+@end lilypond
+
+If the preceding item is a chord, the first note of the chord is
+used as the reference point for the octave placement of a
+following note or chord:
+
+@lilypond[quote,ragged-right,fragment,verbatim]
+\relative c' {
+ c <c e g>
+ <c' e g>
+ <c, e' g> c
+}
+@end lilypond
+
+The @var{startpitch} (after @code{\relative}) is a note name in
+absolute mode. In principle it can be any note name, but common
+practice is to use @code{c} in various octave positions.
+
+When octaves are specified as above by adding @code{'} and
+@code{,} to pitch names, it is easy to accidentally put a pitch in
+the wrong octave. The relative octave mode prevents these errors
+since most of the time it is not necessary to indicate any octaves
+at all. Furthermore, in absolute mode, a single mistake may be
+difficult to spot; in relative mode, a single error puts the rest
+of the piece off by one octave.
+
+@seealso
+
+Snippets: @lsrdir{pitch}
+
+
+@refbugs
+
+The relative conversion will not affect @code{\transpose},
+@code{\chordmode} or @code{\relative} sections in its argument.
+To use relative within transposed music, an additional
+@code{\relative} must be placed inside @code{\transpose}.
+
+@c DEPRECATED
+If no @var{startpitch} is specified for @code{\relative}, then
+@code{c'} is assumed. However, this is a deprecated option and
+may disappear in future versions, so its use is discouraged.
+
+
@node Accidentals
@c and Key Signature pages.
A @rglos{sharp} pitch is made by adding @samp{is} to the name, and
-a @rglos{flat} pitch by adding @samp{es}. As you might expect, a
-@rglos{double sharp} or @rglos{double flat} is made by adding
-@samp{isis} or @samp{eses}@footnote{This syntax derived from note
-naming conventions in Nordic and Germanic languages, like German
-and Dutch. To use other names for accidentals, see @ruser{Note
-names in other languages}.}
+a @rglos{flat} pitch by adding @samp{es}. As you might expect,
+a @rglos{double sharp} or @rglos{double flat} is made by adding
+@samp{isis} or @samp{eses}. This syntax derived from note naming
+conventions in Nordic and Germanic languages, like German and
+Dutch. To use other names for accidentals, see @ref{Note names
+in other languages}.
@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
a2 ais a aes
@noindent
These are the Dutch note names. In Dutch, @code{aes} is
contracted to @code{as}, but both forms are accepted. Similarly,
-both @code{es} and @code{ees} are accepted
+both @code{es} and @code{ees} are accepted:
@lilypond[fragment,quote,ragged-right,verbatim,relative=2]
a2 as e es
A natural will cancel the effect of an accidental or key
signature. However, naturals are not encoded into the note name
syntax with a suffix; a natural pitch is shown as a simple note
-name
+name:
@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
a4 aes a2
@end lilypond
-@commonprop
-
-In accordance with standard typesetting rules, a natural sign is
-printed before a sharp or flat if a previous accidental needs to
-be cancelled. To change this behavior, use @code{\set
-Staff.extraNatural = ##f}
-
-@lilypond[fragment,quote,ragged-right,verbatim,relative=2]
-ceses4 ces cis c
-\set Staff.extraNatural = ##f
-ceses4 ces cis c
-@end lilypond
-
-
-@seealso
-
-Program reference: @internalsref{LedgerLineSpanner},
-@internalsref{NoteHead}.
-
-
-@node Cautionary accidentals
-@unnumberedsubsubsec Cautionary accidentals
@cindex accidental, reminder
@cindex accidental, cautionary
@end lilypond
-@seealso
-
-The automatic production of accidentals can be tuned in many ways.
-For more information, see @ref{Automatic accidentals}.
-
-
-@node Micro tones
-@unnumberedsubsubsec Micro tones
-
@cindex quarter tones
@cindex semi-flats, semi-sharps
Micro tones are also exported to the MIDI file.
+@commonprop
+
+In accordance with standard typesetting rules, a natural sign is
+printed before a sharp or flat if a previous accidental needs to
+be cancelled. To change this behavior, use @code{\set
+Staff.extraNatural = ##f}
+
+@lilypond[fragment,quote,ragged-right,verbatim,relative=2]
+ceses4 ces cis c
+\set Staff.extraNatural = ##f
+ceses4 ces cis c
+@end lilypond
+
+
+@seealso
+
+The automatic production of accidentals can be tuned in many ways
+concerning for how long an accidental is considered to last. For
+more information, see @ref{Automatic accidentals}.
+
+For @emph{musica ficta}, editorial accidentals placed above the
+staff commonly used in editions of early music, see @ref{Musica
+ficta accidentals}.
+
+Program reference: @internalsref{LedgerLineSpanner},
+@internalsref{NoteHead}.
+
+
@refbugs
There are no generally accepted standards for denoting
standard.
+
@node Note names in other languages
@unnumberedsubsubsec Note names in other languages
languages. To use them, include the language specific init file.
For example, add @code{\include "english.ly"} to the top of the
input file. The available language files and the note names they
-define are
+define are:
@cindex note names, other languages
-@c put the rest of the old table into this new format.
+
@example
@multitable @columnfractions .2 .6 .05 .05 .05 .05
@headitem Language
@item netherlands.ly
@tab c d e f g a bes b
@tab -is @tab -es @tab -isis @tab -eses
-@c new stuff here:
-
-
+@item english.ly
+ @tab c d e f g a bf b
+ @tab -s/-sharp @tab -f/-flat @tab -ss/-x/-sharpsharp
+ @tab -ff/-flatflat
+@item deutsch.ly
+ @tab c d e f g a b h
+ @tab -is @tab -es @tab -isis @tab -eses
+@item norsk.ly
+ @tab c d e f g a b h
+ @tab -iss/-is @tab -ess/-es @tab -ississ/-isis
+ @tab -essess/-eses
+@item svenska.ly
+ @tab c d e f g a b h
+ @tab -iss @tab -ess @tab -ississ @tab -essess
+@item italiano.ly
+ @tab do re mi fa sol la sib si
+ @tab -d @tab -b @tab -dd @tab -bb
+@item catalan.ly
+ @tab do re mi fa sol la sib si
+ @tab -d/-s @tab -b @tab -dd/-ss @tab -bb
+@item espanol.ly
+ @tab do re mi fa sol la sib si
+ @tab -s @tab -b @tab -ss @tab -bb
@end multitable
@end example
-@c old table
-@ignore
-@example
- Note Names sharp flat double double
- sharp flat
-
-nederlands.ly c d e f g a bes b -is -es -isis -eses
-english.ly c d e f g a bf b -s/-sharp -f/-flat -ss/-x/ -ff/
- -sharpsharp -flatflat
-deutsch.ly c d e f g a b h -is -es -isis -eses
-norsk.ly c d e f g a b h -iss/-is -ess/-es -ississ/-isis -essess/-eses
-svenska.ly c d e f g a b h -iss -ess -ississ -essess
-italiano.ly do re mi fa sol la sib si -d -b -dd -bb
-catalan.ly do re mi fa sol la sib si -d/-s -b -dd/-ss -bb
-espanol.ly do re mi fa sol la sib si -s -b -ss -bb
-@end example
-@end ignore
-
@noindent
Note that in Dutch, German, Norwegian, and Swedish, the flat
alterations of @samp{a} like for example @code{aes} and
@code{aeses} are usually contracted to @code{as} and @code{ases}
-(or more commonly @code{asas}). Sometimes only these contracted
+(or more commonly @code{asas}). Sometimes only these contracted
names are defined in the corresponding language files (this also
applies to the suffixes for quartertones below).
@noindent
Some music uses microtones whose alterations are fractions of a
-@q{regular} sharp or flat. The note names for quartertones defined
-in the various language files are listed in the following table.
-Here the prefixes @q{semi-} and @q{sesqui-} mean @q{half} and
-@q{one and a half}, respectively. For Norwegian, Swedish, Catalan
-and Spanish no special names have been defined yet.
+@q{regular} sharp or flat. The note names for quartertones
+defined in the various language files are listed in the following
+table. Here the prefixes @q{semi-} and @q{sesqui-} mean @q{half}
+and @q{one and a half}, respectively. For Norwegian, Swedish,
+Catalan and Spanish no special names have been defined yet.
+
@c What about Turkish Maquam music and similar microtonal systems?
@c
@c Note that the term "three-quarter-sharp/-flat" used in lilypond's source code
@c is actually misleading since the alteration is in fact one and a half
-@c of a regular sharp/flat. Whence the naming "sesqui-sharp/-flat" used below.
+@c of a regular sharp/flat. Whence the naming "sesqui-sharp/-flat" used below.
@example
- Note Names semi- semi- sesqui- sesqui-
- sharp flat sharp flat
-
-nederlands.ly c d e f g a bes b -ih -eh -isih -eseh
-english.ly c d e f g a bf b -qs -qf -tqs -tqf
-deutsch.ly c d e f g a b h -ih -eh -isih -eseh
-norsk.ly c d e f g a b h
-svenska.ly c d e f g a b h
-italiano.ly do re mi fa sol la sib si -sd -sb -dsd -bsb
-catalan.ly do re mi fa sol la sib si
-espanol.ly do re mi fa sol la sib si
+@multitable @columnfractions .2 .6 .05 .05 .05 .05
+@headitem Language
+ @tab Note names
+ @tab semi- @tab semi- @tab sesqui- @tab sesqui-
+
+@item nederlands.ly
+ @tab c d e f g a bes b
+ @tab -ih @tab -eh @tab -isih @tab -eseh
+@item english.ly
+ @tab c d e f g a bf b
+ @tab -qs @tab -qf @tab -tqs @tab -tqf
+@item deutsch.ly
+ @tab c d e f g a b h
+ @tab -ih @tab -eh @tab -isih @tab -eseh
+@c @item norsk.ly
+@c @tab c d e f g a b h
+@c @item svenska.ly
+@c @tab c d e f g a b h
+@item italiano.ly
+ @tab do re mi fa sol la sib si
+ @tab -sd @tab -sb @tab -dsd @tab -bsb
+@c @item catalan.ly
+@c @tab do re mi fa sol la sib si
+@c @item espanol.ly
+@c @tab do re mi fa sol la sib si
+@end multitable
@end example
-
@node Changing multiple pitches
@subsection Changing multiple pitches
@menu
-* Relative octaves::
* Octave check::
* Transpose::
@end menu
-@node Relative octaves
-@unnumberedsubsubsec Relative octaves
-
-@cindex Relative
-@cindex Relative octave specification
-@funindex \relative
-
-Octaves are specified by adding @code{'} and @code{,} to pitch
-names. When you copy existing music, it is easy to accidentally
-put a pitch in the wrong octave and hard to find such an error.
-The relative octave mode prevents these errors by making the
-mistakes much larger: a single error puts the rest of the piece
-off by one octave
-
-@example
-\relative @var{startpitch} @var{musicexpr}
-@end example
-
-@noindent
-or
-
-@example
-\relative @var{musicexpr}
-@end example
-
-@noindent
-@code{c'} is used as the default if no starting pitch is defined.
-
-The octave of notes that appear in @var{musicexpr} are calculated
-as follows:
-
-@itemize
-@item
-If no octave changing marks are used, the basic interval between
-this and the last note is always taken to be a fourth or less.
-
-@item
-This distance is determined without regarding alterations; a
-@code{fisis} following a @code{ceses} will be put above the
-@code{ceses}. In other words, a doubly-augmented fourth is
-considered a smaller interval than a diminished fifth, even though
-the doubly-augmented fourth spans seven semitones while the
-diminished fifth only spans six semitones.
-
-@item
-The octave changing marks @code{'} and @code{,} can be added to
-raise or lower the pitch by an extra octave from the basic
-interval.
-
-@item
-Multiple octave changing marks can be used. @code{''} will raise
-the pitch by two octaves.
-
-@item
-The pitch of the first note is relative to @code{\relative
-@var{startpitch} }.
-
-@item
-If you do not specify @var{startpitch} then middle C is used.
-
-@end itemize
-
-Here is the relative mode shown in action
-
-@lilypond[quote,fragment,ragged-right,verbatim]
-\relative c'' {
- b c d c b c bes a
-}
-@end lilypond
-
-Octave changing marks are used for intervals greater than a fourth
-
-@lilypond[quote,ragged-right,fragment,verbatim]
-\relative c'' {
- c g c f, c' a, e''
-}
-@end lilypond
-
-If the preceding item is a chord, the first note of the chord is
-used to determine the first note of the next chord
-
-@lilypond[quote,ragged-right,fragment,verbatim]
-\relative c' {
- c <c e g>
- <c' e g>
- <c, e' g>
-}
-@end lilypond
-
-The pitch after @code{\relative} contains a note name.
-
-The relative conversion will not affect @code{\transpose},
-@code{\chordmode} or @code{\relative} sections in its argument.
-To use relative within transposed music, an additional
-@code{\relative} must be placed inside @code{\transpose}.
-
-
@node Octave check
@unnumberedsubsubsec Octave check
This means that @var{musicexpr} is transposed by the interval
between the pitches @var{from} and @var{to}: any note with pitch
-@code{from} is changed to @code{to}.
+@code{from} is changed to @code{to} and any other note is
+transposed by the same interval.
Consider a piece written in the key of D-major. If this piece is
a little too low for its performer, it can be transposed up to
Consider a part written for violin (a C instrument). If this part
is to be played on the A clarinet (for which an A is notated as a
C, and which sounds a minor third lower than notated), the
-following transposition will produce the appropriate part
+following transposition will produce the appropriate part:
@example
\transpose a c @dots{}
@end example
-@code{\transpose} distinguishes between enharmonic pitches: both
-@code{\transpose c cis} or @code{\transpose c des} will transpose
-up half a tone. The first version will print sharps and the
-second version will print flats
+@code{\transpose} will also transpose key signatures:
@lilypond[quote,ragged-right,verbatim]
mus = { \key d \major cis d fis g }
}
@end lilypond
+@code{\transpose} distinguishes between enharmonic pitches: both
+@code{\transpose c cis} or @code{\transpose c des} will transpose
+up half a tone. The first version will print sharps and the notes
+will remain on the same scale step, the second version will print
+flats on the scale step above.
+
+@lilypond[quote,ragged-right,verbatim]
+mus = { c d e f }
+\new Staff {
+ \transpose c cis { \relative c' \mus }
+ \transpose c des { \relative c' \mus }
+}
+@end lilypond
+
+
+
@code{\transpose} may also be used to input written notes for a
transposing instrument. Pitches are normally entered into
LilyPond in C (or @q{concert pitch}), but they may be entered in
@seealso
-Manual: @ref{Grace notes}.
-
Program reference: @internalsref{Clef}.
+This manual: @ref{Ancient clefs}.
+
@node Key signature
@unnumberedsubsubsec Key signature
at the start of the staff.
Setting or changing the key signature is done with the @code{\key}
-command
+command:
@example
@code{\key} @var{pitch} @var{type}
This command sets the context property @code{Staff.keySignature}.
Non-standard key signatures can be specified by setting this
-property directly.
-
-Accidentals and key signatures often confuse new users, because
-unaltered notes get natural signs depending on the key signature.
-For more information, see @ref{Accidentals}, or
-@rlearning{Accidentals and key signatures}.
+property directly. See @internalsref{Key_engraver}, and for an
+example TODO.
+@c TODO: LSR snippet 248. leave this here for now -gp
+
+@warning{The relationship between accidentals and key signatures can
+be confusing to new users who think of the note letters as scale
+steps and not as absolute pitches. The note names that are
+entered in a music expression are the raw material; key signatures
+and clefs decide how this raw material is displayed. Thus,
+unaltered notes may get natural signs depending on the key
+signature. For more information, see @ref{Accidentals} and
+@rlearning{Accidentals and key signatures}.}
@lilypond[quote,ragged-right,verbatim,relative=2,fragment]
\key g \major
@cindex ottava
@cindex 15ma
+@cindex 8va
+@cindex 8ve
@cindex octavation
@lilypond[quote,ragged-right,verbatim,fragment]
2@tie{}(for 15ma), and -2 (for 15ma bassa) as arguments.
Internally the function sets the properties @code{ottavation}
(e.g., to @code{"8va"} or @code{"8vb"}) and
-@code{centralCPosition}. For overriding the text of the bracket,
-set @code{ottavation} after invoking @code{set-octavation}, i.e.,
+@code{centralCPosition}. To override the text of the bracket, set
+@code{ottavation} after invoking @code{set-octavation}, i.e.,
@lilypond[quote,ragged-right,verbatim]
{
...
@end example
+TODO: also mention that it affects cue voices. Or make a link.
+Or something.
+
+
projects / lilypond.git / blobdiff