musescore / musescore/MuseScore
Apply uncompressed MuseScore format to a large project by default
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
Why don't we offer some options for default format, or just prompt something when a multi-part score has created by a user to inform the potential risk? I request this since lots of my mates have been annoyed by saving issues.
Problem to be solved
For the users who use MuseScore to build massive projects, they don't want to have any accident when saving their projects. Once the accident takes place, it will make the score corrupted, or, even worse, lose all score data. On this stage, they cannot reopen the autosave file.
Prior art
No response
Additional context
No response
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.
Research direction
No files, tests, or entry points are named. Start by tracing how multi-part scores are saved, autosaved, and assigned MuseScore formats; define done as an agreed default, option, or prompt that addresses corruption and makes autosaves reopenable, then validate it against a large-project scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100