X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Flearning%2Ftweaks.itely;h=9f1c5dd0b5d43c52a8746e7dbfc0a561a4286e8e;hb=1ad6474dba041bd509d30fe13362b189f921ff27;hp=daeb0d4736037603ed067e90c9e7c0ee1e27657e;hpb=0945e7219a3995158d76267d26f77f57659c8578;p=lilypond.git diff --git a/Documentation/learning/tweaks.itely b/Documentation/learning/tweaks.itely index daeb0d4736..9f1c5dd0b5 100644 --- a/Documentation/learning/tweaks.itely +++ b/Documentation/learning/tweaks.itely @@ -8,7 +8,7 @@ Guide, node Updating translation committishes.. @end ignore -@c \version "2.12.0" +@c \version "2.14.0" @node Tweaking output @chapter Tweaking output @@ -219,7 +219,7 @@ we shall use just a few simple properties and values which are easily understood. For now, don't worry about the @code{#'}, which must precede the -layout property, and the @code{#}, which must precede the value. +layout property, and the@tie{}@code{#}, which must precede the value. These must always be present in exactly this form. This is the most common command used in tweaking, and most of the rest of this chapter will be directed to presenting examples of how it is @@ -562,7 +562,7 @@ should find Line thickness, generally measured in @code{line-thickness} @end example -This looks a good bet to change the heaviness. It tells us that +This looks a good bet to change the heaviness. It tells us that the value of @code{thickness} is a simple @emph{number}, that the default value is 1.2, and that the units are in another property called @code{line-thickness}. @@ -584,7 +584,7 @@ at first, so we can be sure the command is working. We get: @end example Don't forget the @code{#'} preceding the -property name and a @code{#} preceding the new value! +property name and a@tie{}@code{#} preceding the new value! The final question is, @q{Where should this command be placed?} While you are unsure and learning, the best @@ -923,7 +923,7 @@ to the front of these values when they are entered in the @tab A valid direction constant or its numerical equivalent (decimal values between -1 and 1 are allowed) @tab @code{LEFT}, @code{CENTER}, @code{UP}, - @code{1}, @code{-1} + @code{1}, @w{@code{-1}} @item Integer @tab A positive whole number @tab @code{3}, @code{1} @@ -942,7 +942,7 @@ make-moment function @code{(ly:make-moment 3 8)} @item Number @tab Any positive or negative decimal value - @tab @code{3.5}, @code{-2.45} + @tab @code{3.5}, @w{@code{-2.45}} @item Pair (of numbers) @tab Two numbers separated by a @q{space . space} and enclosed in brackets preceded by an apostrophe @@ -1090,7 +1090,7 @@ our example we want all bar lines to be suppressed, so the value we need is @code{'#(#f #f #f)}. Let's try that, remembering to include the @code{Staff} context. Note also that in writing this value we have @code{#'#} before the opening bracket. The @code{'#} is required -as part of the value to introduce a vector, and the first @code{#} is +as part of the value to introduce a vector, and the first@tie{}@code{#} is required, as always, to precede the value itself in the @code{\override} command. @@ -1632,7 +1632,7 @@ Then it sorts the outside-staff objects according to their @code{outside-staff-priority}. The outside-staff objects are taken one by one, beginning with the object with the lowest @code{outside-staff-priority}, and placed so that they do not -collide with any objects that have already been placed. That is, +collide with any objects that have already been placed. That is, if two outside-staff grobs are competing for the same space, the one with the lower @code{outside-staff-priority} will be placed closer to the staff. If two objects have the same @@ -1718,7 +1718,7 @@ a4 g c a | @end lilypond Here we use the constants @code{DOWN} and @code{UP}. -These have the values @code{-1} and @code{+1} respectively, and +These have the values @w{@code{-1}} and @code{+1} respectively, and these numerical values may be used instead. The value @code{0} may also be used in some cases. It is simply treated as meaning @code{UP} for stems, but for some objects it means @q{center}. @@ -1901,8 +1901,8 @@ Here are a few examples: @noindent If the fingering seems a little crowded the @code{font-size} could be reduced. The default value can be seen from the -@code{Fingering} object in the IR to be @code{-5}, so let's -try @code{-7}: +@code{Fingering} object in the IR to be @w{@code{-5}}, so let's +try @w{@code{-7}}: @lilypond[quote,fragment,ragged-right,verbatim,relative=1] \override Fingering #'font-size = #-7 @@ -1935,9 +1935,7 @@ The @code{outside-staff-priority} is defined in the By default it is set to @code{#f} for all within-staff objects, and to a numerical value appropriate to each outside-staff object when the object is created. The following table shows the default -numerical values for some of the commonest outside-staff objects -which are, by default, placed in the @code{Staff} or @code{Voice} -contexts. +numerical values for some of the commonest outside-staff objects. @cindex spanners @@ -1957,12 +1955,21 @@ linked hairpins and dynamics. @headitem Layout Object @tab Priority @tab Controls position of: -@item @code{MultiMeasureRestText} - @tab @code{450} - @tab Text over full-bar rests +@item @code{RehearsalMark} + @tab @code{1500} + @tab Rehearsal marks +@item @code{MetronomeMark} + @tab @code{1000} + @tab Metronome marks +@item @code{VoltaBracketSpanner} + @tab @code{600} + @tab Volta brackets @item @code{TextScript} @tab @code{450} @tab Markup text +@item @code{MultiMeasureRestText} + @tab @code{450} + @tab Markup text over full-bar rests @item @code{OttavaBracket} @tab @code{400} @tab Ottava brackets @@ -1972,9 +1979,9 @@ linked hairpins and dynamics. @item @code{DynamicLineSpanner} @tab @code{250} @tab All dynamic markings -@item @code{VoltaBracketSpanner} - @tab @code{100} - @tab Volta brackets +@item @code{BarNumber} + @tab @code{ 100} + @tab Bar numbers @item @code{TrillSpanner} @tab @code{50} @tab Spanning trills @@ -2032,25 +2039,6 @@ It also shows how ottava brackets are created. @cindex tweaking rehearsal mark placement @cindex rehearsal marks, tweaking placement -Note that bar numbers, metronome marks and rehearsal marks are not -shown. By default these are created in the @code{Score} context and -their @code{outside-staff-priority} is ignored relative to the layout -objects which are created in the @code{Staff} context. If you wish to -place bar numbers, metronome marks or rehearsal marks in accordance -with the value of their @code{outside-staff-priority} the -@code{Bar_number_engraver}, @code{Metronome_mark_engraver} or -@code{Mark_engraver} respectively should be removed from the -@code{Score} context and placed in the top @code{Staff} context. If -this is done, these marks will be given the following default -@code{outside-staff-priority} values: - -@multitable @columnfractions .3 .3 -@headitem Layout Object @tab Priority -@item @code{RehearsalMark} @tab @code{1500} -@item @code{MetronomeMark} @tab @code{1000} -@item @code{BarNumber} @tab @code{ 100} -@end multitable - If the default values of @code{outside-staff-priority} do not give you the placing you want, the priority of any of the objects may be overridden. Suppose we would like the ottava bracket to be placed @@ -2088,6 +2076,11 @@ c4\ff c \stopTextSpan | c,4 c c c | @end lilypond +Note that some of these objects, in particular bar numbers, +metronome marks and rehearsal marks, live by default in the +@code{Score} context, so be sure to use the correct context +when these are being overriden. + @cindex slurs and outside-staff-priority @cindex slurs and articulations @cindex articulations and slurs @@ -2429,11 +2422,11 @@ reference point. It may be used with all objects which support the @code{self-alignment-interface}. In general these are objects that contain text. The values are @code{LEFT}, @code{RIGHT} or @code{CENTER}. Alternatively, a numerical value between -@code{-1} and @code{+1} may be specified, where @code{-1} is +@w{@code{-1}} and @code{+1} may be specified, where @w{@code{-1}} is left-aligned, @code{+1} is right-aligned, and numbers in between move the text progressively from left-aligned to right-aligned. Numerical values greater than @code{1} may be specified to move -the text even further to the left, or less than @code{-1} to +the text even further to the left, or less than @w{@code{-1}} to move the text even further to the right. A change of @code{1} in the value corresponds to a movement of half the text's length. @@ -2518,7 +2511,7 @@ affecting anything else. @cindex positions property This is most useful for manually adjusting the slope and height -of beams, slurs, and tuplets. It takes a pair of numbers +of beams, slurs, and tuplets. It takes a pair of numbers giving the position of the left and right ends of the beam, slur, etc. relative to the center line of the staff. Units are staff-spaces. Note, though, that slurs and phrasing slurs cannot @@ -2716,7 +2709,7 @@ The best solution here is to move the multimeasure rest down, since the rest is in voice two. The default in @code{\voiceTwo} (i.e. in the second voice of a @code{<<@{...@} \\ @{...@}>>} construct) is that @code{staff-position} is set to -4 for MultiMeasureRest, so we need to -move it, say, four half-staff spaces down to @code{-8}. +move it, say, four half-staff spaces down to @w{@code{-8}}. @cindex MultiMeasureRest, example of overriding @cindex staff-position property, example @@ -2800,42 +2793,55 @@ r4 \acciaccatura e8\( d8 c~ c d c d\) @end lilypond -Here's a further example taken from the opening of the left-hand -staff of Chopin's Prelude Op 28 No. 2. We see that the beam -collides with the upper notes: +Here's a further example. We see that the beams +collide with the ties: @lilypond[quote,verbatim,fragment,ragged-right] { - \clef "bass" - << { b,8 ais, b, g, } \\ { e,8 g e, g } >> - << { b,8 ais, b, g, } \\ { e,8 g e, g } >> + \time 4/2 + << + { c'1 ~ c'2. e'8 f' } + \\ + { e''8 e'' e'' e'' e'' e'' e'' e'' f''2 g'' } + >> + << + { c'1 ~ c'2. e'8 f' } + \\ + { e''8 e'' e'' e'' e'' e'' e'' e'' f''2 g'' } + >> } @end lilypond @noindent This can be resolved by manually moving both ends of the beam -up from their position at 2 staff-spaces above the center line to, -say, 3: +up from their position at 1.81 staff-spaces below the center line to, +say, 1: @cindex Beam, example of overriding @cindex positions property, example @lilypond[quote,verbatim,fragment,ragged-right] { - \clef "bass" + \time 4/2 << - \override Beam #'positions = #'(3 . 3) - { b,8 ais, b, g, } - \\ - { e,8 g e, g } + { c'1 ~ c'2. e'8 f' } + \\ + { + \override Beam #'positions = #'(-1 . -1) + e''8 e'' e'' e'' e'' e'' e'' e'' f''2 g'' + } + >> + << + { c'1 ~ c'2. e'8 f' } + \\ + { e''8 e'' e'' e'' e'' e'' e'' e'' f''2 g'' } >> - << { b,8 ais, b, g, } \\ { e,8 g e, g } >> } @end lilypond @noindent Note that the override continues to apply in the first voice of -the second block of quavers, but not to any of the beams in the +the second measure of eighth notes, but not to any of the beams in the second voice. @subheading force-hshift property @@ -3184,7 +3190,7 @@ different voices together? This is where we need to turn again to the Notation Reference for help. A search for @qq{merge} in the Notation Reference index quickly leads us to the commands for merging differently headed and differently dotted notes in -@ruser{Collision resolution}. In our example we need to merge both +@ruser{Collision resolution}. In our example we need to merge both types of note for the duration of the polyphonic section in bar 3, so using the information we find in the Notation Reference we add @@ -3422,7 +3428,6 @@ lhMusic = \relative c' { * Using variables for tweaks:: * Style sheets:: * Other sources of information:: -* Avoiding tweaks with slower processing:: * Advanced tweaks with Scheme:: @end menu @@ -3556,6 +3561,10 @@ required, but the transparent metronome mark in the first line forces the following tempo indication too high while the second (with the stencil removed) does not. +@seealso +Music Glossary: +@rglos{system}. + @node Using variables for tweaks @subsection Using variables for tweaks @@ -3720,10 +3729,10 @@ inst = @end example We will refer to this file using the @code{\include} command near -the top of the music file. (The extension @code{.ily} is used to +the top of the music file. (The extension @file{.ily} is used to distinguish this included file, which is not meant to be compiled on its own, from the main file.) -Now let's modify our music (let's save this file as @file{"music.ly"}). +Now let's modify our music (let's save this file as @file{music.ly}). @c We have to do this awkward example/lilypond-non-verbatim @c because we can't do the \include stuff in the manual. @@ -3998,12 +4007,12 @@ being used: @item Linux Navigate to -@file{@var{INSTALLDIR}/lilypond/usr/share/lilypond/current/} +@file{@var{INSTALLDIR}/lilypond/usr/@/share/lilypond/current/} @item MacOS X Navigate to -@file{@var{INSTALLDIR}/LilyPond.app/Contents/Resources/share/lilypond/current/} +@file{@var{INSTALLDIR}/LilyPond.app/Contents/@/Resources/share/lilypond/current/} by either @code{cd}-ing into this directory from the Terminal, or control-clicking on the LilyPond application and selecting @q{Show Package Contents}. @@ -4011,7 +4020,7 @@ selecting @q{Show Package Contents}. @item Windows Using Windows Explorer, navigate to -@file{@var{INSTALLDIR}/LilyPond/usr/share/lilypond/current/} +@file{@var{INSTALLDIR}/LilyPond/usr/@/share/lilypond/current/} @end itemize @@ -4070,7 +4079,7 @@ The following are the most useful files to be found in @end multitable Other settings (such as the definitions of markup commands) are -stored as @code{.scm} (Scheme) files. The Scheme programming +stored as @file{.scm} (Scheme) files. The Scheme programming language is used to provide a programmable interface into LilyPond internal operation. Further explanation of these files is currently outside the scope of this manual, as a knowledge of @@ -4102,36 +4111,6 @@ interest are: @end multitable - -@node Avoiding tweaks with slower processing -@subsection Avoiding tweaks with slower processing - -LilyPond can perform extra checks while it processes input files. -These checks will take extra time to perform, but fewer manual tweaks -may be required to obtain an acceptable result. If a text script -or part of the lyrics extends over the margins these checks will -compress that line of the score just enough to fit within the -margins. - -To be effective under all circumstances these checks must be enabled -by placing the overrides in a Score @code{\with} block, rather than -in-line in music, as follows: - -@example -\new Score \with @{ - % Makes sure text scripts and lyrics are within the paper margins - \override PaperColumn #'keep-inside-line = ##t - \override NonMusicalPaperColumn #'keep-inside-line = ##t -@} @{ - .. -@} -@end example - -However, @code{keep-inside-line} is expensive and the recommendation -is to not enable it, to allow for faster processing, until creating -a final version. This way you do not need to manually add @code{\break} -commands to avoid text running off the right-hand side of the page. - @node Advanced tweaks with Scheme @subsection Advanced tweaks with Scheme