Text line disappears if corrupt file by a local time signature
MuseScore v 2.3.2
Open the file "bugreport.mscx" and notice that there is a text line in the two last systems of the score (don't mind the misplacement of the text line, this is a stripped down score just for illustration purposes). Also notice that the XML element is positioned at the beginning of the tag. Change anything on the score with MuseScore and save it.
After saving, notice that the XML element will be repositioned from the beginning of the tag to between two elements. If you re-open this saved score with MuseScore, the text line will be not be displayed anymore!
(The attached file "bugreport_saved.mscx" illustrates the state of the file after having changed a note pitch and saving it.)
| Attachment | Size |
|---|---|
| bugreport.mscx | 120.74 KB |
| bugreport_saved.mscx | 120.74 KB |
Comments
Uhh, looks like I cannot enter XML tags into the bug report's description.
So, errata follows:
Also notice that the [[TextLine]] XML element is positioned at the beginning of the [[Measure]] tag.
the [[TextLine]] element will be repositioned from the beginning of the [[Measure]] tag to between two [[Chord]] elements
You can
< xml >
xmlcode
< / xml >
(without the spaces)
Confirmed. Not sure what the issue is, guessing it might have to do with the grace notes, although I could still reproduce even after removing them (including the one you can't see because it was set to white - btw, an easier way to make things invisble is to just press "V" or set them invisible in the Inspector).
First, this score is in a bad state, due to the use of a local time signature (1/8 for the anacrusis in second staff)
The corruption appears clairly by keeping only the first staff (Tenor1) : tenor1.mscz
And worse, by keeping only the second staff (Tenor2): tenor2.mscz
This causes layout problems (not sure, but I guess this is the cause of the observed behaviour)
This can be seen, for example (on Tenor 2 file), by selecting the last note (Bb) of the penultimate system, and adding (double-clicking) a text line. Result, it "lands" on the last system (image below)
Remove this "wrong" anacrusis (Ctrl + Del) -> insert a new first measure -> change the actual duration for 1/8, and from what I see by now, that solves the problem, the text lines are always here after saving: fixed score.mscz
Considering that:
- the unexpected use of a local time signature for the pick-up measure (in the second staff, 1/8) leads to a bad state of the file
- the fix of this pick-up measure restores it
- and after that, I cannot reproduce anymore the disappearance of lines after saving, I propose to close this issue.
In reply to Considering that:… by cadiz1
I disagree that this issue should be ignored. Issues involving the use of time signatures like this arise from time to time and should be addressed. It should work even though it is not the best way to make a pickup measure.
Agreed, it's worth keeping open, although it's certainly nowhere near as serious as it appeared at first. Would be good to have a simplest case to reproduce from scratch, though.
In reply to Agreed, it's worth keeping… by Marc Sabatella
"Issues involving the use of time signatures like this arise from time to time and should be addressed."
For the record, time signatures are not involved, but local time signatures (as precised by Marc in the new title)
We know there is problems of corruption with local time signatures, and since long years. And some users continue to try to display a pick-up measure as a real time signature. Definitively irrelevant.
So, as long as the problems related to local time signatures are not solved, we have to wait for others. That's why, seeing the origin of this issue (so, local time signature), I closed it.
BTW, there is a few others already submitted (so, this one, in my opinion, is as kind of duplicate of the others, or let's say another aspect/consequence/scenario). Especially since, as we know, a lot of bad things can happen when a score is corrupt.
We have to choose: this problem is fixed (if it is possible one day?), or not. If not, there will be other worries. Or, we live with.
"Would be good to have a simplest case to reproduce from scratch, though."
Which is the volonteer?
Not me, I did my part about this issue.