Issues entering notes in drum kit

[ManzoroB]

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

1.- Select any drum kit. 2.- Try to enter a note. 3.-It behaves as if it were constantly entering the note. With 2 notes crushes. 4.-Only stops with "ESC" key.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/eb27339f-bc9e-456d-8e56-a9589a0caf03

What is the latest version of MuseScore Studio where this issue is present?

OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

AVL-MXe-23.4, this is mostly Debian 12 Bookworm

Additional context

No response

Checklist

• [X] This report follows the guidelines for reporting bugs and issues
• [X] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• [X] I have attached all requested files and information to this report
• [X] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[MarcSabatella]

Probably you have a MIDI loop on your system - you have MuseScore configured to send output to a device that is then also returning it to MuseScore as input.

If you need help diagnosing this or other problems, or if you have other questions about how to use MuseScore, please ask on the official Supoort forum at MuseScore.org.

[ManzoroB]

I'm sorry, you are completely right. I didn't identify it because the problem only occurred in the drumkit. All other instruments worked perfectly well. And the change in that setting happened on its own, when I started musescore without my midi controller like I usually do.

Thanks Marc.

[bkunda]

This is the second midi-loop-related issue on Linux I've seen today (see also this one).

Good deductive work there @MarcSabatella!

I'm curious about this though:

the change in that setting happened on its own

Did you notice this issue shortly after updating MuseScore? Is this the first time you opened this particular score since updating to 4.4.2? Does it only occur in this score (containing a drumkit)?

I'm just wondering whether there's another bug in the mix here. There are a number of known issues with MIDI output, so this might just be another one to add to the mix when it comes time for us to address it.

[cbjeukendrup]

See also what I said last month on Slack:

Since 4.4 is out, we’ve had a suspicious amount of reports of MIDI loops, seemingly all from Linux users; I think too many to be a coincidence. Does anyone have an idea what might cause this? We can’t and needn’t really take action on this yet, but it might be good to keep it in mind.

Some examples: https://musescore.org/en/node/368518 https://musescore.org/en/node/368087 solved it by reinstalling MuseSounds ????? https://github.com/musescore/MuseScore/issues/24264

And then:

AH, I know what must be happening. MIDI output is only active when MS Basic is used (that’s weird, but that’s how it is). Everyone was presumably using Muse Sounds with MS4.3.2; so as long as Muse Sounds is used, there is no MIDI output, and also no MIDI loop. But since 4.4, MuseSampler 0.6 is required, and apparently for many people Muse Hub (or Muse Sounds manager) has failed to update MuseSampler. That means that MS 4.4 cannot find Muse Sounds (it ignores the too-old sampler) and falls back to MS Basic. So now there will be MIDI output, and suddenly the MIDI loop (that was already latent) manifests. That explains why someone said that it was fixed by re-installing Muse Sounds.

To verify this hypothesis, @ManzoroB, could you tell us what sounds are being used in the Mixer? (MS Basic or Muse Sounds)

[MarcSabatella]

The other thing I wonder about given comments I've seen is that people had no idea MuseScore was trying to use their MIDI device. I wonder if 4.4 is autoselecting MIDI devices in some cases where previous versions didn't.

[ManzoroB]

In fact, I just restarted musescore and apparently it didn't recognize my midi controller the first time, leaving a midi loop with the input and output of midi connection of my audio interface by default. Very good point.

[bkunda]

We suspect this might have been caused by some change in linux distributions. If this proves correct, then one thing we might consider is to include some messaging when this is happening so it's clearer to the user that a loop has been created.

[bkunda]

Closing for now as it appears the symptoms of this problem have at least been solvable for the cases in which it has been raised. Happy to reopen if it proves persistent.