Re: More than one tempo mark in a score

Simon, Not all that small, but there's a lot of overrides! Uncommenting the commented-out line moves the text back, so the Largo is correct but the Presto is wrong. Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com \version "2.19.52" \language "english" global = { \tempo "Largo"

Re: More than one tempo mark in a score

On 14.02.2018 13:34, ptoye wrote: the Largo metronome mark is too far to the right as it seems to be aligned to the first silent note rather than the clef or time signature. That seems like a bug to me – I think the MetronomeMark should be aligned the same no matter whether it’s in a context o

Re: More than one tempo mark in a score

Peter Toye writes: > The Internals Reference (or the bits that I've read) doesn't have any > music examples. Yes, it's autogenerated. It does have an index, and Emacs is pretty good at navigating via the index. > And rather oddly, I've never used Emacs. Well, it's gotten easier since your ear

Re: More than one tempo mark in a score

David, The Internals Reference (or the bits that I've read) doesn't have any music examples. And rather oddly, I've never used Emacs. Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Wednesday, February 14, 2018, 12:19:11 PM, you wrote: > ptoye writes: >

Re: More than one tempo mark in a score

Simon Albrecht-2 wrote > Of course it’s possible, and a very common thing to do e.g. in > orchestral scores. See ;. I've compared your solution with Hwaen Ch'uqi's and they give slightly different results on the page. As you sent it, the tempo and mark ind

Re: More than one tempo mark in a score

ptoye writes: > Martin Neubauer wrote >> On 12/02/2018 16:42, Peter Toye wrote: >> >> Although developing lilypond itself on a windows machine might indeed be >> challenging, all the programming capabilities you'd need in your scores >> should just work anywhere lp runs. And even if you don't in

Re: More than one tempo mark in a score

Martin Neubauer wrote > On 12/02/2018 16:42, Peter Toye wrote: > > Although developing lilypond itself on a windows machine might indeed be > challenging, all the programming capabilities you'd need in your scores > should just work anywhere lp runs. And even if you don't intend to write > engrave

Re: More than one tempo mark in a score

On 12/02/2018 16:42, Peter Toye wrote: > Monday, February 12, 2018, 3:22:27 PM, you wrote: > > *> Hi Peter, > >>> The nuisance is that you have to count all the silent bars where there >>> aren't any tempo changes, which is far less convenient than simply adding a >>> \tempo "Allegro" at the

Re: More than one tempo mark in a score

m on a windows-based machine, and I gather that this gives difficulties with developing LP (and many other public domain programs). > Hope that helps, Yes it does! > Kieren. > ____ > Kieren MacMillan, composer > ‣ website: www.kierenmacmillan.info > ‣ email: i...@kier

Re: More than one tempo mark in a score

Hi Peter, > The nuisance is that you have to count all the silent bars where there aren't > any tempo changes, which is far less convenient than simply adding a \tempo > "Allegro" at the relevant place in the score! So you're only adding your tempo markings to one context? And now you're going

Re: More than one tempo mark in a score

Hi Kieren, Thanks, and I agree. The nuisance is that you have to count all the silent bars where there aren't any tempo changes, which is far less convenient than simply adding a \tempo "Allegro" at the relevant place in the score! I always miscount by at least 1. As this particular score has o

Re: More than one tempo mark in a score

Hi Peter, > I can see that with a score which has several staves needing tempo markings > Simon's solution works better, but for two yours is my choice. It's a shame > that LP doesn't have an automated way of doing repeating the metronome (or > tempo) marks automatically. It does, and I use it

Re: More than one tempo mark in a score

Hi Ch'uqi, Thanks for this. I have to put in the tempo markings for each stave, but that's easier than counting all the silent bars in Simon's solution. I can see that with a score which has several staves needing tempo markings Simon's solution works better, but for two yours is my choice. It'

Re: More than one tempo mark in a score

6:13:40 PM, you wrote: > On 11.02.2018 19:00, Peter Toye wrote: >> More than one tempo mark in a score Is it possible to force a score to >> put tempo markings above more than the top line? I'd like to put the >> tempo changes above both of the piano parts in a duet, so

Re: More than one tempo mark in a score

Greetings Peter, Well, I don't know exactly how you are setting up the code for your score, but something like this should do the trick: \score { << \new PianoStaff << \new Staff \with { \consists "Metronome_mark_engraver" } { . . . } \new Staff

Re: More than one tempo mark in a score

On 11.02.2018 19:00, Peter Toye wrote: More than one tempo mark in a score Is it possible to force a score to put tempo markings above more than the top line? I'd like to put the tempo changes above both of the piano parts in a duet, so the secondo player changes tempo at the same time a

More than one tempo mark in a score

Is it possible to force a score to put tempo markings above more than the top line? I'd like to put the tempo changes above both of the piano parts in a duet, so the secondo player changes tempo at the same time as the primo when sight-reading. I've looked through the snippets and the internals