Segno and Coda markers reset
The "Label" property of Segno, Coda, To Coda, and Fine maker types reset when you change the style settings. In fact, you don't even need to actually change the style settings. Changing any settings value and cancelling the change is enough to reset the markers.
Curiously, the bug does only occur for markers placed in the same instance of MuseScore. Saving the score, closing MuseScore, and loading the file again, safeguards the Label properties from any inadvertent reset.
But critically, when a marker is reset this way, the file will not be marked as changed (*). And then saving the file will save the reset Label value, probably unbeknownst to the user more often than not.
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.1-250800846, revision: 603eca8
Comments
Please identify your computer's operating system and version, and MuseScore's version. You can get all three simultaneously by clicking on Help / About MuseScore from the main menu. Then click the copy button (two pieces of paper) next to the "Revision" number. Edit your original post and paste that in.
I have ...
OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: 2232670
... and I can confirm this behavior in the attached score. Including that it does not reset in another instance and that the change does not label the score as "changed" on the tab.
In reply to Please identify your… by TheHutch
Sure.
The D.S./D.C. markers are not affected as far as I can tell. I guess they're more or less entirely separate entities in the code.
In reply to Sure. The D.S./D.C. markers… by 23powerz
No, the D.S. and D.C. markers are not affected because they don't have labels. They use the labels of the other markings, but they do not have labels of their own.
And, I repeat, please identify your computer's OS and version of MuseScore, as I described above.
Just found another (probably related?) bug:
If you place a repeat marker and leave the Label property empty, it will turn into a "Marker type: Custom", and the value of the Label property defaults to "coda" (regardless of what type the marker initially was) once you save and reload the file. Which will likely be referenced by a D.S./D.C. jump and mess with everything, even though it worked just fine before you saved and closed the score.
If you want a non-functional marker for whatever reason, the Label property absolutely has to be filled with a string that is not referenced by a jump. NULL is not a valid value (or rather it is until it isn't) and MuseScore won't tell you that. And before you say there's never a reason to do that: Maybe you have a functional but invisible marker and a non-functional one for the optics, in order to get the layout 'just right'. That's a common enough practice, and leaving the Label property empty is an intuitive way to go about it. Or you use a marker as plain text in order to have text centered on a measure. The repeat makers can do that, normal text entities can't. (Probably not a good idea in the first place to force users to use such janky workarounds, but that's an entirely different subject.)
In the attached score, "centered text" started life as a Fine marker with an empty Label property. D.C. al Coda had worked just as intended, but after closing and reloading the file, “centered text”'s Label property now has the value "coda" and is recognized by D.C. al Coda as such, superceding the actual To Coda with the same value and changing the playback. (From 1-6>1>5,6 when created to 1-6>1,2,3>5,6 upon reloading.) No idea if it is already being saved with the default "coda" value, or if that value is inserted upon loading the file.
No value should ever be changing on its own. There's something really wonky going on with the repeat markers deep in the code.