musescore / musescore/MuseScore
Abilities to reset Mixer Panel Settings to Default / Revert Mixer Panel changes to "new-score" layout. (i.e. All Volumes reset to 0 etc...)
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
It would be helpful if there were a way to revert all changes in the Mixer Workspace Panel back to "New-Score" defaults (All 0 volume, 0 L/R Panning, 0 Reverb, and Empty Aux Channels (aside from the Musesound Default MuseReverb Aux Channel 1, as would be default for a new score))
Problem to be solved
This would resolve the issue of a User having to reset all sounds, panning, and sound FX settings to 0, and/or remove all Aux Channel settings, manually, by systematically going through each and every instrument sound, 1 by 1, to complete this task. (Especially on Music Scores that have 10+ individual parts)
Prior art
No response
Additional context
Ran search queries for this issue/suggestion, and was unable to locate any. If I skimmed it over, please disregard this issue. I am a NEW New user to Github, and apologize for any mistakes made during this issue / feature request drafting.
Checklist
- This request follows the guidelines for reporting issues
- I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
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
Start by locating the Mixer Workspace Panel and the code that applies New-Score defaults; the issue names no files, tests, or entry points. Define the reset behavior for volumes, panning, reverb, and Aux Channels, preserving the default MuseReverb Aux Channel 1, then verify it on scores with multiple parts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100