@unnumberedsubsubsec Durations
@cindex duration
+@cindex beams, automatic
@funindex \longa
@funindex \breve
@funindex \maxima
@funindex .
-To obtain dotted note lengths, simply add a dot (@samp{.}) to the
+To obtain dotted note lengths, simply add a dot (@code{.}) to the
number. Double-dotted notes are produced in a similar way.
@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
@funindex \dotsNeutral
@code{\dotsNeutral}.
-@c TODO: after deciding the link question, fix these. -gp
-Durations are entered in the same way in @code{drummode},
-@code{chordmode}, @code{figuremode}, and (optionally)
-in @code{lyricmode}.
+For ways of specifying durations for the syllables of lyrics and
+ways of aligning lyrics to notes see @ref{Vocal music}.
-@seealso
+A note with the duration of a quadruple breve may be entered with
+@code{\maxima}, but this is supported only within ancient music
+notation; see @ref{Ancient notation}.
-For ways of specifying durations for the syllables of lyrics
-and ways of aligning lyrics to notes see @ref{Vocal music}.
+Optionally, notes can be spaced proportionately to their duration.
+For details of this and other settings which control proportional
+notation see @ref{Proportional notation}.
-For a description of how to enter rests see @ref{Writing rests}.
-A note with the duration of a quadruple breve may be
-entered with \maxima, but this is supported only within
-ancient music notation; see @ref{Ancient notation}.
+@seealso
-Optionally, notes can be spaced proportionately to their duration.
-For details of this and other settings which control
-proportional notation see @ref{Proportional notation}.
+Music Glossary: @rglos{breve}, @rglos{longa}.
+
+Notation Reference:@ref{Automatic beams}, @ref{Ties}, @ref{Writing rests}, @ref{Vocal music},
+@ref{Ancient notation}, @ref{Proportional notation}.
Snippets: @lsrdir{rhythms}
-Internals Reference: @internalsref{Dots}, and
+Internals Reference: @internalsref{Dots},
@internalsref{DotColumn}.
@refbugs
@c duplicated in Durations and Rests. -gp
-There is no fundamental limit to note durations (both in terms of
+There is no fundamental limit to rest durations (both in terms of
longest and shortest), but the number of glyphs is limited: there
-are flags up to 64th and rests up to 128th. At the other extreme,
-there are note heads up to longa (4x whole note) and rests up to
-maxima (8 x whole). Since beams can be stacked without needing
-extra glyphs, beamed notes can be arbitrarily short.
-
+are rests from 128th to maxima (8 x whole).
@node Tuplets
@cindex triplets
@funindex \times
-@c TODO Add Tuplet to glossary
-
Tuplets are made out of a music expression by multiplying all
durations with a fraction:
g4 \times 2/3 {c4 c c} d4 d4
@end lilypond
-Tuplets may be nested, for example,
+Tuplets may be nested; for example,
@lilypond[fragment,ragged-right,verbatim,relative=2]
\times 2/3 {
@commonprop
@funindex tupletNumberFormatFunction
+@funindex tupletSpannerDuration
@cindex tuplet formatting
The property @code{tupletSpannerDuration} specifies how long each
For more information about @code{make-moment}, see
@ref{Time administration}.
+@funindex TupletNumber
+
The format of the number is determined by the property @code{text}
in @code{TupletNumber}. The default prints only the denominator,
but if the property is set with @code{\override
}
@end lilypond
+@cindex bracket, tuplet
+@funindex TupletBracket
+
@c TODO: after LM 6 Tweaks includes \tweak info, look at this.-gp
@c It *should* be explained why \tweak must be used here, and why
@c \override doesn't work. I've made an attempt, but I'm not sure
@lilypond[ragged-right,verbatim,quote]
\new RhythmicStaff {
\set tupletFullLength = ##t
- \time 4/4
- \times 4/5 {
- c4 c1
- }
\set tupletFullLengthNote = ##t
\time 2/4
- \times 2/3 {
- c4 c c
- }
+ \times 2/3 { c4 c c }
+ \set tupletFullLengthNote = ##f
+ \time 4/4
+ \times 4/5 { c4 c1 }
\time 3/4
c4
}
@end lilypond
+@funindex \compressMusic
+@funindex \times
+
+@code{\compressMusic} works similarly to \times, but does not
+create a tuplet bracket; see @ref{Polymetric notation}.
+
+
@refbugs
Tuplets which cross bar lines will prevent a line break at that
@seealso
-@code{\compressMusic} works similarly to \times, but does not
-create a tuplet bracket; see @ref{Polymetric notation}.
+Music Glossary: @rglos{tuplet}.
-FIXME: totally irrelevant link to real-music for
-discussion/demonstration purposes.
+Notation Reference: @ref{Time administration},
+@ref{Objects connected to the input}, @ref{Polymetric notation}.
-Snippets: @lsrdir{rhythms},
-@lsr{real-music,creating-music-with-scheme.ly}.
+Snippets: @lsrdir{rhythms}.
Internals Reference: @internalsref{TupletBracket},
@internalsref{TupletNumber}, and @internalsref{TimeScaledMusic}.
@seealso
-This manual: @ref{Tuplets}, @ref{Skips}, @ref{Polymetric notation}.
+Notation Reference: @ref{Tuplets}, @ref{Skips}, @ref{Polymetric notation}.
Snippets: @lsrdir{rhythms}
\alternative {{ <c e>2. r4 } {<c e>2\repeatTie d4 c }}
@end lilypond
-@cindex Laissez vibrer
-@cindex Ties, laissez vibrer
+@cindex laissez vibrer
+@cindex ties, laissez vibrer
+@funindex \laissezVibrer
+@funindex \tieUp
+@funindex \tieDown
+@funindex \tieNeutral
@notation{L.v.} ties (@notation{laissez vibrer}) indicate that
notes must not be damped at the end. It is used in notation for
@seealso
+Music Glossary: @rglos{tie},
+@c [TODO]add @rglos{laissez vibrer}. when there is a glossary entry.
+
Snippets: @lsrdir{rhythms}
Internals Reference:
-In this manual: @ref{Automatic note splitting}.
+Notation Reference: @ref{Automatic note splitting}.
Snippets: @lsrdir{rhythms}
@node Rests
@unnumberedsubsubsec Rests
-@cindex Rests
+@cindex rest
+@cindex maxima
+@cindex longa
+@cindex breve
@funindex \rest
@funindex r
@funindex \maxima
+@funindex \longa
+@funindex \breve
Rests are entered like notes with the note name @code{r}:
@seealso
-Snippets: @lsrdir{rhythms}
+Notation Reference: @ref{Multi measure rests}.
+
+Snippets: @lsrdir{rhythms}.
Internals Reference: @internalsref{Rest}.
@refbugs
@c duplicated in Durations and Rests. -gp
-There is no fundamental limit to note durations (both in terms of
+There is no fundamental limit to rest durations (both in terms of
longest and shortest), but the number of glyphs is limited: there
-are flags up 64th and rests up to 128th. At the other extreme,
-there are note heads up to longa (4x whole note) and rests up to
-maxima (8 x whole). Since beams can be stacked without needing
-extra glyphs, beamed notes can be arbitrarily short.
-
+are rests from 128th to maxima (8 x whole).
@node Skips
@unnumberedsubsubsec Skips
-@cindex Skip
-@cindex Invisible rest
-@cindex Space note
+@cindex skip
+@cindex invisible rest
+@cindex space note
@funindex \skip
@funindex s
a4 a4 s4 a4 \skip 1 a4
@end lilypond
+@cindex lyrics, skip
+
The @code{s} syntax is only available in note mode and chord mode.
In other situations, for example, when entering lyrics, one must
use the @code{\skip} command:
@cindex multi measure rests
@cindex full measure rests
-@cindex Rests, multi measure
-@cindex Rests, full measure
-@cindex whole rests for a full measure
+@cindex rest, multi measure
+@cindex rest, full measure
+@cindex whole rest for a full measure
@funindex R
Rests for one or more full measures are entered using @code{R}
followed by a duration (see @ref{Durations}). The duration should
correspond to an integral number of measures, otherwise a barcheck
-warning is printed. Multi-measure rests are principally used to
-indicate that a part in a multi-part score should be silent:
+warning is printed. A @rglos{multi-measure rest} is used
+principally to indicate that a part in a multi-part score should
+be silent:
@lilypond[quote,fragment,verbatim,relative=2]
\set Score.skipBars = ##t
or breve rest, centered in the measure, regardless of the time
signature.
+@cindex church rest
+@cindex rest, church
+@cindex kirchenpausen
+
If there are 10 or fewer measures of rest, LilyPond prints
-@rglos{church rests} (a series of longa and breve rests)
-in the staff and
+a series of longa and breve rests (called in German
+Kirchenpausen - @q{church rests}) within the staff and
prints a simple line otherwise. This default number of 10
may be changed by overriding
@code{MultiMeasureRest.expand-limit}.
@code{\emptyText}), since this will cause the measure to expand to
accommodate the length of the text:
-@lilypond[quote,ragged-right,verbatim,fragment]
+@lilypond[quote,ragged-right,verbatim,fragment,relative=2]
\set Score.skipBars = ##t
\fatText
s1*0^\markup {[MAJOR GENERAL]}
s1*0^\markup {[MABEL] }
s1*0_\markup {\italic {Cue: ... it is yours}}
R1*30
-s1^\markup {CHORUS} % Chorus notes would go here
-c1
+c4^\markup {CHORUS} d f c
@end lilypond
@seealso
-This manual: @ref{Text}, @ref{Text scripts}.
+Notation Reference: @ref{Durations}, @ref{Text},
+@ref{Text markup}, @ref{Text scripts}.
Snippets: @lsrdir{rhythms}
-Internals Reference:
-
-@internalsref{MultiMeasureRest}.
+Internals Reference: @internalsref{MultiMeasureRest}.
The layout object @internalsref{MultiMeasureRestNumber} is for the
default number, and @internalsref{MultiMeasureRestText} for user
* Unmetered music::
* Polymetric notation::
* Automatic note splitting::
-* Setting automatic beam behavior::
@end menu
@node Time signature
@unnumberedsubsubsec Time signature
-@cindex Time signature
+@cindex time signature
@cindex meter
@funindex \time
the value of @code{timeSignatureFraction} also causes the symbol
to be printed.
-@cindex Measure groupings
+@cindex measure groupings
More options are available through the Scheme function
@code{set-time-signature}, which takes three arguments: the number
@cindex polymetric signatures
@cindex meter, polymetric
+@c TODO: add glossary entries for {signature, polymetric},
+@c {meter, polymetric}, {polymetric} (time signature, double}. rp
+
Double time signatures are not supported explicitly, but they can
be faked. In the next example, the markup for the time signature
is created with a markup text. This markup text is inserted in
signature. The latter is done with @code{\compressMusic}, which
is used in a similar way to @code{\times}, but does not create
a tuplet bracket. The syntax is
+
@funindex \compressMusic
@example
@seealso
-Snippets: @lsrdir{rhythms}
+@ignore
+TODO: add @rglos{polymetric time signature}, {polymetric}, {double time
+signature}, and {polymetric meter}. when glossary entries
+exist.
+@end ignore
+
+Snippets: @lsrdir{rhythms}, @lsr{contemporary,compound-time-signature}.
+
+Internals Reference: @internalsref{TimeSignature}, @internalsref{Timing-translator}, @internalsref{Staff}.
@node Automatic note splitting
Snippets: @lsrdir{rhythms}
-Internals Reference: @internalsref{Completion_heads_engraver}.
+Internals Reference: @internalsref{Note_heads_engraver},
+@internalsref{Completion_heads_engraver},
+@internalsref{Forbid_line_break_engraver}.
+
+
+
+
+
+@node Beams
+@subsection Beams
+
+@menu
+* Automatic beams::
+* Setting automatic beam behavior::
+* Manual beams::
+@end menu
+
+@node Automatic beams
+@unnumberedsubsubsec Automatic beams
+
+By default, beams are inserted automatically:
+
+@cindex beams, manual
+@cindex manual beams
+
+@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+\time 2/4 c8 c c c
+\time 6/8 c c c c8. c16 c8
+@end lilypond
+
+If these automatic decisions are not satisfactory, beaming can be
+entered explicitly; see @ref{Manual beams}. It is also possible
+to define beaming patterns that differ from the defaults; see
+@ref{Setting automatic beam behavior}. The default beaming rules
+are defined in @file{scm/@/auto@/-beam@/.scm}.
+
+@cindex autoBeamOn
+@cindex autoBeamOff
+
+@noindent
+Automatic beaming may be turned off and on with
+@code{\autoBeamOff} and @code{\autoBeamOn} commands:
+
+@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
+c4 c8 c8. c16 c8. c16 c8
+\autoBeamOff
+c4 c8 c8. c16 c8.
+\autoBeamOn
+c16 c8
+@end lilypond
+
+
+@commonprop
+
+Beaming patterns may be altered with the @code{beatGrouping} property,
+
+@lilypond[quote,verbatim,relative=2,fragment,ragged-right]
+\time 5/16
+\set beatGrouping = #'(2 3)
+c8[^"(2+3)" c16 c8]
+\set beatGrouping = #'(3 2)
+c8[^"(3+2)" c16 c8]
+@end lilypond
+
+@c [TODO I think this could be worded more clearly, but I'm not sure how.] rp
+The property @code{subdivideBeams} can be set in order to
+subdivide all 16th or shorter beams. When set, multiple beams
+will be sub-divided at beat positions, defined by the current
+value of @code{beatLength} (defaults to a quarter note), by
+drawing only one beam over the connection between beats.
+
+@lilypond[fragment,ragged-right,quote,relative=2,verbatim]
+c32[ c c c c c c c]
+\set subdivideBeams = ##t
+c32[ c c c c c c c]
+\set Score.beatLength = #(ly:make-moment 1 8)
+c32[ c c c c c c c]
+\set Score.beatLength = #(ly:make-moment 1 16)
+c32[ c c c c c c c]
+@end lilypond
+@funindex subdivideBeams
+
+@noindent
+For more information about @code{make-moment}, see
+@ref{Time administration}.
+
+@funindex breakable
+@cindex break, line
+@cindex line breaks
+
+Line breaks are normally forbidden when beams cross bar lines.
+This behavior can be changed by setting the @code{breakable}
+property: @code{\override Beam #'breakable = ##t}.
+
+@lilypond[ragged-right,relative=2,fragment,verbatim,quote]
+\override Beam #'breakable = ##t
+c8 \repeat unfold 15 {c[ c] } c
+@end lilypond
+
+@cindex beams and line breaks
+@cindex beams, kneed
+@cindex kneed beams
+@cindex auto-knee-gap
+
+Kneed beams are inserted automatically when a large gap is
+detected between the note heads. This behavior can be tuned
+through the @code{auto-knee-gap} property. A kneed beam is
+drawn if the gap is larger than the value of
+@code{auto-knee-gap} plus the width of the beam object (which
+depends on the duration of the notes and the slope of the beam).
+By default @code{auto-knee-gap} is set to 5.5 staff spaces.
+
+@lilypond[fragment,ragged-right,quote,verbatim]
+f8 f''8 f8 f''8
+\override Beam #'auto-knee-gap = #6
+f8 f''8 f8 f''8
+@end lilypond
+
+
+@seealso
+
+Notation Reference: @ref{Manual beams}, @ref{Setting automatic beam behavior}.
+
+Snippets: @lsrdir{rhythms}
+
+Internals Reference: @internalsref{Beam}.
+
+
+@refbugs
+
+Automatically kneed cross-staff beams cannot be used together with
+hidden staves. See @ref{Hiding staves}.
+
+Beams can collide with noteheads and accidentals in other voices
@node Setting automatic beam behavior
@funindex \autoBeamOn
@code{\autoBeamOn}.
-@commonprop
-
-Beaming patterns may be altered with the @code{beatGrouping} property,
-
-@lilypond[quote,verbatim,relative=2,fragment,ragged-right]
-\time 5/16
-\set beatGrouping = #'(2 3)
-c8[^"(2+3)" c16 c8]
-\set beatGrouping = #'(3 2)
-c8[^"(3+2)" c16 c8]
-@end lilypond
-
@refbugs
If a score ends while an automatic beam has not been ended and is
-still accepting notes, this last beam will not be typeset at all. The
-same holds polyphonic voices, entered with @code{<< @dots{} \\ @dots{}
->>}. If a polyphonic voice ends while an automatic beam is still
-accepting notes, it is not typeset.
+still accepting notes, this last beam will not be typeset at all.
+The same holds for polyphonic voices, entered with @code{<<
+@dots{} \\ @dots{} >>}. If a polyphonic voice ends while an
+automatic beam is still accepting notes, it is not typeset.
@seealso
Snippets: @lsrdir{rhythms}
+@node Manual beams
+@unnumberedsubsubsec Manual beams
+@cindex beams, manual
-@node Beams
-@subsection Beams
-
-@menu
-* Automatic beams::
-* Manual beams::
-@end menu
-
-@node Automatic beams
-@unnumberedsubsubsec Automatic beams
-
-By default beams are inserted automatically
-
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
-\time 2/4 c8 c c c
-\time 6/8 c c c c8. c16 c8
-@end lilypond
-
-When these automatic decisions are not good enough, beaming
-can be entered explicitly. It is also possible to define beaming
-patterns that differ from the defaults. See @ref{Manual beams}
-and @ref{Setting automatic beam behavior}.
-
-@cindex autoBeamOn
-@cindex autoBeamOff
-
-@noindent
-Automatic beaming may be turned off and on with
-@code{\autoBeamOff} and @code{\autoBeamOn} commands:
-
-@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
-c4 c8 c8. c16 c8. c16 c8
-\autoBeamOff
-c4 c8 c8. c16 c8.
-\autoBeamOn
-c16 c8
-@end lilypond
-
-
-@commonprop
-
-@funindex stemLeftBeamCount
-@funindex stemRightBeamCount
-
-LilyPond can automatically determine beaming patterns within a
-beam, but this automatic behavior can sometimes produce odd
-results; therefore the @code{stemLeftBeamCount} and
-@code{stemRightBeamCount} properties can be used to override the
-defaults. If either property is set, its value will be used only
-once, and then it is erased.
+In some cases it may be necessary to override the automatic
+beaming algorithm. For example, the autobeamer will not put beams
+over rests or bar lines, and in choral scores the beaming is
+often set to follow the meter of the lyrics rather than the
+notes. Such beams can be specified manually by
+marking the begin and end point with @code{[} and @code{]}
@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
{
- f8[ r16
- f g a]
- f8[ r16
- \set stemLeftBeamCount = #1
- f g a]
+ r4 r8[ g' a r8] r8 g[ | a] r8
}
@end lilypond
-The property @code{subdivideBeams} can be set in order to
-subdivide all 16th or shorter beams.
-When set, multiple beams will be sub-divided at beat
-positions, defined by the current value of @code{beatLength},
-by drawing only one beam over the beat.
-
-@lilypond[fragment,ragged-right,quote,relative=2,verbatim]
-c16[ c c c c c c c]
-\set subdivideBeams = ##t
-c16[ c c c c c c c]
-\set Score.beatLength = #(ly:make-moment 1 8)
-c16[ c c c c c c c]
-@end lilypond
-@funindex subdivideBeams
-
-@noindent
-For more information about @code{make-moment}, see
-@ref{Time administration}.
-
-@c TODO Consider whether the section Setting automatic
-@c beam behavior should all be moved here. For now
-@c here's a link to it.
-
-For details about modifying the automatic beam behaviour
-see @ref{Setting automatic beam behavior}
-
-@funindex breakable
-
-Line breaks are normally forbidden when beams cross barlines.
-This behavior can be changed by setting the @code{breakable}
-property: @code{\override Beam #'breakable = ##t}.
-
-@cindex beams and line breaks
-@cindex beams, kneed
-@cindex kneed beams
-@cindex auto-knee-gap
-
-Kneed beams are inserted automatically when a large gap is
-detected between the note heads. This behavior can be tuned
-through the @code{auto-knee-gap} property. A kneed beam is
-drawn if the gap is larger than the value of
-@code{auto-knee-gap} plus the width of the beam object (which
-depends on the duration of the notes and the slope of the beam).
-By default @code{auto-knee-gap} is set to 5.5 staff spaces.
-
-@lilypond[fragment,ragged-right,quote,verbatim]
-f8 f''8 f8 f''8
-\override Beam #'auto-knee-gap = #6
-f8 f''8 f8 f''8
-@end lilypond
-
-
-@seealso
-
-Snippets: @lsrdir{rhythms}
-
-Internals Reference: @internalsref{Beam}.
-
-
-@refbugs
-
-Automatically kneed cross-staff beams cannot be used together with
-hidden staves. See @ref{Hiding staves}.
-
-Beams can collide with noteheads and accidentals in other voices
-
-@node Manual beams
-@unnumberedsubsubsec Manual beams
-
-@cindex beams, manual
Individual notes may be marked with @code{\noBeam} to prevent them
from being beamed:
these would delimit the same group of notes, but this is not
required: the two commands are independent.
-In the following example the eight 16th notes occupy exactly
-the same time as a half note, but the first note is twice
-as short as the last one, with the intermediate notes gradually
-lengthening. The first four 32nd notes gradually speed up,
-while the last four 32nd notes are at a constant tempo.
+In the following example the eight 16th notes occupy exactly the
+same time as a half note, but the first note is one half as long
+as the last one, with the intermediate notes gradually
+lengthening. The first four 32nd notes gradually speed up, while
+the last four 32nd notes are at a constant tempo.
@lilypond[ragged-right,relative=1,fragment,verbatim,quote]
\override Beam #'grow-direction = #LEFT
The spacing in the printed output represents the
note durations only approximately, but the midi output is exact.
-
-@commonprop
-
-Line breaking is prevented by beams which straddle barlines. The
-@samp{breakable} property of @code{Beam} allows this behaviour
-to be overridden:
-
-@lilypond[ragged-right,relative=2,fragment,verbatim,quote]
-\override Beam #'breakable = ##t
-c8 \repeat unfold 15 {c[ c] } c
-@end lilypond
-
-
@refbugs
The @code{\featherDurations} command only works with very short
@node Bar lines
@unnumberedsubsubsec Bar lines
-@cindex Bar lines
-@cindex Barlines
+@cindex bar lines
@funindex \bar
@cindex measure lines
@cindex repeat bars
breaks happen only at the end of complete bars, i.e. where
the end of a note coincides with the end of a bar.
+@cindex line breaks
+@cindex bar lines, invisible
+@cindex measure lines, invisible
+
Line breaks are also permitted at manually inserted bar lines
even within incomplete bars. To allow a line break without
printing a bar line, use
f1 \bar "|:" g \bar ":|:" a \bar ":|" b
@end lilypond
+@cindex repeats
+
Although the bar line types signifying repeats may be inserted
manually they do not in themselves cause LilyPond to recognise
a repeated section. Such repeated sections are better entered
@seealso
-In this manual: @ref{Repeats}, @ref{System start delimiters}.
+Notation Reference: @ref{Line breaking}, @ref{Repeats},
+@ref{System start delimiters}.
Snippets: @lsrdir{rhythms}
@node Bar numbers
@unnumberedsubsubsec Bar numbers
-@cindex Bar numbers
+@cindex bar numbers
@cindex measure numbers
@funindex currentBarNumber
-Bar numbers are typeset by default at the start of every line
-except the first line. The
-number itself is stored in the @code{currentBarNumber} property,
-which is normally updated automatically for every measure. It
-may also be set manually:
+Bar numbers are typeset by default at the start of every line except
+the first line. The number itself is stored in the
+@code{currentBarNumber} property, which is normally updated
+automatically for every measure. It may also be set manually:
@lilypond[verbatim,ragged-right,quote,fragment,relative]
c1 c c c
c c c c c
@end lilypond
+@cindex measure number, format
+@cindex bar number, format
+
The size of the bar number may be changed. This is illustrated
in the following example, which also shows how to enclose bar
numbers in boxes and circles, and shows an alternative way
\repeat unfold 4 { c1 } \bar "|."
@end lilypond
-@cindex Bar number alignment
+@cindex bar number alignment
Bar numbers by default are left-aligned to their parent object.
This is usually the left edge of a line or, if numbers are printed
@node Bar and bar number checks
@unnumberedsubsubsec Bar and bar number checks
-@cindex Bar check
+@cindex bar check
@funindex barCheckSynchronize
@funindex |
Bar checks help detect errors in the entered durations.
-A bar check may be entered using the bar symbol, @samp{|},
+A bar check may be entered using the bar symbol, @code{|},
at any place where a bar line is expected to fall.
If bar check lines are encountered at other places,
a list of warnings is printed in the log file,
showing the line numbers and lines
in which the bar checks failed. In the next
-example, the second bar check will signal an error
+example, the second bar check will signal an error.
@example
\time 3/4 c2 e4 | g2 |
@funindex pipeSymbol
It is also possible to redefine the action taken when a bar check
-or pipe symbol, @samp{|}, is encountered in the input, so that
+or pipe symbol, @code{|}, is encountered in the input, so that
it does something other than a bar check. This is done by
assigning a music expression to @code{pipeSymbol}.
-In the following example @samp{|} is set to insert a double bar
+In the following example @code{|} is set to insert a double bar
line wherever it appears in the input, rather than checking
for end of bar.
@node Rehearsal marks
@unnumberedsubsubsec Rehearsal marks
-@cindex Rehearsal marks
+@cindex rehearsal marks
+@cindex mark, rehearsal
@funindex \mark
To print a rehearsal mark, use the @code{\mark} command
mark manually. The value to use is stored in the property
@code{rehearsalMark}.
+@cindex rehearsal mark format
+@cindex rehearsal mark style
+@cindex style, rehearsal mark
+@cindex format, rehearsal mark
+@cindex mark, rehearsal, style
+@cindex mark, rehearsal, format
+
The style is defined by the property @code{markFormatter}. It is
a function taking the current mark (an integer) and the current
context as argument. It should return a markup object. In the
Snippets: @lsrdir{rhythms}
-This manual: @ref{Text marks}.
+This manual: @ref{The Feta font}, @ref{Text marks}.
Internals Reference: @internalsref{RehearsalMark}.
@funindex \afterGrace
+@cindex grace notes, following
+
If you want to end a note with a grace, use the @code{\afterGrace}
command. It takes two arguments: the main note, and the grace
notes following the main note.
seen in the file @file{ly/@/grace@/-init@/.ly}. By redefining
them other effects may be obtained.
+@cindex stem, with slash
+
@noindent
The slash through the stem in @emph{acciaccatura}s can be obtained in
other situations by @code{\override Stem #'stroke-style =
@seealso
+Music Glossary: @rglos{grace notes}, @rglos{acciaccatura},
+@c [TODO add appoggiatura]
+
Snippets: @lsrdir{rhythms}
Internals Reference: @internalsref{GraceMusic}.
@node Aligning to cadenzas
@unnumberedsubsubsec Aligning to cadenzas
+@cindex cadenza
+@cindex cadenza, aligning to
+@cindex aligning to cadenza
+
In an orchestral context, cadenzas present a special problem: when
constructing a score that includes a cadenza, all other
instruments should skip just as many notes as the length of the
cadenza, otherwise they will start too soon or too late.
-A solution to this problem are the functions
+A solution to this problem is to use the functions
@code{mmrest-of-length} and @code{skip-of-length}. These Scheme
-functions take a piece of music as argument, and generate a
-multi-rest or @code{\skip}, exactly as long as the piece. The use
-of @code{mmrest-of-length} is demonstrated in the following
-example.
+functions take a piece of music as argument, and generate a multi-rest
+or @code{\skip}, exactly as long as the piece. The use of
+@code{mmrest-of-length} is demonstrated in the following example.
@lilypond[verbatim,ragged-right,quote]
cadenza = \relative c' {
@node Time administration
@unnumberedsubsubsec Time administration
-@cindex Time administration
+@cindex time administration
+@cindex timing (within the score)
+@cindex music, unmetered
+@cindex unmetered music
@funindex currentBarNumber
@funindex measurePosition
The following properties of @code{Timing} are used
to keep track of timing within the score.
+@cindex bar number
+@cindex measure number
+
@table @code
@item currentBarNumber
The current measure number. For an example showing the
+
projects / lilypond.git / blobdiff