X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fuser%2Fstaff.itely;h=b1d47765da5a93a44bc020566946c2f4b257938f;hb=9e7b53f94e1e3bd7b3f7a14ba11a6cae6c8e9a73;hp=fab1f62cb51bd515fbe3acfe32cfc4e5ef2c2679;hpb=23efbcbaa7dab9303faec9fc0aca4fec805e550c;p=lilypond.git diff --git a/Documentation/user/staff.itely b/Documentation/user/staff.itely index fab1f62cb5..b1d47765da 100644 --- a/Documentation/user/staff.itely +++ b/Documentation/user/staff.itely @@ -9,14 +9,16 @@ @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 @@ -35,22 +37,23 @@ Two or more staves can be grouped vertically in a @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] @@ -62,7 +65,7 @@ at the left, and bar lines are connected between the staves. @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] @@ -74,7 +77,7 @@ all the staves, but the group is started with a bracket. @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] @@ -98,25 +101,28 @@ bar lines are not connected. @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 @@ -132,24 +138,34 @@ More complex nesting can be accomplished using the property >> @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. - -@commonprop +instantiated manually -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 @@ -157,8 +173,8 @@ 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}. +@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}. @@ -173,12 +189,13 @@ b b 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 @@ -218,26 +235,29 @@ In combination with Frenched staves, this may be used to typeset @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 @@ -258,7 +278,7 @@ the second staff in this example disappears in the second line 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 @@ -268,6 +288,8 @@ To remove other types of contexts, use @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 @@ -289,6 +311,16 @@ You can make the staff lines invisible by removing the } @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 @@ -300,7 +332,7 @@ You can make the staff lines invisible by removing the @end menu @node Metronome marks -@unnumberedsubsubsec Metronome marks +@subsubsection Metronome marks @cindex Tempo @cindex beats per minute @@ -344,6 +376,13 @@ For more details, see @ref{Text markup}. @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}. @@ -362,20 +401,23 @@ place it further away from the staff. @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 " @@ -395,6 +437,8 @@ instrument names, for example c''1 @end lilypond +@cindex instrument names, centering + If you wish to center the instrument names, you must center all of them individually: @@ -450,6 +494,8 @@ engraver must be added to that context. 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] @@ -466,13 +512,21 @@ c1 c c c \break @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 @@ -565,8 +619,8 @@ dynamics. @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. @@ -580,17 +634,21 @@ written entirely in lower-case letters: @code{\addquote}. @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 @@ -604,7 +662,7 @@ The syntax is @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 @@ -642,19 +700,20 @@ smaller = { @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. @@ -688,8 +747,10 @@ cbsn = \relative c, { >> @end lilypond +@seealso +Snippets: @lsrdir{Staff,Staff-notation}. - +Internals Reference: @internalsref{Voice}.