Score with invalid tab note marked as dirty on open

• Jun 15, 2021 - 22:29
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
MuseScore

Steps to reproduce:
1) open the file, for example via
MuseScoreNightly-latest-x86_64.AppImage Touch.mscz

Observed behavior:
Without doing anything, the tab of this file receives an asterisk, as if it was changed

Version:
OS: Ubuntu 20.04.2 LTS, Arch.: x86_64, MuseScore version (64-bit): 3.6.2.938029273, revision: 415b192

Touch.mscz

Comments

• Jun 17, 2021 - 13:30
Title Opening this file, immediately marks it changed (asterisk) ⇒ Score with invalid tab note marked as dirty on open
Workaround No ⇒ Yes

Confirmed. I believe it is related to the fact you have an invalid note (in the tablature in measure 65. It's set to fret 26 but your tab staff is defined to go only to 24. So this gets "corrected" for display purposes on load, that's why it shows as "dirty".

Best to fix this - either change the note to something in range, or increase the maximum number of frets for the staff. If you do that, it works as expected.

Still, we probably shouldn't mark the score dirty for this. Also, we could possible either warn about this, or make it harder to create this invalid notation in the first place.

Reply