tempo.followText does not take effect

• Jan 18, 2022 - 16:20
Reported version
3.6
Priority
P2 - Medium
Type
Plugins
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No

is fixed in version: 1.0.3
Will be published later on 20. Jan 2022

Steps to reproduce:
1 use plugin: Sight Reading Trainer and create a score with any tempo (default is 50bpm)
2 Within Musescore, in the score created, click on the "50" bpm and change the value to e.g. 120bpm.
bpm.png
3 play the score as Midi within Musescore.
Result:
Score is played still with 50bpm :-(
Workaround:
Deleting the tempo and adding it via Musescore API then it should work.


Comments

Seems so, the tempochanges plugin doesn't set that flag successfully either

Might be something to report separatly, and against musescore itself

Title tempo cannot be changed after training score is created within Musescore by changing the value tempo.followText does not take effect
Frequency Once Few
Type Functional Plugins
Workaround Yes No
Priority P2 - Medium

TempoChanges is indeed affected as well. https://musescore.org/en/node/120256#comment-1016409
It at least used to work back when originally written (in 2.0.2), so I'm not sure whether it broke in 3.0 or later

Frequency Few Once
Regression Yes No
Severity S3 - Major S4 - Minor

Hold on, this issue is against the Sight Reading Trainer plugin, not against MuseScore's plugin framework.

We'd need an issue against that