musescore / musescore/MuseScore

Sound flags carry over between instrument changes.

Open
#23,746 2 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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
  1. Add an instrument with a sound flag in your score.
  2. Activate a specific sound flag.
  3. Add "Change instr." from the Text tab and change the instrument to something else after you've set the sound flag. Make sure the other instrument does not support the same sound flag.
  4. Add some notes to the instrument you just added.
  5. Start playback and notice the lack of sound from the new instrument.

If you then add a sound flag to that new instrument it works again.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/3b181c7b-46d7-459b-ba1f-7c8dc5a097c6

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

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2

Regression

No.

Operating system

Win 11

Additional context

The issue is probably just MuseScore not removing sound flags after an instrument change if the new instrument does not support that sound flag.

In the recording I have added the piano in the background, because I am not allowed to send just clear samples or smt due to the license... yippie

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.