Fermata tempo is not applied when importing 2.X->3.0 score
Upon importing a file created in the latest version of MuseScore (2.2.1) and playing, a fermata changes the time strech for all notes after it.
The attached file was created in Musescore 2.2.1 and has this error.
There is a relatively easy work around - replacing the fermata in the nightly build puts a correctly working one, but if you were to import something like Beethoven's 5th Symphony, it'd quickly become problematic.
| Attachment | Size |
|---|---|
| test.mscz | 4.33 KB |
Comments
Relates to #272381: [EPIC] Tempotext issues?
In reply to Relates to #272381: [EPIC]… by mike320
Yep, thank you!
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 55e0a7a
Current master doesn't change the tempo after the fermata, but... it doesn't even apply time stretch to fermata.
see https://github.com/musescore/MuseScore/pull/3926
Fixed in branch master, commit 8422a7d410
fix #271616: Fermata tempo is not applied when importing 2.X->3.0 score
Fixed in branch master, commit cb6a5c911f
Merge pull request #3926 from handrok/fix#271616-Fermata_tempo
fix #271616: Fermata tempo is not applied when importing 2.X->3.0 score
Reverted changes from https://github.com/musescore/MuseScore/pull/3926. They led to crashes when opening 2.06 scores.
For reference, see: #275964: Crash involving fermatas when opening a file
https://github.com/musescore/MuseScore/pull/3937
Add test to mtests to prevent crash in the future.
Fixed in branch master, commit 34cf407404
fix #271616: Fermata tempo is not applied when importing 2.X->3.0 score
Add reading timeStretch for feramta from mscz
Add calculating ticks for segments before first using fermata
Add fermata.mscx to unit tests
Fixed in branch master, commit fb9dcac998
Merge pull request #3937 from handrok/fix#271616-Fermata_tempo
fix #271616: Fermata tempo is not applied when importing 2.X->3.0 score
Automatically closed -- issue fixed for 2 weeks with no activity.