Time signature does not always update in score

• Dec 15, 2018 - 16:09
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4482, revision: 2e2af50

Create a score using either 3/4 or 6/8 as the time signature
apply the other time signature to the first measure

Expected result: time signature changes, measure properties indicates the change in actual and nominal Measure durations and time signature properties (in the right click menu) update.

Actual result: time signature stays the same but measure properties are correct but time signature properties show the original time signature.

Additional notes: I have used not parts in any of the testing, so I know this is not a factor. I also tried it in page view and continuous view so that is not an issue. The workaround is to apply a different time signature before the one you want -12/8 works fine for this and does not create ties like 4/4 would. Also note, that 4/4 and equal length time signatures (C and cut) work fine. Creating a custom 3/4 time signature had the same results. The strangest thing in my mind is that the beaming is adjusted according to the new time signature in all tested cases.


Comments

Priority P0 - Critical

Confirmed. Presumably the code that tries to avoid unnecessary changes if the time signature hasn't actually changed is getting fooled by the fact the durations work out the same for 3/4 and 6/8.