I am experiencing similar problem, specifically with note durations. I am typing on a full keyboard. My regular numbers across the top work just fine to change note durations input. However, on my NUM pad, only 1-3 work (64th - 16th notes); NUM4 - NUM9 will not change note durations, even after reassigning tab input shortcuts to ensure no conflict or even resetting to default. All 9 NUM keys work fine in my Word processor, so it's not the keyboard.
@Baptiste Ramond - I was also able to reproduce your italics shortcut problem and then solve it. I noticed that MuseScore 4 also assigned CTRL+I as default shortcut for "Note input: toggle 'insert' mode", which means by default MS4 came with a conflict at that shortcut. Try changing toggle insert mode to something like ALT+I and see if that fixes your problem.
Comments
I am experiencing similar problem, specifically with note durations. I am typing on a full keyboard. My regular numbers across the top work just fine to change note durations input. However, on my NUM pad, only 1-3 work (64th - 16th notes); NUM4 - NUM9 will not change note durations, even after reassigning tab input shortcuts to ensure no conflict or even resetting to default. All 9 NUM keys work fine in my Word processor, so it's not the keyboard.
@Baptiste Ramond - I was also able to reproduce your italics shortcut problem and then solve it. I noticed that MuseScore 4 also assigned CTRL+I as default shortcut for "Note input: toggle 'insert' mode", which means by default MS4 came with a conflict at that shortcut. Try changing toggle insert mode to something like ALT+I and see if that fixes your problem.
My dotted rhythm (.) works fine
The numpad issue is reported numerous times before and got fixed in 4.0.1 (after a factory reset)
As per https://github.com/musescore/MuseScore/issues/15204 that Shift+6 and . should have been fixed, but apparently isn't, see https://musescore.org/en/node/342796
The Ctrl+i issue is reported in https://github.com/musescore/MuseScore/issues/14496
Still not working on 4.0.2, even after doing a factory reset.
Could this be fixed someday? It's very annoying.
Thanks.
At least https://github.com/musescore/MuseScore/issues/14496 is still open, if that's not what you're talking about, open a new issue on GitHub
In reply to At least https://github.com… by Jojo-Schmitz
There's already a ticket for that: https://github.com/musescore/MuseScore/issues/15204
Please note that the problem does exist since MS3
In reply to At least https://github.com… by Jojo-Schmitz
4.1 dropped and you guys still haven't fixed that basic problem known since MS3. It is so frustrating. Do you plan to fix it for MS5 or...?
I tried musescore 4.5.1 and am encountering the same problem (reason for which I am back to MS3). Is there any workaround for this issue ?
In reply to I tried musescore 4.5.1 and… by leobou
Yes, still not working here, and probably never will.
As both GitHub issues are closed meanwhile, and this issue tracker here has been discontinued, re-report it there