musescore / musescore/MuseScore
Corrupt Score after simple edit
@cbjeukendrup is already working on this.
Since Dec 5, 2023.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Choose option...
Bug description
I wanted to make a simple edit. The rhythm in m16 is displaced. I wanted to edit all of the measures that were identical m36 m41.
It wouldn’t let me save without saving a a corrupt file. The error message said it was an incomplete measure. After another attempt it said the measure was showing up as 19/16 time signature.
Oddly that is a time signature from another piece I’m currently working on. In Musescore 3 the actual piece I worked on in 19/16 caused all kinds of issues and corrupted. I decided to start that piece over in Musescore 4. It’s interesting that this is happening but in a different piece.
I tried to attach the mscz file but it wouldn’t attach. I’ll see if it will after I upload this thread.
Steps to reproduce
Delete m36.
re-enter correct rhythm
File goes corrupt.
Screenshots/Screen recordings
No response
MuseScore Version
4.1.1.232071203
Regression
Choose option...
Operating system
macOS Sonoma 14.1.1
Additional context
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.