Cannot increase the duration of a chord/rest within a nested tuplet.
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
Create triplet eighth notes from a quarter note via ctrl+3; divide one of the resulting triplet eighth notes into 3 - 16th notes (16th triplets) via ctrl+3; from there, unable to create (eighth +16th), (16th+eighth) or (dotted eighth) combinations within the 16th note triplet. The only workaround for me has been to beam the notes to get the desired combination. The result is way more notes (16ths) and clutter in the piece than necessary. Wonderful program! Thank you!
Dale Vig (EGad)
Fix version
3.5.0
Comments
I try and I can' t . But I think, such a thing is unplayable for "normal" musician.......
In reply to I try and I can' t . But I… by Raymond Wicquart
Thanks for your reply. As far as being playable, I suppose it depends on the tempo. The score I am working on is in a blues style where each quarter note has a triplet feel and at times the melody or solo is yet another division of that. Perhaps another time signature such as 12/8 or something might be more technically correct or at least another work around. Investigation continues. Thanks, again!
In reply to Thanks for your reply. As… by dalewesleyvig
Perhaps it works in 12/8 I don't try.....to morrow......
You're a good guy, thanks! I kinda think it should work regardless of time signature, tho.
MuseScore does indeed prevent you from increasing the duration of a chord or rest within a nested tuplet, but it does not prevent you from overwriting the chord/rest with a chord/rest of a longer duration. So the workaround is to enter note input mode (or never leave note input mode in the first place), select the desired duration, and enter the new note on top of the old one.
This limitation was introduced with commit c1b55b0, presumably because this calculation would fail in the case of nested tuplets. That calculation has since been replaced with a more general solution, so it should be safe to remove the two lines that cause the function to return early in the case of nested tuplets, which is what prevents the operation from doing anything.
See https://github.com/musescore/MuseScore/pull/5678.
Fixed in branch master, commit d6a80d6c13
fix #300718: Cannot increase the duration of a chord/rest within a nested tuplet.
Fixed in branch master, commit 32812a2fb9
_Merge pull request #5678 from mattmcclinch/300718-nested-tuplet
fix #300718: Cannot increase the duration of a chord/rest within a nested tuplet._
Automatically closed -- issue fixed for 2 weeks with no activity.