musescore / musescore/MuseScore

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

Open
#24,538 3 comments 0 reactions 3 assignees View on GitHub

@Eism is already working on this.

Since Sep 10, 2024.

design debt needs design P3 regression MS4 UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

General playback bug

Description with steps to reproduce
  1. Import a score from MS3
  2. Select a note (see that the velocity says 64)
  3. Change the velocity to anything else
  4. Change it back to 64 again (either manually or by clicking the reset button)
  5. 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
  • 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.