Re: relative tempo changes?

On 2026-02-24 18:31, Dan Eble wrote:
> On 2026-02-22 12:05, Arnold wrote:
>> Another function may create a sequential music for "tempo ramps", you
>> specify the total duration (e.g. 4 measures), the frequency (e.g. each
>> quarter an update) and the relative final tempo (e.g. 2/3), and you can
>> place the resulting sequential music (which only contains
>> relativeTempoChanges and skips) parallel to your existing music.
>> Here an example for such a sequence:
>> { relativeTempo(save OriginalTempo; alter to current * 47/48; no clear)
>>    s4
>>    relativeTempo(no save; alter to OriginalTempo * 46/48; no clear)
>>    s4
>>    relativeTempo(no save; alter to OriginalTempo * 45/48; no clear)
>>    ...
>>    relativeTempo(no save; alter to OriginalTempo * 32/48; no clear)
>>    s4
>> }
> 
> This looks heavily influenced by the workarounds that are currently 
> required.  We don't require this level of detail in music expressions 
> for dynamic ramps.  I confess that I'm not thinking deeply about this 
> right now, but it seems that it should be possible to stick to placing 
> points of interest in the music expressions and let the performance code 
> interpolate between them.

https://gitlab.com/lilypond/lilypond/-/merge_requests/3013 proposes
\startGradualTempoChange and \stopGradualTempoChange affecting MIDI 
only, but with placeholder arguments to add markup later.
-- 
Dan