Playback tempo becomes incorrect if editing score in continuous view

• May 29, 2019 - 22:58
Reported version
3.1
Priority
P0 - Critical
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
fixed
Regression
Yes
Workaround
Yes
Project

Tempo keeps playing at 120 bpm the majority of the time. If I don't select the measure with the tempo marking (and even then), it almost always just plays at 120. This started after updating to the most recent build.

1) Try different starting points in the piece, either selecting an entire measure of just one note
2) Hit play and you can see the tempo playing as 120 with the Play Panel by pressing F11

Attachment Size
Canon in Eb Major.mscz 15.99 KB

Comments

Severity S2 - Critical S3 - Major
Status active needs info

I can't reproduce. Can you give more precise steps to reproduce? I've tried selecting lots of things and can't get it to play at any tempo other than 70.

Frequency Once Many

I have this problem as well. It occurs unpredictably, and I'm not sure how to reproduce it. I have, however, only noticed it happening in continuous view.

Update: fooling with it just now, it looks like the tempo plays as marked until I add a single note to the score, then start playback. But after saving the score, tempo plays correctly.

This seems similar to #283577 - Tempo markings/metric modulations not working till I save

Reproducibility Always Randomly
Workaround No Yes

I've been having this issue as well, since updating to 3.1. It seems that I can 'remind' the program of the correct tempo by double clicking on the marking as if I were editing the text and then clicking away. I believe I've had this problem before, perhaps back in MS2, but I can't recall specifics. The same workaround worked then as well.

Update: This seems to be specific to continuous view for myself as well.

https://musescore.org/en/node/290652

Title Tempo Tempo changes don't work when score or any part is in continuous view
Status needs info active

workaround is to switch score and all parts to page view, then change the tempo text.

Regression No Yes
Reproducibility Randomly Always
Status duplicate active
Priority P0 - Critical

Or not a duplicate actually. The issue #287000: Playback speed is incorrect when selecting a continuous view for a part is related to continuous view being switched on in parts and is present in older versions of MuseScore (tested on 3.1, 3.0.5 and 3.0.2). This issue is not related to parts at all, is present in MuseScore 3.1 but not in version 3.0.5. My fix for #287000: Playback speed is incorrect when selecting a continuous view for a part fixes that issue but not this one.

Here are the steps to reproduce:
1) Open the score attached to this issue's description.
2) Repitch a note at measure 3 or later.
3) Start playback.
Result: playback goes in 120 BPM.

This may be a side effect of the recent continuous view optimization, in this case we may need to handle tempo in continuous view in the same manner as it is done in page view, i.e. move all tempo handling to measure layout stage, both cleaning and filling a tempo map on a per-measure basis.

Title Tempo changes don't work when score or any part is in continuous view Playback tempo becomes incorrect if editing score in continuous view

Maybe this title will be more precise

Status PR created fixed

Fixed in branch master, commit ec37301c37

_fix #289922: don't reset tempomap in continuous view

Tempo is handled on measure layout stage which is common for page
and continuous view. We don't reset the whole tempomap for page view
currently, and we don't really need to do so for continuous view too._

Fix version
3.2.0