TempoChanges plugin: account for notes in all voices.

• Mar 5, 2016 - 21:53
Type
Functional
Severity
S5 - Suggestion
Status
closed
Project
TempoChanges

Thanks for providing this useful plugin. I think it might be worth extending it to account for notes in all voices in the selection. Let's say we'd like a ritardando starting with 4=120 down to 4=60 at the end of the following score: Selecting both staves and setting Start=120 and End=60 gives
TempoChangeTest.png
Because there are only two notes in the first selected voice, only two tempo markings are created.
Selecting the bass staff produces a better result, but the second measure still gets only one tempo marking
TempoChangeTest2.png

Attachment Size
TempoChangeTest.mscz 6.32 KB

Comments

• Mar 5, 2016 - 22:52

As a tempo marking applies to the whole system, it would probably make sense to use the selection as a horizontal range indication only, and apply markings for each next tick upon which a note exists across the whole system.
Agreed?

Reply

• Mar 5, 2016 - 23:22

Indeed, I totally agree.

Just one more thing: If there are a lot of "small notes", they might lead to consecutive tempo markings with the same value. The plugin could make sure, that a new marking really changes the tempo.

Reply

• Mar 22, 2016 - 10:47

I have tried to figure out, whether it is a matter of the MIDI-Standard or a matter of software. But I was not able.

For example I can create in Reaper two kind of tempo markers.
Nr. 1: After this tempo marker the tempo stay the same until the next tempomarker.
Nr. 2: After this tempo marker the tempo in/decrease linear up/down to the tempo value of the next tempomarker.

So the favoured aim would be, that your tempomarkers work like number two.

Reply

• Mar 22, 2016 - 11:38

@hasenfuss:
This plugin was created as a workaround to achieve the result of Nr2 using Nr1. Currently MuseScore only supports markers of you type 1 and a plugin can only use what exists internally.

If markers of type 2 come into existence, this plugin will most likely cease to be, as it wouldn't have any added value anymore. There exists a feature request for adding markers of type 2 to the MuseScore core program, which can be found here: https://musescore.org/en/node/9383

Reply

• Mar 22, 2016 - 12:01

Thank you. Posted 201, status minor and
It is important to realize the primary purpose of MuseScore is *notation* - to allow you to create scores you can print and play yourself. The fact that it also happens to have some sort of rudimentary ability to playback the scores itself is very secondary. makes me not very optimistic.

So I have a suggestion for usability. For Example: Two tempotext are marked in the score, run the plugin and do the same like now, reading the values from the tempotext.

Next suggestion, the first use of the plugin create a invisible muted voice with the smallest notevalue of the score. This voice is the basis to add the invisible tempomarkers.

Reply