@c \version "2.11.61"
-@ignore
-GDP TODO list
-
-1.2.3.1 Time signature
-Needs an example of beatLength, which is broken (see my recent
-mail
-to -bug). What to do? For now I've left a paragraph of text
-which really
-needs to be inserted with an example in a snippet.
-
-1.2.3.4 Polymetric notation
-Quite extensive changes. Could you please check through. Divided
-into three
-sections. Necessarily uses tweaks. I've also left an @lsr under
-@seealso
-Snippets - is this permitted or is @lsr now verboten? This
-snippet is too
-long to include, but seems relevant.
-A snippet "grouping beats" hasn't yet appeared (only sent to vv a
-couple of
-days ago). Text left in Snippets: with TODO.
-@end ignore
-
@node Rhythms
@section Rhythms
are possible, but only as beamed notes.
@c Two 64th notes are needed to obtain beams
-@lilypond[quote,ragged-right,verbatim,fragment,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 8/1
c\longa c\breve c1 c2
c4 c8 c16 c32 c64 c64
@c not strictly "writing rhythms"; more of a "displaying" thing,
@c but it's ok here. -gp
-@lilypond[quote,ragged-right,verbatim,fragment,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 8/1
\autoBeamOff
c\longa c\breve c1 c2
entered duration. The default for the first note is a quarter
note.
-@lilypond[quote,ragged-right,verbatim,fragment,relative=2]
+@lilypond[quote,verbatim,relative=2]
a a a2 a a4 a a1 a
@end lilypond
duration. Double-dotted notes are specified by appending two
dots, and so on.
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
a4 b c4. b8 a4. b4.. c8.
@end lilypond
tuplet is the triplet in which 3 notes have the duration of 2, so
the notes are 2/3 of their written length.
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
a2 \times 2/3 { b4 b b }
c4 c \times 2/3 { b4 a g }
@end lilypond
Tuplets may be nested:
-@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\autoBeamOff
c4 \times 4/5 { f8 e f \times 2/3 { e[ f g] } } f4 |
@end lilypond
In the following example, the first three notes take up exactly
two beats, but no triplet bracket is printed.
-@lilypond[quote,ragged-right,fragment,relative=2,verbatim]
+@lilypond[quote,relative=2,verbatim]
\time 2/4
% Alter durations to triplets
a4*2/3 gis4*2/3 a4*2/3
required. Here is an example showing how music can be compressed
and expanded:
-@lilypond[quote,fragment,relative=2,ragged-right,verbatim]
+@lilypond[quote,relative=2,verbatim]
\time 2/4
% Normal durations
<c a>4 c8 a
A tie is entered using the tilde symbol @code{~}
-@lilypond[quote,ragged-right,fragment,verbatim]
-e'2 ~ e'
+@lilypond[quote,verbatim,relative=2]
+a2 ~ a
@end lilypond
dots cannot be used to denote the rhythm. Ties should also be
used when note values cross larger subdivisions of the measure:
-@lilypond[fragment,quote,ragged-right]
+@lilypond[verbatim,quote]
\relative c' {
r8 c8 ~ c2 r4 |
r8^"not" c2 ~ c8 r4
created. Chords may be partially tied by placing the tie inside
the chord.
-@lilypond[quote,ragged-right,fragment,verbatim,relative=1]
+@lilypond[quote,verbatim,relative=1]
<c e g> ~ <c e g>
<c~ e g~ b> <c e g b>
@end lilypond
When a second alternative of a repeat starts with a tied note, you
have to specify the repeated tie as follows:
-@lilypond[fragment,quote,ragged-right,relative=2,verbatim]
+@lilypond[quote,relative=2,verbatim]
\repeat volta 2 { c g <c e>2 ~ }
\alternative {
% First alternative: following note is tied normally
piano, harp and other string and percussion instruments. They can
be entered as follows:
-@lilypond[fragment,quote,ragged-right,verbatim,relative=1]
+@lilypond[quote,verbatim,relative=1]
<c f g>1\laissezVibrer
@end lilypond
@c \time 16/1 is used to avoid spurious bar lines
@c and long tracts of empty measures
-@lilypond[fragment,quote,ragged-right,verbatim]
+@lilypond[fragment,quote,verbatim]
\new Staff {
% These two lines are just to prettify this example
\time 16/1
allows for precise manual formatting of polyphonic music, since the
automatic rest collision formatter will not move these rests.
-@lilypond[fragment,quote,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
a4\rest d4\rest
@end lilypond
is used to skip a musical moment. @code{\skip} requires an
explicit duration.
-@lilypond[quote,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
<<
{
a2 \skip2 a2 a2
Rests for one or more full measures are entered like notes with
the note name uppercase @code{R}:
-@lilypond[quote,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
% Rest measures contracted to single measure
\compressFullBarRests
R1*4
integral number of measure-lengths, so augmentation
dots or fractions must often be used:
-@lilypond[quote,ragged-right,fragment,verbatim]
+@lilypond[quote,fragment,verbatim]
\compressFullBarRests
\time 2/4
R1 | R2 |
or breve rest, centered in the measure, depending on the time
signature.
-@lilypond[quote,ragged-right,fragment,verbatim]
+@lilypond[quote,verbatim,fragment]
\time 4/4
R1 |
\time 6/4
containing a multi-measure rest symbol, with the number of measures of rest
printed above the measure:
-@lilypond[quote,ragged-right,fragment,verbatim]
+@lilypond[quote,fragment,verbatim]
% Default behavior
\time 3/4 r2. | R2.*2 |
\time 2/4 R2 |
The predefined command @code{\fermataMarkup}
is provided for adding fermatas.
-@lilypond[quote,ragged-right,verbatim,fragment]
+@lilypond[quote,verbatim,fragment]
\compressFullBarRests
\time 3/4
R2.*10^\markup { \italic "ad lib." }
object, or they will be ignored. See the following example.
}
-@lilypond[quote,ragged-right,verbatim,fragment]
+@lilypond[quote,verbatim,fragment]
% This fails, as the wrong object name is specified
\override TextScript #'padding = #5
R1^"wrong"
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{positioning-multi--measure-rests.ly}
-@c TODO -- convert to snippet -- submitted to Neil
-Markups attached to a multi-measure rest will be centered above or
-below it. Long markups attached to multi-measure rests do not cause
-the measure to expand. To expand a multi-measure rest to fit the markup,
-use a spacer rest with an attached markup before the multi-measure rest:
-
-@lilypond[quote,ragged-right,verbatim,fragment,relative=2]
-\compressFullBarRests
-\textLengthOn
-s1*0^\markup { [MAJOR GENERAL] }
-R1*19
-s1*0_\markup { \italic { Cue: ... it is yours } }
-s1*0^\markup { A }
-R1*30^\markup { [MABEL] }
-\textLengthOff
-c4^\markup { CHORUS } d f c
-@end lilypond
-
-@noindent
-Note that the spacer rest causes a bar to be inserted.
-Text attached to a spacer rest in this way is left-aligned to the
-position where the note would be placed in the measure, but if the
-measure length is determined by the length of the text, the text will
-appear to be centered.
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{multi--measure-rest-markup.ly}
@seealso
The time signature is set as follows:
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 2/4 c2
\time 3/4 c2.
@end lilypond
there. This default behavior may be changed, see
@ref{Visibility of objects}.
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 2/4
c2 c
\break
The time signature symbol that is used in 2/2 and 4/4 time can be
changed to a numeric style:
-@lilypond[fragment,quote,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
% Default style
\time 4/4 c1
\time 2/2 c1
@snippets
-@c TODO Send as snippet called "setting measure and beat lengths"
-@c when example is added
-@code{\time} sets the properties @code{timeSignatureFraction},
-@code{beatLength}, and @code{measureLength} in the @code{Timing}
-context, which is normally aliased to @code{Score}. Changing the
-value of @code{timeSignatureFraction} causes the new time
-signature symbol to be printed without changing the other
-properties. The property @code{measureLength} determines where
-bar lines should be inserted and, with @code{beatLength}, how
-automatic beams should be generated.
-
-TODO Add example of using beatLength.
-@c beatLength is broken - see bug 511
-
-@c End of snippet
-
-@cindex measure groupings
-@cindex beats, grouping
-@cindex grouping beats
-@cindex measure sub-grouping
-
-@c TODO Sent as snippet called "grouping beats" 25 Mar 08
-Options to group beats within a bar are available through the
-Scheme function @code{set-time-signature}, which takes three
-arguments: the number of beats, the beat length, and the internal
-grouping of beats in the measure. If the
-@rinternals{Measure_grouping_engraver} is included, the function
-will also create @rinternals{MeasureGrouping} signs. Such signs
-ease reading rhythmically complex modern music. In the example,
-the 9/8 measure is subdivided in 2, 2, 2 and 3. This is passed to
-@code{set-time-signature} as the third argument: @code{'(2 2 2 3)}:
-
-@lilypond[quote,ragged-right,verbatim]
-\score {
- \relative c'' {
- #(set-time-signature 9 8 '(2 2 2 3))
- g8[ g] d[ d] g[ g] a8[( bes g]) |
- #(set-time-signature 5 8 '(3 2))
- a4. g4
- }
- \layout {
- \context {
- \Staff
- \consists "Measure_grouping_engraver"
- }
- }
-}
-@end lilypond
-@c TODO End of snippet called "grouping beats"
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{changing-the-time-signature-without-affecting-the-beaming.ly}
@cindex compound time signatures
@cindex time signature, compound
@rinternals{Timing_translator}.
-@knownissues
-
-Automatic beaming does not use the measure grouping specified with
-@code{set-time-signature}.
-
-
@node Upbeats
@unnumberedsubsubsec Upbeats
entered using the @code{\partial} command, with the syntax
@example
-\partial @var{duration}
+\partial @var{duration}
@end example
where @code{duration} is the rhythmic length of the interval
before the start of the first complete measure:
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\partial 4 e4 |
a2. c,4 |
@end lilypond
The partial measure can be any duration less than a full measure:
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\partial 8*3 c8 d e |
a2. c,4 |
@end lilypond
@seealso
-Music Glossary: @rglos{anacrusis}
+Music Glossary:
+@rglos{anacrusis}.
-Notation Reference: @ref{Grace notes}
+Notation Reference:
+@ref{Grace notes}.
Snippets:
@rlsr{Rhythms}.
Internal Reference:
-@rinternals{Timing_translator}
+@rinternals{Timing_translator}.
@knownissues
-@cindex grace notes, in anacruses
-
The @code{\partial} command is intended to be used only at the
beginning of a piece. If you use it after the beginning, some
odd warnings may occur.
Bar lines and bar numbers are calculated automatically. For
unmetered music (some cadenzas, for example), this is not desirable.
To turn off automatic calculation of bar lines and bar numbers,
-use the command @code{\cadenzaOn}, and use @code{\cadenzaOff}
+use the command @code{\cadenzaOn}, and use @code{\cadenzaOff}
to turn them on again.
-@lilypond[verbatim,quote,ragged-right,relative=2,fragment]
+@lilypond[verbatim,relative=2,fragment]
c4 d e d
\cadenzaOn
c4 c d8 d d f4 g4.
Bar numbering is resumed at the end of the cadenza as if the
cadenza were not there:
-@lilypond[verbatim,quote,ragged-right,relative=2,fragment]
+@lilypond[verbatim,relative=2,fragment]
% Show all bar numbers
\override Score.BarNumber #'break-visibility = #all-visible
c4 d e d
@seealso
Music Glossary:
-@rglos{cadenza}
+@rglos{cadenza}.
Notation Reference:
-@ref{Visibility of objects}
+@c ref{Controlling visibility of objects}.
Snippets:
@rlsr{Rhythms}.
@node Polymetric notation
@unnumberedsubsubsec Polymetric notation
+@c This section necessarily uses \set
+@c This is acceptable -td
+
@cindex double time signatures
@cindex signatures, polymetric
@cindex polymetric signatures
@cindex meter, polymetric
-Polymetric notation is supported, either explicitly or through
-clever use of markup features.
+Polymetric notation is supported, either explicitly or by modifying
+the visible time signature symbol and scaling the note durations.
-@strong{Staves with different time signatures, equal measure lengths}
+@strong{@i{Staves with different time signatures, equal measure lengths}}
This notation can be created by setting a common time signature
for each staff but replacing the symbol manually by setting
@code{timeSignatureFraction} to the desired fraction and scaling
the printed durations in each staff to the common time
-signature. This is done with @code{\scaleDurations}, which
-is used in a similar way to @code{\times}, but does not create
-a tuplet bracket, see @ref{Scaling durations}.
+signature; see @ref{Time signature}. The scaling is done with
+@code{\scaleDurations}, which is used in a similar way to
+@code{\times}, but does not create a tuplet bracket; see
+@ref{Scaling durations}.
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
are multiplied by 2/3, as 2/3 * 9/8 = 3/4, and in the third
staff, shown durations are multiplied by 3/5, as 3/5 * 10/8 = 3/4.
+It will often be necessary to insert beams manually, as the
+duration scaling affects the autobeaming rules.
-@lilypond[quote,ragged-right,verbatim,fragment]
-\relative c' { <<
+@lilypond[quote,verbatim,fragment]
+\relative c' <<
\new Staff {
\time 3/4
c4 c c |
\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
\scaleDurations #'(3 . 5) {
\repeat unfold 2 { c8[ c c] }
\repeat unfold 2 { c8[ c] } |
- c4. c4. \times 2/3 { c8 c c } c4
+ c4. c4. \times 2/3 { c8[ c c] } c4
}
}
->> }
+>>
@end lilypond
-@strong{Staves with different time signatures, unequal bar lengths}
+@strong{@i{Staves with different time signatures, unequal bar lengths}}
Each staff can be given its own independent time signature by
-moving the @code{Timing_translator} to the @code{Staff} context.
+moving the @code{Timing_translator} and the
+@code{Default_bar_line_engraver} to the @code{Staff} context.
-@lilypond[quote,verbatim,ragged-right]
+@lilypond[quote,verbatim]
\layout {
\context {
\Score
@snippets
-@c TODO -- Convert to snippet. -- Sent to Neil 8/14/08
-
-@strong{Alternating time signatures}
-
-Regularly alternating double time signatures are not supported
-explicitly, but they can be faked. In the next example, the
-double time signature is created with markup text, while the
-real time signature is set in the usual way with @code{\time}.
-
-@lilypond[verbatim,ragged-right]
-% Create 9/8 split into 2/4 + 5/8
-tsMarkup = \markup {
- \override #'(baseline-skip . 2) \number {
- \column { "2" "4" }
- \vcenter "+"
- \bracket \column { "5" "8" }
- }
-}
-
-{
- \override Staff.TimeSignature #'stencil =
- #ly:text-interface::print
- \override Staff.TimeSignature #'text = #tsMarkup
- \time 9/8
- c'2 \bar ":" c'4 c'4.
- c'2 \bar ":" c'4 c'4.
-}
-@end lilypond
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{compound-time-signatures.ly}
@seealso
@rglos{polymetric time signature},
@rglos{meter}.
-Notation Reference: @ref{Scaling durations}
+Notation Reference:
+@ref{Time signature},
+@ref{Scaling durations}.
Snippets:
@rlsr{Rhythms}.
-@c Is this still permitted?
-@c @lsr{contemporary,compound-time-signature}
Internals Reference:
@rinternals{TimeSignature},
@rinternals{Timing_translator},
+@rinternals{Default_bar_line_engraver},
@rinternals{Staff}.
@knownissues
@code{Completion_heads_engraver}. In the following
example, notes crossing the bar lines are split and tied.
-@lilypond[quote,fragment,verbatim,relative=1,ragged-right]
+@lilypond[quote,verbatim,relative=1]
\new Voice \with {
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
@knownissues
Not all durations (especially those containing tuplets) can be
-represented exactly with normal notes and dots, but the
+represented exactly with normal notes and dots, but the
@code{Completion_heads_engraver} will not insert tuplets.
The @code{Completion_heads_engraver} only affects notes; it does not
can be done with the rhythmic staff. All pitches of notes on such a
staff are squashed, and the staff itself has a single line
-@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
+@lilypond[quote,relative=1,verbatim]
<<
\new RhythmicStaff {
\new Voice = "myRhythm" {
be done with the @code{Pitch_squash_engraver} and
@code{\improvisationOn}.
-
+
@lilypond[quote,verbatim]
<<
\new ChordNames {
@code{\improvisationOff}.
@snippets
-@c TODO -- Convert to snippet;
-@c tag for both Rhythms and Guitar? Move to @seealso?
-
-For guitar music, it is possible to show strum rhythms, along
-with melody notes, chord names, and fret diagrams.
-
-
-@lilypond[quote,verbatim]
-\include "predefined-guitar-fretboards.ly"
-<<
- \new ChordNames {
- \chordmode {
- c1 f g c
- }
- }
-
- \new FretBoards {
- \chordmode {
- c1 f g c
- }
- }
-
-
- \new Voice \with {
- \consists Pitch_squash_engraver
- } \relative c'' {
- \improvisationOn
- c4 c8 c c4 c8 c
- f4 f8 f f4 f8 f
- g4 g8 g g4 g8 g
- c4 c8 c c4 c8 c
- }
-
- \new Voice = "melody" {
- \relative c'' {
- \improvisationOff
- c2 e4 e4
- f2. r4
- g2. a4
- e4 c2.
- }
- }
-
- \new Lyrics {
- \lyricsto "melody" {
- This is my song.
- I like to sing.
- }
- }
->>
-@end lilypond
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{guitar-strum-rhythms.ly}
@seealso
@cindex beams, manual
@cindex manual beams
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,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}.
+to define beaming patterns that differ from the defaults. The
+default beaming rules for most common time signatures are defined
+in @file{scm/@/auto@/-beam@/.scm}. If there are no beaming rules
+defined for a particular beam's duration in the time signature being
+used, its beaming is controlled by the values of three context
+properties, @code{measureLength}, @code{beatLength} and
+@code{beatGrouping}. Both the beaming rules and the context
+properties can be overridden, see @ref{Setting automatic beam behavior}.
@cindex autoBeamOn
@cindex autoBeamOff
+@warning{If beams are used to indicate melismata in songs, then automatic
+beaming should be switched off with @code{\autoBeamOff} and the beams
+indicated manually.}
+
+
@noindent
Automatic beaming may be turned off and on with
@code{\autoBeamOff} and @code{\autoBeamOn} commands:
-@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
+@lilypond[quote,relative=1,verbatim]
c4 c8 c8. c16 c8. c16 c8
\autoBeamOff
c4 c8 c8. c16 c8.
@snippets
-@c TODO -- convert to snippet
-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 convert to snippet
-The beams of consecutive 16th (or shorter) notes are, by default,
-not sub-divided. That is, the three (or more) beams stretch
-unbroken over entire groups of notes. This behavior can
-be modified to sub-divide the beams into sub-groups by setting
-the property @code{subdivideBeams}. When set, multiple beams
-will be sub-divided at intervals defined by the current value of
-@code{beatLength} by reducing the multiple beams to just one beam
-between the sub-groups. Note that @code{beatLength} lives in the
-@code{Score} context and defaults to a quarter note. It must be
-set to a fraction giving the duration of the beam sub-group
-using the @code{make-moment} function, as shown here:
-
-@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 beam sub-group length to an eighth note
-\set Score.beatLength = #(ly:make-moment 1 8)
-c32[ c c c c c c c]
-% Set beam sub-group length to a sixteenth note
-\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
-@c TODO convert to snippet
-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
-
-@c TODO convert to snippet
-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
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{beams-across-line-breaks.ly}
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{changing-beam-knee-gap.ly}
@seealso
-Notation Reference:
-@ref{Manual beams},
+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}.
@node Setting automatic beam behavior
@unnumberedsubsubsec Setting automatic beam behavior
+@funindex autoBeaming
@funindex autoBeamSettings
@funindex (end * * * *)
@funindex (begin * * * *)
+
@cindex automatic beams, tuning
@cindex tuning automatic beaming
+@cindex automatic beam generation
+@cindex autobeam
+@cindex lyrics and beaming
+
+
+The placement of automatic beams is determined by the rules
+described in @ref{Automatic beams}. There are two mutually
+exclusive ways in which these rules may be modified. The
+first, modifying the grouping of beats, applies to uncommon time
+signatures, i.e. those for which there are no predefined rules
+defining the beam end points. The second method, modifying the
+specification of the beam end points, can be used for any time
+signature. This second method @strong{must} be used for those time
+signatures and beam durations combinations for which beam ending
+rules are pre-defined, unless these have all been reverted. There
+are predefined rules for time signatures of 3/2, 3/4, 4/4, 2/4,
+4/8, 4/16, 6/8, 9/8 and 12/8.
+
+@i{@strong{Modifying the grouping of beats}}
+
+If there are no beam-ending rules defined for the beam duration of a
+particular beam in the time signature in use, its beaming is
+controlled by three context properties:
+@code{measureLength}, @code{beatLength} and @code{beatGrouping}.
+These properties may be set in the @code{Score}, @code{Staff} or
+@code{Voice} contexts to delimit their scope.
+
+These determine the beaming as follows:
+
+Beams may begin anywhere (unless a beam is already active). Beams
+end at a time determined by the values of @code{beatGrouping} and
+@code{beatLength}, as follows:
+
+@itemize
+
+@item If @code{beatGrouping} and @code{beatLength} are consistent
+with @code{measureLength}, @code{beatGrouping} is used to determine
+the end points of beams.
+
+@item If @code{beatGrouping} and @code{beatLength} are inconsistent
+with @code{measureLength}, @code{beatLength} is used to determine
+the end points of beams.
+
+@end itemize
+
+@warning{These three properties become effective for a particular
+beam @strong{only} if there are no beam-ending rules predefined for
+that beam's duration in the time signature in use, or if these
+beam-ending rules have all been reverted.}
+
+By default the @code{measureLength} and @code{beatLength} are
+derived from the time signature set by the @code{\time} command.
+The @code{measureLength} is set to be exactly the same length as
+the measure length given by the time signature, and the
+@code{beatLength} is set to be the same as one over the denominator
+of the time signature.
+
+The default value of @code{beatGrouping} is taken from a table in
+@file{scm/@/music@/-functions@/.scm}. To find this, see
+@rlearning{Other sources of information}. It defines the beat
+grouping for 5/8, 6/8, 8/8, 9/8 and 12/8 time signatures.
+
+Both @code{measureLength} and @code{beatLength} are @i{moments},
+units 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}.
+
+@code{beatGrouping} is a list of integers giving the number of
+beats in each group.
-@c [TODO: use \applyContext]
+@snippets
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{grouping-beats.ly}
-In normal time signatures, automatic beams can start on any note
-but can end in only a few positions within the measure: beams can
-end on a beat, or at durations specified by the properties in
-@code{autoBeamSettings}. The properties in
-@code{autoBeamSettings} consist of a list of rules for where beams
-can begin and end. The default @code{autoBeamSettings} rules are
-defined in @file{scm/@/auto@/-beam@/.scm}.
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{specifying-context-with-beatgrouping.ly}
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{using-beatlength-and-beatgrouping.ly}
+
+@funindex subdivideBeams
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{sub-dividing-beams.ly}
+
+@cindex measure groupings
+@cindex beats, grouping
+@cindex grouping beats
+@cindex measure sub-grouping
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{conducting-signs,-measure-grouping-signs.ly}
+
+
+@strong{@i{Modifying the beam end points}}
+
+In common time signatures, automatic beams can start on any note
+but can end at only a few positions within the measure, namely at
+durations specified by the properties in @code{autoBeamSettings}.
+These properties consist of a list of rules defining where beams can
+end. The default @code{autoBeamSettings} rules are defined in
+@file{scm/@/auto@/-beam@/.scm}. To find this, see
+@rlearning{Other sources of information}.
+
+This method @strong{must} be used for the time signatures for which
+beam-ending rules are defined by default, unless these have all
+been reverted. It is also particularly suitable for many other time
+signatures if the time signature of the measures changes frequently,
+or if the beaming should be different for different beam durations.
In order to add a rule to the list, use
+
@example
-#(override-auto-beam-setting
- '(beam-limit beam-numerator beam-denominator
- time-signature-numerator time-signature-denominator)
+#(override-auto-beam-setting
+ '(beam-limit
+ beam-numerator beam-denominator
+ time-signature-numerator time-signature-denominator)
moment-numerator moment-denominator [context])
@end example
+@noindent
+where
+
@itemize
@item @code{beam-limit} is the type of automatic beam limit
-defined, either @code{begin} or @code{end}.
+defined. This can be either @code{begin} or @code{end} but
+only @code{end} is effective.
@item @code{beam-numerator/beam-denominator} is the beam duration
-for which you want to add a rule. A beam is considered to have
-the duration of its shortest note. Set @code{beam-numerator} and
-@code{beam-denominator} to @code{'*'} to
-have this rule apply beams of any duration.
+to which the rule is to apply. A beam is considered to have
+the duration of its shortest note. Set @code{beam-numerator}
+and @code{beam-denominator} to @code{'*'} to have this rule apply
+to beams of any duration.
@item @code{time-signature-numerator/time-signature-denominator}
-is the time signature to which
-this rule should apply. Set @code{time-signature-numerator} and
-@code{time-signature-denominator} to @code{'*'}
-to have this rule apply in any time signature.
+specifies the time signature to which this rule should apply.
+If @code{time-signature-numerator} and
+@code{time-signature-denominator} are set to @code{'*'} this rule
+will apply in any time signature.
-@item @code{monent-numerator/moment-denominator} is the position
-in the bar at which the beam should
-begin or end.
+@item @code{monent-numerator/moment-denominator} is the position
+in the bar at which the beam should end.
@item @code{context} is optional, and it specifies the context at which
the change should be made. The default is @code{'Voice}.
@end itemize
-TODO -- convert to music example
For example, if automatic beams should always end on the first quarter
-note, use
+note, whatever the time signature or beam duration, use
-@example
+@lilypond[quote,verbatim,relative=2]
+a8 a a a a a a a
#(override-auto-beam-setting '(end * * * *) 1 4)
-@end example
+a8 a a a a a a a
+@end lilypond
-You can force the beam settings to only take effect on beams whose shortest
+You can force the beam settings to take effect only on beams whose shortest
note is a certain duration
-@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 2/4
% end 1/16 beams for all time signatures at the 1/16 moment
#(override-auto-beam-setting '(end 1 16 * *) 1 16)
a32 a a a a16 a a a a a |
@end lilypond
-You can force the beam settings to only take effect in certain time
+You can force the beam settings to take effect only in certain time
signatures
-@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 5/8
% end beams of all durations in 5/8 time signature at the 2/8 moment
#(override-auto-beam-setting '(end * * 5 8) 2 8)
c8 c d d d
@end lilypond
-Existing auto-beam rules are removed by using
+When multiple voices are used the @code{Staff} context must be
+specified if the beaming is to be applied to all voices in the
+staff:
+
+@lilypond[quote,verbatim,relative=2]
+\time 7/8
+% rhythm 3-1-1-2
+% Context not specified - does not work correctly
+#(override-auto-beam-setting '(end * * 7 8) 3 8)
+#(override-auto-beam-setting '(end * * 7 8) 4 8)
+#(override-auto-beam-setting '(end * * 7 8) 5 8)
+<< {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>
+
+% Works correctly with context specified
+#(override-auto-beam-setting '(end * * 7 8) 3 8 'Staff)
+#(override-auto-beam-setting '(end * * 7 8) 4 8 'Staff)
+#(override-auto-beam-setting '(end * * 7 8) 5 8 'Staff)
+<< {a8 a a a16 a a a a8 a} \\ {f4. f8 f f f} >>
+@end lilypond
+
+@warning{If any unexpected beam behavior occurs, check the default
+automatic beam settings in @file{scm/@/auto@/-beam@/.scm} for
+possible interference, because the beam endings defined there will
+still apply in addition to your own.}
+
+Any unwanted or conflicting default endings must be reverted for
+your time signature(s). Existing auto-beam rules are removed by
+using
@example
-#(revert-auto-beam-setting
- '(beam-limit beam-numerator beam-denominator
- time-signature-numerator time-signature-denominator)
+#(revert-auto-beam-setting
+ '(beam-limit
+ beam-numerator beam-denominator
+ time-signature-numerator time-signature-denominator)
moment-numerator moment-denominator [context])
@end example
@noindent
-@code{beam-limit}, @code{beam-numerator}, @code{beam-denominator},
+@code{beam-limit}, @code{beam-numerator}, @code{beam-denominator},
@code{time-signature-numerator}, @code{time-signature-denominator},
@code{moment-numerator}, @code{moment-denominator} and @code{context}
-are the same as above. Note that the default auto-beaming rules are
-specified in @file{scm/@/auto@/-beam@/.scm},
-so you can revert rules that you did not explicitly create.
+are the same as above.
-@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 4/4
a16 a a a a a a a a a a a a a a a
% undo a rule ending 1/16 beams in 4/4 time at 1/4 moment
match the original rule. That is, no wildcard expansion is taken into
account.
-@lilypond[quote,fragment,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 1/4
#(override-auto-beam-setting '(end 1 16 1 4) 1 8)
a16 a a a
a a a a
@end lilypond
+@snippets
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{beam-grouping-in-7-8-time.ly}
-@c TODO: old material -- not covered by above stuff, I think.
-If automatic beams should end on every quarter in 5/4 time, specify
-all endings
-@example
-#(override-auto-beam-setting '(end * * * *) 1 4 'Staff)
-#(override-auto-beam-setting '(end * * * *) 1 2 'Staff)
-#(override-auto-beam-setting '(end * * * *) 3 4 'Staff)
-#(override-auto-beam-setting '(end * * * *) 5 4 'Staff)
-@dots{}
-@end example
-
-The same syntax can be used to specify beam starting points. In this
-example, automatic beams can only end on a dotted quarter note
-@example
-#(override-auto-beam-setting '(end * * * *) 3 8)
-#(override-auto-beam-setting '(end * * * *) 1 2)
-#(override-auto-beam-setting '(end * * * *) 7 8)
-@end example
-In 4/4 time signature, this means that automatic beams could end only on
-3/8 and on the fourth beat of the measure (after 3/4, that is 2 times
-3/8, has passed within the measure).
-
-If any unexpected beam behavior occurs, check the default automatic beam
-settings in @file{scm/@/auto@/-beam@/.scm}
-for possible interference, because the beam
-endings defined there will still apply on top of your own overrides. Any
-unwanted endings in the default vales must be reverted for your time
-signature(s).
-
-For example, to typeset @code{(3 4 3 2)}-beam endings in 12/8, begin
-with
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{reverting-default-beam-endings.ly}
-@example
-%%% revert default values in scm/auto-beam.scm regarding 12/8 time
-#(revert-auto-beam-setting '(end * * 12 8) 3 8)
-#(revert-auto-beam-setting '(end * * 12 8) 3 4)
-#(revert-auto-beam-setting '(end * * 12 8) 9 8)
-
-%%% your new values
-#(override-auto-beam-setting '(end 1 8 12 8) 3 8)
-#(override-auto-beam-setting '(end 1 8 12 8) 7 8)
-#(override-auto-beam-setting '(end 1 8 12 8) 10 8)
-@end example
+@c TODO Convert to snippet called "Beam endings in Score context"
+@c Submitted to LSR 3 Nov 08
-@cindex automatic beam generation
-@cindex autobeam
-@funindex autoBeaming
-@cindex lyrics
+Beam-ending rules specified in the Score context apply to all
+staves, but can be modified at both Staff and Voice levels:
-If beams are used to indicate melismata in songs, then automatic
-beaming should be switched off with @code{\autoBeamOff}.
+@lilypond[quote,verbatim,relative=2]
+ \time 5/4
+ % Set default beaming for all staves
+ #(override-auto-beam-setting '(end * * 5 4) 3 8 'Score)
+ #(override-auto-beam-setting '(end * * 5 4) 7 8 'Score)
+ <<
+ \new Staff {
+ c8 c c c c c c c c c
+ }
+ \new Staff {
+ % Modify beaming for just this staff
+ #(override-auto-beam-setting '(end * * 5 4) 6 8 'Staff)
+ #(revert-auto-beam-setting '(end * * 5 4) 7 8 'Staff)
+ c8 c c c c c c c c c
+ }
+ \new Staff {
+ % Inherit beaming from Score context
+ c8 c c c c c c c c c
+ }
+ >>
+@end lilypond
@predefined
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]
+@lilypond[quote,relative=1,verbatim]
{
r4 r8[ g' a r8] r8 g[ | a] r8
}
@end lilypond
-@funindex \noBeam
Individual notes may be marked with @code{\noBeam} to prevent them
from being beamed:
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\time 2/4 c8 c\noBeam c c
@end lilypond
with only one beam on the left side, i.e., the eighth-note beam of
the group as a whole.
-TODO -- no difference based on stemLeftBeamCount in this example
-@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
-{
- f8[ r16 f g a]
- f8[ r16
- \set stemLeftBeamCount = #1
- f g a]
-}
+@lilypond[quote,relative=2,verbatim]
+a8[ r16 f g a]
+a8[ r16
+\set stemLeftBeamCount = #2
+\set stemRightBeamCount = #1
+f
+\set stemLeftBeamCount = #1
+g a]
@end lilypond
@snippets
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{flat-flags-and-beam-nibs.ly}
+
@node Feathered beams
@unnumberedsubsubsec Feathered beams
@cindex beams, feathered
@funindex \featherDurations
-TODO -- this section relies on overrides. We need to either add
-a predefined, move this to snippets (whole section), or violate
-policy for this section.
-
Feathered beams are used to indicate that a small group of notes
should be played at an increasing (or decreasing) tempo, without
changing the overall tempo of the piece. The extent of the
these would delimit the same group of notes, but this is not
required: the two commands are independent.
-@c TODO -- eliminate "Talking through code"
-
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]
+@lilypond[relative=1,verbatim,quote]
\override Beam #'grow-direction = #LEFT
\featherDurations #(ly:make-moment 2 1)
{ c16[ c c c c c c c] }
@noindent
The spacing in the printed output represents the
-note durations only approximately, but the midi output is exact.
-
-@c TODO -- resolve whether or not midi is capitalized -- policy
-@c decision needed
+note durations only approximately, but the MIDI output is exact.
@knownissues
other types with the @code{\bar} command. For example, a closing
double bar line is usually placed at the end of a piece:
-@lilypond[quote,ragged-right,relative=1,fragment,verbatim]
+@lilypond[quote,relative=1,verbatim]
e4 d c2 \bar "|."
@end lilypond
-@c TODO -- make this warning more clear. What does it mean?
-@warning{An incorrect duration can lead to poorly formatted
-music.}
-
-@c TODO -- check this. I think this behavior no longer happens
-@c with completion_heads_engraver, but it may with note_heads_engraver
-@c Make an example showing the problem
-
It is not invalid if the final note in a measure does not
end on the automatically entered bar line: the note is assumed
to carry over into the next measure. But if a long sequence
of such carry-over measures appears the music can appear compressed
or even flowing off the page. This is because automatic line
breaks happen only at the end of complete measures, i.e., where
-the end of a note coincides with the end of a measure.
+all notes end before the end of a measure.
+
+@warning{An incorrect duration can cause line breaks to be
+inhibited, leading to a line of highly compressed music or
+music which flows off the page.}
@cindex line breaks
@cindex bar lines, invisible
The simple bar line and five types of double bar line are available
for manual insertion:
-@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
+@lilypond[quote,relative=1,verbatim]
f1 \bar "|" g \bar "||" a \bar ".|" b \bar ".|." c \bar "|.|" d \bar "|." e
@end lilypond
@noindent
together with dotted and dashed bar lines:
-@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
+@lilypond[quote,relative=1,verbatim]
f1 \bar ":" g \bar "dashed" a
@end lilypond
@noindent
and five types of repeat bar line:
-@lilypond[quote,ragged-right,fragment,relative=1,verbatim]
+@lilypond[quote,relative=1,verbatim]
f1 \bar "|:" g \bar ":|:" a \bar ":|.|:" b \bar ":|.:" c \bar ":|" d
@end lilypond
line at the end of the line and a start repeat at the beginning of
the next line.
-@lilypond[quote,ragged-right,relative=2,fragment,verbatim]
+@lilypond[quote,relative=2,verbatim]
\override Score.RehearsalMark #'padding = #3
c c c c
\bar "||:"
connected between different staves of a @code{StaffGroup},
@code{InnerStaffGroup}, @code{PianoStaff}, or @code{GrandStaff}.
-@lilypond[quote,ragged-right,fragment,verbatim]
+@lilypond[quote,fragment,verbatim]
<<
\new StaffGroup <<
\new Staff {
@seealso
-Notation Reference: @ref{Line breaking}, @ref{Repeats},
-@c FIXME: node name changed, but is subject to further changes.
-@c @ref{System start delimiters}.
+Notation Reference:
+@ref{Line breaking},
+@ref{Repeats},
+@ref{Grouping staves}.
Snippets:
@rlsr{Rhythms}.
@code{currentBarNumber} property, which is normally updated
automatically for every measure. It may also be set manually:
-@lilypond[verbatim,ragged-right,quote,fragment,relative]
+@lilypond[verbatim,quote,fragment,relative=1]
c1 c c c
\break
\set Score.currentBarNumber = #50
line visible}, @code{beginning of line visible}. In the following
example bar numbers are printed at all possible places:
-@lilypond[verbatim,ragged-right,quote,fragment,relative]
+@lilypond[verbatim,quote,relative=1]
\override Score.BarNumber #'break-visibility = #'#(#t #t #t)
\set Score.currentBarNumber = #11
\bar "" % Permit first bar number to be printed
and here the bar numbers are printed every two measures
except at the end of the line:
-@lilypond[verbatim,ragged-right,quote,fragment,relative]
+@lilypond[verbatim,quote,relative=1]
\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
\set Score.currentBarNumber = #11
\bar "" % Permit first bar number to be printed
numbers in boxes and circles, and shows an alternative way
of specifying @code{#(#f #t #t)} for @code{break-visibility}.
-@lilypond[verbatim,ragged-right,quote,fragment,relative]
+@lilypond[verbatim,quote,relative=1]
% Prevent bar numbers at the end of a line and permit them elsewhere
\override Score.BarNumber #'break-visibility
= #end-of-line-invisible
be positioned directly on the bar line or right-aligned to the
bar line:
-@lilypond[verbatim,ragged-right,quote,fragment,relative]
+@lilypond[verbatim,quote,relative=1]
\set Score.currentBarNumber = #111
\override Score.BarNumber #'break-visibility = #'#(#t #t #t)
% Increase the size of the bar number by 2
Bar numbers can be removed entirely by removing the
@code{Bar_number_engraver} from the @code{Score} context.
-@lilypond[verbatim,ragged-right,quote]
+@lilypond[verbatim,quote]
\layout {
\context {
\Score
inserted there, and a value other than @code{1} must be placed
in @code{currentBarNumber}:
-@lilypond[verbatim,ragged-right,quote,fragment,relative]
+@lilypond[verbatim,quote,relative=1]
\set Score.currentBarNumber = #50
\bar ""
c1 c c c
line wherever it appears in the input, rather than checking
for end of bar.
-@lilypond[quote,ragged-right,verbatim]
+@lilypond[quote,verbatim]
pipeSymbol = \bar "||"
{
c'2 c'2 |
To print a rehearsal mark, use the @code{\mark} command
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
c1 \mark \default
c1 \mark \default
c1 \mark #8
procedure. After a few measures, it is set to a procedure that
produces a boxed number.
-@lilypond[fragment,quote,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\set Score.markFormatter = #format-mark-numbers
c1 \mark \default
c1 \mark \default
\set Score.markFormatter = #format-mark-box-numbers
c1 \mark \default
+\set Score.markFormatter = #format-mark-circle-numbers
c1 \mark \default
+\set Score.markFormatter = #format-mark-circle-letters
c1
@end lilypond
Music glyphs (such as the segno sign) may be printed inside a
@code{\mark}
-@lilypond[fragment,quote,ragged-right,verbatim,relative]
+@lilypond[quote,verbatim,relative=1]
c1 \mark \markup { \musicglyph #"scripts.segno" }
c1 \mark \markup { \musicglyph #"scripts.coda" }
c1 \mark \markup { \musicglyph #"scripts.ufermata" }
@seealso
-This manual:
-@ref{The Feta font},
+Notation Reference:
+@ref{The Feta font},
@ref{Formatting text}.
-Installed Files:
+Installed Files:
@file{scm/@/translation@/-functions@/.scm} contains
the definition of @code{format-mark-numbers} and
@code{format-mark-letters}. They can be used as inspiration for
Internals Reference: @rinternals{RehearsalMark}.
-Examples: @c @lsr{parts,rehearsal-mark-numbers.ly}
-
@node Special rhythmic concerns
@subsection Special rhythmic concerns
@cindex acciaccatura
Grace notes are ornaments that are written out. Grace notes
-are printed in a smaller font and take up no logical time
+are printed in a smaller font and take up no logical time
in a measure.
-@lilypond[quote,ragged-right,relative=2,verbatim,fragment]
+@lilypond[quote,relative=2,verbatim]
c4 \grace c16 c4
\grace { c16[ d16] } c2
@end lilypond
-Lilypond also supports two special types of grace notes, the
-@emph{acciaccatura}--an unmeasured grace note indicated by a slurred
-small note with a slashed stem--and the @emph{appoggiatura}, which
-takes a fixed fraction of the main note and appears in small print
-without a slash.
+Lilypond also supports two special types of grace notes, the
+@emph{acciaccatura}--an unmeasured grace note indicated by a slurred
+small note with a slashed stem--and the @emph{appoggiatura}, which
+takes a fixed fraction of the main note and appears in small print
+without a slash.
-@lilypond[quote,ragged-right,relative=2,verbatim,fragment]
-\grace c8 b4
+@lilypond[quote,relative=2,verbatim]
+\grace c8 b4
\acciaccatura d8 c4
\appoggiatura e8 d4
\acciaccatura { g16[ f] } e4
staves. In the following example, there are two sixteenth grace
notes for every eighth grace note
-@lilypond[quote,ragged-right,relative=2,verbatim,fragment]
+@lilypond[quote,relative=2,verbatim]
<< \new Staff { e2 \grace { c16[ d e f] } e2 }
\new Staff { c2 \grace { g8[ b] } c2 } >>
@end lilypond
command. It takes two arguments: the main note, and the grace
notes following the main note.
-@lilypond[quote,ragged-right,verbatim,relative=2,fragment]
+@lilypond[quote,verbatim,relative=2]
c1 \afterGrace d1 { c16[ d] } c1
@end lilypond
This will put the grace notes after a space lasting 3/4 of the
length of the main note. The default fraction 3/4 can be changed by
setting @code{afterGraceFraction}. The following example shows
-the results from setting the space at the default, at 15/16, and
+the results from setting the space at the default, at 15/16, and
finally at 1/2 of the main note.
-@lilypond[quote,ragged-right,verbatim,relative=2,fragment]
+@lilypond[quote,verbatim,relative=2]
<<
\new Staff {
c1 \afterGrace d1 { c16[ d] } c1
specified using spacers. The following example places the grace
note after a space lasting 7/8 of the main note.
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\new Voice {
<< { d1^\trill_( }
{ s2 s4. \grace { c16[ d] } } >>
inside the grace expression. Here, the grace note's default stem
direction is overriden and then reverted.
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\new Voice {
\acciaccatura {
\stemDown
@snippets
-The slash through the stem found in @emph{acciaccatura}s can be applied
+The slash through the stem found in @emph{acciaccatura}s can be applied
in other situations:
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\relative c'' {
\override Stem #'stroke-style = #"grace"
c8( d2) e8( f4)
example undefines the @code{Stem} direction for this grace, so
that stems do not always point up.
-@lilypond[quote,ragged-right,fragment,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\relative c'' {
\new Staff {
#(add-grace-property 'Voice 'Stem 'direction ly:stem::calc-direction)
#(remove-grace-property 'Voice 'Stem 'direction)
\new Voice {
- \acciaccatura { f16 } g4
+ \acciaccatura { f16 } g4
\grace { d16[ e] } f4
\appoggiatura { a,32[ b c d] } e2
}
Grace notes may be forced to align with regular notes
in other staves:
-@lilypond[verbatim,quote,ragged-right]
+@lilypond[verbatim,quote]
\relative c'' {
<<
\override Score.SpacingSpanner #'strict-grace-spacing = ##t
@knownissues
-A multi-note beamed @emph{acciaccatura} is printed without a slash,
+A multi-note beamed @i{acciaccatura} is printed without a slash,
and looks exactly the same as a multi-note beamed
-@emph{appoggiatura}.
+@i{appoggiatura}.
+
@c TODO Add link to LSR snippet to add slash when available
Grace note synchronization can also lead to surprises. Staff
synchronized. Take care when you mix staves with grace notes and
staves without, for example,
-@lilypond[quote,ragged-right,relative=2,verbatim,fragment]
+@lilypond[quote,relative=2,verbatim]
<< \new Staff { e4 \bar "|:" \grace c16 d2. }
\new Staff { c4 \bar "|:" d2. } >>
@end lilypond
This can be remedied by inserting grace skips of the corresponding
durations in the other staves. For the above example
-@lilypond[quote,ragged-right,relative=2,verbatim,fragment]
+@lilypond[quote,relative=2,verbatim]
<< \new Staff { e4 \bar "|:" \grace c16 d2. }
\new Staff { c4 \bar "|:" \grace s16 d2. } >>
@end lilypond
-Predefined commands, like @code{\voiceOne}, which are intended to
-change the behaviour of the notation after a grace note, may not
-be effective if placed immediately before the grace note -- they
-should be placed after it.
-
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.
In an orchestral context, cadenzas present a special problem: when
constructing a score that includes a measured cadenza or other solo
-passage, all other instruments should skip just as many notes as the
-length of the cadenza, otherwise they will start too soon or too late.
+passage, all other instruments should skip just as many notes as the
+length of the cadenza, otherwise they will start too soon or too late.
One solution to this problem is to use the functions
@code{mmrest-of-length} and @code{skip-of-length}. These Scheme
-functions take a defined piece of music as an argument and generate a
-multi-measure rest or @code{\skip} exactly as long as the piece.
+functions take a defined piece of music as an argument and generate a
+multi-measure rest or @code{\skip} exactly as long as the piece.
-@lilypond[verbatim,ragged-right,quote]
+@lilypond[verbatim,quote]
MyCadenza = \relative c' {
- c4 d8 e f g g4
+ c4 d8 e f g g4
f2 g4 g
}
\new GrandStaff <<
- \new Staff {
- \MyCadenza c'1
+ \new Staff {
+ \MyCadenza c'1
\MyCadenza c'1
}
\new Staff {
advanced by 1/8 to 5/8, shortening that bar by 1/8.
The next bar line then falls at 9/8 rather than 5/4.
-@lilypond[quote,ragged-right,verbatim,relative,fragment]
+@lilypond[quote,verbatim,relative=1]
\set Score.measureLength = #(ly:make-moment 5 4)
c1 c4
c1 c4
projects / lilypond.git / blobdiff