Midi Output not working in Musescore 4.2.2 - test report
Every time a new release of Musescore 4 is available, I test it to see if this bug has finally been solved, but to no avail so far (up to 4.2.2 tested today), so I keep using M3. I keep testing because I like very much the new M4 interface. However, as the mcsz files are not compatible, I would not quit M3 until key functions like midi are fully functional in M4.
On my device, properly selected in the E/S menu of M4, I only hear very weak sounds, like a repeated note or some notes not matching the played score. Midi input works fine.
Unfortunately, It seems that developers (using Linux?) cannot reproduce the problem.
Here I am trying to help by producing evidences, by capturing the midi-out flow (using a loop tool + midi viewer).
Here are the test data, captured in the Musescore "help/about" menu:
- OS: Windows 10 Version 2009 or later, Arch.: x86_64,
- MuseScore version (64-bit): 4.2.0-233521124, revision: eb8d33cI
Attached files:
- M4 mcsz file (very simple score)
- Midi output log (midi) generated by Musescore 4.2.2)
- M3 mcsz file (same score as for M4)
- Midi output log (midi) generated by Musescore 3.6.0)
Hoping this can help the developpers to analyse this long outstanding bug.
These files show that M4 is actually connected and sends data to the midi output port, so the problem is not there but rather in the contents of the generated midi data.
| Attachment | Size |
|---|---|
| 2023-12-21 M4.2.0 Midi output test.mscz | 15.44 KB |
| 2023-12-21 M4.2.0 Midi output test (midi sniffing).csv | 3.79 KB |
| 2023-12-21 M3.6.0 Midi output test.mscz | 3.32 KB |
| 2023-12-21 M3.6.0 Midi output test (midi sniffing).csv | 49.3 KB |
Comments
There os no 4.2.2 only a 4.2.0 and a 4.2.1 is in the works
in the E/S menu of M4 ??, I/O, Input/Output?
In reply to There os no 4.2.2 only a 4.2… by Jojo-Schmitz
1) Sorry for the typo: indeed version 4.2.0
The details of the OS/SW versions were correct in my message.
2) In the E/S menu of M4, I selected my midi capture application in the "Sortie MIDI" menu (French version for Output). Defining a MIDI input or not obviously should not change anything, but I have now double-checked that. Velocity is always 1 (= inaudible volume) + only some notes are correct: the other notes are erratic values.
I should also mention that :
- I use the M4 version without musehub, but just to be sure, I tested the version with musehub: same issue.
- I even tried to manually set a velocity for some notes or to adjust the volume in the mixer: no effect on midi.
Midi input works fine, as already the case with several previous M4 versions.
In reply to There os no 4.2.2 only a 4.2… by Jojo-Schmitz
midi output is still not working... really a pity!
In reply to There os no 4.2.2 only a 4.2… by Jojo-Schmitz
4.2.1 is already out. That's what I have installed:
OS: Windows 10 Version 2009 or later,
Arch.: x86_64,
MuseScore version (64-bit): 4.2.1-240230937,
revision: d757433
In reply to 4.2.1 is already out. That's… by bill0287
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: d757433
is mine
does it work for you?
In reply to OS: Windows 10 Version 2009… by Adriano Ellero
I'm sorry, but I don't know how to test it.
Tested again with the latest version 4.2.1 (4.2.1.240230937 to be precise).
Still not working as it should: the notes are present in the midi output, but the sound level is still extremely low, barely audible with the keyboard volume set to maximum.
I tested a midi export : the file is OK, with a correct volume level: obviously something different is sent to the midi port.
On another post, I saw a reference to similar reports on the Musescore Japanese forum.
According to what they observed, the problem is very simple: Musescore 4.2.1 sends all the notes to the midi port with velocity =1, i.e. the lowest audible volume level.
Here are the references:
https://musescore.org/ja/node/352572
https://musescore.org/ja/node/338263
https://musescore.org/ja/node/340226