Tempo Change Plugin

• Mar 19, 2021 - 17:21

I really like the performance of Jeetee's Tempo Change plugin. The results are so much more flexible and musical than the changes I was inputting manually.

I note, however that the final tempo is placed on the beat following the selected range. (Eg. The range is from beat 1 to beat 4 of a measure, but the plugin places the new tempo on beat 1 of the following measure.) This is fine in most cases, but there are times where it is appropriate to "release" a tempo change at a different tempo than the accelerando or rallentando. For example, a conductor, wishing to rall from 100 bpm to 92 bpm, may intentionally overshoot the change to 88, and resolve the tempo change at the planned 92 bpm. This accentuates the tension of the tempo change with a satisfying tempo resolution. The same often applies to accelerando, where you slightly overshoot the planned marking.

As regards the tempo change plugin, this means that it is necessary to place the final marker a note (beat?) earlier so that the end marking does not conflict with the new tempo. (I hope that makes sense.)

Is there any way to set the plugin so that its function is completed on the last selected note of the range?

Thanks so much.


Comments

Another possibility is to just overwrite the last marking with your desired new value instead? So let the plugin overshoot, but then double click the last marking to edit it into what you're looking for?

You could try editing lines 253-258 (where selection.end is set) to fill the endSeg with the .prev of the current segment and then use the ticks from that one for end as well.

In reply to by jeetee

Yes, indeed. Seeing as I tend to use the effect of resolving to a different tempo rather often, I generally either delete the final (visible) entry of the tempo change chain, or set the range to end one note earlier if possible. (This is not always possible, for example when the last note in the range is a half or whole note.)

BTW, I'm sure your suggestion to edit lines of code is perfectly correct, but it's gibberish to me. :)
Thanks so much, and please do not take my concerns as a criticism of your plugin. I think it's a fantastic addition to MS!

Do you still have an unanswered question? Please log in first to post your question.