musescore / musescore/MuseScore

Issues with Detached Mixer and Percussion Panel in MuseScore

Open
#33,769 7 comments 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Jun 15, 2026.

awaiting reply from user needs review UI VST
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

I am using the beta version 4.7.3 of MuseScore and I have noticed some issues with the detached Mixer and Percussion Panel windows when using a second monitor.

I move both the Mixer and the Percussion Panel to my second monitor. When I do this, two problems occur:

When I close MuseScore, the detached Mixer and Percussion Panel windows remain active/open if they were being used.
Every time I reopen the software, I have to manually set the Mixer window's width and height again because its size and position are not remembered.

Additionally, is it possible to improve the detached-window functionality so that the Mixer and Percussion Panel can be fully optimized for use on a second monitor? For example, it would be very useful if MuseScore could remember their size, position, and monitor assignment between sessions.

I would also like to suggest adding a maximize/resize button to detached windows, making it easier to quickly adapt them to different screen sizes and multi-monitor setups.

MuseScore is becoming a real standard for many musicians, composers, arrangers, and educators, so improvements to multi-monitor workflows could greatly enhance the user experience for professional and advanced users.

Are these known bugs? Is there a way to fix these issues, or are there plans to address them in a future update?

Thank you.

Supporting files, videos and screenshots
Image Image Image Image Image
In which versions of MuseScore Studio is this issue present?

4.7.3

Regression

I was unable to check

Operating system

Windows 11

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.