X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fuser%2Fchanging-defaults.itely;h=3b681cb22decee6e4c8f0c2fc42cfac2e1e6af65;hb=af770f3440264c18ce01525dce1aa76b86ace0d5;hp=992338d991266a7d4978902671b1c9eeeaa8e885;hpb=5b1695e47e039e4751cac2f945ea5c53b5af1492;p=lilypond.git diff --git a/Documentation/user/changing-defaults.itely b/Documentation/user/changing-defaults.itely index 992338d991..3b681cb22d 100644 --- a/Documentation/user/changing-defaults.itely +++ b/Documentation/user/changing-defaults.itely @@ -192,7 +192,7 @@ c1 cis cis c @item forget This is sort of the opposite of @code{no-reset}: Accidentals -are not remembered at all---and hence all accidentals are +are not remembered at all -- and hence all accidentals are typeset relative to the key signature, regardless of what was before in the music @@ -355,6 +355,28 @@ In 4/4 time signature, this means that automatic beams could end only on 3/8 and on the fourth beat of the measure (after 3/4, that is 2 times 3/8, has passed within the measure). +If any unexpected beam behaviour occurs, check the default automatic beam +settings in @file{scm/@/auto@/-beam@/.scm} +for possible interference, because the beam +endings defined there will still apply on top of your own overrides. Any +unwanted endings in the default vales must be reverted for your time +signature(s). + +For example, to typeset @code{(3 4 3 2)}-beam endings in 12/8, begin +with + +@example +%%% revert default values in scm/auto-beam.scm regarding 12/8 time +#(revert-auto-beam-setting '(end * * 12 8) 3 8) +#(revert-auto-beam-setting '(end * * 12 8) 3 4) +#(revert-auto-beam-setting '(end * * 12 8) 9 8) + +%%% your new values +#(override-auto-beam-setting '(end 1 8 12 8) 3 8) +#(override-auto-beam-setting '(end 1 8 12 8) 7 8) +#(override-auto-beam-setting '(end 1 8 12 8) 10 8) +@end example + @cindex automatic beam generation @cindex autobeam @funindex autoBeaming @@ -371,6 +393,18 @@ beaming should be switched off with @code{\autoBeamOff}. @funindex \autoBeamOn @code{\autoBeamOn}. +@commonprop + +Beaming patterns may be altered with the @code{beatGrouping} property, + +@lilypond[quote,verbatim,relative=2,fragment,ragged-right] +\time 5/16 +\set beatGrouping = #'(2 3) +c8[^"(2+3)" c16 c8] +\set beatGrouping = #'(3 2) +c8[^"(3+2)" c16 c8] +@end lilypond + @refbugs @@ -592,8 +626,8 @@ To have it interpreted at the @context{Score} or @context{Staff} level use these forms @example -\context \applyOutput #'Score #@var{function} -\context \applyOutput #'Staff #@var{function} +\applyOutput #'Score #@var{function} +\applyOutput #'Staff #@var{function} @end example @end itemize @@ -1591,7 +1625,7 @@ is more or less equivalent to The value of @code{context} (the alist) is used to initalize the properties of individual grobs. Grobs also have -properties, named in scheme style, with +properties, named in Scheme style, with @code{dashed-words}. The values of grob properties change during the formatting process: formatting basically amounts to computing properties using callback functions.