Allow score-level default velocity settings for dynamic marks + Display actual note velocity values in Properties

Your idea

• Allow each score to define its own default velocity values for dynamic marks.
• Do not keep all notes within the range of a dynamic mark at the default velocity value “64”. Display the actual velocity applied by the dynamic mark in the Properties panel.

Problem to be solved

I understand that in MuseScore 4, dynamic marks no longer have user-editable velocity values, and that the application has shifted to a model where absolute velocity values must be set at the note level. While this design change is clear, it introduces significant problems.

Currently, users are forced to compose according to the fixed velocity values that MuseScore internally assigns to dynamic marks. As you know, the real-world velocity associated with symbols like “mf” varies widely depending on the composer, the musical style, the instrument, and the performance context. Because the default velocities cannot be customized per score, MuseScore cannot reflect these differences.

In addition, even within a passage where a dynamic mark is applied, all notes still display the default velocity value “64” in the Properties panel. This does not represent the actual playback velocity. As a result, users cannot see what velocity is actually being used, which creates confusion when attempting to make manual adjustments at the note level.

It should be possible for MuseScore to:

1. Apply the dynamic mark’s velocity value to the notes within its range.
2. Display those resulting velocity values in the Properties panel.

This would improve clarity and make MuseScore more suitable for detailed dynamic control.

Prior art

No response

Additional context

Currently, the lack of visible per-note velocity values and the inability to change dynamic mapping per score significantly limits expressive control, especially in projects that require nuanced dynamic behavior.

Additionally, even when using MuseScore purely as a notation tool, the current MIDI export functionality does not work reliably (for example, issue #22669). Because of this, editing the exported data in a DAW becomes unnecessarily difficult.

Related: #13858

Checklist

• This request follows the guidelines for reporting issues
• I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests