version that you are working on. See TRANSLATION for details.
@end ignore
-@c \version "2.11.51"
-
@node Staff notation
@section Staff notation
-@lilypondfile[quote]{staff-headword.ly}
+@lilypondfile[quote,ragged-right,line-width=16\cm,staffsize=16]
+{staff-headword.ly}
+
+Notes, dynamic signs, rests, etc., are grouped with a set of horizontal
+lines, called a staff (plural @q{staves}). In LilyPond, these
+lines are drawn using a separate layout object called @code{staff
+symbol}.
+
+Two or more staves can be grouped vertically in a @code{GrandStaff}, a
+@code{StaffGroup}, or a @code{ChoirStaff}.
-This section explains how to influence the staff appearance, print
-scores with more than one staff, and how to apply specific
-performance marks to single staves.
@menu
-* Displaying staves::
-* Modifying single staves::
-* Writing parts::
+* Displaying staves::
+* Writing parts::
@end menu
@node Displaying staves
@subsection Displaying staves
-This section shows the different possibilities of creating and
-grouping staves, which are marked at the beginning of each line
-with either a bracket or a brace.
-
@menu
-* Instantiating new staves::
-* Grouping staves::
-* Deeper nested staff groups::
+* System start delimiters::
+* Staff symbol::
+* Hiding staves::
@end menu
-@node Instantiating new staves
-@unnumberedsubsubsec Instantiating new staves
-
-@cindex new staff
-@cindex staff initiation
-@cindex staff instantiation
-@cindex staff, new
-@cindex staff, single
-@cindex drum staff
-@cindex percussion staff
-@cindex Gregorian transcription staff
-@cindex rhythmic staff
-@cindex tabstaff
-@cindex tablature
-
-@notation{Staves} (singular: @notation{staff}) are created with
-the @code{\new} or @code{\context} commands. For details, see
-@ref{Creating contexts}.
-
-The basic staff context is @code{Staff}:
-
-@lilypond[verbatim,quote,relative=2]
-\new Staff { c4 d e f }
-@end lilypond
-
-@code{DrumStaff} creates a five-line staff set up for a
-typical drum set. It uses different names for each instrument.
-The instrument names are set using the @code{\drummode} command.
-For details, see @ref{Percussion staves}.
-
-@lilypond[verbatim,quote]
-\new DrumStaff {
- \drummode { cymc hh ss tomh }
-}
-@end lilypond
-
-@c FIXME: remove when mentioned in NR 2.8
-@code{GregorianTranscriptionStaff} creates a staff to notate
-modern Gregorian chant. It does not show bar lines.
-
-@lilypond[verbatim,quote,relative=2]
-\new GregorianTranscriptionStaff { c4 d e f }
-@end lilypond
-
-@code{RhythmicStaff} creates a single-line staff that only
-displays the rhythmic values of the input. Real durations are
-preserved. For details, see @ref{Showing melody rhythms}.
-
-@lilypond[verbatim,quote,relative=2]
-\new RhythmicStaff { c4 d e f }
-@end lilypond
-
-@code{TabStaff} creates a tablature with six strings in standard
-guitar tuning. For details, see @ref{Default tablatures}.
-
-@lilypond[verbatim,quote,relative=2]
-\new TabStaff { c4 d e f }
-@end lilypond
-
-There are two staff contexts specific for the notation of ancient
-music: @code{MensuralStaff} and @code{VaticanaStaff}. They are
-described in @ref{Pre-defined contexts}.
-
-Staves can be started or stopped at any point in the score. The
-commands @code{\startStaff} and @code{\stopStaff} are used for
-this purpose. For details, see @ref{Staff symbol}.
-
-
-@seealso
-
-Music Glossary:
-@rglos{staff},
-@rglos{staves}.
-
-Notation Reference:
-@ref{Creating contexts},
-@ref{Percussion staves},
-@ref{Default tablatures},
-@ref{Gregorian chant contexts},
-@ref{Mensural contexts},
-@ref{Staff symbol},
-@ref{Pre-defined contexts},
-@ref{Showing melody rhythms}.
-
-Snippets:
-@rlsr{Staff notation}.
-
-Internals Reference:
-@rinternals{Staff},
-@rinternals{DrumStaff},
-@rinternals{GregorianTranscriptionStaff},
-@rinternals{RhythmicStaff},
-@rinternals{TabStaff},
-@rinternals{MensuralStaff},
-@rinternals{VaticanaStaff},
-@rinternals{StaffSymbol}.
-
-
-@node Grouping staves
-@unnumberedsubsubsec Grouping staves
+@node System start delimiters
+@unnumberedsubsubsec System start delimiters
@cindex start of system
@cindex staff, multiple
-@cindex staves, multiple
-@cindex system start delimiters
+@cindex vertical bracket
@cindex bracket, vertical
@cindex brace, vertical
-@cindex choir staff
+@cindex vertical brace
@cindex grand staff
-@cindex piano staff
@cindex staff group
@cindex staff, choir
-@cindex staff, piano
@cindex system
-Various contexts exist to group single staves together in order to
-form multi-stave systems. Each grouping context sets the style of
-the system start delimiter and the behavior of bar lines.
+Many scores consist of more than one staff. These staves can be
+grouped in several different ways:
-If no context is specified, the default properties will be used:
-the group is started with a vertical line, and the bar lines are
-not connected.
+@itemize
+@item
+In a @code{GrandStaff}, the group is started with a brace
+at the left, and bar lines are connected between the staves.
-@lilypond[verbatim,quote,relative=2]
-<<
- \new Staff { c1 c }
+@lilypond[verbatim,ragged-right,quote]
+\new GrandStaff
+\relative <<
\new Staff { c1 c }
+ \new Staff { c c }
>>
@end lilypond
-In the @code{StaffGroup} context, the group is started with a
-bracket and bar lines are drawn through all the staves.
+@item
+In a @code{StaffGroup}, the bar lines will be drawn through
+all the staves, but the group is started with a bracket.
-@lilypond[verbatim,quote,relative=2]
-\new StaffGroup <<
- \new Staff { c1 c }
+@lilypond[verbatim,ragged-right,quote]
+\new StaffGroup
+\relative <<
\new Staff { c1 c }
+ \new Staff { c c }
>>
@end lilypond
-In a @code{ChoirStaff}, the group starts with a bracket, but bar
-lines are not connected.
+@item
+In a @code{ChoirStaff}, the group is started with a
+bracket, but bar lines are not connected.
-@lilypond[verbatim,quote,relative=2]
-\new ChoirStaff <<
- \new Staff { c1 c }
+@lilypond[verbatim,ragged-right,quote]
+\new ChoirStaff
+\relative <<
\new Staff { c1 c }
+ \new Staff { c c }
>>
@end lilypond
-In a @code{GrandStaff}, the group begins with a brace, and bar
-lines are connected between the staves.
-
-@lilypond[verbatim,quote,relative=2]
-\new GrandStaff <<
- \new Staff { c1 c }
- \new Staff { c1 c }
->>
-@end lilypond
-
-The @code{PianoStaff} is almost identical to a @code{GrandStaff},
-except that it supports printing the instrument name directly.
-For details, see @ref{Instrument names}.
+@item
+If no context is specified, the default properties for the score
+will be used: the group is started with a vertical line, and the
+bar lines are not connected.
-@lilypond[verbatim,quote,relative=2]
-\new PianoStaff <<
- \set PianoStaff.instrumentName = "Piano"
- \new Staff { c1 c }
+@lilypond[verbatim,ragged-right,quote]
+\relative <<
\new Staff { c1 c }
+ \new Staff { c c }
>>
@end lilypond
+@end itemize
-Each staff group context sets the property
-@code{systemStartDelimiter} to one of the following values:
-@code{SystemStartBar}, @code{SystemStartBrace}, or
-@code{SystemStartBracket}. A fourth delimiter,
-@code{SystemStartSquare}, is also available, but it must be
-explicitly specified.
-
-
-@snippets
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{use-square-bracket-at-the-start-of-a-staff-group.ly}
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{display-bracket-with-only-one-staff-in-a-system.ly}
-
-@cindex mensurstriche layout
-@cindex renaissance music
-@cindex transcription of mensural music
-@cindex mensural music, transcription of
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{mensurstriche-layout-bar-lines-between-the-staves.ly}
-@c FIXME: move to NR 2.8.x when sectioning is ready
-
-
-@seealso
-
-Music Glossary:
-@rglos{brace},
-@rglos{bracket},
-@rglos{grand staff}.
-
-Notation Reference:
-@ref{Instrument names}.
-
-Snippets:
-@rlsr{Staff notation}.
+@cindex Mensurstriche layout
+@cindex Renaissance music
-Internals Reference:
-@rinternals{Staff},
-@rinternals{ChoirStaff},
-@rinternals{GrandStaff},
-@rinternals{PianoStaff},
-@rinternals{StaffGroup},
-@rinternals{SystemStartBar},
-@rinternals{SystemStartBrace},
-@rinternals{SystemStartBracket},
-@rinternals{SystemStartSquare}.
+In addition to these four staff group types, other groupings can
+be produced by changing various properties. E.g., the
+@q{Mensurstriche} layout common in Renaissance music, with
+bar lines running between but not through the staves, can be
+produced from a @code{StaffGroup} or @code{GrandStaff} context if
+the bar lines are made transparent in the @code{Staff} itself, with
+the command @code{\override Staff.BarLine #'transparent = ##t}
+@cindex staff, nested
-@node Deeper nested staff groups
-@unnumberedsubsubsec Deeper nested staff groups
+Staff groups can be nested, using the context
+@code{InnerStaffGroup} or @code{InnerChoirStaff}; see
+@lsr{staff,staff-brackets.ly}
+@c snippet 137
-@cindex staff, nested
-@cindex staves, nested
-@cindex nesting of staves
-@cindex system start delimiters, nested
-@cindex nested staff brackets
-@cindex brackets, nesting of
-@cindex braces, nesting of
-@cindex inner staff group
-@cindex inner choir staff group
-
-Two additional staff-group contexts are available that can be
-nested within a @code{StaffGroup} or @code{ChoirStaff} context:
-@code{InnerStaffGroup} and @code{InnerChoirStaff}. These contexts
-create an additional bracket next to the original bracket of their
-parent staff group.
-
-An @code{InnerStaffGroup} is treated similarly to a
-@code{StaffGroup}; bar lines are connected between each stave
-within the context:
-
-@lilypond[verbatim,quote,relative=2]
-\new StaffGroup <<
- \new Staff { c2 c }
- \new InnerStaffGroup <<
- \new Staff { g2 g }
- \new Staff { e2 e }
- >>
->>
-@end lilypond
+@commonprop
-Bar lines are @emph{not} connected between staves of an
-@code{InnerChoirStaff}, just like a @code{ChoirStaff}:
+More complex nesting can be accomplished using the property
+@code{systemStartDelimiterHierarchy}:
-@lilypond[verbatim,quote,relative=2]
-\new ChoirStaff <<
- \new Staff { c2 c }
- \new InnerChoirStaff <<
- \new Staff { g2 g }
- \new Staff { e2 e }
- >>
+@lilypond[quote,ragged-right,verbatim]
+\new StaffGroup
+\relative <<
+ \set StaffGroup.systemStartDelimiterHierarchy
+ = #'(SystemStartSquare (SystemStartBracket a
+ (SystemStartSquare b)) d)
+ \new Staff { c1 }
+ \new Staff { c1 }
+ \new Staff { c1 }
+ \new Staff { c1 }
\new Staff { c1 }
>>
@end lilypond
-
-@snippets
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{nesting-staves.ly}
-
+Each staff group context sets the property
+@code{systemStartDelimiter} to one of the values
+@internalsref{SystemStartBar}, @internalsref{SystemStartBrace},
+and @internalsref{SystemStartBracket}. A fourth delimiter,
+@code{systemStartSquare}, is also available, but must be
+instantiated manually.
+
+@c FIXME: Graham will deal with this. -gp
+@c snippet 201
+To display a bracket even if there is only one staff, see
+@lsr{staff,display-bracket-with-only-one-staff-in-a
+system.ly}
@seealso
-Notation Reference:
-@ref{Grouping staves},
-@ref{Instrument names}.
-
-Snippets:
-@rlsr{Staff notation}.
+Music Glossary: @rglos{brace}, @rglos{staff}, @rglos{staves}
+@rglos{bracket}.
-Internals Reference:
-@rinternals{InnerStaffGroup},
-@rinternals{StaffGroup},
-@rinternals{InnerChoirStaff},
-@rinternals{ChoirStaff},
-@rinternals{SystemStartBar},
-@rinternals{SystemStartBrace},
-@rinternals{SystemStartBracket}.
+Snippets: @lsrdir{staff}
-
-@node Modifying single staves
-@subsection Modifying single staves
-
-This section explains how to change specific attributes of one
-staff: for example, modifying the number of staff lines or the
-staff size. Methods to start and stop staves and set ossia
-sections are also described.
-
-@menu
-* Staff symbol::
-* Ossia staves::
-* Hiding staves::
-@end menu
+Internals Reference: @internalsref{ChoirStaff},
+@internalsref{GrandStaff}, @internalsref{StaffGroup},
+@internalsref{SystemStartBar}, @internalsref{SystemStartBrace},
+@internalsref{SystemStartBracket},
+@internalsref{systemStartDelimiterHierarchy}.
@node Staff symbol
@unnumberedsubsubsec Staff symbol
-@cindex adjusting staff symbol
-@cindex drawing staff symbol
-@cindex staff symbol, setting of
-@cindex stop staff lines
-@cindex start staff lines
-@cindex staff lines, amount of
-@cindex staff lines, number of
-@cindex staff line, thickness of
-@cindex amount of staff lines
-@cindex thickness of staff lines
-@cindex ledger lines, setting
-@cindex setting of ledger lines
-@cindex spacing of ledger lines
-@cindex number of staff lines
-
-The grob @code{StaffSymbol} is responsible for drawing the lines
-of a staff. Its properties can be altered in order to change the
-appearance of a staff, but they must be changed before the staff
-is created. A staff may be started or stopped at any point in the
-score.
-
-The number of staff lines may be changed. The clef position and
-the position of middle C may need to be modified to fit the new
-staff. For an explanation, refer to the snippet section in
-@ref{Clef}.
-
-@lilypond[verbatim,quote,relative=2]
-\new Staff {
- \override Staff.StaffSymbol #'line-count = #3
- d4 d d d
-}
-@end lilypond
-
-The vertical position of staff lines and the number of staff lines
-can be defined at the same time. As the example shows, the
-positions of the notes are not influenced by the position of the
-staff lines. Details for modifying this property are found in
-@rinternals{staff-symbol-interface}.
-
-@warning{The @code{'line-positions} property overrides the
-@code{'line-count} property. The number of staff lines is
-implicitly defined by the number of elements in the list of values
-for @code{'line-positions}}
-
-@lilypond[verbatim,quote,relative=1]
-\new Staff \with {
- \override StaffSymbol #'line-positions = #'(7 3 0 -4 -6 -7)
-}
-{ a4 e' f b | d1 }
-@end lilypond
-
-The staff line thickness can be modified. The thickness of ledger
-lines and stems are also affected, since they depend on staff line
-thickness.
-
-@lilypond[verbatim,quote,relative=1]
-\new Staff \with {
- \override StaffSymbol #'thickness = #3
-}
-{ e4 d c b }
-@end lilypond
-
-The thickness of ledger lines can be set independently of staff
-line thickness. A description of this property is also found in
-@rinternals{staff-symbol-interface}.
-
-@lilypond[verbatim,quote,relative=1]
-\new Staff \with {
- \override StaffSymbol #'ledger-line-thickness = #'(1 . 0.2)
-}
-{ e4 d c b }
-@end lilypond
-
-The distance between staff lines can be changed. The setting has
-influence on ledger lines as well.
+@cindex staff symbol, adjusting
+@cindex staff, starting
+@cindex staff, stopping
-@lilypond[verbatim,quote,relative=1]
-\new Staff \with {
- \override StaffSymbol #'staff-space = #1.5
-}
-{ a4 b c d }
-@end lilypond
-
-The width of a staff can be adjusted. The unit is one staff
-space. The spacing of objects inside the staff is not influenced
-by this setting.
-
-@lilypond[verbatim,quote,relative=1]
-\new Staff \with {
- \override StaffSymbol #'width = #23
-}
-{ a4 e' f b | d1 }
-@end lilypond
-
-Modifications to staff properties in the middle of a score can be
-placed between @code{\stopStaff} and @code{\startStaff}:
-
-@lilypond[verbatim,quote,relative=2]
-c2 c
-\stopStaff
-\override Staff.StaffSymbol #'line-count = #2
-\startStaff
-b2 b
-\stopStaff
+@fundindex \startStaff
+@funindex startStaff
+@funindex \stopStaff
+@funindex stopStaff
+
+The layout object which draws the lines of a staff is called
+@code{staff symbol}. The staff symbol may be tuned in the number,
+thickness and distance of lines, using properties. This is
+demonstrated in the example files
+@lsr{staff,changing-the-number-of-lines-in-a-staff.ly} and
+@lsr{staff,changing-the-staff-size.ly}.
+
+In addition, staves may be started and stopped at will. This is
+done with @code{\startStaff} and @code{\stopStaff}.
+
+@lilypond[verbatim,relative=2,fragment]
+b4 b
+\override Staff.StaffSymbol #'line-count = 2
+\stopStaff \startStaff
+b b
\revert Staff.StaffSymbol #'line-count
-\startStaff
-a2 a
+\stopStaff \startStaff
+b b
@end lilypond
-
-@predefined
-
-@funindex \startStaff
-@code{\startStaff},
-@funindex \stopStaff
-@code{\stopStaff}.
-
-
-@snippets
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{making-some-staff-lines-thicker-than-the-others.ly}
-
-
-@seealso
-
-Music Glossary:
-@rglos{line},
-@rglos{ledger line},
-@rglos{staff}.
-
-Notation Reference:
-@ref{Displaying pitches}.
-
-Snippets:
-@rlsr{Staff notation}.
-
-Internals Reference:
-@rinternals{StaffSymbol},
-@rinternals{staff-symbol-interface}.
-
-
-@knownissues
-
-When setting staff lines manually, bar lines are always drawn
-centered on the position 0, so the maximum distance of the bar
-lines in either direction must be equal.
-
-
-@node Ossia staves
-@unnumberedsubsubsec Ossia staves
-
-@cindex staff, Frenched
+@cindex staves, Frenched
@cindex ossia
@cindex Frenched staves
-@cindex staff, resizing of
-@cindex resizing of staves
-
-@notation{Ossia} staves can be set by creating a new simultaneous
-staff in the appropriate location:
-
-@lilypond[verbatim,quote]
-\new Staff \relative c'' {
- c4 b d c
- <<
- { c4 b d c }
- \new Staff { e4 d f e }
- >>
- c4 b c2
-}
-@end lilypond
-
-However, the above example is usually not the desired result. To
-create ossia staves that are above the original staff, have no
-time signature or clef, and have a smaller font size, tweaks must
-be used. The Learning Manual describes a specific technique to
-achieve this goal, beginning with
-@rlearning{Nesting music expressions}.
-
-The following example uses the @code{alignAboveContext} property
-to align the ossia staff. This method is most appropriate when
-only a few ossia staves are needed.
-
-@lilypond[verbatim,quote]
-\new Staff = main \relative c'' {
- c4 b d c
- <<
- { c4 b d c }
-
- \new Staff \with {
- \remove "Time_signature_engraver"
- alignAboveContext = #"main"
- fontSize = #-3
- \override StaffSymbol #'staff-space = #(magstep -3)
- \override StaffSymbol #'thickness = #(magstep -3)
- firstClef = ##f
- }
- { e4 d f e }
- >>
- c4 b c2
-}
-@end lilypond
-If many isolated ossia staves are needed, creating an empty
-@code{Staff} context with a specific @emph{context id} may be more
-appropriate; the ossia staves may then be created by
-@emph{calling} this context and using @code{\startStaff} and
-@code{\stopStaff} at the desired locations. The benefits of this
-method are more apparent if the piece is longer than the following
-example.
+In combination with Frenched staves, this may be used to typeset
+@emph{ossia} sections. An example is shown here
-@lilypond[verbatim,quote,ragged-right]
-<<
- \new Staff = ossia \with {
- \remove "Time_signature_engraver"
- \remove "Clef_engraver"
- fontSize = #-3
- \override StaffSymbol #'staff-space = #(magstep -3)
- \override StaffSymbol #'thickness = #(magstep -3)
- }
- { \stopStaff s1*6 }
-
- \new Staff \relative c' {
- c4 b c2
- <<
- { e4 f e2 }
- \context Staff = ossia {
- \startStaff e4 g8 f e2 \stopStaff
- }
- >>
- g4 a g2 \break
- c4 b c2
- <<
- { g4 a g2 }
- \context Staff = ossia {
- \startStaff g4 e8 f g2 \stopStaff
- }
- >>
- e4 d c2
- }
->>
-@end lilypond
-
-@c The following is the legacy "ossia.ly" example
-@c
-@c I don't think this method is very efficient.
-@c I'm commenting it out for now. -pm
-
-@ignore
-
-@ lilypond[verbatim,quote]
+@lilypond[verbatim,relative=2,quote]
<<
\new Staff \with
{
- %No time signature in the ossia staff
\remove "Time_signature_engraver"
- fontSize = #-3
- \override StaffSymbol #'staff-space = #(magstep -3)
- \override StaffSymbol #'thickness = #(magstep -3)
+ fontSize = #-2
+ \override StaffSymbol #'staff-space = #(magstep -2)
firstClef = ##f
}
\relative c'' {
s2
\startStaff
- f8 d g4
+ f8 d g4
}
- \new Staff \relative c'' {
+ \new Staff \relative
+ {
\time 2/4
c4 c g' g a a g2
}
->>
-@ end lilypond
-
-@end ignore
-Using the @code{\RemoveEmptyStaffContext} command to create ossia
-staves may be used as an alternative. This method is most
-convenient when ossia staves occur immediately following a line
-break. In this case, spacer rests do not need to be used at all;
-only @code{\startStaff} and @code{\stopStaff} are necessary. For
-more information about @code{\RemoveEmptyStaffContext}, see
-@ref{Hiding staves}.
-
-@lilypond[verbatim,quote,ragged-right]
-<<
- \new Staff = ossia \with {
- \remove "Time_signature_engraver"
- \remove "Clef_engraver"
- fontSize = #-3
- \override StaffSymbol #'staff-space = #(magstep -3)
- \override StaffSymbol #'thickness = #(magstep -3)
- }
- \new Staff \relative c' {
- c4 b c2
- e4 f e2
- g4 a g2 \break
- <<
- { c4 b c2 }
- \context Staff = ossia {
- c4 e8 d c2 \stopStaff
- }
- >>
- g4 a g2
- e4 d c2
- }
>>
-
-\layout {
- \context {
- \RemoveEmptyStaffContext
- \override VerticalAxisGroup #'remove-first = ##t
- }
-}
@end lilypond
-
-@snippets
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{vertically-aligning-ossias-and-lyrics.ly}
-
+@cindex staff lines, setting number of
+@cindex staff lines, setting thickness of
+@cindex thickness of staff lines, setting
+@cindex number of staff lines, setting
@seealso
-Music Glossary:
-@rglos{ossia},
-@rglos{staff},
-@rglos{Frenched staff}.
-
-Learning Manual:
-@rlearning{Nesting music expressions},
-@rlearning{Size of objects},
-@rlearning{Length and thickness of objects}.
+Music Glossary: @rglos{ossia}, @rglos{staff}, @rglos{Frenched staff}.
-Notation Reference:
-@ref{Setting the staff size}.
+Snippets: @lsrdir{staff}
-Snippets:
-@rlsr{Staff notation}.
-
-Internals Reference:
-@rinternals{StaffSymbol}.
+Internals Reference: @internalsref{StaffSymbol},
+@internalsref{DrumStaff}.
@node Hiding staves
@unnumberedsubsubsec Hiding staves
@cindex Frenched scores
-@cindex staff, hiding
-@cindex staff, empty
-@cindex hiding of staves
-@cindex empty staves
-@cindex Frenched staves
+@cindex staves, hiding empty
+@cindex hiding empty staves
In orchestral scores, staff lines that only have rests are usually
-removed in order to save some space. This style is called
-@q{French Score}. For the @code{Lyrics}, @code{ChordNames}, and
-@code{FiguredBass} contexts, this is switched on by default.
-
-For other staff contexts, this behavior is set with the
-@code{\RemoveEmptyStaffContext} command. It is set in the
-@code{\layout} block. As a result, empty staves or staves
-containing multi-measure rests are removed after a line break.
-
-@lilypond[verbatim,quote,ragged-right]
+removed; this saves some space. This style is called @q{French
+Score}. For @code{Lyrics}, @code{ChordNames} and
+@code{FiguredBass}, this is switched on by default. When
+the lines of these contexts turn out empty after the line-breaking
+process, they are removed.
+
+For normal staves, a specialized @code{Staff} context is
+available, which does the same: staves containing nothing (or only
+multi-measure rests) are removed. The context definition is
+stored in @code{\RemoveEmptyStaffContext} variable. Observe how
+the second staff in this example disappears in the second line
+
+@lilypond[quote,ragged-right,verbatim]
\layout {
- \context {
- \RemoveEmptyStaffContext
- }
+ \context { \RemoveEmptyStaffContext }
}
-\relative c'' {
- <<
+
+{
+ \relative c' <<
\new Staff { e4 f g a \break c1 }
\new Staff { c4 d e f \break R1 }
>>
}
@end lilypond
+The first system shows all staves in full. If empty staves should
+be removed from the first system too, set @code{remove-first} to
+true in @code{VerticalAxisGroup}.
+
+@example
+\override Score.VerticalAxisGroup #'remove-first = ##t
+@end example
+
To remove other types of contexts, use
@code{\AncientRemoveEmptyStaffContext} or
@code{\RemoveEmptyRhythmicStaffContext}.
@cindex ossia
-Another application of @code{\RemoveEmptyStaffContext} is to make
-ossia sections, i.e., alternative melodies on a separate piece of
-staff, with help of a Frenched staff. For details, see
-@ref{Ossia staves}.
+Another application of the @code{\RemoveEmptyStaffContext} is to
+make ossia sections, i.e., alternative melodies on a separate
+piece of staff, with help of a Frenched staff. See @ref{Staff
+symbol}.
+
+You can make the staff lines invisible by removing the
+@code{Staff_symbol_engraver} from the @code{Staff} context.
-Staff lines can be made invisible by removing the
-@code{Staff_symbol_engraver} from the @code{Staff} context:
-@lilypond[verbatim,quote]
-\new Staff \with {
- \remove "Staff_symbol_engraver"
+@lilypond[quote,ragged-right,verbatim]
+\score {
+ \context Staff \relative c'' { c8 c c16 c c c }
+ \layout{
+ \context {
+ \Staff
+ \remove Staff_symbol_engraver
+ }
+ }
}
-\relative c'' { c8 c c16 c c c c2 }
@end lilypond
-
-@snippets
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{removing-the-first-empty-line.ly}
-
-
-@predefined
-
-@funindex \RemoveEmptyStaffContext
-@code{\RemoveEmptyStaffContext},
-@funindex \AncientRemoveEmptyStaffContext
-@code{\AncientRemoveEmptyStaffContext},
-@funindex \RemoveEmptyRhythmicStaffContext
-@code{\RemoveEmptyRhythmicStaffContext}.
-
-
@seealso
-Notation Reference:
-@ref{Staff symbol},
-@ref{Ossia staves}.
+Notation Reference: @ref{Staff symbol}.
-Snippets:
-@rlsr{Staff notation}.
-
-Internals Reference:
-@rinternals{ChordNames},
-@rinternals{FiguredBass},
-@rinternals{Lyrics},
-@rinternals{Staff},
-@rinternals{VerticalAxisGroup}.
+Snippets: @lsrdir{staff}
+Internals Reference: @internalsref{ChordNames},
+@internalsref{FiguredBass}, @internalsref{Lyrics},
+@internalsref{Staff}, @internalsref{VerticalAxisGroup}.
@node Writing parts
@subsection Writing parts
-This section explains how to insert tempo indications and
-instrument names into a score. Methods to quote other voices and
-format cue notes are also described.
-
@menu
-* Metronome marks::
-* Instrument names::
-* Quoting other voices::
-* Formatting cue notes::
+* Metronome marks::
+* Instrument names::
+* Quoting other voices::
+* Formatting cue notes::
@end menu
-
@node Metronome marks
@unnumberedsubsubsec Metronome marks
@cindex tempo
@cindex beats per minute
@cindex metronome marking
-@cindex metronome marking with text
-@funindex \tempo
-
-Basic metronome markings can be entered as follows:
-
-@lilypond[verbatim,quote,relative=2]
-\tempo 2 = 120
-c1
-@end lilypond
-Textual tempo indications can be used instead:
+@funindex \tempo
+@funindex tempo
-@lilypond[verbatim,quote,relative=2]
-\tempo "Allegretto"
-d2 c
-@end lilypond
+Metronome settings can be entered as follows
-The combination of a metronome marking and textual description
-will automatically place the metronome marking within parentheses:
+@example
+\tempo @var{duration} = @var{per-minute}
+@end example
-@lilypond[verbatim,quote,relative=2]
-\tempo "Allegro" 4 = 160
-g4 c d e
-@end lilypond
+In the MIDI output, they are interpreted as a tempo change. In
+the layout output, a metronome marking is printed
-To write a metronome marking in parentheses without the text,
-include an empty string in the input:
-@lilypond[verbatim,quote,relative=2]
-\tempo "" 8 = 96
-d4 g e c
+@lilypond[quote,ragged-right,verbatim,fragment]
+\tempo 8.=120 c''1
@end lilypond
-@snippets
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{printing-metronome-and-rehearsal-marks-below-the-staff.ly}
-
-@c perhaps also an example of how to move it horizontally?
+@commonprop
-@c TODO add snippet to LSR -pm
To change the tempo in the MIDI output without printing anything,
-make the metronome marking invisible
+make the metronome marking invisible @example \once \override
+Score.MetronomeMark #'transparent = ##t @end example
-@example
-\once \override Score.MetronomeMark #'transparent = ##t
-@end example
-
-@c TODO add snippet to LSR -pm
To print other metronome markings, use these markup commands
-
-@lilypond[verbatim,quote,relative=1]
+@lilypond[quote,ragged-right,verbatim,relative,fragment]
c4^\markup {
(
\smaller \general-align #Y #DOWN \note #"16." #1
) }
@end lilypond
-For more details, see @ref{Formatting text}.
+@noindent
+For more details, see @ref{Text markup}.
@seealso
-Music Glossary:
-@rglos{metronome},
-@rglos{metronomic indication},
-@rglos{tempo indication},
-@rglos{metronome mark}.
+Music Glossary: @rglos{metronome}, @rglos{metronomic indication},
+@rglos{tempo indication}, @rglos{metronome mark}.
+
+Notation Reference: @ref{Text markup}.
+
+Snippets: @lsrdir{staff}.
+
+Internals Reference: @internalsref{MetronomeMark}, @ref{MIDI
+output}.
+
-Notation Reference:
-@ref{Formatting text},
-@ref{MIDI output}.
+@refbugs
-Snippets:
-@rlsr{Staff notation}.
+Collisions are not checked. If you have notes above the top line
+of the staff (or notes with articulations, slurs, text, etc), then
+the metronome marking may be printed on top of musical symbols.
+If this occurs, increase the padding of the metronome mark to
+place it further away from the staff.
-Internals Reference:
-@rinternals{MetronomeMark}.
+@example
+\override Score.MetronomeMark #'padding = #2.5
+@end example
+
+@c perhaps also an example of how to move it horizontally?
@node Instrument names
@cindex instrument names
@cindex instrument names, short
-Instrument names can be printed on the left side of staves for the
-@code{Staff} and @code{PianoStaff} contexts. The value of
-@code{instrumentName} is used for the first staff, and the value
-of @code{shortInstrumentName} is used for all succeeding staves.
+In an orchestral score, instrument names are printed at the left
+side of the staves.
+
+This can be achieved by setting @code{Staff}.@code{instrumentName} and
+@code{Staff}.@code{shortInstrumentName}, or
+@code{PianoStaff}.@code{instrumentName} and
+@code{PianoStaff}.@code{shortInstrumentName}. This will print text
+before the start of the staff. For the first staff,
+@code{instrumentName} is used. If set, @code{shortInstrumentName} is
+used for the following staves.
-@lilypond[verbatim,quote,ragged-right,relative=1]
-\set Staff.instrumentName = "Violin "
-\set Staff.shortInstrumentName = "Vln "
+@lilypond[quote,verbatim,ragged-right,relative=1,fragment]
+\set Staff.instrumentName = "Ploink "
+\set Staff.shortInstrumentName = "Plk "
c1
\break
-c''1
+c''
@end lilypond
-Markup mode can be used to create more complicated instrument
-names:
+You can also use markup texts to construct more complicated
+instrument names, for example
-@lilypond[verbatim,quote,relative=2]
+@lilypond[quote,fragment,verbatim,ragged-right]
\set Staff.instrumentName = \markup {
\column { "Clarinetti"
\line { "in B" \smaller \flat } } }
-c1
+c''1
@end lilypond
@cindex instrument names, centering
+@cindex centering instrument names
+@cindex aligning instrument names
+@cindex instrument names, aligning
-When two or more staff contexts are grouped together, the
-instrument names and short instrument names are centered by
-default. To center multi-line instrument names,
-@code{\center-align} must be used:
+If you wish to center the instrument names, you must center all of
+them individually:
-@lilypond[verbatim,quote,relative=2]
-<<
- \new Staff {
- \set Staff.instrumentName = \markup \center-align {
- Clarinetti
- \line { "in B" \smaller \flat }
- }
- c1
- }
- \new Staff {
- \set Staff.instrumentName = "Vibraphone"
- c1
- }
+@lilypond[quote,verbatim,ragged-right]
+{ <<
+\new Staff {
+ \set Staff.instrumentName = \markup {
+ \center-align { "Clarinetti"
+ \line { "in B" \smaller \flat } } }
+ c''1
+}
+\new Staff {
+ \set Staff.instrumentName =
+ \markup{ \center-align { Vibraphone }}
+ c''1
+}
>>
+}
@end lilypond
-@cindex indent
-@cindex short-indent
+For longer instrument names, it may be useful to increase the
+@code{indent} setting in the @code{\layout} block.
-The @code{indent} and @code{short-indent} settings specify the
-level of indentation for the first system and all succeeding
-systems, respectively. They can be modified in the @code{\layout}
-block. For longer instrument names or short instrument names, it
-may be useful to increase the @code{indent} and
-@code{short-indent} settings:
+To center instrument names while leaving extra space to the right,
-@lilypond[verbatim,quote]
-\relative c' <<
- \new Staff \with {
- instrumentName = "Oboe"
+@lilypond[quote,verbatim,ragged-right]
+\new StaffGroup \relative
+<<
+ \new Staff {
+ \set Staff.instrumentName =
+ \markup { \hcenter-in #10 "blabla" }
+ c1 c1
}
- { c2 d }
- \new Staff \with {
- instrumentName = "Glockenspiel"
+ \new Staff {
+ \set Staff.instrumentName =
+ \markup { \hcenter-in #10 "blo" }
+ c1 c1
}
- { c'2 d }
>>
-
-\layout {
- indent = 2.5\cm
-}
@end lilypond
To add instrument names to other contexts (such as
-@code{GrandStaff}, @code{ChoirStaff}, or @code{StaffGroup}),
-@code{Instrument_name_engraver} must be added to that context.
-For details, see @ref{Modifying context plug-ins}.
+@code{GrandStaff}, @code{ChoirStaff}, or @code{StaffGroup}), the
+engraver must be added to that context.
+
+@example
+\layout@{
+ \context @{\GrandStaff \consists "Instrument_name_engraver"@}
+@}
+@end example
+
+@noindent
+More information about adding and removing engravers can be found
+in @ref{Modifying context plug-ins}.
@cindex instrument names, changing
-Instrument names may be changed in the middle of a piece:
+Instrument names may be changed in the middle of a piece,
-@lilypond[verbatim,quote,ragged-right,relative=1]
+@lilypond[quote,fragment,verbatim,ragged-right]
\set Staff.instrumentName = "First"
\set Staff.shortInstrumentName = "one"
c1 c c c \break
@end lilypond
-@snippets
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{aligning-and-centering-instrument-names.ly}
-
-
@seealso
-Notation Reference:
-@ref{Modifying context plug-ins}.
+Notation Reference: @ref{Modifying context plug-ins}.
-Snippets:
-@rlsr{Staff notation}.
+Snippets: @lsrdir{staff}
-Internals Reference:
-@rinternals{InstrumentName},
-@rinternals{PianoStaff},
-@rinternals{Staff}.
+Internals Reference: @internalsref{InstrumentName},
+@internalsref{PianoStaff}, @internalsref{Staff}.
@node Quoting other voices
@cindex quoting other voices
@cindex fragments
@cindex cue notes
+@cindex cue transposition
+@cindex trasposition of cue notes
+@cindex quote transposition
+@cindex transposition of quotes
+
+@funindex \addQuote
+@funindex addQuote
+@funindex \quoteDuring
+@funindex quoteDuring
+@funindex \cueDuring
+@funindex cueDuring
+@funindex \transposition
+@funindex transposition
+
+With quotations, fragments of other parts can be inserted into a
+part directly. Before a part can be quoted, it must be marked
+especially as quotable. This is done with the @code{\addQuote}
+command.
+
+@example
+\addQuote @var{name} @var{music}
+@end example
-Quotations allow fragments of other parts to be inserted directly
-into a music expression. Before a part can be quoted, the
-@code{\addQuote} command must be used to initialize the quoted
-fragment. This command must be used in the toplevel scope. The
-first argument is an identifying string, and the second is a music
-expression:
+
+@noindent
+Here, @var{name} is an identifying string. The @var{music} is any
+kind of music. Here is an example of @code{\addQuote}
@example
-flute = \relative c' @{
+\addQuote clarinet \relative c' @{
f4 fis g gis
@}
-\addQuote "flute" @{ \flute @}
@end example
-The @code{\quoteDuring} command may then be used to indicate when
-the quotation should take place. The corresponding measures from
-the quotation are inserted into the music expression. The syntax
-is similar to @code{\addQuote}:
+This command must be entered at toplevel, i.e., outside any music
+blocks. Typically, one would use an already defined music event
+as the @var{music}:
-@lilypond[verbatim,quote]
-flute = \relative c' {
+@example
+clarinet = \relative c' @{
f4 fis g gis
-}
-\addQuote "flute" { \flute }
+@}
+\addQuote clarinet @{ \clarinet @}
+@end example
-\relative c' {
- c4 cis \quoteDuring #"flute" { s2 }
-}
-@end lilypond
-If the music expression used for @code{\quoteDuring} contains
-anything but a spacer rest or multi-measure rest, a polyphonic
-situation is created, which is often not desirable:
+After calling @code{\addQuote}, the quotation may then be done
+with @code{\quoteDuring} or @code{\cueDuring},
-@lilypond[verbatim,quote]
-flute = \relative c' {
- f4 fis g gis
-}
-\addQuote "flute" { \flute }
+@example
+\quoteDuring #@var{name} @var{music}
+@end example
-\relative c' {
- c4 cis \quoteDuring #"flute" { c4 b }
-}
-@end lilypond
+During a part, a piece of music can be quoted with the
+@code{\quoteDuring} command.
+
+@example
+\quoteDuring #"clarinet" @{ s2. @}
+@end example
+
+This would cite three quarter notes (the duration of @code{s2.})
+of the previously added @code{clarinet} voice.
+
+More precisely, it takes the current time-step of the part being
+printed, and extracts the notes at the corresponding point of the
+@code{\addQuote}d voice. Therefore, the argument to
+@code{\addQuote} should be the entire part of the voice to be
+quoted, including any rests at the beginning.
-Quotations recognize instrument transposition settings for both
-the source and target instruments if they are specified using the
-@code{\transposition} command:
+It is possible to use another music expression instead of
+@code{s}, thus creating a polyphonic section, but this may not
+always give the desired result.
-@lilypond[verbatim,quote]
-clarinet = \relative c' {
+Quotations take into account the transposition of both source and
+target instruments, if they are specified using the
+@code{\transposition} command.
+
+@lilypond[quote,ragged-right,verbatim]
+\addQuote clarinet \relative c' {
\transposition bes
f4 fis g gis
}
-\addQuote "clarinet" { \clarinet }
-\relative c' {
- c4 cis \quoteDuring #"clarinet" { s2 }
+{
+ e'8 f'8 \quoteDuring #"clarinet" { s2 }
}
@end lilypond
-@c add to snippets, possibly. It might already be there. -pm
-@c
-@c The type of events that are present in the quoted music can be
-@c trimmed with the @code{quotedEventTypes} property. The default
-@c value is @code{(note-event rest-event)}, which means that only
-@c notes and rests of the quoted voice end up in the
-@c @code{\quoteDuring}. Setting
-@c
-@c @example
-@c \set Staff.quotedEventTypes =
-@c #'(note-event articulation-event dynamic-event)
-@c @end example
-@c
-@c @noindent
-@c will quote notes (but no rests), together with scripts and
-@c dynamics.
-
-
-@snippets
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{quoting-another-voice-with-transposition.ly}
-
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
-{quoting-another-voice.ly}
-
-
-@seealso
-
-Notation Reference:
-@ref{Instrument transpositions}.
+The type of events that are present in the quoted music can be
+trimmed with the @code{quotedEventTypes} property. The default
+value is @code{(note-event rest-event)}, which means that only
+notes and rests of the quoted voice end up in the
+@code{\quoteDuring}. Setting
-Snippets:
-@rlsr{Staff notation}.
-
-Internals Reference:
-@rinternals{QuoteMusic},
-@rinternals{Voice}.
+@example
+\set Staff.quotedEventTypes =
+ #'(note-event articulation-event dynamic-event)
+@end example
+@noindent
+will quote notes (but no rests), together with scripts and
+dynamics.
-@knownissues
+@refbugs
Only the contents of the first @code{Voice} occurring in an
@code{\addQuote} command will be considered for quotation, so
-@var{music} cannot contain @code{\new} and @code{\context Voice}
+@var{music} can not contain @code{\new} and @code{\context Voice}
statements that would switch to a different Voice.
Quoting grace notes is broken and can even cause LilyPond to
In earlier versions of LilyPond (pre 2.11), @code{addQuote} was
written entirely in lower-case letters: @code{\addquote}.
+@seealso
+
+Notation Reference: @ref{Instrument transpositions}.
+
+Snippets: @lsrdir{staff}
+
+Internals Reference: @internalsref{QuoteMusic}, @internalsref{Voice}.
+
@node Formatting cue notes
@unnumberedsubsubsec Formatting cue notes
@cindex cue notes
@cindex cue notes, formatting
@cindex fragments
-@cindex quoting other voices
+@cindex quoting other voices
@cindex cues, formatting
+@cindex transposing cue notes
+@cindex transposing cues
+@cindex cues, transposing
+@cindex cue notes, transposing
-The previous section explains how to quote other voices. The
-@code{\cueDuring} command is a more specialized form of
-@code{\quoteDuring}, being particularly useful for inserting cue
-notes into a part. The syntax is as follows:
+@funindex \cueDuring
+@funindex cueDuring
+@funindex \transposedCueDuring
+@funindex transposedCueDuring
+
+The previous section deals with inserting notes from another
+voice. There is a more advanced music function called
+@code{\cueDuring}, which makes formatting cue notes easier.
+
+The syntax is
@example
- \cueDuring #@var{partname} #@var{voice} @var{music}
+ \cueDuring #@var{name} #@var{updown} @var{music}
@end example
-This command copies the corresponding measures from @var{partname}
-into a @code{CueVoice} context. The @code{CueVoice} is created
-implicitly, and occurs simultaneously with @var{music}, which
-creates a polyphonic situation. The @var{voice} argument
-determines whether the cue notes should be notated as a first or
-second voice; @code{DOWN} corresponds to the first voice, and
-@code{UP} corresponds to the second.
-
-@lilypond[verbatim,quote]
-oboe = \relative c'' {
- r2 r8 d16 f e g f a
- g8 g16 g g2.
+This will insert notes from the part @var{name} into a
+@code{Voice} called @code{cue}. This happens
+simultaneously with @var{music}, which usually is a rest. When
+the cue notes start, the staff in effect becomes polyphonic for a
+moment. The argument @var{updown} determines whether the cue
+notes should be notated as a first or second voice.
+
+
+@lilypond[verbatim,ragged-right]
+smaller = {
+ \set fontSize = #-2
+ \override Stem #'length-fraction = #0.8
+ \override Beam #'thickness = #0.384
+ \override Beam #'length-fraction = #0.8
}
-\addQuote "oboe" { \oboe }
-\new Voice \relative c'' {
- \cueDuring #"oboe" #UP { R1 }
- g2 c,
+\addQuote clarinet \relative {
+ R1*20
+ r2 r8 c' f f
}
-@end lilypond
-In the above example, the @code{Voice} context had to be
-explicitly declared, or else the entire music expression would
-belong to the @code{CueVoice} context.
+\new Staff \relative <<
+
+ % setup a context for cue notes.
+ \new Voice = "cue" { \smaller \skip 1*21 }
+
+ \set Score.skipBars = ##t
+
+ \new Voice {
+ R1*20
+ \cueDuring #"clarinet" #UP {
+ R1
+ }
+ g4 g2.
+ }
+>>
+@end lilypond
-@c TODO document \killCues
-@c TODO document instrumentCueName context property
-When typesetting cue notes, some guidelines should be followed:
+Here are a couple of hints for successful cue notes:
@itemize
@item
-The instrument playing the cue should be clearly marked on the
-score.
+Cue notes have smaller font sizes.
+
+@item
+The cued part is marked with the instrument playing the cue.
@item
-When the cue notes end, the name of the original instrument should
-be indicated.
+When the original part takes over again, this should be marked
+with the name of the original instrument.
@item
Any other changes introduced by the cued part should also be
@end itemize
-The @code{\transposedCueDuring} command is useful to add cues for
-instruments in a completely different register. Having piccolo
-cues within a contrabassoon part is a good example.
-@lilypond[verbatim,quote]
-piccolo = \relative c''' {
+The macro @code{\transposedCueDuring} is useful to add cues to
+instruments which use a completely different octave range (for
+example, having a cue of a piccolo flute within a contra bassoon
+part).
+
+@lilypond[verbatim,ragged-right,quote]
+picc = \relative c''' {
\clef "treble^8"
- R1
- c8 c c e g2
- a4 g g2
+ R1 |
+ c8 c c e g2 |
+ a4 g g2 |
}
-\addQuote "piccolo" { \piccolo }
+\addQuote "picc" { \picc }
-cbassoon = \relative c, {
+cbsn = \relative c, {
\clef "bass_8"
c4 r g r
- \transposedCueDuring #"piccolo" #UP c,, { R1 }
- c4 r g r
+ \transposedCueDuring #"picc" #UP c,, { R1 } |
+ c4 r g r |
}
<<
- \new Staff = "piccolo" \piccolo
- \new Staff = "cbassoon" \cbassoon
+ \context Staff = "picc" \picc
+ \context Staff = "cbsn" \cbsn
>>
@end lilypond
-
@seealso
-Snippets:
-@rlsr{Staff notation}.
-
-Internals Reference:
-@rinternals{Voice}.
+Snippets: @lsrdir{staff}.
+Internals Reference: @internalsref{Voice}.
-@knownissues
-Collisions are not checked between @code{Voice} and
-@code{CueVoice} contexts.
projects / lilypond.git / blobdiff