musescore / musescore/MuseScore

Incorrect repeat in MIDI export when section break is present

Open
#34,871 4 comments 1 reaction 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Sep 11, 2026.

P3 UX/interaction
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
  1. Take the attached score
  2. Open in 4.7.5 (and latest main, but that has a different issue on top, see #34870)
  3. Delete the bogus section break at the title frame (although it doesn't really harm)
  4. Play, notice the playback works and pauses only before the next section, not at the repeats/jumps
  5. Export to MIDI (expand repeats, of course)
  6. Play the MIDI and notice that it doesn't pause at the section breaks at all
    EDIT: notice it pauses at every section break, repeat or not, so shows the very bug that got fixed for playback
Supporting files, videos and screenshots

https://github.com/user-attachments/files/31793375/repeats%40section_breaks.zip

In which versions of MuseScore Studio is this issue present?

Ever since up to 4.7.5. Latest main too, but that has another issue on top, see #34870)

Regression

No.

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.