Re: articulate.ly creates MetronomeMark under lilypond > 2.25.22
Graham King <[email protected]> Tue, 05 Aug 2025 12:10:15 +0100
| Newsgroups | gmane.comp.gnu.lilypond.bugs |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 2025-08-04 at 22:31 +0100, Timothy Lanfear wrote:
>
> On 04/08/2025 16:11, Graham King wrote:
>
>
> >
> > 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.
> >
>
> Whilst not having a fix, I can propose a work-around that wraps a
> command to hide the metronome mark with ac:tempoChange. Any \tempo
> commands with a metronome mark are not affected.
>
> \version "2.24.0"
> \include "articulate.ly"
>
> mytempoChange = #(define-music-function (newTempo) (ly:moment?)
> #{
> \once \set Score.tempoHideNote=##t
> #(ac:tempoChange (if (ly:version? > '(2 25 22))
> (ly:moment-main newTempo)
> newTempo))
> #})
>
> % (my scores and functions all use moments):
>
> {
> \tempo "Allegro" 4=100
> c'2 2
> \mytempoChange #(ly:make-moment 100 2)
> c'2 2
> }
>
Thanks Timothy, I'll give this a try. There are a handful of similar
workrounds, however my difficulty lies in integrating them deep in the
scheme code from which the MWE was laboriously distilled :)
all the best
-- Graham
> Thanks Timothy
>