Drum-Notation on MacOS broken?
Whenever I try to enter a drum-note Musescore switches to "machine-gun-mode" and keeps entering notes as if I had never released the key. Same with mouse-input.
Regular scores work fine and on Ubuntu 23.04 all works fine.
Don't know if this is a known bug or just my install but behaviour persists since 4.0 update - any help appreciated!
Intel MacBook Pro, MacOS Monterey 12.6.8, Musescore 4.1.1
Comments
That definitely shouldn't happen, and I don't think there are any known other reports of it. can you attach a score and precise steps to reproduce the problem? I doubt we'll be able to as I can't think of anything that could be happening in your score that would cause this. But it will be an important first step to rule out before we start trying to figure out what's different about your keyboard or mouse or operating system or settings.
In reply to That definitely shouldn't… by Marc Sabatella
Okay, I've got it:
I have a virtual midi bus configured in my system (for internal midi routing) and in Musescore preferences / I/O this virtual bus was configured as both MIDI input and output (don't know if Musescore took the first available as default or if it was my fault). This obviously created a feedback loop.
Setting the MIDI input/output to "no device" in preferences or disabling "Toggle Midi Input" under the menubar cogwheel fixed it.
Still puzzling is why this only affected note input in drum-notation, regular scores (at least piano scores) worked well?
But thank you for confirming that the problem was on my side - I eagerly waited for each new Musescore version to fix this problem :)
In reply to Okay, I've got it: I have a… by marcusBvS
Glad you got it fixed, but - yeah, that's really surprising the loop would only cause a problem for percussion. Maybe it's because percussion normally uses a dedicated channel (10) and the loop only existed on that channel?
In reply to Glad you got it fixed, but -… by Marc Sabatella
nope, the IAC driver bus routes all MIDI channels. Perhaps the additional processing (MIDI mapping / voice selection) in the percussion editor introduces some latency which lets Musescore recognize the event returning from the loop as a new keystroke instead of a simple key bounce. Only a wild guess and I don't think it values the pain to investigate this further.
I can confirm though that Musescore did choose the bus as MIDI in/out device by default (probably because it gets reported by the system as first). At least in my case it would have been better to default to the "no device" setting, but I reckon for 99% of all users the current behaviour is more convenient.
So it all boils down to you knowing where to look when someone complains about Musescore machine-gunning notes into the score and btw thank you for your unremitting support!