lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Aligning offset quintuplets and triplets


From: Lukas-Fabian Moser
Subject: Re: Aligning offset quintuplets and triplets
Date: Wed, 27 Dec 2023 13:18:07 +0100
User-agent: Mozilla Thunderbird

Hi Knute, hi Mark,

here's an example of what I mean. The "cheating" system should create what the original engraving suggests, even if it's wrong mathematically. I didn't check the difference in MIDI; of course the "conductor" part (consisting of eigths throughout) shows a significant difference.

Of course I took advantage of the fact that the original engraving stops bothering with tuplet brackets/numbers starting from the second bar; it should be possible to get them back, but this will involve some further tweaking in the "cheating" version.

Lukas

Am 27.12.23 um 09:17 schrieb Lukas-Fabian Moser:

Hi Mark,

Am 27.12.23 um 01:54 schrieb Mark Stephen Mrotek:

Knute,

In the original the first beat of the second measure is three against 2. The 5 against 3 does not start until the second beat.

Unfortunately, that can't be true, as with this interpretation, the measure is over-full. Rather, the groups of quintuplets/triplets continue, with a beaming not in sync with the measure's beat structure.

This also implies that the original engraving isn't mathematically correct (as the beginnings of the bems groups look as if they're aligned). Situations like that are hard to approximate with LilyPond, as Lily has a strict binary notion of two notes being simultaneous or not. One can try cheating a bit by engraving the measure according to its visual apperance (3-vs-2 in the first beat, exact 4-vs-1 in the last quaver of the measure), but then it will be necessary to compress whatever will be in the measure to the duration of one whole note, and it's not certain what LilyPond's spacing algorithm will make of it.

Sorry for describing the situation verbally; I'll try to cook up an example as soon as I have time (later today).

Lukas

Attachment: knute.ly
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]