musescore / musescore/MuseScore

Necessary improvements on the UI of tuplets

Open
#18,980 9 comments 6 reactions 4 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea
image

At the moment, it is not possible to create this tuplet in Musescore. This is a very silly limitation, considering that the screenshot above is obtained... in Musescore.

I have realized this example by writing the tuplet manually into our file, to prove that our system is already perfectly capable of representing and handling such tuplet. The problem is a purely UI one, meaning that we don't have a flexible enough UI to allow creating it.

Problem to be solved

In Musescore, a tuplet can only be created by selecting a single rythmic figure and turning it into a tuplet. The natural consequence is that we can create tuplets only for those durations that can be represented by a single figure. Consider this example.

I can easily create a 3:4 tuplet inside the 9-tuplet, because I can compress the last 4 quavers into a single 2/4 figure. However, I can't create a 3:5 tuplet, because there is no single figure which can represent a duration of 5 quavers.

https://github.com/musescore/MuseScore/assets/93707756/b15a694e-3171-43d9-9ac4-bc6a2fafe96f

I think that the most naive solution here is just to change the UI so that the tuplet isn't entered on the duration of the figure, but on the duration of the selected range. This way, the tuplet can be entered into any duration, not just the ones representable by a single musical figure. In principle I think it could be done quite easily. However, maybe the whole tuplets UI needs some design consideration.

Prior art

No response

Additional context

No response

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.