[MU4 Issue] Muse Sounds: Showing or hiding staves during playback temp. mutes all Muse Sounds
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the issue in a score with Muse Sounds enabled by starting playback and showing or hiding a staff. Trace the desktop playback and staff-visibility handling to identify why Muse Sounds stops while other staves continue. Done means Muse Sounds playback continues during staff visibility changes, with regression coverage if the relevant test area is found.
Written by the indexing model from the issue text.
Description
Describe the bug
If you show or hide stave(s) or instrument(s) during playback (even not Muse Sound staves), all staves with Muse Sounds enabled cease playback temporarily (usually (especially if the act of showing/hiding the staff lags Musescore))
To Reproduce
Steps to reproduce the behavior:
- Open score with Muse Sounds
- Press play
- Show/hide staff during playback
- Hear all Muse Sounds staves cease playback
Expected behavior
Playback of Muse Sounds staves should continue
Screenshots
Platform information
- OS: Reported on Windows
Additional context
All non Muse Sounds staves continue playback as if nothing happened
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from musescore/MuseScore
-
engraving P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
community P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
regression nightly UX/interaction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in musescore/MuseScore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·