Differences

This shows you the differences between two versions of the page.

--- doc:manual-lilypondoptions-en [2009/10/29 21:01]
michael
+++ doc:manual-lilypondoptions-en [2010/09/23 02:25]
shelagh minor formatting
@@ Line 1: / Line 1: @@
 ====== LilyPond Options ======
-[screenshot]
+{{ http://rosegardenmusic.com/wiki/_media/doc:lilypond-options.png?w=400 }}
-If you use one of the LilyPond export functions, a dialog will appear in which options specific to LilyPond export may be altered.
+This dialog appears when you select **File -> Print**, **File -> Print Preview** and **File -> Export -> Export LilyPond File**.  It allows you to alter options specific to LilyPond export.  (When using the **Print** or **Print Preview** options, your work is exported to a hidden temporary file.  As of Rosegarden Thorn, LilyPond is the only available print engine.)
-=== LilyPond version ===
+==== Basic Options ====
+=== Export content ===
+Export content concerns tracks that have segments in them, which are the tracks that are not empty. It is possible to export “All” tracks, “Non-muted” tracks, the current “Selected” track, or “Selected” segments. If LilyPond export is launched from the Notation view, Selected segments include the same selection which was used in opening the Notation view.
+=== Compatibility level ===
+The LilyPond version installed on the system should be automatically detected in the dialog, but it is possible to export to any other LilyPond version from 2.6 up to the most recent version supported. Historically, LilyPond's syntax has changed somewhat over time, but since LilyPond version 2.6 changes have have been less radical and more maintainable.
-The LilyPond version installed on the system should be automatically detected in the dialog, but it is possible to export to any other LilyPond version since 2.6. Historically, LilyPond's syntax has changed somewhat over time, but since LilyPond version 2.6 changes have have been less radical and more maintainable.
+//TIP:  Occasionally we will fail to catch a change in LilyPond syntax.  When this happens, it may be useful to choose an older version than the one installed on your system.  If you are using **Print** or **Print Preview**, the processing engine will run the **convert-ly** utility automatically, and that will usually take care of this sort of problem.//
 === Paper size and Landscape ===
 Paper size can be A3, A4, A5, A6, Legal, US Letter, and Tabloid. All paper sizes may also be used in Landscape mode.
-=== Font size ===
+=== Staff size ===
+Staff size affects the size of the notes. If you want to fit more staffs into the paper, you should decrease the staff size.
+Certain sizes are marked with an asterisk (''*'').  These are suggested as being the best sizes to use for optimum output quality, although with recent versions of LilyPond it does not seem to matter which sizes you choose.
-Font size affects the size of the notes. If you want to fit more staffs into the paper, you should decrease the font size.
+==== Specific options ====
-=== Export content ===
-Export content concerns tracks that have segments in them, which are the tracks that are not empty. It is possible to export “All” tracks, “Non-muted” tracks, the current “Selected” track, or “Selected” segments. If LilyPond export is launched from the Notation view, Selected segments include the same selection which was used in opening the Notation view.
-=== Merge tracks that have the same name ===
-<del>It is possible to Merge tracks that have the same name. This options allows for example to make a piano score with several independent voices. You may give first three tracks name “Right” and three next tracks “Left” and then merge them in LilyPond export. (This provides an easier way to manage overlapping segments with the price that the top and bottom parts will have different names on the page. If you wish both of them to be named, eg. “Piano,” then you will have to keep all of the segments on the same pair of staffs. Consult [[http://rosegarden.sourceforge.net/tutorial/supplemental/piano/|Piano by Example]] for a hands-on demonstration of this.) Adjust → Fine Positioning → Push Right/Left.</del>
 === Export tempo marks ===
+Tempo marks are not exported by default.  If selected, LilyPond will print a tempo mark {{http://rosegardenmusic.com/wiki/_media/doc:tempo-mark.png?w=50}} for the **First** tempo change, or for **All** tempo changes.   If tempo changes rarely, you may want to export all tempo marks, but if tempo changes too often, the marks will jumble together and be illegible, so you may want to export only the first mark in that case.
+//NOTE: Tempo marks may conflict with notation.  There is not currently any way to improve the positioning of the tempo marks, and this would require hand editing an exported **.ly** file.//
-Tempo marks are not exported by default. If tempo changes rarely, you may want to export all tempo marks, but if tempo changes too often, you may export only the first mark.
 === Export lyrics ===
+Lyrics are exported if present.  Lyrics are aligned left by default. Sometimes center or right alignment provide more pleasing output.
-[[/#nv-text-lyrics|Lyrics]] is exported if this option is checked. Text is entered in Unicode, which makes it possible to enter lyrics in all languages. Multiple lines of lyrics per staff is also possible, see the section on [[/#nv-text-lyrics|Editing lyrics]].
 === Export beamings ===
+If selected, Rosegarden's own [[doc:notation-en#beams|beams]] will be exported, otherwise LilyPond will be left to calculate beams automatically.  In general, Rosegarden's automatic beaming is terrible, so it may be quicker to leave that alone and rely on LilyPond to clean up the mess.  However, if you have gone to some trouble to specify your own beaming, you probably want to try this option.  It generally works, but exporting beams can lead to export problems, because it makes the LilyPond syntax much more messy and prone to conflicts.
+=== Export track staff brackets ===
+If checked, track staff brackets will be exported.  These are configured through [[doc:manual-en#the_track_parameter_box|Track Parameters]] and provide a crude mechanism for grouping parts on a score.
-[[/#nv-beamed-groups|Beams]] defined in Rosegarden can be exported, or the default beam grouping of LilyPond can be used. Future versions of Rosegarden may support nested note grouping.
+[EXPAND.  LINK TO WIKI-IZED FIDELIO TUTORIAL] FIXME
-=== Lyrics alignment ===
+=== Export chord texts as lead sheet chord names ===
+[EXPAND. LINK TO WIKI-IZED VERSION OF SHELAGH'S TUTORIAL] FIXME
-Lyrics are aligned left by default. Sometimes center or right alignment provide more pleasing output.
 === Ragged bottom ===
 The staffs normally cover the whole page from top to bottom. When there are only a few staffs, this option places the extra vertical space at the bottom of the page.
-=== Export \midi block ===
+=== Export markers ===
+FIXME
-DEPRECATED?  I think so:
+==== Headers ====
-<del>LilyPond is also capable of producing MIDI output. Check this option if you wish the LilyPond source to use this option. Note however that MIDI output which you obtain with Rosegarden sequencer, via File → Export → Export MIDI file, and LilyPond's MIDI output may differ considerably.</del>
+You can edit headers both in LilyPond export dialog and through **Composition → Edit Document Properties**.
-=== Headers ===
-You can edit headers both in LilyPond export dialog and through Composition → Edit Document Properties.
 Some of the headers will appear only in LilyPond output. The position of the printable headers match roughly with the positions of the headers in the printed output. Below is shown an example with all headers and lyrics entered with Unicode text.
+FIXME
 {{http://rosegardenmusic.com/wiki/headers-and-unicode-lyrics.png|LilyPond's output showing all headers and Unicode lyrics.}}
-\\
-----
-<sup>[[[/#id590926|1]]] </sup> Many users have complained about our opaque binary file format. It is, in fact, nothing more than gzipped XML.