musescore / musescore/MuseScore
View resets to top of page during playback
Nobody has claimed this yet.
- 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
- Continuous view in MS
- Scroll to somewhere below the top of the score (i.e. strings)
- Play
- Once the playback reaches the end of the screen, it occasionally resets to the top of the screen
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/01c4954f-b59e-4dc7-8baa-23d1ae571e9f
In which versions of MuseScore Studio is this issue present?
4.6.3
Regression
No.
Operating system
Windows 11
Additional context
It also occurs most of the time if you are scrolling the score during playback when the playback reaches the right edge of the screen, but it's most annoying when it does it randomly as shown in the above video.
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
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.
Research direction
Reproduce the issue in MuseScore Studio 4.6.3 on Windows 11 using Continuous view: scroll below the top, start playback, and observe behavior when playback reaches the screen edge. Trace the playback auto-scroll and score-view positioning logic; done means playback no longer unexpectedly resets the view to the top, including while scrolling during playback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100