Tempo text oddities in score with linked parts until save/reopen
First reported at https://musescore.org/en/node/78251. I don't really know what's going on, but it's easy to reproduce similar issues with a new score. Here's exactly what I did:
1) Create new score from string orchestra template
2) In Volin I staff, quickly enter a mess of random notes
3) File -> Parts… -> New All
4) In main score, [Option]+[T] at measure one to create "Quarter = 80"
5) "Quarter = 120" at measure 3
6) "Quarter = 144" at measure 5
7) Double-click tempo at measure 3 and change to "Quarter = 60"
Everything will play back correctly in the main score. Now: switch to part for Violin I, and:
1) In the Inspector, though all tempos are set to "Follow Text", the first two (80 and 60) display "120" in the grayed out BPM box, and the third one (144) displays 80;
2) Actual playback tempo (as reported by the Play Panel) is 80 BPM at the first tempo text (80), 120 at the second (60), and 80 at the third (144).
Furthermore, the above now is also messed up in the main score.
The tempos are fixed by saving and reopening the score.
Comments
See also discussion at https://musescore.org/en/node/100046.
See https://github.com/musescore/MuseScore/pull/2451
Two more users reported the same problem: #109921: Tempo and Playback Issues
Shouldn't this fix be merged?
This is bugging me again. Still, miraculously, no merge conflicts in the PR, https://github.com/musescore/MuseScore/pull/2451.
Similar issue: #174451: Actual tempo doesn't revert when undoing an edit on a tempo text
That PR would Need a rebase though meanwhile
Ah, that's a shame. It lasted without conflicting for at least a good five months, and now, when it's time, it's too late and needs to be rebased.
Came up again in https://musescore.org/en/node/208041
The PR might still me mergable to the 2.2 branch?
I tried an amended version of that code in master and it doesn't seem to fix the issue
In reply to #10 by Jojo-Schmitz
Came up again https://musescore.org/en/node/271777
Edit: this might be a different issue.
Came up for me just now: https://musescore.org/en/node/271835
Relates to #272381: [EPIC] Tempotext issues
I tested it in the 3.1 Beta and the issue is seemed to be fixed.
The only thing I did differently from the initial description, I couldn't make Option+T work, so I just added a tempo text and edit the tempo values.
Automatically closed -- issue fixed for 2 weeks with no activity.