musescore / musescore/MuseScore

Continue creating tuplets in note-entry mode

Open
#34,260 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

needs design UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

After entering the last note in a tuplet, instead of the current state (creating another non-tuplet note of the same length):

Image

We should create a new set of tuplets of the same number and length:

Image
Problem to be solved

The current UX seems hard to justify.

With non-tuplets, you choose the length of note you want, and enter an unlimited number of notes of that length.

With tuplets, you choose the length of note you want (one third of a beat), and then after three of them, now you are entering a different length of note (half a beat).

It doesn't line up with expected use cases: it's more likely that someone wants to enter 6 triplet quavers in a row than 3 triplet quavers then one or more regular quavers.

It is cumbersome to create a second set of triplets of the same length: you need to choose the crotchet length again (shortcut "5") then triplets again ("ctrl+3"). And thus it's very clunky to enter long series of triplets. (See #34108, #34174...)

However, there are some caveats here. If we simply automatically converted the next beat (or however many beats) into tuplets as soon as this tuplet was complete (and before the user had chosen what the next note is), we'd be potentially doing something destructive and unexpected. (When working with non-tuplets, you can always leave note-entry mode without overwriting or changing anything after the last note you entered.)

Which means we'd probably need some creative new UX, along the lines of showing a ghost tuplet, telling the user "if you enter a note now, you'll be creating tuplets). A hackier version might be that if you exit note-entry mode before entering any notes of the next tuplet, it undoes the creation of the tuplet.

Prior art

No response

Additional context

No response

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing note-entry mode with a completed tuplet, then review the related issues #34108 and #34174 for existing context. The change is complete when consecutive tuplets of the same number and length can be entered without reselecting them, while leaving note-entry mode before the next tuplet remains non-destructive.

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
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.