musescore / musescore/MuseScore

Dynamic markings affect notes that are not supposed to sound anymore

Open
#34,561 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

P2 playback regression MS4
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

Repro:

  • Enter a relatively long note (half, whole, etc.) of a sustained instrument (strings, winds) with a pianissimo (pp) marking
  • Right after it ends, on the next beat (where that note is not supposed to sound anymore), add fortissimo (ff)

Expected:

  • The volume of the note that ended is not supposed to change. It's fine if there is some natural tail, but it shouldn't become louder.

Actual:

  • The leftovers of the note that is not supposed to play anymore go full fortissimo, and it sounds like a new staccato note.

Notes:

  • It makes the playback of the score completely incorrect in such places, and I couldn't figure out a workaround. Sometimes I try adding a small rest, but first, it makes the score wrong (not as intended), and second, it doesn't always fix the issue.
  • I am attaching the screen recording with the audio (and the corresponding MuseScore project as well) – I hope it demonstrates the problem clearly.
  • This might not be noticed by most people who use MuseScore just for small and simple projects, however, it becomes a really big one when you do a more complex orchestral score where there can be many instruments playing at the same time, and sudden dynamics changes.
Supporting files, videos and screenshots

dynamics issue.mscz.zip

https://github.com/user-attachments/assets/b46dcb33-a9ee-4158-a3a8-2a9ffd4aa114

In which versions of MuseScore Studio is this issue present?

4.7.4-260706075, revision: github-musescore-musescore-7688c00

Regression

I was unable to check

Operating system

macOS Tahoe (26.5.2)

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.