MuseScore 4: NumPad not functioning
Any word on a fix for this? I really cannot use MuseScore without the numpad. I'm going to have to stick with 3 until its working in 4.
Do you still have an unanswered question? Please log in first to post your question.
Comments
Yeah, this is frustrating. If you press N, the number pad functions -- but only for choosing quarter notes. Hopefully this will be corrected in an update, because it takes a lot longer to enter notes if you're restricted to continually clicking on the menu bar.
You can follow the issue progress here: https://github.com/musescore/MuseScore/issues/12791
The fix described in https://github.com/musescore/MuseScore/issues/12791 takes about 10 minutes to do (assuming you don't know your way around exporting the shortcuts xml file, adding in the num pad short cuts, then importing it back). It's totally worth doing.
Basically, you do the following:
1. Edit > Preferences > Shortcuts > Export
2. Specify local directory, name file, and save it in your local directory. (You might want to save a second copy as a backup, just in case.)
3. Open the xml file in a plain text editor like Notepad++
4. Search for the following strings in the file, one at a time:
<key>pad-note-64</key>
<key>pad-note-32</key>
<key>pad-note-16</key>
<key>pad-note-8</key>
<key>pad-note-4</key>
<key>pad-note-2</key>
<key>pad-note-1</key>
You will find "key" entries like this:
<SC>
<key>pad-note-16</key>
<seq>3</seq>
</SC>
Add a second "seq" entry as follows:
<SC>
<key>pad-note-16</key>
<seq>3</seq>
<seq>Num+3</seq> <===NEW ENTRY
</SC>
Ignore the "TAB" entries (e.g. "pad-note-16-TAB") and and "fret" entires (e.g. "fret-6") which also contain "seq" strings for number pad keys (e.g. "<seq>3</seq>").
In reply to The fix described in https:/… by Pat Richman
Thanks for the detailed procedure. It didn't quite work for me, though. After I re-saved the file, MS4 refused to import it, saying it wasn't a valid XML file. I used TextEdit (in Plain Text mode) to edit it. Is there a different app I should use?
In reply to Thanks for the detailed… by Jay-Ducharme
Hmmm, does the file that you saved locally end with the ".xml" extension, or something like ".txt"? Attaching the file I edited for my Windows machine to do this fix in case it's useful to you.
In reply to Hmmm, does the file that you… by Pat Richman
The other thing I can think of is that you accidentally typed a stray character (maybe even an invisible character like a tab or space) into the file somewhere, and thus the file isn't 100% valid xml. There are online xml validators that might help you find what exactly isn't valid in your file. You can google "xml validator online" (or "xml validator online reviews" or "xml validator online reddit" if you want to read opinions from people who might favor a particular one).
In reply to Hmmm, does the file that you… by Pat Richman
Woohoo! Your file worked. Thank you!
In reply to Hmmm, does the file that you… by Pat Richman
Hi. It's work for me. THX!
In reply to Hmmm, does the file that you… by Pat Richman
Much obliged!
In reply to Hmmm, does the file that you… by Pat Richman
Thanks for the fix !
Malachi O'Sullivan
In reply to Hmmm, does the file that you… by Pat Richman
YAY! Thanks!! (It's still relevant... in 2024)
In reply to The fix described in https:/… by Pat Richman
Finally it works.....!! Thanks a lot, Pat.
See #336170: Number Keypad keys not definable for keyboard shortcuts
In reply to See #336170: Number Keypad… by Jojo-Schmitz
Thanks, Jojo. I did see that. But my problem is that MS4 won't import the new XML file I save. Perhaps if I were able to edit the parameters directly in MuseScore, it would work. But exporting the shortcuts as XML seems to be a dead end for me right now.
In reply to Thanks, Jojo. I did see… by Jay-Ducharme
That's what I was trying to avoid was a lot of coding that doesn't have to do with music composing. That's why also I abandonned the "other" free music notation software program..I want to avoid our colleagues "dead end". By the way, I love Musescore and I just started to use 3.0 when the 4.0 update came along. 3.0 was working with the Num Pad. Much appreciate if this can be fixed please in an update because it seems many users are having the same issue. I also commented on Github about this. Thank you in advance. And thank you for such a wonderful program. It really changed my life so it's appreciated!
In reply to That's what I was trying to… by liferesearcher57
A lot of coding? Well, you have just have to follow this quick and easy procedure.
To be safe, close all open MuseScore windows before doing the below. Then:
In reply to A lot of coding? Well, you… by cadiz1
That's amazing! Thank you so much! Worked perfectly. :)
In reply to A lot of coding? Well, you… by cadiz1
Thank you! Worked perfectly.
In reply to A lot of coding? Well, you… by cadiz1
Thank you so much! Works great.
In reply to A lot of coding? Well, you… by cadiz1
You are a god, THANK YOU
Same, the numpad is the area of the keyboard I use the most in Musescore. How had it not been tested I wonder? It's definitely a core part of the program.
In reply to Same, the numpad is the area… by StratfordMusic
It has been tested and complained about before the release...