X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fnl%2Flearning%2Ftweaks.itely;h=51bac2fbc28882dc581e37519f7e8831255eb0ba;hb=09ef86c87175cc6c1071eedb022ed1d01a93bcaf;hp=a97b9cde425d46520c58fd5b596f29288dd8220d;hpb=a94d26b6693cad58b946a01b7efaaed29480f063;p=lilypond.git diff --git a/Documentation/nl/learning/tweaks.itely b/Documentation/nl/learning/tweaks.itely index a97b9cde42..51bac2fbc2 100644 --- a/Documentation/nl/learning/tweaks.itely +++ b/Documentation/nl/learning/tweaks.itely @@ -8,7 +8,7 @@ Guide, node Updating translation committishes.. @end ignore -@c \version "2.19.21" +@c \version "2.19.22" @node Tweaking output @chapter Tweaking output @@ -187,7 +187,6 @@ the types of objects and properties from their names. @cindex override syntax @funindex \override -@funindex override We have already met the commands @code{\set} and @code{\with}, used to change the properties of @strong{contexts} and to remove and add @@ -243,12 +242,14 @@ color of the note head: @cindex color property, example @cindex NoteHead, example of overriding -@lilypond[quote,fragment,ragged-right,verbatim,relative=1] -c4 d -\override NoteHead.color = #red -e4 f | -\override NoteHead.color = #green -g4 a b c | +@lilypond[quote,ragged-right,verbatim] +\relative { + c'4 d + \override NoteHead.color = #red + e4 f | + \override NoteHead.color = #green + g4 a b c | +} @end lilypond @@ -258,7 +259,6 @@ g4 a b c | @cindex revert command @funindex \revert -@funindex revert Once overridden, the property retains its new value until it is overridden again or a @code{\revert} command is encountered. @@ -279,14 +279,16 @@ of the note head to the default value for the final two notes: @cindex color property, example @cindex NoteHead, example of overriding -@lilypond[quote,fragment,ragged-right,verbatim,relative=1] -c4 d -\override NoteHead.color = #red -e4 f | -\override NoteHead.color = #green -g4 a -\revert NoteHead.color -b4 c | +@lilypond[quote,ragged-right,verbatim] +\relative { + c'4 d + \override NoteHead.color = #red + e4 f | + \override NoteHead.color = #green + g4 a + \revert NoteHead.color + b4 c | +} @end lilypond @@ -294,7 +296,6 @@ b4 c | @unnumberedsubsubsec The @code{\once} prefix @funindex \once -@funindex once Both the @code{\override} and the @code{\set} commands may be prefixed by @code{\once}. This causes the following @code{\override} or @@ -324,7 +325,6 @@ b c | @cindex overrideProperty command @funindex \overrideProperty -@funindex overrideProperty There is another form of the override command, @code{\overrideProperty}, which is occasionally required. @@ -339,7 +339,6 @@ We mention it here for completeness, but for details see @cindex tweak command @funindex \tweak -@funindex tweak The final tweaking command which is available is @code{\tweak}. This should be used when several objects occur at the same musical moment, @@ -355,11 +354,13 @@ middle note head (the E) in a C major chord. Let's first see what @cindex font-size property, example @cindex NoteHead, example of overriding -@lilypond[quote,fragment,ragged-right,verbatim,relative=1] -4 -\once \override NoteHead.font-size = #-3 -4 -4 +@lilypond[quote,ragged-right,verbatim] +\relative { + 4 + \once \override NoteHead.font-size = #-3 + 4 + 4 +} @end lilypond We see the override affects @emph{all} the note heads in the chord. @@ -380,9 +381,11 @@ a chord would be changed in this way: @cindex font-size property, example @cindex @code{\tweak}, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=1] -4 -4 +@lilypond[quote,ragged-right,verbatim] +\relative { + 4 + 4 +} @end lilypond Note that the syntax of @code{\tweak} is different from that of the @@ -402,8 +405,8 @@ a series of articulations, as shown here: @cindex color property, example @cindex @code{\tweak}, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -a4^"Black" +@lilypond[quote,fragment,ragged-right,verbatim] +a'4^"Black" -\tweak color #red ^"Red" -\tweak color #green _"Green" @end lilypond @@ -423,10 +426,10 @@ directly from the following event. It is still possible to use the layout object, provided that LilyPond can trace its origin back to the original event: -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -<\tweak Accidental.color #red cis4 - \tweak Accidental.color #green es - g> +@lilypond[quote,fragment,ragged-right,verbatim] +<\tweak Accidental.color #red cis''4 + \tweak Accidental.color #green es'' + g''> @end lilypond This long form of the @code{\tweak} command can be described as @@ -459,13 +462,15 @@ printed in red on the first short tuplet bracket. @cindex direction property, example @cindex color property, example -@lilypond[quote,ragged-right,verbatim,fragment,relative=2] -\tweak direction #up -\tuplet 3/4 { - \tweak color #red - \tuplet 3/2 { c8[ c c] } - \tuplet 3/2 { c8[ c c] } - \tuplet 3/2 { c8[ c c] } +@lilypond[quote,ragged-right,verbatim] +\relative c'' { + \tweak direction #up + \tuplet 3/4 { + \tweak color #red + \tuplet 3/2 { c8[ c c] } + \tuplet 3/2 { c8[ c c] } + \tuplet 3/2 { c8[ c c] } + } } @end lilypond @@ -478,15 +483,17 @@ appearance may be modified in the usual way with @cindex transparent property, example @cindex TupletNumber, example of overriding -@lilypond[quote,ragged-right,verbatim,fragment,relative=1] -\tuplet 3/2 { c8[ c c] } -\once \override TupletNumber.text = #tuplet-number::calc-fraction-text -\tuplet 3/2 { - c8[ c] - c8[ c] - \once \override TupletNumber.transparent = ##t - \tuplet 3/2 { c8[ c c] } - \tuplet 3/2 { c8[ c c] } +@lilypond[quote,ragged-right,verbatim] +\relative { + \tuplet 3/2 { c'8[ c c] } + \once \override TupletNumber.text = #tuplet-number::calc-fraction-text + \tuplet 3/2 { + c8[ c] + c8[ c] + \once \override TupletNumber.transparent = ##t + \tuplet 3/2 { c8[ c c] } + \tuplet 3/2 { c8[ c c] } + } } @end lilypond @@ -545,12 +552,12 @@ music: @c Mozart, Die Zauberflöte Nr.7 Duett -@lilypond[quote,verbatim,relative=2] +@lilypond[quote,verbatim] { \key es \major \time 6/8 - { - r4 bes8 bes[( g]) g | + \relative { + r4 bes'8 bes[( g]) g | g8[( es]) es d[( f]) as | as8 g } @@ -630,14 +637,14 @@ close to it.} Let's do that: @cindex Slur example of overriding @cindex thickness property, example -@lilypond[quote,verbatim,relative=2] +@lilypond[quote,verbatim] { \key es \major \time 6/8 - { + \relative { % Increase thickness of all following slurs from 1.2 to 5.0 \override Slur.thickness = #5.0 - r4 bes8 bes[( g]) g | + r4 bes'8 bes[( g]) g | g8[( es]) es d[( f]) as | as8 g } @@ -684,7 +691,6 @@ location. @cindex once override @funindex \once -@funindex once As you can see, @emph{all} the slurs are thicker in the final example above. But what if we wanted just the first slur to be thicker? This @@ -699,12 +705,12 @@ repositioned as follows: @cindex Slur, example of overriding @cindex thickness property, example -@lilypond[quote,verbatim,relative=2] +@lilypond[quote,verbatim] { \key es \major \time 6/8 - { - r4 bes8 + \relative { + r4 bes'8 % Increase thickness of immediately following slur only \once \override Slur.thickness = #5.0 bes8[( g]) g | @@ -729,7 +735,6 @@ command. @cindex default properties, reverting to @funindex \revert -@funindex revert Finally, what if we wanted just the first two slurs to be heavier? Well, we could use two commands, each preceded by @@ -739,12 +744,12 @@ the slurs begin: @cindex Slur, example of overriding @cindex thickness property, example -@lilypond[quote,verbatim,relative=2] +@lilypond[quote,verbatim] { \key es \major \time 6/8 - { - r4 bes8 + \relative { + r4 bes'8 % Increase thickness of immediately following slur only \once \override Slur.thickness = #5.0 bes[( g]) g | @@ -767,12 +772,12 @@ after the second slur: @cindex Slur, example of overriding @cindex thickness property, example -@lilypond[quote,verbatim,relative=2] +@lilypond[quote,verbatim] { \key es \major \time 6/8 - { - r4 bes8 + \relative { + r4 bes'8 % Increase thickness of all following slurs from 1.2 to 5.0 \override Slur.thickness = #5.0 bes[( g]) g | @@ -874,12 +879,12 @@ like so: @cindex LyricText, example of overriding @cindex @code{\addlyrics}, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] +@lilypond[quote,ragged-right,verbatim] { \key es \major \time 6/8 - { - r4 bes8 bes[( g]) g | + \relative { + r4 bes'8 bes[( g]) g | g8[( es]) es d[( f]) as | as8 g } @@ -1044,11 +1049,11 @@ the implied Context, @code{Voice}: @cindex BarLine, example of overriding @cindex stencil property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \override BarLine.stencil = ##f - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1069,11 +1074,11 @@ it by adding the correct context: @cindex BarLine, example of overriding @cindex stencil property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \override Staff.BarLine.stencil = ##f - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1084,11 +1089,11 @@ property to @code{#f} is such a frequent operation that there is a shorthand for it called @code{\omit}: @funindex \omit -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \omit Staff.BarLine - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1102,9 +1107,9 @@ correct processing. For example, errors will be generated if the @code{point-stencil} function, which sets the stencil to an object with zero size: -@lilypond[quote,verbatim,relative=2] -{ - c4 c +@lilypond[quote,verbatim] +\relative { + c''4 c \once \override NoteHead.stencil = #point-stencil c4 c } @@ -1131,11 +1136,11 @@ required, as always, to precede the value itself in the @cindex BarLine, example of overriding @cindex break-visibility property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \override Staff.BarLine.break-visibility = ##(#f #f #f) - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1164,11 +1169,11 @@ transparent is: @cindex TimeSignature, example of overriding @cindex transparent property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \override Staff.TimeSignature.transparent = ##t - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1180,11 +1185,11 @@ frequent operation, so we have a shorthand for it called @code{\hide}: @funindex \hide -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \hide Staff.TimeSignature - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1202,11 +1207,11 @@ instead: @cindex TimeSignature, example of overriding @cindex stencil property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \omit Staff.TimeSignature - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1246,11 +1251,11 @@ we write: @cindex BarLine, example of overriding @cindex color property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \override Staff.BarLine.color = #white - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1280,11 +1285,11 @@ converts X11 color symbols into the list of internal values like this: @cindex BarLine, example of overriding @cindex color property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \override Staff.BarLine.color = #(x11-color 'white) - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1311,11 +1316,11 @@ and to white it should be @code{(rgb-color 1 1 1)}: @cindex BarLine, example of overriding @cindex color property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \override Staff.BarLine.color = #(rgb-color 1 1 1) - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1336,8 +1341,8 @@ various shades of grey: @cindex color property, example @cindex x11-color, example of using -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -{ +@lilypond[quote,ragged-right,verbatim] +\relative { \time 12/16 \override Staff.StaffSymbol.color = #(x11-color 'grey30) \override Staff.TimeSignature.color = #(x11-color 'grey60) @@ -1345,7 +1350,7 @@ various shades of grey: \override Voice.NoteHead.color = #(x11-color 'grey85) \override Voice.Stem.color = #(x11-color 'grey85) \override Staff.BarLine.color = #(x11-color 'grey10) - c4 b8 c d16 c d8 | + c''4 b8 c d16 c d8 | g,8 a16 b8 c d4 e16 | e8 } @@ -1377,7 +1382,7 @@ how to introduce a new temporary staff, as in an @rglos{ossia}. @cindex alignAboveContext property, example @cindex @code{\with}, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] +@lilypond[quote,ragged-right,verbatim] \new Staff ="main" { \relative { r4 g'8 g c4 c8 d | @@ -1404,7 +1409,7 @@ we simply set the stencil of each to @code{#f}, as follows: @cindex Clef, example of overriding @cindex TimeSignature, example of overriding -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] +@lilypond[quote,ragged-right,verbatim] \new Staff ="main" { \relative { r4 g'8 g c4 c8 d | @@ -1467,7 +1472,7 @@ So we could replace the example above with @cindex Clef, example of overriding @cindex TimeSignature, example of overriding -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] +@lilypond[quote,ragged-right,verbatim] \new Staff ="main" { \relative { r4 g'8 g c4 c8 d | @@ -1492,7 +1497,7 @@ It turns out that we can also employ the shorthands @code{\hide} and @code{\omit} for setting the @code{transparent} property and clearing the @code{stencil} here, leading to the result -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] +@lilypond[quote,ragged-right,verbatim] \new Staff ="main" { \relative { r4 g'8 g c4 c8 d | @@ -1556,7 +1561,7 @@ Let's try it in our ossia example: @cindex TimeSignature, example of overriding @cindex fontSize property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] +@lilypond[quote,ragged-right,verbatim] \new Staff ="main" { \relative { r4 g'8 g c4 c8 d | @@ -1622,7 +1627,7 @@ objects in proportion. It is used like this: @cindex staff-space property, example @cindex stencil property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] +@lilypond[quote,ragged-right,verbatim] \new Staff ="main" { \relative { r4 g'8 g c4 c8 d | @@ -1729,11 +1734,11 @@ under @q{Text2}. @cindex markup example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -c2^"Text1" -c2^"Text2" | -c2^"Text3" -c2^"Text4" | +@lilypond[quote,fragment,ragged-right,verbatim] +c''2^"Text1" +c''2^"Text2" | +c''2^"Text3" +c''2^"Text4" | @end lilypond Staves are also positioned, by default, as closely together as @@ -1889,12 +1894,14 @@ specifying @code{DOWN} and @code{UP}: @cindex Fingering, example of overriding @cindex direction property, example -@lilypond[quote,verbatim,relative=2] -c4-5 a-3 f-1 c'-5 | -\override Fingering.direction = #DOWN -c4-5 a-3 f-1 c'-5 | -\override Fingering.direction = #UP -c4-5 a-3 f-1 c'-5 | +@lilypond[quote,verbatim] +\relative { + c''4-5 a-3 f-1 c'-5 | + \override Fingering.direction = #DOWN + c4-5 a-3 f-1 c'-5 | + \override Fingering.direction = #UP + c4-5 a-3 f-1 c'-5 | +} @end lilypond However, overriding the @code{direction} property is not the @@ -1905,10 +1912,12 @@ example using this method: @cindex fingering example -@lilypond[quote,verbatim,relative=2] -c4-5 a-3 f-1 c'-5 | -c4_5 a_3 f_1 c'_5 | -c4^5 a^3 f^1 c'^5 | +@lilypond[quote,verbatim] +\relative { + c''4-5 a-3 f-1 c'-5 | + c4_5 a_3 f_1 c'_5 | + c4^5 a^3 f^1 c'^5 | +} @end lilypond The @code{direction} property is ignored for chords, but the @@ -1918,10 +1927,12 @@ notes of a chord, as shown: @cindex fingering example -@lilypond[quote,verbatim,relative=2] -4 -4 -4 +@lilypond[quote,verbatim] +\relative { + 4 + 4 + 4 +} @end lilypond @noindent @@ -1930,10 +1941,12 @@ individual fingering numbers above or below: @cindex fingering example -@lilypond[quote,verbatim,relative=2] -4 -4 -4 +@lilypond[quote,verbatim] +\relative { + 4 + 4 + 4 +} @end lilypond Even greater control over the placement of fingering of the @@ -1971,22 +1984,24 @@ Here are a few examples: @cindex @code{\set}, example of using @cindex fingeringOrientations property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=1] -\set fingeringOrientations = #'(left) -4 -4 -\set fingeringOrientations = #'(left) -4 -4 | -\set fingeringOrientations = #'(up left down) -4 -4 -\set fingeringOrientations = #'(up left) -4 -4 | -\set fingeringOrientations = #'(right) -4 -4 +@lilypond[quote,ragged-right,verbatim] +\relative { + \set fingeringOrientations = #'(left) + 4 + 4 + \set fingeringOrientations = #'(left) + 4 + 4 | + \set fingeringOrientations = #'(up left down) + 4 + 4 + \set fingeringOrientations = #'(up left) + 4 + 4 | + \set fingeringOrientations = #'(right) + 4 + 4 +} @end lilypond @noindent @@ -1995,23 +2010,25 @@ could be reduced. The default value can be seen from the @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 -\set fingeringOrientations = #'(left) -4 -4 -\set fingeringOrientations = #'(left) -4 -4 | -\set fingeringOrientations = #'(up left down) -4 -4 -\set fingeringOrientations = #'(up left) -4 -4 | -\set fingeringOrientations = #'(right) -4 -4 +@lilypond[quote,ragged-right,verbatim] +\relative { + \override Fingering.font-size = #-7 + \set fingeringOrientations = #'(left) + 4 + 4 + \set fingeringOrientations = #'(left) + 4 + 4 | + \set fingeringOrientations = #'(up left down) + 4 + 4 + \set fingeringOrientations = #'(up left) + 4 + 4 | + \set fingeringOrientations = #'(right) + 4 + 4 +} @end lilypond @node Outside-staff objects @@ -2099,14 +2116,12 @@ these. @cindex ottava bracket @funindex \startTextSpan -@funindex startTextSpan @funindex \stopTextSpan -@funindex stopTextSpan @cindex TextSpanner, example of overriding @cindex bound-details property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=1] +@lilypond[quote,fragment,ragged-right,verbatim] % Set details for later Text Spanner \override TextSpanner.bound-details.left.text = \markup { \small \bold Slower } @@ -2114,18 +2129,18 @@ these. \dynamicUp % Start Ottava Bracket \ottava #1 -c'4 \startTextSpan +c''4 \startTextSpan % Add Dynamic Text and hairpin -c4\pp\< -c4 +c''4\pp\< +c''4 % Add Text Script -c4^Text | -c4 c +c''4^Text | +c''4 c'' % Add Dynamic Text and terminate hairpin -c4\ff c \stopTextSpan | +c''4\ff c'' \stopTextSpan | % Stop Ottava Bracket \ottava #0 -c,4 c c c | +c'4 c' c' c' | @end lilypond This example also shows how to create Text Spanners -- @@ -2156,7 +2171,7 @@ in the @code{Staff} context: @cindex TextSpanner, example of overriding @cindex bound-details property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=1] +@lilypond[quote,fragment,ragged-right,verbatim] % Set details for later Text Spanner \override TextSpanner.bound-details.left.text = \markup { \small \bold Slower } @@ -2166,19 +2181,19 @@ in the @code{Staff} context: \once \override Staff.OttavaBracket.outside-staff-priority = #340 % Start Ottava Bracket \ottava #1 -c'4 \startTextSpan +c''4 \startTextSpan % Add Dynamic Text -c4\pp +c''4\pp % Add Dynamic Line Spanner -c4\< +c''4\< % Add Text Script -c4^Text | -c4 c +c''4^Text | +c''4 c'' % Add Dynamic Text -c4\ff c \stopTextSpan | +c''4\ff c'' \stopTextSpan | % Stop Ottava Bracket \ottava #0 -c,4 c c c | +c'4 c' c' c' | @end lilypond Note that some of these objects, in particular bar numbers, @@ -2203,14 +2218,16 @@ can be set to a numerical value to cause it to be placed along with other outside-staff objects according to that value. Here's an example showing the effect of the two methods: -@lilypond[quote,verbatim,relative=2] -c4( c^\markup { \tiny \sharp } d4.) c8 | -c4( -\once \override TextScript.avoid-slur = #'inside -\once \override TextScript.outside-staff-priority = ##f -c4^\markup { \tiny \sharp } d4.) c8 | -\once \override Slur.outside-staff-priority = #500 -c4( c^\markup { \tiny \sharp } d4.) c8 | +@lilypond[quote,verbatim] +\relative c'' { + c4( c^\markup { \tiny \sharp } d4.) c8 | + c4( + \once \override TextScript.avoid-slur = #'inside + \once \override TextScript.outside-staff-priority = ##f + c4^\markup { \tiny \sharp } d4.) c8 | + \once \override Slur.outside-staff-priority = #500 + c4( c^\markup { \tiny \sharp } d4.) c8 | +} @end lilypond Changing the @code{outside-staff-priority} can also be used to @@ -2225,12 +2242,12 @@ in the IR or in the tables above, and increase the priority of @cindex TextScript, example of overriding @cindex outside-staff-priority property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -c2^"Text1" -c2^"Text2" | +@lilypond[quote,fragment,ragged-right,verbatim] +c''2^"Text1" +c''2^"Text2" | \once \override TextScript.outside-staff-priority = #500 -c2^"Text3" -c2^"Text4" | +c''2^"Text3" +c''2^"Text4" | @end lilypond This certainly lifts @qq{Text3} above @qq{Text4} but it also lifts it @@ -2247,21 +2264,19 @@ command. @cindex notes, spreading out with text @funindex \textLengthOn -@funindex textLengthOn @funindex \textLengthOff -@funindex textLengthOff By default, text produced by markup takes up no horizontal space as far as laying out the music is concerned. The @code{\textLengthOn} command reverses this behavior, causing the notes to be spaced out as far as is necessary to accommodate the text: -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] +@lilypond[quote,fragment,ragged-right,verbatim] \textLengthOn % Cause notes to space out to accommodate text -c2^"Text1" -c2^"Text2" | -c2^"Text3" -c2^"Text4" | +c''2^"Text1" +c''2^"Text2" | +c''2^"Text3" +c''2^"Text4" | @end lilypond The command to revert to the default behavior is @@ -2279,25 +2294,27 @@ example to show how markup text interacts with such notes. @cindex TextScript, example of overriding @cindex outside-staff-priority property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=2] -% This markup is short enough to fit without collision -c2^"Tex" c'' | -R1 | - -% This is too long to fit, so it is displaced upwards -c,,2^"Text" c'' | -R1 | - -% Turn off collision avoidance -\once \override TextScript.outside-staff-priority = ##f -c,,2^"Long Text " c'' | -R1 | - -% Turn off collision avoidance -\once \override TextScript.outside-staff-priority = ##f -\textLengthOn % and turn on textLengthOn -c,,2^"Long Text " % Spaces at end are honored -c''2 | +@lilypond[quote,ragged-right,verbatim] +\relative { + % This markup is short enough to fit without collision + c''2^"Tex" c'' | + R1 | + + % This is too long to fit, so it is displaced upwards + c,,2^"Text" c'' | + R1 | + + % Turn off collision avoidance + \once \override TextScript.outside-staff-priority = ##f + c,,2^"Long Text " c'' | + R1 | + + % Turn off collision avoidance + \once \override TextScript.outside-staff-priority = ##f + \textLengthOn % and turn on textLengthOn + c,,2^"Long Text " % Spaces at end are honored + c''2 | +} @end lilypond @node Dynamics placement @@ -2314,13 +2331,15 @@ all within-staff objects such as phrasing slurs and bar numbers. This can give quite acceptable results, as this example shows: -@lilypond[quote,fragment,ragged-right,verbatim,relative=1] -\clef "bass" -\key aes \major -\time 9/8 -\dynamicUp -bes4.~\f\< \( bes4 bes8 des4\ff\> c16 bes\! | -ees,2.~\)\mf ees4 r8 | +@lilypond[quote,ragged-right,verbatim] +\relative { + \clef "bass" + \key aes \major + \time 9/8 + \dynamicUp + bes4.~\f\< \( bes4 bes8 des4\ff\> c16 bes\! | + ees,2.~\)\mf ees4 r8 | +} @end lilypond However, if the notes and attached dynamics are close @@ -2686,8 +2705,8 @@ above or below notes. @cindex Script, example of overriding @cindex padding property, example -@lilypond[quote,fragment,relative=1,verbatim] -c2\fermata +@lilypond[quote,fragment,verbatim] +c'2\fermata \override Script.padding = #3 b2\fermata @end lilypond @@ -2695,15 +2714,15 @@ b2\fermata @cindex MetronomeMark, example of overriding @cindex padding property, example -@lilypond[quote,fragment,relative=1,verbatim] +@lilypond[quote,fragment,verbatim] % This will not work, see below \override MetronomeMark.padding = #3 \tempo 4 = 120 -c1 | +c'1 | % This works \override Score.MetronomeMark.padding = #3 \tempo 4 = 80 -d1 | +d'1 | @end lilypond Note in the second example how important it is to figure out what @@ -2802,11 +2821,11 @@ right edge with the reference point of the parent note: @cindex StringNumber, example of overriding @cindex self-alignment-X property, example -@lilypond[quote,fragment,ragged-right,verbatim,relative=3] +@lilypond[quote,fragment,ragged-right,verbatim] \voiceOne - + \once \override StringNumber.self-alignment-X = #RIGHT - + @end lilypond @node The staff-position property @@ -2822,8 +2841,8 @@ handling between notes and between notes and rests is done only for notes and rests that occur at the same time. Here's an example of a collision of this type: -@lilypond[quote,verbatim,fragment,ragged-right, relative=1] -<< { c4 c c c } \\ { R1 } >> +@lilypond[quote,verbatim,ragged-right] +<< \relative { c'4 c c c } \\ { R1 } >> @end lilypond The best solution here is to move the multimeasure rest down, since @@ -2835,9 +2854,9 @@ move it, say, four half-staff spaces down to @w{@code{-8}}. @cindex MultiMeasureRest, example of overriding @cindex staff-position property, example -@lilypond[quote,verbatim,fragment,ragged-right, relative=1] +@lilypond[quote,verbatim,ragged-right] << - { c4 c c c } + \relative { c'4 c c c } \\ \override MultiMeasureRest.staff-position = #-8 { R1 } @@ -2888,8 +2907,8 @@ manually. Here's an example in which the phrasing slur and slur collide: -@lilypond[quote,verbatim,fragment,ragged-right,relative=2] -a8 \( ( a'16 ) a \) +@lilypond[quote,verbatim,ragged-right] +\relative { a'8 \( ( a'16 ) a \) } @end lilypond @cindex PhrasingSlur, example of overriding @@ -2902,9 +2921,9 @@ centre line and the right end to 4.5 above, and LilyPond will select the phrasing slur from the candidates it has found with its end points closest to these: -@lilypond[quote,verbatim,fragment,ragged-right,relative=2] +@lilypond[quote,verbatim,fragment,ragged-right] \once \override PhrasingSlur.positions = #'(2.5 . 4.5) -a8 \( ( a'16 ) a \) +a'8 \( ( a''16 ) a'' \) @end lilypond This is an improvement, but why not lower the right end of the slur @@ -3586,8 +3605,8 @@ different voices using ties. Normally, only two notes in the same voice can be connected with ties. By using two voices, with the tied notes in one of them -@lilypond[quote,fragment,relative=2] -<< { b8~ 8\noBeam } \\ { b8[ g] } >> +@lilypond[quote] +<< { b'8~ 8\noBeam } \\ { b'8[ g'] } >> @end lilypond @noindent @@ -3849,7 +3868,7 @@ mpdolce = inst = #(define-music-function - (parser location string) + (string) (string?) #{ <>^\markup \bold \box #string #}) @@ -3882,7 +3901,7 @@ mpdolce = inst = #(define-music-function - (parser location string) + (string) (string?) #@{ <>^\markup \bold \box #string #@}) @end example @@ -3920,7 +3939,7 @@ mpdolce = inst = #(define-music-function - (parser location string) + (string) (string?) #{ <>^\markup \bold \box #string #}) @@ -3955,7 +3974,7 @@ mpdolce = inst = #(define-music-function - (parser location string) + (string) (string?) #@{ <>^\markup \bold \box #string #@}) @@ -3988,7 +4007,7 @@ mpdolce = inst = #(define-music-function - (parser location string) + (string) (string?) #{ <>^\markup \bold \box #string #}) @@ -4039,7 +4058,7 @@ mpdolce = inst = #(define-music-function - (parser location string) + (string) (string?) #@{ <>^\markup \bold \box #string #@}) @@ -4073,7 +4092,7 @@ mpdolce = inst = #(define-music-function - (parser location string) + (string) (string?) #{ <>^\markup \bold \box #string #})