Support for entering 256th, 512th and 1024th notes/rests

• Jan 10, 2015 - 07:54
S5 - Suggestion

Whenever making a 128th triplet in 4/4 time the according rests don't get shown (256th rests). Also the only time 256th's flags are shown is when the triplets are filled with notes not when you put note, rest, note in that order in the triplet. I first click the 128th note and then the ctrl+3 keys and I get some visual corruption as well.

OS: Arch Linux
Release: Musescore 2.0 rev. 7771.68600ec (built from the aur with qt5).

Attachment Size
128th triplet broken rests.png 23.02 KB


For the record, we don't support 256th notes, but of course we should not create corruption either. We should simply disable creation of tuplets with 256th's as the value.

Yes, thanks for the link, I had remembered that there was talk of this at one time but didn't know the status.

PR looks good for what it is, but tuplets would need to be handled differently. It's not enough to disable the tuplets commands for 128th notes; we would also need to disable certain tuplets for *any* note value (eg, Ctrl+9 on a 32nd note).

I've been looking for an excuse to deal with the issues raised in, and having already looked at that, I know it's the exact same chunk of code where we'd want to be testing the results. I will look at all of these when I can, if no one else does first.

Severity S4 - Minor S5 - Suggestion
Status PR created active
Reported version 2.1  
Regression No
Workaround Yes

PR got closed, such short notes are possible (in 3.1 at least), but there's no direkt method to enter them. Only method is to enter a 128th and half its duration (if needed several times) by use the corresponding shortcut, Q

Title Broken 128th triplet (rests), support 256th, 512th and 1024th notes/rests Support for entering 256th, 512th and 1024th notes/rests
Fix version