tempo.followText does not take effect
Reported version
3.6
Priority
P2 - Medium
Type
Plugins
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
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.
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
Or tick the "Follow Text" box in the tempo marking's Inspector
In reply to Or tick the "ollow Text" bix… by Jojo-Schmitz
Thought about your comment a day or two... still have no idea what you mean?
what is allow Text bix?
Typos, corrected now, sorry
In reply to Typos, corrected now, sorry by Jojo-Schmitz
yeah! still took a moment to find it but yes that works fine. Do you also know how to set this option from within QML?
set the tempo's
followTextproperty totrue. See how the tempochanges plugin does itActually it seems you do that already, in sight_reading_trainer.qml, line 126
In reply to Actually it seems you do… by Jojo-Schmitz
yes thats right. I just tried to move the line 126 "tempoElement.followText = true;" to line 122 so before "cursor.add(tempoElement);". Still the same. Could that be a bug?
Seems so, the tempochanges plugin doesn't set that flag successfully either
Might be something to report separatly, and against musescore itself
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
It must have worked at one time, probably in MuseScore 2, so is a regression (albeit not a very recent one?)
Hold on, this issue is against the Sight Reading Trainer plugin, not against MuseScore's plugin framework.
We'd need an issue against that
In reply to Hold on, this issue is… by Jojo-Schmitz
ok. so I should enter an issue against Musescore, agreed?
yes, please
Hold on.. got a hunch here
The property was renamed in 3.0.2 when switching from an explicit element exposed API to the generic "Element" PluginAPI. Use
.tempoFollowTextinstead. See reference commit on TempoChangessorry.. this plugin isn't fixed yet
In reply to sorry.. this plugin isn't… by jeetee
Yes! Thanks so much. It works now. I close the issue https://musescore.org/en/node/328538
In reply to Yes! Thanks so much. It… by karsten.spries…
Plugin is updated to version 1.0.3
Automatically closed -- issue fixed for 2 weeks with no activity.