musescore / musescore/MuseScore
Incorrect repeat playback when multiple section breaks are present
@RomanPudashkin is already working on this.
Since Sep 10, 2026.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
- Take the attached score
- Open in latest main
- Delete the bogus section break at the title frame
- Play, notice the playback doesn't work but pauses at the 2nd and subsequent repeats/jumps rather than after having processed them
For some strange reason 4.7.5 is not affected by that.
Problems even happens with just one section break, if the 2nd section ends with a repeat or jump
Supporting files, videos and screenshots
https://github.com/user-attachments/files/31793375/repeats%40section_breaks.zip
See video from https://github.com/musescore/MuseScore/issues/14262#issuecomment-5589349816:
https://github.com/user-attachments/assets/cf900eb8-449e-4733-8770-1c9cb5523917
In which versions of MuseScore Studio is this issue present?
latest main
Regression
I was unable to check, it might have worked with an earlier version of main, some time between now and the merge of #34350, as it still does work in 4.7.5, which had the same fix backported
Operating system
Windows 11, but that hardly matters
Additional context
See https://github.com/musescore/MuseScore/issues/14262#issuecomment-5526873001
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.