musescore / musescore/MuseScore

Playback volume of sf, sfz, and similar accents are incorrect

Open
#23,997 4 comments 1 reaction 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Aug 12, 2024.

needs review playback
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. create a score with a part that uses piano as a dynamic
  2. add in a sf or sfz to the part
  3. the playback volume for the accent is played above the level of a forte; which is not correct
  4. the expected result is an accent that is one dynamic louder than the current dynamic; the accent should be performed at the mp level
  5. change the overall dynamic to ff and the sf is played back at a volume lower than ff
  6. The expected result is that sf should perform the accent one dynamic louder and sff is two dynamic levels louder
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/6526739f-7cdb-43a1-aeba-dce47d8139dc

https://github.com/user-attachments/assets/51e3680c-b3da-4086-9770-3a2bb4683769

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

OS: macOS 14.5, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630832, revision: github-musescore-musescore-22b46f2

Regression

I was unable to check

Operating system

macOS 14.5

Additional context

My guess is that the accents of sf and sfz have been set at the volume of forte and the sff and sffz accents are set to the ff level. This is an incorrect interpretation of the symbols. sf and sfz should be one dynamic higher than the current dynamic level and sff and sffz is two dynamic levels higher than the current dynamic.

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.