1
<html><head><title>LilyPond options</title><link rel="stylesheet" href="kde-default.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.67.2"><meta name="keywords" content="Rosegarden, sequencer, MIDI, audio, music, notation, score, KDE"><link rel="start" href="index.html" title="The Rosegarden Handbook"><link rel="up" href="file-operations.html" title="Chapter�2.�Rosegarden Files and Documents"><link rel="prev" href="file-printing.html" title="Printing"><link rel="next" href="segment-view.html" title="Chapter�3.�The Track Editor"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.13 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div style="background-image: url(top-middle.png); width: 100%; height: 131px;"><div style="position: absolute; right: 0px;"><img src="top-right-konqueror.png" style="margin: 0px" alt=""></div><div style="position: absolute; top: 25px; right: 100px; text-align: right; font-size: xx-large; font-weight: bold; text-shadow: #fff 0px 0px 5px; color: #444">LilyPond options</div></div><div style="margin-top: 20px; background-color: #white; color: black; margin-left: 20px; margin-right: 20px;"><div style="position: absolute; left: 20px;"><a accesskey="p" href="file-printing.html">Prev</a></div><div style="position: absolute; right: 20px;"><a accesskey="n" href="segment-view.html">Next</a></div><div class="navCenter">Rosegarden Files and Documents</div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lilypond-options"></a>LilyPond options</h2></div></div></div><p>If one of the LilyPond export functions is invoked, there will
2
appear a dialog in which options specific to LilyPond export may be
4
</p><div class="variablelist"><dl><dt><span class="term">LilyPond version</span></dt><dd><p>
5
LilyPond version installed into the system should be automatically
6
detected in the dialog, but it is possible to export to any other
7
LilyPond version since 2.6. Historically, LilyPond's syntax has
8
changed somewhat over time, but since LilyPond version 2.6 changes
9
have have been less radical and more maintainable.</p></dd><dt><span class="term">Paper size and Landscape</span></dt><dd><p>
10
Paper size can be A3, A4, A5, A6, Legal, US Letter, and Tabloid.
11
All paper sizes may also be used in Landscape mode.</p></dd><dt><span class="term">Font size</span></dt><dd><p>
12
Font size affects the size of the notes. If you want to fit more
13
staffs into the paper, you should decrease the font size.</p></dd><dt><span class="term">Export content</span></dt><dd><p>
14
Export content concerns tracks that have segments in them, which
15
are the tracks that are not empty.
16
It is possible to export All tracks, Non-muted tracks, the current
17
Selected track, or Selected segments. If LilyPond export is
18
launched from the Notation view, Selected segments include
19
the same selection which was used in opening the Notation view.</p></dd><dt><span class="term">Merge tracks that have the same name</span></dt><dd><p>
20
It is possible to Merge tracks that have the same name.
21
This options allows for example to make a piano score with
22
several independent voices. You may give first three tracks
23
name "Right" and three next tracks "Left" and then merge
24
them in LilyPond export. Sometimes you may encounter notes that
25
overlap in printed from, you may avoid them by selecting one
26
of the collapsing notes and fine adjust its position in
27
Notation view function
28
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenu">Adjust</span></span>-><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenuitem">Fine Positioning</span></span>-><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenuitem">Push Right/Left</span></span>.</p></dd><dt><span class="term">Export tempo marks</span></dt><dd><p>
29
Tempo marks are not exported by default. If tempo changes
30
rarely, you may want to export all tempo marks, but if
31
tempo changes too often, you may eport only the first mark.</p></dd><dt><span class="term">Export lyrics</span></dt><dd><p>
32
<a href="nv-text.html#nv-text-lyrics" title="Editing lyrics">Lyrics</a> is exported if this
33
option is checked. Text is entered in Unicode, which
34
makes it possible to enter lyrics in all languages. Multiple
35
lines of lyrics per staff is also possible, see the section
36
on <a href="nv-text.html#nv-text-lyrics" title="Editing lyrics">Editign lyrics</a>.</p></dd><dt><span class="term">Export beamings</span></dt><dd><p>
37
<a href="nv-beamed-groups.html" title="Beams">Beams</a> defined in
38
<span class="application">Rosegarden</span> can be exported, or the default
39
beam grouping of LilyPond can be used. Future versions
40
of <span class="application">Rosegarden</span> may support nested note grouping.</p></dd><dt><span class="term">Add staff group bracket</span></dt><dd><p>
41
Staff group bracket may be added to cover all staffs.
42
Future versions of <span class="application">Rosegarden</span> may support nested staff
43
groupings.</p></dd><dt><span class="term">Lyrics alignment</span></dt><dd><p>
44
Lyrics is aligned Left by default. Sometimes Center or
45
Right alignment provides results in more pleasant output.</p></dd><dt><span class="term">Ragged bottom</span></dt><dd><p>
46
The staff cover the whole page from the top to the bottom.
47
When there are only few staff, Ragged bottom places the
48
extra vertical space to the bottom of the page instead.</p></dd><dt><span class="term">Enable "point-and-click" debugging</span></dt><dd><p>
49
If you export the LilyPond source with the
50
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenu">File</span></span>-><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenuitem">Export</span></span>-><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenuitem">Export LilyPond</span></span>
51
function, you may open the LilyPond source by clicking
52
notes in the PDF output. Consult <a href="http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Point-and-click#Point-and-click" target="_top">LilyPond documentation</a> for more
54
</p></dd><dt><span class="term">Export \midi block</span></dt><dd><p>
55
LilyPond is capable to produce also MIDI output. Check this
56
option if you wish the LilyPond source to use this option.
57
Note however that MIDI output which you obtain via <span class="application">Rosegarden</span>
59
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenu">File</span></span>-><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenuitem">Export</span></span>-><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenuitem">Export MIDI file</span></span>,
60
and via LilyPond's MIDI output may differ.</p></dd><dt><span class="term">Headers</span></dt><dd><p>
61
Headers can be edited both in LilyPond export dialog and through the
62
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenu">Composition</span></span>-><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guimenuitem">Edit Document Properties</span></span> function.</p><p>Some of the headers will appear
63
only in LilyPond output.
64
The position of the Printable headers match roughly with
65
the positions of the headers in the printed output.
66
Below is shown an example with all headers and lyrics
67
entered with Unicode text.</p><p>
68
<div class="screenshot"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="headers-and-unicode-lyrics.png" alt="LilyPond's output showing all headers and Unicode lyrics."><hr></div></div>
69
</p></dd></dl></div></div><div style="background-color: #white; color: black; margin-top: 20px; margin-left: 20px; margin-right: 20px;"><div style="position: absolute; left: 20px;"><a accesskey="p" href="file-printing.html">Prev</a></div><div style="position: absolute; right: 20px;"><a accesskey="n" href="segment-view.html">Next</a></div><div align="center"><a accesskey="h" href="index.html">Home</a></div></div><div style="background-color: #white; color: black; margin-left: 20px; margin-right: 20px;"><div class="navLeft">Printing�</div><div class="navRight">�The Track Editor</div><div class="navCenter"><a accesskey="u" href="file-operations.html">Up</a></div></div><br><br><div class="bannerBottom" style="background-image: url(bottom-middle.png); background-repeat: x-repeat; width: 100%; height: 100px; bottom:0px;"><div class="BannerBottomRight"><img src="bottom-right.png" style="margin: 0px" alt=""></div><div class="bannerBottomLeft"><img src="bottom-left.png" style="margin: 0px;" alt=""></div><div id="comments" style="position:relative; top: 5px; left: 1em; height:85px; width: 50%; color: #cfe1f6"><p>Would you like to make a comment or contribute an update to this page?<br>
70
Send feedback to the <a href="mailto:kde-docs@kdemail.net" style="background:transparent; color:#cfe1f6; text-decoration: underline;">KDE Docs Team</a></p></div></div></body></html>
b'\\ No newline at end of file'
added
removed
docs/en/lilypond-options.html
