musescore / musescore/MuseScore

AUX Channel MUTE button behaviour during playback

Open
#31,609 0 comments 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Jan 6, 2026.

P2 playback UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. open the mixer in MS
  2. activate (unmute) the AUX Channel of the internal Muse Reverb
  3. start play of a mscz file and you should listen reverb sound as expected
  4. press MUTE button of the reverb AUX Channel but unexpected, you will continue listen reverb sound
  5. it seems as if the MUTE button was not activated, but it is activated, because the button color changed over
  6. there are two alternative methods to activate the MUTE button function to stop the reverb: either a)when you stop playing and start play again, then there is no reverb sound, or b) during playback put the mixer fader of this reverb AUX channel to ZERO, when you then return it to any level there is no reverb sound
  7. if you unlock the reverb MUTE button, you will listen reverb sound as expected
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/7be5b887-0fad-40f5-ab4c-3cd4b98a3ce9

In which versions of MuseScore Studio is this issue present?

4.5.2 and 4.6.5 and actual nightly build

Regression

I was unable to check

Operating system

UbuntuStudio 24.04.3

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.