musescore / musescore/MuseScore

Clicking notes in an instrument part causes playback to go forte and to ignore dynamic markings

Open
#34,563 4 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Aug 12, 2026.

P2 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

NB I think it might be a MuseSounds-specific issue, however, when you select "MuseSounds Issue" on GitHub, it navigates you to a non-existent page on a different website, where you can't create a ticket.

Repro:

  1. Create a multi-instrument score with various dynamic markings
  2. Open one instrument's part (it's always reproducible when using any MuseSounds instrument)
  3. Click randomly on musical notes there

Expected:

  • Playback shouldn't be affected/changed in any way after that

Actual:

  • Going forward, the part is always going to be played at fortissimo, ignoring all the dynamic markings (both in the specific part tab and in the main full score view)
Supporting files, videos and screenshots

part-dynamics.mscz.zip

https://github.com/user-attachments/assets/153851df-23b7-4e1f-aa73-bcec4d719089

In which versions of MuseScore Studio is this issue present?

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

Regression

Choose option...

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.