On Thu, 12 Sep 2024, msk...@ansuz.sooke.bc.ca wrote:
> It's not clear to me from the description of that issue what the issue
> actually is. There is one sentence describing the grace music data
> structure but no other text.
Further to this: I wonder if what's really going on is an issue with
interaction between Lilypond as such, and articulate.ly. Note that my
tests so far have been with this code, which uses \articulate:
\include "articulate.ly"
\score {
\new Staff {
\articulate { \appoggiatura { e'8 g'8 } c'4 r4 r2 | }
}
\layout { }
\midi { }
}
If I change that to leave out the call to \articulate, then even "good"
versions of Lilypond give the "9/40 of notated duration" timing. It is
\articulate that changes it to the longer duration, presumably by
recognizing and editing the "grace music" data structure. I note that
articulate.ly does not seem to have changed between "good" and "bad"
versions. But the description of issue #6617 refers to the grace music
data structure.
So I wonder if what's going on is:
* Lilypond as such, by itself without articulate.ly, has always (or for a
long time) created the "9/40 of notated duration" timing.
* \articulate in the past would recognize the resulting data structure
from \appoggiatura and change it to the longer "half of following
notehead" timing.
* Commit 7a31661dd33a69aece5f8c986f03b770768eafad changed the data
structure without changing articulate.ly.
* Now \articulate no longer recognizes the changed data structure and
leaves the timing at the Lilypond-created "9/40 of notated duration."
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before tribes.
https://ansuz.sooke.bc.ca/
