On 5/9/10 6:02 PM, "Bernhard Ott" wrote:
> Hi,
> I just had a hard time making "subdivideBeams" work: the subdivision
> always started with an offset. I had a look at the beam-settings.scm and
> I really can't figure out, why the "my" redefinition via
> \overrideBeamSettings changes anything (
Han-Wen Nienhuys wrote:
Alard de Boer escreveu:
On 17/01/07, Alard de Boer <[EMAIL PROTECTED]> wrote:
Hello list,
Does anyone know how subdivideBeams is supposed to work
with automatic beaming? I haven't seen any replies to this
message I sent a couple of days ago.
It's a bug.
Filed as
htt
Alard de Boer escreveu:
> On 17/01/07, Alard de Boer <[EMAIL PROTECTED]> wrote:
>> Hello list,
>
> Does anyone know how subdivideBeams is supposed to work
> with automatic beaming? I haven't seen any replies to this
> message I sent a couple of days ago.
>
It's a bug.
--
Han-Wen Nienhuys - [
On 17/01/07, Alard de Boer <[EMAIL PROTECTED]> wrote:
Hello list,
Does anyone know how subdivideBeams is supposed to work
with automatic beaming? I haven't seen any replies to this
message I sent a couple of days ago.
Using subdivideBeams with manual beaming, as explained
in 6.5.6 in the manu
Hello list,
Using subdivideBeams with manual beaming, as explained
in 6.5.6 in the manual, works fine. However, using it with
automatic beaming with the LilyPond code below, results in
the attached output, which has two problems:
1) The last beam of the first measure is subdivided; a
workaround
