Why doesn't MIDI output work on Musescore 4?

• Jan 6, 2023 - 17:07

It used to work perfectly with the previous version, but now it doesn't work. I double-checked to see if it was a problem with my digital piano or computer, but it isn't, because MIDI output works everywhere else.


I have the same problem.
The midi input/output worked initially, but no longer with the current version v4.0.1.230121751.
Here is a snapshot of my preferences, where I have selected my keyboard as input and output.
When I play the score, it still goes to my PC Loudspeaker instead of my MIDI keyboard.
I have also "Activer input MIDI" in the playback setting, although is should not affect playback, I guess.
Is there any other setting that I should change?

Note: initially, the selection was totally empty; the pulldown menu was populated with "Aucun périphérique" and "CASIO USB-MIDI", but the latter could not be selected. I found a workaround by first selecting "Aucun périphérique", and then "CASIO USB-MIDI". This is probably an unrelated small bug.

UPDATE: when I set the volume of my CASIO keyboard to maximum, I can hear the notes very weakly. There is also a note (A) superposed to each of the actual notes.
Midi input did not work half an hour ago, but now it does; could this be linked to a test I did with Musescore 3 to confirm that the keyboard worked fine with M3?

In reply to by vcsteven55

Same bug in 4.2: Note on message is bad issued so the velocity is set to 1 or 0. Any hack like using MIDIOX as a midi transformer, could make it sound, but with no expression since volume will be loud or soft depending on the values given to 1 and 0 on traslation. This is unnaceptable and a pretty dumb bug for a released music software.

In reply to by Marc Sabatella

I can confirm the same behavior: MIDI output does not work properly. If I turn up the volume on the Casio keyboard (with built-in USB port, shows up as "CASIO USB-MIDI" in Preferences), I can barely hear some notes playing, even when there are no notes (only pauses) in the staff. And by barely I mean about the same loudness as the speaker background noise.

MuseScore 4.1.1 on Manjaro Linux with KDE and Pipewire. I don't see any MIDI connection in qpwgraph, which makes me believe it's trying to connect to MIDI directly instead of using JACK/Pipewire.

Some related issues on GitHub:
* https://github.com/musescore/MuseScore/issues/16787
* https://github.com/musescore/MuseScore/issues/18382

In reply to by Flying Roger

I tested again today, with the latest version Révision e4d1ddf, on a desktop PC running the latest version of Windows 10.

A good point for version 4.1.1 is that PC playback issues (cracks and other perturbations) are seemingly solved.

For Midi, I have still the same problem as before: Midi input works, but not Midi output, despite performing all selections mentioned by Marc S. Sometimes, I only hear a repeated tiny A4 note in the background, as already reported by other users.

Sequence for testing:
1)- launch Musescore 4
- create a new score, just selecting keyboard/piano/add
- edit preferences i/o: midi menus are empty so I click on the pulldown and try to select Casio midi, to no avail.
using a trick already mentioned last year, I first select "aucun périphérique" (no peripheral) and then reselect "CASIO USB-MIDI" (I already signaled this bug on the pulldown selector on the previous version: it is still there).
so I finally get CASIO USB-MIDI for both Midi input and Midi output.
- check that the playback menu has "Activate Midi input" selected
- click on the first rest and press N
- play notes on the Casio keyboard => the notes appear on the M4 score. => Midi input is workging
- press N to exit the input mode
- click on the first note and press space to play the score => it only plays on the PC Window, not on the Casio.
2) close and restart Musescore, opening the last played score:
- the CASIO USB-MIDI selection and the "Activate Midi input" are still there
- but the Midi output still does not work.
3) Launch Musescore 3.6.0, opening the last recent score
- press space => the score plays on both PC desktop loudspeakers and on the Casio Keyboard.

Conclusion: I will once more stick to 3.6.0 until a new release of M4 is available, hoping that these issues will eventually be solved.
It's a pity because I appreciate the new layout and menus organisation of M4 and I am sure that a lot of good work has been done by the developpers.
Unfortunately, mscz 4 files incompatibility makes it cumbersome to move back to M3 once you edit a file in M4.
Therefore, I do not dare to create (or even edit) my scores in M4 until basic functions like midi playback are reliably working.

In reply to by robertopr

I figured out a different way to connect MS4 to midi connections for each instrument in a score to support the following use cases:
1- Connect to non vst3 plugins
2 - Connect instruments to vst/racks in your DAW
3 - Connect instruments to external midi hardware

Using the Element plugin from kvraudio installs a vst3 plugin that can be added to each instrument in the mixer. The Element plugin allows the creation of a workflow where you have multiple options to route and monitor the midi signal sent by MS4. Drag the midi port for your instrument to the editor and link it to the midi input - that is it.
I was cable to configure a piano and a drum track going to a Yamaha P125 and a drum VST in Reaper, properly equalized. When I press play in MS4 the piano plays on the Yamaha and the drum plays on a Reaper track. The DAW is irrelevant. As a side note I tested Dexed (DX7 emulator free) in MS4 as piano VST and was very pleased with the results.

Attachment Size
elemen1.PNG 6.72 KB

In reply to by omarlfrancisc

Tested again today with version 4.2.1
Something new is that I can hear the notes of my score on my midi device.
Previously, it was simply a repeated note.
Bad news ist that the volume is again very very low, barely audible with volume set to maximum level on the device. Changing the setting of the mixer master has no effect on this.
I also noticed that only one note of the chords is played on the device while the full chord is played on the PC loudspeaker.
Just sending this update in case it could help to localise the cause of this issue.

I have the same problem with my Yamaha Arius YDP 143. I can input notes to a score with it, but musescore doesn't output to my piano even though in I/O my Arius is recognised for input and output. So also here I'm forced to keep using version 3 because there it's working fine.

This problem is caused by all note on/off velocity value generated MU4 is 1. It's too small value.
MIDI velocity can take value from 0 to 127, usually around 64.
This occurs in all Ver.4 series. This does not occur in Ver.3.
It's very inconvenient.

See this figure.


I and some users reported same issue in Japanese forum.
We waiting fix this for a long time.

「[MS 4.1.0] Note On/Off Velocity がすべて 1」

「[MS 4.0] Note On Velocity がすべて 1」

「MIDI OUTの不具合」

In reply to by harakiriman

Did you check the velocity of the MIDI messages as indicated above?

In any case, to be clear: museSvore is not “MIDI music software” - it is music notation software Thant just happens to employ MIDI for its own internal playback. MuseSvore having limits in its MIDI I/O is no more surprising than your favorite DAW having limits in its music notation.

In reply to by Marc Sabatella

Sure, but it worked fine in version 3, so it is a feature that have been spoiled somehow during development, so it shoudn't be so hard to fix it, since it is a problem that during building the midi message, the 2nd data byte in NOTE-ON message, which is the note velocity is set either to 1 or 0, instead of the real value. Moreover, it works fine when using the internal synth, so either internally you ar not using standar midi messages or the routines that creates the messages are different for internal and external synths. Attached you will find the Note-on midi message format I mentioned.

In reply to by harakiriman

Fully supported.
It is hard to understand why it takes so much time to simply recognise that there is a bug.
I would like to ask this question: are there users (running on Windows 10) that do NOT experience this bug ?

Maybe this forum is not the right place for signalling bugs in v4.
I have now posted a bug report on github.

In reply to by knoike


By captured MIDI output, I may have found other problem.
This sample score is contain 4 notes, C4, E4, G4, C5.
The corresponding MIDI messages are as follows:

C4 note on/off: 90 3c 01/80 3c 01
E4 note on/off: 90 40 01/80 40 01
G4 note on/off: 90 43 01/80 43 01
C5 note on/off: 90 48 01/80 48 01

But the captured MIDI output also contained the following note on/off messages:

E5 note on/off: 90 4c 01/80 4c 01
F5 note on/off: 90 4d 01/80 4d 01

What are these? How about others?

Attachment Size
MU4_MIDI_out.png 27.2 KB
MIDI_out_test_CDEG.png 16.27 KB

In reply to by harakiriman

Thanks. I also confirmed it.
I guess from the results of your experiment, these MIDI messages may be for metronome sounds.
In the current implementation, it cannot be turned off... .
I think this is a bug too.

I think that MIDI messages for metronome sounds should not be output.

In reply to by knoike

Yes, I agree with you, taking into account that they are sent in the same channel (1) of the instrument, in case they sound, piano notes will sound instead of metronome sounds. And what about those pitch bend and sustain pedal events? Repeating this events with 0 value is useless and can eventually cause that a sustain pedal maintained between measures be cut too early.

In reply to by Marc Sabatella

To have music notation software that "is not MIDI music software", in 2024, is like having a car that is not meant for driving on a road. I'm sorry. That sounds harsh. I mean, if you're going to support control of musical instruments, which is a great idea from notation software, you need to do it adequately. If it's going to be poor, don't do it at all.

Very same thing happened to me! Doesn't recognize a device but did when I originally downloaded Musescore.
I also lost the ability to use Garageband... informs me that there is an e-licenser problem. Even with a native Mac app like Garage Band!

Do you still have an unanswered question? Please log in first to post your question.