-@c -*- coding: latin-1; mode: texinfo; -*-
+@c -*- coding: utf-8; mode: texinfo; -*-
@c This file is part of lilypond.tely
@c A menu is needed before every deeper *section nesting of @node's; run
* Chord names::
* Vocal music::
* Rhythmic music::
-* Tablatures::
+* Guitar::
+* Bagpipe::
* Ancient notation::
* Other instrument specific notation::
@end menu
Piano staves are two normal staves coupled with a brace. The staves
are largely independent, but sometimes voices can cross between the
two staves. The same notation is also used for harps and other key
-@c Is this `harp' or `harpsichord'?
-@c both. -gp
instruments. The @internalsref{PianoStaff} is especially built to
handle this cross-staffing behavior. In this section we discuss the
@internalsref{PianoStaff} and some other pianistic peculiarities.
-
@menu
* Automatic staff changes::
* Manual staff switches::
+* Laissez vibrer ties::
* Pedals::
* Staff switch lines::
* Cross staff stems::
@code{\autochange} cannot be inside @code{\times}.
-Internally, the @code{\partcombine} interprets both arguments as
-@code{Voice}s named @code{one} and @code{two}, and then decides when
-the parts can be combined. Consequently, if the arguments switch to
-differently named @internalsref{Voice} contexts, the events in those
-will be ignored.
-
@node Manual staff switches
@subsection Manual staff switches
@end example
+@node Laissez vibrer ties
+@subsection Laissez vibrer ties
+@cindex Laissez vibrer
+@cindex Ties, laissez vibrer
+
+L.v. ties (laissez vibrer) indicate that notes must not be damped at the
+end. It is used in notation for piano, harp and other string and
+percussion instruments. They can be entered using @code{\laissezVibrer},
+
+@lilypond[fragment,raggedright,verbatim,relative=1]
+<c f g>\laissezVibrer
+@end lilypond
+
+@seealso
+
+Program reference:
+@internalsref{LaissezVibrerTie}
+@internalsref{LaissezVibrerTieColumn}
+
+Example files:
+@inputfileref{input/regression,laissez-vibrer-tie.ly}
+
@node Pedals
@subsection Pedals
@cindex Pedals
c\sostenutoDown d e c, f g a\sostenutoUp
@end lilypond
+@seealso
+
+In this manual: @ref{Laissez vibrer ties}
+
@node Staff switch lines
@subsection Staff switch lines
@code{followVoice} to true
@lilypond[quote,raggedright,fragment,relative=1,verbatim]
-\context PianoStaff <<
- \set followVoice = ##t
- \context Staff \context Voice {
+\new PianoStaff <<
+ \context Staff=one {
+ \set followVoice = ##t
c1
\change Staff=two
b2 a
}
- \context Staff=two { \clef bass \skip 1*2 }
+ \context Staff=two { \clef bass \skip 1*2 }
>>
@end lilypond
@end lilypond
+
@node Chord names
@section Chord names
@menu
-* Printing chord names::
+* Introducing chord names::
* Chords mode::
* Printing chord names::
@end menu
@c awkward name; awkward section name.
@c still, the Basic "chords" seems like a good name... :(
-@node Printing chord names
-@subsection Printing chord names
-@cindex Chord names
+@node Introducing chord names
+@subsection Introducing chord names
+@cindex chord names
LilyPond has support for printing chord names. Chords may be entered
in musical chord notation, i.e., @code{< .. >}, but they can also be
be intelligent. The last chord (@code{f bes d}) is not interpreted as
an inversion.
+Note that the duration of chords must be specified outside the
+@code{<>}.
+
+@example
+<c e g>2
+@end example
+
@node Chords mode
@subsection Chords mode
to a specialized function to change this behavior. For example, the
base can be printed in lower case.
+@cindex @code{chordPrefixSpacer}
+@item chordPrefixSpacer
+The ``m'' for minor chords is usually printed right after the root of
+the chord. By setting @code{chordPrefixSpacer}, you can fix a spacer
+between the root and ``m''. The spacer is not used when the root
+is altered.
+
@end table
The predefined variables @code{\germanChords},
-@code{\semiGermanChords} set these variables. The effect is
+@code{\semiGermanChords}, @code{\italianChords} and @code{\frenchChords}
+set these variables. The effect is
demonstrated here,
-@lilypondfile[raggedright]{chord-names-german.ly}
+@lilypondfile[raggedright]{chord-names-languages.ly}
There are also two other chord name schemes implemented: an alternate
Jazz chord notation, and a systematic scheme called Banter chords. The
@code{\germanChords},
@cindex @code{\semiGermanChords}
@code{\semiGermanChords}.
+@cindex @code{\italianChords}
+@code{\italianChords}.
+@cindex @code{\frenchChords}
+@code{\frenchChords}.
@code{< .. >} syntax.
+
@node Vocal music
@section Vocal music
@node Entering lyrics
@subsection Entering lyrics
-
@cindex lyrics
@cindex @code{\lyricmode}
@cindex punctuation
Lyrics are entered in a special input mode. This mode is introduced
-by the keyword @code{\lyricmode}, or by using @code{addlyrics} or
-@code{lyricsto}. In this mode you can enter lyrics,
+by the keyword @code{\lyricmode}, or by using @code{\addlyrics} or
+@code{\lyricsto}. In this mode you can enter lyrics,
with punctuation and accents, and the input @code{d} is not parsed as
a pitch, but rather as a one letter syllable. Syllables are entered
like notes, but with pitches replaced by text. For example,
\lyricmode @{ Twin-4 kle4 twin- kle litt- le star2 @}
@end example
+There is a difference between @code{\addlyrics} and
+@code{\lyricmode}. @code{\addlyrics} and @code{\lyricsto}
+ignore all durations and aligns syllables to notes; @code{\lyricmode}
+uses the durations specified.
A word lyrics mode begins with an alphabetic character, and ends with
any space or digit. The following characters can be any character
Any @code{_} character that appears in an unquoted word is converted
to a space. This provides a mechanism for introducing spaces into words
-without using quotes. Quoted words can also be used in Lyrics mode to
-specify words that cannot be written with the above rules. The
-following example incorporates double quotes
+without using quotes.
-@example
-\lyricmode @{ He said: "\"Let" my peo ple "go\"" @}
-@end example
+To enter lyrics with characters from non-English languages, or with
+non-ascii characters (such as the heart symbol or slanted quotes),
+simply insert the characters directly into the input file and save
+it with utf-8 encoding. See @ref{Text encoding} for more info.
-This example is slightly academic, since it gives better looking
-results using single quotes, @code{``} and @code{''}
@example
-\lyricmode @{ He said: ``Let my peo ple go'' @}
+\lyricmode @{ He said: “Let my peo ple go”. @}
@end example
-
The full definition of a word start in Lyrics mode is somewhat more
complex.
@seealso
-Program reference: events @internalsref{LyricEvent}, and
-@internalsref{LyricText}.
+Program reference: @internalsref{LyricText}.
@refbugs
@cindex hyphens
-Centered hyphens are entered as `@code{-}@code{-}' between syllables.
+Centered hyphens are entered as `@code{--}' between syllables.
The hyphen will have variable length depending on the space between
the syllables and it will be centered between the syllables.
When a lyric is sung over many notes (this is called a melisma), this is
indicated with a horizontal line centered between a syllable and the
next one. Such a line is called an extender line, and it is entered as
-@code{__}.
-
-@ignore
-FIXME: check that this compiles and displays correctly. I don't want
-to commit this part blindly.
+`@code{__}'.
In tighly engraved music, hyphens can be removed. In some languages
(e.g. German and Hungarian), hyphens should not disappear, since
forced to remain by overriding @code{minimum-length} of
the @code{LyricHyphen} grob.
-(code from 2.2)
+@lilypond[quote,verbatim,raggedright]
\score {
-<< \notes \new Staff \relative c'' { \time 1/4 c16[ c c c]
-\time 1/4
-c16[ c c c]
-\time 1/4
-c16[ c c c]
-
-}
- \lyrics \new Lyrics \with {
- % Otherwise lyrics are so far apart that hyphens don't disappear
- \override SeparationItem #'padding = #0.0
- }{ bla -- bla -- bla -- bla --
- bla -- bla -- bla -- bla --
-
- \override LyricHyphen #'minimum-length = #0.7
- \override LyricHyphen #'spacing-procedure =
- #Hyphen_spanner::set_spacing_rods
-
- bla -- bla -- bla -- bla
- }>>
- \paper {
- indent = 0.0 \cm
- linewidth = 3.4 \cm
-
- \context {
- \StaffContext \remove "Time_signature_engraver"
- }
-
+ <<
+ \new Staff \relative c'' {
+ \time 1/4 c16 c c c c16 c c c c16 c c c
+ }
+ \lyricmode { \new Lyrics
+ \with {
+ \override SeparationItem #'padding = #0.0
+ % Otherwise lyrics are so far apart that hyphens don't disappear
+ }
+ {
+ An -- ti -- cons -- ti --
+ tu -- tion -- nel -- le --
+ \override LyricHyphen #'minimum-length = #0.7
+ \override LyricHyphen #'spacing-procedure =
+ #Hyphen_spanner::set_spacing_rods
+ men -- taire -- ment. ouf~!
}
-
+ }
+ >>
+ \layout {
+ indent = 0.0 \cm
+ linewidth = 3.4 \cm
+ \context {
+ \Staff \remove "Time_signature_engraver"
+ }
+ }
}
-@end ignore
-
+@end lilypond
@seealso
-Program reference: @internalsref{HyphenEvent},
-@internalsref{ExtenderEvent}, @internalsref{LyricHyphen}, and
-@internalsref{LyricExtender}
+Program reference: @internalsref{LyricHyphen}, @internalsref{LyricExtender}.
@node Flexibility in alignment
@subsection Flexibility in alignment
-
Often, different stanzas of one song are put to one melody in slightly
differing ways. Such variations can still be captured with
@code{\lyricsto}.
+@subsubsection Lyrics to multiple notes of a melisma
+
+
One possibility is that the text has a melisma in one stanza, but
multiple syllables in another one. One solution is to make the faster
voice ignore the melisma. This is done by setting
}
@end lilypond
+
+@subsection Switching the melody associated with a lyrics line
+
+
+
More complex variations in text underlay are possible. It is possible
to switch the melody for a line of lyrics during the text. This is
done by setting the @code{associatedVoice} property. In the example
+@subsection Specifying melismata within the lyrics
+
+It is also possible to define melismata entirely in the lyrics. This
+can be done by entering @code{_} for every note that is part of the
+melisma.
+
+@lilypond[relative=1,verbatim,fragment]
+{ \set melismaBusyProperties = #'()
+ c d( e) f f( e) e e }
+\addlyrics
+ { Ky -- _ _ ri __ _ _ _ e }
+@end lilypond
+
+In this case, you can also have ties and slurs in the melody, if you
+set @code{melismaBusyProperties}, as is done in the example above.
+
+@lilypond[relative=1,verbatim,fragment]
+{
+ \set melismaBusyProperties = #'()
+ c d( e) f f( e) e e
+}
+\addlyrics
+ { Ky -- _ _ ri __ _ _ _ e }
+@end lilypond
+
+@subsubsection Spacing lyrics
+
+@cindex Spacing lyrics
+@cindex Lyrics, increasing space between
+
+To increase the space between lyrics, use the @code{SeparationItem}
+property.
+
+@lilypond[relative,verbatim,fragment,quote,raggedright]
+{
+ c c c c
+ \override Score.SeparationItem #'padding = #5
+ c c c c
+}
+\addlyrics {
+ longtext longtext longtext longtext
+ longtext longtext longtext longtext
+}
+@end lilypond
+
+
@node More stanzas
@subsection More stanzas
}
@end lilypond
+You can display alternate (or divisi) lyrics by naming voice
+contexts and attaching lyrics to those specific contexts.
+
+@lilypond[verbatim,raggedright,quote]
+\score{ <<
+ \context Voice = "melody" {
+ \relative c' {
+ c4
+ <<
+ { \voiceOne c8 e }
+ \context Voice = splitpart { \voiceTwo c4 }
+ >>
+ \oneVoice c4 c | c
+ }
+ }
+ \new Lyrics \lyricsto "melody" { we shall not o- ver- come }
+ \new Lyrics \lyricsto "splitpart" { will }
+>> }
+@end lilypond
+
+
+You can use this trick to display different lyrics for a repeated
+section.
+
+@lilypond[verbatim,raggedright,quote]
+\score{ <<
+ \context Voice = melody \relative c' {
+ c2 e | g e | c1 |
+ \context Voice = verse \repeat volta 2 {c4 d e f | g1 | }
+ a2 b | c1}
+ \lyricsto melody \context Lyrics = mainlyrics \lyricmode {
+ do mi sol mi do
+ la si do }
+ \lyricsto verse \context Lyrics = mainlyrics \lyricmode {
+ do re mi fa sol }
+ \lyricsto verse \context Lyrics = repeatlyrics \lyricmode {
+ dodo rere mimi fafa solsol }
+>>
+}
+@end lilypond
+
+
@seealso
-Program reference: Layout objects @internalsref{LyricText} and
-@internalsref{VocalName}. Music expressions
-@internalsref{LyricEvent}.
+Program reference: @internalsref{LyricText}, @internalsref{StanzaNumber}, @internalsref{VocalName}.
There is no collision handling in the case of multiple per-voice
ambitus.
+
@node Other vocal issues
-@subsection Other vocal issue
+@subsection Other vocal issues
@ignore
yeah, I'm giving up somewhat by stuffing a bunch of things in
examples, and that might get them more involved in the docs. -gp
@end ignore
-You can display alternate (or divisi) lyrics by naming voice
-contexts and attaching lyrics to those specific contexts.
-
-@lilypond[verbatim,raggedright,quote]
-\score{ <<
- \context Voice = "melody" {
- \relative c' {
- c4
- <<
- { \voiceOne c8 e }
- \context Voice = splitpart { \voiceTwo c4 }
- >>
- \oneVoice c4 c | c
- }
- }
- \new Lyrics \lyricsto "melody" { we shall not o- ver- come }
- \new Lyrics \lyricsto "splitpart" { shall }
->> }
-@end lilypond
-
-
-You can use this trick to display different lyrics for a repeated
-section.
-
-@lilypond[verbatim,raggedright,quote]
-\score{ <<
- \context Voice = melody \relative c' {
- c2 e | g e | c1 |
- \context Voice = verse \repeat volta 2 {c4 d e f | g1 | }
- a2 b | c1}
- \lyricsto melody \context Lyrics = mainlyrics \lyricmode {
- do mi sol mi do
- la si do }
- \lyricsto verse \context Lyrics = mainlyrics \lyricmode {
- do re mi fa sol }
- \lyricsto verse \context Lyrics = repeatlyrics \lyricmode {
- dodo rere mimi fafa solsol }
->>
-}
-@end lilypond
-
-
-To notate ``parlato'' (spoken without pitch but still with
-rhythm) sections,
-
-@lilypond[raggedright,verbatim,quote,fragment,relative=2]
-c4 d
-\override NoteHead #'style = #'cross
-e f
-\revert NoteHead #'style
-e d
-@end lilypond
+``Parlato'' is spoken without pitch but still with rhythm; it is
+notated by cross noteheads. This is demonstrated in
+@ref{Special noteheads}.
@node Rhythmic music
@seealso
-Program reference: @internalsref{DrumNoteEvent}.
+Program reference: @internalsref{note-event}.
@node Percussion staves
@subsection Percussion staves
The above example shows verbose polyphonic notation. The short
polyphonic notation, described in @ref{Polyphony}, can also be used if
-the @internalsref{DrumVoices} are instantiated by hand first. For example,
+the @internalsref{DrumVoice}s are instantiated by hand first. For example,
@lilypond[quote,raggedright,fragment,verbatim]
\new DrumStaff <<
-
-@node Tablatures
-@section Tablatures
+@node Guitar
+@section Guitar
@cindex tablature
@cindex guitar tablature
-Tablature notation is used for notating music for plucked string
-instruments. Pitches are not denoted with note heads, but by
-indicating on which string and fret a note must be played. LilyPond
-offers limited support for tablature.
-
@menu
+* String number indications::
* Tablatures basic::
* Non-guitar tablatures::
* Fret diagrams::
+* Other guitar issues::
@end menu
+@node String number indications
+@subsection String number indications
+
+@cindex String numbers
+
+String numbers can be added to chords, by indicating the string number
+with @code{\}@var{number},
+
+@lilypond[relative,relative=1,raggedright,fragment]
+<c\1 e\2 g\3>
+@end lilypond
+
+See also @inputfileref{input/regression,string-number.ly}.
+
+
+@seealso
+
+Program reference: @internalsref{StringNumber}.
+
+
@node Tablatures basic
@subsection Tablatures basic
@cindex Tablatures basic
+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.
+
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
@seealso
-Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}, and
-@internalsref{StringNumberEvent}.
+Program reference: @internalsref{TabStaff}, @internalsref{TabVoice}.
@refbugs
@lilypond[verbatim, raggedright, quote]
\context Voice {
- d' ^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
+ d'^\markup \fret-diagram #"6-x;5-x;4-o;3-2;2-3;1-2;"
d' d' d'
- fis' ^\markup \override #'(size . 0.75) {
+ 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)
}
}
fis' fis' fis'
- c' ^\markup \override #'(dot-radius . 0.35) {
+ c'^\markup \override #'(dot-radius . 0.35) {
\override #'(finger-code . in-dot) {
\override #'(dot-color . white) {
\fret-diagram-terse #"x;3-1-(;5-2;5-3;5-4;3-1-);"
Examples: @inputfileref{input/@/test,fret@/-diagram@/.ly}
+@node Other guitar issues
+@subsection Other guitar issues
+
+This example demonstrates how to include guitar position and
+barring indications.
+
+@lilypond[quote,raggedright,fragment,verbatim,relative=0]
+\clef "G_8"
+b16 d16 g16 b16 e16
+\textSpannerDown
+\override TextSpanner #'edge-text = #'("XII " . "")
+ g16\startTextSpan
+ b16 e16 g16 e16 b16 g16\stopTextSpan
+e16 b16 g16 d16
+@end lilypond
+
+
+Stopped (X) note heads are used in guitar music to signal a place where the
+guitarist must play a certain note or chord, with its fingers just
+touching the strings instead of fully pressing them. This gives the sound a
+percussive noise-like sound that still maintains part of the original
+pitch. It is notated with cross noteheads; this is
+demonstrated in @ref{Special noteheads}.
+
+
+@node Bagpipe
+@section Bagpipe
+
+@cindex Bagpipe
+
+@menu
+* Bagpipe definitions::
+* Bagpipe example::
+@end menu
+
+
+@node Bagpipe definitions
+@subsection Bagpipe definitions
+
+LilyPond contains special definitions for music for the Scottish
+highland bagpipe; to use them, add
+
+@example
+\include "bagpipe.ly"
+@end example
+
+@noindent
+at the top of your input file. This lets you add the special gracenotes
+common to bagpipe music with short commands. For example, you could
+write @code{\taor} instead of
+
+@example
+\grace @{ \small G32[ d G e] @}
+@end example
+
+@code{bagpipe.ly} also contains pitch definitions for the bagpipe
+notes in the appropiate octaves, so you do not need to worry about
+@code{\relative} or @code{\transpose}.
+
+@lilypond[raggedright,verbatim,quote,notime]
+\include "bagpipe.ly"
+{ \grg G4 \grg a \grg b \grg c \grg d \grg e \grg f \grA g A }
+@end lilypond
+
+Bagpipe music nominally uses the key of D Major (even though that
+isn't really true). However, since that is the only key that can be used,
+the key signature is normally not written out. To set this up correctly,
+always start your music with @code{\hideKeySignature}. If you for some
+reason want to show the key signature, you can use @code{\showKeySignature}
+instead.
+
+Some modern music use cross fingering on c and f to flatten those notes.
+This can be indicated by @code{cflat} or @code{fflat}. Similarly, the
+piobaireachd high g can be written @code{gflat} when it occurs in light
+music.
+
+
+@node Bagpipe example
+@subsection Bagpipe example
+
+This is what the well known tune Amazing Grace looks like in bagpipe
+notation.
+
+@lilypond[verbatim,quote]
+\include "bagpipe.ly"
+\layout {
+ indent = 0.0\cm
+ \context { \Score \remove "Bar_number_engraver" }
+}
+
+\header {
+ title = "Amazing Grace"
+ meter = "Hymn"
+ arranger = "Trad. arr."
+}
+
+{
+ \hideKeySignature
+ \time 3/4
+ \grg \partial 4 a8. d16
+ \slurd d2 \grg f8[ e32 d16.]
+ \grg f2 \grg f8 e
+ \thrwd d2 \grg b4
+ \grG a2 \grg a8. d16
+ \slurd d2 \grg f8[ e32 d16.]
+ \grg f2 \grg e8. f16
+ \dblA A2 \grg A4
+ \grg A2 f8. A16
+ \grg A2 \hdblf f8[ e32 d16.]
+ \grg f2 \grg f8 e
+ \thrwd d2 \grg b4
+ \grG a2 \grg a8. d16
+ \slurd d2 \grg f8[ e32 d16.]
+ \grg f2 e4
+ \thrwd d2.
+ \slurd d2
+ \bar "|."
+}
+@end lilypond
+
@node Ancient notation
@section Ancient notation
* Ligatures::
* Gregorian Chant contexts::
* Mensural contexts::
+* Musica ficta accidentals::
* Figured bass::
@end menu
+
@node Ancient note heads
@subsection Ancient note heads
For ancient notation, a note head style other than the @code{default}
style may be chosen. This is accomplished by setting the @code{style}
property of the @internalsref{NoteHead} object to @code{baroque},
-@code{neomensural} or @code{mensural}. The @code{baroque} style
-differs from the @code{default} style only in using a square shape
-for @code{\breve} note heads. The @code{neomensural} style differs from
-the @code{baroque} style in that it uses rhomboidal heads for whole notes
-and all smaller durations. Stems are centered on the note heads.
-This style is particularly useful when transcribing mensural music,
-e.g., for the incipit. The @code{mensural} style finally produces note
-heads that mimic the look of note heads in historic printings of the
-16th century.
+@code{neomensural}, @code{mensural} or @code{petrucci}. The
+@code{baroque} style differs from the @code{default} style only in
+using a square shape for @code{\breve} note heads. The
+@code{neomensural} style differs from the @code{baroque} style in that
+it uses rhomboidal heads for whole notes and all smaller durations.
+Stems are centered on the note heads. This style is particularly
+useful when transcribing mensural music, e.g., for the incipit. The
+@code{mensural} style produces note heads that mimic the look of note
+heads in historic printings of the 16th century. Finally, the
+@code{petrucci} style also mimicks historic printings, but uses bigger
+note heads.
The following example demonstrates the @code{neomensural} style
@seealso
In this manual: @ref{Pitches}, @ref{Cautionary accidentals} and
-@ref{Accidentals} give a general introduction of the use of
+@ref{Automatic accidentals} give a general introduction of the use of
accidentals. @ref{Key signature} gives a general introduction of
the use of key signatures.
@node Ancient rests
@subsection Ancient rests
-@cindex rests
+@cindex rests, ancient
Use the @code{style} property of grob @internalsref{Rest} to select
@code{petrucci-c5}
@tab
@lilypond[fragment,relative=1,notime]
- \clef "petrucci-c2" c
+ \clef "petrucci-c2"
+ \override NoteHead #'style = #'mensural
+ c
@end lilypond
@item
@code{petrucci-f}
@tab
@lilypond[fragment,relative=1,notime]
- \clef "petrucci-f" c
+ \clef "petrucci-f"
+ \override NoteHead #'style = #'mensural
+ c
@end lilypond
@item
@code{petrucci-g}
@tab
@lilypond[fragment,relative=1,notime]
- \clef "petrucci-g" c
+ \clef "petrucci-g"
+ \override NoteHead #'style = #'mensural
+ c
@end lilypond
@item
@code{mensural-c3}, @code{mensural-c4}
@tab
@lilypond[fragment,relative=1,notime]
- \clef "mensural-c2" c
+ \clef "mensural-c2"
+ \override NoteHead #'style = #'mensural
+ c
@end lilypond
@item
@code{mensural-f}
@tab
@lilypond[fragment,relative=1,notime]
- \clef "mensural-f" c
+ \clef "mensural-f"
+ \override NoteHead #'style = #'mensural
+ c
@end lilypond
@item
@code{mensural-g}
@tab
@lilypond[fragment,relative=1,notime]
- \clef "mensural-g" c
+ \clef "mensural-g"
+ \override NoteHead #'style = #'mensural
+ c
@end lilypond
@item
@tab
@lilypond[fragment,relative=1,notime]
\override Staff.StaffSymbol #'line-count = #4
- \clef "vaticana-do2" c
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
+ \override Voice.Stem #'transparent = ##t
+ \override NoteHead #'style = #'vaticana.punctum
+ \clef "vaticana-do2"
+ c
@end lilypond
@item
@tab
@lilypond[fragment,relative=1,notime]
\override Staff.StaffSymbol #'line-count = #4
- \clef "vaticana-fa2" c
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
+ \override Voice.Stem #'transparent = ##t
+ \override NoteHead #'style = #'vaticana.punctum
+ \clef "vaticana-fa2"
+ c
@end lilypond
@item
@tab
@lilypond[fragment,relative=1,notime]
\override Staff.StaffSymbol #'line-count = #4
- \clef "medicaea-do2" c
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
+ \override Voice.Stem #'transparent = ##t
+ \override NoteHead #'style = #'medicaea.punctum
+ \clef "medicaea-do2"
+ c
@end lilypond
@item
@tab
@lilypond[fragment,relative=1,notime]
\override Staff.StaffSymbol #'line-count = #4
- \clef "medicaea-fa2" c
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
+ \override Voice.Stem #'transparent = ##t
+ \override NoteHead #'style = #'medicaea.punctum
+ \clef "medicaea-fa2"
+ c
@end lilypond
@item
@tab
@lilypond[fragment,relative=1,notime]
\override Staff.StaffSymbol #'line-count = #4
- \clef "hufnagel-do2" c
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
+ \override Voice.Stem #'transparent = ##t
+ \override NoteHead #'style = #'hufnagel.punctum
+ \clef "hufnagel-do2"
+ c
@end lilypond
@item
@tab
@lilypond[fragment,relative=1,notime]
\override Staff.StaffSymbol #'line-count = #4
- \clef "hufnagel-fa2" c
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
+ \override Voice.Stem #'transparent = ##t
+ \override NoteHead #'style = #'hufnagel.punctum
+ \clef "hufnagel-fa2"
+ c
@end lilypond
@item
@code{hufnagel-do-fa}
@tab
@lilypond[fragment,relative=1,notime]
- \clef "hufnagel-do-fa" c
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
+ \override Voice.Stem #'transparent = ##t
+ \override NoteHead #'style = #'hufnagel.punctum
+ \clef "hufnagel-do-fa"
+ c
@end lilypond
@end multitable
@lilypond[quote,raggedright]
\layout {
indent = 0.0
- \context { \Staff
+ \context {
+ \Staff
\remove Staff_symbol_engraver
\remove Clef_engraver
\remove Time_signature_engraver
}
-} {
+}
+{
\set Score.timing = ##f
\set Score.barAlways = ##t
- s_\markup { "\\time 4/4" }
- ^\markup { " " \musicglyph #"timesig.neomensural44" }
+ s_\markup { "\\time 4/4" }^\markup { " " \musicglyph #"timesig.neomensural44" }
s
- s_\markup { "\\time 2/2" }
- ^\markup { " " \musicglyph #"timesig.neomensural22" }
+ s_\markup { "\\time 2/2" }^\markup { " " \musicglyph #"timesig.neomensural22" }
s
- s_\markup { "\\time 6/4" }
- ^\markup { " " \musicglyph #"timesig.neomensural64" }
+ s_\markup { "\\time 6/4" }^\markup { " " \musicglyph #"timesig.neomensural64" }
s
- s_\markup { "\\time 6/8" }
- ^\markup { " " \musicglyph #"timesig.neomensural68" }
+ s_\markup { "\\time 6/8" }^\markup { " " \musicglyph #"timesig.neomensural68" }
\break
- s_\markup { "\\time 3/2" }
- ^\markup { " " \musicglyph #"timesig.neomensural32" }
+ s_\markup { "\\time 3/2" }^\markup { " " \musicglyph #"timesig.neomensural32" }
s
- s_\markup { "\\time 3/4" }
- ^\markup { " " \musicglyph #"timesig.neomensural34" }
+ s_\markup { "\\time 3/4" }^\markup { " " \musicglyph #"timesig.neomensural34" }
s
- s_\markup { "\\time 9/4" }
- ^\markup { " " \musicglyph #"timesig.neomensural94" }
+ s_\markup { "\\time 9/4" }^\markup { " " \musicglyph #"timesig.neomensural94" }
s
- s_\markup { "\\time 9/8" }
- ^\markup { " " \musicglyph #"timesig.neomensural98" }
+ s_\markup { "\\time 9/8" }^\markup { " " \musicglyph #"timesig.neomensural98" }
\break
- s_\markup { "\\time 4/8" }
- ^\markup { " " \musicglyph #"timesig.neomensural48" }
+ s_\markup { "\\time 4/8" }^\markup { " " \musicglyph #"timesig.neomensural48" }
s
- s_\markup { "\\time 2/4" }
- ^\markup { " " \musicglyph #"timesig.neomensural24" }
+ s_\markup { "\\time 2/4" }^\markup { " " \musicglyph #"timesig.neomensural24" }
}
@end lilypond
@lilypond[raggedright,fragment,relative=1,quote]
{
\fatText
+
\time 2/2
c1^\markup { \hspace #-2.0 \typewriter default }
\include "gregorian-init.ly"
\score {
\context VaticanaVoice {
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
\override TextScript #'font-family = #'typewriter
\override TextScript #'font-shape = #'upright
\override Script #'padding = #-0.1
\new Lyrics \lyricmode {
\markup { \column {
\typewriter "vaticana"
- \line { " " \musicglyph #"custodes.vaticana-u0" }
+ \line { " " \musicglyph #"custodes.vaticana.u0" }
} }
\markup { \column {
\typewriter "medicaea"
- \line { " " \musicglyph #"custodes.medicaea-u0" }
+ \line { " " \musicglyph #"custodes.medicaea.u0" }
}}
\markup { \column {
\typewriter "hufnagel"
- \line { " " \musicglyph #"custodes.hufnagel-u0" }
+ \line { " " \musicglyph #"custodes.hufnagel.u0" }
}}
\markup { \column {
\typewriter "mensural"
- \line { " " \musicglyph #"custodes.mensural-u0" }
+ \line { " " \musicglyph #"custodes.mensural.u0" }
}}
}
@end lilypond
In this manual: @ref{Breath marks}.
-Program reference: @internalsref{BreathingSign}, @internalsref{BreathingSignEvent}.
+Program reference: @internalsref{BreathingSign}.
Examples: @inputfileref{input/@/test,divisiones@/.ly}.
Augmentum dots within ligatures are not handled correctly.
+The syntax still uses the deprecated infix style @code{\[ music expr
+\]}. For consistency reasons, it will eventually be changed to
+postfix style @code{note\[ ... note\]}. Alternatively, the file
+@file{gregorian@/-init@/.ly} can be included; it provides a scheme
+function
+@example
+\ligature @var{music expr}
+@end example
+with the same effect and is believed to be stable.
@menu
* White mensural ligatures::
\override NoteHead #'style = #'neomensural
\override Staff.TimeSignature #'style = #'neomensural
\clef "petrucci-g"
-\[ g\longa c\breve a\breve f\breve d'\longa \]
+\[ c'\maxima g \]
s4
-\[ e1 f1 a\breve g\longa \]
+\[ d\longa c\breve f e d \]
+s4
+\[ c'\maxima d'\longa \]
+s4
+\[ e'1 a g\breve \]
@end example
@lilypond[quote,raggedright]
\score {
\override NoteHead #'style = #'neomensural
\override Staff.TimeSignature #'style = #'neomensural
\clef "petrucci-g"
- \[ g\longa c\breve a\breve f\breve d'\longa \]
+ \[ c'\maxima g \]
+ s4
+ \[ d\longa c\breve f e d \]
+ s4
+ \[ c'\maxima d'\longa \]
s4
- \[ e1 f1 a\breve g\longa \]
+ \[ e'1 a g\breve \]
}
\layout {
\context {
\override NoteHead #'style = #'neomensural
\override Staff.TimeSignature #'style = #'neomensural
\clef "petrucci-g"
- \[ g\longa c\breve a\breve f\breve d'\longa \]
+ \[ c'\maxima g \]
s4
- \[ e1 f1 a\breve g\longa \]
+ \[ d\longa c\breve f e d \]
+ s4
+ \[ c'\maxima d'\longa \]
+ s4
+ \[ e'1 a g\breve \]
}
@end lilypond
@refbugs
-The implementation is experimental. It may output strange warnings,
-incorrect results, and might even crash on more complex ligatures.
+The invisible rests (@code{s4}) in the example are used to compensate
+for the poor horizontal spacing.
@node Gregorian square neumes ligatures
@subsubsection Gregorian square neumes ligatures
proper values, so you can immediately go ahead entering the chant, as
the following excerpt demonstrates
-@lilypond[quote,raggedright,verbatim]
+@lilypond[quote,raggedright,packed,verbatim]
\include "gregorian-init.ly"
\score {
<<
\context VaticanaVoice = "cantus" {
+ \override Staff.StaffSymbol #'color = #red
+ \override Staff.LedgerLineSpanner #'color = #red
\override Score.BarNumber #'transparent = ##t {
\[ c'\melisma c' \flexa a \]
\[ a \flexa \deminutum g\melismaEnd \]
}
@end lilypond
+@node Musica ficta accidentals
+@subsection Musica ficta accidentals
+
+In European music from before about 1600, singers were often expected
+to chromatically alter notes at their own initiative. This is called
+``Musica Ficta''. In modern transcriptions, these accidentals are
+usually printed over the note.
+
+@cindex Musica ficta
+
+Support for such suggested accidentals is included, and can be
+switched on by setting @code{suggestAccidentals} to true.
+
+@cindex @code{suggestAccidentals}
+
+@lilypond[verbatim,fragment,relative=1]
+fis gis
+\set suggestAccidentals = ##t
+ais bis
+@end lilypond
+
+@seealso
+
+Program reference: @internalsref{Accidental_engraver} engraver and the
+@internalsref{AccidentalSuggestion} object.
@node Figured bass
@subsection Figured bass
@c TODO: musicological blurb about FB
-LilyPond has limited support for figured bass
+LilyPond has support for figured bass
@lilypond[quote,raggedright,verbatim,fragment]
<<
@end lilypond
Spaces or dashes may be inserted by using @code{_}. Brackets are
-introduced with @code{[} and @code{]}
+introduced with @code{[} and @code{]}. You can also include text
+strings and text markups, see @ref{Overview of text markup commands}.
@example
-< [4 6] 8 [_! 12] >
+< [4 6] 8 [_! 12] > < 5 \markup @{ + \number 6 @} >
@end example
@lilypond[quote,raggedright,fragment]
\context FiguredBass
-\figuremode { < [4 6] 8 [_! 12] > }
+\figuremode { < [4 6] 8 [_! 12] > < 5 \markup{ + \number 6 } > }
+@end lilypond
+
+It is also possible to use continuation lines for repeated figures,
+
+@lilypond[verbatim,relative=1]
+<<
+ \new Staff { c4 c }
+ \figures {
+ \set useBassFigureExtenders = ##t
+ <4 6> <3 6> <3 7>
+ }
+>>
@end lilypond
Although the support for figured bass may superficially resemble chord
-support, it works much simpler. The @code{\figuremode} mode simply
-stores the numbers and @internalsref{FiguredBass} context prints
-them as entered. There is no conversion to pitches and no
-realizations of the bass are played in the MIDI file.
+support, it is much simpler. The @code{\figuremode} mode simply
+stores the numbers and @internalsref{FiguredBass} context prints them
+as entered. There is no conversion to pitches and no realizations of
+the bass are played in the MIDI file.
Internally, the code produces markup texts. You can use any of the
markup text properties to override formatting. For example, the
@seealso
-Program reference: @internalsref{BassFigureEvent} music,
-@internalsref{BassFigure} object, and @internalsref{FiguredBass} context.
+Program reference: @internalsref{NewBassFigure},
+@internalsref{BassFigureAlignment}, @internalsref{BassFigureLine},
+@internalsref{BassFigureBracket}, and
+@internalsref{BassFigureContinuation} objects and
+@internalsref{FiguredBass} context.
@refbugs
@menu
* Artificial harmonics (strings)::
-* Stopped notes (guitar)::
@end menu
@node Artificial harmonics (strings)
<c g'\harmonic>4
@end lilypond
-
-@node Stopped notes (guitar)
-@subsection Stopped notes (guitar)
-
-Stopped (X) note heads are used in guitar music to signal a place where the
-guitarist must play a certain note or chord, with its fingers just
-touching the strings instead of fully pressing them. This gives the sound a
-percussive noise-like sound that still maintains part of the original pitch.
-
-Finger stopped technique is extremely important for rhythm and rock-heavy
-metal guitarists; the former often uses barré based stopped chords to
-intermix harmony with rythm, the latters use finger stopping to mute power
-chords, or charge them with more expression in close-tied power chord stums.
-
-It is also used (even if rarely) in classic guitar music, generally in the
-melodic line, to provide some rithmic pattern right in the melody.
-
-@lilypond[raggedright,verbatim,quote,fragment,relative=2]
-c4 d
-\override NoteHead #'style = #'cross
-e f
-\revert NoteHead #'style
-e d
-@end lilypond
-
-
projects / lilypond.git / blobdiff