|
From: | Mats Bengtsson |
Subject: | Re: doc bug(s)?/beam bug? |
Date: | Tue, 29 Nov 2005 13:16:24 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 |
I've corrected the two typos in the documentation. For your last question, see below. David Bobroff wrote:
Not sure if I've spotted a documentation bug (at the very least there is a typo), a program bug, or some of each. Here goes: In section 8.6.2 "Setting automatic beam behavior" it says; #(override-auto-beam-setting '(be p q n m) a b [context])be is either "begin" or "end".[OK] b/q is the duration of the note for which you want to add a rule. A beam is considered to have the duration of its shortest note. Set p and q to '*' to have this apply to any beam. [Should be p/q no?]
Right!
n/m is the position in the time signature to which this rule should apply. Set n and m to '*' to have this apply in any time signature. [...is the position in the time signature...? Or ...is the time signature...? I infer from the example for 5/8 time which follows that n/m should *be* the time signature.]
Right!
a/b is the position in the bar at which the beam should end.No, since there already are a number of settings defined by default in LilyPond,[OK, I think] So, shouldn't this code: \version "2.7.20" \score { \relative { #(override-auto-beam-setting '(end * * * *) 4 8) \time 2/4 c8 c c c } } ...produce a single beam across four eighth notes? Also, shouldn't:
see scm/auto-beam.scm.
[Prev in Thread] | Current Thread | [Next in Thread] |