musescore / musescore/MuseScore
Enable user to have augmentation dotting be retained or not when applying durations
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
Someone (https://musescore.org/en/node/317384) about three years ago mentioned that they find it extremely annoying to have augmentation dotting "retained" while in Rhythm-Entry since it's meant for "speedy" entry, all the while regular note-entry doesn't retain it. I tend to agree. Seems like nothing came to fruition about it though...
As for why the agreement, instead of merely assuming it to be self-explanatory, here is some exposition: if your pattern of rhythm consists of non-consecutive augmentations, the following note entries post-augmentation feel "clunky" if extra note-input activity has to occur (untoggling) first before placing their rhythm information. it's nice to be able to type numbers, and when coming across an augmented note, merely apply it to the note that needs it and be done with it without requiring de-toggling. Minimal activations, less thinking. And in the case that many consecutive augmentations occur, using regular step entry first to retain them before re-pitching is a decent workaround.
Allowing for augmentation to not be retained or to be retained in some user-accessible fashion would be a nice feature, but either that means dropping the "retainment" in rhythm-mode or have some sort of means to allow the user to do so or not as they see fit in the moment, regardless of input-mode. Not sure how you'd go about implementing that.
Problem to be solved
Being annoyed having to untoggle augmentation after placing an augmented duration within rhythm-entry mode when the following entry is to be non-augmented.
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 tracing how duration input behaves in rhythm-entry mode and compare it with regular step entry. Determine whether the feature should disable retention in rhythm-entry or expose a user-controlled setting. Done means augmentation retention follows the chosen behavior without disrupting duration entry.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100