@node Staff notation
@section Staff notation
-Notes, dynamic signs, etc., are grouped with a set of horizontal
+@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
-@internalsref{GrandStaff}, a @internalsref{StaffGroup}, or a
-@internalsref{ChoirStaff}.
+Two or more staves can be grouped vertically in a @code{GrandStaff}, a
+@code{StaffGroup}, or a @code{ChoirStaff}.
@menu
@end menu
@node System start delimiters
-@unnumberedsubsubsec System start delimiters
+@subsubsection System start delimiters
@cindex start of system
-@cindex Staff, multiple
+@cindex staff, multiple
@cindex bracket, vertical
@cindex brace, vertical
@cindex grand staff
@cindex staff group
@cindex staff, choir
+@cindex system
Many scores consist of more than one staff. These staves can be
grouped in several different ways:
@itemize
@item
-In a @internalsref{GrandStaff}, the group is started with a brace
+In a @code{GrandStaff}, the group is started with a brace
at the left, and bar lines are connected between the staves.
@lilypond[verbatim,ragged-right,quote]
@end lilypond
@item
-In a @internalsref{StaffGroup}, the barlines will be drawn through
+In a @code{StaffGroup}, the bar lines will be drawn through
all the staves, but the group is started with a bracket.
@lilypond[verbatim,ragged-right,quote]
@end lilypond
@item
-In a @internalsref{ChoirStaff}, the group is started with a
+In a @code{ChoirStaff}, the group is started with a
bracket, but bar lines are not connected.
@lilypond[verbatim,ragged-right,quote]
@end lilypond
@end itemize
+@cindex Mensurstriche layout
+@cindex Renaissance music
+
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
-barlines running between but not through the staves, can be
+bar lines running between but not through the staves, can be
produced from a @code{StaffGroup} or @code{GrandStaff} context if
-the barlines are made transparent in the @code{Staff} itself, with
+the bar lines are made transparent in the @code{Staff} itself, with
the command @code{\override Staff.BarLine #'transparent = ##t}
@cindex staff, nested
Staff groups can be nested, using the context
@code{InnerStaffGroup} or @code{InnerChoirStaff}; see
-@lsr{staff,staff-brackets.ly}
+@c @lsr{staff,staff-brackets.ly}
@c snippet 137
@commonprop
More complex nesting can be accomplished using the property
-@internalsref{systemStartDelimiterHierarchy}:
+@code{systemStartDelimiterHierarchy}:
@lilypond[quote,ragged-right,verbatim]
\new StaffGroup
>>
@end lilypond
-@seealso
-
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.
+instantiated manually
-@commonprop
-
-To display a bracket even if there is only one staff, see
-@lsr{staff,display-bracket-with-only-one-staff-in-a
-system.ly}
+@c FIXME: Graham will deal with this. -gp
@c snippet 201
+To display a bracket even if there is only one staff, see
+@c @lsr{staff,display-bracket-with-only-one-staff-in-a system.ly}
+
+@seealso
+
+Music Glossary: @rglos{brace}, @rglos{staff}, @rglos{staves}
+@rglos{bracket}.
+
+Snippets: @lsrdir{Staff,Staff-notation}
+
+Internals Reference: @internalsref{ChoirStaff},
+@internalsref{GrandStaff}, @internalsref{StaffGroup},
+@internalsref{SystemStartBar}, @internalsref{SystemStartBrace},
+@internalsref{SystemStartBracket},
+@internalsref{systemStartDelimiterHierarchy}.
+
@node Staff symbol
-@unnumberedsubsubsec Staff symbol
+@subsubsection Staff symbol
@cindex adjusting staff symbol
@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}.
+@c @lsr{staff,changing-the-number-of-lines-in-a-staff.ly} and
+@c @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}.
b b
@end lilypond
+@cindex staves, Frenched
+@cindex ossia
+@cindex Frenched staves
+
In combination with Frenched staves, this may be used to typeset
@emph{ossia} sections. An example is shown here
-@cindex staves, Frenched
-@cindex ossia
-
@lilypond[verbatim,relative=2,quote]
<<
\new Staff \with
@seealso
+Music Glossary: @rglos{ossia}, @rglos{staff}, @rglos{Frenched staff}.
+
+Snippets: @lsrdir{Staff,Staff-notation}
+
Internals Reference: @internalsref{StaffSymbol},
@internalsref{DrumStaff}.
-Examples: @lsrdir{staff}
-
@node Hiding staves
-@unnumberedsubsubsec Hiding staves
+@subsubsection Hiding staves
@cindex Frenched scores
-@cindex staves, hiding
+@cindex staves, hiding
+@cindex staves, empty
In orchestral scores, staff lines that only have rests are usually
removed; this saves some space. This style is called @q{French
-Score}. For @internalsref{Lyrics}, @internalsref{ChordNames} and
-@internalsref{FiguredBass}, this is switched on by default. When
+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 @internalsref{Staff} context is
+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 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 @internalsref{VerticalAxisGroup}.
+true in @code{VerticalAxisGroup}.
@example
\override Score.VerticalAxisGroup #'remove-first = ##t
@code{\AncientRemoveEmptyStaffContext} or
@code{\RemoveEmptyRhythmicStaffContext}.
+@cindex ossia
+
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
}
@end lilypond
+@seealso
+
+Notation Reference: @ref{Staff symbol}.
+
+Snippets: @lsrdir{Staff,Staff-notation}
+
+Internals Reference: @internalsref{ChordNames},
+@internalsref{FiguredBass}, @internalsref{Lyrics},
+@internalsref{Staff}, @internalsref{VerticalAxisGroup}.
+
@node Writing parts
@subsection Writing parts
@end menu
@node Metronome marks
-@unnumberedsubsubsec Metronome marks
+@subsubsection Metronome marks
@cindex Tempo
@cindex beats per minute
@seealso
+Music Glossary: @rglos{metronome}, @rglos{metronomic indication},
+@rglos{tempo indication}, @rglos{metronome mark}.
+
+Notation Reference: @ref{Text markup}.
+
+Snippets: @lsrdir{Staff,Staff-notation}.
+
Internals Reference: @internalsref{MetronomeMark}, @ref{MIDI
output}.
@c perhaps also an example of how to move it horizontally?
+
@node Instrument names
-@unnumberedsubsubsec Instrument names
+@subsubsection Instrument names
+
+@cindex instrument names
+@cindex instrument names, short
In an orchestral score, instrument names are printed at the left
side of the staves.
-This can be achieved by setting
-@internalsref{Staff}.@code{instrumentName} and
-@internalsref{Staff}.@code{shortInstrumentName}, or
-@internalsref{PianoStaff}.@code{instrumentName} and
-@internalsref{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.
+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[quote,verbatim,ragged-right,relative=1,fragment]
\set Staff.instrumentName = "Ploink "
c''1
@end lilypond
-If you wish to center the instrument names, you must center all of
-them individually:
+@cindex instrument names, centering
+
+As instrument names are centered by default, multi line names
+are better entered using @code{\center-align}:
@lilypond[quote,verbatim,ragged-right]
{ <<
\new Staff {
- \set Staff.instrumentName = \markup {
- \center-align { "Clarinetti"
- \line { "in B" \smaller \flat } } }
+ \set Staff.instrumentName = \markup \center-align {
+ Clarinetti
+ \line { "in B" \smaller \flat }
+ }
c''1
}
\new Staff {
- \set Staff.instrumentName =
- \markup{ \center-align { Vibraphone }}
+ \set Staff.instrumentName = "Vibraphone"
c''1
}
>>
For longer instrument names, it may be useful to increase the
@code{indent} setting in the @code{\layout} block.
-To center instrument names while leaving extra space to the right,
-
-@lilypond[quote,verbatim,ragged-right]
-\new StaffGroup \relative
-<<
- \new Staff {
- \set Staff.instrumentName =
- \markup { \hcenter-in #10 "blabla" }
- c1 c1
- }
- \new Staff {
- \set Staff.instrumentName =
- \markup { \hcenter-in #10 "blo" }
- c1 c1
- }
->>
-@end lilypond
+Short instrument names, printed before the systems following the first
+one, are also centered by default, in a space which width is given by
+the @code{short-indent} variable of the @code{\layout} block.
To add instrument names to other contexts (such as
@code{GrandStaff}, @code{ChoirStaff}, or @code{StaffGroup}), the
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,
@lilypond[quote,fragment,verbatim,ragged-right]
@seealso
-Internals Reference: @internalsref{InstrumentName}.
+Notation Reference: @ref{Modifying context plug-ins}.
+
+Snippets: @lsrdir{Staff,Staff-notation}
+
+Internals Reference: @internalsref{InstrumentName},
+@internalsref{PianoStaff}, @internalsref{Staff}.
@node Quoting other voices
-@unnumberedsubsubsec Quoting other voices
+@subsubsection Quoting other voices
@cindex cues
+@cindex quoting other voices
+@cindex fragments
+@cindex cue notes
With quotations, fragments of other parts can be inserted into a
part directly. Before a part can be quoted, it must be marked
@refbugs
-Only the contents of the first @internalsref{Voice} occurring in
-an @code{\addQuote} command will be considered for quotation, so
+Only the contents of the first @code{Voice} occurring in an
+@code{\addQuote} command will be considered for quotation, so
@var{music} can not contain @code{\new} and @code{\context Voice}
statements that would switch to a different Voice.
@seealso
-In this manual: @ref{Instrument transpositions}.
+Notation Reference: @ref{Instrument transpositions}.
-Examples: @lsr{parts,quote.ly},
-@lsr{parts,quote-transportation.ly}
+Snippets: @lsrdir{Staff,Staff-notation}
-Internals Reference: @internalsref{QuoteMusic}.
+Internals Reference: @internalsref{QuoteMusic}, @internalsref{Voice}.
@node Formatting cue notes
-@unnumberedsubsubsec Formatting cue notes
+@subsubsection Formatting cue notes
+@cindex cues
+@cindex cue notes
+@cindex cue notes, formatting
+@cindex fragments
+@cindex quoting other voices
@cindex cues, formatting
The previous section deals with inserting notes from another
@end example
This will insert notes from the part @var{name} into a
-@internalsref{Voice} called @code{cue}. This happens
+@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
@end lilypond
-Here are a couple of hints for successful cue notes
+Here are a couple of hints for successful cue notes:
@itemize
@item
Cue notes have smaller font sizes.
@item
-the cued part is marked with the instrument playing the cue.
+The cued part is marked with the instrument playing the cue.
@item
-when the original part takes over again, this should be marked
+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
undone. For example, if the cued instrument plays in a different
clef, the original clef should be stated once again.
>>
@end lilypond
+@seealso
+Snippets: @lsrdir{Staff,Staff-notation}.
-
+Internals Reference: @internalsref{Voice}.
projects / lilypond.git / blobdiff