Playback becomes broken after a certain point when a repetition bar line is removed or altered
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Regression has Not been tested.
The attached score tagged CORRUPTED doesn't play after part F, that is, beat 68. Pressing play the second time forces it to start from the beginning.
How to reproduce:
1. Open the attached score Without the word "CORRUPTED"
2. Alter (exchange) or remove the "end repetition" bar line.
3. Try to start the playback from any point after the bar line (part F).
The issue exists only in the attached scores. Removing the other bar line doesn't fix it. No workarounds have been found.
FYI: the attached score is an arrangement from Deltarune's soundtrack. It's not finished but listen to it if you want ;)
Comments
Where are the files that I have attached? I can't see them.
Uploading again:
Field of Hopes and Dreams kameralne CORRUPTED.mscz
Field of Hopes and Dreams kameralne.mscz
I don't understand. If you remove the end repeat, the score is now incorrect notation, and it's not at all clear - to MuseScore or to a human musicians - what should be expected. A start repeat and voltas without and end repeat is undefined.
Removing the start repeat isn't enough to make the results well-defined, true - you need to remove the voltas too.
On the other hand, it would be nice if issues like this didn't stop playback entirely. So I'm leaving this open, but it's nowhere near critical.
Ok I've just found the solution and this changes the cause of the bug. There was a seconda volta left. Removing the repetition end bar line AND the seconda volta makes playback possible. Removing only the repetition end bar line breaks playback when seconda volta is in place.
I had marked it as critical (for me) but since it only partially broke playback, it was probably major, without the workaround.
In reply to (No subject) by Jojo-Schmitz
Does "Frequency" count the report it's in, or only separate reports? I couldn't find any others.
"Frequency" counts how many people have reported the bug, here in this issue or in others.