Keyboard shortcut for note duration: 16th (3) not working
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
Environment:
MuseScore 3.5 Beta
macOS Catalina
Steps:
1. Click on a measure.
2. Press numerical key 3 on keyboard.
Reproduces on both note input mode and select mode.
Workaround is to click the 16th note button on the note input toolbar.
Also, using "3" as a keyboard shortcut in the Shortcuts tab of the Preference dialog only conflicts with "Add fret 3 on current string (TAB only)" despite also being listed as the keyboard shortcut for "Note duration: 16th".
Shortcut still does not work even when changing keyboard shortcut for "Add fret 3 on current string (TAB only)" to something else.
Attachment | Size |
---|---|
Screen Shot 2020-06-14 at 11.36.22.png | 143.78 KB |
Comments
Regression vs. what?
What is the workaround?
What if you try setting all to the defaults?
Also, is it possible you have some of system-wide keyboard macro facility installed that is intercepting this keystroke?
In reply to Regression vs. what? What is… by Jojo-Schmitz
Regression: It works in the latest official release. It regressed in the beta.
Workaround: As said above, "Workaround is to click the 16th note button on the note input toolbar."
In reply to What if you try setting all… by Marc Sabatella
Are you asking me if I set a system-wide keybind for the numerical "3"? Then, no.
Very strange, I can't see any way in which this key is handled different from the other numeric shortcuts, nor do I see any relevant changes.
Just to be 100% sure, can you please attach a sample score and more precise steps - what exactly you are selecting before pressing 3, what note you are entering after pressing 3 in note input mode?
In reply to Very strange, I can't see… by Marc Sabatella
Hold on. I just uploaded to the latest revision (OS: macOS 10.15, Arch.: x86_64, MuseScore version (64-bit): 3.5.0.28145, revision: fb3c202) and it is working again. Would it still be helpful if I revert to the previous version and try to replicate it?
My guess is that whatever was going wrong was a fluke - something about the particular measure you were trying just not supporting changing durations all at once, or a speck of dust in the "3" key. And so even if you do re-install the beta, you might not stumble on that same exact situation. Maybe first see if you can remember the exact sequence and see if it still applies - really, again, nothing has changed in this department recently. If you aren't, since it's working now, I wouldn't worry about it further.
reopen if it happens again