bug-lilypond
[Top][All Lists]
Advanced

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

Re: Textual tempo markers in adjacent bars are stacked


From: Phil Holmes
Subject: Re: Textual tempo markers in adjacent bars are stacked
Date: Mon, 7 Jun 2010 16:56:59 +0100

"Reinhold Kainhofer" <address@hidden> wrote in message news:address@hidden
Am Donnerstag, 7. Januar 2010 18:06:26 schrieben Sie:
Hi,

2010/1/7 Reinhold Kainhofer <address@hidden>:
> PS: I'm forwarding this to bug-lilypond, so that it gets at least
> recorded for the future.

There are already (at least) 2 open issues about this:

684: Enhancement: MetronomeMark should support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
712: alignment of multiple \tempo marks over `church rests'
http://code.google.com/p/lilypond/issues/detail?id=712

Nope, although both are about tempo marks, neither of them is about this
issue. The first bug is that metronome marks don't start at the center of the time signature (as they are supposed to, according to e.g. Gardner Read), the second one is basically a consequence of the first bug, which results in tempo marks starting in the middle of a multi-measure rest measure rather than at
the beginning...

However, none of them is about widening a multi-measure rest measure to make
sure the tempo mark fits in the space until the next tempo mark.

Several people have already complained about this (including me, actually I
"groused" about it, which wasn't the best way to move forward  :p ).
The thread about this can be found in the archives of this mailing-list
(gnu.org archives seems unavailable now but subject was "Tempo mark
 alignment" and date was 23/05/2009).
Nabble archive:
http://old.nabble.com/Tempo-mark-alignment-ts23679524.html#a23773635

As a workaroud I use this user-defined "TempoMark" command for textual
tempo marks:

tempoMark = #(define-music-function (parser location markp) (string?)
#{
  \once \override Score.RehearsalMark #'self-alignment-X = #LEFT
  \once \override Score.RehearsalMark #'break-align-symbols =
#'(time-signature key-signature)
  \once \override Staff.TimeSignature #'break-align-anchor-alignment =
 #LEFT \once \override Score.RehearsalMark #'font-size = #1
  \mark \markup { \bold $markp }
#})

There was a debate about issues priority classification, someone (Werner?)
spoke about an "annoying" tag, which seems now to be "Priority-High".
I hope these issues are "eligible" to this higher priority.

Cheers,
Xavier

PS: +1  Me too!  ;-D

     Issue 1024:  measure width should adapt to MetronomeMarks


--
Phil Holmes






reply via email to

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