musescore / musescore/MuseScore

Auto fix corrupt time signatures

Open
#23,706 0 comments 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since Jul 23, 2024.

corruption feature request 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

Open the attached mcsz file, it reports 'File “” is critically corrupted and cannot be processed.'
Unzippind examining the mscx finds a few measures with invalid time signatures which are multiples of 1920, eg should have been 8/4. I edited the .mscx in the zip, fixed the measures, and it opens fine.

This came from a MIDI file whjch I opened and edited, also attached renamed to .txt FYI.
.mid is not an allowed upload type, why not?

I suggest that any multiple of 1920 should be auto-fixed to multiples of 4, or ask the user what base to use (2,4,8...)
gregorian-dies-irae - Copy.mid.txt

Supporting files, videos and screenshots

gregorian-dies-irae D JV Nuffel.zip
gregorian-dies-irae - Copy.mid.txt

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2

Regression

I was unable to check

Operating system

Win 10

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.