Re: complex time signatures: scheme help

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Samstag, 15. August 2009 01:06:40 schrieb Carl Sorensen:
> On 8/14/09 4:46 PM, "Reinhold Kainhofer" <address@hidden> wrote:
> > Attached is my current code for general complex time signatures
> > (arbitrary # of fractions, arbitrary # of numerators). I have not yet
> > tried to get it into master, because the auto-beaming does not yet follow
> > the signature.
>
> How should auto-beaming respond to a compound time signature?
>
> In particular, how should ((2 3 8) (4 8)) be different from (2 3 4 8)?

That's one of the reasons why I haven't attacked that problem yet ;-)

> I think with the new autobeaming code it would not be hard to get the
> top-level beaming right.

yeah, I simply never managed to read the docs..

> BeatLength, on the other hand, probably doesn't have sufficient structure
> built into it to handle ((1 2 3 4 8) (2 4) (2 3 8)), because for that time
> signature, beatLength should vary with measure position.

I currently simply take the largest denominator ad common beatLength, so in 
this case the beatLength will be 8. I also don't know enough about the beaming 
rules to know how 2/4 and 4/8 behave differently.

> I'm willing to take a shot at fixing the auto-beaming, if you'd like.

Yeah, that would  be great!

Currently, the code I sent (albeit not perfect yet) is already used in 
musicxml2ly (where it is copied verbatim to the output file), but it should 
become part of master sooner or later, so that lilypond also supports complex 
time signatures properly.

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFKhfnUTqjEwhXvPN0RAt5EAJ4ot7fHua+hmvuQ2moKNT1/Z7VZtwCgoPfb
4ZzCTmAC5WUVwIdT0q9ZLHc=
=4Ocb
-----END PGP SIGNATURE-----