<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- header_tag -->
<html lang="en">
<head>
<title>collated-files.tely</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="collated-files.tely">
<meta name="generator" content="makeinfo 4.11">
<link title="Top" rel="top" href="#Top">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
hr { border:0; height:1; color: #000000; background-color: #000000; }
/* hr {
border: none;
height: 1px;
color: #666666;
background-color: #666666;
}
body {
border-left: 1px solid #666666;
border-right: 1px solid #666666;
color: #332d28;
margin-right: auto;
margin-left: auto;
width: 60em;
list-style-type: square;
font-family: Arial,Helvetica,sans-serif;
padding-right: 1em;
padding-left: 1em;
}
a {
border-bottom: 1px dashed #344242;
text-decoration: none;
color: #344242;
}
a:link {
text-decoration: none;
}
a:visited {
border-bottom: 1px dashed #666666;
color: #666666;
}
a:active {
border-bottom: 1px solid #00cccc;
color: #00cccc;
}
a:hover {
border-bottom: 1px solid #1d7b85;
color: #1d7b85;
}
blockquote {
border: 1px solid #cccccc;
padding: 3px;
width: 40em;
}
.node {
border-left: 1px solid #666666;
margin: -0.5em 0px 1em;
padding: 2px 1px 0px;
font-style: italic;
}
.node a {
border: none;
text-decoration: underline;
font-style: normal;
font-weight: bold;
}
.verbatim {
font-family: "Courier New",Courier,monospace;
}
.unnumberedsubsubsec {
font-size: large;
color: #1d7b85;
}
.subsubheading {
font-size: large;
color: #3b220d;
}
.contents {
border: 1px dashed #339999;
margin: 3px 2em;
list-style-type: square;
padding-right: 1em;
width: 40em;
background-color: #fcfff9;
}
.contents a {
border-bottom: 1px dashed #423d34;
text-decoration: none;
color: #423d34;
}
.contents a:visited {
border-bottom: 1px dashed #666666;
color: #666666;
}
.contents a:active {
border-bottom: 1px solid #f0d86d;
color: #f0d86d;
}
.contents a:hover {
border-bottom: 1px solid #3b220d;
color: #3b220d;
}
.menu {
border-left: 1px dashed #339999;
margin: 3px 2em 1em;
list-style-type: square;
padding-left: 1.4em;
width: 40em;
}
.unnumbered {
}
h2 {
font-size: x-large;
color: #1d7b85;
}
*/
--></style>
</head>
<BODY BGCOLOR=WHITE TEXT=BLACK>
<a name="Top"></a>
<p><a name="AAA-intro-regression.ly"></a>
<p><a href="12/lily-cd9b2dc7.ly"><samp><span class="file">AAA-intro-regression.ly</span></samp>
</a>
<h2 class="unnumbered">Introduction</h2>
<p>This document presents proofs for
LilyPond 2.11.57. When the
text corresponds with the shown notation, we consider LilyPond Officially
BugFree (tm). This document is intended for finding bugs and for
documenting bugfixes.
<p>In the web version of this document, you can click on the file name
or figure for each example to see the corresponding input file.
<p>TODO: order of tests (file names!), test only one feature per test.
Smaller and neater tests.
<p class="noindent"><p>
<a href="12/lily-cd9b2dc7.ly">
<img align="middle"
border="0" src="12/lily-cd9b2dc7.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-ancient.ly"></a>
<p><a href="9f/lily-4712fb2c.ly"><samp><span class="file">accidental-ancient.ly</span></samp>
</a>
<p><a name="index-Ancient-Accidentals-1"></a>Accidentals are available in different ancient styles, which all
are collected here.
<p class="noindent"><p>
<a href="9f/lily-4712fb2c.ly">
<img align="middle"
border="0" src="9f/lily-4712fb2c.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-broken-tie-spacing.ly"></a>
<p><a href="b6/lily-0712b40b.ly"><samp><span class="file">accidental-broken-tie-spacing.ly</span></samp>
</a>
<p>When a tie is broken, the spacing engine must consider the
accidental after the line break, to prevent a collision from occurring.
<p>
<a href="b6/lily-0712b40b.ly">
<img align="middle"
border="0" src="b6/lily-0712b40b.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-cautionary.ly"></a>
<p><a href="e1/lily-f20a3642.ly"><samp><span class="file">accidental-cautionary.ly</span></samp>
</a>
<p>Cautionary accidentals may be indicated using either
parentheses (default) or smaller accidentals.
<p class="noindent"><p>
<a href="e1/lily-f20a3642.ly">
<img align="middle"
border="0" src="e1/lily-f20a3642.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-clef-change.ly"></a>
<p><a href="47/lily-47d51904.ly"><samp><span class="file">accidental-clef-change.ly</span></samp>
</a>
<p>Accidentals are reset for clef changes.
<p>
<a href="47/lily-47d51904.ly">
<img align="middle"
border="0" src="47/lily-47d51904.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-collision.ly"></a>
<p><a href="fb/lily-3c69ced8.ly"><samp><span class="file">accidental-collision.ly</span></samp>
</a>
<p>accidentals avoid stems of other notes too.
<p>
<a href="fb/lily-3c69ced8.ly">
<img align="middle"
border="0" src="fb/lily-3c69ced8.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-double.ly"></a>
<p><a href="5f/lily-c25eb0b2.ly"><samp><span class="file">accidental-double.ly</span></samp>
</a>
<p>If two forced accidentals happen at the same time, only one
sharp sign is printed.
<p>
<a href="5f/lily-c25eb0b2.ly">
<img align="middle"
border="0" src="5f/lily-c25eb0b2.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-forced-tie-barline.ly"></a>
<p><a href="92/lily-9b22cc2b.ly"><samp><span class="file">accidental-forced-tie-barline.ly</span></samp>
</a>
<p>Cautionary accidentals applied to tied notes after a
bar line are valid for the whole measure.
<p>
<a href="92/lily-9b22cc2b.ly">
<img align="middle"
border="0" src="92/lily-9b22cc2b.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-forced-tie.ly"></a>
<p><a href="70/lily-a72d6825.ly"><samp><span class="file">accidental-forced-tie.ly</span></samp>
</a>
<p>Accidentals can be forced with ! and ? even if the notes are tied.
<p>
<a href="70/lily-a72d6825.ly">
<img align="middle"
border="0" src="70/lily-a72d6825.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-ledger.ly"></a>
<p><a href="9e/lily-2bcdf112.ly"><samp><span class="file">accidental-ledger.ly</span></samp>
</a>
<p>Ledger lines are shortened when there are accidentals.
This happens only for the single ledger line close to the note head,
and only if the accidental is horizontally close to the head.
<p>
<a href="9e/lily-2bcdf112.ly">
<img align="middle"
border="0" src="9e/lily-2bcdf112.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-octave.ly"></a>
<p><a href="08/lily-e133592d.ly"><samp><span class="file">accidental-octave.ly</span></samp>
</a>
<p>This shows how accidentals in different octaves are handled. The note names
are also automatically printed but the octavation has been dropped out.
<p class="noindent"><p>
<a href="08/lily-e133592d.ly">
<img align="middle"
border="0" src="08/lily-e133592d.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-piano.ly"></a>
<p><a href="d7/lily-c8534915.ly"><samp><span class="file">accidental-piano.ly</span></samp>
</a>
<p>In piano accidental style, notes in both staves
influence each other. In this example, each note should have an
accidental.
<p>
<a href="d7/lily-c8534915.ly">
<img align="middle"
border="0" src="d7/lily-c8534915.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-placement.ly"></a>
<p><a href="91/lily-e366e051.ly"><samp><span class="file">accidental-placement.ly</span></samp>
</a>
<p>Accidentals are placed as closely as possible.
Accidentals in corresponding octaves are aligned.
The top accidental should be nearest to the chord. The
flats in a sixth should be staggered.
<p>
<a href="91/lily-e366e051.ly">
<img align="middle"
border="0" src="91/lily-e366e051.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-quarter.ly"></a>
<p><a href="3b/lily-dd9f0e5a.ly"><samp><span class="file">accidental-quarter.ly</span></samp>
</a>
<p>Quarter tone notation is supported, including
threequarters flat.
<p>
<a href="3b/lily-dd9f0e5a.ly">
<img align="middle"
border="0" src="3b/lily-dd9f0e5a.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-single-double.ly"></a>
<p><a href="7e/lily-27d10a70.ly"><samp><span class="file">accidental-single-double.ly</span></samp>
</a>
<p>A sharp sign after a double sharp sign, as well as a flat sign
after a double flat sign is automatically prepended with a
natural sign.
<p class="noindent"><p>
<a href="7e/lily-27d10a70.ly">
<img align="middle"
border="0" src="7e/lily-27d10a70.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-suggestions.ly"></a>
<p><a href="2f/lily-6334bec3.ly"><samp><span class="file">accidental-suggestions.ly</span></samp>
</a>
<p>setting the <code>suggestAccidentals</code> will print
accidentals vertically relative to the note. This is useful for
denoting Musica Ficta.
<p>
<a href="2f/lily-6334bec3.ly">
<img align="middle"
border="0" src="2f/lily-6334bec3.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-tie.ly"></a>
<p><a href="30/lily-81ce8ffd.ly"><samp><span class="file">accidental-tie.ly</span></samp>
</a>
<p>The second and third notes should not get accidentals,
because they are tied to a note. However, an accidental is
present if the line is broken at the tie, which happens for the G
sharp.
<p>
<a href="30/lily-81ce8ffd.ly">
<img align="middle"
border="0" src="30/lily-81ce8ffd.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-unbroken-tie-spacing.ly"></a>
<p><a href="f1/lily-612492e3.ly"><samp><span class="file">accidental-unbroken-tie-spacing.ly</span></samp>
</a>
<p>Tied accidentaled notes (which cause reminder accidentals) do not
wreak havoc in the spacing when unbroken.
<p>
<a href="f1/lily-612492e3.ly">
<img align="middle"
border="0" src="f1/lily-612492e3.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental-voice.ly"></a>
<p><a href="c0/lily-7438df96.ly"><samp><span class="file">accidental-voice.ly</span></samp>
</a>
<p>This shows how modern cross voice auto cautionary accidentals are handled.
The first two fisses get accidentals because they belong to different voices.
The first f gets cautionary natural because of previous measure.
The last f gets cautionary natural because fis was only in the other voice.
<p class="noindent"><p>
<a href="c0/lily-7438df96.ly">
<img align="middle"
border="0" src="c0/lily-7438df96.png" alt="[image of music]">
</a>
</p>
<p><a name="accidental.ly"></a>
<p><a href="b4/lily-989734fd.ly"><samp><span class="file">accidental.ly</span></samp>
</a>
<p>Accidentals work: the second note does not get a sharp. The third and
fourth show forced and courtesy accidentals.
<p class="noindent"><p>
<a href="b4/lily-989734fd.ly">
<img align="middle"
border="0" src="b4/lily-989734fd.png" alt="[image of music]">
</a>
</p>
<p><a name="alignment-order.ly"></a>
<p><a href="11/lily-5e4f67ee.ly"><samp><span class="file">alignment-order.ly</span></samp>
</a>
<p>Newly created contexts can be inserted
anywhere in the vertical alignment.
<p>
<a href="11/lily-5e4f67ee.ly">
<img align="middle"
border="0" src="11/lily-5e4f67ee.png" alt="[image of music]">
</a>
</p>
<p><a name="alignment-vertical-manual-setting.ly"></a>
<p><a href="a4/lily-417b3705.ly"><samp><span class="file">alignment-vertical-manual-setting.ly</span></samp>
</a>
<p>Alignments may be changed pre system by setting
<code>alignment-offsets</code> in the <code>line-break-system-details</code>
property
<p>
<a href="a4/lily-417b3705.ly">
<img align="middle"
border="0" src="a4/lily-417b3705.png" alt="[image of music]">
</a>
</p>
<p><a name="alignment-vertical-spacing.ly"></a>
<p><a href="1d/lily-b7773331.ly"><samp><span class="file">alignment-vertical-spacing.ly</span></samp>
</a>
<p>By setting properties in <code>NonMusicalPaperColumn</code>, vertical
spacing of alignments can be adjusted per system.
<p>By setting <code>alignment-extra-space</code> or
<code>fixed-alignment-extra-space</code> an individual system may be
stretched vertically.
<p>For technical reasons, <code>overrideProperty</code> has to be used for
setting properties on individual object. <code>\override</code> in a
<code>\context</code> block may still be used for global overrides.
<p class="noindent"><p>
<a href="1d/lily-b7773331.ly">
<img align="middle"
border="0" src="1d/lily-b7773331.png" alt="[image of music]">
</a>
</p>
<p><a name="ambitus-pitch-ordering.ly"></a>
<p><a href="4d/lily-e1f01b61.ly"><samp><span class="file">ambitus-pitch-ordering.ly</span></samp>
</a>
<p>Ambituses use actual pitch not lexicographic ordering.
<p>
<a href="4d/lily-e1f01b61.ly">
<img align="middle"
border="0" src="4d/lily-e1f01b61.png" alt="[image of music]">
</a>
</p>
<p><a name="ambitus.ly"></a>
<p><a href="80/lily-9fe57a41.ly"><samp><span class="file">ambitus.ly</span></samp>
</a>
<p>Ambituses indicate pitch ranges for voices.
<p>Accidentals only show up if they're not part of key
signature. <code>AmbitusNoteHead</code> grobs also have ledger lines.
<p class="noindent"><p>
<a href="80/lily-9fe57a41.ly">
<img align="middle"
border="0" src="80/lily-9fe57a41.png" alt="[image of music]">
</a>
</p>
<p><a name="apply-context.ly"></a>
<p><a href="fc/lily-41e89f26.ly"><samp><span class="file">apply-context.ly</span></samp>
</a>
<p>With <code>\applyContext</code>, <code>\properties</code> can be modified
procedurally. Applications include: checking bar numbers, smart
octavation.
<p>This example prints a bar-number during processing on stdout.
<p class="noindent"><p>
<a href="fc/lily-41e89f26.ly">
<img align="middle"
border="0" src="fc/lily-41e89f26.png" alt="[image of music]">
</a>
</p>
<p><a name="apply-output.ly"></a>
<p><a href="f8/lily-1e95a1f0.ly"><samp><span class="file">apply-output.ly</span></samp>
</a>
<p>The <code>\applyOutput</code> expression is the most flexible way to
tune properties for individual grobs.
<p>Here, the layout of a note head is changed depending on its vertical
position.
<p class="noindent"><p>
<a href="f8/lily-1e95a1f0.ly">
<img align="middle"
border="0" src="f8/lily-1e95a1f0.png" alt="[image of music]">
</a>
</p>
<p><a name="arpeggio-bracket.ly"></a>
<p><a href="59/lily-7c3cea36.ly"><samp><span class="file">arpeggio-bracket.ly</span></samp>
</a>
<p>A square bracket on the left indicates that the player should not
arpeggiate the chord.
<p class="noindent"><p>
<a href="59/lily-7c3cea36.ly">
<img align="middle"
border="0" src="59/lily-7c3cea36.png" alt="[image of music]">
</a>
</p>
<p><a name="arpeggio-collision.ly"></a>
<p><a href="c2/lily-6be6d1ec.ly"><samp><span class="file">arpeggio-collision.ly</span></samp>
</a>
<p>Arpeggio stays clear of accidentals and flipped note heads.
<p>
<a href="c2/lily-6be6d1ec.ly">
<img align="middle"
border="0" src="c2/lily-6be6d1ec.png" alt="[image of music]">
</a>
</p>
<p><a name="arpeggio-parenthesis.ly"></a>
<p><a href="d7/lily-e8a6d791.ly"><samp><span class="file">arpeggio-parenthesis.ly</span></samp>
</a>
<p>There is a variant of the arpeggio sign that uses a
`vertical slur' instead of the wiggle.
<p>
<a href="d7/lily-e8a6d791.ly">
<img align="middle"
border="0" src="d7/lily-e8a6d791.png" alt="[image of music]">
</a>
</p>
<p><a name="arpeggio-span-one-staff.ly"></a>
<p><a href="e3/lily-81d9179d.ly"><samp><span class="file">arpeggio-span-one-staff.ly</span></samp>
</a>
<p>Span arpeggios within one staff also work
<p>
<a href="e3/lily-81d9179d.ly">
<img align="middle"
border="0" src="e3/lily-81d9179d.png" alt="[image of music]">
</a>
</p>
<p><a name="arpeggio.ly"></a>
<p><a href="26/lily-c835b42f.ly"><samp><span class="file">arpeggio.ly</span></samp>
</a>
<p>Arpeggios are supported, both cross-staff and broken single staff.
<p class="noindent"><p>
<a href="26/lily-c835b42f.ly">
<img align="middle"
border="0" src="26/lily-c835b42f.png" alt="[image of music]">
</a>
</p>
<p><a name="augmentum.ly"></a>
<p><a href="ce/lily-e282243a.ly"><samp><span class="file">augmentum.ly</span></samp>
</a>
<p>Augmentum dots are accounted for in horizontal spacing.
<p>
<a href="ce/lily-e282243a.ly">
<img align="middle"
border="0" src="ce/lily-e282243a.png" alt="[image of music]">
</a>
</p>
<p><a name="auto-beam-bar.ly"></a>
<p><a href="18/lily-c0910e2d.ly"><samp><span class="file">auto-beam-bar.ly</span></samp>
</a>
<p>No auto beams will be put over (manual) repeat bars.
<p>
<a href="18/lily-c0910e2d.ly">
<img align="middle"
border="0" src="18/lily-c0910e2d.png" alt="[image of music]">
</a>
</p>
<p><a name="auto-beam-beaming-override.ly"></a>
<p><a href="bf/lily-72ba59ab.ly"><samp><span class="file">auto-beam-beaming-override.ly</span></samp>
</a>
<p>Autobeamer remembers <code>subdivideBeams</code> and other
beaming pattern related functions at the start of an autobeam.
<p>
<a href="bf/lily-72ba59ab.ly">
<img align="middle"
border="0" src="bf/lily-72ba59ab.png" alt="[image of music]">
</a>
</p>
<p><a name="auto-beam-no-beam.ly"></a>
<p><a href="8a/lily-fcd8ae6f.ly"><samp><span class="file">auto-beam-no-beam.ly</span></samp>
</a>
<p>The autobeamer may be switched off for a single note
with <code>\noBeam</code>.
<p>
<a href="8a/lily-fcd8ae6f.ly">
<img align="middle"
border="0" src="8a/lily-fcd8ae6f.png" alt="[image of music]">
</a>
</p>
<p><a name="auto-beam-triplet.ly"></a>
<p><a href="6a/lily-f380b6c7.ly"><samp><span class="file">auto-beam-triplet.ly</span></samp>
</a>
<p>Automatic beaming is also done on tuplets.
<p>
<a href="6a/lily-f380b6c7.ly">
<img align="middle"
border="0" src="6a/lily-f380b6c7.png" alt="[image of music]">
</a>
</p>
<p><a name="auto-beam-tuplets.ly"></a>
<p><a href="af/lily-00bc341c.ly"><samp><span class="file">auto-beam-tuplets.ly</span></samp>
</a>
<p>Tuplet-spanner should not put (visible) brackets on
beams even if they're auto generated.
<p>
<a href="af/lily-00bc341c.ly">
<img align="middle"
border="0" src="af/lily-00bc341c.png" alt="[image of music]">
</a>
</p>
<p><a name="auto-beam.ly"></a>
<p><a href="ef/lily-728ebbb1.ly"><samp><span class="file">auto-beam.ly</span></samp>
</a>
<p>Beams are place automatically; the last measure should have a single
beam.
<p>
<a href="ef/lily-728ebbb1.ly">
<img align="middle"
border="0" src="ef/lily-728ebbb1.png" alt="[image of music]">
</a>
</p>
<p><a name="auto-change.ly"></a>
<p><a href="51/lily-1fce8c76.ly"><samp><span class="file">auto-change.ly</span></samp>
</a>
<p>Auto change piano staff switches voices between up
and down staves automatically; rests are switched along with the coming
note. When central C is reached, staff is not yet switched (by default).
<p class="noindent"><p>
<a href="51/lily-1fce8c76.ly">
<img align="middle"
border="0" src="51/lily-1fce8c76.png" alt="[image of music]">
</a>
</p>
<p><a name="backend-excercise.ly"></a>
<p><a href="1e/lily-3e151376.ly"><samp><span class="file">backend-excercise.ly</span></samp>
</a>
<p>Excercise all output functions
<p>
<a href="1e/lily-3e151376.ly">
<img align="middle"
border="0" src="1e/lily-3e151376.png" alt="[image of music]">
</a>
</p>
<p><a name="backend-svg.ly"></a>
<p><a href="0d/lily-6ca2b194.ly"><samp><span class="file">backend-svg.ly</span></samp>
</a> <p>
<a href="0d/lily-6ca2b194.ly">
<img align="middle"
border="0" src="0d/lily-6ca2b194.png" alt="[image of music]">
</a>
</p>
<p><a name="balloon.ly"></a>
<p><a href="0e/lily-603c86f7.ly"><samp><span class="file">balloon.ly</span></samp>
</a>
<p>With balloon texts, objects in the output can be marked,
with lines and explanatory text added.
<p>
<a href="0e/lily-603c86f7.ly">
<img align="middle"
border="0" src="0e/lily-603c86f7.png" alt="[image of music]">
</a>
</p>
<p><a name="bar-check-redefine.ly"></a>
<p><a href="ea/lily-cc0f6012.ly"><samp><span class="file">bar-check-redefine.ly</span></samp>
</a>
<p>The meaning of <code>|</code> is stored in the
identifier <code>pipeSymbol</code>.
<p>
<a href="ea/lily-cc0f6012.ly">
<img align="middle"
border="0" src="ea/lily-cc0f6012.png" alt="[image of music]">
</a>
</p>
<p><a name="bar-line-dashed.ly"></a>
<p><a href="c2/lily-bb34ae84.ly"><samp><span class="file">bar-line-dashed.ly</span></samp>
</a>
<p>The dashes in a dashed bar line covers staff
lines exactly. Dashed barlines between staves start and end on a
half dash precisely.
<p>
<a href="c2/lily-bb34ae84.ly">
<img align="middle"
border="0" src="c2/lily-bb34ae84.png" alt="[image of music]">
</a>
</p>
<p><a name="bar-line-dotted.ly"></a>
<p><a href="81/lily-5aa181ef.ly"><samp><span class="file">bar-line-dotted.ly</span></samp>
</a>
<p>The dots in a dotted bar line are in spaces.
<p>
<a href="81/lily-5aa181ef.ly">
<img align="middle"
border="0" src="81/lily-5aa181ef.png" alt="[image of music]">
</a>
</p>
<p><a name="bar-number.ly"></a>
<p><a href="21/lily-437a980e.ly"><samp><span class="file">bar-number.ly</span></samp>
</a>
<p>Bar numbers may be set and their padding adjusted individually.
The counting of bar numbers is started after the anacrusis.
<p>To prevent clashes at the beginning of a line, the padding may have to
be increased.
<p class="noindent"><p>
<a href="21/lily-437a980e.ly">
<img align="middle"
border="0" src="21/lily-437a980e.png" alt="[image of music]">
</a>
</p>
<p><a name="bar-scripts.ly"></a>
<p><a href="17/lily-98dcef40.ly"><samp><span class="file">bar-scripts.ly</span></samp>
</a>
<p>Markings can be attached to (invisible) barlines.
<p class="noindent"><p>
<a href="17/lily-98dcef40.ly">
<img align="middle"
border="0" src="17/lily-98dcef40.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-auto-knee.ly"></a>
<p><a href="a9/lily-65fc874e.ly"><samp><span class="file">beam-auto-knee.ly</span></samp>
</a>
<p>A knee is made automatically when a horizontal
beam fits in a gap between note heads that is larger than a predefined
threshold.
<p class="noindent"><p>
<a href="a9/lily-65fc874e.ly">
<img align="middle"
border="0" src="a9/lily-65fc874e.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-auto.ly"></a>
<p><a href="80/lily-22dce09d.ly"><samp><span class="file">beam-auto.ly</span></samp>
</a>
<p><a name="index-Beaming-Presets-2"></a>There are presets for the <code>auto-beam</code> engraver in the case of common
time signatures.
<p>
<a href="80/lily-22dce09d.ly">
<img align="middle"
border="0" src="80/lily-22dce09d.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-beamlet-break.ly"></a>
<p><a href="37/lily-2fdf9b15.ly"><samp><span class="file">beam-beamlet-break.ly</span></samp>
</a>
<p>beamlets don't run to end of line if there are no other
beamlets on the same height.
<p>
<a href="37/lily-2fdf9b15.ly">
<img align="middle"
border="0" src="37/lily-2fdf9b15.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-beamlet-grace.ly"></a>
<p><a href="3a/lily-267d7a33.ly"><samp><span class="file">beam-beamlet-grace.ly</span></samp>
</a>
<p>Beamlets in grace notes remain readable.
<p>
<a href="3a/lily-267d7a33.ly">
<img align="middle"
border="0" src="3a/lily-267d7a33.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-beat-grouping.ly"></a>
<p><a href="34/lily-5bf11887.ly"><samp><span class="file">beam-beat-grouping.ly</span></samp>
</a>
<p>Beaming patterns obey the <code>beatGrouping</code> property.
<p>
<a href="34/lily-5bf11887.ly">
<img align="middle"
border="0" src="34/lily-5bf11887.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-break-no-bar.ly"></a>
<p><a href="3c/lily-5ffffe9a.ly"><samp><span class="file">beam-break-no-bar.ly</span></samp>
</a>
<p>Broken beams have sane endings even if grobs
are not present at the broken end.
<p>
<a href="3c/lily-5ffffe9a.ly">
<img align="middle"
border="0" src="3c/lily-5ffffe9a.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-break.ly"></a>
<p><a href="e1/lily-7f6b9800.ly"><samp><span class="file">beam-break.ly</span></samp>
</a>
<p>Beams can be printed across line breaks, if forced.
<p class="noindent"><p>
<a href="e1/lily-7f6b9800.ly">
<img align="middle"
border="0" src="e1/lily-7f6b9800.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-center-slope.ly"></a>
<p><a href="df/lily-49ccfe1f.ly"><samp><span class="file">beam-center-slope.ly</span></samp>
</a>
<p>Simple beams on middle staffline are allowed to be
slightly sloped, even if the notes have ledgers. Beams reaching
beyond middle line can have bigger slope.
<p>
<a href="df/lily-49ccfe1f.ly">
<img align="middle"
border="0" src="df/lily-49ccfe1f.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-concave-chord.ly"></a>
<p><a href="ce/lily-a13875e3.ly"><samp><span class="file">beam-concave-chord.ly</span></samp>
</a> <p>
<a href="ce/lily-a13875e3.ly">
<img align="middle"
border="0" src="ce/lily-a13875e3.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-concave-damped.ly"></a>
<p><a href="26/lily-31ad4de6.ly"><samp><span class="file">beam-concave-damped.ly</span></samp>
</a>
<p>Beams that are not strictly concave are damped
according to their concaveness.
<p>
<a href="26/lily-31ad4de6.ly">
<img align="middle"
border="0" src="26/lily-31ad4de6.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-concave.ly"></a>
<p><a href="5f/lily-a989c297.ly"><samp><span class="file">beam-concave.ly</span></samp>
</a>
<p>Fully concave beams should be horizontal. Informally spoken,
concave refers to the shape of the notes that are opposite a
beam. If an up-beam has high notes on its center stems, then we call
it concave.
<p>If a beam is fails a test, the desired slope is printed next to it.
<p class="noindent"><p>
<a href="5f/lily-a989c297.ly">
<img align="middle"
border="0" src="5f/lily-a989c297.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-cross-staff-auto-knee.ly"></a>
<p><a href="50/lily-10a9905a.ly"><samp><span class="file">beam-cross-staff-auto-knee.ly</span></samp>
</a>
<p>Automatic cross-staff knees work also (here they were
produced with explicit staff switches).
<p>
<a href="50/lily-10a9905a.ly">
<img align="middle"
border="0" src="50/lily-10a9905a.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-cross-staff-script.ly"></a>
<p><a href="5d/lily-15887dcf.ly"><samp><span class="file">beam-cross-staff-script.ly</span></samp>
</a>
<p>scripts don't trigger beam formatting. If this
does happen, we can have a cyclic dependency on Y-positions of
staves.
<p>
<a href="5d/lily-15887dcf.ly">
<img align="middle"
border="0" src="5d/lily-15887dcf.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-cross-staff-slope.ly"></a>
<p><a href="2b/lily-2edcab11.ly"><samp><span class="file">beam-cross-staff-slope.ly</span></samp>
</a>
<p>Cross staff (kneed) beams do not cause extreme slopes.
<p>
<a href="2b/lily-2edcab11.ly">
<img align="middle"
border="0" src="2b/lily-2edcab11.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-cross-staff.ly"></a>
<p><a href="11/lily-c8270acd.ly"><samp><span class="file">beam-cross-staff.ly</span></samp>
</a>
<p>Beams can be typeset over fixed distance aligned staves, beam
beautification does not really work, but knees do. Beams should be
behave well, wherever the switching point is.
<p class="noindent"><p>
<a href="11/lily-c8270acd.ly">
<img align="middle"
border="0" src="11/lily-c8270acd.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-damp.ly"></a>
<p><a href="cf/lily-da90d214.ly"><samp><span class="file">beam-damp.ly</span></samp>
</a>
<p><a name="index-Beam-Damp-3"></a>Beams are less steep than the notes they encompass.
<p>
<a href="cf/lily-da90d214.ly">
<img align="middle"
border="0" src="cf/lily-da90d214.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-default-lengths.ly"></a>
<p><a href="7a/lily-71450b12.ly"><samp><span class="file">beam-default-lengths.ly</span></samp>
</a>
<p>Beamed stems have standard lengths if possible. Quantization is switched off in this example.
<p>
<a href="7a/lily-71450b12.ly">
<img align="middle"
border="0" src="7a/lily-71450b12.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-extreme.ly"></a>
<p><a href="3f/lily-fbf205e0.ly"><samp><span class="file">beam-extreme.ly</span></samp>
</a>
<p>Beams should behave reasonably well, even under extreme circumstances.
Stems may be short, but noteheads should never touch the beam. Note that
under normal circumstances, these beams would get knees. Here
<code>Beam.auto-knee-gap</code> was set to false.
<p class="noindent"><p>
<a href="3f/lily-fbf205e0.ly">
<img align="middle"
border="0" src="3f/lily-fbf205e0.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-feather-knee-stem-length.ly"></a>
<p><a href="f6/lily-db6ce3f4.ly"><samp><span class="file">beam-feather-knee-stem-length.ly</span></samp>
</a>
<p>In feathered beams, stems in knees reach up to the feathered part correctly.
<p class="noindent"><p>
<a href="f6/lily-db6ce3f4.ly">
<img align="middle"
border="0" src="f6/lily-db6ce3f4.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-feather.ly"></a>
<p><a href="14/lily-b1ba6485.ly"><samp><span class="file">beam-feather.ly</span></samp>
</a>
<p>Specifying <code>grow-direction</code> on a beam, will cause
feathered beaming. The <code>\featherDurations</code> function can be used
to adjust note durations.
<p>
<a href="14/lily-b1ba6485.ly">
<img align="middle"
border="0" src="14/lily-b1ba6485.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-flat-retain-direction.ly"></a>
<p><a href="ad/lily-281bc56e.ly"><samp><span class="file">beam-flat-retain-direction.ly</span></samp>
</a>
<p>Even very flat but slanted patterns should give slanted beams.
<p>
<a href="ad/lily-281bc56e.ly">
<img align="middle"
border="0" src="ad/lily-281bc56e.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-french.ly"></a>
<p><a href="a3/lily-a69e7de5.ly"><samp><span class="file">beam-french.ly</span></samp>
</a>
<p>In French style beaming, the stems do not go between beams.
<p>
<a href="a3/lily-a69e7de5.ly">
<img align="middle"
border="0" src="a3/lily-a69e7de5.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-funky-beamlet.ly"></a>
<p><a href="fb/lily-d44c0a60.ly"><samp><span class="file">beam-funky-beamlet.ly</span></samp>
</a>
<p>Funky kneed beams with beamlets also work. The beamlets
should be pointing to the note head.
<p class="noindent"><p>
<a href="fb/lily-d44c0a60.ly">
<img align="middle"
border="0" src="fb/lily-d44c0a60.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-funky.ly"></a>
<p><a href="1d/lily-e3004b0c.ly"><samp><span class="file">beam-funky.ly</span></samp>
</a>
<p>In complex configurations of knee beaming, according to
Paul Roberts, the first stem of a beam determines the direction of the
beam, and as such the way that following (kneed) stems attach to the
beam. This is in disagreement with the current algorithm.
<p>
<a href="1d/lily-e3004b0c.ly">
<img align="middle"
border="0" src="1d/lily-e3004b0c.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-isknee.ly"></a>
<p><a href="d0/lily-004ffda1.ly"><samp><span class="file">beam-isknee.ly</span></samp>
</a>
<p><a name="index-Beam-Isknee-4"></a>
Beams can be placed across a <code>PianoStaff</code>.
<p class="noindent"><p>
<a href="d0/lily-004ffda1.ly">
<img align="middle"
border="0" src="d0/lily-004ffda1.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-knee-symmetry.ly"></a>
<p><a href="70/lily-b7ec2d1a.ly"><samp><span class="file">beam-knee-symmetry.ly</span></samp>
</a>
<p>Point-symmetric beams should receive the same
quanting. There is no up/down bias in the quanting code.
<p>
<a href="70/lily-b7ec2d1a.ly">
<img align="middle"
border="0" src="70/lily-b7ec2d1a.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-length.ly"></a>
<p><a href="bf/lily-cf8e3e28.ly"><samp><span class="file">beam-length.ly</span></samp>
</a>
<p>Beams should look the same.
<p class="noindent"><p>
<a href="bf/lily-cf8e3e28.ly">
<img align="middle"
border="0" src="bf/lily-cf8e3e28.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-manual-beaming.ly"></a>
<p><a href="42/lily-29f7d641.ly"><samp><span class="file">beam-manual-beaming.ly</span></samp>
</a>
<p>Beaming can be overidden for individual stems.
<p>
<a href="42/lily-29f7d641.ly">
<img align="middle"
border="0" src="42/lily-29f7d641.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-multiple-cross-staff.ly"></a>
<p><a href="5e/lily-b231123d.ly"><samp><span class="file">beam-multiple-cross-staff.ly</span></samp>
</a>
<p>Kneed beams (often happens with cross-staff beams)
should look good when there are multiple beams: all the beams should
go on continuously at the staff change. Stems in both staves reach up
to the last beam.
<p class="noindent"><p>
<a href="5e/lily-b231123d.ly">
<img align="middle"
border="0" src="5e/lily-b231123d.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-multiplicity-over-rests.ly"></a>
<p><a href="a0/lily-fc51de2f.ly"><samp><span class="file">beam-multiplicity-over-rests.ly</span></samp>
</a>
<p>When a beam goes over a rest, there should not be any
beamlets pointing towards the rest unless absolutely necessary.
<p>
<a href="a0/lily-fc51de2f.ly">
<img align="middle"
border="0" src="a0/lily-fc51de2f.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-outside-beamlets.ly"></a>
<p><a href="35/lily-572f19b8.ly"><samp><span class="file">beam-outside-beamlets.ly</span></samp>
</a>
<p>Beams may overshoot stems. This is also controlled with <code>break-overshoot</code>.
<p>
<a href="35/lily-572f19b8.ly">
<img align="middle"
border="0" src="35/lily-572f19b8.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-over-barline.ly"></a>
<p><a href="3a/lily-ca8c4ee9.ly"><samp><span class="file">beam-over-barline.ly</span></samp>
</a>
<p>Explicit beams may cross barlines.
<p>
<a href="3a/lily-ca8c4ee9.ly">
<img align="middle"
border="0" src="3a/lily-ca8c4ee9.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-position.ly"></a>
<p><a href="be/lily-5aefb5aa.ly"><samp><span class="file">beam-position.ly</span></samp>
</a>
<p>Beams on ledgered notes should always reach the middle staff
line. The second beam, counting from the note head side, should never
be lower than the second staff line. This does not hold for grace
note beams. Override with <code>no-stem-extend</code>.
<p>
<a href="be/lily-5aefb5aa.ly">
<img align="middle"
border="0" src="be/lily-5aefb5aa.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-quant-standard.ly"></a>
<p><a href="34/lily-06ae9f78.ly"><samp><span class="file">beam-quant-standard.ly</span></samp>
</a>
<p>This file tests a few standard beam quants, taken from
Ted Ross' book. If LilyPond finds another quant, the correct quant
is printed over the beam.
<p>
<a href="34/lily-06ae9f78.ly">
<img align="middle"
border="0" src="34/lily-06ae9f78.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-quanting-32nd.ly"></a>
<p><a href="0c/lily-4cabe209.ly"><samp><span class="file">beam-quanting-32nd.ly</span></samp>
</a>
<p>Stem lengths take precedence over beam quants: `forbidden'
quants are only avoided for 32nd beams when they are outside of
the staff. However, that leads to very long stems, which is even
worse.
<p>
<a href="0c/lily-4cabe209.ly">
<img align="middle"
border="0" src="0c/lily-4cabe209.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-quanting-horizontal.ly"></a>
<p><a href="f9/lily-95c7b67d.ly"><samp><span class="file">beam-quanting-horizontal.ly</span></samp>
</a>
<p>In this test for beam quant positions for horizontal beams,
staff lines should be covered in all cases. For 32nd beams, the free stem
lengths are between 2 and 1.5.
<p>
<a href="f9/lily-95c7b67d.ly">
<img align="middle"
border="0" src="f9/lily-95c7b67d.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-quarter.ly"></a>
<p><a href="a4/lily-229a5f85.ly"><samp><span class="file">beam-quarter.ly</span></samp>
</a>
<p>Quarter notes may be beamed: the beam is halted momentarily.
<p>
<a href="a4/lily-229a5f85.ly">
<img align="middle"
border="0" src="a4/lily-229a5f85.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-rest.ly"></a>
<p><a href="5d/lily-85076187.ly"><samp><span class="file">beam-rest.ly</span></samp>
</a>
<p>The number of beams does not change on a rest.
<p>
<a href="5d/lily-85076187.ly">
<img align="middle"
border="0" src="5d/lily-85076187.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-second.ly"></a>
<p><a href="65/lily-86357423.ly"><samp><span class="file">beam-second.ly</span></samp>
</a>
<p>Engraving second intervals is tricky. We used to have
problems with seconds being too steep, or getting too long stems. In
a file like this, showing seconds, you'll spot something fishy very
quickly.
<p>
<a href="65/lily-86357423.ly">
<img align="middle"
border="0" src="65/lily-86357423.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-shortened-lengths.ly"></a>
<p><a href="93/lily-6296bb8f.ly"><samp><span class="file">beam-shortened-lengths.ly</span></samp>
</a>
<p>Beams in unnatural direction, have shortened stems, but do not look too short.
<p>
<a href="93/lily-6296bb8f.ly">
<img align="middle"
border="0" src="93/lily-6296bb8f.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-single-stem.ly"></a>
<p><a href="00/lily-500ff3f1.ly"><samp><span class="file">beam-single-stem.ly</span></samp>
</a>
<p>Single stem beams are also allowed. For such beams,
clip-edges is switched off automatically.
<p>
<a href="00/lily-500ff3f1.ly">
<img align="middle"
border="0" src="00/lily-500ff3f1.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-slope-stemlet.ly"></a>
<p><a href="7a/lily-ede3396c.ly"><samp><span class="file">beam-slope-stemlet.ly</span></samp>
</a>
<p>For slope calculations, stemlets are treated
as invisible stems.
<p>
<a href="7a/lily-ede3396c.ly">
<img align="middle"
border="0" src="7a/lily-ede3396c.png" alt="[image of music]">
</a>
</p>
<p><a name="beam-unconnected-beamlets.ly"></a>
<p><a href="8b/lily-9c84ecb2.ly"><samp><span class="file">beam-unconnected-beamlets.ly</span></samp>
</a>
<p>By setting <code>max-beam-connect</code>, it is
possible to create pairs of unconnected beamlets.
<p>
<a href="8b/lily-9c84ecb2.ly">
<img align="middle"
border="0" src="8b/lily-9c84ecb2.png" alt="[image of music]">
</a>
</p>
<p><a name="beaming-ternary-metrum.ly"></a>
<p><a href="89/lily-2f9a6882.ly"><samp><span class="file">beaming-ternary-metrum.ly</span></samp>
</a>
<p>Automatic beaming works also in ternary time sigs. In
this case, the 8th is a beat, so the 16ths are split into two
groups. This can be avoided by overriding <code>beatLength</code> to be
three 8th notes.
<p>
<a href="89/lily-2f9a6882.ly">
<img align="middle"
border="0" src="89/lily-2f9a6882.png" alt="[image of music]">
</a>
</p>
<p><a name="beaming.ly"></a>
<p><a href="65/lily-bc6aae7d.ly"><samp><span class="file">beaming.ly</span></samp>
</a>
<p>Beaming is generated automatically. Beams may cross bar lines. In that
case, line breaks are forbidden.
<p class="noindent"><p>
<a href="65/lily-bc6aae7d.ly">
<img align="middle"
border="0" src="65/lily-bc6aae7d.png" alt="[image of music]">
</a>
</p>
<p><a name="beams.ly"></a>
<p><a href="8e/lily-5f7fa662.ly"><samp><span class="file">beams.ly</span></samp>
</a>
<p>Beaming can be also given explicitly.
<p>
<a href="8e/lily-5f7fa662.ly">
<img align="middle"
border="0" src="8e/lily-5f7fa662.png" alt="[image of music]">
</a>
</p>
<p><a name="bend-after.ly"></a>
<p><a href="d1/lily-fdf1b17c.ly"><samp><span class="file">bend-after.ly</span></samp>
</a>
<p>Falls and doits can be created with bendAfter. They run
to the next note, or to the next barline. Microtone bends (i.e.
\bendAfter #3.5) are also supported.
<p>
<a href="d1/lily-fdf1b17c.ly">
<img align="middle"
border="0" src="d1/lily-fdf1b17c.png" alt="[image of music]">
</a>
</p>
<p><a name="bend-dot.ly"></a>
<p><a href="02/lily-58ee604e.ly"><samp><span class="file">bend-dot.ly</span></samp>
</a>
<p>Bends avoid dots, but only if necessary.
<p>
<a href="02/lily-58ee604e.ly">
<img align="middle"
border="0" src="02/lily-58ee604e.png" alt="[image of music]">
</a>
</p>
<p><a name="break-alignment-anchor-alignment.ly"></a>
<p><a href="b2/lily-4aa765d1.ly"><samp><span class="file">break-alignment-anchor-alignment.ly</span></samp>
</a>
<p>The default callback for break-align-anchor in clefs and time/key
signatures reads the break-align-anchor-aligment property to align
the anchor to the extent of the break-aligned grob.
<p>
<a href="b2/lily-4aa765d1.ly">
<img align="middle"
border="0" src="b2/lily-4aa765d1.png" alt="[image of music]">
</a>
</p>
<p><a name="break-alignment-anchors.ly"></a>
<p><a href="42/lily-6a95a25a.ly"><samp><span class="file">break-alignment-anchors.ly</span></samp>
</a>
<p>The break-align-anchor property of a break-aligned grob gives
the horizontal offset at which other grobs should attach.
<p>
<a href="42/lily-6a95a25a.ly">
<img align="middle"
border="0" src="42/lily-6a95a25a.png" alt="[image of music]">
</a>
</p>
<p><a name="break.ly"></a>
<p><a href="57/lily-653c9e70.ly"><samp><span class="file">break.ly</span></samp>
</a>
<p>Breaks can be encouraged and discouraged using <code>\break</code> and
<code>\noBreak</code>.
<p>
<a href="57/lily-653c9e70.ly">
<img align="middle"
border="0" src="57/lily-653c9e70.png" alt="[image of music]">
</a>
</p>
<p><a name="breathing-sign-ancient.ly"></a>
<p><a href="31/lily-d2753e3e.ly"><samp><span class="file">breathing-sign-ancient.ly</span></samp>
</a>
<p>Gregorian chant notation sometimes also uses commas and ticks, but in
smaller font size (we call it 'virgula' and 'caesura'). However, the
most common breathing signs are divisio minima/maior/maxima and
finalis, the latter three looking similar to bar glyphs.
<p class="noindent"><p>
<a href="31/lily-d2753e3e.ly">
<img align="middle"
border="0" src="31/lily-d2753e3e.png" alt="[image of music]">
</a>
</p>
<p><a name="breathing-sign.ly"></a>
<p><a href="2e/lily-5718bad6.ly"><samp><span class="file">breathing-sign.ly</span></samp>
</a>
<p>Breathing signs are available in different tastes: commas (default),
ticks, vees and `railroad tracks' (caesura).
<p>
<a href="2e/lily-5718bad6.ly">
<img align="middle"
border="0" src="2e/lily-5718bad6.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-changes.ly"></a>
<p><a href="b9/lily-7601bd3e.ly"><samp><span class="file">chord-changes.ly</span></samp>
</a>
<p>Property chordChanges: display chord names only when
there's a change in the chords scheme, but always display the
chord name after a line break.
<p class="noindent"><p>
<a href="b9/lily-7601bd3e.ly">
<img align="middle"
border="0" src="b9/lily-7601bd3e.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-name-entry-11.ly"></a>
<p><a href="7f/lily-e0877587.ly"><samp><span class="file">chord-name-entry-11.ly</span></samp>
</a>
<p>The 11 is only added to major-13 if it
is mentioned explicitly.
<p>
<a href="7f/lily-e0877587.ly">
<img align="middle"
border="0" src="7f/lily-e0877587.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-name-entry.ly"></a>
<p><a href="23/lily-559ba6c8.ly"><samp><span class="file">chord-name-entry.ly</span></samp>
</a>
<p>Chords can be produced with the chordname entry
code (<code>\chordmode</code> mode), using a pitch and a suffix. Here,
the suffixes are printed below pitches.
<p class="noindent"><p>
<a href="23/lily-559ba6c8.ly">
<img align="middle"
border="0" src="23/lily-559ba6c8.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-name-exceptions.ly"></a>
<p><a href="df/lily-32f2e76d.ly"><samp><span class="file">chord-name-exceptions.ly</span></samp>
</a>
<p>The property <code>chordNameExceptions</code> can used
to store a list of special notations for specific chords.
<p>
<a href="df/lily-32f2e76d.ly">
<img align="middle"
border="0" src="df/lily-32f2e76d.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-name-major7.ly"></a>
<p><a href="f3/lily-1e075f54.ly"><samp><span class="file">chord-name-major7.ly</span></samp>
</a>
<p>The layout of the major 7 can be tuned with
<code>majorSevenSymbol</code>.
<p>
<a href="f3/lily-1e075f54.ly">
<img align="middle"
border="0" src="f3/lily-1e075f54.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-names-bass.ly"></a>
<p><a href="33/lily-09d51d46.ly"><samp><span class="file">chord-names-bass.ly</span></samp>
</a>
<p>In ignatzek inversions, a note is dropped down to act as the
bass note of the chord. Bass note may be also added explicitly.
Above the staff: computed chord names. Below staff: entered chord name.
<p class="noindent"><p>
<a href="33/lily-09d51d46.ly">
<img align="middle"
border="0" src="33/lily-09d51d46.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-names-languages.ly"></a>
<p><a href="c1/lily-db48c054.ly"><samp><span class="file">chord-names-languages.ly</span></samp>
</a>
<p><a name="index-Chord-Names-German-5"></a>The english naming of chords (default) can be changed to german
(<code>\germanChords</code> replaces B and Bes to H and B), semi-german
(<code>\semiGermanChords</code> replaces B and Bes to H and Bb), italian
(<code>\italianChords</code> uses Do Re Mi Fa Sol La Si), or french
(<code>\frenchChords</code> replaces Re to Ré).
<p class="noindent"><p>
<a href="c1/lily-db48c054.ly">
<img align="middle"
border="0" src="c1/lily-db48c054.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-scripts.ly"></a>
<p><a href="98/lily-5397032e.ly"><samp><span class="file">chord-scripts.ly</span></samp>
</a>
<p>Scripts can also be attached to chord elements.
<p>
<a href="98/lily-5397032e.ly">
<img align="middle"
border="0" src="98/lily-5397032e.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-tremolo-short.ly"></a>
<p><a href="72/lily-e2cdb3eb.ly"><samp><span class="file">chord-tremolo-short.ly</span></samp>
</a>
<p>Tremolo repeats can be constructed for short tremolos (total duration smaller than 1/4) too. Only some of the beams are connected to the stems.
<p>
<a href="72/lily-e2cdb3eb.ly">
<img align="middle"
border="0" src="72/lily-e2cdb3eb.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-tremolo-single.ly"></a>
<p><a href="cd/lily-210dad23.ly"><samp><span class="file">chord-tremolo-single.ly</span></samp>
</a>
<p>Chord tremolos on a single note.
<p>
<a href="cd/lily-210dad23.ly">
<img align="middle"
border="0" src="cd/lily-210dad23.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-tremolo-stem-direction.ly"></a>
<p><a href="f7/lily-4e1960f7.ly"><samp><span class="file">chord-tremolo-stem-direction.ly</span></samp>
</a>
<p>Stem directions influence positioning of whole note
tremolo beams.
<p>
<a href="f7/lily-4e1960f7.ly">
<img align="middle"
border="0" src="f7/lily-4e1960f7.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-tremolo-whole.ly"></a>
<p><a href="83/lily-202aa1d6.ly"><samp><span class="file">chord-tremolo-whole.ly</span></samp>
</a>
<p>chord tremolos don't collide with whole
notes.
<p>
<a href="83/lily-202aa1d6.ly">
<img align="middle"
border="0" src="83/lily-202aa1d6.png" alt="[image of music]">
</a>
</p>
<p><a name="chord-tremolo.ly"></a>
<p><a href="3a/lily-7ed89d95.ly"><samp><span class="file">chord-tremolo.ly</span></samp>
</a>
<p>Chord tremolos look like beams, but are a kind of repeat symbol.
To avoid confusion, chord tremolo beams do not reach the stems, but
leave a gap. Chord tremolo beams on half notes are not ambiguous,
as half notes cannot appear in a regular beam, and should reach the
stems.
<p>In this example, each tremolo lasts exactly one measure.
<p>(To ensure that the spacing engine is not confused we add some regular
notes as well.)
<p class="noindent"><p>
<a href="3a/lily-7ed89d95.ly">
<img align="middle"
border="0" src="3a/lily-7ed89d95.png" alt="[image of music]">
</a>
</p>
<p><a name="chords-funky-ignatzek.ly"></a>
<p><a href="06/lily-a0c546b3.ly"><samp><span class="file">chords-funky-ignatzek.ly</span></samp>
</a>
<p>Jazz chords may have unusual combinations.
<p>
<a href="06/lily-a0c546b3.ly">
<img align="middle"
border="0" src="06/lily-a0c546b3.png" alt="[image of music]">
</a>
</p>
<p><a name="chromatic-scales.ly"></a>
<p><a href="1c/lily-2a710825.ly"><samp><span class="file">chromatic-scales.ly</span></samp>
</a>
<p><code>staffLineLayoutFunction</code> is used to change the position of the notes.
This sets <code>staffLineLayoutFunction</code> to <code>ly:pitch-semitones</code> to
produce a chromatic scale with the distance between a consecutive
space and line equal to one semitone.
<p class="noindent"><p>
<a href="1c/lily-2a710825.ly">
<img align="middle"
border="0" src="1c/lily-2a710825.png" alt="[image of music]">
</a>
</p>
<p><a name="clef-oct.ly"></a>
<p><a href="c2/lily-9bd573a3.ly"><samp><span class="file">clef-oct.ly</span></samp>
</a>
<p>Octavation signs may be added to clefs. These
octavation signs may be placed below or above (meaning an octave
higher or lower), and can take any value, including 15 for two octaves.
<p>
<a href="c2/lily-9bd573a3.ly">
<img align="middle"
border="0" src="c2/lily-9bd573a3.png" alt="[image of music]">
</a>
</p>
<p><a name="clef-ottava.ly"></a>
<p><a href="50/lily-d2c89672.ly"><samp><span class="file">clef-ottava.ly</span></samp>
</a>
<p>Ottava brackets and clefs both modify Staff.middleCPosition,
but they don't confuse one another.
<p>
<a href="50/lily-d2c89672.ly">
<img align="middle"
border="0" src="50/lily-d2c89672.png" alt="[image of music]">
</a>
</p>
<p><a name="clef-warn.ly"></a>
<p><a href="65/lily-c6111dd6.ly"><samp><span class="file">clef-warn.ly</span></samp>
</a>
<p>Unknown clef name warning displays available clefs
<p>
<a href="65/lily-c6111dd6.ly">
<img align="middle"
border="0" src="65/lily-c6111dd6.png" alt="[image of music]">
</a>
</p>
<p><a name="clefs.ly"></a>
<p><a href="8a/lily-0c63943b.ly"><samp><span class="file">clefs.ly</span></samp>
</a>
<p>Clefs with <code>full-size-change</code> should be typeset in
full size.
<p>
<a href="8a/lily-0c63943b.ly">
<img align="middle"
border="0" src="8a/lily-0c63943b.png" alt="[image of music]">
</a>
</p>
<p><a name="clip-systems.ly"></a>
<p><a href="5a/lily-c83540b5.ly"><samp><span class="file">clip-systems.ly</span></samp>
</a>
<p>Clipping snippets from a finished score
<p>Notes:
<ul>
<li>If system starts and ends are included, they include extents of the System grob, eg. instrument names.
<li>Grace notes at the end point of the region are not included
<li>Regions can span multiple systems. In this case, multiple EPS files are generated.
</ul>
<p>This file needs to be run separately with <code>-dclip-systems</code>; the
collated-files.html of the regression test does not adequately show
the results.
<p>The result will be files named
<samp><var>base</var><span class="file">-from-</span><var>start</var><span class="file">-to-</span><var>end</var><span class="file">[-</span><var>count</var><span class="file">].eps</span></samp>.
<p class="noindent"><p>
<a href="5a/lily-c83540b5.ly">
<img align="middle"
border="0" src="5a/lily-c83540b5.png" alt="[image of music]">
</a>
</p>
<p><a name="cluster-break.ly"></a>
<p><a href="65/lily-24f28313.ly"><samp><span class="file">cluster-break.ly</span></samp>
</a>
<p>Clusters behave well across line breaks.
<p>
<a href="65/lily-24f28313.ly">
<img align="middle"
border="0" src="65/lily-24f28313.png" alt="[image of music]">
</a>
</p>
<p><a name="cluster-cross-staff.ly"></a>
<p><a href="ff/lily-d339742b.ly"><samp><span class="file">cluster-cross-staff.ly</span></samp>
</a>
<p>Clusters can be written across staves.
<p>
<a href="ff/lily-d339742b.ly">
<img align="middle"
border="0" src="ff/lily-d339742b.png" alt="[image of music]">
</a>
</p>
<p><a name="cluster-single-note.ly"></a>
<p><a href="94/lily-b5af6804.ly"><samp><span class="file">cluster-single-note.ly</span></samp>
</a>
<p>don't crash on single chord clusters.
<p>
<a href="94/lily-b5af6804.ly">
<img align="middle"
border="0" src="94/lily-b5af6804.png" alt="[image of music]">
</a>
</p>
<p><a name="cluster-style.ly"></a>
<p><a href="dd/lily-47a1d8a5.ly"><samp><span class="file">cluster-style.ly</span></samp>
</a>
<p>Clusters behave well across line breaks.
<p>
<a href="dd/lily-47a1d8a5.ly">
<img align="middle"
border="0" src="dd/lily-47a1d8a5.png" alt="[image of music]">
</a>
</p>
<p><a name="cluster.ly"></a>
<p><a href="3f/lily-057ba8cc.ly"><samp><span class="file">cluster.ly</span></samp>
</a>
<p>Clusters are a device to denote that a complete range of
notes is to be played.
<p>
<a href="3f/lily-057ba8cc.ly">
<img align="middle"
border="0" src="3f/lily-057ba8cc.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-2.ly"></a>
<p><a href="a2/lily-6d9fbe3d.ly"><samp><span class="file">collision-2.ly</span></samp>
</a>
<p>Single head notes may collide.
<p>
<a href="a2/lily-6d9fbe3d.ly">
<img align="middle"
border="0" src="a2/lily-6d9fbe3d.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-alignment.ly"></a>
<p><a href="17/lily-4d0e3c08.ly"><samp><span class="file">collision-alignment.ly</span></samp>
</a>
<p>Notes in different staves should be aligned to the
left-most note, in case of collisions.
<p>
<a href="17/lily-4d0e3c08.ly">
<img align="middle"
border="0" src="17/lily-4d0e3c08.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-dots-invert.ly"></a>
<p><a href="41/lily-c4b3cfab.ly"><samp><span class="file">collision-dots-invert.ly</span></samp>
</a>
<p>When notes are colliding, the resolution depends on the
dots: notes with dots should go to the right, if there could be
confusion to which notes the dots belong.
<p>
<a href="41/lily-c4b3cfab.ly">
<img align="middle"
border="0" src="41/lily-c4b3cfab.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-dots-move.ly"></a>
<p><a href="f4/lily-4ccc603f.ly"><samp><span class="file">collision-dots-move.ly</span></samp>
</a>
<p>If dotted note heads must remain on the left side,
collision resolution moves the dots to the right.
<p>
<a href="f4/lily-4ccc603f.ly">
<img align="middle"
border="0" src="f4/lily-4ccc603f.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-dots-up-space-dotted.ly"></a>
<p><a href="35/lily-7391811d.ly"><samp><span class="file">collision-dots-up-space-dotted.ly</span></samp>
</a>
<p>For collisions where the upper note is dotted and in a
space, the upper is moved to right. This behavior can be tuned by
prefer-dotted-right.
<p>
<a href="35/lily-7391811d.ly">
<img align="middle"
border="0" src="35/lily-7391811d.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-dots.ly"></a>
<p><a href="1e/lily-d050be6e.ly"><samp><span class="file">collision-dots.ly</span></samp>
</a>
<p>Collision resolution tries to put notes with dots
on the right side.
<p>
<a href="1e/lily-d050be6e.ly">
<img align="middle"
border="0" src="1e/lily-d050be6e.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-head-chords.ly"></a>
<p><a href="79/lily-00df2f39.ly"><samp><span class="file">collision-head-chords.ly</span></samp>
</a>
<p>Note heads in collisions should be merged if
they have the same positions in the extreme note heads.
<p class="noindent"><p>
<a href="79/lily-00df2f39.ly">
<img align="middle"
border="0" src="79/lily-00df2f39.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-head-solfa-fa.ly"></a>
<p><a href="7f/lily-30770ec0.ly"><samp><span class="file">collision-head-solfa-fa.ly</span></samp>
</a>
<p>The FA note (a triangle) is merged to avoid creating a
block-shaped note.
<p>
<a href="7f/lily-30770ec0.ly">
<img align="middle"
border="0" src="7f/lily-30770ec0.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-heads.ly"></a>
<p><a href="c4/lily-d646b267.ly"><samp><span class="file">collision-heads.ly</span></samp>
</a>
<p>Open and black note heads are not merged by default.
<p>
<a href="c4/lily-d646b267.ly">
<img align="middle"
border="0" src="c4/lily-d646b267.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-manual.ly"></a>
<p><a href="5c/lily-429fd413.ly"><samp><span class="file">collision-manual.ly</span></samp>
</a>
<p>Collision resolution may be forced manually with <code>force-hshift</code>.
<p>
<a href="5c/lily-429fd413.ly">
<img align="middle"
border="0" src="5c/lily-429fd413.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-merge-differently-dotted.ly"></a>
<p><a href="51/lily-2a1c9c9f.ly"><samp><span class="file">collision-merge-differently-dotted.ly</span></samp>
</a>
<p>If <code>NoteCollision</code> has
<code>merge-differently-dotted = ##t</code> note
heads that have differing dot counts may be merged anyway. Dots
should not disappear when merging similar note heads.
<p>
<a href="51/lily-2a1c9c9f.ly">
<img align="middle"
border="0" src="51/lily-2a1c9c9f.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-merge-differently-headed.ly"></a>
<p><a href="54/lily-cb4f12b9.ly"><samp><span class="file">collision-merge-differently-headed.ly</span></samp>
</a>
<p>If <code>merge-differently-headed</code> is enabled, then
open note heads may be merged with black noteheads, but only
if the black note heads are from 8th or shorter notes.
<p class="noindent"><p>
<a href="54/lily-cb4f12b9.ly">
<img align="middle"
border="0" src="54/lily-cb4f12b9.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-merge-dots.ly"></a>
<p><a href="d2/lily-57a2c999.ly"><samp><span class="file">collision-merge-dots.ly</span></samp>
</a>
<p>When merging heads, the dots are merged too.
<p>
<a href="d2/lily-57a2c999.ly">
<img align="middle"
border="0" src="d2/lily-57a2c999.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-mesh.ly"></a>
<p><a href="1b/lily-471aab27.ly"><samp><span class="file">collision-mesh.ly</span></samp>
</a>
<p>Oppositely stemmed chords, meshing into each other,
are resolved.
<p>
<a href="1b/lily-471aab27.ly">
<img align="middle"
border="0" src="1b/lily-471aab27.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-seconds.ly"></a>
<p><a href="cf/lily-1f333206.ly"><samp><span class="file">collision-seconds.ly</span></samp>
</a>
<p>Seconds do not confuse the collision algorithm too much. The best
way to format this would be to merge the two Ds, but we will be happy for now
if the upstem D does not collide with the downstem C.
<p>
<a href="cf/lily-1f333206.ly">
<img align="middle"
border="0" src="cf/lily-1f333206.png" alt="[image of music]">
</a>
</p>
<p><a name="collision-whole.ly"></a>
<p><a href="27/lily-0cded0b3.ly"><samp><span class="file">collision-whole.ly</span></samp>
</a>
<p>Mixed collisions with whole notes require asymmetric shifts.
<p>
<a href="27/lily-0cded0b3.ly">
<img align="middle"
border="0" src="27/lily-0cded0b3.png" alt="[image of music]">
</a>
</p>
<p><a name="collisions.ly"></a>
<p><a href="85/lily-49d2fa91.ly"><samp><span class="file">collisions.ly</span></samp>
</a>
<p>In addition to normal collision rules, there is support for polyphony,
where the collisions are avoided by shifting middle voices horizontally.
<p class="noindent"><p>
<a href="85/lily-49d2fa91.ly">
<img align="middle"
border="0" src="85/lily-49d2fa91.png" alt="[image of music]">
</a>
</p>
<p><a name="color.ly"></a>
<p><a href="13/lily-b49cfd0a.ly"><samp><span class="file">color.ly</span></samp>
</a>
<p>Each grob can have a color assigned to it.
Use the <code>\override</code> and <code>\revert</code> expressions to set the
<code>color</code> property.
<p>
<a href="13/lily-b49cfd0a.ly">
<img align="middle"
border="0" src="13/lily-b49cfd0a.png" alt="[image of music]">
</a>
</p>
<p><a name="completion-heads-lyrics.ly"></a>
<p><a href="f1/lily-6737f4bb.ly"><samp><span class="file">completion-heads-lyrics.ly</span></samp>
</a>
<p>You can put lyrics under completion heads.
<p>
<a href="f1/lily-6737f4bb.ly">
<img align="middle"
border="0" src="f1/lily-6737f4bb.png" alt="[image of music]">
</a>
</p>
<p><a name="completion-heads-multiple-ties.ly"></a>
<p><a href="42/lily-b2098109.ly"><samp><span class="file">completion-heads-multiple-ties.ly</span></samp>
</a>
<p>The <code>Completion_heads_engraver</code> correctly handles notes that need to be split into more than 2 parts.
<p class="noindent"><p>
<a href="42/lily-b2098109.ly">
<img align="middle"
border="0" src="42/lily-b2098109.png" alt="[image of music]">
</a>
</p>
<p><a name="completion-heads-polyphony.ly"></a>
<p><a href="2a/lily-3e4c3fa1.ly"><samp><span class="file">completion-heads-polyphony.ly</span></samp>
</a>
<p>Completion heads are broken across bar lines. This was
intended as a debugging tool, but it can be used to ease music entry.
Completion heads are not fooled by polyphony with a different rhythm.
<p class="noindent"><p>
<a href="2a/lily-3e4c3fa1.ly">
<img align="middle"
border="0" src="2a/lily-3e4c3fa1.png" alt="[image of music]">
</a>
</p>
<p><a name="completion-heads.ly"></a>
<p><a href="46/lily-109c4664.ly"><samp><span class="file">completion-heads.ly</span></samp>
</a>
<p>If the <code>Note_heads_engraver</code> is replaced by the <code>Completion_heads_engraver</code>, notes that cross bar lines are split into tied notes.
<p class="noindent"><p>
<a href="46/lily-109c4664.ly">
<img align="middle"
border="0" src="46/lily-109c4664.png" alt="[image of music]">
</a>
</p>
<p><a name="context-die-staff.ly"></a>
<p><a href="cd/lily-ba9ad7ac.ly"><samp><span class="file">context-die-staff.ly</span></samp>
</a>
<p>a staff should die if there is reference to it.
<p>
<a href="cd/lily-ba9ad7ac.ly">
<img align="middle"
border="0" src="cd/lily-ba9ad7ac.png" alt="[image of music]">
</a>
</p>
<p><a name="custos.ly"></a>
<p><a href="65/lily-d2dce9e6.ly"><samp><span class="file">custos.ly</span></samp>
</a>
<p>Custodes may be engraved in various styles.
<p>
<a href="65/lily-d2dce9e6.ly">
<img align="middle"
border="0" src="65/lily-d2dce9e6.png" alt="[image of music]">
</a>
</p>
<p><a name="display-lily-tests.ly"></a>
<p><a href="3f/lily-09024434.ly"><samp><span class="file">display-lily-tests.ly</span></samp>
</a>
<p>This is a test of the display-lily-music unit. Problems are reported on the
stderr of this run.
<p>
<a href="3f/lily-09024434.ly">
<img align="middle"
border="0" src="3f/lily-09024434.png" alt="[image of music]">
</a>
</p>
<p><a name="dot-column-rest-collision.ly"></a>
<p><a href="ca/lily-2c8f85fb.ly"><samp><span class="file">dot-column-rest-collision.ly</span></samp>
</a>
<p>Dot columns do not trigger beam slanting too early.
<p>
<a href="ca/lily-2c8f85fb.ly">
<img align="middle"
border="0" src="ca/lily-2c8f85fb.png" alt="[image of music]">
</a>
</p>
<p><a name="dot-flag-collision.ly"></a>
<p><a href="d5/lily-c6939caf.ly"><samp><span class="file">dot-flag-collision.ly</span></samp>
</a>
<p>Dots move to the right when a collision with the (up)flag happens.
<p>
<a href="d5/lily-c6939caf.ly">
<img align="middle"
border="0" src="d5/lily-c6939caf.png" alt="[image of music]">
</a>
</p>
<p><a name="dot-rest-beam-trigger.ly"></a>
<p><a href="dd/lily-91c42909.ly"><samp><span class="file">dot-rest-beam-trigger.ly</span></samp>
</a>
<p>Dotted rests connected with beams do not trigger
premature beam calculations. In this case, the beam should be
sloped, and there should be no programming_error() warnings.
<p>
<a href="dd/lily-91c42909.ly">
<img align="middle"
border="0" src="dd/lily-91c42909.png" alt="[image of music]">
</a>
</p>
<p><a name="dot-up-voice-collision.ly"></a>
<p><a href="62/lily-37df1d4e.ly"><samp><span class="file">dot-up-voice-collision.ly</span></samp>
</a>
<p>in collisions, the stems of outer voice are added to the
dot support of the inner voices.
<p>
<a href="62/lily-37df1d4e.ly">
<img align="middle"
border="0" src="62/lily-37df1d4e.png" alt="[image of music]">
</a>
</p>
<p><a name="dots.ly"></a>
<p><a href="7b/lily-d97afdb6.ly"><samp><span class="file">dots.ly</span></samp>
</a>
<p>Both noteheads and rests can have dots.
Augmentation dots should never be printed on a staff line,
but rather be shifted vertically. They should go up, but in case of
multiple parts, the down stems have down shifted dots. In case of
chords, all dots should be in a column. The dots follow the shift
of rests when avoiding collisions.
<p>The priorities to print the dots are (ranked in importance):
<ul>
<li>keeping dots off staff lines,
<li>keeping dots close to their note heads,
<li>moving dots in the direction specified by the voice,
<li>moving dots up.
</ul>
<p class="noindent"><p>
<a href="7b/lily-d97afdb6.ly">
<img align="middle"
border="0" src="7b/lily-d97afdb6.png" alt="[image of music]">
</a>
</p>
<p><a name="drums.ly"></a>
<p><a href="9c/lily-efee2bb4.ly"><samp><span class="file">drums.ly</span></samp>
</a>
<p>In drum notation, there is a special clef symbol, drums are
placed to their own staff positions and have note heads according to the
drum, an extra symbol may be attached to the drum, and the number of lines
may be restricted.
<p>
<a href="9c/lily-efee2bb4.ly">
<img align="middle"
border="0" src="9c/lily-efee2bb4.png" alt="[image of music]">
</a>
</p>
<p><a name="dynamics-broken-hairpin.ly"></a>
<p><a href="4c/lily-36070a0d.ly"><samp><span class="file">dynamics-broken-hairpin.ly</span></samp>
</a>
<p>Broken crescendi should be open on one side.
<p>
<a href="4c/lily-36070a0d.ly">
<img align="middle"
border="0" src="4c/lily-36070a0d.png" alt="[image of music]">
</a>
</p>
<p><a name="dynamics-glyphs.ly"></a>
<p><a href="3c/lily-2e405126.ly"><samp><span class="file">dynamics-glyphs.ly</span></samp>
</a>
<p>Dynamic letters are kerned, and their weight
matches that of the hairpin signs. The dynamic scripts should be
horizontally centered on the note head. Scripts that should appear
closer to the note head (staccato, accent) are reckoned with.
<p class="noindent"><p>
<a href="3c/lily-2e405126.ly">
<img align="middle"
border="0" src="3c/lily-2e405126.png" alt="[image of music]">
</a>
</p>
<p><a name="dynamics-hairpin-length.ly"></a>
<p><a href="9f/lily-000ca1f3.ly"><samp><span class="file">dynamics-hairpin-length.ly</span></samp>
</a>
<p>Hairpins extend to the extremes of the bound if there
is no adjacent hairpin or dynamic-text. If there is, the hairpin
extends to the center of the column or the bound of the text
respectively.
<p>
<a href="9f/lily-000ca1f3.ly">
<img align="middle"
border="0" src="9f/lily-000ca1f3.png" alt="[image of music]">
</a>
</p>
<p><a name="dynamics-line.ly"></a>
<p><a href="39/lily-97207152.ly"><samp><span class="file">dynamics-line.ly</span></samp>
</a>
<p>Dynamics appear below or above the staff. If multiple
dynamics are linked with (de)crescendi, they should be on the same
line. Isolated dynamics may be forced up or down.
<p>
<a href="39/lily-97207152.ly">
<img align="middle"
border="0" src="39/lily-97207152.png" alt="[image of music]">
</a>
</p>
<p><a name="dynamics-text-spanner-abs-dynamic.ly"></a>
<p><a href="1a/lily-19750301.ly"><samp><span class="file">dynamics-text-spanner-abs-dynamic.ly</span></samp>
</a>
<p>left attach dir for text crescendi starting on an
absolute dynamic is changed, so cresc. and the absolute dynamic
don't overstrike.
<p>
<a href="1a/lily-19750301.ly">
<img align="middle"
border="0" src="1a/lily-19750301.png" alt="[image of music]">
</a>
</p>
<p><a name="dynamics-text-spanner-padding.ly"></a>
<p><a href="22/lily-c8140332.ly"><samp><span class="file">dynamics-text-spanner-padding.ly</span></samp>
</a>
<p>The 2nd half of the cresc. stays at a reasonable distance
from the notes.
<p>
<a href="22/lily-c8140332.ly">
<img align="middle"
border="0" src="22/lily-c8140332.png" alt="[image of music]">
</a>
</p>
<p><a name="dynamics-unbound-hairpin.ly"></a>
<p><a href="84/lily-f334cd3a.ly"><samp><span class="file">dynamics-unbound-hairpin.ly</span></samp>
</a>
<p>Crescendi may start off-notes, however, they should not collapse into flat lines.
<p>
<a href="84/lily-f334cd3a.ly">
<img align="middle"
border="0" src="84/lily-f334cd3a.png" alt="[image of music]">
</a>
</p>
<p><a name="easy-notation.ly"></a>
<p><a href="6d/lily-294bfe34.ly"><samp><span class="file">easy-notation.ly</span></samp>
</a>
<p>Easy-notation (or Ez-notation) prints names in note heads.
You also get ledger lines, of course.
<p>
<a href="6d/lily-294bfe34.ly">
<img align="middle"
border="0" src="6d/lily-294bfe34.png" alt="[image of music]">
</a>
</p>
<p><a name="fermata-rest-position.ly"></a>
<p><a href="cd/lily-833800a5.ly"><samp><span class="file">fermata-rest-position.ly</span></samp>
</a>
<p>Fermatas over multimeasure rests are positioned as over normal rests.
<p class="noindent"><p>
<a href="cd/lily-833800a5.ly">
<img align="middle"
border="0" src="cd/lily-833800a5.png" alt="[image of music]">
</a>
</p>
<p><a name="figured-bass-alteration.ly"></a>
<p><a href="27/lily-9b86f67f.ly"><samp><span class="file">figured-bass-alteration.ly</span></samp>
</a>
<p>Bass figures can carry alterations.
<p>
<a href="27/lily-9b86f67f.ly">
<img align="middle"
border="0" src="27/lily-9b86f67f.png" alt="[image of music]">
</a>
</p>
<p><a name="figured-bass-continuation-center.ly"></a>
<p><a href="b6/lily-b81ac7ad.ly"><samp><span class="file">figured-bass-continuation-center.ly</span></samp>
</a>
<p>Pairs of congruent figured bass extender lines are
vertically centered if <code>figuredBassCenterContinuations</code> is set to
true.
<p>
<a href="b6/lily-b81ac7ad.ly">
<img align="middle"
border="0" src="b6/lily-b81ac7ad.png" alt="[image of music]">
</a>
</p>
<p><a name="figured-bass-continuation-forbid.ly"></a>
<p><a href="9f/lily-d2287a37.ly"><samp><span class="file">figured-bass-continuation-forbid.ly</span></samp>
</a>
<p>By adorning a bass figure with <code>\!</code>, an extender
may be forbidden.
<p>
<a href="9f/lily-d2287a37.ly">
<img align="middle"
border="0" src="9f/lily-d2287a37.png" alt="[image of music]">
</a>
</p>
<p><a name="figured-bass-continuation.ly"></a>
<p><a href="91/lily-ee466dd8.ly"><samp><span class="file">figured-bass-continuation.ly</span></samp>
</a>
<p>Figured bass extender lines run between repeated bass
figures. They are switched on with <code>useBassFigureExtenders</code>
<p>
<a href="91/lily-ee466dd8.ly">
<img align="middle"
border="0" src="91/lily-ee466dd8.png" alt="[image of music]">
</a>
</p>
<p><a name="figured-bass-implicit.ly"></a>
<p><a href="63/lily-9c08359a.ly"><samp><span class="file">figured-bass-implicit.ly</span></samp>
</a>
<p>Implicit bass figures are not printed, but they do get extenders.
<p>
<a href="63/lily-9c08359a.ly">
<img align="middle"
border="0" src="63/lily-9c08359a.png" alt="[image of music]">
</a>
</p>
<p><a name="figured-bass-slashed-numbers.ly"></a>
<p><a href="8a/lily-e9544f5b.ly"><samp><span class="file">figured-bass-slashed-numbers.ly</span></samp>
</a> <p>
<a href="8a/lily-e9544f5b.ly">
<img align="middle"
border="0" src="8a/lily-e9544f5b.png" alt="[image of music]">
</a>
</p>
<p><a name="figured-bass-staff.ly"></a>
<p><a href="65/lily-5d1dbe93.ly"><samp><span class="file">figured-bass-staff.ly</span></samp>
</a>
<p>Figured bass can also be added to Staff context directly.
In that case, the figures must be entered with <code>\figuremode</code> and be directed
to an existing <code>Staff</code> context.
<p>Since these engravers are on <code>Staff</code> level, properties
controlling figured bass should be set in <code>Staff</code> context.
<p class="noindent"><p>
<a href="65/lily-5d1dbe93.ly">
<img align="middle"
border="0" src="65/lily-5d1dbe93.png" alt="[image of music]">
</a>
</p>
<p><a name="figured-bass.ly"></a>
<p><a href="f2/lily-90b03741.ly"><samp><span class="file">figured-bass.ly</span></samp>
</a>
<p>Figured bass is created by the FiguredBass context which
responds to figured bass events and rest events. You must enter these
using the special <code>\figuremode { }</code> mode, which allows you to
type numbers, like <code><4 6+></code> and add slashes, backslashes and pluses.
<p>You can also enter markup strings. The vertical alignment may also be tuned.
<p class="noindent"><p>
<a href="f2/lily-90b03741.ly">
<img align="middle"
border="0" src="f2/lily-90b03741.png" alt="[image of music]">
</a>
</p>
<p><a name="fill-line-test.ly"></a>
<p><a href="c0/lily-e1e78d33.ly"><samp><span class="file">fill-line-test.ly</span></samp>
</a>
<p>The fill-line markup command should align texts in
columns. For example, the characters in the center should form one
column.
<p>
<a href="c0/lily-e1e78d33.ly">
<img align="middle"
border="0" src="c0/lily-e1e78d33.png" alt="[image of music]">
</a>
</p>
<p><a name="finger-chords-accidental.ly"></a>
<p><a href="22/lily-c042878d.ly"><samp><span class="file">finger-chords-accidental.ly</span></samp>
</a>
<p>Scripts left of a chord avoid accidentals.
<p>
<a href="22/lily-c042878d.ly">
<img align="middle"
border="0" src="22/lily-c042878d.png" alt="[image of music]">
</a>
</p>
<p><a name="finger-chords-order.ly"></a>
<p><a href="a7/lily-dadbda1e.ly"><samp><span class="file">finger-chords-order.ly</span></samp>
</a>
<p>Ordering of the fingerings depends on vertical ordering of the notes, and
is independent of up/down direction.
<p>
<a href="a7/lily-dadbda1e.ly">
<img align="middle"
border="0" src="a7/lily-dadbda1e.png" alt="[image of music]">
</a>
</p>
<p><a name="finger-chords.ly"></a>
<p><a href="4f/lily-706008bf.ly"><samp><span class="file">finger-chords.ly</span></samp>
</a>
<p>It is possible to associate
fingerings uniquely with notes. This makes it possible to add
horizontal fingerings to notes.
<p class="noindent"><p>
<a href="4f/lily-706008bf.ly">
<img align="middle"
border="0" src="4f/lily-706008bf.png" alt="[image of music]">
</a>
</p>
<p><a name="fingering-cross-staff.ly"></a>
<p><a href="82/lily-9cb4dad8.ly"><samp><span class="file">fingering-cross-staff.ly</span></samp>
</a>
<p>Fingerings work correctly with cross-staff beams.
<p>
<a href="82/lily-9cb4dad8.ly">
<img align="middle"
border="0" src="82/lily-9cb4dad8.png" alt="[image of music]">
</a>
</p>
<p><a name="fingering.ly"></a>
<p><a href="f0/lily-3f050e5e.ly"><samp><span class="file">fingering.ly</span></samp>
</a>
<p>Automatic fingering tries to put fingering instructions
next to noteheads.
<p class="noindent"><p>
<a href="f0/lily-3f050e5e.ly">
<img align="middle"
border="0" src="f0/lily-3f050e5e.png" alt="[image of music]">
</a>
</p>
<p><a name="follow-voice-break.ly"></a>
<p><a href="87/lily-d494af25.ly"><samp><span class="file">follow-voice-break.ly</span></samp>
</a>
<p>The line-spanners connects to the Y position of the note on the next line.
When put across line breaks, only the part before the line break is
printed.
<p class="noindent"><p>
<a href="87/lily-d494af25.ly">
<img align="middle"
border="0" src="87/lily-d494af25.png" alt="[image of music]">
</a>
</p>
<p><a name="follow-voice-consecutive.ly"></a>
<p><a href="4a/lily-d86a6424.ly"><samp><span class="file">follow-voice-consecutive.ly</span></samp>
</a>
<p>The voice follower is not confused when set for consecutive
sets of staff switches.
<p>
<a href="4a/lily-d86a6424.ly">
<img align="middle"
border="0" src="4a/lily-d86a6424.png" alt="[image of music]">
</a>
</p>
<p><a name="font-bogus-ligature.ly"></a>
<p><a href="82/lily-3d498fd9.ly"><samp><span class="file">font-bogus-ligature.ly</span></samp>
</a>
<p>TM and No should not be changed into trademark/number symbols.
This may happen with incorrect font versions.
<p class="noindent"><p>
<a href="82/lily-3d498fd9.ly">
<img align="middle"
border="0" src="82/lily-3d498fd9.png" alt="[image of music]">
</a>
</p>
<p><a name="font-family-override.ly"></a>
<p><a href="c7/lily-cd4a154a.ly"><samp><span class="file">font-family-override.ly</span></samp>
</a>
<p>The default font families for text can be
overridden with <code>make-pango-font-tree</code>
<p>
<a href="c7/lily-cd4a154a.ly">
<img align="middle"
border="0" src="c7/lily-cd4a154a.png" alt="[image of music]">
</a>
</p>
<p><a name="font-kern.ly"></a>
<p><a href="ea/lily-de5f98fe.ly"><samp><span class="file">font-kern.ly</span></samp>
</a>
<p>Text set in TrueType Fonts that contain kerning tables, are kerned.
<p>
<a href="ea/lily-de5f98fe.ly">
<img align="middle"
border="0" src="ea/lily-de5f98fe.png" alt="[image of music]">
</a>
</p>
<p><a name="font-name.ly"></a>
<p><a href="b4/lily-61baa760.ly"><samp><span class="file">font-name.ly</span></samp>
</a>
<p>Other fonts can be used by setting <code>font-name</code> for
the appropriate object. The string should be a Pango font description
without size specification.
<p>
<a href="b4/lily-61baa760.ly">
<img align="middle"
border="0" src="b4/lily-61baa760.png" alt="[image of music]">
</a>
</p>
<p><a name="font-postscript.ly"></a>
<p><a href="eb/lily-b6eff249.ly"><samp><span class="file">font-postscript.ly</span></samp>
</a>
<p>This file demonstrates how to load different
(postscript) fonts. The file <samp><span class="file">font.scm</span></samp> shows how to define
the scheme-function <code>make-century-schoolbook-tree</code>.
<p>This file should be run with the TeX and extra options should be
passed to LaTeX and dvips to help it find the uncb font.
<p>
<a href="eb/lily-b6eff249.ly">
<img align="middle"
border="0" src="eb/lily-b6eff249.png" alt="[image of music]">
</a>
</p>
<p><a name="fret-boards.ly"></a>
<p><a href="eb/lily-8f93cae9.ly"><samp><span class="file">fret-boards.ly</span></samp>
</a>
<p>Frets can be assigned automatically. The results will be
best when one string number is indicated in advance
<p>
<a href="eb/lily-8f93cae9.ly">
<img align="middle"
border="0" src="eb/lily-8f93cae9.png" alt="[image of music]">
</a>
</p>
<p><a name="fret-diagrams.ly"></a>
<p><a href="97/lily-034a5a19.ly"><samp><span class="file">fret-diagrams.ly</span></samp>
</a> <p>
<a href="97/lily-034a5a19.ly">
<img align="middle"
border="0" src="97/lily-034a5a19.png" alt="[image of music]">
</a>
</p>
<p><a name="general-scheme-bindings.ly"></a>
<p><a href="96/lily-6d2e5597.ly"><samp><span class="file">general-scheme-bindings.ly</span></samp>
</a>
<p>This file tests various Scheme utility functions.
<p>
<a href="96/lily-6d2e5597.ly">
<img align="middle"
border="0" src="96/lily-6d2e5597.png" alt="[image of music]">
</a>
</p>
<p><a name="generic-output-property.ly"></a>
<p><a href="48/lily-fda4b94a.ly"><samp><span class="file">generic-output-property.ly</span></samp>
</a>
<p>As a last resort, the placement of grobs can be adjusted manually, by
setting the <code>extra-offset</code> of a grob.
<p class="noindent"><p>
<a href="48/lily-fda4b94a.ly">
<img align="middle"
border="0" src="48/lily-fda4b94a.png" alt="[image of music]">
</a>
</p>
<p><a name="glissando-broken.ly"></a>
<p><a href="a2/lily-14557f5a.ly"><samp><span class="file">glissando-broken.ly</span></samp>
</a>
<p>If broken, Glissandi anticipate on the pitch of the next line.
<p>
<a href="a2/lily-14557f5a.ly">
<img align="middle"
border="0" src="a2/lily-14557f5a.png" alt="[image of music]">
</a>
</p>
<p><a name="glissando-no-break.ly"></a>
<p><a href="66/lily-5c01ffc8.ly"><samp><span class="file">glissando-no-break.ly</span></samp>
</a>
<p>Glissandi are not broken. Here a <code>\break</code> is ineffective.
Use <code>breakable</code> grob property to override.
<p>
<a href="66/lily-5c01ffc8.ly">
<img align="middle"
border="0" src="66/lily-5c01ffc8.png" alt="[image of music]">
</a>
</p>
<p><a name="glissando.ly"></a>
<p><a href="a1/lily-ba8400ab.ly"><samp><span class="file">glissando.ly</span></samp>
</a>
<p>Between notes, there may be simple glissando lines.
Here, the first two glissandi are not consecutive.
<p>The engraver does no time-keeping, so it involves some trickery to get
<< { s8 s8 s4 } { c4 \gliss d4 } >> working correctly.
<p class="noindent"><p>
<a href="a1/lily-ba8400ab.ly">
<img align="middle"
border="0" src="a1/lily-ba8400ab.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-auto-beam.ly"></a>
<p><a href="cc/lily-9bb106e7.ly"><samp><span class="file">grace-auto-beam.ly</span></samp>
</a>
<p>The autobeamer is not confused by grace notes.
<p>
<a href="cc/lily-9bb106e7.ly">
<img align="middle"
border="0" src="cc/lily-9bb106e7.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-bar-line.ly"></a>
<p><a href="e5/lily-793faa21.ly"><samp><span class="file">grace-bar-line.ly</span></samp>
</a>
<p>Bar line should come before the grace note.
<p>
<a href="e5/lily-793faa21.ly">
<img align="middle"
border="0" src="e5/lily-793faa21.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-bar-number.ly"></a>
<p><a href="4a/lily-420917e2.ly"><samp><span class="file">grace-bar-number.ly</span></samp>
</a>
<p>Grace notes do tricky things with timing. If a measure
starts with a grace note, the measure does not start at 0, but
earlier. Nevertheless, lily should not get confused. For example, line
breaks should be possible at grace notes, and the bar number should be
printed correctly.
<p class="noindent"><p>
<a href="4a/lily-420917e2.ly">
<img align="middle"
border="0" src="4a/lily-420917e2.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-beam.ly"></a>
<p><a href="5f/lily-f03eb237.ly"><samp><span class="file">grace-beam.ly</span></samp>
</a>
<p>Grace beams and normal beams may occur simultaneously.
Unbeamed grace notes are not put into normal beams.
<p class="noindent"><p>
<a href="5f/lily-f03eb237.ly">
<img align="middle"
border="0" src="5f/lily-f03eb237.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-direction-polyphony.ly"></a>
<p><a href="d1/lily-96438522.ly"><samp><span class="file">grace-direction-polyphony.ly</span></samp>
</a>
<p>The <code>\voiceOne</code> setting is retained after
finishing the grace section.
<p>
<a href="d1/lily-96438522.ly">
<img align="middle"
border="0" src="d1/lily-96438522.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-end-2.ly"></a>
<p><a href="ed/lily-5663ca48.ly"><samp><span class="file">grace-end-2.ly</span></samp>
</a>
<p>Grace notes at the end of an expression don't cause crashes.
<p>
<a href="ed/lily-5663ca48.ly">
<img align="middle"
border="0" src="ed/lily-5663ca48.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-end.ly"></a>
<p><a href="10/lily-2d98b27c.ly"><samp><span class="file">grace-end.ly</span></samp>
</a>
<p><a name="index-Grace-End-6"></a> Grace notes after the last note do not confuse the timing code.
<p>
<a href="10/lily-2d98b27c.ly">
<img align="middle"
border="0" src="10/lily-2d98b27c.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-nest1.ly"></a>
<p><a href="27/lily-dca8c9e2.ly"><samp><span class="file">grace-nest1.ly</span></samp>
</a>
<p>Grace code should not be confused by nested sequential music containing grace notes; practically speaking, this means that the end-bar and measure bar coincide in this example.
<p>
<a href="27/lily-dca8c9e2.ly">
<img align="middle"
border="0" src="27/lily-dca8c9e2.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-nest2.ly"></a>
<p><a href="08/lily-50896fa4.ly"><samp><span class="file">grace-nest2.ly</span></samp>
</a>
<p>Grace code should not be confused by nested sequential music containing grace notes; practically speaking, this means that the end-bar and measure bar coincide in this example.
<p>
<a href="08/lily-50896fa4.ly">
<img align="middle"
border="0" src="08/lily-50896fa4.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-nest3.ly"></a>
<p><a href="2f/lily-da45ddbe.ly"><samp><span class="file">grace-nest3.ly</span></samp>
</a>
<p>In nested syntax, graces are still properly handled.
<p>
<a href="2f/lily-da45ddbe.ly">
<img align="middle"
border="0" src="2f/lily-da45ddbe.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-nest4.ly"></a>
<p><a href="88/lily-d229598b.ly"><samp><span class="file">grace-nest4.ly</span></samp>
</a>
<p>Also in the nested syntax here, grace notes appear rightly.
<p>
<a href="88/lily-d229598b.ly">
<img align="middle"
border="0" src="88/lily-d229598b.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-nest5.ly"></a>
<p><a href="bf/lily-d24ca622.ly"><samp><span class="file">grace-nest5.ly</span></samp>
</a>
<p>Graces notes may have the same duration as the main note.
<p>
<a href="bf/lily-d24ca622.ly">
<img align="middle"
border="0" src="bf/lily-d24ca622.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-part-combine.ly"></a>
<p><a href="15/lily-2fead398.ly"><samp><span class="file">grace-part-combine.ly</span></samp>
</a>
<p>Grace notes may be put in a <code>partcombine</code>r.
<p>
<a href="15/lily-2fead398.ly">
<img align="middle"
border="0" src="15/lily-2fead398.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-partial.ly"></a>
<p><a href="dc/lily-87e5976c.ly"><samp><span class="file">grace-partial.ly</span></samp>
</a>
<p>A <code>\partial</code> may be combined with a
<code>\grace</code>.
<p>
<a href="dc/lily-87e5976c.ly">
<img align="middle"
border="0" src="dc/lily-87e5976c.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-staff-length.ly"></a>
<p><a href="89/lily-b7aa9506.ly"><samp><span class="file">grace-staff-length.ly</span></samp>
</a>
<p>Stripped version of trip.ly. Staves should be of correct length.
<p>
<a href="89/lily-b7aa9506.ly">
<img align="middle"
border="0" src="89/lily-b7aa9506.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-start.ly"></a>
<p><a href="ab/lily-a82eba66.ly"><samp><span class="file">grace-start.ly</span></samp>
</a>
<p>Pieces may begin with grace notes.
<p>
<a href="ab/lily-a82eba66.ly">
<img align="middle"
border="0" src="ab/lily-a82eba66.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-stem-length.ly"></a>
<p><a href="ca/lily-165cd412.ly"><samp><span class="file">grace-stem-length.ly</span></samp>
</a>
<p>Stem lengths for grace notes should be shorter than
normal notes, if possible. They should never be longer, even if that
would lead to beam quanting problems.
<p>
<a href="ca/lily-165cd412.ly">
<img align="middle"
border="0" src="ca/lily-165cd412.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-stems.ly"></a>
<p><a href="3d/lily-64ae220f.ly"><samp><span class="file">grace-stems.ly</span></samp>
</a>
<p>Here <code>startGraceMusic</code> should set <code>no-stem-extend</code> to
true; the two grace beams should be the same here.
<p class="noindent"><p>
<a href="3d/lily-64ae220f.ly">
<img align="middle"
border="0" src="3d/lily-64ae220f.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-sync.ly"></a>
<p><a href="e5/lily-73a6264c.ly"><samp><span class="file">grace-sync.ly</span></samp>
</a>
<p>Grace notes in different voices/staves are synchronized.
<p>
<a href="e5/lily-73a6264c.ly">
<img align="middle"
border="0" src="e5/lily-73a6264c.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-types.ly"></a>
<p><a href="98/lily-371ed573.ly"><samp><span class="file">grace-types.ly</span></samp>
</a>
<p>There are three different kinds of grace types: the base
grace switches to smaller type, the appoggiatura inserts also a slur, and the
acciaccatura inserts a slur and slashes the stem.
<p>
<a href="98/lily-371ed573.ly">
<img align="middle"
border="0" src="98/lily-371ed573.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-unfold-repeat.ly"></a>
<p><a href="21/lily-896871a1.ly"><samp><span class="file">grace-unfold-repeat.ly</span></samp>
</a>
<p>When grace notes are entered with unfolded repeats,
line breaks take place before grace notes.
<p class="noindent"><p>
<a href="21/lily-896871a1.ly">
<img align="middle"
border="0" src="21/lily-896871a1.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-volta-repeat-2.ly"></a>
<p><a href="f1/lily-5bc8dea1.ly"><samp><span class="file">grace-volta-repeat-2.ly</span></samp>
</a>
<p>A volta repeat may begin with a grace. Consecutive
ending and starting repeat bars are merged into one <code>:||:</code>.
<p>
<a href="f1/lily-5bc8dea1.ly">
<img align="middle"
border="0" src="f1/lily-5bc8dea1.png" alt="[image of music]">
</a>
</p>
<p><a name="grace-volta-repeat.ly"></a>
<p><a href="13/lily-9f95d796.ly"><samp><span class="file">grace-volta-repeat.ly</span></samp>
</a>
<p>Repeated music can start with grace notes. Bar checks
preceding the grace notes do not cause synchronization effects.
<p>
<a href="13/lily-9f95d796.ly">
<img align="middle"
border="0" src="13/lily-9f95d796.png" alt="[image of music]">
</a>
</p>
<p><a name="grace.ly"></a>
<p><a href="98/lily-d62e32c7.ly"><samp><span class="file">grace.ly</span></samp>
</a>
<p>You can have beams, notes, chords, stems etc. within a
<code>\grace</code> section. If there are tuplets, the grace notes will not
be under the brace.
<p>Main note scripts do not end up on the grace note.
<p class="noindent"><p>
<a href="98/lily-d62e32c7.ly">
<img align="middle"
border="0" src="98/lily-d62e32c7.png" alt="[image of music]">
</a>
</p>
<p><a name="graphviz.ly"></a>
<p><a href="7c/lily-5a2fdb88.ly"><samp><span class="file">graphviz.ly</span></samp>
</a>
<p>The graphviz feature draws dependency graphs for grob properties.
<p>
<a href="7c/lily-5a2fdb88.ly">
<img align="middle"
border="0" src="7c/lily-5a2fdb88.png" alt="[image of music]">
</a>
</p>
<p><a name="grid-lines.ly"></a>
<p><a href="3e/lily-557b510d.ly"><samp><span class="file">grid-lines.ly</span></samp>
</a>
<p>With grid lines, vertical lines can be drawn between
staves synchronized with the notes.
<p>
<a href="3e/lily-557b510d.ly">
<img align="middle"
border="0" src="3e/lily-557b510d.png" alt="[image of music]">
</a>
</p>
<p><a name="grob-tweak.ly"></a>
<p><a href="e7/lily-47f2058b.ly"><samp><span class="file">grob-tweak.ly</span></samp>
</a>
<p>With the <code>\tweak</code> function, individual grobs that
are directly caused by events may be tuned directly.
<p>
<a href="e7/lily-47f2058b.ly">
<img align="middle"
border="0" src="e7/lily-47f2058b.png" alt="[image of music]">
</a>
</p>
<p><a name="hairpin-barline-break.ly"></a>
<p><a href="4e/lily-61c03c0c.ly"><samp><span class="file">hairpin-barline-break.ly</span></samp>
</a>
<p>If a hairpin ends on the first note of a new stave, we
do not print that ending. But on the previous line, this hairpin
should not be left open, and should end at the bar line.
<p>
<a href="4e/lily-61c03c0c.ly">
<img align="middle"
border="0" src="4e/lily-61c03c0c.png" alt="[image of music]">
</a>
</p>
<p><a name="hairpin-circled.ly"></a>
<p><a href="0c/lily-7a3f8e51.ly"><samp><span class="file">hairpin-circled.ly</span></samp>
</a>
<p>Hairpins can have circled tips. A decrescendo del niente
followed by a crescendo al niente should only print one circle.
<p>
<a href="0c/lily-7a3f8e51.ly">
<img align="middle"
border="0" src="0c/lily-7a3f8e51.png" alt="[image of music]">
</a>
</p>
<p><a name="hairpin-dashed.ly"></a>
<p><a href="bb/lily-627f64c6.ly"><samp><span class="file">hairpin-dashed.ly</span></samp>
</a>
<p>Hairpin crescendi may be dashed.
<p>
<a href="bb/lily-627f64c6.ly">
<img align="middle"
border="0" src="bb/lily-627f64c6.png" alt="[image of music]">
</a>
</p>
<p><a name="hairpin-ending.ly"></a>
<p><a href="2b/lily-de0daea8.ly"><samp><span class="file">hairpin-ending.ly</span></samp>
</a>
<p>Hairpin dynamics start under notes if there are
no text-dynamics. If there are text dynamics, the hairpin does not run
into them.
<p>
<a href="2b/lily-de0daea8.ly">
<img align="middle"
border="0" src="2b/lily-de0daea8.png" alt="[image of music]">
</a>
</p>
<p><a name="hairpin-to-barline-mark.ly"></a>
<p><a href="12/lily-3f6f1b24.ly"><samp><span class="file">hairpin-to-barline-mark.ly</span></samp>
</a>
<p>'to-barline is not confused by very long marks.
<p>
<a href="12/lily-3f6f1b24.ly">
<img align="middle"
border="0" src="12/lily-3f6f1b24.png" alt="[image of music]">
</a>
</p>
<p><a name="hairpin-to-barline.ly"></a>
<p><a href="a0/lily-6a75c38c.ly"><samp><span class="file">hairpin-to-barline.ly</span></samp>
</a>
<p>Hairpins whose end note is preceded by a bar line
should end at that bar line.
<p>
<a href="a0/lily-6a75c38c.ly">
<img align="middle"
border="0" src="a0/lily-6a75c38c.png" alt="[image of music]">
</a>
</p>
<p><a name="hairpin-to-rest.ly"></a>
<p><a href="f1/lily-a61e5be4.ly"><samp><span class="file">hairpin-to-rest.ly</span></samp>
</a>
<p>Hairpins end at the left edge of a rest.
<p>
<a href="f1/lily-a61e5be4.ly">
<img align="middle"
border="0" src="f1/lily-a61e5be4.png" alt="[image of music]">
</a>
</p>
<p><a name="hara-kiri-percent-repeat.ly"></a>
<p><a href="78/lily-502d3ed6.ly"><samp><span class="file">hara-kiri-percent-repeat.ly</span></samp>
</a>
<p>Staves with percent repeats are not killed.
<p>
<a href="78/lily-502d3ed6.ly">
<img align="middle"
border="0" src="78/lily-502d3ed6.png" alt="[image of music]">
</a>
</p>
<p><a name="hara-kiri-pianostaff.ly"></a>
<p><a href="20/lily-f560bcca.ly"><samp><span class="file">hara-kiri-pianostaff.ly</span></samp>
</a>
<p>Hara-kiri staves kill themselves if they are empty. This
example really contains three staves, but as they progress, empty ones
are removed: this example has three staves, but some of them
disappear: note how the 2nd line only has the bar number 2. (That the
bar number is printed might be considered a bug, however, the scenario
of all staves disappearing does not happen in practice.)
<p>Any staff brackets and braces are removed, both in the single staff
and no staff case.
<p>This example was done with a pianostaff, which has fixed distance
alignment; this should not confuse the mechanism.
<p class="noindent"><p>
<a href="20/lily-f560bcca.ly">
<img align="middle"
border="0" src="20/lily-f560bcca.png" alt="[image of music]">
</a>
</p>
<p><a name="hara-kiri-stanza-number.ly"></a>
<p><a href="97/lily-29193ddc.ly"><samp><span class="file">hara-kiri-stanza-number.ly</span></samp>
</a>
<p>stanza numbers remain, even on otherwise empty lyrics
lines.
<p>
<a href="97/lily-29193ddc.ly">
<img align="middle"
border="0" src="97/lily-29193ddc.png" alt="[image of music]">
</a>
</p>
<p><a name="harp-pedals-sanity-checks.ly"></a>
<p><a href="81/lily-39ee62e0.ly"><samp><span class="file">harp-pedals-sanity-checks.ly</span></samp>
</a>
<p>The harp-pedal markup function does some sanity checks. All
the diagrams here violate the standard (7 pedals with divider after third), so
a warning is printed out, but they should still look okay.
<p>
<a href="81/lily-39ee62e0.ly">
<img align="middle"
border="0" src="81/lily-39ee62e0.png" alt="[image of music]">
</a>
</p>
<p><a name="harp-pedals-tweaking.ly"></a>
<p><a href="8b/lily-bffe35ed.ly"><samp><span class="file">harp-pedals-tweaking.ly</span></samp>
</a>
<p>Harp pedals can be tweaked through the size, thickness and
harp-pedal-details properties of TextScript.
<p>
<a href="8b/lily-bffe35ed.ly">
<img align="middle"
border="0" src="8b/lily-bffe35ed.png" alt="[image of music]">
</a>
</p>
<p><a name="harp-pedals.ly"></a>
<p><a href="6b/lily-80ba05d8.ly"><samp><span class="file">harp-pedals.ly</span></samp>
</a>
<p>Basic harp diagram functionality, including circled pedal boxes.
The third diagram uses an empty string, the third contains invalid characters.
Both cases will create warnings, but should still not fail with an error.
<p>
<a href="6b/lily-80ba05d8.ly">
<img align="middle"
border="0" src="6b/lily-80ba05d8.png" alt="[image of music]">
</a>
</p>
<p><a name="horizontal-bracket-break.ly"></a>
<p><a href="7d/lily-0e9d1a09.ly"><samp><span class="file">horizontal-bracket-break.ly</span></samp>
</a>
<p>Horizontal brackets connect over line breaks.
<p>
<a href="7d/lily-0e9d1a09.ly">
<img align="middle"
border="0" src="7d/lily-0e9d1a09.png" alt="[image of music]">
</a>
</p>
<p><a name="horizontal-bracket.ly"></a>
<p><a href="76/lily-f1005b34.ly"><samp><span class="file">horizontal-bracket.ly</span></samp>
</a>
<p>Note grouping events are used to indicate where
analysis brackets start and end.
<p><a name="index-bracket-7"></a><a name="index-note-groups-8"></a><a name="index-music-analysis-9"></a><a name="index-analysis-10"></a>
<p class="noindent"><p>
<a href="76/lily-f1005b34.ly">
<img align="middle"
border="0" src="76/lily-f1005b34.png" alt="[image of music]">
</a>
</p>
<p><a name="identifier-following-chordmode.ly"></a>
<p><a href="f9/lily-304ff73f.ly"><samp><span class="file">identifier-following-chordmode.ly</span></samp>
</a>
<p>Identifiers following a chordmode section are not
interpreted as chordmode tokens. In the following snippet, the
identifier `m' is not interpreted by the lexer as as a minor chord
modifier.
<p>
<a href="f9/lily-304ff73f.ly">
<img align="middle"
border="0" src="f9/lily-304ff73f.png" alt="[image of music]">
</a>
</p>
<p><a name="identifiers.ly"></a>
<p><a href="af/lily-7947daf0.ly"><samp><span class="file">identifiers.ly</span></samp>
</a>
<p>test identifiers.
<p>
<a href="af/lily-7947daf0.ly">
<img align="middle"
border="0" src="af/lily-7947daf0.png" alt="[image of music]">
</a>
</p>
<p><a name="incipit.ly"></a>
<p><a href="ee/lily-54ffba6c.ly"><samp><span class="file">incipit.ly</span></samp>
</a>
<p>Incipit can be printed using an InstrumentName grob.
<p>
<a href="ee/lily-54ffba6c.ly">
<img align="middle"
border="0" src="ee/lily-54ffba6c.png" alt="[image of music]">
</a>
</p>
<p><a name="instrument-name-dynamic.ly"></a>
<p><a href="23/lily-c7da0b4d.ly"><samp><span class="file">instrument-name-dynamic.ly</span></samp>
</a>
<p>Instrument names (aligned on axis group spanners) ignore dynamic and
pedal line spanners.
<p>
<a href="23/lily-c7da0b4d.ly">
<img align="middle"
border="0" src="23/lily-c7da0b4d.png" alt="[image of music]">
</a>
</p>
<p><a name="instrument-name-hara-kiri.ly"></a>
<p><a href="97/lily-06fe842e.ly"><samp><span class="file">instrument-name-hara-kiri.ly</span></samp>
</a>
<p><code>PianoStaff.instrument</code> and
<code>PianoStaff.instr</code> are removed when the staves are killed off.
<p>In this example, the 2nd staff (marked by the barnumber 2) disappears
as does the instrument name.
<p>
<a href="97/lily-06fe842e.ly">
<img align="middle"
border="0" src="97/lily-06fe842e.png" alt="[image of music]">
</a>
</p>
<p><a name="instrument-name-markup.ly"></a>
<p><a href="b8/lily-12509686.ly"><samp><span class="file">instrument-name-markup.ly</span></samp>
</a>
<p>Instrument names are set with <code>Staff.instrument</code> and
<code>Staff.instr</code>. You can enter markup texts to create more funky names,
including alterations.
<p>
<a href="b8/lily-12509686.ly">
<img align="middle"
border="0" src="b8/lily-12509686.png" alt="[image of music]">
</a>
</p>
<p><a name="instrument-name-partial.ly"></a>
<p><a href="34/lily-f0f03921.ly"><samp><span class="file">instrument-name-partial.ly</span></samp>
</a>
<p>Instrument names are also printed on partial starting measures.
<p>
<a href="34/lily-f0f03921.ly">
<img align="middle"
border="0" src="34/lily-f0f03921.png" alt="[image of music]">
</a>
</p>
<p><a name="instrument-name-x-align.ly"></a>
<p><a href="62/lily-fe4cca70.ly"><samp><span class="file">instrument-name-x-align.ly</span></samp>
</a>
<p>Instrument names horizontal alignment is tweaked by
changing the <code>Staff.Instrument #'self-alignment-X</code> property. The
<code>\layout</code> variables <code>indent</code> and <code>short-indent</code> define
the space where the instrument names are aligned before the first and
the following systems, respectively.
<p>
<a href="62/lily-fe4cca70.ly">
<img align="middle"
border="0" src="62/lily-fe4cca70.png" alt="[image of music]">
</a>
</p>
<p><a name="instrument-name.ly"></a>
<p><a href="a2/lily-71c83851.ly"><samp><span class="file">instrument-name.ly</span></samp>
</a>
<p>Staff margins are also markings attached to barlines. They should be
left of the staff, and be centered vertically with respect to the staff.
They may be on normal staves, but also on compound staves, like the
PianoStaff.
<p class="noindent"><p>
<a href="a2/lily-71c83851.ly">
<img align="middle"
border="0" src="a2/lily-71c83851.png" alt="[image of music]">
</a>
</p>
<p><a name="instrument-switch.ly"></a>
<p><a href="2c/lily-9ceb73c1.ly"><samp><span class="file">instrument-switch.ly</span></samp>
</a>
<p>The <code>switchInstrument</code> music function modifies
properties for an in staff instrument switch.
<p>
<a href="2c/lily-9ceb73c1.ly">
<img align="middle"
border="0" src="2c/lily-9ceb73c1.png" alt="[image of music]">
</a>
</p>
<p><a name="key-clefs.ly"></a>
<p><a href="f1/lily-08d9f278.ly"><samp><span class="file">key-clefs.ly</span></samp>
</a>
<p>Each clef has its own accidental placing
rules.
<p>
<a href="f1/lily-08d9f278.ly">
<img align="middle"
border="0" src="f1/lily-08d9f278.png" alt="[image of music]">
</a>
</p>
<p><a name="key-signature-cancellation-extra-natural.ly"></a>
<p><a href="19/lily-3f22bb4a.ly"><samp><span class="file">key-signature-cancellation-extra-natural.ly</span></samp>
</a>
<p>If <code>extraNatural</code> is set then keys that are not
altered farther away (eg from sharp to double sharp) are
cancelled. Otherwise only keys that do not occur in the new key
signature are cancelled.
<p>
<a href="19/lily-3f22bb4a.ly">
<img align="middle"
border="0" src="19/lily-3f22bb4a.png" alt="[image of music]">
</a>
</p>
<p><a name="key-signature-cancellation.ly"></a>
<p><a href="52/lily-a714908b.ly"><samp><span class="file">key-signature-cancellation.ly</span></samp>
</a>
<p>Key cancellation signs consists of naturals for pitches
that are not in the new key signature. Naturals get a little padding
so the stems don't collide.
<p>
<a href="52/lily-a714908b.ly">
<img align="middle"
border="0" src="52/lily-a714908b.png" alt="[image of music]">
</a>
</p>
<p><a name="key-signature-padding.ly"></a>
<p><a href="99/lily-702a0f4f.ly"><samp><span class="file">key-signature-padding.ly</span></samp>
</a>
<p>With the <code>padding-pairs</code> property, distances
between individual key signature items can be adjusted.
<p>
<a href="99/lily-702a0f4f.ly">
<img align="middle"
border="0" src="99/lily-702a0f4f.png" alt="[image of music]">
</a>
</p>
<p><a name="key-signature-scordatura.ly"></a>
<p><a href="a3/lily-06f531bf.ly"><samp><span class="file">key-signature-scordatura.ly</span></samp>
</a>
<p>By setting <code>Staff.keySignature</code> directly,
key signatures can be set invidually per pitch.
<p class="noindent"><p>
<a href="a3/lily-06f531bf.ly">
<img align="middle"
border="0" src="a3/lily-06f531bf.png" alt="[image of music]">
</a>
</p>
<p><a name="keys.ly"></a>
<p><a href="1e/lily-32fbb066.ly"><samp><span class="file">keys.ly</span></samp>
</a>
<p>Key signatures may appear on key changes, even without a barline.
In the case of a line break, the restoration accidentals are printed at
end of a line. If <code>createKeyOnClefChange</code> is set, key signatures
are created also on a clef change.
<p class="noindent"><p>
<a href="1e/lily-32fbb066.ly">
<img align="middle"
border="0" src="1e/lily-32fbb066.png" alt="[image of music]">
</a>
</p>
<p><a name="laissez-vibrer-tie-beam.ly"></a>
<p><a href="12/lily-7b0c876a.ly"><samp><span class="file">laissez-vibrer-tie-beam.ly</span></samp>
</a>
<p><code>\laissezVibrer</code> ties on beamed notes don't trigger
premature beam slope calculation.
<p>
<a href="12/lily-7b0c876a.ly">
<img align="middle"
border="0" src="12/lily-7b0c876a.png" alt="[image of music]">
</a>
</p>
<p><a name="laissez-vibrer-ties.ly"></a>
<p><a href="3e/lily-736f1535.ly"><samp><span class="file">laissez-vibrer-ties.ly</span></samp>
</a>
<p>l.v. ties should avoid dots and staff lines, similar to normal ties.
They have fixed size. Their formatting can be tuned with
<code>tie-configuration</code>.
<p class="noindent"><p>
<a href="3e/lily-736f1535.ly">
<img align="middle"
border="0" src="3e/lily-736f1535.png" alt="[image of music]">
</a>
</p>
<p><a name="landscape.ly"></a>
<p><a href="28/lily-a8b6b71b.ly"><samp><span class="file">landscape.ly</span></samp>
</a>
<p>Scores may be printed in landcape mode.
<p>
<a href="28/lily-a8b6b71b.ly">
<img align="middle"
border="0" src="28/lily-a8b6b71b.png" alt="[image of music]">
</a>
</p>
<p><a name="ledger-line-minimum.ly"></a>
<p><a href="3d/lily-73d5909d.ly"><samp><span class="file">ledger-line-minimum.ly</span></samp>
</a>
<p>When ledgered notes are very close, for example, in grace
notes, they are kept at a minimum distance to prevent the ledgers from
disappearing.
<p>
<a href="3d/lily-73d5909d.ly">
<img align="middle"
border="0" src="3d/lily-73d5909d.png" alt="[image of music]">
</a>
</p>
<p><a name="ledger-line-shorten.ly"></a>
<p><a href="cb/lily-144845b2.ly"><samp><span class="file">ledger-line-shorten.ly</span></samp>
</a>
<p>Ledger lines are shortened when they are very close. This ensures
that ledger lines stay separate.
<p>
<a href="cb/lily-144845b2.ly">
<img align="middle"
border="0" src="cb/lily-144845b2.png" alt="[image of music]">
</a>
</p>
<p><a name="ledger-lines-varying-staves.ly"></a>
<p><a href="a5/lily-7243d208.ly"><samp><span class="file">ledger-lines-varying-staves.ly</span></samp>
</a>
<p>Ledger lines should appear at every other location
for a variety of staves using both <code>line-count</code> and
<code>line-positions</code>.
<p>
<a href="a5/lily-7243d208.ly">
<img align="middle"
border="0" src="a5/lily-7243d208.png" alt="[image of music]">
</a>
</p>
<p><a name="ligature-bracket.ly"></a>
<p><a href="f6/lily-c095ba23.ly"><samp><span class="file">ligature-bracket.ly</span></samp>
</a>
<p>The ligature bracket right-end is not affected by other voices.
<p>
<a href="f6/lily-c095ba23.ly">
<img align="middle"
border="0" src="f6/lily-c095ba23.png" alt="[image of music]">
</a>
</p>
<p><a name="lily-in-scheme.ly"></a>
<p><a href="26/lily-bd80fe98.ly"><samp><span class="file">lily-in-scheme.ly</span></samp>
</a>
<p>LilyPond syntax can be used inside scheme to
build music expressions, with the <code>#{ ... #}</code> syntax.
Scheme forms can be introduced inside these blocks by escaping
them with a <code>$</code>, both in a LilyPond context or in a Scheme
context.
<p>In this example, the <code>\withpaddingA</code>, <code>\withpaddingB</code> and
<code>\withpaddingC</code> music functions set different kinds of padding on
the <code>TextScript</code> grob.
<p class="noindent"><p>
<a href="26/lily-bd80fe98.ly">
<img align="middle"
border="0" src="26/lily-bd80fe98.png" alt="[image of music]">
</a>
</p>
<p><a name="line-arrows.ly"></a>
<p><a href="a0/lily-40e429d7.ly"><samp><span class="file">line-arrows.ly</span></samp>
</a>
<p>Arrows can be applied to text-spanners and line-spanners (such as the Glissando)
<p>
<a href="a0/lily-40e429d7.ly">
<img align="middle"
border="0" src="a0/lily-40e429d7.png" alt="[image of music]">
</a>
</p>
<p><a name="line-dash-small-period.ly"></a>
<p><a href="04/lily-07f19cda.ly"><samp><span class="file">line-dash-small-period.ly</span></samp>
</a>
<p>Generate valid postscript even if dash-period is small
compared to line thickness.
<p>
<a href="04/lily-07f19cda.ly">
<img align="middle"
border="0" src="04/lily-07f19cda.png" alt="[image of music]">
</a>
</p>
<p><a name="line-dashed-period.ly"></a>
<p><a href="47/lily-c195cd3c.ly"><samp><span class="file">line-dashed-period.ly</span></samp>
</a>
<p>The period of a dashed line is adjusted such that it
starts and ends on a full dash.
<p>
<a href="47/lily-c195cd3c.ly">
<img align="middle"
border="0" src="47/lily-c195cd3c.png" alt="[image of music]">
</a>
</p>
<p><a name="line-style.ly"></a>
<p><a href="82/lily-cd4f103f.ly"><samp><span class="file">line-style.ly</span></samp>
</a>
<p>Cover all line styles available
<p>
<a href="82/lily-cd4f103f.ly">
<img align="middle"
border="0" src="82/lily-cd4f103f.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-combine-new.ly"></a>
<p><a href="68/lily-61faf160.ly"><samp><span class="file">lyric-combine-new.ly</span></samp>
</a>
<p>With the <code>\lyricsto</code> mechanism, individual lyric
lines can be associated with one melody line. Each lyric line
can be tuned to either follow or ignore melismata.
<p>
<a href="68/lily-61faf160.ly">
<img align="middle"
border="0" src="68/lily-61faf160.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-combine-polyphonic.ly"></a>
<p><a href="8b/lily-f3c13f5f.ly"><samp><span class="file">lyric-combine-polyphonic.ly</span></samp>
</a>
<p>Polyphonic rhythms and rests do not disturb
<code>\lyricsto</code>.
<p>
<a href="8b/lily-f3c13f5f.ly">
<img align="middle"
border="0" src="8b/lily-f3c13f5f.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-combine-switch-voice-2.ly"></a>
<p><a href="30/lily-0d41282e.ly"><samp><span class="file">lyric-combine-switch-voice-2.ly</span></samp>
</a>
<p>switching voices in the middle of the lyrics is possible using <code>lyricsto</code>.
<p>
<a href="30/lily-0d41282e.ly">
<img align="middle"
border="0" src="30/lily-0d41282e.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-combine-switch-voice.ly"></a>
<p><a href="19/lily-a7eecb51.ly"><samp><span class="file">lyric-combine-switch-voice.ly</span></samp>
</a>
<p>Switching the melody to a different voice works even
if the switch occurs together with context instantiation.
<p>
<a href="19/lily-a7eecb51.ly">
<img align="middle"
border="0" src="19/lily-a7eecb51.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-combine.ly"></a>
<p><a href="8f/lily-dcbde598.ly"><samp><span class="file">lyric-combine.ly</span></samp>
</a>
<p>Lyrics can be set to a melody automatically. Excess
lyrics will be discarded. Lyrics will not be set over rests. You can
have melismata either by setting a property melismaBusy, or by setting
automaticMelismas (which will set melismas during slurs and ties). If
you want a different order than first Music, then Lyrics, you must
precook a chord of staves/lyrics and label those. Of course, the
lyrics ignore any other rhythms in the piece.
<p>
<a href="8f/lily-dcbde598.ly">
<img align="middle"
border="0" src="8f/lily-dcbde598.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-extender-broken.ly"></a>
<p><a href="64/lily-9fd87c7a.ly"><samp><span class="file">lyric-extender-broken.ly</span></samp>
</a>
<p>Lyric extenders run to the end of the line if it
continues the next line. Otherwise, it should run to the last note
of the melisma.
<p>
<a href="64/lily-9fd87c7a.ly">
<img align="middle"
border="0" src="64/lily-9fd87c7a.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-extender-no-heads.ly"></a>
<p><a href="f8/lily-d2cbd81a.ly"><samp><span class="file">lyric-extender-no-heads.ly</span></samp>
</a>
<p>Extender engraver also notices the lack of note heads.
Here the extender ends on the 2nd quarter note, despite the grace note
without a lyric attached.
<p>
<a href="f8/lily-d2cbd81a.ly">
<img align="middle"
border="0" src="f8/lily-d2cbd81a.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-extender-rest.ly"></a>
<p><a href="d2/lily-413b141c.ly"><samp><span class="file">lyric-extender-rest.ly</span></samp>
</a>
<p>If <code>extendersOverRests</code> is set, an extender
is not terminated upon encountering a rest.
<p>
<a href="d2/lily-413b141c.ly">
<img align="middle"
border="0" src="d2/lily-413b141c.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-extender-right-margin.ly"></a>
<p><a href="49/lily-8b827dc5.ly"><samp><span class="file">lyric-extender-right-margin.ly</span></samp>
</a>
<p>Extenders will not protrude into the right margin
<p>
<a href="49/lily-8b827dc5.ly">
<img align="middle"
border="0" src="49/lily-8b827dc5.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-extender.ly"></a>
<p><a href="f4/lily-17658757.ly"><samp><span class="file">lyric-extender.ly</span></samp>
</a>
<p>A LyricExtender may span several notes. A LyricExtender
does not extend past a rest, or past the next lyric syllable.
<p>
<a href="f4/lily-17658757.ly">
<img align="middle"
border="0" src="f4/lily-17658757.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-hyphen-break.ly"></a>
<p><a href="aa/lily-06228277.ly"><samp><span class="file">lyric-hyphen-break.ly</span></samp>
</a>
<p>Hyphens are printed at the beginning of the line only when
they go past the first note.
<p>
<a href="aa/lily-06228277.ly">
<img align="middle"
border="0" src="aa/lily-06228277.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-hyphen-retain.ly"></a>
<p><a href="1f/lily-4a9d4d3c.ly"><samp><span class="file">lyric-hyphen-retain.ly</span></samp>
</a>
<p>The minimum distance between lyrics is determined by the
<code>minimum-distance</code> of <code>LyricHyphen</code> and
<code>LyricSpace</code>.
<p>The ideal length of a hyphen is determined by its <code>length</code>
property, but it may be shortened down to <code>minimum-length</code> in
tight situations. If in this it still does not fit, the hyphen will be
omitted.
<p>Like all overrides within <code>\lyricsto</code> and <code>\addlyrics</code>, the
effect of a setting is delayed is one syllable.
<p>
<a href="1f/lily-4a9d4d3c.ly">
<img align="middle"
border="0" src="1f/lily-4a9d4d3c.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-hyphen.ly"></a>
<p><a href="a2/lily-4cceb7c2.ly"><samp><span class="file">lyric-hyphen.ly</span></samp>
</a>
<p>In lyrics, hyphens may be used.
<p>
<a href="a2/lily-4cceb7c2.ly">
<img align="middle"
border="0" src="a2/lily-4cceb7c2.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-melisma-manual.ly"></a>
<p><a href="fd/lily-79c1f7a6.ly"><samp><span class="file">lyric-melisma-manual.ly</span></samp>
</a>
<p>Melisma's may be entered manually by substituting
<code>_</code> for lyrics on notes that are part of the melisma.
<p>
<a href="fd/lily-79c1f7a6.ly">
<img align="middle"
border="0" src="fd/lily-79c1f7a6.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-no-association-rhythm.ly"></a>
<p><a href="56/lily-f20899ab.ly"><samp><span class="file">lyric-no-association-rhythm.ly</span></samp>
</a>
<p>When lyrics are not associated with specific voices, the
lyric placement should follow lyric rhythms. In particular, the
second syllable here should not be attached to the first note of the first staff.
<p>
<a href="56/lily-f20899ab.ly">
<img align="middle"
border="0" src="56/lily-f20899ab.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-phrasing.ly"></a>
<p><a href="bb/lily-2fc84273.ly"><samp><span class="file">lyric-phrasing.ly</span></samp>
</a>
<p>Normally, the lyric is centered on the note head. However, on
melismata, the text is left aligned on the left-side of the note head.
<p class="noindent"><p>
<a href="bb/lily-2fc84273.ly">
<img align="middle"
border="0" src="bb/lily-2fc84273.png" alt="[image of music]">
</a>
</p>
<p><a name="lyric-tie.ly"></a>
<p><a href="c7/lily-31ba4958.ly"><samp><span class="file">lyric-tie.ly</span></samp>
</a>
<p>Tildes in lyric syllables are converted to tie symbols.
<p>
<a href="c7/lily-31ba4958.ly">
<img align="middle"
border="0" src="c7/lily-31ba4958.png" alt="[image of music]">
</a>
</p>
<p><a name="lyrics-after-grace.ly"></a>
<p><a href="ab/lily-a08841e7.ly"><samp><span class="file">lyrics-after-grace.ly</span></samp>
</a>
<p>Lyrics are ignored for aftergrace notes.
<p>
<a href="ab/lily-a08841e7.ly">
<img align="middle"
border="0" src="ab/lily-a08841e7.png" alt="[image of music]">
</a>
</p>
<p><a name="lyrics-bar.ly"></a>
<p><a href="cc/lily-88a57848.ly"><samp><span class="file">lyrics-bar.ly</span></samp>
</a>
<p>Adding a <code>Bar_engraver</code> to the Lyrics context makes sure that
lyrics do not collide with barlines.
<p class="noindent"><p>
<a href="cc/lily-88a57848.ly">
<img align="middle"
border="0" src="cc/lily-88a57848.png" alt="[image of music]">
</a>
</p>
<p><a name="lyrics-melisma-beam.ly"></a>
<p><a href="f1/lily-398e77f5.ly"><samp><span class="file">lyrics-melisma-beam.ly</span></samp>
</a>
<p>Melismata are triggered by manual beams.
<p>
<a href="f1/lily-398e77f5.ly">
<img align="middle"
border="0" src="f1/lily-398e77f5.png" alt="[image of music]">
</a>
</p>
<p><a name="lyrics-no-notes.ly"></a>
<p><a href="b2/lily-98c1f233.ly"><samp><span class="file">lyrics-no-notes.ly</span></samp>
</a>
<p>Lyric syllables without note attachment are not
centered. Centering may cause unintended effects when the
paper column is very wide.
<p>
<a href="b2/lily-98c1f233.ly">
<img align="middle"
border="0" src="b2/lily-98c1f233.png" alt="[image of music]">
</a>
</p>
<p><a name="lyrics-tenor-clef.ly"></a>
<p><a href="49/lily-db5f8e44.ly"><samp><span class="file">lyrics-tenor-clef.ly</span></samp>
</a>
<p>Lyrics are not lowered despite the presence of an octavation 8.
<p>
<a href="49/lily-db5f8e44.ly">
<img align="middle"
border="0" src="49/lily-db5f8e44.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-arrows.ly"></a>
<p><a href="3b/lily-23d579b8.ly"><samp><span class="file">markup-arrows.ly</span></samp>
</a>
<p>The feta font has arrow heads
<p>
<a href="3b/lily-23d579b8.ly">
<img align="middle"
border="0" src="3b/lily-23d579b8.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-bidi-pango.ly"></a>
<p><a href="bb/lily-0451ac4b.ly"><samp><span class="file">markup-bidi-pango.ly</span></samp>
</a>
<p>A single pango string is considered to have one
direction. The hebrew in this example (including punctuation) is set
right-to-left, with the first word (containing 1) on the right.
<p>
<a href="bb/lily-0451ac4b.ly">
<img align="middle"
border="0" src="bb/lily-0451ac4b.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-column-align.ly"></a>
<p><a href="c6/lily-99fe9726.ly"><samp><span class="file">markup-column-align.ly</span></samp>
</a>
<p>Fixed horizontal alignment of columns of text can be set using
\left-column, \center-column and \right-column.
<p class="noindent"><p>
<a href="c6/lily-99fe9726.ly">
<img align="middle"
border="0" src="c6/lily-99fe9726.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-commands.ly"></a>
<p><a href="b4/lily-729dec5f.ly"><samp><span class="file">markup-commands.ly</span></samp>
</a>
<p>test various markup commands.
<p>
<a href="b4/lily-729dec5f.ly">
<img align="middle"
border="0" src="b4/lily-729dec5f.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-eps.ly"></a>
<p><a href="9c/lily-9b7af774.ly"><samp><span class="file">markup-eps.ly</span></samp>
</a>
<p>The epsfile markup command reads an EPS file
<p>
<a href="9c/lily-9b7af774.ly">
<img align="middle"
border="0" src="9c/lily-9b7af774.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-line-thickness.ly"></a>
<p><a href="59/lily-b41c5592.ly"><samp><span class="file">markup-line-thickness.ly</span></samp>
</a>
<p>The thickness setting between markup lines and other
lines is consistent.
<p>
<a href="59/lily-b41c5592.ly">
<img align="middle"
border="0" src="59/lily-b41c5592.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-lines.ly"></a>
<p><a href="f3/lily-b0a19f47.ly"><samp><span class="file">markup-lines.ly</span></samp>
</a>
<p>Text that can spread over pages is entered with the
<code>\markuplines</code> command.
<p>
<a href="f3/lily-b0a19f47.ly">
<img align="middle"
border="0" src="f3/lily-b0a19f47.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-music-glyph.ly"></a>
<p><a href="09/lily-6da92323.ly"><samp><span class="file">markup-music-glyph.ly</span></samp>
</a>
<p>Reset fontname for musicglyph. For unknown glyphs, we print a warning.
<p>
<a href="09/lily-6da92323.ly">
<img align="middle"
border="0" src="09/lily-6da92323.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-note-dot.ly"></a>
<p><a href="91/lily-d65d81a1.ly"><samp><span class="file">markup-note-dot.ly</span></samp>
</a>
<p>A dotted whole note displayed via the <code>\note</code>
command must separate the note head and the dot. The dot avoids the upflag.
<p>
<a href="91/lily-d65d81a1.ly">
<img align="middle"
border="0" src="91/lily-d65d81a1.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-note.ly"></a>
<p><a href="c9/lily-1031245f.ly"><samp><span class="file">markup-note.ly</span></samp>
</a>
<p>The note markup function may be used to make metronome
markings. It works for a variety of flag, dot and duration settings.
<p>
<a href="c9/lily-1031245f.ly">
<img align="middle"
border="0" src="c9/lily-1031245f.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-scheme.ly"></a>
<p><a href="a2/lily-33de60f3.ly"><samp><span class="file">markup-scheme.ly</span></samp>
</a>
<p>There is a Scheme macro <code>markup</code> to produce markup
texts using a similar syntax as <code>\markup</code>.
<p class="noindent"><p>
<a href="a2/lily-33de60f3.ly">
<img align="middle"
border="0" src="a2/lily-33de60f3.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-score.ly"></a>
<p><a href="2a/lily-50ad65f6.ly"><samp><span class="file">markup-score.ly</span></samp>
</a>
<p>Use \score block as markup command.
<p>
<a href="2a/lily-50ad65f6.ly">
<img align="middle"
border="0" src="2a/lily-50ad65f6.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-stack.ly"></a>
<p><a href="21/lily-eac1fd9a.ly"><samp><span class="file">markup-stack.ly</span></samp>
</a>
<p>Markup scripts may be stacked.
<p>
<a href="21/lily-eac1fd9a.ly">
<img align="middle"
border="0" src="21/lily-eac1fd9a.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-syntax.ly"></a>
<p><a href="ea/lily-c4bc3c78.ly"><samp><span class="file">markup-syntax.ly</span></samp>
</a>
<p>Demo of markup texts, using LilyPond syntax.
<p>
<a href="ea/lily-c4bc3c78.ly">
<img align="middle"
border="0" src="ea/lily-c4bc3c78.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-user.ly"></a>
<p><a href="e5/lily-531dec27.ly"><samp><span class="file">markup-user.ly</span></samp>
</a>
<p>Users may define non-standard markup commands using
the <code>define-markup-command</code> scheme macro.
<p>
<a href="e5/lily-531dec27.ly">
<img align="middle"
border="0" src="e5/lily-531dec27.png" alt="[image of music]">
</a>
</p>
<p><a name="markup-word-wrap.ly"></a>
<p><a href="17/lily-96bffde7.ly"><samp><span class="file">markup-word-wrap.ly</span></samp>
</a>
<p>The markup commands <code>\wordwrap</code> and <code>\justify</code>
produce simple paragraph text.
<p>
<a href="17/lily-96bffde7.ly">
<img align="middle"
border="0" src="17/lily-96bffde7.png" alt="[image of music]">
</a>
</p>
<p><a name="measure-grouping.ly"></a>
<p><a href="6d/lily-e95bb12f.ly"><samp><span class="file">measure-grouping.ly</span></samp>
</a>
<p>The <code>Measure_grouping_engraver</code> adds triangles and
brackets above beats when the beats of a time signature are grouped.
<p>
<a href="6d/lily-e95bb12f.ly">
<img align="middle"
border="0" src="6d/lily-e95bb12f.png" alt="[image of music]">
</a>
</p>
<p><a name="mensural-ligatures.ly"></a>
<p><a href="3b/lily-7cac6433.ly"><samp><span class="file">mensural-ligatures.ly</span></samp>
</a>
<p>Mensural ligatures show different shapes, depending on the
rhythmical pattern and direction of the melody line.
<p>
<a href="3b/lily-7cac6433.ly">
<img align="middle"
border="0" src="3b/lily-7cac6433.png" alt="[image of music]">
</a>
</p>
<p><a name="mensural.ly"></a>
<p><a href="3c/lily-e2945cda.ly"><samp><span class="file">mensural.ly</span></samp>
</a>
<p>There is limited support for mensural notation: note head
shapes are available. Mensural stems are centered on the note heads,
both for up and down stems.
<p>
<a href="3c/lily-e2945cda.ly">
<img align="middle"
border="0" src="3c/lily-e2945cda.png" alt="[image of music]">
</a>
</p>
<p><a name="metronome-marking.ly"></a>
<p><a href="99/lily-2c29d100.ly"><samp><span class="file">metronome-marking.ly</span></samp>
</a>
<p>Here <code>\tempo</code> directives are printed as metronome markings.
<p>The marking is left aligned with the time signature, if there is one.
<p class="noindent"><p>
<a href="99/lily-2c29d100.ly">
<img align="middle"
border="0" src="99/lily-2c29d100.png" alt="[image of music]">
</a>
</p>
<p><a name="metronome-parenthesized.ly"></a>
<p><a href="fe/lily-c7ead3ce.ly"><samp><span class="file">metronome-parenthesized.ly</span></samp>
</a>
<p>Using an empty text in the metronome marks, one can generate parenthesized tempo marks.
<p class="noindent"><p>
<a href="fe/lily-c7ead3ce.ly">
<img align="middle"
border="0" src="fe/lily-c7ead3ce.png" alt="[image of music]">
</a>
</p>
<p><a name="metronome-text.ly"></a>
<p><a href="4c/lily-d2ea6c27.ly"><samp><span class="file">metronome-text.ly</span></samp>
</a>
<p>The tempo command supports text markup and/or duration=count. Using the
Score.hideTempoNote, one can hide the duration=count in the tempo mark.
<p class="noindent"><p>
<a href="4c/lily-d2ea6c27.ly">
<img align="middle"
border="0" src="4c/lily-d2ea6c27.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-drums.ly"></a>
<p><a href="f4/lily-2fd09f72.ly"><samp><span class="file">midi-drums.ly</span></samp>
</a>
<p>Midi can create drums.
<p>
<a href="f4/lily-2fd09f72.ly">
<img align="middle"
border="0" src="f4/lily-2fd09f72.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-dynamics.ly"></a>
<p><a href="a1/lily-ab015401.ly"><samp><span class="file">midi-dynamics.ly</span></samp>
</a>
<p>Midi also handles crescendo and decrescendo, either
starting and ending from specified or unspecified sound level.
<p>
<a href="a1/lily-ab015401.ly">
<img align="middle"
border="0" src="a1/lily-ab015401.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-grace.ly"></a>
<p><a href="77/lily-e308a253.ly"><samp><span class="file">midi-grace.ly</span></samp>
</a>
<p>Grace notes don't intrroduce syncing problems: the last note
off will appear at tick 768 (2 * 384).
<p>
<a href="77/lily-e308a253.ly">
<img align="middle"
border="0" src="77/lily-e308a253.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-lyric-barcheck.ly"></a>
<p><a href="8f/lily-3c040267.ly"><samp><span class="file">midi-lyric-barcheck.ly</span></samp>
</a>
<p>Lyrics in MIDI are aligned to ties and beams:
this examples causes no bar checks in MIDI.
<p class="noindent"><p>
<a href="8f/lily-3c040267.ly">
<img align="middle"
border="0" src="8f/lily-3c040267.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-microtone-off.ly"></a>
<p><a href="b9/lily-6d674c58.ly"><samp><span class="file">midi-microtone-off.ly</span></samp>
</a>
<p>Microtonal shifts should be corrected before the start of
the next (possibly grace) note.
<p>
<a href="b9/lily-6d674c58.ly">
<img align="middle"
border="0" src="b9/lily-6d674c58.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-microtone.ly"></a>
<p><a href="2f/lily-8e03ec27.ly"><samp><span class="file">midi-microtone.ly</span></samp>
</a>
<p>The pitch wheel is used for microtones.
<p>
<a href="2f/lily-8e03ec27.ly">
<img align="middle"
border="0" src="2f/lily-8e03ec27.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-partial.ly"></a>
<p><a href="f3/lily-3ab2534a.ly"><samp><span class="file">midi-partial.ly</span></samp>
</a>
<p>MIDI and partial measures work together.
<p>
<a href="f3/lily-3ab2534a.ly">
<img align="middle"
border="0" src="f3/lily-3ab2534a.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-pedal.ly"></a>
<p><a href="f2/lily-2bf08a0d.ly"><samp><span class="file">midi-pedal.ly</span></samp>
</a>
<p>Pedals. Run <code>timidity -idvvv file.midi |grep Midi</code>
to see midi events.
<p>
<a href="f2/lily-2bf08a0d.ly">
<img align="middle"
border="0" src="f2/lily-2bf08a0d.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-scales.ly"></a>
<p><a href="3f/lily-b226f9bd.ly"><samp><span class="file">midi-scales.ly</span></samp>
</a>
<p>Converting LilyPond input to MIDI and then again back with
<code>midi2ly.py</code> is a reversible procedure in some simple cases,
which mean that the original <code>.ly</code> -file and the one converted
back from the generated <code>.midi</code> -file do not differ.
Here are produced some scales.
<p class="noindent"><p>
<a href="3f/lily-b226f9bd.ly">
<img align="middle"
border="0" src="3f/lily-b226f9bd.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-transposition.ly"></a>
<p><a href="ea/lily-c6f8ddf1.ly"><samp><span class="file">midi-transposition.ly</span></samp>
</a>
<p>should deliver f' in MIDI
<p>
<a href="ea/lily-c6f8ddf1.ly">
<img align="middle"
border="0" src="ea/lily-c6f8ddf1.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-tuplets.ly"></a>
<p><a href="79/lily-e67b9b06.ly"><samp><span class="file">midi-tuplets.ly</span></samp>
</a>
<p>Midi2ly tuplet test.
<pre class="example"> python scripts/midi2ly.py --duration-quant=32 \
--allow-tuplet=4*2/3 \
--allow-tuplet=8*2/3 \
--allow-tuplet=4*3/5 \
--allow-tuplet=8*3/5 \
tu.midi
</pre>
<p class="noindent"><p>
<a href="79/lily-e67b9b06.ly">
<img align="middle"
border="0" src="79/lily-e67b9b06.png" alt="[image of music]">
</a>
</p>
<p><a name="midi-volume-equaliser.ly"></a>
<p><a href="e0/lily-99429df1.ly"><samp><span class="file">midi-volume-equaliser.ly</span></samp>
</a>
<p><a name="index-Midi-Volume-Equaliser-11"></a>The full orchestra plays a note, where groups stop one after
another. Use this to tune equalizer settings.
<p>
<a href="e0/lily-99429df1.ly">
<img align="middle"
border="0" src="e0/lily-99429df1.png" alt="[image of music]">
</a>
</p>
<p><a name="mm-rests2.ly"></a>
<p><a href="3f/lily-999edc6d.ly"><samp><span class="file">mm-rests2.ly</span></samp>
</a>
<p>If <code>Score.skipBars</code> is set,
the signs for four, two, and one measure rest are combined to
produce the graphical representation of rests for up to 10 bars.
The number of bars will be written above the sign.
<p class="noindent"><p>
<a href="3f/lily-999edc6d.ly">
<img align="middle"
border="0" src="3f/lily-999edc6d.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest-center.ly"></a>
<p><a href="01/lily-b632d1a7.ly"><samp><span class="file">multi-measure-rest-center.ly</span></samp>
</a>
<p>The multimeasure rest is centered exactly between bar lines.
<p>
<a href="01/lily-b632d1a7.ly">
<img align="middle"
border="0" src="01/lily-b632d1a7.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest-center2.ly"></a>
<p><a href="07/lily-fa1718b7.ly"><samp><span class="file">multi-measure-rest-center2.ly</span></samp>
</a>
<p>The existence of a text mark does not affect the placement of a multimeasure rest.
<p>
<a href="07/lily-fa1718b7.ly">
<img align="middle"
border="0" src="07/lily-fa1718b7.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest-grace.ly"></a>
<p><a href="44/lily-bb7a34e5.ly"><samp><span class="file">multi-measure-rest-grace.ly</span></samp>
</a>
<p>Multi-measure rests are centered also in the case of grace notes.
<p>
<a href="44/lily-bb7a34e5.ly">
<img align="middle"
border="0" src="44/lily-bb7a34e5.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest-instr-name.ly"></a>
<p><a href="8f/lily-cedf5897.ly"><samp><span class="file">multi-measure-rest-instr-name.ly</span></samp>
</a>
<p>There are both long and short instrument names.
Engraving instrument names should not be confused by the
multimeasure rests.
<p>
<a href="8f/lily-cedf5897.ly">
<img align="middle"
border="0" src="8f/lily-cedf5897.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest-multi-staff-center.ly"></a>
<p><a href="7f/lily-f2fc1bfa.ly"><samp><span class="file">multi-measure-rest-multi-staff-center.ly</span></samp>
</a>
<p>The centering of multi-measure rests is
independent on prefatory matter in other staves.
<p>
<a href="7f/lily-f2fc1bfa.ly">
<img align="middle"
border="0" src="7f/lily-f2fc1bfa.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest-spacing.ly"></a>
<p><a href="62/lily-32b8361a.ly"><samp><span class="file">multi-measure-rest-spacing.ly</span></samp>
</a>
<p>By setting texts starting with a multi-measure rest, an
extra spacing column is created. This should not cause problems.
<p>
<a href="62/lily-32b8361a.ly">
<img align="middle"
border="0" src="62/lily-32b8361a.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest-text.ly"></a>
<p><a href="41/lily-f8a1f48a.ly"><samp><span class="file">multi-measure-rest-text.ly</span></samp>
</a>
<p>Texts may be added to the multi-measure rests.
<p>By setting the appropriate <code>spacing-procedure</code>, we can make
measures stretch to accomodate wide texts.
<p class="noindent"><p>
<a href="41/lily-f8a1f48a.ly">
<img align="middle"
border="0" src="41/lily-f8a1f48a.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest-usebreve.ly"></a>
<p><a href="9b/lily-1770a96c.ly"><samp><span class="file">multi-measure-rest-usebreve.ly</span></samp>
</a>
<p>For longer measure lengths, the breve rest is used.
<p>
<a href="9b/lily-1770a96c.ly">
<img align="middle"
border="0" src="9b/lily-1770a96c.png" alt="[image of music]">
</a>
</p>
<p><a name="multi-measure-rest.ly"></a>
<p><a href="ea/lily-262eafe7.ly"><samp><span class="file">multi-measure-rest.ly</span></samp>
</a>
<p>Multi-measure rests do not collide with barlines and clefs. They
are not expanded when you set <code>Score.skipBars</code>. Although the
multi-measure-rest is a Spanner, minimum distances are set to keep it
colliding from barlines.
<p>Rests over measures during longer than 2 wholes use breve rests. When
more than 10 or more measures (tunable through <code>expand-limit</code>)
are used then a different symbol is used.
<p class="noindent"><p>
<a href="ea/lily-262eafe7.ly">
<img align="middle"
border="0" src="ea/lily-262eafe7.png" alt="[image of music]">
</a>
</p>
<p><a name="music-function-end-spanners.ly"></a>
<p><a href="af/lily-dd8c0314.ly"><samp><span class="file">music-function-end-spanners.ly</span></samp>
</a>
<p>the <code>endSpanners</code> music function inserts
end span events at the end of a note.
<p>
<a href="af/lily-dd8c0314.ly">
<img align="middle"
border="0" src="af/lily-dd8c0314.png" alt="[image of music]">
</a>
</p>
<p><a name="music-function.ly"></a>
<p><a href="a5/lily-36ac9457.ly"><samp><span class="file">music-function.ly</span></samp>
</a>
<p>Music functions are generic music transformation functions,
which can be used to extend music syntax seamlessly. Here we
demonstrate a <code>\myBar</code> function, which works similar to
<code>\bar</code>, but is implemented completely in Scheme.
<p>
<a href="a5/lily-36ac9457.ly">
<img align="middle"
border="0" src="a5/lily-36ac9457.png" alt="[image of music]">
</a>
</p>
<p><a name="music-map.ly"></a>
<p><a href="a0/lily-ad212a44.ly"><samp><span class="file">music-map.ly</span></samp>
</a>
<p>With <code>music-map</code>, you can apply functions operating on a
single piece of music to an entire music expression. In this example,
the the function <code>notes-to-skip</code> changes a note to a skip. When
applied to an entire music expression in the 1st measure, the scripts
and dynamics are left over. These are put onto the 2nd measure.
<p>
<a href="a0/lily-ad212a44.ly">
<img align="middle"
border="0" src="a0/lily-ad212a44.png" alt="[image of music]">
</a>
</p>
<p><a name="newaddlyrics.ly"></a>
<p><a href="62/lily-db765dfd.ly"><samp><span class="file">newaddlyrics.ly</span></samp>
</a>
<p>newlyrics, multiple stanzas, multiple lyric voices.
<p>
<a href="62/lily-db765dfd.ly">
<img align="middle"
border="0" src="62/lily-db765dfd.png" alt="[image of music]">
</a>
</p>
<p><a name="no-staff.ly"></a>
<p><a href="2e/lily-a0b2592f.ly"><samp><span class="file">no-staff.ly</span></samp>
</a>
<p><a name="index-Staff-Remove-12"></a>The printing of the staff lines may be suppressed by removing the
corresponding engraver.
<p class="noindent"><p>
<a href="2e/lily-a0b2592f.ly">
<img align="middle"
border="0" src="2e/lily-a0b2592f.png" alt="[image of music]">
</a>
</p>
<p><a name="non-centered-bar-lines.ly"></a>
<p><a href="a5/lily-34e9a240.ly"><samp><span class="file">non-centered-bar-lines.ly</span></samp>
</a>
<p>Bar lines are positioned correctly when using custom
staves which are not centered around position 0.
<p class="noindent"><p>
<a href="a5/lily-34e9a240.ly">
<img align="middle"
border="0" src="a5/lily-34e9a240.png" alt="[image of music]">
</a>
</p>
<p><a name="non-empty-text.ly"></a>
<p><a href="69/lily-fb9b743a.ly"><samp><span class="file">non-empty-text.ly</span></samp>
</a>
<p>By default, text is set with empty horizontal dimensions.
The boolean property <code>no-spacing-rods</code> in <code>TextScript</code> is used
to control the horizontal size of text.
<p>
<a href="69/lily-fb9b743a.ly">
<img align="middle"
border="0" src="69/lily-fb9b743a.png" alt="[image of music]">
</a>
</p>
<p><a name="note-head-chord.ly"></a>
<p><a href="32/lily-badb23dc.ly"><samp><span class="file">note-head-chord.ly</span></samp>
</a>
<p>Note heads are flipped on the stem to prevent collisions.
It also works for whole heads that have invisible stems.
<p class="noindent"><p>
<a href="32/lily-badb23dc.ly">
<img align="middle"
border="0" src="32/lily-badb23dc.png" alt="[image of music]">
</a>
</p>
<p><a name="note-head-harmonic-whole.ly"></a>
<p><a href="a7/lily-753b6340.ly"><samp><span class="file">note-head-harmonic-whole.ly</span></samp>
</a>
<p>A harmonic note head must be centered if the base note
is a whole note.
<p>
<a href="a7/lily-753b6340.ly">
<img align="middle"
border="0" src="a7/lily-753b6340.png" alt="[image of music]">
</a>
</p>
<p><a name="note-head-harmonic.ly"></a>
<p><a href="f4/lily-e330d62e.ly"><samp><span class="file">note-head-harmonic.ly</span></samp>
</a>
<p>The handling of stems for harmonic notes must be
completely identical to normal note heads.
<p>Harmonic heads do not get dots. If <code>harmonicAccidentals</code> is
unset, they also don't get accidentals.
<p>
<a href="f4/lily-e330d62e.ly">
<img align="middle"
border="0" src="f4/lily-e330d62e.png" alt="[image of music]">
</a>
</p>
<p><a name="note-head-solfa.ly"></a>
<p><a href="90/lily-9e3f672e.ly"><samp><span class="file">note-head-solfa.ly</span></samp>
</a>
<p>With <code>shapeNoteStyles</code>, the style of the note head
is adjusted according to the step of the scale, as measured relative
to the <code>tonic</code> property.
<p>
<a href="90/lily-9e3f672e.ly">
<img align="middle"
border="0" src="90/lily-9e3f672e.png" alt="[image of music]">
</a>
</p>
<p><a name="note-head-style.ly"></a>
<p><a href="54/lily-ebb1426b.ly"><samp><span class="file">note-head-style.ly</span></samp>
</a>
<p>Note head shapes may be set from several choices.
The stem endings should be adjusted according to the note head.
If you want different note head styles on one stem,
you must create a special context.
<p>Harmonic notes have a different shape and different
dimensions.
<p class="noindent"><p>
<a href="54/lily-ebb1426b.ly">
<img align="middle"
border="0" src="54/lily-ebb1426b.png" alt="[image of music]">
</a>
</p>
<p><a name="note-line.ly"></a>
<p><a href="8e/lily-5e40a2f7.ly"><samp><span class="file">note-line.ly</span></samp>
</a>
<p>Note head lines (e.g. glissando)
run between centers of the note heads.
<p>
<a href="8e/lily-5e40a2f7.ly">
<img align="middle"
border="0" src="8e/lily-5e40a2f7.png" alt="[image of music]">
</a>
</p>
<p><a name="number-staff-lines.ly"></a>
<p><a href="1b/lily-21ba700e.ly"><samp><span class="file">number-staff-lines.ly</span></samp>
</a>
<p>The number of stafflines of a staff can be set. Ledger
lines both on note heads and rests, as well as barlines, are
adjusted accordingly.
<p>
<a href="1b/lily-21ba700e.ly">
<img align="middle"
border="0" src="1b/lily-21ba700e.png" alt="[image of music]">
</a>
</p>
<p><a name="optimal-page-breaking-hstretch.ly"></a>
<p><a href="46/lily-6bfad76d.ly"><samp><span class="file">optimal-page-breaking-hstretch.ly</span></samp>
</a>
<p>The optimal page breaker will stretch the
systems horizontally so that the vertical spacing will be
more acceptable. The page-spacing-weight parameter
controls the relative importance of vertical/horizontal
spacing. Because ragged-last-bottom is on, only the
first page should be horizontally stretched.
<p class="noindent"><p>
<a href="46/lily-6bfad76d.ly">
<img align="middle"
border="0" src="46/lily-6bfad76d.png" alt="[image of music]">
</a>
</p>
<p><a name="option-help.ly"></a>
<p><a href="71/lily-05f362b1.ly"><samp><span class="file">option-help.ly</span></samp>
</a>
<p>Print the option help text, for comparison against
previous releases.
<p>
<a href="71/lily-05f362b1.ly">
<img align="middle"
border="0" src="71/lily-05f362b1.png" alt="[image of music]">
</a>
</p>
<p><a name="ottava-broken.ly"></a>
<p><a href="54/lily-1cbb0fc3.ly"><samp><span class="file">ottava-broken.ly</span></samp>
</a>
<p>At line breaks, ottava brackets have no vertical line and
their horizontal line does not stick out. The dashed line runs until
the end of the line (regardless of prefatory matter).
<p class="noindent"><p>
<a href="54/lily-1cbb0fc3.ly">
<img align="middle"
border="0" src="54/lily-1cbb0fc3.png" alt="[image of music]">
</a>
</p>
<p><a name="ottava-edge.ly"></a>
<p><a href="69/lily-6b4155e0.ly"><samp><span class="file">ottava-edge.ly</span></samp>
</a>
<p>Both edge heights of an ottava bracket can be specified.
<p>
<a href="69/lily-6b4155e0.ly">
<img align="middle"
border="0" src="69/lily-6b4155e0.png" alt="[image of music]">
</a>
</p>
<p><a name="ottava.ly"></a>
<p><a href="c5/lily-951137e9.ly"><samp><span class="file">ottava.ly</span></samp>
</a>
<p>Ottava brackets are supported, through the
use of the music function <code>\ottava</code>.
<p>The spanner should go below a staff for 8va bassa, and the ottavation
markup can be tuned with <code>Staff.ottavation</code>.
<p class="noindent"><p>
<a href="c5/lily-951137e9.ly">
<img align="middle"
border="0" src="c5/lily-951137e9.png" alt="[image of music]">
</a>
</p>
<p><a name="override-nest.ly"></a>
<p><a href="d6/lily-55a536e6.ly"><samp><span class="file">override-nest.ly</span></samp>
</a>
<p>Sublist of grob property lists may be also tuned. In the
next example, the <code>beamed-lengths</code> property of the <code>Stem</code>
grob is tweaked.
<p>
<a href="d6/lily-55a536e6.ly">
<img align="middle"
border="0" src="d6/lily-55a536e6.png" alt="[image of music]">
</a>
</p>
<p><a name="page-break-between-scores.ly"></a>
<p><a href="b8/lily-edeabdd3.ly"><samp><span class="file">page-break-between-scores.ly</span></samp>
</a>
<p>Page breaks work when they are placed at the end of a score,
or between scores.
<p>
<a href="b8/lily-edeabdd3.ly">
<img align="middle"
border="0" src="b8/lily-edeabdd3.png" alt="[image of music]">
</a>
</p>
<p><a name="page-break-turn-toplevel.ly"></a>
<p><a href="b4/lily-88f2f58e.ly"><samp><span class="file">page-break-turn-toplevel.ly</span></samp>
</a>
<p>Page breaking and page turning commands (<code>\pageBreak</code>,
<code>\noPageBreak</code>, etc), can be used at top level.
<p>
<a href="b4/lily-88f2f58e.ly">
<img align="middle"
border="0" src="b4/lily-88f2f58e.png" alt="[image of music]">
</a>
</p>
<p><a name="page-break-warn-forbidden.ly"></a>
<p><a href="77/lily-f336e220.ly"><samp><span class="file">page-break-warn-forbidden.ly</span></samp>
</a>
<p>If a page break is forced where it is forbidden,
a warning is printed.
<p>
<a href="77/lily-f336e220.ly">
<img align="middle"
border="0" src="77/lily-f336e220.png" alt="[image of music]">
</a>
</p>
<p><a name="page-breaking-page-count1.ly"></a>
<p><a href="62/lily-6f29d04d.ly"><samp><span class="file">page-breaking-page-count1.ly</span></samp>
</a>
<p>The number of pages in a score can be forced by setting
<code>page-count</code> in the (book-level) paper block.
<p>
<a href="62/lily-6f29d04d.ly">
<img align="middle"
border="0" src="62/lily-6f29d04d.png" alt="[image of music]">
</a>
</p>
<p><a name="page-breaking-page-count2.ly"></a>
<p><a href="5c/lily-6751103f.ly"><samp><span class="file">page-breaking-page-count2.ly</span></samp>
</a>
<p>The number of pages in a score can be forced by setting
<code>page-count</code> in the (book-level) paper block. If there are too
few systems for the number of pages, we append blank pages.
<p>
<a href="5c/lily-6751103f.ly">
<img align="middle"
border="0" src="5c/lily-6751103f.png" alt="[image of music]">
</a>
</p>
<p><a name="page-breaking-page-count3.ly"></a>
<p><a href="10/lily-fa5ab697.ly"><samp><span class="file">page-breaking-page-count3.ly</span></samp>
</a>
<p>The number of pages in a score can be forced by setting
<code>page-count</code> in the (book-level) paper block. Even if there are
too many systems for that number of pages, we will squeeze them in.
<p>
<a href="10/lily-fa5ab697.ly">
<img align="middle"
border="0" src="10/lily-fa5ab697.png" alt="[image of music]">
</a>
</p>
<p><a name="page-breaks.ly"></a>
<p><a href="61/lily-2788b461.ly"><samp><span class="file">page-breaks.ly</span></samp>
</a>
<p>Stress optimal page breaking. This should look
nice and even on 4 a6 pages.
<p>
<a href="61/lily-2788b461.ly">
<img align="middle"
border="0" src="61/lily-2788b461.png" alt="[image of music]">
</a>
</p>
<p><a name="page-label.ly"></a>
<p><a href="0f/lily-18785a58.ly"><samp><span class="file">page-label.ly</span></samp>
</a>
<p>Page labels may be placed inside music or at top-level,
and refered to in markups.
<p>
<a href="0f/lily-18785a58.ly">
<img align="middle"
border="0" src="0f/lily-18785a58.png" alt="[image of music]">
</a>
</p>
<p><a name="page-layout-manual-position.ly"></a>
<p><a href="f3/lily-88341a73.ly"><samp><span class="file">page-layout-manual-position.ly</span></samp>
</a>
<p>By setting <code>Y-offset</code> and <code>X-offset</code> for the
<code>line-break-system-details</code> of <code>NonMusicalPaperColumn</code>,
systems may be placed absolutely on the printable area of the page.
<p>
<a href="f3/lily-88341a73.ly">
<img align="middle"
border="0" src="f3/lily-88341a73.png" alt="[image of music]">
</a>
</p>
<p><a name="page-layout-twopass.ly"></a>
<p><a href="cf/lily-f4372e4a.ly"><samp><span class="file">page-layout-twopass.ly</span></samp>
</a>
<p>Page breaking details can be stored for later reference.
<p>
<a href="cf/lily-f4372e4a.ly">
<img align="middle"
border="0" src="cf/lily-f4372e4a.png" alt="[image of music]">
</a>
</p>
<p><a name="page-layout.ly"></a>
<p><a href="2d/lily-3d03ae4b.ly"><samp><span class="file">page-layout.ly</span></samp>
</a>
<p>This shows how different settings on \paper modify the
general page layout. Basically \paper will set the values for the
whole paper while \layout for each \score block.
<p>This file is best viewed outside the collated files document.
<p class="noindent"><p>
<a href="2d/lily-3d03ae4b.ly">
<img align="middle"
border="0" src="2d/lily-3d03ae4b.png" alt="[image of music]">
</a>
</p>
<p><a name="page-limited-space.ly"></a>
<p><a href="ea/lily-456e4dc3.ly"><samp><span class="file">page-limited-space.ly</span></samp>
</a>
<p>The space between systems can be limited when there is too
much space left on the page by setting <code>page-limit-inter-system-space</code>.
<p>
<a href="ea/lily-456e4dc3.ly">
<img align="middle"
border="0" src="ea/lily-456e4dc3.png" alt="[image of music]">
</a>
</p>
<p><a name="page-minimal-page-breaking-last-page.ly"></a>
<p><a href="24/lily-a3dcdb9d.ly"><samp><span class="file">page-minimal-page-breaking-last-page.ly</span></samp>
</a>
<p>Minimal page breaker: special case when the last system is moved
to an other page when there is not enough space because of the tagline.
<p>
<a href="24/lily-a3dcdb9d.ly">
<img align="middle"
border="0" src="24/lily-a3dcdb9d.png" alt="[image of music]">
</a>
</p>
<p><a name="page-minimal-page-breaking.ly"></a>
<p><a href="4d/lily-62aa1a11.ly"><samp><span class="file">page-minimal-page-breaking.ly</span></samp>
</a>
<p>The minimal page breaker stacks as many lines on pages,
only accounting for manual page break commands.
<p>
<a href="4d/lily-62aa1a11.ly">
<img align="middle"
border="0" src="4d/lily-62aa1a11.png" alt="[image of music]">
</a>
</p>
<p><a name="page-spacing.ly"></a>
<p><a href="a9/lily-58bba651.ly"><samp><span class="file">page-spacing.ly</span></samp>
</a>
<p>By setting properties in NonMusicalPaperColumn, vertical
spacing of page layout can be adjusted.
<p>For technical reasons, <code>overrideProperty</code> has to be used for
setting properties on individual object. <code>\override</code> may still be
used for global overrides.
<p>By setting <code>annotate-spacing</code>, we can see the effect of each property.
<p class="noindent"><p>
<a href="a9/lily-58bba651.ly">
<img align="middle"
border="0" src="a9/lily-58bba651.png" alt="[image of music]">
</a>
</p>
<p><a name="page-top-space.ly"></a>
<p><a href="4f/lily-fefc648a.ly"><samp><span class="file">page-top-space.ly</span></samp>
</a>
<p>By setting <code>page-top-space,</code> the Y position of the
first system can be forced to be uniform.
<p>
<a href="4f/lily-fefc648a.ly">
<img align="middle"
border="0" src="4f/lily-fefc648a.png" alt="[image of music]">
</a>
</p>
<p><a name="page-turn-page-breaking-auto-first-page.ly"></a>
<p><a href="5f/lily-885a7a20.ly"><samp><span class="file">page-turn-page-breaking-auto-first-page.ly</span></samp>
</a>
<p>By default, we start with page 1, which is on the right hand side
of a double page. In this example, auto-first-page-number is set to ##t and the
music won't fit on a single page, so we should automatically set the first page
number to 2 in order to avoid a bad page turn.
<p>
<a href="5f/lily-885a7a20.ly">
<img align="middle"
border="0" src="5f/lily-885a7a20.png" alt="[image of music]">
</a>
</p>
<p><a name="page-turn-page-breaking-auto-first-page2.ly"></a>
<p><a href="c7/lily-266dc151.ly"><samp><span class="file">page-turn-page-breaking-auto-first-page2.ly</span></samp>
</a>
<p>By default, we start with page 1, which is on the right hand side
of a double page. In this example, auto-first-page-number is set to ##t.
ALthough the music will fit on a single page, it would require stretching the
first page badly, so we should automatically set the first page
number to 2 in order to avoid a bad page turn.
<p>
<a href="c7/lily-266dc151.ly">
<img align="middle"
border="0" src="c7/lily-266dc151.png" alt="[image of music]">
</a>
</p>
<p><a name="page-turn-page-breaking-badturns.ly"></a>
<p><a href="36/lily-5643c8e1.ly"><samp><span class="file">page-turn-page-breaking-badturns.ly</span></samp>
</a>
<p>If there are no good places to have a page turn,
the optimal-breaker will just have to recover gracefully. This
should appear on 3 pages.
<p class="noindent"><p>
<a href="36/lily-5643c8e1.ly">
<img align="middle"
border="0" src="36/lily-5643c8e1.png" alt="[image of music]">
</a>
</p>
<p><a name="page-turn-page-breaking-repeats.ly"></a>
<p><a href="a6/lily-217ce667.ly"><samp><span class="file">page-turn-page-breaking-repeats.ly</span></samp>
</a>
<p>The page-turn engraver will not count potential page
turns if they occur in the middle of a repeat unless there is a
long gap at the beginning or at the end of the repeat.
<p class="noindent"><p>
<a href="a6/lily-217ce667.ly">
<img align="middle"
border="0" src="a6/lily-217ce667.png" alt="[image of music]">
</a>
</p>
<p><a name="page-turn-page-breaking.ly"></a>
<p><a href="03/lily-ea893a30.ly"><samp><span class="file">page-turn-page-breaking.ly</span></samp>
</a>
<p>The page-turn breaker will put a page turn after
a rest unless there is a 'special' barline within the rest,
in which case the turn will go after the special barline.
<p class="noindent"><p>
<a href="03/lily-ea893a30.ly">
<img align="middle"
border="0" src="03/lily-ea893a30.png" alt="[image of music]">
</a>
</p>
<p><a name="parenthesize-singlenotes-chords-rests.ly"></a>
<p><a href="d3/lily-3d53955a.ly"><samp><span class="file">parenthesize-singlenotes-chords-rests.ly</span></samp>
</a>
<p>The parenthesize function should also work on single notes (not inside chords), rests and on whole chords (each note of the chord is parenthesized). Also, parenthesizing articulations, dynamics and text markup is possible. On all other music expressions, parenthesize does not have an effect.
<p>Measure 1: Three parenthesized notes (staccato not parenthesized), one note with staccato in parentheses; Measure 2: Chord and two rests in parentheses (accent and markup not); Measure 3: note (no parentheses) with \p in parentheses, with text in parentheses, and note in parentheses with p not in parentheses, rest (no parentheses); Measure 4: shows that \parenthesize does not apply to other expressions like SequentialMusic
<p>
<a href="d3/lily-3d53955a.ly">
<img align="middle"
border="0" src="d3/lily-3d53955a.png" alt="[image of music]">
</a>
</p>
<p><a name="parenthesize.ly"></a>
<p><a href="2e/lily-813f2fef.ly"><samp><span class="file">parenthesize.ly</span></samp>
</a>
<p>The parenthesize function is a special tweak that
encloses objects in parentheses. The associated grob is
<code>Score.ParenthesesItem</code>.
<p>
<a href="2e/lily-813f2fef.ly">
<img align="middle"
border="0" src="2e/lily-813f2fef.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-a2.ly"></a>
<p><a href="a2/lily-418b739f.ly"><samp><span class="file">part-combine-a2.ly</span></samp>
</a>
<p>The a2 string is printed only on notes (i.e. not on rests),
and only after chords, solo or polyphony.
<p>
<a href="a2/lily-418b739f.ly">
<img align="middle"
border="0" src="a2/lily-418b739f.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-cross.ly"></a>
<p><a href="e0/lily-96fbe22a.ly"><samp><span class="file">part-combine-cross.ly</span></samp>
</a>
<p>The part combiner stays apart for crossing voices.
<p class="noindent"><p>
<a href="e0/lily-96fbe22a.ly">
<img align="middle"
border="0" src="e0/lily-96fbe22a.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-global.ly"></a>
<p><a href="19/lily-4d7b26d0.ly"><samp><span class="file">part-combine-global.ly</span></samp>
</a>
<p>The analysis of the part combiner is non-local:
in the following example, the decision for using separate voices in
the 1st measure is made on the 2nd note, but influences the 1st note.
<p>In the 2nd measure, the pattern without the tie, leads to combined
voices.
<p class="noindent"><p>
<a href="19/lily-4d7b26d0.ly">
<img align="middle"
border="0" src="19/lily-4d7b26d0.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-markup.ly"></a>
<p><a href="6e/lily-f74f3ad6.ly"><samp><span class="file">part-combine-markup.ly</span></samp>
</a>
<p>Part combine texts accept markup.
<p>
<a href="6e/lily-f74f3ad6.ly">
<img align="middle"
border="0" src="6e/lily-f74f3ad6.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-mmrest-after-solo.ly"></a>
<p><a href="23/lily-3ae699ca.ly"><samp><span class="file">part-combine-mmrest-after-solo.ly</span></samp>
</a>
<p>Multimeasure rests are printed after solos, both
for solo1 and for solo2.
<p>
<a href="23/lily-3ae699ca.ly">
<img align="middle"
border="0" src="23/lily-3ae699ca.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-solo-end.ly"></a>
<p><a href="4b/lily-677ba989.ly"><samp><span class="file">part-combine-solo-end.ly</span></samp>
</a>
<p>SOLO is printed even if the solo voice ends before the
other one. Unfortunately, the multi-rest of the 1st voice (which
is 2 bars longer than the 2nd voice) does not get printed.
<p>
<a href="4b/lily-677ba989.ly">
<img align="middle"
border="0" src="4b/lily-677ba989.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-solo-global.ly"></a>
<p><a href="37/lily-54a1b627.ly"><samp><span class="file">part-combine-solo-global.ly</span></samp>
</a>
<p>In this example, solo1
should not be printed over the 1st note, because of the slur
which is present from the one-voice to the two-voice situation.
<p>
<a href="37/lily-54a1b627.ly">
<img align="middle"
border="0" src="37/lily-54a1b627.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-solo.ly"></a>
<p><a href="d5/lily-7a2a9df0.ly"><samp><span class="file">part-combine-solo.ly</span></samp>
</a>
<p>A solo string can only be printed when a note
starts. Hence, in this example, there is no Solo-2 although the
2nd voice has a dotted quarter, while the first voice has a rest.
<p>A Solo indication is only printed once; (shared) rests do not require
reprinting a solo indication.
<p>Solo 1/2 can not be used when a spanner is active, so there is no solo
over any of the tied notes.
<p class="noindent"><p>
<a href="d5/lily-7a2a9df0.ly">
<img align="middle"
border="0" src="d5/lily-7a2a9df0.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-text.ly"></a>
<p><a href="2a/lily-996d5b02.ly"><samp><span class="file">part-combine-text.ly</span></samp>
</a>
<p>The part combiner detects a2, solo1 and solo2, and prints
texts accordingly.
<p class="noindent"><p>
<a href="2a/lily-996d5b02.ly">
<img align="middle"
border="0" src="2a/lily-996d5b02.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-tuplet-end.ly"></a>
<p><a href="93/lily-f8f50fd2.ly"><samp><span class="file">part-combine-tuplet-end.ly</span></samp>
</a>
<p>End tuplets events are sent to the starting context, so
even after a switch, a tuplet ends correctly.
<p>
<a href="93/lily-f8f50fd2.ly">
<img align="middle"
border="0" src="93/lily-f8f50fd2.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine-tuplet-single.ly"></a>
<p><a href="d2/lily-3413725e.ly"><samp><span class="file">part-combine-tuplet-single.ly</span></samp>
</a>
<p>Tuplets in combined parts only print one bracket.
<p>
<a href="d2/lily-3413725e.ly">
<img align="middle"
border="0" src="d2/lily-3413725e.png" alt="[image of music]">
</a>
</p>
<p><a name="part-combine.ly"></a>
<p><a href="3a/lily-994358d2.ly"><samp><span class="file">part-combine.ly</span></samp>
</a>
<p>The new part combiner stays apart from:
<ul>
<li>different durations,
<li>different articulations (taking into account only slur/beam/tie), and
<li>wide pitch ranges.
</ul>
<p class="noindent"><p>
<a href="3a/lily-994358d2.ly">
<img align="middle"
border="0" src="3a/lily-994358d2.png" alt="[image of music]">
</a>
</p>
<p><a name="pedal-bracket.ly"></a>
<p><a href="5a/lily-f453acda.ly"><samp><span class="file">pedal-bracket.ly</span></samp>
</a>
<p>The brackets of a piano pedal should start and end at
the left side of the note. If a note is shared between two brackets,
these ends are flared.
<p>At a line-break, there are no vertical endings.
<p>
<a href="5a/lily-f453acda.ly">
<img align="middle"
border="0" src="5a/lily-f453acda.png" alt="[image of music]">
</a>
</p>
<p><a name="pedal-end.ly"></a>
<p><a href="7b/lily-eb70cfa8.ly"><samp><span class="file">pedal-end.ly</span></samp>
</a>
<p>Unterminated piano pedal brackets run to the end of the piece.
<p>
<a href="7b/lily-eb70cfa8.ly">
<img align="middle"
border="0" src="7b/lily-eb70cfa8.png" alt="[image of music]">
</a>
</p>
<p><a name="pedal-ped.ly"></a>
<p><a href="6b/lily-bfb2e61e.ly"><samp><span class="file">pedal-ped.ly</span></samp>
</a>
<p>The standard piano pedals style comes with Ped symbols.
The pedal string can be also tuned, for example, to a shorter tilde/P variant
at the end of the melody.
<p>
<a href="6b/lily-bfb2e61e.ly">
<img align="middle"
border="0" src="6b/lily-bfb2e61e.png" alt="[image of music]">
</a>
</p>
<p><a name="phrasing-slur-slur-avoid.ly"></a>
<p><a href="d2/lily-fd151ce6.ly"><samp><span class="file">phrasing-slur-slur-avoid.ly</span></samp>
</a>
<p><code>PhrasingSlur</code>s go over normal slurs.
<p>
<a href="d2/lily-fd151ce6.ly">
<img align="middle"
border="0" src="d2/lily-fd151ce6.png" alt="[image of music]">
</a>
</p>
<p><a name="predefined-fretboards.ly"></a>
<p><a href="13/lily-bbe87efd.ly"><samp><span class="file">predefined-fretboards.ly</span></samp>
</a> <p>
<a href="13/lily-bbe87efd.ly">
<img align="middle"
border="0" src="13/lily-bbe87efd.png" alt="[image of music]">
</a>
</p>
<p><a name="prefatory-empty-spacing.ly"></a>
<p><a href="ee/lily-6cae61be.ly"><samp><span class="file">prefatory-empty-spacing.ly</span></samp>
</a>
<p>The A is atop an invisible barline. The barline,
although invisible, is also translated because it is the last one of
the break alignment.
<p>
<a href="ee/lily-6cae61be.ly">
<img align="middle"
border="0" src="ee/lily-6cae61be.png" alt="[image of music]">
</a>
</p>
<p><a name="prefatory-spacing-matter.ly"></a>
<p><a href="c8/lily-105faac9.ly"><samp><span class="file">prefatory-spacing-matter.ly</span></samp>
</a>
<p>Distances between prefatory items (e.g. clef, bar,
etc.) are determined by engraving standards. These distances depend
on which items are combined. Mid-line, the order for clef and
bar-line is different from the start of line.
<p class="noindent"><p>
<a href="c8/lily-105faac9.ly">
<img align="middle"
border="0" src="c8/lily-105faac9.png" alt="[image of music]">
</a>
</p>
<p><a name="profile-property-access.ly"></a>
<p><a href="0f/lily-2c957d20.ly"><samp><span class="file">profile-property-access.ly</span></samp>
</a>
<p>heavily mutilated Edition Peters Morgenlied by Schubert
<p>
<a href="0f/lily-2c957d20.ly">
<img align="middle"
border="0" src="0f/lily-2c957d20.png" alt="[image of music]">
</a>
</p>
<p><a name="property-grace-polyphony.ly"></a>
<p><a href="56/lily-cfade3c6.ly"><samp><span class="file">property-grace-polyphony.ly</span></samp>
</a>
<p>Property overrides and reverts from <code>\grace</code> do
not interfere with the overrides and reverts from polyphony.
<p>
<a href="56/lily-cfade3c6.ly">
<img align="middle"
border="0" src="56/lily-cfade3c6.png" alt="[image of music]">
</a>
</p>
<p><a name="property-nested-revert.ly"></a>
<p><a href="13/lily-c536bf33.ly"><samp><span class="file">property-nested-revert.ly</span></samp>
</a>
<p>nested properties may also be reverted. This uses
Scheme list syntax.
<p>
<a href="13/lily-c536bf33.ly">
<img align="middle"
border="0" src="13/lily-c536bf33.png" alt="[image of music]">
</a>
</p>
<p><a name="property-once.ly"></a>
<p><a href="92/lily-0e5b9fb2.ly"><samp><span class="file">property-once.ly</span></samp>
</a>
<p>Once properties take effect during a single time step only.
<p>
<a href="92/lily-0e5b9fb2.ly">
<img align="middle"
border="0" src="92/lily-0e5b9fb2.png" alt="[image of music]">
</a>
</p>
<p><a name="quote-cue-during.ly"></a>
<p><a href="ff/lily-0df5afb4.ly"><samp><span class="file">quote-cue-during.ly</span></samp>
</a>
<p>The <code>cueDuring</code> form of quotation will set stem
directions on both quoted and main voice, and deliver the quoted voice
in the <code>cue</code> <code>Voice</code>. The music function <code>\killCues</code>
can remove all cue notes.
<p>Spanners run to the end of a cue section, and are not started on the
last note.
<p>
<a href="ff/lily-0df5afb4.ly">
<img align="middle"
border="0" src="ff/lily-0df5afb4.png" alt="[image of music]">
</a>
</p>
<p><a name="quote-cyclic.ly"></a>
<p><a href="bd/lily-f2191a62.ly"><samp><span class="file">quote-cyclic.ly</span></samp>
</a>
<p>Two quoted voices may refer to each other. In this
example, there are notes with each full-bar rest.
<p>
<a href="bd/lily-f2191a62.ly">
<img align="middle"
border="0" src="bd/lily-f2191a62.png" alt="[image of music]">
</a>
</p>
<p><a name="quote-during.ly"></a>
<p><a href="5f/lily-c3826a5e.ly"><samp><span class="file">quote-during.ly</span></samp>
</a>
<p>With <code>\cueDuring</code> and <code>\quoteDuring</code>,
fragments of previously entered music may be
quoted. <code>quotedEventTypes</code> will determines what things are
quoted. In this example, a 16th rest is not quoted, since
<code>rest-event</code> is not in <code>quotedEventTypes</code>.
<p>
<a href="5f/lily-c3826a5e.ly">
<img align="middle"
border="0" src="5f/lily-c3826a5e.png" alt="[image of music]">
</a>
</p>
<p><a name="quote-grace.ly"></a>
<p><a href="e7/lily-dd7b8198.ly"><samp><span class="file">quote-grace.ly</span></samp>
</a>
<p>Quotes may contain grace notes. The grace note leading up
to an unquoted note is not quoted.
<p>
<a href="e7/lily-dd7b8198.ly">
<img align="middle"
border="0" src="e7/lily-dd7b8198.png" alt="[image of music]">
</a>
</p>
<p><a name="quote-tie.ly"></a>
<p><a href="11/lily-62c30e20.ly"><samp><span class="file">quote-tie.ly</span></samp>
</a>
<p>Voices from different cues must not be tied together. In
this example, the first note has a tie. This note should not be tied
to the 2nd note.
<p>
<a href="11/lily-62c30e20.ly">
<img align="middle"
border="0" src="11/lily-62c30e20.png" alt="[image of music]">
</a>
</p>
<p><a name="quote-transposition.ly"></a>
<p><a href="b8/lily-b070b893.ly"><samp><span class="file">quote-transposition.ly</span></samp>
</a>
<p>Quotations take into account the transposition of both
source and target. In this example, all instruments play sounding
central C, the target is a instrument in F. The target part may be
<code>\transpose</code>d. In this case, all the pitches (including the
quoted ones) will transposed as well.
<p>
<a href="b8/lily-b070b893.ly">
<img align="middle"
border="0" src="b8/lily-b070b893.png" alt="[image of music]">
</a>
</p>
<p><a name="quote-tuplet-end.ly"></a>
<p><a href="a7/lily-bca50a78.ly"><samp><span class="file">quote-tuplet-end.ly</span></samp>
</a>
<p>Tuplet bracket ends properly when quoting.
<p>
<a href="a7/lily-bca50a78.ly">
<img align="middle"
border="0" src="a7/lily-bca50a78.png" alt="[image of music]">
</a>
</p>
<p><a name="quote-tuplet.ly"></a>
<p><a href="34/lily-26fa8285.ly"><samp><span class="file">quote-tuplet.ly</span></samp>
</a>
<p>In cue notes, Tuplet stops are handled before new tuplets
start.
<p>
<a href="34/lily-26fa8285.ly">
<img align="middle"
border="0" src="34/lily-26fa8285.png" alt="[image of music]">
</a>
</p>
<p><a name="quote.ly"></a>
<p><a href="c5/lily-2649de55.ly"><samp><span class="file">quote.ly</span></samp>
</a>
<p>With <code>\quote</code>, fragments of previously entered
music may be quoted. <code>quotedEventTypes</code> will determines what
things are quoted. In this example, a 16th rest is not quoted, since
<code>rest-event</code> is not in <code>quotedEventTypes</code>.
<p>
<a href="c5/lily-2649de55.ly">
<img align="middle"
border="0" src="c5/lily-2649de55.png" alt="[image of music]">
</a>
</p>
<p><a name="ragged-right-compressed.ly"></a>
<p><a href="51/lily-d34e7a91.ly"><samp><span class="file">ragged-right-compressed.ly</span></samp>
</a>
<p>When a score takes up only a single line and it is compressed, it
is not printed as ragged.
<p>
<a href="51/lily-d34e7a91.ly">
<img align="middle"
border="0" src="51/lily-d34e7a91.png" alt="[image of music]">
</a>
</p>
<p><a name="ragged-right-disabled.ly"></a>
<p><a href="e2/lily-4ae834e1.ly"><samp><span class="file">ragged-right-disabled.ly</span></samp>
</a>
<p>When ragged-right is specifically disabled, a score with only one
line will not be printed as ragged.
<p>
<a href="e2/lily-4ae834e1.ly">
<img align="middle"
border="0" src="e2/lily-4ae834e1.png" alt="[image of music]">
</a>
</p>
<p><a name="ragged-right-one-line.ly"></a>
<p><a href="03/lily-df5a0bee.ly"><samp><span class="file">ragged-right-one-line.ly</span></samp>
</a>
<p>When a score takes up only a single line and it is stretched, it
is printed as ragged by default.
<p>
<a href="03/lily-df5a0bee.ly">
<img align="middle"
border="0" src="03/lily-df5a0bee.png" alt="[image of music]">
</a>
</p>
<p><a name="rehearsal-mark-align-priority.ly"></a>
<p><a href="d8/lily-5b62f093.ly"><samp><span class="file">rehearsal-mark-align-priority.ly</span></samp>
</a>
<p>When the break-align-symbols property is given as a list,
the alignment depends on which symbols are visible.
<p>
<a href="d8/lily-5b62f093.ly">
<img align="middle"
border="0" src="d8/lily-5b62f093.png" alt="[image of music]">
</a>
</p>
<p><a name="rehearsal-mark-align-staff-context.ly"></a>
<p><a href="e0/lily-bc68b539.ly"><samp><span class="file">rehearsal-mark-align-staff-context.ly</span></samp>
</a>
<p>RehearsalMarks still align correctly if Mark_engraver is moved to
another context.
<p>
<a href="e0/lily-bc68b539.ly">
<img align="middle"
border="0" src="e0/lily-bc68b539.png" alt="[image of music]">
</a>
</p>
<p><a name="rehearsal-mark-align.ly"></a>
<p><a href="42/lily-bbff2713.ly"><samp><span class="file">rehearsal-mark-align.ly</span></samp>
</a>
<p>The rehearsal mark is put on top a breakable symbol,
according to the value of <code>break-align-symbols</code> value of the
<code>RehearsalMark</code>. The same holds for <code>BarNumber</code> grobs.
<p>
<a href="42/lily-bbff2713.ly">
<img align="middle"
border="0" src="42/lily-bbff2713.png" alt="[image of music]">
</a>
</p>
<p><a name="rehearsal-mark-letter.ly"></a>
<p><a href="ed/lily-b2ca296b.ly"><samp><span class="file">rehearsal-mark-letter.ly</span></samp>
</a>
<p>Rehearsal marks in letter style: the I is skipped, and
after Z, double letters are used. The mark may be set with
<code>\mark NUMBER</code>, or with <code>Score.rehearsalMark</code>.
<p>
<a href="ed/lily-b2ca296b.ly">
<img align="middle"
border="0" src="ed/lily-b2ca296b.png" alt="[image of music]">
</a>
</p>
<p><a name="rehearsal-mark-number.ly"></a>
<p><a href="60/lily-d8073ef3.ly"><samp><span class="file">rehearsal-mark-number.ly</span></samp>
</a>
<p>Marks can be printed as numbers.
By setting <code>markFormatter</code> we may choose a different style of mark printing. Also, marks can be specified manually, with a markup argument.
<p>
<a href="60/lily-d8073ef3.ly">
<img align="middle"
border="0" src="60/lily-d8073ef3.png" alt="[image of music]">
</a>
</p>
<p><a name="relative-repeat.ly"></a>
<p><a href="75/lily-eedbd6bd.ly"><samp><span class="file">relative-repeat.ly</span></samp>
</a>
<p>Relative mode for repeats uses order of entry.
<p>
<a href="75/lily-eedbd6bd.ly">
<img align="middle"
border="0" src="75/lily-eedbd6bd.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-line-break.ly"></a>
<p><a href="eb/lily-837dab5b.ly"><samp><span class="file">repeat-line-break.ly</span></samp>
</a>
<p>Across linebreaks, the left edge of a first and second alternative
bracket should be equal.
<p class="noindent"><p>
<a href="eb/lily-837dab5b.ly">
<img align="middle"
border="0" src="eb/lily-837dab5b.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-percent-count.ly"></a>
<p><a href="88/lily-2f1fe97f.ly"><samp><span class="file">repeat-percent-count.ly</span></samp>
</a>
<p>Percent repeats get incremental numbers when
<code>countPercentRepeats</code> is set, to indicate the repeat counts, but
only if there are more than two repeats.
<p>
<a href="88/lily-2f1fe97f.ly">
<img align="middle"
border="0" src="88/lily-2f1fe97f.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-percent-grace.ly"></a>
<p><a href="c3/lily-ecea0884.ly"><samp><span class="file">repeat-percent-grace.ly</span></samp>
</a>
<p>Percent repeats are also centered when there is a grace note in a parallel staff.
<p>
<a href="c3/lily-ecea0884.ly">
<img align="middle"
border="0" src="c3/lily-ecea0884.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-percent-skipbars.ly"></a>
<p><a href="72/lily-cceb3fd0.ly"><samp><span class="file">repeat-percent-skipbars.ly</span></samp>
</a>
<p>Percent repeats are not skipped, even when <code>skipBars</code> is set.
<p>
<a href="72/lily-cceb3fd0.ly">
<img align="middle"
border="0" src="72/lily-cceb3fd0.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-percent.ly"></a>
<p><a href="0c/lily-101a1d6a.ly"><samp><span class="file">repeat-percent.ly</span></samp>
</a>
<p>Measure repeats may be nested with beat repeats.
<p>
<a href="0c/lily-101a1d6a.ly">
<img align="middle"
border="0" src="0c/lily-101a1d6a.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-slash.ly"></a>
<p><a href="2f/lily-ec40e7c6.ly"><samp><span class="file">repeat-slash.ly</span></samp>
</a>
<p>Within a bar, beat repeats denote that a music snippet should be
played again.
<p>
<a href="2f/lily-ec40e7c6.ly">
<img align="middle"
border="0" src="2f/lily-ec40e7c6.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-tie.ly"></a>
<p><a href="c9/lily-70d0b8bc.ly"><samp><span class="file">repeat-tie.ly</span></samp>
</a>
<p>Repeat ties are only connected on the right side to a
note head.
<p>
<a href="c9/lily-70d0b8bc.ly">
<img align="middle"
border="0" src="c9/lily-70d0b8bc.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-tremolo-beams.ly"></a>
<p><a href="d5/lily-2ee6b053.ly"><samp><span class="file">repeat-tremolo-beams.ly</span></samp>
</a>
<p>Each of the staves here should have four tremolo beams.
<p>
<a href="d5/lily-2ee6b053.ly">
<img align="middle"
border="0" src="d5/lily-2ee6b053.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-tremolo-dots.ly"></a>
<p><a href="e4/lily-7be33e07.ly"><samp><span class="file">repeat-tremolo-dots.ly</span></samp>
</a>
<p>Dots are added to tremolo notes if the durations involved require them.
<p>
<a href="e4/lily-7be33e07.ly">
<img align="middle"
border="0" src="e4/lily-7be33e07.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-unfold-all.ly"></a>
<p><a href="82/lily-955c31b3.ly"><samp><span class="file">repeat-unfold-all.ly</span></samp>
</a>
<p>Volta repeats may be unfolded through the music
function <code>\unfoldRepeats</code>.
<p>
<a href="82/lily-955c31b3.ly">
<img align="middle"
border="0" src="82/lily-955c31b3.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-unfold-tremolo.ly"></a>
<p><a href="13/lily-babc8613.ly"><samp><span class="file">repeat-unfold-tremolo.ly</span></samp>
</a>
<p>Unfolding tremolo repeats. All fragments fill one
measure with 16th notes exactly.
<p>
<a href="13/lily-babc8613.ly">
<img align="middle"
border="0" src="13/lily-babc8613.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-unfold.ly"></a>
<p><a href="e8/lily-365f8c62.ly"><samp><span class="file">repeat-unfold.ly</span></samp>
</a>
<p>LilyPond has two modes for repeats: unfolded and semi-unfolded.
Unfolded repeats are fully written out. Semi unfolded repeats have the body
written and all alternatives sequentially. If the number of alternatives is
larger than the repeat count, the excess alternatives are ignored. If the
number of alternatives is smaller, the first alternative is multiplied to
get to the number of repeats.
<p>Unfolded behavior:
<p>
<a href="e8/lily-365f8c62.ly">
<img align="middle"
border="0" src="e8/lily-365f8c62.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-volta-skip-alternatives.ly"></a>
<p><a href="4b/lily-4469fb9d.ly"><samp><span class="file">repeat-volta-skip-alternatives.ly</span></samp>
</a>
<p>When too few alternatives are present, the first
alternative is repeated, by printing a range for the 1st repeat.
<p>
<a href="4b/lily-4469fb9d.ly">
<img align="middle"
border="0" src="4b/lily-4469fb9d.png" alt="[image of music]">
</a>
</p>
<p><a name="repeat-volta.ly"></a>
<p><a href="df/lily-e9eb9182.ly"><samp><span class="file">repeat-volta.ly</span></samp>
</a>
<p>Volta (Semi folded) behavior. Voltas can start on non-barline moments.
If they don't barlines should still be shown.
<p class="noindent"><p>
<a href="df/lily-e9eb9182.ly">
<img align="middle"
border="0" src="df/lily-e9eb9182.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-collision-beam-note.ly"></a>
<p><a href="a1/lily-80feba89.ly"><samp><span class="file">rest-collision-beam-note.ly</span></samp>
</a>
<p>Beam/rest collision resolution and normal rest/note
collisions can be combined.
<p>
<a href="a1/lily-80feba89.ly">
<img align="middle"
border="0" src="a1/lily-80feba89.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-collision-beam-quantized.ly"></a>
<p><a href="7c/lily-eeca2b77.ly"><samp><span class="file">rest-collision-beam-quantized.ly</span></samp>
</a>
<p>Rests under beams are moved by whole staff spaces.
<p>
<a href="7c/lily-eeca2b77.ly">
<img align="middle"
border="0" src="7c/lily-eeca2b77.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-collision-beam-restdir.ly"></a>
<p><a href="7b/lily-51629e6a.ly"><samp><span class="file">rest-collision-beam-restdir.ly</span></samp>
</a>
<p>Beam/rest collision takes offset due to <code>Rest #'direction</code> into
account properly.
<p>
<a href="7b/lily-51629e6a.ly">
<img align="middle"
border="0" src="7b/lily-51629e6a.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-collision-beam.ly"></a>
<p><a href="16/lily-33cbec52.ly"><samp><span class="file">rest-collision-beam.ly</span></samp>
</a>
<p>Rests under beams are shifted upon
collision.
<p>
<a href="16/lily-33cbec52.ly">
<img align="middle"
border="0" src="16/lily-33cbec52.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-collision.ly"></a>
<p><a href="af/lily-935757ff.ly"><samp><span class="file">rest-collision.ly</span></samp>
</a>
<p>Rests should not collide with beams, stems and noteheads. Rests may
be under beams. Rests should be move by integral number of spaces
inside the staff, and by half spaces outside. Notice that the half
and whole rests just outside the staff get ledger lines in different
cases.
<p class="noindent"><p>
<a href="af/lily-935757ff.ly">
<img align="middle"
border="0" src="af/lily-935757ff.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-dot-position.ly"></a>
<p><a href="1e/lily-96a2a028.ly"><samp><span class="file">rest-dot-position.ly</span></samp>
</a>
<p>Dots of rests should follow the rest positions.
<p>
<a href="1e/lily-96a2a028.ly">
<img align="middle"
border="0" src="1e/lily-96a2a028.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-ledger.ly"></a>
<p><a href="cf/lily-0bc3553c.ly"><samp><span class="file">rest-ledger.ly</span></samp>
</a>
<p>Whole and half rests moving outside the staff should get
ledger lines.
<p>
<a href="cf/lily-0bc3553c.ly">
<img align="middle"
border="0" src="cf/lily-0bc3553c.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-note-collision.ly"></a>
<p><a href="5b/lily-97c8d214.ly"><samp><span class="file">rest-note-collision.ly</span></samp>
</a>
<p>In rest-note collisions, the rest moves in discrete
steps, and inside the staff, it moves in whole staff spaces.
<p>
<a href="5b/lily-97c8d214.ly">
<img align="middle"
border="0" src="5b/lily-97c8d214.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-pitch.ly"></a>
<p><a href="2f/lily-79adb47b.ly"><samp><span class="file">rest-pitch.ly</span></samp>
</a>
<p>Rests can have pitches–these will be affected by
transposition and relativization. If a rest has a pitch, rest/rest and
beam/rest collision resolving will leave it alone.
<p>
<a href="2f/lily-79adb47b.ly">
<img align="middle"
border="0" src="2f/lily-79adb47b.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-pitched-beam.ly"></a>
<p><a href="d4/lily-42ff5657.ly"><samp><span class="file">rest-pitched-beam.ly</span></samp>
</a>
<p>Pitched rests under beams.
<p>
<a href="d4/lily-42ff5657.ly">
<img align="middle"
border="0" src="d4/lily-42ff5657.png" alt="[image of music]">
</a>
</p>
<p><a name="rest-polyphonic.ly"></a>
<p><a href="7f/lily-b03d0a4f.ly"><samp><span class="file">rest-polyphonic.ly</span></samp>
</a>
<p>In polyphonic situations, rests are moved down
even if there is no opposite note or rest. The amount is two
<code>staff-space</code>s.
<p>
<a href="7f/lily-b03d0a4f.ly">
<img align="middle"
border="0" src="7f/lily-b03d0a4f.png" alt="[image of music]">
</a>
</p>
<p><a name="rest.ly"></a>
<p><a href="48/lily-63d6a1fd.ly"><samp><span class="file">rest.ly</span></samp>
</a>
<p>There is a big variety of rests. Note that the dot of 8th, 16th and 32nd
rests rest should be next to the top of the rest. All rests except the
whole rest are centered on the middle staff line.
<p class="noindent"><p>
<a href="48/lily-63d6a1fd.ly">
<img align="middle"
border="0" src="48/lily-63d6a1fd.png" alt="[image of music]">
</a>
</p>
<p><a name="rhythmic-staff.ly"></a>
<p><a href="d3/lily-27daaff4.ly"><samp><span class="file">rhythmic-staff.ly</span></samp>
</a>
<p>In rhythmic staves stems should go up, and bar lines
have the size for a 5 line staff. The whole rest hangs from the
rhythmic staff.
<p>
<a href="d3/lily-27daaff4.ly">
<img align="middle"
border="0" src="d3/lily-27daaff4.png" alt="[image of music]">
</a>
</p>
<p><a name="safe.ly"></a>
<p><a href="77/lily-80b78bc5.ly"><samp><span class="file">safe.ly</span></samp>
</a>
<p>This should not survive lilypond –safe-mode
<p>
<a href="77/lily-80b78bc5.ly">
<img align="middle"
border="0" src="77/lily-80b78bc5.png" alt="[image of music]">
</a>
</p>
<p><a name="score-text.ly"></a>
<p><a href="5d/lily-9beacfa9.ly"><samp><span class="file">score-text.ly</span></samp>
</a>
<p>Markup texts are rendered above or below a score.
<p>
<a href="5d/lily-9beacfa9.ly">
<img align="middle"
border="0" src="5d/lily-9beacfa9.png" alt="[image of music]">
</a>
</p>
<p><a name="script-center-seconds.ly"></a>
<p><a href="ca/lily-1e9ce23f.ly"><samp><span class="file">script-center-seconds.ly</span></samp>
</a>
<p>Scripts on chords with seconds remain centered on the extremal note head
<p>
<a href="ca/lily-1e9ce23f.ly">
<img align="middle"
border="0" src="ca/lily-1e9ce23f.png" alt="[image of music]">
</a>
</p>
<p><a name="script-collision.ly"></a>
<p><a href="80/lily-0d5a791d.ly"><samp><span class="file">script-collision.ly</span></samp>
</a>
<p>Scripts are put on the utmost head, so they are
positioned correctly when there are collisions.
<p>
<a href="80/lily-0d5a791d.ly">
<img align="middle"
border="0" src="80/lily-0d5a791d.png" alt="[image of music]">
</a>
</p>
<p><a name="script-horizontal-slur.ly"></a>
<p><a href="ab/lily-7269953a.ly"><samp><span class="file">script-horizontal-slur.ly</span></samp>
</a>
<p>Horizontal scripts don't have <code>avoid-slur</code> set.
<p>
<a href="ab/lily-7269953a.ly">
<img align="middle"
border="0" src="ab/lily-7269953a.png" alt="[image of music]">
</a>
</p>
<p><a name="script-stack-horizontal.ly"></a>
<p><a href="83/lily-9e197d8f.ly"><samp><span class="file">script-stack-horizontal.ly</span></samp>
</a>
<p>horizontal scripts are ordered, so they do not overlap.
The order may be set with script-priority.
<p>The scripts should not be folded under the time signature.
<p class="noindent"><p>
<a href="83/lily-9e197d8f.ly">
<img align="middle"
border="0" src="83/lily-9e197d8f.png" alt="[image of music]">
</a>
</p>
<p><a name="script-stack-order.ly"></a>
<p><a href="86/lily-1965fa1c.ly"><samp><span class="file">script-stack-order.ly</span></samp>
</a>
<p>Scripts can be stacked. The order is determined by a
priority field, but when objects have the same priority, the input
order determines the order. Objects specified first are closest to the note.
<p class="noindent"><p>
<a href="86/lily-1965fa1c.ly">
<img align="middle"
border="0" src="86/lily-1965fa1c.png" alt="[image of music]">
</a>
</p>
<p><a name="script-stacked.ly"></a>
<p><a href="25/lily-436e42bf.ly"><samp><span class="file">script-stacked.ly</span></samp>
</a>
<p>Scripts may be stacked.
<p>
<a href="25/lily-436e42bf.ly">
<img align="middle"
border="0" src="25/lily-436e42bf.png" alt="[image of music]">
</a>
</p>
<p><a name="script-stem-tremolo.ly"></a>
<p><a href="cc/lily-28953d65.ly"><samp><span class="file">script-stem-tremolo.ly</span></samp>
</a>
<p>Scripts avoid stem tremolos even if there is no visible stem.
<p>
<a href="cc/lily-28953d65.ly">
<img align="middle"
border="0" src="cc/lily-28953d65.png" alt="[image of music]">
</a>
</p>
<p><a name="semi-tie-manual-direction.ly"></a>
<p><a href="0f/lily-690c072d.ly"><samp><span class="file">semi-tie-manual-direction.ly</span></samp>
</a>
<p>Semi tie directions may be forced from the input.
<p>
<a href="0f/lily-690c072d.ly">
<img align="middle"
border="0" src="0f/lily-690c072d.png" alt="[image of music]">
</a>
</p>
<p><a name="size11.ly"></a>
<p><a href="cb/lily-9a329d67.ly"><samp><span class="file">size11.ly</span></samp>
</a>
<p>Different text styles are used for various purposes.
<p class="noindent"><p>
<a href="cb/lily-9a329d67.ly">
<img align="middle"
border="0" src="cb/lily-9a329d67.png" alt="[image of music]">
</a>
</p>
<p><a name="size13.ly"></a>
<p><a href="3f/lily-6f9d0385.ly"><samp><span class="file">size13.ly</span></samp>
</a>
<p>Different text styles are used for various purposes.
<p class="noindent"><p>
<a href="3f/lily-6f9d0385.ly">
<img align="middle"
border="0" src="3f/lily-6f9d0385.png" alt="[image of music]">
</a>
</p>
<p><a name="size16.ly"></a>
<p><a href="93/lily-b7e0db02.ly"><samp><span class="file">size16.ly</span></samp>
</a>
<p>Different text styles are used for various purposes.
<p class="noindent"><p>
<a href="93/lily-b7e0db02.ly">
<img align="middle"
border="0" src="93/lily-b7e0db02.png" alt="[image of music]">
</a>
</p>
<p><a name="size20.ly"></a>
<p><a href="0a/lily-65f6f7da.ly"><samp><span class="file">size20.ly</span></samp>
</a>
<p>Different text styles are used for various purposes.
<p class="noindent"><p>
<a href="0a/lily-65f6f7da.ly">
<img align="middle"
border="0" src="0a/lily-65f6f7da.png" alt="[image of music]">
</a>
</p>
<p><a name="size23.ly"></a>
<p><a href="52/lily-bbea6837.ly"><samp><span class="file">size23.ly</span></samp>
</a>
<p>Different text styles are used for various purposes.
<p class="noindent"><p>
<a href="52/lily-bbea6837.ly">
<img align="middle"
border="0" src="52/lily-bbea6837.png" alt="[image of music]">
</a>
</p>
<p><a name="size26.ly"></a>
<p><a href="b6/lily-cc0266f4.ly"><samp><span class="file">size26.ly</span></samp>
</a>
<p>Different text styles are used for various purposes.
<p class="noindent"><p>
<a href="b6/lily-cc0266f4.ly">
<img align="middle"
border="0" src="b6/lily-cc0266f4.png" alt="[image of music]">
</a>
</p>
<p><a name="skip-of-length.ly"></a>
<p><a href="dd/lily-b570259b.ly"><samp><span class="file">skip-of-length.ly</span></samp>
</a>
<p>skip-of-length and mmrest-of-length create skips and rests that
last as long as their arguments.
<p>
<a href="dd/lily-b570259b.ly">
<img align="middle"
border="0" src="dd/lily-b570259b.png" alt="[image of music]">
</a>
</p>
<p><a name="skiptypesetting-bar-check.ly"></a>
<p><a href="ca/lily-b292984e.ly"><samp><span class="file">skiptypesetting-bar-check.ly</span></samp>
</a>
<p>skipTypesetting doesn't affect bar checks.
<p>
<a href="ca/lily-b292984e.ly">
<img align="middle"
border="0" src="ca/lily-b292984e.png" alt="[image of music]">
</a>
</p>
<p><a name="skiptypesetting-show-last.ly"></a>
<p><a href="81/lily-c836e04d.ly"><samp><span class="file">skiptypesetting-show-last.ly</span></samp>
</a>
<p><code>showLastLength</code> will only show the last bit of a score
<p>
<a href="81/lily-c836e04d.ly">
<img align="middle"
border="0" src="81/lily-c836e04d.png" alt="[image of music]">
</a>
</p>
<p><a name="skiptypesetting-tuplet.ly"></a>
<p><a href="e0/lily-862283c9.ly"><samp><span class="file">skiptypesetting-tuplet.ly</span></samp>
</a>
<p>Tuplet brackets are also skipped with
<code>skipTypesetting</code>.
<p>
<a href="e0/lily-862283c9.ly">
<img align="middle"
border="0" src="e0/lily-862283c9.png" alt="[image of music]">
</a>
</p>
<p><a name="skyline-debug.ly"></a>
<p><a href="48/lily-19ecaefd.ly"><samp><span class="file">skyline-debug.ly</span></samp>
</a>
<p><code>-ddebug-skyline</code> draws the outline of the skyline used.
<p>
<a href="48/lily-19ecaefd.ly">
<img align="middle"
border="0" src="48/lily-19ecaefd.png" alt="[image of music]">
</a>
</p>
<p><a name="skyline-vertical-placement.ly"></a>
<p><a href="ae/lily-a0ce91a9.ly"><samp><span class="file">skyline-vertical-placement.ly</span></samp>
</a>
<p>Grobs that have outside-staff-priority set are positioned
using a skyline algorithm so that they don't collide with other objects.
<p>
<a href="ae/lily-a0ce91a9.ly">
<img align="middle"
border="0" src="ae/lily-a0ce91a9.png" alt="[image of music]">
</a>
</p>
<p><a name="skyline-vertical-spacing.ly"></a>
<p><a href="0f/lily-badc4f16.ly"><samp><span class="file">skyline-vertical-spacing.ly</span></samp>
</a>
<p>We use a skyline algorithm to determine the distance to the next
system instead of relying only on bounding boxes. This keeps gaps between
systems more uniform.
<p>
<a href="0f/lily-badc4f16.ly">
<img align="middle"
border="0" src="0f/lily-badc4f16.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-broken-trend.ly"></a>
<p><a href="5b/lily-371288a9.ly"><samp><span class="file">slur-broken-trend.ly</span></samp>
</a>
<p>Across line breaks, slurs behave nicely. On the left, they extend to
just after the preferatory matter, and on the right to the end of the
staff. A slur should follow the same vertical direction it would have
in unbroken state.
<p class="noindent"><p>
<a href="5b/lily-371288a9.ly">
<img align="middle"
border="0" src="5b/lily-371288a9.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-clef.ly"></a>
<p><a href="39/lily-dcd21aef.ly"><samp><span class="file">slur-clef.ly</span></samp>
</a>
<p>Slurs avoid clefs, but don't avoid barlines.
<p>
<a href="39/lily-dcd21aef.ly">
<img align="middle"
border="0" src="39/lily-dcd21aef.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-cross-staff-beam.ly"></a>
<p><a href="0a/lily-aab49b6b.ly"><samp><span class="file">slur-cross-staff-beam.ly</span></samp>
</a>
<p>Slurs that depend on a cross-staff beam are not calculated until after line-breaking.
<p>
<a href="0a/lily-aab49b6b.ly">
<img align="middle"
border="0" src="0a/lily-aab49b6b.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-cross-staff.ly"></a>
<p><a href="8b/lily-2fc3362c.ly"><samp><span class="file">slur-cross-staff.ly</span></samp>
</a>
<p>Slurs behave decently when broken across a linebreak.
<p class="noindent"><p>
<a href="8b/lily-2fc3362c.ly">
<img align="middle"
border="0" src="8b/lily-2fc3362c.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-dash.ly"></a>
<p><a href="19/lily-084d1f12.ly"><samp><span class="file">slur-dash.ly</span></samp>
</a>
<p><a name="index-Slur_002c-dotted_002c-dashed-13"></a>The appearance of slurs may be changed from solid to dotted or dashed.
<p class="noindent"><p>
<a href="19/lily-084d1f12.ly">
<img align="middle"
border="0" src="19/lily-084d1f12.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-dots.ly"></a>
<p><a href="bc/lily-87fa579b.ly"><samp><span class="file">slur-dots.ly</span></samp>
</a>
<p>Slurs should not get confused by augmentation dots. With a lot
of dots, the problems becomes more visible.
<p>
<a href="bc/lily-87fa579b.ly">
<img align="middle"
border="0" src="bc/lily-87fa579b.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-double.ly"></a>
<p><a href="36/lily-f1d75928.ly"><samp><span class="file">slur-double.ly</span></samp>
</a>
<p>Some composers use slurs both above and below chords.
This can be typeset by setting <code>doubleSlurs</code>
<p>
<a href="36/lily-f1d75928.ly">
<img align="middle"
border="0" src="36/lily-f1d75928.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-dynamics.ly"></a>
<p><a href="fc/lily-d56a4f76.ly"><samp><span class="file">slur-dynamics.ly</span></samp>
</a>
<p>Dynamics avoid collision with slur.
<p>
<a href="fc/lily-d56a4f76.ly">
<img align="middle"
border="0" src="fc/lily-d56a4f76.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-extreme.ly"></a>
<p><a href="75/lily-676b468f.ly"><samp><span class="file">slur-extreme.ly</span></samp>
</a>
<p>Extreme slurs are scaled to fit the pattern, but only symmetrically.
Asymmetric slurs are created by setting <code>eccentricity</code>.
<p>
<a href="75/lily-676b468f.ly">
<img align="middle"
border="0" src="75/lily-676b468f.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-manual.ly"></a>
<p><a href="68/lily-dbe59c37.ly"><samp><span class="file">slur-manual.ly</span></samp>
</a>
<p>Setting <code>positions</code> overrides the automatic
positioning of the slur. It selects the slur configuration closest to
the given pair.
<p>
<a href="68/lily-dbe59c37.ly">
<img align="middle"
border="0" src="68/lily-dbe59c37.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-nice.ly"></a>
<p><a href="70/lily-b7761c65.ly"><samp><span class="file">slur-nice.ly</span></samp>
</a>
<p>Slurs should look nice and symmetric. The curvature may increase
only to avoid noteheads, and as little as possible. Slurs never
run through noteheads or stems.
<p class="noindent"><p>
<a href="70/lily-b7761c65.ly">
<img align="middle"
border="0" src="70/lily-b7761c65.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-rest.ly"></a>
<p><a href="06/lily-a9acb52b.ly"><samp><span class="file">slur-rest.ly</span></samp>
</a>
<p>Slurs may be placed over rests. The slur will avoid
colliding with the rests.
<p class="noindent"><p>
<a href="06/lily-a9acb52b.ly">
<img align="middle"
border="0" src="06/lily-a9acb52b.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-scoring.ly"></a>
<p><a href="8d/lily-e3b7379e.ly"><samp><span class="file">slur-scoring.ly</span></samp>
</a>
<p>Slur formatting is based on scoring. A large number of
slurs are generated. Each esthetic aspect gets demerits, the best
configuration (with least demerits) wins. This must be tested in
one big file, since changing one score parameter for one situation
may affect several other situations.
<p>Tunable parameters are in <samp><span class="file">scm/slur.scm</span></samp>.
<p class="noindent"><p>
<a href="8d/lily-e3b7379e.ly">
<img align="middle"
border="0" src="8d/lily-e3b7379e.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-script-inside.ly"></a>
<p><a href="bd/lily-e4d90cb0.ly"><samp><span class="file">slur-script-inside.ly</span></samp>
</a>
<p>Slurs avoid scripts with <code>avoid-slur</code> set to
<code>inside</code>, scripts avoid slurs with <code>avoid-slur</code> set to
<code>around</code>. Slurs and scripts keep a distance of
<code>slur-padding</code>.
<p>
<a href="bd/lily-e4d90cb0.ly">
<img align="middle"
border="0" src="bd/lily-e4d90cb0.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-script.ly"></a>
<p><a href="6a/lily-9f3c6934.ly"><samp><span class="file">slur-script.ly</span></samp>
</a>
<p>A slur avoids collisions with scripts, which are placed
either inside or outside the slur, depending on the script. The
slur responds appropriately if a script is moved.
<p>
<a href="6a/lily-9f3c6934.ly">
<img align="middle"
border="0" src="6a/lily-9f3c6934.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-symmetry-1.ly"></a>
<p><a href="85/lily-4868d4cb.ly"><samp><span class="file">slur-symmetry-1.ly</span></samp>
</a>
<p>Symmetric figures should lead to symmetric slurs.
<p>
<a href="85/lily-4868d4cb.ly">
<img align="middle"
border="0" src="85/lily-4868d4cb.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-symmetry.ly"></a>
<p><a href="a6/lily-5bdb6585.ly"><samp><span class="file">slur-symmetry.ly</span></samp>
</a>
<p>Symmetric figures should lead to symmetric slurs.
<p>
<a href="a6/lily-5bdb6585.ly">
<img align="middle"
border="0" src="a6/lily-5bdb6585.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-tilt.ly"></a>
<p><a href="df/lily-763eca24.ly"><samp><span class="file">slur-tilt.ly</span></samp>
</a>
<p>The attachment point for strongly sloped slurs is
shifted horizontally slightly. Without this correction, slurs will
point into one note head, and point over another note head.
<p>
<a href="df/lily-763eca24.ly">
<img align="middle"
border="0" src="df/lily-763eca24.png" alt="[image of music]">
</a>
</p>
<p><a name="slur-tuplet.ly"></a>
<p><a href="54/lily-3114d35c.ly"><samp><span class="file">slur-tuplet.ly</span></samp>
</a>
<p><code>TupletNumber</code> grobs are always inside slurs.
This may not work if the slur starts after the tuplet.
<p>
<a href="54/lily-3114d35c.ly">
<img align="middle"
border="0" src="54/lily-3114d35c.png" alt="[image of music]">
</a>
</p>
<p><a name="song-associated-voice.ly"></a>
<p><a href="ba/lily-44266b99.ly"><samp><span class="file">song-associated-voice.ly</span></samp>
</a> <p>
<a href="ba/lily-44266b99.ly">
<img align="middle"
border="0" src="ba/lily-44266b99.png" alt="[image of music]">
</a>
</p>
<p><a name="song-basic-nonenglish.ly"></a>
<p><a href="98/lily-bbb6571a.ly"><samp><span class="file">song-basic-nonenglish.ly</span></samp>
</a> <p>
<a href="98/lily-bbb6571a.ly">
<img align="middle"
border="0" src="98/lily-bbb6571a.png" alt="[image of music]">
</a>
</p>
<p><a name="song-basic.ly"></a>
<p><a href="63/lily-974cb56c.ly"><samp><span class="file">song-basic.ly</span></samp>
</a> <p>
<a href="63/lily-974cb56c.ly">
<img align="middle"
border="0" src="63/lily-974cb56c.png" alt="[image of music]">
</a>
</p>
<p><a name="song-breathe.ly"></a>
<p><a href="05/lily-9033cb3e.ly"><samp><span class="file">song-breathe.ly</span></samp>
</a> <p>
<a href="05/lily-9033cb3e.ly">
<img align="middle"
border="0" src="05/lily-9033cb3e.png" alt="[image of music]">
</a>
</p>
<p><a name="song-melisma.ly"></a>
<p><a href="50/lily-a4b92952.ly"><samp><span class="file">song-melisma.ly</span></samp>
</a> <p>
<a href="50/lily-a4b92952.ly">
<img align="middle"
border="0" src="50/lily-a4b92952.png" alt="[image of music]">
</a>
</p>
<p><a name="song-reordering.ly"></a>
<p><a href="60/lily-0ab3390e.ly"><samp><span class="file">song-reordering.ly</span></samp>
</a> <p>
<a href="60/lily-0ab3390e.ly">
<img align="middle"
border="0" src="60/lily-0ab3390e.png" alt="[image of music]">
</a>
</p>
<p><a name="song-reordering2.ly"></a>
<p><a href="d6/lily-f6164eb5.ly"><samp><span class="file">song-reordering2.ly</span></samp>
</a> <p>
<a href="d6/lily-f6164eb5.ly">
<img align="middle"
border="0" src="d6/lily-f6164eb5.png" alt="[image of music]">
</a>
</p>
<p><a name="song-repetition.ly"></a>
<p><a href="94/lily-39f676ab.ly"><samp><span class="file">song-repetition.ly</span></samp>
</a> <p>
<a href="94/lily-39f676ab.ly">
<img align="middle"
border="0" src="94/lily-39f676ab.png" alt="[image of music]">
</a>
</p>
<p><a name="song-skip-noword.ly"></a>
<p><a href="f3/lily-0d3e0ad8.ly"><samp><span class="file">song-skip-noword.ly</span></samp>
</a> <p>
<a href="f3/lily-0d3e0ad8.ly">
<img align="middle"
border="0" src="f3/lily-0d3e0ad8.png" alt="[image of music]">
</a>
</p>
<p><a name="song-skip.ly"></a>
<p><a href="b3/lily-9d21c876.ly"><samp><span class="file">song-skip.ly</span></samp>
</a> <p>
<a href="b3/lily-9d21c876.ly">
<img align="middle"
border="0" src="b3/lily-9d21c876.png" alt="[image of music]">
</a>
</p>
<p><a name="song-slurs.ly"></a>
<p><a href="b6/lily-121aebc1.ly"><samp><span class="file">song-slurs.ly</span></samp>
</a> <p>
<a href="b6/lily-121aebc1.ly">
<img align="middle"
border="0" src="b6/lily-121aebc1.png" alt="[image of music]">
</a>
</p>
<p><a name="song-splitpart.ly"></a>
<p><a href="4a/lily-94d98ed1.ly"><samp><span class="file">song-splitpart.ly</span></samp>
</a> <p>
<a href="4a/lily-94d98ed1.ly">
<img align="middle"
border="0" src="4a/lily-94d98ed1.png" alt="[image of music]">
</a>
</p>
<p><a name="song-stanzas.ly"></a>
<p><a href="0d/lily-b940b1b6.ly"><samp><span class="file">song-stanzas.ly</span></samp>
</a> <p>
<a href="0d/lily-b940b1b6.ly">
<img align="middle"
border="0" src="0d/lily-b940b1b6.png" alt="[image of music]">
</a>
</p>
<p><a name="song-tempo.ly"></a>
<p><a href="71/lily-de438c13.ly"><samp><span class="file">song-tempo.ly</span></samp>
</a> <p>
<a href="71/lily-de438c13.ly">
<img align="middle"
border="0" src="71/lily-de438c13.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-accidental-staffs.ly"></a>
<p><a href="85/lily-fa807f6e.ly"><samp><span class="file">spacing-accidental-staffs.ly</span></samp>
</a>
<p>Accidentals in different staves do not affect the
spacing of the eighth notes here.
<p>
<a href="85/lily-fa807f6e.ly">
<img align="middle"
border="0" src="85/lily-fa807f6e.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-accidental-stretch.ly"></a>
<p><a href="94/lily-c2daf4ed.ly"><samp><span class="file">spacing-accidental-stretch.ly</span></samp>
</a>
<p>Accidentals do not influence the amount of stretchable space.
The accidental does add a little non-stretchable space.
<p class="noindent"><p>
<a href="94/lily-c2daf4ed.ly">
<img align="middle"
border="0" src="94/lily-c2daf4ed.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-accidental-tie.ly"></a>
<p><a href="06/lily-20481132.ly"><samp><span class="file">spacing-accidental-tie.ly</span></samp>
</a>
<p>Horizontal spacing works as expected on tied notes with
accidentals. No space is reserved for accidentals that end up not being printed,
but accidentals that are printed don't collide with anything.
<p>
<a href="06/lily-20481132.ly">
<img align="middle"
border="0" src="06/lily-20481132.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-accidental.ly"></a>
<p><a href="0c/lily-4f060ab3.ly"><samp><span class="file">spacing-accidental.ly</span></samp>
</a>
<p>Accidentals sticking out to the left
of a note will take a little more space, but only if the spacing is tight.
<p>
<a href="0c/lily-4f060ab3.ly">
<img align="middle"
border="0" src="0c/lily-4f060ab3.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-bar-accidental.ly"></a>
<p><a href="a5/lily-cd4637a8.ly"><samp><span class="file">spacing-bar-accidental.ly</span></samp>
</a>
<p>An accidental following a bar gets space so
the left edge of the acc is at 0.3 - 0.6 staff space of the bar line
<p>
<a href="a5/lily-cd4637a8.ly">
<img align="middle"
border="0" src="a5/lily-cd4637a8.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-bar-arpeggio.ly"></a>
<p><a href="ec/lily-f768fc53.ly"><samp><span class="file">spacing-bar-arpeggio.ly</span></samp>
</a>
<p>An arpeggio following a bar gets space
<p>
<a href="ec/lily-f768fc53.ly">
<img align="middle"
border="0" src="ec/lily-f768fc53.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-bar-stem.ly"></a>
<p><a href="dc/lily-8ecbcaa1.ly"><samp><span class="file">spacing-bar-stem.ly</span></samp>
</a>
<p>Downstem notes following a barline are
printed with some extra space. This is an optical correction similar
to juxtaposed stems.
<p>The bar upstem should be approx 1.1 staff space, the bar downstem 1.3
to 1.5 staff space.
<p>
<a href="dc/lily-8ecbcaa1.ly">
<img align="middle"
border="0" src="dc/lily-8ecbcaa1.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-bar-whole-measure.ly"></a>
<p><a href="ba/lily-ba6b1ded.ly"><samp><span class="file">spacing-bar-whole-measure.ly</span></samp>
</a>
<p>Notes that fill a whole measure are preceded by extra space.
<p>
<a href="ba/lily-ba6b1ded.ly">
<img align="middle"
border="0" src="ba/lily-ba6b1ded.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-clef-first-note.ly"></a>
<p><a href="2d/lily-7a4335aa.ly"><samp><span class="file">spacing-clef-first-note.ly</span></samp>
</a>
<p>Clef changes at the start of a line get much more space
than clef changes halfway the line.
<p>
<a href="2d/lily-7a4335aa.ly">
<img align="middle"
border="0" src="2d/lily-7a4335aa.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-end-of-line.ly"></a>
<p><a href="54/lily-d3bc710e.ly"><samp><span class="file">spacing-end-of-line.ly</span></samp>
</a>
<p>Broken engraving of a bar at the end of a line does not upset
the space following rests and notes.
<p>
<a href="54/lily-d3bc710e.ly">
<img align="middle"
border="0" src="54/lily-d3bc710e.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-ended-voice.ly"></a>
<p><a href="42/lily-fb3d62e1.ly"><samp><span class="file">spacing-ended-voice.ly</span></samp>
</a>
<p>A voicelet (a very short voice to get polyphonic chords correct)
should not confuse the spacing engine.
<p>
<a href="42/lily-fb3d62e1.ly">
<img align="middle"
border="0" src="42/lily-fb3d62e1.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-folded-clef-cross-staff.ly"></a>
<p><a href="17/lily-c39b9005.ly"><samp><span class="file">spacing-folded-clef-cross-staff.ly</span></samp>
</a>
<p>Clefs are also folded under cross staff constructs.
<p>
<a href="17/lily-c39b9005.ly">
<img align="middle"
border="0" src="17/lily-c39b9005.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-folded-clef.ly"></a>
<p><a href="44/lily-189e475c.ly"><samp><span class="file">spacing-folded-clef.ly</span></samp>
</a>
<p>A clef can be folded below notes in a different staff, if
this does not disrupt the flow of the notes.
<p>
<a href="44/lily-189e475c.ly">
<img align="middle"
border="0" src="44/lily-189e475c.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-folded-clef2.ly"></a>
<p><a href="7f/lily-dec12ae5.ly"><samp><span class="file">spacing-folded-clef2.ly</span></samp>
</a>
<p>A clef can be folded below notes in a different staff, if
there is space enough. With <code>Paper_column</code> stencil callbacks we
can show where columns are in the score.
<p>
<a href="7f/lily-dec12ae5.ly">
<img align="middle"
border="0" src="7f/lily-dec12ae5.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-folded-clef3.ly"></a>
<p><a href="89/lily-0c48d80e.ly"><samp><span class="file">spacing-folded-clef3.ly</span></samp>
</a>
<p>Voices that go back and forth between staves do not confuse the spacing engine.
<p>
<a href="89/lily-0c48d80e.ly">
<img align="middle"
border="0" src="89/lily-0c48d80e.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-grace-duration.ly"></a>
<p><a href="40/lily-a9eca5f6.ly"><samp><span class="file">spacing-grace-duration.ly</span></samp>
</a>
<p>Spacing uses the duration of the notes, but disregards
grace notes for this. In this example, the 8ths around the grace
are spaced exactly as the other 8th notes.
<p class="noindent"><p>
<a href="40/lily-a9eca5f6.ly">
<img align="middle"
border="0" src="40/lily-a9eca5f6.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-grace.ly"></a>
<p><a href="e8/lily-1b78c632.ly"><samp><span class="file">spacing-grace.ly</span></samp>
</a>
<p>Grace note runs have their own spacing variables in
<code>Score.GraceSpacing</code>. So differing grace note lengths inside a
run are spaced accordingly.
<p>
<a href="e8/lily-1b78c632.ly">
<img align="middle"
border="0" src="e8/lily-1b78c632.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-horizontal-skyline-grace.ly"></a>
<p><a href="dd/lily-c78dedc3.ly"><samp><span class="file">spacing-horizontal-skyline-grace.ly</span></samp>
</a>
<p>Skyline horizontal spacing may fold non-adjacent columns
together, but they still do not collide. In this case, the arpeggio
and the barline do not collide.
<p>
<a href="dd/lily-c78dedc3.ly">
<img align="middle"
border="0" src="dd/lily-c78dedc3.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-horizontal-skyline.ly"></a>
<p><a href="c2/lily-5f41b948.ly"><samp><span class="file">spacing-horizontal-skyline.ly</span></samp>
</a>
<p>accidentals may be folded under preceding notes.
<p>
<a href="c2/lily-5f41b948.ly">
<img align="middle"
border="0" src="c2/lily-5f41b948.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-knee-compressed.ly"></a>
<p><a href="fa/lily-eac2f942.ly"><samp><span class="file">spacing-knee-compressed.ly</span></samp>
</a>
<p>Spacing corrections for kneed beams still work when compression is involved.
<p>
<a href="fa/lily-eac2f942.ly">
<img align="middle"
border="0" src="fa/lily-eac2f942.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-knee.ly"></a>
<p><a href="07/lily-32dff2da.ly"><samp><span class="file">spacing-knee.ly</span></samp>
</a>
<p>For knees, the spacing correction is such that the
stems are put at regular distances. This effect takes into account the
width of the note heads and the thickness of the stem.
<p class="noindent"><p>
<a href="07/lily-32dff2da.ly">
<img align="middle"
border="0" src="07/lily-32dff2da.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-loose-grace-error.ly"></a>
<p><a href="2d/lily-21eafd72.ly"><samp><span class="file">spacing-loose-grace-error.ly</span></samp>
</a>
<p>Even in case of incorrect contexts (eg. shortlived
contexts) that break linking of columns through spacing wishes,
<code>strict-note-spacing</code> defaults to a robust solution.
<p>
<a href="2d/lily-21eafd72.ly">
<img align="middle"
border="0" src="2d/lily-21eafd72.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-loose-grace-linebreak.ly"></a>
<p><a href="8e/lily-a2f530e9.ly"><samp><span class="file">spacing-loose-grace-linebreak.ly</span></samp>
</a>
<p>If a floating grace spacing section attaches to a note
across a line break, it gets attached to the end of line.
<p>
<a href="8e/lily-a2f530e9.ly">
<img align="middle"
border="0" src="8e/lily-a2f530e9.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-loose-grace.ly"></a>
<p><a href="76/lily-cb6588c3.ly"><samp><span class="file">spacing-loose-grace.ly</span></samp>
</a>
<p>With <code>strict-grace-spacing</code>, grace notes don't influence
spacing.
<p>
<a href="76/lily-cb6588c3.ly">
<img align="middle"
border="0" src="76/lily-cb6588c3.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-mark-width.ly"></a>
<p><a href="65/lily-6ff06f57.ly"><samp><span class="file">spacing-mark-width.ly</span></samp>
</a>
<p>Width of marks does not affect spacing.
<p>
<a href="65/lily-6ff06f57.ly">
<img align="middle"
border="0" src="65/lily-6ff06f57.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-measure-length.ly"></a>
<p><a href="6d/lily-58e09688.ly"><samp><span class="file">spacing-measure-length.ly</span></samp>
</a>
<p>Horizontal spacing is bounded by the current measure length.
This means that the 3/8 setting does not affect the whole rest spacing.
<p>
<a href="6d/lily-58e09688.ly">
<img align="middle"
border="0" src="6d/lily-58e09688.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-multi-tuplet.ly"></a>
<p><a href="46/lily-74506e88.ly"><samp><span class="file">spacing-multi-tuplet.ly</span></samp>
</a>
<p>Concurrent tuplets should be equidistant on all staves.
Such equidistant spacing is at odds with elegant engraver spacing;
hence it must be switched on explicitly with the
<code>uniform-stretching</code> property of <code>SpacingSpanner</code>.
<p>
<a href="46/lily-74506e88.ly">
<img align="middle"
border="0" src="46/lily-74506e88.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-no-note.ly"></a>
<p><a href="16/lily-4b7a1b88.ly"><samp><span class="file">spacing-no-note.ly</span></samp>
</a>
<p>In the absence of NoteSpacings, wide objects still get
extra space. In this case, the slash before the barline gets a little
more space.
<p>
<a href="16/lily-4b7a1b88.ly">
<img align="middle"
border="0" src="16/lily-4b7a1b88.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-non-adjacent-columns1.ly"></a>
<p><a href="91/lily-dd4fb4af.ly"><samp><span class="file">spacing-non-adjacent-columns1.ly</span></samp>
</a>
<p>The spacing engine avoids collisions between non-adjacent columns.
<p>
<a href="91/lily-dd4fb4af.ly">
<img align="middle"
border="0" src="91/lily-dd4fb4af.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-non-adjacent-columns2.ly"></a>
<p><a href="1c/lily-1013f33b.ly"><samp><span class="file">spacing-non-adjacent-columns2.ly</span></samp>
</a>
<p>The spacing engine avoids collisions between non-adjacent columns.
<p>
<a href="1c/lily-1013f33b.ly">
<img align="middle"
border="0" src="1c/lily-1013f33b.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-note-flags.ly"></a>
<p><a href="8e/lily-f62960b2.ly"><samp><span class="file">spacing-note-flags.ly</span></samp>
</a>
<p>The flags of 8th notes take some space, but not
too much: the space following a flag is less than the space
following a beamed 8th head.
<p>
<a href="8e/lily-f62960b2.ly">
<img align="middle"
border="0" src="8e/lily-f62960b2.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-packed.ly"></a>
<p><a href="b2/lily-d5c9b1ae.ly"><samp><span class="file">spacing-packed.ly</span></samp>
</a>
<p> In packed mode, pack notes as tight as possible. This makes
sense mostly in combination with ragged-right mode: the notes
are then printed at minimum distance. This is mostly useful
for ancient notation, but may also be useful for some flavours
of contemporary music. If not in ragged-right mode, lily will
pack as many bars of music as possible into a line, but the
line will then be stretched to fill the whole linewidth.
<p class="noindent"><p>
<a href="b2/lily-d5c9b1ae.ly">
<img align="middle"
border="0" src="b2/lily-d5c9b1ae.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-proportional.ly"></a>
<p><a href="5e/lily-0960c580.ly"><samp><span class="file">spacing-proportional.ly</span></samp>
</a>
<p>Proportional notation can be created by setting
<code>proportionalNotationDuration</code>. Notes will be spaced proportional
to the distance for the given duration.
<p>
<a href="5e/lily-0960c580.ly">
<img align="middle"
border="0" src="5e/lily-0960c580.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-ragged-last.ly"></a>
<p><a href="e7/lily-8123e469.ly"><samp><span class="file">spacing-ragged-last.ly</span></samp>
</a>
<p>If <code>ragged-last</code> is set, the systems are broken
similar to paragraph formatting in text: the last line is
unjustified.
<p>
<a href="e7/lily-8123e469.ly">
<img align="middle"
border="0" src="e7/lily-8123e469.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-rest.ly"></a>
<p><a href="9e/lily-1c736fea.ly"><samp><span class="file">spacing-rest.ly</span></samp>
</a>
<p>Rests get a little less space, since they are narrower.
However, the quarter rest in feta font is relatively wide, causing this
effect to be very small.
<p class="noindent"><p>
<a href="9e/lily-1c736fea.ly">
<img align="middle"
border="0" src="9e/lily-1c736fea.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-section.ly"></a>
<p><a href="74/lily-d2bd7070.ly"><samp><span class="file">spacing-section.ly</span></samp>
</a>
<p>New sections for spacing can be started with
<code>
ewSpacingSection</code>. In this example, a section is started at
the 4/16, and a 16th in the second section takes as much space as a
8th in first section.
<p>
<a href="74/lily-d2bd7070.ly">
<img align="middle"
border="0" src="74/lily-d2bd7070.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-short-notes.ly"></a>
<p><a href="19/lily-529f1eb5.ly"><samp><span class="file">spacing-short-notes.ly</span></samp>
</a>
<p>Notes that are shorter than the common shortest note get a
space (i.e. without the space needed for the note) proportional to
their duration. So, the 16th notes get 1/2 of the space of an eigth note.
The total distance for a 16th (which includes note head) is 3/4 of the
eighth note.
<p>
<a href="19/lily-529f1eb5.ly">
<img align="middle"
border="0" src="19/lily-529f1eb5.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-space-to-barline.ly"></a>
<p><a href="fb/lily-900fa841.ly"><samp><span class="file">spacing-space-to-barline.ly</span></samp>
</a>
<p>When space-to-barline is false, we measure the space between the note and the
start of the clef. When space-to-barline is true, we measure the space between the note and
the start of the barline.
<p>
<a href="fb/lily-900fa841.ly">
<img align="middle"
border="0" src="fb/lily-900fa841.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-stem-bar.ly"></a>
<p><a href="53/lily-a4b6aa67.ly"><samp><span class="file">spacing-stem-bar.ly</span></samp>
</a>
<p>Upstem notes before a barline are printed with some extra
space. This is an optical correction similar to juxtaposed stems.
<p class="noindent"><p>
<a href="53/lily-a4b6aa67.ly">
<img align="middle"
border="0" src="53/lily-a4b6aa67.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-stem-direction.ly"></a>
<p><a href="24/lily-d87c4314.ly"><samp><span class="file">spacing-stem-direction.ly</span></samp>
</a>
<p>There are optical corrections to the spacing of stems. The overlap between
two adjacent stems of different direction is used as a measure for how
much to correct.
<p>
<a href="24/lily-d87c4314.ly">
<img align="middle"
border="0" src="24/lily-d87c4314.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-stem-same-direction.ly"></a>
<p><a href="39/lily-9a7d1e17.ly"><samp><span class="file">spacing-stem-same-direction.ly</span></samp>
</a>
<p>For juxtaposed chords with the same direction, a
slight optical correction is used. It is constant, and works only if
two chords have no common head-positions range.
<p>
<a href="39/lily-9a7d1e17.ly">
<img align="middle"
border="0" src="39/lily-9a7d1e17.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-stick-out.ly"></a>
<p><a href="1b/lily-47a754cb.ly"><samp><span class="file">spacing-stick-out.ly</span></samp>
</a>
<p>If <code>keep-inside-line</code> is set for the relevant
PaperColumn, LilyPond will space a line to prevent text sticking out
of the right margin.
<p>
<a href="1b/lily-47a754cb.ly">
<img align="middle"
border="0" src="1b/lily-47a754cb.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-strict-notespacing.ly"></a>
<p><a href="d5/lily-6729582f.ly"><samp><span class="file">spacing-strict-notespacing.ly</span></samp>
</a>
<p>If <code>strict-note-spacing</code> is set, then spacing of
notes is not influenced by bars and clefs half-way on the system.
Rather, they are put just before the note that occurs at the same
time. This may cause collisions.
<p>
<a href="d5/lily-6729582f.ly">
<img align="middle"
border="0" src="d5/lily-6729582f.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-strict-spacing-grace.ly"></a>
<p><a href="bf/lily-0bfc00dc.ly"><samp><span class="file">spacing-strict-spacing-grace.ly</span></samp>
</a>
<p>With <code>strict-note-spacing</code> spacing for grace notes
(even multiple ones), is floating as well.
<p>
<a href="bf/lily-0bfc00dc.ly">
<img align="middle"
border="0" src="bf/lily-0bfc00dc.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-to-empty-barline.ly"></a>
<p><a href="54/lily-7b5dbb61.ly"><samp><span class="file">spacing-to-empty-barline.ly</span></samp>
</a>
<p>An empty barline does not confuse the spacing engine too much.
The two scores should look approximately the same.
<p>
<a href="54/lily-7b5dbb61.ly">
<img align="middle"
border="0" src="54/lily-7b5dbb61.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-to-grace.ly"></a>
<p><a href="07/lily-c4c90b85.ly"><samp><span class="file">spacing-to-grace.ly</span></samp>
</a>
<p>Space from a normal note (or barline) to a grace note is
smaller than to a normal note.
<p>
<a href="07/lily-c4c90b85.ly">
<img align="middle"
border="0" src="07/lily-c4c90b85.png" alt="[image of music]">
</a>
</p>
<p><a name="spacing-uniform-stretching.ly"></a>
<p><a href="f4/lily-858eaf9c.ly"><samp><span class="file">spacing-uniform-stretching.ly</span></samp>
</a>
<p>Notes are spaced exactly according to durations,
if <code>uniform-stretching</code> is set. Accidentals are ignored, and no
optical-stem spacing is performed.
<p>
<a href="f4/lily-858eaf9c.ly">
<img align="middle"
border="0" src="f4/lily-858eaf9c.png" alt="[image of music]">
</a>
</p>
<p><a name="span-bar-break.ly"></a>
<p><a href="58/lily-5c60fc4d.ly"><samp><span class="file">span-bar-break.ly</span></samp>
</a>
<p>At the beginning of a system, the <code>|:</code> repeat
barline is drawn between the staves, but the <code>:|</code> is not.
<p>
<a href="58/lily-5c60fc4d.ly">
<img align="middle"
border="0" src="58/lily-5c60fc4d.png" alt="[image of music]">
</a>
</p>
<p><a name="span-bar-partial.ly"></a>
<p><a href="f6/lily-8f2c322e.ly"><samp><span class="file">span-bar-partial.ly</span></samp>
</a>
<p>Span bars can be turned on/off on a staff-by-staff basis.
<p>
<a href="f6/lily-8f2c322e.ly">
<img align="middle"
border="0" src="f6/lily-8f2c322e.png" alt="[image of music]">
</a>
</p>
<p><a name="span-bar-spacing.ly"></a>
<p><a href="c9/lily-dfb04b8d.ly"><samp><span class="file">span-bar-spacing.ly</span></samp>
</a>
<p>SpanBars participate in the horizontal collision system;
the accidentals should not collide with the bar lines.
<p>
<a href="c9/lily-dfb04b8d.ly">
<img align="middle"
border="0" src="c9/lily-dfb04b8d.png" alt="[image of music]">
</a>
</p>
<p><a name="span-bar.ly"></a>
<p><a href="85/lily-3286ec56.ly"><samp><span class="file">span-bar.ly</span></samp>
</a>
<p>Span bars are drawn only between staff bar lines. By setting
bar lines to transparent, they are shown only between systems.
<p>Setting <code>SpanBar</code> transparent removes the barlines
between systems.
<p class="noindent"><p>
<a href="85/lily-3286ec56.ly">
<img align="middle"
border="0" src="85/lily-3286ec56.png" alt="[image of music]">
</a>
</p>
<p><a name="spanner-break-beyond-parent.ly"></a>
<p><a href="f5/lily-0208323f.ly"><samp><span class="file">spanner-break-beyond-parent.ly</span></samp>
</a>
<p>Spanners parts that extend beyond their parents
are killed in case of line breaks.
<p>
<a href="f5/lily-0208323f.ly">
<img align="middle"
border="0" src="f5/lily-0208323f.png" alt="[image of music]">
</a>
</p>
<p><a name="spanner-break-overshoot.ly"></a>
<p><a href="6c/lily-390dd425.ly"><samp><span class="file">spanner-break-overshoot.ly</span></samp>
</a>
<p>The <code>break-overshoot</code> property sets the amount that
a spanner (in this case: the beam) in case of a line break extends
beyond the rightmost column and extends to the left beyond the
prefatory matter.
<p>
<a href="6c/lily-390dd425.ly">
<img align="middle"
border="0" src="6c/lily-390dd425.png" alt="[image of music]">
</a>
</p>
<p><a name="staccato-pos.ly"></a>
<p><a href="01/lily-fe894752.ly"><samp><span class="file">staccato-pos.ly</span></samp>
</a>
<p>Some scripts must have quantized postions. VErtical
position descend monotonously for a descending scale. The staccato
dot is close to the notehead. If the head is in a space, then the dot
is in the space next to it.
<p>
<a href="01/lily-fe894752.ly">
<img align="middle"
border="0" src="01/lily-fe894752.png" alt="[image of music]">
</a>
</p>
<p><a name="staff-halfway.ly"></a>
<p><a href="5b/lily-f516da1a.ly"><samp><span class="file">staff-halfway.ly</span></samp>
</a>
<p>Staves can be started and stopped at command.
<p>
<a href="5b/lily-f516da1a.ly">
<img align="middle"
border="0" src="5b/lily-f516da1a.png" alt="[image of music]">
</a>
</p>
<p><a name="staff-line-positions.ly"></a>
<p><a href="57/lily-2d4741b1.ly"><samp><span class="file">staff-line-positions.ly</span></samp>
</a>
<p>The vertical positions of staff lines may be specified
individually, by setting the <code>line-positions</code> property of the
StaffSymbol.
<p>
<a href="57/lily-2d4741b1.ly">
<img align="middle"
border="0" src="57/lily-2d4741b1.png" alt="[image of music]">
</a>
</p>
<p><a name="staff-mixed-size.ly"></a>
<p><a href="4c/lily-02cadffb.ly"><samp><span class="file">staff-mixed-size.ly</span></samp>
</a>
<p>Staves may be present in several sizes within a score.
This is achieved with an internal scaling factor. If the scaling factor is
forgotten in some places, objects generally become too thick or too
large on smaller staves.
<p>
<a href="4c/lily-02cadffb.ly">
<img align="middle"
border="0" src="4c/lily-02cadffb.png" alt="[image of music]">
</a>
</p>
<p><a name="staff-online-symbol-absence.ly"></a>
<p><a href="96/lily-c6d0a1da.ly"><samp><span class="file">staff-online-symbol-absence.ly</span></samp>
</a>
<p>Symbols that need on-staffline info (like dots and ties)
continue to work in absence of a staff-symbol.
<p>
<a href="96/lily-c6d0a1da.ly">
<img align="middle"
border="0" src="96/lily-c6d0a1da.png" alt="[image of music]">
</a>
</p>
<p><a name="staff-tweak.ly"></a>
<p><a href="d3/lily-47ea667c.ly"><samp><span class="file">staff-tweak.ly</span></samp>
</a>
<p>The staff is a grob (graphical object) which may be adjusted as well, for example, to have 6 thick lines and a slightly large <code>staff-space</code>.
However, beams remain correctly quantized.
<p>
<a href="d3/lily-47ea667c.ly">
<img align="middle"
border="0" src="d3/lily-47ea667c.png" alt="[image of music]">
</a>
</p>
<p><a name="stanza-number.ly"></a>
<p><a href="4c/lily-d0565888.ly"><samp><span class="file">stanza-number.ly</span></samp>
</a>
<p>Stanza numbers are put left of their lyric. They
are aligned in a column.
<p>
<a href="4c/lily-d0565888.ly">
<img align="middle"
border="0" src="4c/lily-d0565888.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-direction-context.ly"></a>
<p><a href="1e/lily-3cf46339.ly"><samp><span class="file">stem-direction-context.ly</span></samp>
</a>
<p>Stem directions for notes on the middle staff line are
determined by the directions of their neighbors.
<p>
<a href="1e/lily-3cf46339.ly">
<img align="middle"
border="0" src="1e/lily-3cf46339.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-direction.ly"></a>
<p><a href="70/lily-ec3e8f7e.ly"><samp><span class="file">stem-direction.ly</span></samp>
</a>
<p>Stems, beams, ties and slurs should behave similarly, when placed
on the middle staff line. Of course stem-direction is down for high
notes, and up for low notes.
<p class="noindent"><p>
<a href="70/lily-ec3e8f7e.ly">
<img align="middle"
border="0" src="70/lily-ec3e8f7e.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-shorten.ly"></a>
<p><a href="9d/lily-0cc89756.ly"><samp><span class="file">stem-shorten.ly</span></samp>
</a>
<p>If note head is `over' the center line, the stem is
shortened. This happens with forced stem directions, and with some
chord configurations.
<p>
<a href="9d/lily-0cc89756.ly">
<img align="middle"
border="0" src="9d/lily-0cc89756.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-stemlet-whole.ly"></a>
<p><a href="a2/lily-48af41bb.ly"><samp><span class="file">stem-stemlet-whole.ly</span></samp>
</a>
<p>Stemlets don't cause stems on whole notes.
<p>
<a href="a2/lily-48af41bb.ly">
<img align="middle"
border="0" src="a2/lily-48af41bb.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-stemlet.ly"></a>
<p><a href="21/lily-b9c2d7da.ly"><samp><span class="file">stem-stemlet.ly</span></samp>
</a>
<p>Stemlets are small stems under beams over rests. Their
length can be set with <code>stemlet-length</code>.
<p>
<a href="21/lily-b9c2d7da.ly">
<img align="middle"
border="0" src="21/lily-b9c2d7da.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-tremolo-forced-dir.ly"></a>
<p><a href="37/lily-1678c87e.ly"><samp><span class="file">stem-tremolo-forced-dir.ly</span></samp>
</a> <p>
<a href="37/lily-1678c87e.ly">
<img align="middle"
border="0" src="37/lily-1678c87e.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-tremolo-position.ly"></a>
<p><a href="74/lily-5bd910cd.ly"><samp><span class="file">stem-tremolo-position.ly</span></samp>
</a>
<p>Tremolos are positioned a fixed distance from the
end of the beam. Tremolo flags are shortened and made rectangular
on beamed notes or on stem-up notes with a flag. Tremolo flags are
tilted extra on stem-down notes with a flag.
<p>
<a href="74/lily-5bd910cd.ly">
<img align="middle"
border="0" src="74/lily-5bd910cd.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-tremolo-staff-space.ly"></a>
<p><a href="91/lily-4269fe67.ly"><samp><span class="file">stem-tremolo-staff-space.ly</span></samp>
</a>
<p>stem tremolo vertical distance also obeys staff-space settings.
<p>
<a href="91/lily-4269fe67.ly">
<img align="middle"
border="0" src="91/lily-4269fe67.png" alt="[image of music]">
</a>
</p>
<p><a name="stem-tremolo.ly"></a>
<p><a href="3f/lily-d61a8b2f.ly"><samp><span class="file">stem-tremolo.ly</span></samp>
</a>
<p>Stem tremolos or rolls are tremolo signs that look like beam segments
crossing stems. If the stem is in a beam, the tremolo must be parallel
to the beam. If the stem is invisible (e.g. on a whole note), the
tremolo must be centered on the note. If the note has a flag (eg. an
unbeamed 8th note), the tremolo should be shortened if the stem is up
and tilted extra if the stem is down.
<p>The tremolos should be positioned a fixed distance from the end of the
stems unless there is no stem, in which case they should be positioned
a fixed distance from the note head.
<p class="noindent"><p>
<a href="3f/lily-d61a8b2f.ly">
<img align="middle"
border="0" src="3f/lily-d61a8b2f.png" alt="[image of music]">
</a>
</p>
<p><a name="stencil-color-rotation.ly"></a>
<p><a href="18/lily-81e1510f.ly"><samp><span class="file">stencil-color-rotation.ly</span></samp>
</a>
<p>Combinations of rotation and color do work.
<p>
<a href="18/lily-81e1510f.ly">
<img align="middle"
border="0" src="18/lily-81e1510f.png" alt="[image of music]">
</a>
</p>
<p><a name="stencil-hacking.ly"></a>
<p><a href="96/lily-8cdbb095.ly"><samp><span class="file">stencil-hacking.ly</span></samp>
</a>
<p>You can write stencil callbacks in Scheme, thus
providing custom glyphs for notation elements. A simple example is
adding parentheses to existing stencil callbacks.
<p>The parenthesized beam is less successful due to implementation of the
Beam. The note head is also rather naive, since the extent of the
parens are also not seen by accidentals.
<p class="noindent"><p>
<a href="96/lily-8cdbb095.ly">
<img align="middle"
border="0" src="96/lily-8cdbb095.png" alt="[image of music]">
</a>
</p>
<p><a name="string-number-around-slur.ly"></a>
<p><a href="ce/lily-bd17ea9f.ly"><samp><span class="file">string-number-around-slur.ly</span></samp>
</a>
<p>String numbers should only be moved outside slurs when there
is a collision.
<p>
<a href="ce/lily-bd17ea9f.ly">
<img align="middle"
border="0" src="ce/lily-bd17ea9f.png" alt="[image of music]">
</a>
</p>
<p><a name="string-number.ly"></a>
<p><a href="e9/lily-b4034e65.ly"><samp><span class="file">string-number.ly</span></samp>
</a>
<p>String numbers can be added to chords. They use the same
positioning mechanism as finger instructions.
<p>
<a href="e9/lily-b4034e65.ly">
<img align="middle"
border="0" src="e9/lily-b4034e65.png" alt="[image of music]">
</a>
</p>
<p><a name="system-extents.ly"></a>
<p><a href="c6/lily-9a2914ca.ly"><samp><span class="file">system-extents.ly</span></samp>
</a>
<p>The size of every system is correctly determined; this
includes postscript constructs such as slurs.
<p>
<a href="c6/lily-9a2914ca.ly">
<img align="middle"
border="0" src="c6/lily-9a2914ca.png" alt="[image of music]">
</a>
</p>
<p><a name="system-overstrike.ly"></a>
<p><a href="6d/lily-9794532b.ly"><samp><span class="file">system-overstrike.ly</span></samp>
</a>
<p>By setting between-system-padding to a negative
value, it is possible to eliminate the anti-collision constraints.
Then setting <code>between-system-space</code> to a low (nonzero) value,
print systems in overstrike.
<p>Unfortunately, this does not show in the colllated texinfo document. Run this example stand-alone to see the effect.
<p class="noindent"><p>
<a href="6d/lily-9794532b.ly">
<img align="middle"
border="0" src="6d/lily-9794532b.png" alt="[image of music]">
</a>
</p>
<p><a name="system-separator.ly"></a>
<p><a href="17/lily-776cef9e.ly"><samp><span class="file">system-separator.ly</span></samp>
</a>
<p>System separators may be defined as markups in the
<code>systemSeparator</code> field of the paper block. They are centered
between the boundary staves of each system.
<p>
<a href="17/lily-776cef9e.ly">
<img align="middle"
border="0" src="17/lily-776cef9e.png" alt="[image of music]">
</a>
</p>
<p><a name="system-start-bracket.ly"></a>
<p><a href="94/lily-ae084cb3.ly"><samp><span class="file">system-start-bracket.ly</span></samp>
</a>
<p>A piano context included within a staff group should
cause the piano brace to be drawn to the left of the staff angle
bracket.
<p>
<a href="94/lily-ae084cb3.ly">
<img align="middle"
border="0" src="94/lily-ae084cb3.png" alt="[image of music]">
</a>
</p>
<p><a name="system-start-heavy-bar.ly"></a>
<p><a href="92/lily-1fe6f0ae.ly"><samp><span class="file">system-start-heavy-bar.ly</span></samp>
</a>
<p>A heavy-bar system start delimiter may be created by tuning the <code>SystemStartBar</code> grob.
<p>
<a href="92/lily-1fe6f0ae.ly">
<img align="middle"
border="0" src="92/lily-1fe6f0ae.png" alt="[image of music]">
</a>
</p>
<p><a name="system-start-nesting.ly"></a>
<p><a href="21/lily-5e9d1026.ly"><samp><span class="file">system-start-nesting.ly</span></samp>
</a>
<p>Deeply nested system braces/brackets/etc. may be created with the
<code>Nested_system_start_delimiter_engraver</code>
<p>
<a href="21/lily-5e9d1026.ly">
<img align="middle"
border="0" src="21/lily-5e9d1026.png" alt="[image of music]">
</a>
</p>
<p><a name="tablature-banjo.ly"></a>
<p><a href="13/lily-56b6abd2.ly"><samp><span class="file">tablature-banjo.ly</span></samp>
</a>
<p>Tablature may also be tuned for banjo.
<p>
<a href="13/lily-56b6abd2.ly">
<img align="middle"
border="0" src="13/lily-56b6abd2.png" alt="[image of music]">
</a>
</p>
<p><a name="tablature-harmonic.ly"></a>
<p><a href="d6/lily-c400d469.ly"><samp><span class="file">tablature-harmonic.ly</span></samp>
</a>
<p>Harmonics get angled brackets in tablature
<p>
<a href="d6/lily-c400d469.ly">
<img align="middle"
border="0" src="d6/lily-c400d469.png" alt="[image of music]">
</a>
</p>
<p><a name="tablature-slide.ly"></a>
<p><a href="21/lily-b68d746e.ly"><samp><span class="file">tablature-slide.ly</span></samp>
</a>
<p>Tab supports slides.
<p>
<a href="21/lily-b68d746e.ly">
<img align="middle"
border="0" src="21/lily-b68d746e.png" alt="[image of music]">
</a>
</p>
<p><a name="tablature-string-tunings.ly"></a>
<p><a href="11/lily-132cabeb.ly"><samp><span class="file">tablature-string-tunings.ly</span></samp>
</a>
<p>For other tunings, it is sufficient to set
<code>stringTunings</code>. The number of staff lines is adjusted
accordingly.
<p>
<a href="11/lily-132cabeb.ly">
<img align="middle"
border="0" src="11/lily-132cabeb.png" alt="[image of music]">
</a>
</p>
<p><a name="tablature.ly"></a>
<p><a href="20/lily-8ea36199.ly"><samp><span class="file">tablature.ly</span></samp>
</a>
<p><a name="index-Tabulature-14"></a>A sample tablature, with both normal staff and tab.
<p>Tablature is done by overriding the note-head formatting function, and
putting it on a 6-line staff. A special engraver takes care of going
from string-number + pitch to number.
<p>String numbers can be entered as note articulations (inside a chord) and
chord articulations (outside a chord)
<p class="noindent"><p>
<a href="20/lily-8ea36199.ly">
<img align="middle"
border="0" src="20/lily-8ea36199.png" alt="[image of music]">
</a>
</p>
<p><a name="tag-filter.ly"></a>
<p><a href="0a/lily-ba5b4ddd.ly"><samp><span class="file">tag-filter.ly</span></samp>
</a>
<p>The <code>\tag</code> command marks music expressions with a
name. These tagged expressions can be filtered out later. This
mechanism can be used to make different versions of the same music. In
this example, the top stave displays the music expression with all
tags included. The bottom two staves are filtered: the part has cue
notes and fingerings, but the score has not.
<p>
<a href="0a/lily-ba5b4ddd.ly">
<img align="middle"
border="0" src="0a/lily-ba5b4ddd.png" alt="[image of music]">
</a>
</p>
<p><a name="test-output-distance.ly"></a>
<p><a href="98/lily-9f103498.ly"><samp><span class="file">test-output-distance.ly</span></samp>
</a>
<p>This file gives a different result each time it is run, so
it should always show up in the output-distance testing.
<p>
<a href="98/lily-9f103498.ly">
<img align="middle"
border="0" src="98/lily-9f103498.png" alt="[image of music]">
</a>
</p>
<p><a name="text-spanner-attachment-alignment.ly"></a>
<p><a href="48/lily-755c4b15.ly"><samp><span class="file">text-spanner-attachment-alignment.ly</span></samp>
</a>
<p>Text and trill spanners are attached to note columns, so
attachments in other staves have no effect on them.
<p>
<a href="48/lily-755c4b15.ly">
<img align="middle"
border="0" src="48/lily-755c4b15.png" alt="[image of music]">
</a>
</p>
<p><a name="text-spanner-override-order.ly"></a>
<p><a href="e2/lily-c7bae6f9.ly"><samp><span class="file">text-spanner-override-order.ly</span></samp>
</a>
<p>The order of setting nested properties does not influence
text spanner layout.
<p>
<a href="e2/lily-c7bae6f9.ly">
<img align="middle"
border="0" src="e2/lily-c7bae6f9.png" alt="[image of music]">
</a>
</p>
<p><a name="text-spanner.ly"></a>
<p><a href="64/lily-de50e758.ly"><samp><span class="file">text-spanner.ly</span></samp>
</a>
<p>Text spanners should not repeat start text when broken.
<p>
<a href="64/lily-de50e758.ly">
<img align="middle"
border="0" src="64/lily-de50e758.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-accidental.ly"></a>
<p><a href="b5/lily-926c1d66.ly"><samp><span class="file">tie-accidental.ly</span></samp>
</a>
<p>lilypond should flip the tie's direction
to avoid a collision with the sharp.
<p class="noindent"><p>
<a href="b5/lily-926c1d66.ly">
<img align="middle"
border="0" src="b5/lily-926c1d66.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-arpeggio-collision.ly"></a>
<p><a href="83/lily-562f0b29.ly"><samp><span class="file">tie-arpeggio-collision.ly</span></samp>
</a>
<p>Advanced tie chord formatting also works with arpegiated
ties. Due to arpeggios, tie directions may be changed relative to the
unarpegiated case.
<p>
<a href="83/lily-562f0b29.ly">
<img align="middle"
border="0" src="83/lily-562f0b29.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-arpeggio.ly"></a>
<p><a href="16/lily-a84b938a.ly"><samp><span class="file">tie-arpeggio.ly</span></samp>
</a>
<p>when <code>tieWaitForNote</code> is set, the right-tied note does not
have to follow the lef-tied note directly. When <code>tieWaitForNote</code>
is set to false, any tie will erase all pending ties.
<p>
<a href="16/lily-a84b938a.ly">
<img align="middle"
border="0" src="16/lily-a84b938a.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-broken-minimum-length.ly"></a>
<p><a href="30/lily-9a9e485e.ly"><samp><span class="file">tie-broken-minimum-length.ly</span></samp>
</a>
<p>Broken ties honor <code>minimum-length</code> also. This tie
has a <code>minimum-length</code> of 5.
<p>
<a href="30/lily-9a9e485e.ly">
<img align="middle"
border="0" src="30/lily-9a9e485e.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-broken-other-staff.ly"></a>
<p><a href="3d/lily-456cb3ce.ly"><samp><span class="file">tie-broken-other-staff.ly</span></samp>
</a>
<p>Broken tie lengths are not affected by clefs
in other staves.
<p>
<a href="3d/lily-456cb3ce.ly">
<img align="middle"
border="0" src="3d/lily-456cb3ce.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-broken.ly"></a>
<p><a href="8d/lily-b66bab00.ly"><samp><span class="file">tie-broken.ly</span></samp>
</a>
<p>Ties behave properly at line breaks.
<p>
<a href="8d/lily-b66bab00.ly">
<img align="middle"
border="0" src="8d/lily-b66bab00.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-chord-broken-extremal.ly"></a>
<p><a href="49/lily-bfc8139e.ly"><samp><span class="file">tie-chord-broken-extremal.ly</span></samp>
</a>
<p>Tie detail property multi-tie-region-size controls how many variations
are tried for the extremal ties in a chord.
<p class="noindent"><p>
<a href="49/lily-bfc8139e.ly">
<img align="middle"
border="0" src="49/lily-bfc8139e.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-chord-debug.ly"></a>
<p><a href="29/lily-dd8d2657.ly"><samp><span class="file">tie-chord-debug.ly</span></samp>
</a>
<p>Switching on debug-tie-scoring annotates the tie scoring
decisions made.
<p>
<a href="29/lily-dd8d2657.ly">
<img align="middle"
border="0" src="29/lily-dd8d2657.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-chord-partial.ly"></a>
<p><a href="0b/lily-143d0c7a.ly"><samp><span class="file">tie-chord-partial.ly</span></samp>
</a>
<p>Individual chord notes can also be tied
<p>
<a href="0b/lily-143d0c7a.ly">
<img align="middle"
border="0" src="0b/lily-143d0c7a.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-chord.ly"></a>
<p><a href="c8/lily-3424d25f.ly"><samp><span class="file">tie-chord.ly</span></samp>
</a>
<p>In chords, ties keep closer to the note head vertically,
but never collide with heads or stems. Seconds are formatted up/down;
the rest of the ties are positioned according to their vertical
position.
<p>The code does not handle all cases. Sometimes ties will printed on top
of or very close to each other. This happens in the last chords of
each system.
<p>
<a href="c8/lily-3424d25f.ly">
<img align="middle"
border="0" src="c8/lily-3424d25f.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-direction-broken.ly"></a>
<p><a href="28/lily-6dd45069.ly"><samp><span class="file">tie-direction-broken.ly</span></samp>
</a>
<p>In the single tie case, broken ties peek across line
boundaries to determine which direction to take.
<p>
<a href="28/lily-6dd45069.ly">
<img align="middle"
border="0" src="28/lily-6dd45069.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-direction-manual.ly"></a>
<p><a href="1d/lily-18942276.ly"><samp><span class="file">tie-direction-manual.ly</span></samp>
</a>
<p>Tie directions can be set with <code>_</code> and <code>^</code>.
This makes correction in complex chords easier.
<p>
<a href="1d/lily-18942276.ly">
<img align="middle"
border="0" src="1d/lily-18942276.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-dot.ly"></a>
<p><a href="5e/lily-f1dadc13.ly"><samp><span class="file">tie-dot.ly</span></samp>
</a>
<p>Ties avoid collisions with dots.
<p>
<a href="5e/lily-f1dadc13.ly">
<img align="middle"
border="0" src="5e/lily-f1dadc13.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-grace.ly"></a>
<p><a href="52/lily-897a6617.ly"><samp><span class="file">tie-grace.ly</span></samp>
</a>
<p>Tying a grace to a following grace or main note works.
<p>
<a href="52/lily-897a6617.ly">
<img align="middle"
border="0" src="52/lily-897a6617.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-manual-vertical-tune.ly"></a>
<p><a href="38/lily-1b77ec2d.ly"><samp><span class="file">tie-manual-vertical-tune.ly</span></samp>
</a>
<p>If using integers, the tie will vertically tuned for
staff line avoidance. If using a floating point number, this is taken
as the exact location.
<p>
<a href="38/lily-1b77ec2d.ly">
<img align="middle"
border="0" src="38/lily-1b77ec2d.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-manual.ly"></a>
<p><a href="fd/lily-d50929b7.ly"><samp><span class="file">tie-manual.ly</span></samp>
</a>
<p>Tie formatting may be adjusted manually, by setting the
<code>tie-configuration</code> property. The override should be placed at
the second note of the chord.
<p>You can leave a Tie alone by introducing a non-pair value
(eg. <code>#t</code>) in the <code>tie-configuration</code> list.
<p class="noindent"><p>
<a href="fd/lily-d50929b7.ly">
<img align="middle"
border="0" src="fd/lily-d50929b7.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-semi-single.ly"></a>
<p><a href="3f/lily-d93c694d.ly"><samp><span class="file">tie-semi-single.ly</span></samp>
</a>
<p>Like normal ties, single semities (LaissezVibrerTie or
RepeatTie) get their direction from the stem direction, and may be
tweaked with <code>#'direction</code>.
<p>
<a href="3f/lily-d93c694d.ly">
<img align="middle"
border="0" src="3f/lily-d93c694d.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-single-chord.ly"></a>
<p><a href="17/lily-4a9664ff.ly"><samp><span class="file">tie-single-chord.ly</span></samp>
</a>
<p>Tie directions are also scored. In hairy configurations,
the default rule for tie directions is overruled.
<p>
<a href="17/lily-4a9664ff.ly">
<img align="middle"
border="0" src="17/lily-4a9664ff.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-single-manual.ly"></a>
<p><a href="e3/lily-0c8af632.ly"><samp><span class="file">tie-single-manual.ly</span></samp>
</a>
<p>Individual ties may be formatted manually by
specifying their <code>direction</code> and/or <code>staff-position</code>.
<p>
<a href="e3/lily-0c8af632.ly">
<img align="middle"
border="0" src="e3/lily-0c8af632.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-single.ly"></a>
<p><a href="c3/lily-88ca2c79.ly"><samp><span class="file">tie-single.ly</span></samp>
</a>
<p>Formatting for isolated ties.
<ul>
<li>short ties are in spaces
<li>long ties cross staff lines
<li>ties avoid flags of left stems.
<li>ties avoid dots of left notes.
<li>short ties are vertically centered in the space, as well those
that otherwise don't fit in a space
<li>extremely short ties are put over the noteheads, instead of inbetween.
</ul>
<p class="noindent"><p>
<a href="c3/lily-88ca2c79.ly">
<img align="middle"
border="0" src="c3/lily-88ca2c79.png" alt="[image of music]">
</a>
</p>
<p><a name="tie-whole.ly"></a>
<p><a href="f7/lily-3f9735b6.ly"><samp><span class="file">tie-whole.ly</span></samp>
</a>
<p>For whole notes, the inside ties do not cross the center
of the note head, horizontally.
<p>
<a href="f7/lily-3f9735b6.ly">
<img align="middle"
border="0" src="f7/lily-3f9735b6.png" alt="[image of music]">
</a>
</p>
<p><a name="to-xml.ly"></a>
<p><a href="70/lily-1370ccdd.ly"><samp><span class="file">to-xml.ly</span></samp>
</a>
<p>The input representation is generic, and may be translated to XML.
<p>
<a href="70/lily-1370ccdd.ly">
<img align="middle"
border="0" src="70/lily-1370ccdd.png" alt="[image of music]">
</a>
</p>
<p><a name="toc.ly"></a>
<p><a href="3f/lily-06f431d0.ly"><samp><span class="file">toc.ly</span></samp>
</a>
<p>A table of contents is included using
<code>\markuplines \table-of-contents</code>. The toc items are added with
the <code>\tocItem</code> command.
<p>
<a href="3f/lily-06f431d0.ly">
<img align="middle"
border="0" src="3f/lily-06f431d0.png" alt="[image of music]">
</a>
</p>
<p><a name="trill-spanner-broken.ly"></a>
<p><a href="42/lily-816f200e.ly"><samp><span class="file">trill-spanner-broken.ly</span></samp>
</a>
<p>A TrillSpanner crossing a line break should restart exactly above
the first note on the new line.
<p>
<a href="42/lily-816f200e.ly">
<img align="middle"
border="0" src="42/lily-816f200e.png" alt="[image of music]">
</a>
</p>
<p><a name="trill-spanner-grace.ly"></a>
<p><a href="e6/lily-f68e92a8.ly"><samp><span class="file">trill-spanner-grace.ly</span></samp>
</a>
<p>Trill spanner can end on a grace note
<p>
<a href="e6/lily-f68e92a8.ly">
<img align="middle"
border="0" src="e6/lily-f68e92a8.png" alt="[image of music]">
</a>
</p>
<p><a name="trill-spanner-pitched-consecutive.ly"></a>
<p><a href="79/lily-d1480364.ly"><samp><span class="file">trill-spanner-pitched-consecutive.ly</span></samp>
</a>
<p>Pitched trills on consecutive notes with the same
name and octave should not lose accidentals; in the following
example, accidentals should be visible for all trill-pitches.
<p class="noindent"><p>
<a href="79/lily-d1480364.ly">
<img align="middle"
border="0" src="79/lily-d1480364.png" alt="[image of music]">
</a>
</p>
<p><a name="trill-spanner-pitched-forced.ly"></a>
<p><a href="11/lily-4f229431.ly"><samp><span class="file">trill-spanner-pitched-forced.ly</span></samp>
</a>
<p>Pitched trill accidentals can be forced.
<p>
<a href="11/lily-4f229431.ly">
<img align="middle"
border="0" src="11/lily-4f229431.png" alt="[image of music]">
</a>
</p>
<p><a name="trill-spanner-pitched.ly"></a>
<p><a href="9f/lily-dd39ecbe.ly"><samp><span class="file">trill-spanner-pitched.ly</span></samp>
</a>
<p>Pitched trills are denoted by a small note head in
parentheses following the main note. This note head is properly
ledgered, and parentheses include the accidental.
<p>
<a href="9f/lily-dd39ecbe.ly">
<img align="middle"
border="0" src="9f/lily-dd39ecbe.png" alt="[image of music]">
</a>
</p>
<p><a name="trill-spanner.ly"></a>
<p><a href="5e/lily-e4c5a4c5.ly"><samp><span class="file">trill-spanner.ly</span></samp>
</a>
<p>The trill symbol and the wavy line are neatly aligned:
the wavy line should appear to come from the crook of the r
<p>
<a href="5e/lily-e4c5a4c5.ly">
<img align="middle"
border="0" src="5e/lily-e4c5a4c5.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-beam.ly"></a>
<p><a href="58/lily-38a0af71.ly"><samp><span class="file">tuplet-beam.ly</span></samp>
</a>
<p>In combination with a beam, the bracket of the tuplet
bracket is removed. This only happens if there is one beam, as long as
the bracket.
<p>
<a href="58/lily-38a0af71.ly">
<img align="middle"
border="0" src="58/lily-38a0af71.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-bracket-cross-staff.ly"></a>
<p><a href="6c/lily-f06873a0.ly"><samp><span class="file">tuplet-bracket-cross-staff.ly</span></samp>
</a>
<p>Cross-staff tuplets are drawn correctly,
even across multiple staves.
<p>
<a href="6c/lily-f06873a0.ly">
<img align="middle"
border="0" src="6c/lily-f06873a0.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-broken.ly"></a>
<p><a href="2b/lily-b5882cad.ly"><samp><span class="file">tuplet-broken.ly</span></samp>
</a>
<p>Broken tuplets are adorned with little arrows. The arrows
come from the <code>edge-text</code> property, and thus be replaced with
larger glyphs or other text.
<p>
<a href="2b/lily-b5882cad.ly">
<img align="middle"
border="0" src="2b/lily-b5882cad.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-full-length-extent.ly"></a>
<p><a href="ab/lily-6e6886de.ly"><samp><span class="file">tuplet-full-length-extent.ly</span></samp>
</a>
<p>With <code>full-length-to-extent</code>, the extent of the
attaching column for a full-length tuplet bracket can be ignored.
<p>
<a href="ab/lily-6e6886de.ly">
<img align="middle"
border="0" src="ab/lily-6e6886de.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-full-length-note.ly"></a>
<p><a href="44/lily-074e143e.ly"><samp><span class="file">tuplet-full-length-note.ly</span></samp>
</a>
<p>tuplet can be made to run to prefatory matter or
the next note, by setting <code>tupletFullLengthNote</code>.
<p>
<a href="44/lily-074e143e.ly">
<img align="middle"
border="0" src="44/lily-074e143e.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-full-length.ly"></a>
<p><a href="d0/lily-7763a467.ly"><samp><span class="file">tuplet-full-length.ly</span></samp>
</a>
<p>If <code>tupletFullLength</code> is set, tuplets end at the
start of the next non-tuplet note.
<p>
<a href="d0/lily-7763a467.ly">
<img align="middle"
border="0" src="d0/lily-7763a467.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-gap.ly"></a>
<p><a href="d9/lily-3151c78c.ly"><samp><span class="file">tuplet-gap.ly</span></samp>
</a>
<p>The size of the tuplet bracket gap is adjusted to the
width of the text.
<p>
<a href="d9/lily-3151c78c.ly">
<img align="middle"
border="0" src="d9/lily-3151c78c.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-nest-beam.ly"></a>
<p><a href="7a/lily-16b783e8.ly"><samp><span class="file">tuplet-nest-beam.ly</span></samp>
</a>
<p>Nested tuplets do collision resolution, also when they
span beams.
<p>
<a href="7a/lily-16b783e8.ly">
<img align="middle"
border="0" src="7a/lily-16b783e8.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-nest.ly"></a>
<p><a href="e2/lily-c9818fd1.ly"><samp><span class="file">tuplet-nest.ly</span></samp>
</a>
<p>Tuplets may be nested.
<p>
<a href="e2/lily-c9818fd1.ly">
<img align="middle"
border="0" src="e2/lily-c9818fd1.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-no-stems.ly"></a>
<p><a href="e0/lily-ad078509.ly"><samp><span class="file">tuplet-no-stems.ly</span></samp>
</a>
<p>Removing Stem_engraver doesn't cause crashes.
<p>
<a href="e0/lily-ad078509.ly">
<img align="middle"
border="0" src="e0/lily-ad078509.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-properties.ly"></a>
<p><a href="07/lily-1fa05dad.ly"><samp><span class="file">tuplet-properties.ly</span></samp>
</a>
<p>Tuplet bracket formatting supports numerous options,
for instance, bracketed (B) and non-bracketed (NB).
<p class="noindent"><p>
<a href="07/lily-1fa05dad.ly">
<img align="middle"
border="0" src="07/lily-1fa05dad.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-rest.ly"></a>
<p><a href="24/lily-a1262f3b.ly"><samp><span class="file">tuplet-rest.ly</span></samp>
</a>
<p>Tuplets may contain rests.
<p>
<a href="24/lily-a1262f3b.ly">
<img align="middle"
border="0" src="24/lily-a1262f3b.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-single-note.ly"></a>
<p><a href="2d/lily-6a2cd9fb.ly"><samp><span class="file">tuplet-single-note.ly</span></samp>
</a>
<p>Show tuplet numbers also on single-note tuplets (otherwise the timing would look messed up!), but don't show a bracket. Make sure that tuplets without any notes don't show any number, either.
<p>
<a href="2d/lily-6a2cd9fb.ly">
<img align="middle"
border="0" src="2d/lily-6a2cd9fb.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-slope.ly"></a>
<p><a href="4c/lily-dc49e0f6.ly"><samp><span class="file">tuplet-slope.ly</span></samp>
</a>
<p>Tuplet brackets stay clear of the staff. The
slope is determined by the graphical characteristic of the notes, but
if the musical pattern does not follow graphical slope, then the
bracket is horizontal
<p>The bracket direction is determined by the dominating stem direction.
<p class="noindent"><p>
<a href="4c/lily-dc49e0f6.ly">
<img align="middle"
border="0" src="4c/lily-dc49e0f6.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplet-staffline-collision.ly"></a>
<p><a href="21/lily-5364cef1.ly"><samp><span class="file">tuplet-staffline-collision.ly</span></samp>
</a>
<p>Horizontal tuplet brackets are shifted vertically
to avoid staff line collisions.
<p>
<a href="21/lily-5364cef1.ly">
<img align="middle"
border="0" src="21/lily-5364cef1.png" alt="[image of music]">
</a>
</p>
<p><a name="tuplets.ly"></a>
<p><a href="37/lily-c2d463ee.ly"><samp><span class="file">tuplets.ly</span></samp>
</a>
<p>Tuplets are indicated by a bracket with a number. There should be no
bracket if there is a beam exactly matching the length of the tuplet.
The bracket does not interfere with the stafflines, and the number is
centered in the gap in the bracket.
<p>The bracket stops at the end of the stems, if the stems have the same
direction as the bracket. The endings can be adjusted with
<code>bracket-flare</code>.
<p class="noindent"><p>
<a href="37/lily-c2d463ee.ly">
<img align="middle"
border="0" src="37/lily-c2d463ee.png" alt="[image of music]">
</a>
</p>
<p><a name="utf-8-mixed-text.ly"></a>
<p><a href="93/lily-a836e958.ly"><samp><span class="file">utf-8-mixed-text.ly</span></samp>
</a>
<p>words in mixed font in a single string
are separated by spaces as in the input string.
Here a Russian word followed by a roman word.
<p>
<a href="93/lily-a836e958.ly">
<img align="middle"
border="0" src="93/lily-a836e958.png" alt="[image of music]">
</a>
</p>
<p><a name="utf-8.ly"></a>
<p><a href="7a/lily-241c98f5.ly"><samp><span class="file">utf-8.ly</span></samp>
</a>
<p>Various scripts may be used for texts (like titles and
lyrics) introduced by entering them in UTF-8 encoding, and using a
Pango based backend. Depending on the fonts installed, this fragment
will render Bulgarian (Cyrillic), Hebrew, Japanese and Portuguese.
<p class="noindent"><p>
<a href="7a/lily-241c98f5.ly">
<img align="middle"
border="0" src="7a/lily-241c98f5.png" alt="[image of music]">
</a>
</p>
<p><a name="voice-follower.ly"></a>
<p><a href="90/lily-b7e88382.ly"><samp><span class="file">voice-follower.ly</span></samp>
</a>
<p>Whenever a voice switches to another staff a line connecting the notes
can be printed automatically. This is enabled if the property
<code>followVoice</code> is set to true.
<p>
<a href="90/lily-b7e88382.ly">
<img align="middle"
border="0" src="90/lily-b7e88382.png" alt="[image of music]">
</a>
</p>
<p><a name="volta-broken-left-edge.ly"></a>
<p><a href="9f/lily-1dd5798c.ly"><samp><span class="file">volta-broken-left-edge.ly</span></samp>
</a>
<p>Broken volta spanners behave correctly at their left edge in all cases.
<p>
<a href="9f/lily-1dd5798c.ly">
<img align="middle"
border="0" src="9f/lily-1dd5798c.png" alt="[image of music]">
</a>
</p>
<p><a name="volta-markup-text.ly"></a>
<p><a href="7d/lily-14e7ba8a.ly"><samp><span class="file">volta-markup-text.ly</span></samp>
</a>
<p>Volte using <code>repeatCommands</code> can have markup
text.
<p>
<a href="7d/lily-14e7ba8a.ly">
<img align="middle"
border="0" src="7d/lily-14e7ba8a.png" alt="[image of music]">
</a>
</p>
<p><a name="volta-multi-staff-inner-staff.ly"></a>
<p><a href="36/lily-74c369a7.ly"><samp><span class="file">volta-multi-staff-inner-staff.ly</span></samp>
</a>
<p>By putting Volta_engraver in a staff context, one can get
volta brackets on staves other than the topmost one.
<p>
<a href="36/lily-74c369a7.ly">
<img align="middle"
border="0" src="36/lily-74c369a7.png" alt="[image of music]">
</a>
</p>
<p><a name="volta-multi-staff.ly"></a>
<p><a href="8d/lily-642729cc.ly"><samp><span class="file">volta-multi-staff.ly</span></samp>
</a>
<p>By default, the volta brackets appear only in the topmost staff.
<p>
<a href="8d/lily-642729cc.ly">
<img align="middle"
border="0" src="8d/lily-642729cc.png" alt="[image of music]">
</a>
</p>
<p><a name="warn-conflicting-key-signatures.ly"></a>
<p><a href="73/lily-1ee635ee.ly"><samp><span class="file">warn-conflicting-key-signatures.ly</span></samp>
</a>
<p>If you specify two different key signatures at one point, a
warning is printed.
<p>
<a href="73/lily-1ee635ee.ly">
<img align="middle"
border="0" src="73/lily-1ee635ee.png" alt="[image of music]">
</a>
</p>
<p><a name="whiteout.ly"></a>
<p><a href="58/lily-a4c1cd85.ly"><samp><span class="file">whiteout.ly</span></samp>
</a>
<p>The whiteout command underlays a white box under a
markup. The whitening effect only is only guaranteed for staff lines,
since staff lines are in a lower layer than most other grobs.
<p>
<a href="58/lily-a4c1cd85.ly">
<img align="middle"
border="0" src="58/lily-a4c1cd85.png" alt="[image of music]">
</a>
</p>
<!-- footer_tag -->
<div style="background-color: #e8ffe8; padding: 2; border: #c0ffc0 1px solid;">
<p>
<font size="-1">
This page is for LilyPond-2.11.57 (development-branch).
<br>
<address>
Report errors to <a href="http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs">http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs</a>. </address>
<br>
Your <a href="http://lilypond.org/web/devel/participating/documentation-adding">suggestions for the documentation</a> are welcome.
</font>
</p>
</div>
</BODY></html>
<!--
Local Variables:
coding: utf-8
End:
-->
