musescore / musescore/MuseScore

Impossible to reset to its default the velocity of a note

Open
#28,528 2 comments 1 reaction 1 assignee View on GitHub

@avvvvve is already working on this.

Since Jun 24, 2025.

P3 regression MS3 UX/interaction
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
  1. Enter a few note and a "p" dynamic on the first note
  2. Select one of the notes and open its "Playback" panel . The velocity is indicated as "64".
  3. Change to velocity to "15" and play the phrase. That note can be now heard as lower that the other notes of the phrases
  4. Reset that note velocity in order to have it controlled by the last dynamic (the "p") , by either (a) typing "64" as velocity, or (b) using the reset button above the velocity.

Expected:
When playing the phrase, that note has the same velocity as the other ones of the phrase,

Actual:
The note has a much louder velocity.

Conclusion:

  1. The original default velocity "64" is incorrect and does not reflect the actual velocity of the note but instead and "unspecified" velocity
  2. Resetting or typing a velocity does not return to that "unspecified" state but to an actual velocity of "64".
    Its velocity can no longer be controlled by dynamics.

Workaround:

  1. Delete the note and retype it. Its velocity will be reset to "unspecified"

This is a regression of MU3 where a single note velocity could be defined either as absolute or as offset. Resetting a note velocity with simple a matter of setting it to "Offset | 0".

Image

Supporting files, videos and screenshots

Image

What is the latest version of MuseScore Studio where this issue is present?

MU4.5.2

Regression

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

Operating system

Windows 10

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.