Remove select range in a score with parts results in corruption

• Jun 1, 2019 - 18:53
Reported version
3.1
Priority
P0 - Critical
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
MuseScore

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.7078, revision: e26f7c4

I thought this kind of issue was solved. Apparently not, or not completely, or possibly a regression.

  • First scenario:

1) Default "Untitled" score with parts (test file: test1.mscz )
2) Select the first quarter rest -> Ctrl + Del (for Remove select range)
3) Save/Quit/Reopen ( test1 result.mscz )

Result: as expected, apparently. But:

4) Toggle in piano Part
Result: four beats here.
5) Enter a whole note -> Undo -> Crash (not a surprise of course)

  • Second scenario:

1) Default "Untitled" score with parts (test file: test2.mscz )
2) Select the second quarter rest -> Ctrl + Del
3) Save/Quit/Reopen ( test2 result.mscz )

Result: corruption warning: Expected 3/4, Found 2/4

Comments

• Jun 11, 2019 - 08:13

Or/and, in a more secure and preventive way (when there are parts in the score), the advice will be to adopt the former method of changing the measure duration (current/nominal) in Measure Properties.

Reply

• Jan 23, 2020 - 17:11
Frequency Few ⇒ Many
Regression No ⇒ Yes

Had come up quite often in the forum in the past months. Seems to be a regression vs. 2.x (which didn't have timewise delete, hence not this bug)

Reply

• Jan 25, 2020 - 11:51
Status PR created ⇒ fixed

Fixed in branch master, commit ea62a4a9ff

_fix #290096: fix parts corruption on timewise delete of individual beats

Ensure that all operations in Score::timeDelete() act on all excerpts
rather than only on the current one._

Reply

Fix version
3.4.1