Re: setting beams for "odd" time signatures

[Markus Schneider]

So, what you're saying is, the default rules are interferring because they
are still valid!

That means, if any unexpected beam behaviour occurs, you have to

1. look up the "autoBeamSettings" set in "Score"

(http://lilypond.org/doc/v2.9/Documentation/user/lilypond-internals/Score.ht
ml#Score
    or
    scm/auto-beam.scm)
2. revert any settings that might interfere with your time signature(s)
3. set your own overrides

I think this is worth a doc addition. I'll post a summary of these findings
on devel.

Markus

"Mats Bengtsson" <address@hidden> schrieb im Newsbeitrag
news:address@hidden
> It turns out that what was missing in my proposed solution was
> to revert the default settings:
>
>   #(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)
>
> Then, you can use
> #(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)
>
> (or  with wildcards '*' as Markus proposes). Also, setting beatLength
> doesn't seem to have any relevance at all here. I tried to comment it
> out in Markus' example and didn't notice any difference.
>
>    /Mats