musescore / musescore/MuseScore
Iterative Chord Voicing and Inversion Shortcut
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
Add a keyboard shortcut or palette tool to iteratively cycle through chord voicings (e.g., root position, inversions, close/spread voicings) for a selected chord or realized chord symbols.
Problem to be solved
When using "Realize Chord Symbols" in MuseScore, the default output can place notes awkwardly (e.g., the bass note an octave or more below its "chordmates"). Adjusting the voicing manually involves selecting individual notes, using octave shifts, or adjusting them step-by-step, which is cumbersome and time-consuming.
Prior art
No response
Additional context
Proposed Behavior
- Shortcut Key
- A user highlights a realized chord.
- Pressing a defined shortcut (e.g., Ctrl+Shift+V or similar) cycles the chord through:
- Root position → 1st inversion → 2nd inversion → Spread voicing → Back to root.
- User-Defined Voicings:
- A palette or settings menu allows users to specify chord voicing presets.
Optional Alternatives:
- Confine to Treble/Bass Clef: Realize voicings or adjust notes to stay within the selected clef.
- Dynamic Range Options: Restrict chord note placement to a specific octave range.
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 implementation files or tests are named. Start by locating the existing “Realize Chord Symbols” action and its shortcut or palette handling, then clarify the supported voicing cycle and completion criteria before scoping implementation.
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
- 30/100