lilypond-user
[Top][All Lists]
Advanced

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

Re: Problem with Long Tempo


From: Thomas Morley
Subject: Re: Problem with Long Tempo
Date: Thu, 2 Feb 2017 00:22:54 +0100

2017-02-01 2:55 GMT+01:00 Dave Hartley <address@hidden>:
>
> Hi all
>
> Using 2.18.2, I'm having problems with a long tempo bumping into another 
> tempo marking a couple of bars later. I'm transcribing music for brass bands, 
> so I tend to put the timing structure in a variable so it can be used for 
> other instruments easily. So something like this:
>
>
> %%%%%%%%%%%%%%%%%%%%%
> \version "2.18.2"
>
> timing = {
> \tempo \markup { \column { "Moderato Con" "Dolore e Fuoco" } } 4=94
> s1*2
> \tempo "accel."
> s1
> \bar "|."
> }
>
> eflatMusic = \relative c {
> \markLengthOn
> <f c>1->\ff ~ | <f c>\> ~ | <f c>8\p r8 r4 r2
> }
>
> \score {
> \new Staff {
> <<
> \timing
> { \clef "treble_8" \eflatMusic }
> >>
> }
> }
> %%%%%%%%%%%%%%%%%%%%%
>
>
> works well, producing
>
>
> However, when I try and make the decrescendo start half-way through the bar, 
> I get this:
>
> Here's how I'm making the decrescendo start halfway through:
>
> %%%%%%%%%%%%%%%%%%%%%
> eflatMusic = \relative c {
> \markLengthOn
> <f c>1->\ff ~ | << { <f c>\> ~ | <f c>8 } \new Voice { s2 s\> s8\p } >> r8 r4 
> r2
> }
> %%%%%%%%%%%%%%%%%%%%%
>
> but I get the same effect if I put the dynamics in a separate variable and 
> add a \new Dynamics into the score. It just seems weird that adding in an 
> extra voice destroys the effect of \markLengthOn. Any ideas?
>
> Dave


Hi Dave,

I think it's a bug.
Hence I opened
https://sourceforge.net/p/testlilyissues/issues/5047/
There you might get an idea for a workaround:
use \mark \instead of \tempo or replace spacers with (omitted) rests

Cheers,
  Harm



reply via email to

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