musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
11.85k stars 2.57k forks source link

Midi output sets velocity to 1 for all notes #22354

Open Flying-Roger opened 3 months ago

Flying-Roger commented 3 months ago

Issue type

General playback bug

Bug description

For any score, the playback on a MIDI device produces very weak sounds. Reason: the velocity is set to 1 (on a 0-127 range) for all notes. Note: a beat sound is also heard (metronome?), with the same velocity = 1.

Steps to reproduce

  1. Create a score with a few notes
  2. Assign the output device in the preferences.
  3. Capture the output MIDI port and check the velocity in the notes messages or listen to the keyboard sound.

Screenshots/Screen recordings

No response

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 10

Additional context

Tested with a Casio keyboard.

bkunda commented 3 months ago

Possibly a good one to tackle together with a range of other midi-related issues. (@cbjeukendrup FYI)

knoike commented 3 months ago

MIDI_out_test_CDEG MU4_MIDI_out

I have same problem in all Ver.4 series. This is a sample MIDI output. I used the Web App "Send And Receive" to capture the MIDI output routed by virtual MIDI driver "loopMIDI". I showed note on message "90 pp vv" in yellow. "vv" is velocity value. You can see that all values are 01.

Send And Receive: https://mikatahara.github.io/SendReceive/

loopMIDI: https://www.tobias-erichsen.de/software/loopmidi.html

harakiriman commented 3 months ago

I have just monitored an empy score midi out, and found that Musescore sends strange midi messages on every measure, just when crossing the bar line. See attached image. Captura de pantalla 2024-04-13 140342

Flying-Roger commented 1 month ago

Tested again today with Musescore Studio 4.3.1 to confirm that the problem is still there. I see that the issue is still open here on github, so probably not tackled yet.