musescore / musescore/MuseScore
Two tuplet entry modes
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
To make Musescore more intuitive, we need an alternative tuplet entry mode in the Custom Tuplets Dialog. Both tuplet entry modes need to be implemented, and there should be a little toggle in the dialog that helps you to switch between both tuplet entry modes. The tuplet presets and keyboard shortcuts should use the default type.
How to use it
The intuitive tuplet entry mode is called "Expansion", and the default tuplet type is called "Compression". The compression type splits into the selected note into that many notes as typed in the X-box, and they are notated as the note as the fraction of the selected note 1/Y-box.
The expansion type creates the tuplet across as many notes as the selected note as typed in the Y-box, and puts that many notes as the number in the X-box in that space.
Try to do this as soon as possible.
Problem to be solved
The workaround at https://musescore.org/en/node/260646 and https://musescore.org/en/node/331197 will no longer be necessary, you can just use the expansion type.
Prior art
Flat and Soundslice use the expansion type for tuplet entry.
Additional context
In the "Ratio" field, the box on the left is the X-box and the box on the right is the Y-box.
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 Custom Tuplets Dialog and its existing Compression behavior. Review the two linked workaround discussions and use the X-box/Y-box definitions to clarify the requested Expansion behavior. Done means the dialog can switch between both entry modes while presets and keyboard shortcuts retain the default type.
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
- Mostly clear
- Newbie friendliness
- 35/100