@funindex \huge
@code{\huge}.
-@snippets
-
@seealso
Snippets: @lsrdir{Editorial,Editorial-annotations}.
Fingering instructions can be entered using
@var{note}-@var{digit}:
-
@lilypond[quote,verbatim,ragged-right,fragment,relative=2]
c4-1 d-2 f-4 e-3
@end lilypond
-Use markup texts for finger changes.
+Markup texts may be used for finger changes.
@lilypond[quote,verbatim,ragged-right,fragment,relative=2]
c4-1 d-2 f-4 c^\markup { \finger "2 - 3" }
@snippets
-@code{fingeringOrientations} are used to control where the fingering
-numbers are placed.
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
+{controlling-the-placement-of-chord-fingerings.ly}
-@lilypond[quote,verbatim,ragged-right,fragment,relative=2]
-\set fingeringOrientations = #'(left)
-<c-1 e-3 a-5 > 4
-\set fingeringOrientations = #'(down)
-<c-1 e-3 a-5 >
-\set fingeringOrientations = #'(right)
-<c-1 e-3 a-5 >
-\set fingeringOrientations = #'(up)
-<c-1 e-3 a-5 >
-\set fingeringOrientations = #'(left down)
-<c-1 e-3 a-5 > 2
-\set fingeringOrientations = #'(up right down)
-<c-1 e-3 a-5 >
-@end lilypond
@seealso
-@ref{Controlling direction and placement}
+
+Notation Reference: @ref{Controlling direction and placement}
Snippets: @lsrdir{Editorial,Editorial-annotations}.
@cindex stem, down
@cindex stem, neutral
-To change the direction of stems on the center line of the staff, use
-
-@lilypond[quote,ragged-right,fragment,relative=2,verbatim]
-a4 b c b
-\override Stem #'neutral-direction = #up
-a4 b c b
-\override Stem #'neutral-direction = #down
-a4 b c b
-@end lilypond
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
+{default-direction-of-stems-on-the-center-line-of-the-staff.ly}
@seealso
-@ref{Controlling direction and placement}.
+Notation Reference: @ref{Controlling direction and placement}.
Snippets: @lsrdir{Editorial,Editorial-annotations}.
\new Voice \with { \consists "Balloon_engraver" }
{
\balloonGrobText #'Stem #'(3 . 4) \markup { "I'm a Stem" }
- a4
+ a8
+ \balloonGrobText #'Rest #' (-4 . -4) \markup { "I'm a rest" }
+ r
<c, g'-\balloonText #'(-2 . -2) \markup { "I'm a note head" } c>2.
}
@end lilypond
@snippets
-To change the grid lines use \override.
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
+{grid-lines-changing-their-appearance.ly}
-@lilypond[quote,verbatim,ragged-right]
-\layout {
- \context {
- \Staff
- \consists "Grid_point_engraver"
- gridInterval = #(ly:make-moment 1 4)
- }
-}
-
-\new Score \with {
- \consists "Grid_line_span_engraver"
- % this moves them to the right half a staff space
- \override NoteColumn #'X-offset = #-0.5
- }
-
-\new ChoirStaff <<
- \new Staff {
- \relative c'' {
- \stemUp
- c'4. d8 e8 f g4
- }
- }
- \new Staff {
- \relative c {
- % this moves them up one staff space from the default position
- \override Score.GridLine #'extra-offset = #'( 0.0 . 1.0 )
- \stemDown
- \clef bass
- \once \override Score.GridLine #'thickness = #5.0
- c4
- \once \override Score.GridLine #'thickness = #1.0
- g'
- \once \override Score.GridLine #'thickness = #3.0
- f
- \once \override Score.GridLine #'thickness = #5.0
- e
- }
- }
->>
-@end lilypond
@seealso
line with either a bracket or a brace.
@menu
-* Initiating new staves::
-* Grouping staves::
+* Instantiating new staves::
+* Grouping staves::
+* Deeper nested staff groups::
@end menu
-@node Initiating new staves
-@subsubsection Initiating new staves
+@node Instantiating new staves
+@subsubsection 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 transciption staff
+@cindex rhythmic staff
+@cindex tabstaff
+@cindex tablature
-The lines of a staff (pl. staves) are produced by a @code{staff symbol}
-layout object.
-LilyPond ensures that all music is printed on staff lines so if you just
-type in some notes, the staff symbol is added automatically to the output.
-This is just a shortcut to make the program usage more easy, but in most
-cases where you want to print more complex music on more than on staff
-it is better to create the staff explicitly at the beginning of your
-music inside of the @code{\score} environment.
+The lines of a staff (pl. staves) are produced by the @code{staff symbol}
+layout object. Staves are created with the @code{\new} or
+@code{\context} commands. For an explanation on these commands,
+see @ref{Creating contexts}.
-With the command @code{\new Staff @{ ... @}} you actually call a new
-Staff context that has already everything set up to the default
-engraving rules. @ref{Creating contexts} explains how different contexts
-are called.
+There are different predefined staff contexts available in Lilypond:
+
+@itemize
+@item
+The default is @code{Staff}:
+@lilypond[verbatim,ragged-right,quote]
+\relative c'' {
+ \new Staff { c d e f }
+}
+@end lilypond
+
+@item
+@code{DrumStaff} creates a five line staff set up for a typical drum set.
+It uses different names for each instrument. The instrument names have to
+be set using the @code{drummode}. See @ref{Percussion staves}.
+@lilypond[verbatim,ragged-right,quote]
+\new DrumStaff {
+ \drummode { cymc hh ss tomh }
+}
+@end lilypond
+
+@item
+@code{GregorianTranscriptionStaff} sets up a staff to notate modern
+Gregorian chant. It does not show bar lines.
+@lilypond[verbatim,ragged-right,quote]
+\relative c'' {
+ \new GregorianTranscriptionStaff { c d e f }
+}
+@end lilypond
+
+@item
+@code{RhythmicStaff} can be used to show the rhythm of some music. The
+notes are printed on one line regardless of their pitch, but the duration
+is preserved. See @ref{Showing melody rhythms}.
+@lilypond[verbatim,ragged-right,quote]
+\relative c'' {
+ \new RhythmicStaff { c d e f }
+}
+@end lilypond
+
+@item
+@code{TabStaff} creates by default a tabulature with six strings in
+standard guitar tuning. See @ref{Tablatures basic}.
+@lilypond[verbatim,ragged-right,quote]
+\relative c'' {
+ \new TabStaff { c d e f }
+}
+@end lilypond
+
+@end itemize
+
+@noindent
+Besides these staves 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}.
Once a staff is instantiated it can be started or stopped at every point
in the score. This is done with the commands @code{\startStaff} and
-@code{\stopStaff}. How to use it is shown in @ref{Staff symbol}.
+@code{\stopStaff}. How to use it is explained in @ref{Staff symbol}.
-Besides the default @code{Staff} context there are also
-specialized staff contexts for setting percussion, Guitar music,
-and ancient music.
-See @ref{Printing chord names}, @ref{Percussion staves},
-@ref{Tablatures basic}, @ref{Gregorian Chant contexts}, and
-@ref{Mensural contexts} for an explanation.
@seealso
Music Glossary: @rglos{staff}, @rglos{staves}.
-Notation Reference: @ref{Printing chord names}, @ref{Percussion staves},
+Notation Reference: @ref{Percussion staves},
@ref{Tablatures basic}, @ref{Gregorian Chant contexts}, and
@ref{Mensural contexts}.
Snippets: @lsrdir{Staff,Staff-notation}.
-Internals Reference: @internalsref{Staff}.
+Internals Reference: @internalsref{Staff}, @internalsref{DrumStaff},
+@internalsref{GregorianTranscriptionStaff}, @internalsref{RhythmicStaff},
+@internalsref{TabStaff}, @internalsref{MensuralStaff},
+@internalsref{VaticanaStaff}.
of the system start delimiter, but they have also influence on the
behaviour of the bar lines.
+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. The usage of this last delimiter is shown in the
+snippet section in @ref{Deeper nested staff groups}.
+
@itemize
@item
optimized for setting piano music.
@lilypond[verbatim,ragged-right,quote]
-\new PianoStaff
-\relative c'' <<
- \new Staff { c1 c }
- \new Staff { c c }
->>
+\new PianoStaff {
+ \relative c'' <<
+ \new Staff { c1 c }
+ \new Staff { c c }
+ >>
+}
@end lilypond
@end itemize
As the context names tell, @code{PianoStaff} is used for notating
piano music and @code{ChoirStaff} for all kind of vocal ensemble music.
-Here is an example of an orchestral score using groupings. Note that the
-instrument names are omited here, see @ref{Instrument names} how to set
-them.
-
-@lilypond[verbatim,ragged-right,quote]
-\score{ \relative c' {
-<<
- \new StaffGroup %the woodwinds group
- <<
- \new Staff { c1 c }
- \new Staff { c c }
- \new Staff { c c }
- >>
- \new StaffGroup %the brass group
- <<
- \new Staff { c c }
- \new Staff { c c }
- \new GrandStaff %the horns need a GrandStaff (same instrument)
- <<
- \new Staff { c c }
- \new Staff {\clef bass c c }
- >>
- >>
- \new ChoirStaff %for a vocal part
- <<
- \new Staff { c c }
- \new Staff {\clef alto c c }
- \new Staff {\clef bass c c }
- >>
- \new PianoStaff %for the piano
- <<
- \new Staff { c c }
- \new Staff {\clef bass c c }
- >>
->>
-} }
-@end lilypond
-
-The different staff contexts are already nested in this example, as
-the @q{horn section} is contained both in a @code{StaffGroup} and a
-@code{GrandStaff}.
-
-@cindex staff, nested
-
-It is also possible to nest staves of the same type with the contexts
-@code{InnerStaffGroup} and @code{InnerChoirStaffGroup}. These behave like
-the corresponding normal staff groups but can only initiated inside of
-another staff context. Again LilyPond would add a normal @code{StaffGroup}
-to the output, if you would start a score with an @code{InnerStaffGroup}.
-
-Note that @code{GrandStaff} and @code{PianoStaff} do not have any inner
-grouping contexts. They can both be inside an inner staff context, though.
-
-@c snippet staff-brackets.ly
-@lilypond[verbatim,ragged-right,quote]
-\score {
-<<
- \new StaffGroup <<
- \new Staff {c' d' e' f'}
- \new InnerStaffGroup <<
- \new Staff {c' d' e' f'}
- \new GrandStaff <<
- \new Staff {c' d' e' f'}
- \new Staff {c' d' e' f'}
- >>
- \new Staff {c' d' e' f'}
- >>
- \new ChoirStaff <<
- \new Staff {c' d' e' f'}
- \new InnerStaffGroup <<
- \new Staff {c' d' e' f'}
- >>
- \new Staff {c' d' e' f'}
- >>
- >>
- \new ChoirStaff <<
- \new Staff {c' d' e' f'}
- \new InnerChoirStaff <<
- \new Staff {c' d' e' f'}
- \new Staff {c' d' e' f'}
- >>
- \new Staff {c' d' e' f'}
- >>
->> }
-@end lilypond
-
@snippets
-@c FIXME: not yet in master
+@c FIXME: Graham will deal with this. -gp
+@c snippet 201
+To display a bracket even if there is only one staff, see
@c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
-@c {nesting-staves.ly}
-
-
-More complex nesting can be accomplished using the property
-@code{systemStartDelimiterHierarchy}:
-
-@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 }
->>
+@c {staff,display-bracket-with-only-one-staff-in-a system.ly}
+@lilypond[verbatim,ragged-right,quote]
+\score {
+ \new StaffGroup <<
+ % Must be one lower than your actual amount off staff lines
+ \override StaffGroup.SystemStartBracket #'collapse-height = #4
+ \new Staff {
+ c'4 d' e' f'
+ }
+ >>
+ }
+ {
+ \new PianoStaff <<
+ \override PianoStaff.SystemStartBrace #'collapse-height = #4
+ \new Staff {
+ c'4 d' e' f'
+ }
+ >>
+ }
@end lilypond
-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
-
-
@cindex mensurstriche layout
@cindex renaissance music
@end lilypond
-
-@c FIXME: Graham will deal with this. -gp
-@c snippet 201
-To display a bracket even if there is only one staff, see
-@c @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
-@c {staff,display-bracket-with-only-one-staff-in-a system.ly}
-
@seealso
Music Glossary: @rglos{brace},
Snippets: @lsrdir{Staff,Staff-notation}
Internals Reference: @internalsref{ChoirStaff},
-@internalsref{GrandStaff}, @internalsref{PianoStaff},
-@internalsref{StaffGroup},
+@internalsref{GrandStaff}, @internalsref{StaffGroup},
@internalsref{SystemStartBar}, @internalsref{SystemStartBrace},
-@internalsref{SystemStartBracket}, @internalsref{SystemStartSquare}.
+@internalsref{SystemStartBracket}.
+
+
+
+@node Deeper nested staff groups
+@subsubsection Deeper nested staff groups
+
+There are also two inner staff contexts named @code{InnerStaffGroup}
+and @code{InnerChoirStaffGroup} besides the grouping contexts mentioned
+in @ref{Grouping staves}. They behave in the same way as their simple
+counterparts, except that they are contained in another staff grouping
+context, thus producing one more bracket on top of the existing one.
+Note that @code{GrandStaff} and @code{PianoStaff} do not have any inner
+grouping contexts. They can both be inside any other staff context,
+including inner staff groups, though.
+
+Here is an example of an orchestral score using groupings and nesting
+of these groupings. Note that the instrument names are omited from the
+source code, see @ref{Instrument names} how to set them.
+
+
+@cindex staff, nested
+@cindex staves, nested
+@cindex nesting of staves
+
+
+@example
+\score @{ <<
+ \new StaffGroup %woodwinds
+ <<
+ \new Staff @{ c'1 d' @} %flute
+ \new InnerStaffGroup <<
+ \new Staff @{ c' d' @} %sax
+ \new Staff @{ c' d' @} %oboe
+ \new Staff @{ c' d' @} %English horn
+ >>
+ \new Staff @{ \clef bass c d @} %bassoon
+ >>
+ \new StaffGroup %the brass group
+ <<
+ \new Staff @{ c' d' @} %trumpet
+ \new Staff @{ \clef bass c d @} %trombone
+ \new GrandStaff %the horns need a GrandStaff (same instrument)
+ <<
+ \new Staff @{ c' d' @}
+ \new Staff @{ \clef bass c d @}
+ >>
+ >>
+ \new ChoirStaff %for setting vocal music
+ <<
+ \new Staff @{ c' d' @}
+ \new InnerChoirStaff <<
+ \new Staff @{ c' d' @}
+ \new Staff @{ c' d' @}
+ >>
+ \new Staff @{ c' d' @}
+ >>
+ \new PianoStaff %for the piano
+ <<
+ \new Staff @{ c' d' @}
+ \new Staff @{\clef bass c d @}
+ >>
+>> @}
+@end example
+
+@c no verbatim so instrument names are only in the music
+@lilypond[ragged-right,quote]
+\score { <<
+ \new StaffGroup %woodwinds
+ <<
+ \new Staff {\set Staff.instrumentName = "fl" c'1 d' } %flute
+ \new InnerStaffGroup <<
+ \new Staff { \set Staff.instrumentName = "sax" c' d' } %sax 1
+ \new Staff { \set Staff.instrumentName = "ob" c' d' } %sax 2
+ \new Staff { \set Staff.instrumentName = "ca" c' d' }
+ >>
+ \new Staff {\set Staff.instrumentName = "bs" \clef bass c d } %bassoon
+ >>
+ \new StaffGroup %the brass group
+ <<
+ \new Staff {\set Staff.instrumentName = "tr" c' d' } %trumpet
+ \new Staff {\set Staff.instrumentName = "tb" \clef bass c d } %trombone
+ \new GrandStaff %the horns need a GrandStaff (same instrument)
+ <<
+ \new Staff {\set Staff.instrumentName = "cor1" c' d' }
+ \new Staff {\set Staff.instrumentName = "cor2" \clef bass c d }
+ >>
+ >>
+ \new ChoirStaff %for setting vocal music
+ <<
+ \new Staff {\set Staff.instrumentName = "S" c' d' }
+ \new InnerChoirStaff <<
+ \new Staff {\set Staff.instrumentName = "A1" c' d' }
+ \new Staff {\set Staff.instrumentName = "A2" c' d' }
+ >>
+ \new Staff {\set Staff.instrumentName = "T" c' d' }
+ >>
+ \new PianoStaff %for the piano
+ <<
+ \new Staff { c' d' }
+ \new Staff {\clef bass c d }
+ >>
+>> }
+@end lilypond
+
+
+@snippets
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
+{nesting-staves.ly}
+
+
+@seealso
+
+Internals Reference: @internalsref{SystemStartBar},
+@internalsref{SystemStartBrace}, @internalsref{SystemStartBracket},
+@internalsref{systemStartDelimiterHierarchy}.
@subsection Modifying single staves
@menu
-* Staff symbol::
-* Ossia staves::
-* Hiding staves::
+* Staff symbol::
+* Ossia staves::
+* Hiding staves::
@end menu
@node Staff symbol
@subsubsection Staff symbol
@cindex adjusting staff symbol
+@cindex drawing staff symbol
+@cindex stop staff lines
+@cindex start staff lines
+@cindex staff lines, amount of
+@cindex staff line, thickness of
+@cindex amount of staff lines
+@cindex thickness of staff lines
The layout object which draws the lines of a staff is called
@code{staff symbol}. The staff symbol may be tuned in the number,
@cindex thickness of staff lines, setting
@cindex number of staff lines, setting
+@snippets
+
+@c lilypondfile{Making-some-staff-lines-thicker-than-the-others.ly}
+@c snippet 277
+
@seealso
Music Glossary: @rglos{ossia}, @rglos{staff}, @rglos{Frenched staff}.
action='store', dest='output_dir',
default='')
+ p.add_option ('--skip-lily-check',
+ help=_ ("do not fail if no lilypond output is found."),
+ metavar=_ ("DIR"),
+ action='store_true', dest='skip_lilypond_run',
+ default=False)
+
+ p.add_option ('--skip-png-check',
+ help=_ ("do not fail if no PNG images are found for EPS files"),
+ metavar=_ ("DIR"),
+ action='store_true', dest='skip_png_check',
+ default=False)
+
p.add_option ('--lily-output-dir',
help=_ ("write lily-XXX files to DIR, link into --output dir."),
metavar=_ ("DIR"),
return re.sub (r'\\(version|sourcefileline|sourcefilename)[^\n]*\n', '', ly)
def link_all_output_files (self, output_dir, output_dir_files, destination):
- existing = self.all_output_files (output_dir, output_dir_files)
+ existing, missing = self.all_output_files (output_dir, output_dir_files)
+ if missing:
+ print '\nMissing', missing
+ raise CompileError(self.basename())
for name in existing:
try:
os.unlink (os.path.join (destination, name))
output_dir_files is the list of files in the output directory.
"""
- class Missing(Exception):
- pass
-
- result = set()
+ result = set ()
+ missing = set ()
base = self.basename()
full = os.path.join (output_dir, base)
def consider_file (name):
if name in output_dir_files:
result.add (name)
-
+
def require_file (name):
- if name not in output_dir_files:
- raise Missing
- result.add (name)
-
- try:
- for required in [base + '.ly',
- base + '.txt',
- base + '-systems.count']:
- require_file (required)
-
- map (consider_file, [base + '.tex',
- base + '.eps',
- base + '.texidoc',
- base + '-systems.texi',
- base + '-systems.tex',
- base + '-systems.pdftexi'])
-
- if base + '.eps' in result and self.format in (HTML, TEXINFO):
- page_count = ps_page_count (full + '.eps')
- if page_count <= 1:
- require_file (base + '.png')
- else:
- for page in range (1, page_count + 1):
- require_file (base + '-page%d.png' % page)
+ if name in output_dir_files:
+ result.add (name)
+ else:
+ missing.add (name)
+
+ # UGH - junk global_options
+ skip_lily = global_options.skip_lilypond_run
+ for required in [base + '.ly',
+ base + '.txt']:
+ require_file (required)
+ if not skip_lily:
+ require_file (base + '-systems.count')
+
+ map (consider_file, [base + '.tex',
+ base + '.eps',
+ base + '.texidoc',
+ base + '-systems.texi',
+ base + '-systems.tex',
+ base + '-systems.pdftexi'])
+
+ # UGH - junk global_options
+ if (base + '.eps' in result and self.format in (HTML, TEXINFO)
+ and not global_options.skip_png_check):
+ page_count = ps_page_count (full + '.eps')
+ if page_count <= 1:
+ require_file (base + '.png')
+ else:
+ for page in range (1, page_count + 1):
+ require_file (base + '-page%d.png' % page)
+ system_count = 0
+ if not skip_lily and not missing:
system_count = int(file (full + '-systems.count').read())
- for number in range(1, system_count + 1):
- systemfile = '%s-%d' % (base, number)
- require_file (systemfile + '.eps')
- consider_file (systemfile + '.pdf')
- except Missing:
- return None
+ for number in range(1, system_count + 1):
+ systemfile = '%s-%d' % (base, number)
+ require_file (systemfile + '.eps')
+ consider_file (systemfile + '.pdf')
- return result
+ return (result, missing)
def is_outdated (self, output_dir, current_files):
- return self.all_output_files (output_dir, current_files) is None
+ found, missing = self.all_output_files (output_dir, current_files)
+ return missing
def filter_text (self):
"""Run snippet bodies through a command (say: convert-ly).
This functionality is rarely used, and this code must have bitrot.
"""
-
code = self.substring ('code')
s = filter_pipe (code, global_options.filter_cmd)
d = {
def find_toplevel_snippets (input_string, format, types):
res = {}
for t in types:
- res[t] = ly.re.compile (snippet_res[format][t])
+ res[t] = re.compile (snippet_res[format][t])
snippets = []
index = 0
projects / lilypond.git / commitdiff