Keyboard values not working

• Aug 16, 2022 - 13:20

If I use the numpad to enter notes, I cdan only enter crochets. Whether numlock is on of off makes no difference. This is quite contrary to the behaviour in 3.6. I find the claim that entering notes is not much different in either version to be substantially untrue as far as Alpha 1 is concerned. Any ideas why? I also can't change key-signatures time-signature, number of bars, speed of beats, Anacrusis, and -- well, that's enough to be going on with. I also can't get Palettes to work, not add title, subtitle, composer, etc. I'm not happy!


Thanks for the feedback! Right now there do seem to be known issues using the numeric keypad specifically on some systems. This is still being investigated. For now, though, the standard numeric keys on the top row work fine on all keyboards. FWIW, this was also true with MuseSocre 3 - some keyboards just didn't work with the numeric keypad for whatever reason, while others did.

As for key and time signatures etc, as mentioned in my tutorial, it does seem that NVDA specifically has problems with the score wizard. That's why I recommended skipping that and simply adding those things normally from the palette (for key and time signatures, tempo, etc) and/or menus (for measures, title, composer, etc). Or, try a different screen reader - Narrator is able to read the score creation wizard just fine. Not sure about JAWS.

Elsewhere you mentioned using F9 to access the palette search. That's not actually the correct shortcut. That's for opening and closing the palette, which you shouldn't need to be doing. Just leave the palettes open, and use Ctrl+F9 to access the search. This is actually the same as we have always recommended for MuseScore 3 - leave the palettes open, use Ctrl+F9 to jump directly to the search box.

In reply to by rogerfrdhm

Just use the regular period - on most systems, it's to the lower right portion of the keyboard, near the Ctrl and Shift keys, usually next to the comma to the right of the letter M.

The shortcut for rests is the number 0.

With Narrator, as I said, it actually is reading all the keys, it just isn't reading the accidental. Go to the B major, then hit the arrow to hear it read the next key. You will hear it read "F", but what I'm saying is, it really is F sharp. It's just that Narrator doesn't know how to read the sharp symbol correctly. So as I said, it's something we're looking into finding a solution for.

But anyhow, again, yes, this section of this dialog is not as good as it could be, so I recommend just adding the key from the palette later. That's what I normally do anyhow in MuseScore 3; I almost always skip right past the places in the wizard where you can select these things.

Do you still have an unanswered question? Please log in first to post your question.