Guide, node Updating translation committishes..
@end ignore
-@c \version "2.12.0"
+@c \version "2.14.0"
@node Rhythms
@section Rhythms
@snippets
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{alternative-breve-note.ly}
+
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{changing-the-number-of-augmentation-dots-per-note.ly}
@knownissues
-
Switching staves when a tie is active will not produce a slanted
tie.
-Changing clefs or octavations during a tie is not really
+Changing clefs or ottavations during a tie is not really
well-defined. In these cases, a slur may be preferable.
@funindex breve
Rests are entered like notes with the note name @code{r}.
-Durations longer than a whole rest use the predefined
-commands shown:
+Durations longer than a whole rest use the following predefined
+commands:
@c \time 16/1 is used to avoid spurious bar lines
@c and long tracts of empty measures
-@lilypond[fragment,quote,verbatim]
+@lilypond[quote,verbatim,relative=2]
\new Staff {
% These two lines are just to prettify this example
\time 16/1
Whole measure rests, centered in the middle of the measure, must be
entered as multi-measure rests. They can be used for a single
-measure as well as many measures and are discussed in @ref{Full
-measure rests}.
+measure as well as many measures and are discussed in
+@ref{Full measure rests}.
@cindex rest, specifying vertical position
Spacer rests are available only in note mode and chord mode. In
other situations, for example, when entering lyrics, the
command @code{\skip} is used to skip a musical moment.
-@code{\skip} requires an explicit duration.
+@code{\skip} requires an explicit duration, but this is ignored if
+the lyrics derive their durations from the notes in an associated
+melody through @code{\addlyrics} or @code{\lyricsto}.
@lilypond[quote,verbatim,relative=2]
<<
@lilypond[quote,verbatim,relative=2]
<<
{
- \repeat unfold 8 {a4}
+ \repeat unfold 8 { a4 }
}
{
a4 \skip 2 a |
contexts to be created if none exist, just like notes and rests
do:
-@lilypond[quote,verbatim,fragment]
+@lilypond[quote,verbatim,relative=2]
s1 s s
@end lilypond
@code{\skip} simply skips musical time; it creates no output of
any kind.
-@lilypond[quote,verbatim,fragment]
+@lilypond[quote,verbatim,relative=2]
% This is valid input, but does nothing
\skip 1 \skip1 \skip 1
@end lilypond
always be an integral number of measure-lengths, so augmentation dots
or fractions must often be used:
-@lilypond[quote,fragment,verbatim]
+@lilypond[quote,verbatim,relative=2]
\compressFullBarRests
\time 2/4
R1 | R2 |
A full-measure rest is printed as either a whole or breve rest,
centered in the measure, depending on the time signature.
-@lilypond[quote,verbatim,fragment]
+@lilypond[quote,verbatim,relative=2]
\time 4/4
R1 |
\time 6/4
rest can be shown as a single measure containing a multi-measure rest
symbol, with the number of measures of rest printed above the measure:
-@lilypond[quote,fragment,verbatim]
+@lilypond[quote,verbatim,relative=2]
% Default behavior
\time 3/4 r2. | R2.*2 |
\time 2/4 R2 |
The predefined command @code{\fermataMarkup}
is provided for adding fermatas.
-@lilypond[quote,verbatim,fragment]
+@lilypond[quote,verbatim,relative=2]
\compressFullBarRests
\time 3/4
R2.*10^\markup { \italic "ad lib." }
R2.^\fermataMarkup
@end lilypond
-@warning{
-Markups attached to a multi-measure rest are
-objects of type @code{MultiMeasureRestText}, not
-@code{TextScript}. Overrides must be directed to the correct
-object, or they will be ignored. See the following example.
-}
+@warning{Markups attached to a multi-measure rest are objects of type
+@code{MultiMeasureRestText}, not @code{TextScript}. Overrides must
+be directed to the correct object, or they will be ignored. See the
+following example:}
-@lilypond[quote,verbatim,fragment]
+@lilypond[quote,verbatim,relative=2]
% This fails, as the wrong object name is specified
\override TextScript #'padding = #5
R1^"wrong"
-% This is correct and works
+% This is the correct object name to be specified
\override MultiMeasureRestText #'padding = #5
R1^"right"
@end lilypond
@cindex multi-measure rests and fingerings
@knownissues
-
-If an attempt is made to use fingerings (e.g.,
-@code{R1*10-4}) to put numbers over multi-measure rests, the
-fingering numeral (4) may collide with the bar counter
-numeral (10).
+Fingerings over multi-measure rests (e.g. @code{R1*10-4}) may result
+in the fingering numeral colliding with the bar counter
+numeral.
@cindex condensing rests
@cindex rest, condensing ordinary
@lilypond[quote,verbatim]
\score {
- \relative c' {
- \overrideTimeSignatureSettings
- #'Score % context
- #'(4 . 4) % timeSignatureFraction
- #'(1 . 4) % baseMomentFraction
- #'(3 1) % beatStructure
- #'() % beamExceptions
- \time 4/4
- \repeat unfold 8 c8 |
+ \new Staff {
+ \relative c' {
+ \overrideTimeSignatureSettings
+ #'(4 . 4) % timeSignatureFraction
+ #'(1 . 4) % baseMomentFraction
+ #'(3 1) % beatStructure
+ #'() % beamExceptions
+ \time 4/4
+ \repeat unfold 8 { c8 } |
+ }
}
}
@end lilypond
-@code{\overrideTimeSignatureSettings} takes five arguments:
+@code{\overrideTimeSignatureSettings} takes four arguments:
@enumerate
-@item
-@code{@var{context}}, a Scheme symbol that describes the context
-to which the default setting will apply.
@item
@code{@var{timeSignatureFraction}}, a Scheme pair describing the
described in @ref{Setting automatic beam behavior}.
@end enumerate
+The context containing @code{\overrideTimeSignatureSettings} must
+be instantiated before the @code{\overrideTimeSignatureSettings}
+call is executed. That means it must either be explicitly
+instantiated or there must be music in the context before the
+@code{\overrideTimeSignatureSettings} call:
+
+@lilypond[quote,verbatim]
+\score {
+ \relative c' {
+ % This call will fail because the context isn't yet instantiated
+ \overrideTimeSignatureSettings
+ #'(4 . 4) % timeSignatureFraction
+ #'(1 . 4) % baseMomentFraction
+ #'(3 1) % beatStructure
+ #'() % beamExceptions
+ \time 4/4
+ c8^\markup {"Beamed (2 2)"}
+ \repeat unfold 7 { c8 } |
+ % This call will succeed
+ \overrideTimeSignatureSettings
+ #'(4 . 4) % timeSignatureFraction
+ #'(1 . 4) % baseMomentFraction
+ #'(3 1) % beatStructure
+ #'() % beamExceptions
+ \time 4/4
+ c8^\markup {"Beamed (3 1)"}
+ \repeat unfold 7 { c8 } |
+ }
+}
+@end lilypond
+
+
@cindex time signature properties, restoring default values
@cindex restoring default properties for time signatures
@funindex \revertTimeSignatureSettings
@lilypond[quote,verbatim]
\score{
\relative c' {
- \repeat unfold 8 c8 |
+ \repeat unfold 8 { c8 } |
\overrideTimeSignatureSettings
- #'Score % context
- #'(4 . 4) % timeSignatureFraction
- #'(1 . 4) % baseMomentFraction
- #'(3 1) % beatStructure
- #'((end . (((1 . 8) . (3 1))))) % beamExceptions
+ #'(4 . 4) % timeSignatureFraction
+ #'(1 . 4) % baseMomentFraction
+ #'(3 1) % beatStructure
+ #'() % beamExceptions
\time 4/4
- \repeat unfold 8 c8 |
- \revertTimeSignatureSettings #'Score #'(4 . 4)
+ \repeat unfold 8 { c8 } |
+ \revertTimeSignatureSettings #'(4 . 4)
\time 4/4
- \repeat unfold 8 c8 |
+ \repeat unfold 8 { c8 } |
+ }
+}
+@end lilypond
+
+Different values of default time signature properties can be established
+for different staves by moving the @code{Timing_translator} and the
+@code{Default_bar_line_engraver} from the @code{Score} context to the
+@code{Staff} context.
+
+@lilypond[quote, verbatim]
+\score {
+ \new StaffGroup <<
+ \new Staff {
+ \overrideTimeSignatureSettings
+ #'(4 . 4) % timeSignatureFraction
+ #'(1 . 4) % baseMomentFraction
+ #'(3 1) % beatStructure
+ #'() % beamExceptions
+ \time 4/4
+ \repeat unfold 8 {c''8}
+ }
+ \new Staff {
+ \overrideTimeSignatureSettings
+ #'(4 . 4) % timeSignatureFraction
+ #'(1 . 4) % baseMomentFraction
+ #'(1 3) % beatStructure
+ #'() % beamExceptions
+ \time 4/4
+ \repeat unfold 8 {c''8}
+ }
+ >>
+ \layout {
+ \context {
+ \Score
+ \remove "Timing_translator"
+ \remove "Default_bar_line_engraver"
+ }
+ \context {
+ \Staff
+ \consists "Timing_translator"
+ \consists "Default_bar_line_engraver"
+ }
}
}
@end lilypond
e4. d8 c2
@end lilypond
+Metronome marks may also be printed as a range of two numbers:
+
+@lilypond[verbatim,quote,relative=1]
+\tempo 4 = 40 ~ 46
+c4. e8 a4 g
+b,2 d4 r
+@end lilypond
+
Tempo indications with text can be used instead:
@lilypond[verbatim,quote,relative=2]
The property @code{measurePosition} contains a rational number
indicating how much of the measure has passed at this point. Note
that this is set to a negative number by the @code{\partial} command:
-i.e., @code{\partial 4} is internally translated to @code{-4}, meaning
+i.e., @code{\partial 4} is internally translated to @w{@code{-4}}, meaning
@qq{there is a quarter note left in the measure.}
@seealso
@lilypond[verbatim,relative=2,quote]
c4 d e d
\cadenzaOn
-c4 c d8 d d f4 g4.
+c4 c d8[ d d] f4 g4.
\cadenzaOff
\bar "|"
d4 e d c
\override Score.BarNumber #'break-visibility = #all-visible
c4 d e d
\cadenzaOn
-c4 c d8 d d f4 g4.
+c4 c d8[ d d] f4 g4.
\cadenzaOff
\bar "|"
d4 e d c
@end lilypond
+@cindex beams, in cadenzas
+@cindex beams, in unmetered music
+@cindex cadenza, with beams
+@cindex unmetered music, with beams
+
+Automatic beaming is disabled by @code{\cadenzaOn} and enabled
+by @code{\cadenzaOff}. Therefore, all beaming in cadenzas
+must be entered manually (@ref{Manual beams}).
+
+@lilypond[verbatim,relative=2,quote]
+\repeat unfold 8 { c8 }
+\cadenzaOn
+\repeat unfold 5 { c8 }
+\bar"|"
+\cadenzaOff
+\repeat unfold 8 { c8 }
+@end lilypond
+
Note that these predefined commands affect all staves in the
score, even when they are placed in just one @code{Voice}
context. To change this, move the @code{Timing_translator}
Notation Reference:
@ref{Visibility of objects},
-@ref{Polymetric notation}.
+@ref{Polymetric notation},
+@ref{Manual beams}.
Snippets:
@rlsr{Rhythms}.
@noindent
to indicate where breaks can occur.
-You must explicitly create a @code{Voice} context when starting a
+You should explicitly create a @code{Voice} context when starting a
piece with @code{\cadenzaOn}, otherwise strange errors may occur.
-@lilypond[verbatim,relative=2,quote]
-\new Voice \relative c'{
- \cadenzaOn
- c16^"Solo Free Time" d e f g2. \bar "||"
- \cadenzaOff
-}
-@end lilypond
+@example
+\new Voice @{
+ \relative c' @{
+ \cadenzaOn
+ c16[^"Solo Free Time" d e f] g2.
+ \bar "||"
+ \cadenzaOff
+ @}
+@}
+@end example
@node Polymetric notation
@code{\times}, but does not create a tuplet bracket; see
@ref{Scaling durations}.
-@cindex beaming in polymetric music
-@cindex beaming in polymetric meter
+@cindex beams, with polymetric meters
+@cindex polymetric meters, with beams
In this example, music with the time signatures of 3/4, 9/8, and
10/8 are used in parallel. In the second staff, shown durations
It will often be necessary to insert beams manually, as the
duration scaling affects the autobeaming rules.
-@lilypond[quote,verbatim,fragment]
+@lilypond[quote,verbatim]
\relative c' <<
\new Staff {
\time 3/4
\time 3/4
\set Staff.timeSignatureFraction = #'(9 . 8)
\scaleDurations #'(2 . 3)
- \repeat unfold 6 { c8[ c c] }
+ \repeat unfold 6 { c8[ c c] }
}
\new Staff {
\time 3/4
@cindex notes, splitting
@cindex splitting notes
+@cindex rests, splitting
+@cindex splitting rests
@funindex Note_heads_engraver
@funindex Completion_heads_engraver
+@funindex Completion_rest_engraver
-Long notes which overrun bar lines can be converted automatically
-to tied notes. This is done by replacing the
-@code{Note_heads_engraver} with the
-@code{Completion_heads_engraver}. In the following
-example, notes crossing the bar lines are split and tied.
+Long notes which overrun bar lines can be converted automatically to
+tied notes. This is done by replacing the @code{Note_heads_engraver}
+with the @code{Completion_heads_engraver}. Similarly, long rests which
+overrun bar lines are split automatically by replacing the
+@code{Rest_engraver} with the @code{Completion_rest_engraver}. In the
+following example, notes and rests crossing the bar lines are split,
+notes are also tied.
@lilypond[quote,verbatim,relative=1]
\new Voice \with {
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
+ \remove "Rest_engraver"
+ \consists "Completion_rest_engraver"
}
-{ c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2 }
+{ c2. c8 d4 e f g a b c8 c2 b4 a g16 f4 e d c8. c2 r1*2 }
@end lilypond
-This engraver splits all running notes at the bar line, and
-inserts ties. One of its uses is to debug complex scores: if the
-measures are not entirely filled, then the ties show exactly how
+These engravers split all running notes and rests at the bar line, and
+inserts ties for notes. One of its uses is to debug complex scores: if
+the measures are not entirely filled, then the ties show exactly how
much each measure is off.
Internals Reference:
@rinternals{Note_heads_engraver},
@rinternals{Completion_heads_engraver},
+@rinternals{Rest_engraver},
+@rinternals{Completion_rest_engraver},
@rinternals{Forbid_line_break_engraver}.
c1 f g c
}
}
-
\new Voice \with {
\consists Pitch_squash_engraver
} \relative c'' {
@cindex beams, manual
@cindex manual beams
-@cindex beams, setting rules for
-@cindex beams, custom rules for
+@cindex beams, customizing rules
@funindex \autoBeamOn
@funindex autoBeamOn
@lilypond[quote,verbatim,relative=2]
\time 2/4 c8 c c c
-\time 6/8 c c c c8. c16 c8
+\time 6/8 c8 c c c8. c16 c8
@end lilypond
If these automatic decisions are not satisfactory, beaming can be
c16 c8
@end lilypond
-@cindex melismata, beams
-@cindex beams and melismata
+@cindex melismata, with beams
+@cindex beams, with melismata
@warning{If beams are used to indicate melismata in songs, then
automatic beaming should be switched off with @code{\autoBeamOff}
Beaming patterns that differ from the automatic defaults can be
created; see @ref{Setting automatic beam behavior}.
-
@predefined
@code{\autoBeamOff},
@code{\autoBeamOn}.
@endpredefined
-
-@snippets
-
-
-@cindex line breaks and beams
-@cindex beams and line breaks
-
+@cindex beams, line breaks
+@cindex line breaks, beams
+@cindex beams, with knee gap
+@cindex knee gap, with beams
@funindex breakable
+@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{beams-across-line-breaks.ly}
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{changing-beam-knee-gap.ly}
-@cindex \partcombine and \autoBeamOff
-@cindex \autoBeamOff and \partcombine
-
+@cindex beams, \partcombine with \autoBeamOff
+@cindex voices, \partcombine with \autoBeamOff
@lilypondfile [verbatim, lilyquote, ragged-right, texidoc, doctitle]
{partcombine-and-autobeamoff.ly}
-
@seealso
Notation Reference:
@ref{Manual beams},
@ref{Setting automatic beam behavior}.
Installed Files:
-@file{scm/@/auto@/-beam@/.scm}.
+@file{scm/auto-beam.scm}.
Snippets:
@rlsr{Rhythms}.
@rinternals{beam-interface},
@rinternals{unbreakable-spanner-interface}.
-
-@knownissues
-
-Beams can collide with note heads and accidentals in other voices.
-
-
@node Setting automatic beam behavior
@unnumberedsubsubsec Setting automatic beam behavior
-
-@cindex automatic beams, tuning
-@cindex tuning automatic beaming
-@cindex automatic beam generation
-@cindex autobeam
-@cindex lyrics and beaming
+@cindex beams, with lyrics
+@cindex lyrics, with beams
@funindex autoBeaming
@funindex baseMoment
@funindex \set
@funindex set
-The placement of automatic beams is determined by the context properties
-@code{baseMoment}, @code{beatStructure}, @code{beamExceptions},
-and @code{autoBeaming}.
-
-The following rules, in order of priority, apply when determining
-the appearance of beams:
-
-@itemize
-@item
-If a manual beam is specified with @code{[..]} set the beam
-as specified, otherwise
-
-@item
-if @code{\autoBeamOff} is in force do not beam, otherwise
-
-@item
-if a beam-ending rule is defined in @code{beamExceptions}
-for the beam-type, use it to determine the valid places where
-beams may end, otherwise
-
-@item
-if a beam-ending rule is defined in @code{beamExceptions}
-for a longer beam-type, use it to determined the valid places
-where beams may end, otherwise
-
-@item
-use the values of @code{baseMoment} and @code{beatStructure} to
-determine the ends of the beats in the measure, and
-end beams at the end of beats.
-
-@end itemize
-
-The beam-type is the duration of the shortest note in the beamed group.
-
-@i{@strong{Modifying the grouping of beats}}
-
-By default @code{baseMoment} is set by the @code{\time} command,
-normally to one over the denominator of the time signature.
-Any exceptions to this default
-can be found in @file{scm/@/time@/-signature@/-settings@/.scm}.
-Changing the default value of @code{baseMoment} for a given
-time signature is described in @ref{Time signature}.
-
-@code{baseMoment} is a @i{moment},
-a unit of musical duration. A quantity of type @i{moment} is
-created by the scheme function @code{ly:make-moment}. For more
-information about this function, see @ref{Time administration}.
-
-Special (i.e., other than at the end of the beat) autobeam settings
-are stored in the
-@code{beamExceptions} property. Default values of @code{beamExceptions}
-are established by the @code{\time} command. Default values of
-@code{beamExceptions} for a time signature
-are determined in @file{scm/@/time@/-signature@/-settings@/.scm}.
-Entries in @code{beamExceptions} are indexed by rule type and beam type.
-
-Rule type should be @code{#'end} for beam ending.
-
-The ending rules consist of a scheme alist
-(or list of pairs) that
-indicates the beam type and the grouping to be applied to
-beams containing notes with a shortest duration of that
-beam type.
-
-@example
-#'((beam-type1 . grouping-1)
- (beam-type2 . grouping-2)
- (beam-type3 . grouping-3))
-@end example
-
-Beam type is a scheme pair indicating the duration
-of the beam, e.g., @code{(1 . 16)}.
-
-Grouping is a scheme list indicating the grouping to be applied to
-the beam. The grouping is in units of the beam type.
-
-For reference, the default beaming rules are found in
-@file{scm/time-signature-settings.scm}.
-
-Alternate values for @code{beamExceptions}
-can be defined using the @code{\set} command.
-
-@warning{
-A @code{beamExceptions} value must be
-@emph{complete} exceptions list. That is, every exception that should
-be applied must be included in the setting.
-It is not possible to add, remove, or change only one of the exceptions.
-While this may seem cumbersome,
-it means that the current beaming settings need not be known
-in order to specify a new beaming pattern.}
+In most instances, automatic beams will end at the end of a beat.
+The ending points for beats are determined by the context properties
+@code{baseMoment} and @code{beatStructure}. @code{beatStructure}
+is a scheme list that defines the length of each beat in the measure
+in units of @code{baseMoment}. By default, @code{baseMoment} is
+the one over numerator of the time signature. By default,
+each unit of length @code{baseMoment} is a single beat.
@lilypond[quote,relative=2,verbatim]
\time 5/16
-c8^"beats" c16 c8 |
-\set beatStructure = #'(2 3)
-c8^"(2+3)" c16 c8
-\set beatStructure = #'(3 2)
-c8^"(3+2)" c16 c8
+c16^"default" c c c c |
+\set Timing.beatStructure = #'(2 3)
+c16^"(2+3)" c c c c |
+\set Timing.beatStructure = #'(3 2)
+c16^"(3+2)" c c c c |
@end lilypond
Beam setting changes can be limited to specific contexts. If no
@lilypond[quote,verbatim,relative=2]
\time 7/8
% rhythm 3-1-1-2
-% Context Voice specified -- does not work correctly
+% Change applied to Voice by default -- does not work correctly
% Because of autogenerated voices, all beating will
% be at baseMoment (1 . 8)
\set beatStructure = #'(3 1 1 2)
<< {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>
@end lilypond
-Beam settings can be set back to default behavior. This
-is accomplished by setting the time signature.
+The value of @code{baseMoment} can be adjusted to change
+the beaming behavior, if desired. When this is done,
+the value of @code{beatStructure} must be set to be
+compatible with the new value of @code{baseMoment}.
@lilypond[quote,verbatim,relative=2]
-\time 4/4
-\repeat unfold 8 {a8}
-% eliminate beam exception that groups beats 1, 2 and 3, 4
-\set Timing.beamExceptions = #'()
-\repeat unfold 8 {a8}
+\time 5/8
+\set Timing.baseMoment = #(ly:make-moment 1 16)
+\set Timing.beatStructure = #'(7 3)
+\repeat unfold 10 { a16 }
+@end lilypond
+
+@code{baseMoment} is a @i{moment}; a unit of musical duration. A
+quantity of type @i{moment} is created by the scheme function
+@code{ly:make-moment}. For more information about this function,
+see @ref{Time administration}.
+
+By default @code{baseMoment} is set to one over the denominator of
+the time signature. Any exceptions to this default can be found in
+@file{scm/time-signature-settings.scm}.
+
+Special autobeaming rules (other than ending a beam on a beat)
+are defined in the @code{beamExceptions} property.
+
+@lilypond[quote,relative=2,verbatim]
+\time 3/16
+\set Timing.beatStructure = #'(2 1)
+\set Timing.beamExceptions =
+ #'( ;start of alist
+ (end . ;entry for end of beams
+ ( ;start of alist of end points
+ ((1 . 32) . (2 2 2)) ;rule for 1/32 beams -- end each 1/16
+ ))) %close all entries
+c16 c c |
+\repeat unfold 6 { c32 } |
+@end lilypond
+
+@code{beamExceptions} is an alist with a key of rule-type and a value
+of beaming-rules.
+
+At this time the only available value of rule-type is
+@code{#'end} for beam ending.
+
+Beaming-rules is a scheme alist (or list of pairs) that indicates the
+beam type and the grouping to be applied to beams containing notes with
+a shortest duration of that beam type.
+
+@example
+#'((beam-type1 . grouping-1)
+ (beam-type2 . grouping-2)
+ (beam-type3 . grouping-3))
+@end example
+
+Beam type is a scheme pair indicating the duration of the beam,
+e.g., @code{(1 . 16)}.
+
+Grouping is a scheme list indicating the grouping to be applied to
+the beam. The grouping is in units of the beam type.
+
+@warning{ A @code{beamExceptions} value must be @emph{complete}
+exceptions list. That is, every exception that should be applied
+must be included in the setting. It is not possible to add, remove,
+or change only one of the exceptions. While this may seem cumbersome,
+it means that the current beaming settings need not be known in order
+to specify a new beaming pattern.}
+
+When the time signature is changed, default values of
+@code{Timing.baseMoment}, @code{Timing.beatStructure},
+and @code{Timing.beamExceptions} are set. Setting the time signature
+will reset the automatic beaming settings for the @code{Timing}
+context to the default behavior.
+
+@lilypond[quote,verbatim,relative=2]
+\time 6/8
+\repeat unfold 6 { a8 }
+% group (4 + 2)
+\set Timing.beatStructure = #'(4 2)
+\repeat unfold 6 { a8 }
% go back to default behavior
+\time 6/8
+\repeat unfold 6 { a8 }
+@end lilypond
+
+The default automatic beaming settings for a time signature
+are determined in @file{scm/time-signature-settings.scm}.
+Changing the default automatic beaming settings
+for a time signature is described in @ref{Time signature}.
+
+Many automatic beaming settings for a time signature contain an
+entry for @code{beamExceptions}. For example, 4/4 time tries to
+beam the measure in two if there are only eighth notes. The
+@code{beamExceptions} rule can override the @code{beatStructure} setting
+if @code{beamExceptions} is not reset.
+
+@lilypond[quote,verbatim,relative=2]
\time 4/4
-\repeat unfold 8 {a8}
+\set Timing.baseMoment = #(ly:make-moment 1 8)
+\set Timing.beatStructure = #'(3 3 2)
+% This won't beam (3 3 2) because of beamExceptions
+\repeat unfold 8 {c8} |
+% This will beam (3 3 2) because we clear beamExceptions
+\set Timing.beamExceptions = #'()
+\repeat unfold 8 {c8}
@end lilypond
+In a similar fashion, eighth notes in 3/4 time are beamed as a full
+measure by default. To beam eighth notes in 3/4 time on the beat,
+reset @code{beamExceptions}.
+
+@lilypond[quote,verbatim,relative=2]
+\time 3/4
+% by default we beam in (3) due to beamExceptions
+\repeat unfold 6 {a8} |
+% This will beam (1 1 1) due to beatLength
+\set Timing.beamExceptions = #'()
+\repeat unfold 6 {a8}
+@end lilypond
+
+@i{@strong{How automatic beaming works}}
+
+When automatic beaming is enabled, the placement of automatic beams
+is determined by the context properties
+@code{baseMoment}, @code{beatStructure}, and @code{beamExceptions}.
+
+The following rules, in order of priority, apply when determining
+the appearance of beams:
+
+@itemize
+@item
+If a manual beam is specified with @code{[..]} set the beam
+as specified, otherwise
+
+@item
+if a beam-ending rule is defined in @code{beamExceptions}
+for the beam-type, use it to determine the valid places where
+beams may end, otherwise
+
+@item
+if a beam-ending rule is defined in @code{beamExceptions}
+for a longer beam-type, use it to determined the valid places
+where beams may end, otherwise
+
+@item
+use the values of @code{baseMoment} and @code{beatStructure} to
+determine the ends of the beats in the measure, and
+end beams at the end of beats.
+
+@end itemize
+
+In the rules above, the @emph{beam-type} is the duration of the
+shortest note in the beamed group.
+
+The default beaming rules can be found in
+@file{scm/time-signature-settings.scm}.
@snippets
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{conducting-signs,-measure-grouping-signs.ly}
-@cindex beam, last in score
-@cindex beam, last in polyphonic voice
+@cindex beam, endings in a score
+@cindex beam, endings with multiple voices
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{beam-endings-in-score-context.ly}
@seealso
-Installed files:
+Installed Files:
@file{scm/beam-settings.scm}.
Snippets:
@knownissues
-
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 for polyphonic voices, entered with @code{<<
-@dots{} \\ @dots{} >>}. If a polyphonic voice ends while an
+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.
The workaround for these problems is to manually beam the last
beam in the voice or score.
+By default, the @code{Timing} translator is aliased to the
+@code{Score} context. This means that setting the time signature
+in one staff will affect the beaming of the other staves as well.
+Thus, a time signature setting in a later staff will reset custom
+beaming that was set in an earlier staff.
+One way to avoid this problem is to set the time signature
+in only one staff.
+
+@lilypond[quote,verbatim,relative=2]
+<<
+ \new Staff {
+ \time 3/4
+ \set Timing.baseMoment = #(ly:make-moment 1 8)
+ \set Timing.beatStructure = #'(1 5)
+ \repeat unfold 6 { a8 }
+ }
+ \new Staff {
+ \repeat unfold 6 { a8 }
+ }
+>>
+@end lilypond
+
+The default beam settings for the time signature can also be changed, so
+that the desired beaming will always be used. Changes in automatic
+beaming settings for a time signature are described in
+@ref{Time signature}.
+
+@lilypond[quote,verbatim,relative=2]
+<<
+ \new Staff {
+ \overrideTimeSignatureSettings
+ #'(3 . 4) % timeSignatureFraction
+ #'(1 . 8) % baseMomentFraction
+ #'(1 5) % beatStructure
+ #'() % beamExceptions
+ \time 3/4
+ \repeat unfold 6 { a8 }
+ }
+ \new Staff {
+ \time 3/4
+ \repeat unfold 6 { a8 }
+ }
+>>
+@end lilypond
+
@node Manual beams
@unnumberedsubsubsec Manual beams
marking the begin and end point with @code{[} and @code{]}.
@lilypond[quote,relative=1,verbatim]
-r4 r8[ g' a r8] r8 g[ | a] r8
+r4 r8[ g' a r] r g[ | a] r
@end lilypond
@cindex manual beams, direction shorthand for
@lilypond[quote,verbatim,relative=2]
c4 d8[
\grace { e32[ d c d] }
-e8] e8[ e
+e8] e[ e
\grace { f16 }
e8 e]
@end lilypond
direction to the @code{Beam} property @code{grow-direction}.
If the placement of the notes and the sound in the MIDI output is to
-reflect the ritardando or accelerando indicated by the feathered beam
-the notes must be grouped as a music expression delimited by braces
-and preceded by a @code{featherDurations} command which specifies
+reflect the @emph{ritardando} or @emph{accelerando} indicated by the
+feathered beam the notes must be grouped as a music expression delimited
+by braces and preceded by a @code{featherDurations} command which specifies
the ratio between the durations of the first and last notes in the
group.
a1 \bar ":|.|:"
b1 \bar ":|.:"
c1 \bar ":|"
-d1
+e1
@end lilypond
Additionally, a bar line can be printed as a simple tick:
@cindex collision, bar number
@knownissues
-
Bar numbers may collide with the top of the @code{StaffGroup} bracket,
if there is one. To solve this, the @code{padding} property of
@code{BarNumber} can be used to position the number correctly. See
@lilypond[quote,verbatim]
pipeSymbol = \bar "||"
{
- c'2 c'2 |
- c'2 c'2
- c'2 | c'2
- c'2 c'2
+ c'2 c' |
+ c'2 c'
+ c'2 | c'
+ c'2 c'
}
@end lilypond
c1
@end lilypond
-The file @file{scm/@/translation@/-functions@/.scm} contains the
+The file @file{scm/translation-functions.scm} contains the
definitions of @code{format-mark-numbers} (the default format),
@code{format-mark-box-numbers}, @code{format-mark-letters} and
@code{format-mark-box-letters}. These can be used as inspiration
@ref{Aligning objects}.
Installed Files:
-@file{scm/@/translation@/-functions@/.scm} contains
+@file{scm/translation-functions.scm} contains
the definitions of @code{format-mark-numbers} and
@code{format-mark-letters}. They can be used as inspiration for
other formatting functions.
@ref{Manual beams}.
Installed Files:
-@file{ly/@/grace@/-init@/.ly}.
+@file{ly/grace-init.ly}.
Snippets:
@rlsr{Rhythms}.
>>
@end lilypond
-Grace sections should only be used within sequential music
-expressions. Nesting or juxtaposing grace sections is not
-supported, and might produce crashes or other errors.
+The use of grace notes within voice contexts confuses the way the voice
+is typeset. This can be overcome by inserting a rest or note between the
+voice command and the grace note.
+
+@lilypond[quote,verbatim]
+accMusic = {
+ \acciaccatura { f8 } e8 r8 \acciaccatura { f8 } e8 r4
+}
+
+\new Staff {
+ <<
+ \new Voice {
+ \relative c'' {
+ r8 r8 \voiceOne \accMusic \oneVoice r8 |
+ r8 \voiceOne r8 \accMusic \oneVoice r8 |
+ }
+ }
+ \new Voice {
+ \relative c' {
+ s8 s8 \voiceTwo \accMusic \oneVoice s8 |
+ s8 \voiceTwo r8 \accMusic \oneVoice s8 |
+ }
+ }
+ >>
+}
+@end lilypond
+
+Grace sections should only be used within sequential music expressions.
+Nesting or juxtaposing grace sections is not supported, and might
+produce crashes or other errors.
+
+Each grace note in MIDI output has a length of 1/4 of its actual
+duration. If the combined length of the grace notes is greater than the
+length of the preceding note a @qq{@code{Going back in MIDI time}}
+error will be generated. Either make the grace notes shorter in
+duration, for example:
+
+@example
+\acciaccatura @{ c'8[ d' e' f' g'] @}
+@end example
+
+becomes:
+
+@example
+\acciaccatura @{ c'16[ d' e' f' g'] @}
+@end example
+
+Or explicitly change the musical duration:
+
+@example
+\acciaccatura @{ \scaleDurations #' (1 . 2) @{ c'8[ d' e' f' g'] @} @}
+@end example
+
+See @ref{Scaling durations}.
+
@node Aligning to cadenzas
@unnumberedsubsubsec Aligning to cadenzas
projects / lilypond.git / blobdiff