musescore/MuseScore

Mixer appears empty after closing large score and opening small score

Open

#25,559 opened on Nov 18, 2024

View on GitHub
 (3 comments) (0 reactions) (2 assignees)C++ (2,432 forks)batch import
P2UIcommunitygood first issue

Repository metrics

Stars
 (11,122 stars)
PR merge metrics
 (Avg merge 8d 17h) (128 merged PRs in 30d)

Description

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

  1. Open larger score (I use "Concert band" template)
  2. Scroll all the way to the right in the mixer and write a note in your score
  3. Close that score and open a new score (I use "Treble Clef" template)
  4. Mixer appears empty

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/f10d50b5-b132-451c-bb33-d00ee2a8f545

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

OS: macOS 14.6, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.4-243231423, revision: github-musescore-musescore-54ac741

Regression

No.

Operating system

Mac OS 14

Additional context

Present in all versions of 4

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

Research direction
Investigate the mixer panel state management in MuseScore. The bug occurs when switching from a large score to a small score, causing the mixer to appear empty. Likely the mixer's scroll position or cached state is not reset properly. Look at source files related to the mixer, such as mscore/mixer.cpp or similar, focusing on how the mixer initializes and resets when a new score is opened. Check if there is any leftover state from the previous score that should be cleared.
Tech stack
c
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
basic C++understanding of Qt
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25