Use of MIDI keyboard in Ubuntu
Reported version
4.0
Type
Functional
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Using Ubuntu 22.04, Musescore 4 does not recognize my MIDI keyboard. The keyboard worked fine in version 3.2.
Under Preferences ... I/O ... MIDI input lists no device.
MIDI output lists KeyRig 49, but this is an input, not an output device.
OS: Ubuntu 22.04.1 LTS, Arch.: x86_64,
MuseScore version (64-bit): 4.0.0-223472159, r
evision: 5485621
By they way, the new layout looks great!
Comments
Same problem here on Archlinux, only lists "no device" for both input and output.
I'm also having this problem. I'm on Arch Linux, using MuseScore 4.0, and trying to connect VMPK to MuseScore for note input. My system is using PulseAudio and I get the following output from
aconnect
:So it would seem that VMPK exposes itself as a MIDI device to ALSA, but MuseScore does not.
Historically I have used JACK and I saw another report that this is removed for now in MuseScore 4.0. But the documentation and UI don't tell me what MIDI backend is actually being used on Linux now, so I have no idea how to set it up! Do I have to use Pipewire or something instead? How can I get MuseScore to see my ALSA MIDI devices?
Same error for me. Tried with pipewire and without on linux mint 21.2
aconnect -i
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 32: 'masterkey 49' [type=kernel,card=4]
0 'masterkey 49 MIDI 1'
How do I submit merge request, or patch? Error looks to be a pretty simple to fix https://github.com/musescore/MuseScore/blob/master/src/framework/midi/i…
port capabilities should be read insted of write
SND_SEQ_PORT_CAP_SUBS_READ | SND_SEQ_PORT_CAP_READ
I've attached a patch, tested on linux mint 21.2 on commit 01139e235fdaf189bca76faa017b6d32a3040c6e
See https://github.com/musescore/MuseScore/pull/19717
I notice that my MIDI keyboard (RIG49) now works in MuseScore 4.2. Thank you very much, and as always, great work!
[I don't know how to mark this as fixed. Would appreciate if someone could do this for me]
Automatically closed -- issue fixed for 2 weeks with no activity.