On Tue, 2025-08-05 at 05:28 +0000, Werner LEMBERG wrote: > > In lilypond 2.25.23, tempoWholesPerMinute was changed from a moment > > > to a fraction. I'm trying to avoid making my existing scores a > > > hostage to the eventual removal of tempoWholesPerMinuteAsMoment, > > but > > > an associated change to the behaviour of articulate.ly is causing > > > trouble. > > > > > > This problem was originally raised at > > > https://lists.gnu.org/archive/html/lilypond-user/2025-07/msg00068.html > > > but I'm re-sending it as a bug, in the hope that articulate.ly can > > > be prevented from creating a visual artefact. > > > > > > If the following MWE is compiled under lilypond 2.25.22, the PDF > > output > > > is as expected. However if it is compiled under 2.25.23, an > > unwanted > > > MetronomeMark "[semibreve] = 50" appears at bar 2. > > > Please file an issue.
Thanks Werner. https://gitlab.com/lilypond/lilypond/-/issues/6833 > Hopefully Dan can have a look whether it is > possible to improve the `convert-ly` script so that it catches this > case – or maybe `articulate.ly` can be modified accordingly. > Otherwise, `convert-ly` should at least emit a warning. I think that convert-ly explicitly avoids trying to deal with this: see https://lists.gnu.org/archive/html/lilypond-user/2025-04/msg00073.html IMHO the best fix would lie in articulate.ly. After all, articulate.ly has no business altering the PDF output. -- Graham > > > Werner
