Incorrect tempo after tempo edits in presence of fermata with time stretch enabled
Reported version
3.1
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
There are several scenarios that are very likely to be related so I'll put them in one issue.
Scenario 1:
1) Open the attached score (it contains a tempo marking and some time-stretched fermatas).
2) Remove the tempo marking.
3) Play the score.
Result: playback tempo is 120BPM before the first fermata (correct), fermata plays time-stretched (correct), after the fermata tempo goes to 200BPM (wrong).
Scenario 2:
1) Open the attached score
2) Assign different tempo to the tempo marking (either via editing its text or directly via Inspector).
3) Play the score.
Result: time stretch of fermatas is ignored.
Not a regression, both issues can be reproduced at least since version 3.0.2 (and very likely in earlier versions too).
Attachment | Size |
---|---|
fermata_time_stretch.mscz | 5.31 KB |
Fix version
3.2.0
Comments
Pull request: https://github.com/musescore/MuseScore/pull/5143
Fixed in branch master, commit fc32f2726d
fix #290997 pt.2: unify tempo/timesig map rebuilding in layout and fixTicks
Fixed in branch master, commit 1e04a9db59
fix #290997, pt.1: rebuild tempomap on adding/removing tempo text
Automatically closed -- issue fixed for 2 weeks with no activity.