Open TheMinilena opened 2 weeks ago
Confirmed to be broken going back to 4.2 at least. It fixes itself on save/reload, but also fixes itself as you edit the score. In particular, adding or editing a tempo mark at the beginning of the score fixes it completely.
@zacjansheski pls regression check
Same in all versions of MS4
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/c26fa32f-84dd-49fe-aa18-3c8e5836c6b3
What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
Windows 10 and 11
Additional context
This might have worked in earlier MS4 builds, I haven't made a template in years
Checklist