musescore / musescore/MuseScore
Bar set variations / versions
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
Interface for multiple branches (spanning few bars). Instead of copying around A-B1-C-[empty bars]-(A)-B2-(C), allow A-B-C, where B has a selector for the currently active version.
Bonus: Sometimes the variation is only a few notes ("This E♭ could be a C"), it could be shown as a faint ghost?
Problem to be solved
I transcribe recordings with multiple takes, where I'm not quite sure which one is the best. I add empty bars for the other takes, and copy-paste a lot over. System text is used to keep track which part is supposed to link with what, and randomly-generated alphanumerics to link the parts to the recording markers in Reaper.
Experimentation, as well, is slow and messy. It demands discipline to label everything, save-close file-duplicate-label-open copies-keep track which is which.
Prior art
Similar workflow I've seen people use in Ableton Live timeline: disabled clips.
Additional context
This feature could be extended by plugins for better writing of performer-picks cycles popularized by Philip Glass.
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
No files, tests, or entry points are named. Start by mapping how MuseScore represents bars and edits notation, then examine the desktop interface areas involved in selecting alternate versions. Done would require an agreed design and implementation for multi-bar branches, version selection, and the optional faint variation display.
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