MIDI Input / Output doesn't work

• Dec 2, 2018 - 00:52
Reported version
P2 - Medium
S2 - Critical

I can't get MS 3.0 to recognize any of my MIDI input or output gear. I make a selection, hit Apply. Close MS 3.0 and reopen so it can update the changes. Nothing. Also, all the choices in the I/O tab say MMSystem,2 or MMSystem,3. MS 2.3.2 always recognized my MIDI gear.

THANK YOU for all your help!


Frequency Many Once
Status active needs info
Priority P2 - Medium

What kind of gear do you use? Which OS? Could record a gif if possible showing what is going on.

Interestingly...I'm noticing something similar too...I'm on 3.0 release on windows 10 x86-64. I'm able to use the midi input from my keyboard. But the name in the PortAudio section in the I/O tab doesn't give my midi device a useful name...it is simply called "MMSystem,M". And I see three outputs "MMSystem,M", which I believe are the actual legitimate outputs, but just named funny.

Stepping through the debugger in PortMidi code, I see that Pm_GetDeviceInfo() is returning these funny-named devices. It sounds like PortMidi is what is at fault unforutnately... :( I wonder what changed since the past release that would have caused this???

Workaround No Yes

I wish someone notified me about this, cause I was the one who implemented this last year.

I'm adding one workaround: Because the orders of the midi devices are probably the same as in MuseScore 2.3.2, that means can look at the ordering on 2.3.2 and then just remember which position you picked in the dropbox for what midi device you want, and then in MuseScore 3.0 just pick the same index from the dropbox.

I've verified that with my PR that the names of devices now properly appear again:

Screenshot (36).png

Also I've verified the midi output is working, as I'm at least able to play with Window's default midi synth. But as I mentioned earlier, the MIDI was working prior, but rather it was simply the device names that were messed up.

Status PR created fixed

Fixed in branch master, commit 2ca9980d24

fix #279203 PortMidi Win device names unicode

I don't know history about why an earlier commit 3acc363 "Solved all compilation errors on MSVC" had to remove this #undef UNICODE. I'm on MSVC 2017 right now and I'm able to compile just fine. That commit's removal of those lines caused all the Midi device names to be identical and undescriptive as 'MMSystem,M' although the devices were perfectly valid.

Status active closed

MIDI output does work, right? It is only the button label you're complaining about, isn't it? So please open a new issue for that, but I guess that might be by design, no different string being sent to MuseScore


Does anyone know why Musescore 3 doesnt catch any notes from my MIDI Keyboard? For example, in the 1st picture are the REAPER Preferences and it works perfectly. Howerer, when I turn on MuseScore 3 it doesnt work as it should be. I redo all these preferences in MuseScore as they are in the Reaper. I dunno what to do, I was changing these preferences in all possible combination and it doesnt work. I turn on the Kyeboard before turning on the MuseScore obviously and still nothing..

Attachment Size
Bez tytułu.png 114.19 KB
qwe.png 118.14 KB
Regression No Yes
Workaround Yes No

I am running MuseScore, complete revision details OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit):, revision: 43c5553. In preferences, I see many choices for MIDI input and MIDI output devices. But when I select any of them and click apply or ok buttons, and restart or not restart musescore app, I go back to preferences and my MIDI input and MIDI output don't stay selected. When playing a score I can hear fine but using the default musescore sounds. Is this known bug? Is there a workaround?

Fix version