Score playback tempo changes after editing a score

• Oct 13, 2018 - 12:31
Reported version
3.0
Type
Functional
Severity
S4 - Minor
Status
closed
Regression
No
Workaround
No
Project
MuseScore

Steps to reproduce:
1. Open the attached score (it is this score converted to 2.X and further to 3.X format with some minor edits).
2. Play it a bit, just to hear the tempo of playback.
3. Edit something in the measure 7 or later. For example, repitch some note or remove/add some elements.
4. Play the score again.
Expected results: nothing should change except for the edit that was done.
Actual results: MuseScore somehow decides to play the score 2 or 3 times faster.
5. Now edit something in the measures 1—6. Play the score.
Result: playback returns to its original tempo.

Saving the score also returns playback to the original tempo as well as editing the first six measures.

Tested on
OS: Debian GNU/Linux 9 (stretch), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 59594be

Attachment Size
The_Entertainer.mscz 47.16 KB

Comments

• Oct 30, 2018 - 02:58

I wonder if this is a Linux-specific problem. I happen to be on Arch (with GNOME).
I have been experiencing this issue on all my scores, regardless of whether they have ever been processed in a 2.x version. It happens in your example exactly as described on all my scores and on your example. I feel like this is a pretty major issue, but nobody else is complaining. That's why I think it must be limited to Linux.

It looks as if Musescore periodically forgets about tempo texts, and instead ignores them and defaults to 120BPM, or whatever is the last tempo it remembers.

I've also found that clicking any given tempo text and changing its tempo or checking/unchecking "follow text" seems to remind Musescore about that particular tempo text, but it doesn't then become aware of any other tempo texts.

So let's say I have The Entertainer start at 72BPM like in the example. If I add a tempo change to 90BPM at measure 22 (without saving), Musescore, from the beginning, will play at 120BPM (having forgotten about the initial 72BPM, as I made an edit) until measure 22, where it will play at 90BPM as expected.
But then, if I check/uncheck "follow text" on the first tempo, 72BPM, Musescore will follow at 72BPM the whole way through, having forgotten about the 90BPM.
Then if I save, the whole thing works as expected.

I also have no idea what determines the break between where editing fixes the score vs where editing causes the glitch (in your example measure 6 to measure 7)

Reply