UI awkwardness: Velocity displays "64" when it is actually "0" (which means "use the default velocity")

erinic04 commented 1 week ago

Issue type

General playback bug

Description with steps to reproduce

Import a score from MS3
Select a note (see that the velocity says 64)
Change the velocity to anything else
Change it back to 64 again (either manually or by clicking the reset button)
Hear that the playback volume is not the same as it normally is

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/02437413-ded1-4d7e-85b2-ea0d3b72f3a1

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

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.1-242490810, revision: github-musescore-musescore-0b3dd00

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Reported on Windows 11

Additional context

I have only been able to reproduce this in imported scores from MS3, however I believe others have been having this problem in non-imported scores

Checklist

[X] This report follows the guidelines for reporting bugs and issues
[X] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
[X] I have attached all requested files and information to this report
[X] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

cbjeukendrup commented 1 week ago

See also my research at https://github.com/musescore/MuseScore/issues/14768#issuecomment-2211558560; the default value is 0, which means "use the default", but this is displayed as 64. You can change it back to "use the default" by typing 0 into the velocity field. Intuitively it surprises me that clicking the reset button does not internally set it to 0 but apparently to 64, but probably that is just part of the same problem (namely that it is utterly janky to display 0 as 64).

bkunda commented 1 week ago

Thanks for this info @cbjeukendrup!

So it looks like the real bug here is that the UI is creating awkwardness. I'd suggest something more along the lines not displaying any specific value and requiring the user to "set custom velocity" (this needs to be designed).

The user shouldn't be seeing "0" (or 0 displayed as "64") as this is completely meaningless to 99% of people.

musescore / MuseScore