A feature: File>Cleanup... to remove unused stuff from the project
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
The old projects have unused mixer channels (64 total).
Sometimes we get an empty automation track or a B+B pattern that's of no use.
Sometimes an instrument with no notes to play.
Or muted B+B clips that could as well be deleted.
I thought about adding a little dialog under File > Cleanup with several chekcboxes:
*\* Clean up **
[ ] Unused mixer channels
[ ] Empty automation tracks
[ ] Empty audio tracks
[ ] Unused instruments
[ ] Unused B+B patterns
[ ] Muted B+B clips
[ ] Muted instrument clips
[ ] Muted automation clips
[ ] Muted audio clips
[ ] Disabled effects in the mixer (unless they are enabled by automation)
[ ] Disabled effects in instruments
[ ] Dummy effects
It'd be also nice if the dialog could perform a test cleanup in the background and show the estimated change in project filesize after the cleanup.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or implementation entry points. Start by tracing the existing File menu and project cleanup-related behavior, then define completion around the requested cleanup choices, safe handling of enabled or used items, and the background estimated filesize change.
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