[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
doc bug(s)?/beam bug?
From: |
David Bobroff |
Subject: |
doc bug(s)?/beam bug? |
Date: |
Mon, 28 Nov 2005 22:19:31 +0000 |
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?]
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.]
a/b is the position in the bar at which the beam should end.
[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:
#(override-auto-beam-setting '(end * * 2 4) 4 8)
...mean that in 2/4 time four eights should be beamed together?
Neither one does that for me on CVS 2.7.20. So, is this a bug, a doc
bug, a failure on my part to understand, or some combination of the
three?
-David
- doc bug(s)?/beam bug?,
David Bobroff <=