duplets, quadruplets etc are messed up in 3/4, 6/4, 6/8, etc

• Jun 16, 2021 - 14:09
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
by design
Regression
No
Workaround
Yes
Project

duplets, quadruplets etc are F***ed up in 3/4, 6/4, 6/8, etc .
This does not make any sense when writing music in 3 time we have to make use of duplets or quadruplets. it is still okay in 2 time music with triplets and other odd tuplets.

Attachment Size
buggy duplets in _musescore.mscz 10.53 KB

 Frequency Many ⇒ Once
 Status active ⇒ needs info

You don't say exactly what you are perceiving to be a bug. MuseScore allows you to create a wide variety of different types of tuples. If you don't want duplets, don't create them,. Or if you want them notated differently, simply use the Add / Tuplets / Other dialog to set them up how you like.

If you believe there to be a bug where attempting to create one type of notation actually creates a different one, please list precise steps to reproduce this. And also, please try to do so without profanity.

 Title duplets, quadruplets etc are F***ed up in 3/4, 6/4, 6/8, etc ⇒ duplets, quadruplets etc are messed up in 3/4, 6/4, 6/8, etc Frequency Once ⇒ Many Status needs info ⇒ active

Look. suppose I try to add a triplet from the tuplet menu in a score which uses a time signature of say 4,4 time, then it is okay. Does fine, it shows that TWO beats could be divided into THREE.

NOW, if you use suppose 6,8 and then try to use a duplet from the tuplet menu, to get THREE beats all together divided into TWO, technically which means each beat getting a value of ONE POINT FIVE, but instead of writing it so, we need to simply add a duplet for the ease of reading. But that exactly is not working even when instructions are followed as stated in the handbook : https://musescore.org/en/handbook/3/tuplets#instructions as @Shoichi pointed out.
there are many it seems who has the same problem https://musescore.org/en/search/content?keys=duplets
I am adding once again another simpler .mscz file to explain my pain.
I am also attaching the photo of the precise thing i want but cannot achieve which is already mentioned in the handbook.