musescore / musescore/MuseScore
MIDI velocity data incorrectly captured when entering chords in "Input by duration" mode
@avvvvve is already working on this.
Since Aug 11, 2026.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
When using a MIDI keyboard, entering chords and entering single notes show different behaviour with respect to capturing key velocity information.
From within MuseScore, select File→New and click "Done" to accept the defaults.
Key 'M to select "Input by duration".
On an attached MIDI keyboard, firmly play and hold two keys, then key 7 before releasing them. This fills a single bar with a semibreve chord.
Gently play and hold the same two keys, then key 7 before releasing them. This fills the second bar with the same chord.
In the property inspector, select playback and note the velocities.
Expected behaviour: the velocities should be "unspecified/follows dynamics".
Actual behaviour: the velocities differ between the two bars and, in each bar, between the two notes entered.
If single notes are entered rather than intervals or chords, the velocity data are discarded and the score shows velocities of 64. This is better but, in both cases, I believe the velocities should be "unspecified/follows dynamics".
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
OS: Ubuntu 26.04 LTS, Arch.: x86_64, MuseScore Studio version (64-bit): 4.7.4-260706075, revision: github-musescore-musescore-7688c00
- I have now (2026/08/12) verified that this issue is also present in MuseScore-Studio-Nightly-260812043-4.7-06234ae-x86_64.AppImage
Regression
I was unable to check
Operating system
Ubuntu 26.04
Additional context
No response
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.