Add Interval Below Note NOT Working Currently
After updating to Musescore 4.4 on my Macbook, my shortcuts for add interval below stopped working. I have them set to control with the number for adding the interval, for example control-3 to add a third below. You can see my preferences in the screenshot. After this update they no longer seem to work. Normally I can just click on a note, use my shortcut, and it will add the interval below. Now when I do that, nothing happens. I tried deleting the shortcuts and redoing them but to no effect. Is this a bug of this update, is anyone else experiencing this, and does anyone have a workaround? (Please don't say, drop the note an octave and then add interval above, that's not a great workaround for some situations).
Thanks!
Attachment | Size |
---|---|
Screenshot 2024-08-29 at 10.15.26 PM.png | 131.96 KB |
Comments
Came here to say a similar thing, for different shortcuts. Something definitely feels broken here. At first none of my shortcuts were working properly (even, like, add a hairpin dynamic). I restarted the computer. I tried using the laptop keyboard instead of my normal keyboard. Same thing. I tried reinstalling my shortcuts. The only thing that kind of helped was resetting all shortcuts to default. But then when I try to customize them again sometimes it works and sometimes they just don't no matter what I do. Separately, or maybe relatedly, the Numpad on my keyboard which previously worked fine is now seemingly an alien.
In reply to Came here to say a similar… by chrismcqueenmusic
I should say, Macbook Pro over here. It could be specifically the Mac Ctrl key. That's the one I'm having an issue with and it looks like you are too.
In reply to I should say, Macbook Pro… by chrismcqueenmusic
Don't think it's specifically related to the Ctrl key, I have shortcuts that use Cmd and aren't working as well. All of my add interval shortcuts stopped working since the update. Luckily, I use a midi keyboard here and can write my chords with it but can't do it while I'm on the go.
Best report this on GitHub