musescore / musescore/MuseScore

Local time signatures (sometimes) corrupt score by failing to update empty measure rest values

Open
#33,773 2 comments 0 reactions 3 assignees View on GitHub

@ajuncosa is already working on this.

Since Aug 11, 2026.

corruption P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

File corruption

Description with steps to reproduce

I can't reliably reproduce it (thus, "sometimes"). I thought it was easy to reproduce (and actually got to do it a bunch of times on new, minimal scores). But when trying to pinpoint the exact cause, it started to not corrupt the score and now I can't get to reproduce it on new scores.

I have a score where it happens that I can attach, though. Perform these steps on the attached score.

  1. Add a local 2/4 time signature on top of Tuba's hidden time signature (one after F, bar 109).

  2. Try to save the score.

  3. It says it's corrupted because of some incomplete measures on Tuba (116 to 126, marked red).

  4. Revert to last saved state.

  5. Add the local time signature again.

  6. This time, select from the red measures to the end and clear their contents (they were already empty).

  7. Try to save the score.

  8. Now it does save it properly.

Supporting files, videos and screenshots

Juny.mscz.zip

In which versions of MuseScore Studio is this issue present?

4.7.2-260525085

Regression

I was unable to check

Operating system

macOS Sonoma (14.5), Arch.: arm64

Additional context

No response

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.