Two tuplet entry modes

[VighneshJadha]

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.

[cbjeukendrup]

Try to do this as soon as possible.

This is a rude thing to say, said in a very rude way. It's rude towards us, who work hard on MuseScore every day, and towards your fellow MuseScore users, who have logged many issues that are more critical than this one. Of course we do things as soon as possible. What did you think? That we are permanently on vacation? Or that we are lazy? The fact that we cannot implement all requests within a few days is that we handle requests in a sensible order of priority.

[RobFog]

Sadly, it's not the first this user does that: #23196.

[LucySuccubus]

Please refrain from comments enforcing a timeframe for developers to work on your requests and reports. Let them work their intended pace. If you really want to speed things along, you can help by continuing to make well-written and documented reports/requests, and connect issues that are related to eachother as best as you can. A bonus would be checking out other reports/request, investigate on them by testing and checking the comment threads, and engage in ways that can be helpful to identify and verify aspects of the problem in the report/request.

It's wonderful that we have a community that wants this app to be better over time, so let's be best at our part by providing the best help we can outside the coding board.