musescore / musescore/MuseScore

Score corrupted, and becomes re-corrupted after fixing, saving and re-opening

Open
#16,547 0 comments 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since Apr 24, 2023.

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

Description

Describe the bug
Opening this score, saved by MU 4, will result in an invalid score.
You can ignore the loading errors, but you cannot overwrite them .

Even the guides did not work:

Especially saving will not save actual corrected data. The file will be as corrupt as before.

So what actually happened:

  • MS4 crashed (probably while saving)
  • The backup is also corrupted
  • Bars missing, barlines missing, notes missing, notes replaced by whole-bar-rests, upbeats missing and/or merged into the next bar without a time signature change, etc.
  • lots more

To Reproduce

Steps to reproduce the behavior:

  1. Open the provided file
  2. Click ignore
  3. Edit anything
  4. Save
  5. Repeat

Expected behavior

  • Do not save invalid files, not even on crashes.
  • Have a non-corrupted backup
  • Offer a non-corrupted backup
  • Actually save the corrections I did.

Screenshots

2023-02-25T195717_screenshot

as well as

2023-02-25T195748_screenshot

(editing the file and saving does not fix the corruption).

Platform information

  • OS: [e.g. macOS, Windows, Linux]
$ uname -a
Linux wells 6.1.12-1-MANJARO #1 SMP PREEMPT_DYNAMIC Tue Feb 14 21:59:10 UTC 2023 x86_64 GNU/Linux

OS: Manjaro Linux, Arch.: x86_64, MuseScore version (64-bit): 4.0.1-, revision: github-musescore-musescore-7ef0732

Additional context

Choräle für Blasorchester.tar.gz

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.