@c -*- coding: utf-8; mode: texinfo; -*- @c This file is part of lilypond.tely @ignore Translation of GIT committish: FILL-IN-HEAD-COMMITTISH When revising a translation, copy the HEAD committish of the version that you are working on. See TRANSLATION for details. @end ignore @c A menu is needed before every deeper *section nesting of @node's; run @c M-x texinfo-all-menus-update @c to automatically fill in these menus before saving changes @node Basic notation @chapter Basic notation This chapter explains how to use basic notation features. @menu * Staff notation:: * Connecting notes:: * Expressive marks old:: @end menu @node Staff notation @section Staff notation @cindex Staff notation This section describes music notation that occurs on staff level, such as key signatures, clefs and time signatures. @menu * Clef:: * Key signature:: * Time signature:: * Bar lines:: * Unmetered music:: * System start delimiters:: * Staff symbol:: * Writing music in parallel:: @end menu @anchor{System start delimiters} @unnumberedsubsubsec System start delimiters @cindex start of system @cindex Staff, multiple @cindex bracket, vertical @cindex brace, vertical @cindex grand staff @cindex staff group @cindex staff, choir Many scores consist of more than one staff. These staves can be joined in four different ways @itemize @bullet @item The group is started with a brace at the left, and bar lines are connected. This is done with the @internalsref{GrandStaff} context. @lilypond[verbatim,ragged-right,quote] \new GrandStaff \relative << \new Staff { c1 c } \new Staff { c c } >> @end lilypond @item The group is started with a bracket, and bar lines are connected. This is done with the @internalsref{StaffGroup} context @lilypond[verbatim,ragged-right,quote] \new StaffGroup \relative << \new Staff { c1 c } \new Staff { c c } >> @end lilypond @item The group is started with a bracket, but bar lines are not connected. This is done with the @internalsref{ChoirStaff} context. @lilypond[verbatim,ragged-right,quote] \new ChoirStaff \relative << \new Staff { c1 c } \new Staff { c c } >> @end lilypond @item The group is started with a vertical line. Bar lines are not connected. This is the default for the score. @lilypond[verbatim,ragged-right,quote] \relative << \new Staff { c1 c } \new Staff { c c } >> @end lilypond @end itemize @seealso The bar lines at the start of each system are @internalsref{SystemStartBar}, @internalsref{SystemStartBrace}, and @internalsref{SystemStartBracket}. Only one of these types is created in every context, and that type is determined by the property @code{systemStartDelimiter}. @commonprop System start delimiters may be deeply nested, @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 @anchor{Staff symbol} @unnumberedsubsubsec Staff symbol @cindex adjusting staff symbol Notes, dynamic signs, 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}. 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 \stopStaff \startStaff b b @end lilypond In combination with Frenched staves, this may be used to typeset ossia sections. An example is shown here @cindex ossia @lilypondfile{ossia.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 Program reference: @internalsref{StaffSymbol}. Examples: @lsrdir{staff} @node Connecting notes @section Connecting notes This section deals with notation that affects groups of notes. @menu * Ties:: * Slurs:: * Phrasing slurs:: * Laissez vibrer ties:: * Automatic beams:: * Manual beams:: * Grace notes:: @end menu @node Expressive marks old @section Expressive marks old Expressive marks help musicians to bring more to the music than simple notes and rhythms. @menu * Articulations:: * Fingering instructions:: * Dynamics:: * Breath marks:: * Trills:: * Glissando:: * Arpeggio:: * Falls and doits:: @end menu @anchor{Fingering instructions} @unnumberedsubsubsec Fingering instructions @cindex fingering @cindex finger change Fingering instructions can be entered using @example @var{note}-@var{digit} @end example For finger changes, use markup texts @lilypond[quote,verbatim,ragged-right,fragment,relative=1] c4-1 c-2 c-3 c-4 c^\markup { \finger "2 - 3" } @end lilypond You can use the thumb-script to indicate that a note should be played with the thumb (e.g., in cello music) @lilypond[quote,verbatim,ragged-right,fragment,relative=2] 8 @end lilypond Fingerings for chords can also be added to individual notes of the chord by adding them after the pitches @lilypond[quote,verbatim,ragged-right,fragment,relative=2] < c-1 e-2 g-3 b-5 >4 @end lilypond @commonprop You may exercise greater control over fingering chords by setting @code{fingeringOrientations} @lilypond[quote,verbatim,ragged-right,fragment,relative=1] \set fingeringOrientations = #'(left down) 4 \set fingeringOrientations = #'(up right down) 4 @end lilypond Using this feature, it is also possible to put fingering instructions very close to note heads in monophonic music, @lilypond[verbatim,ragged-right,quote,fragment] \set fingeringOrientations = #'(right) 4 @end lilypond @seealso Program reference: @internalsref{Fingering}. Examples: @lsr{expressive,fingering-chords.ly}