-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smooth panning (auto-scrolling) should work as good as in MS3.6.2 #19210
Comments
Not sure I agree this is a P1, especially given the mountain of other issues we have in the 4.2 project. |
Another improvement would be to always position the playback cursor near the left edge of the screen (maybe 1/4 of the way in). It's more valuable to see the music that is coming than the music that has already been played. |
I concur. That should be a trivial change (possibly just changing "2" to "4" in both places here: https://github.com/musescore/MuseScore/pull/18718/files#diff-1ad85d6753e0a807acd0537fa45ee920e557f46ba99c86331e045fd37bec36abR865-R872) that should make it more in line with what's expected. |
The way this worked in MS 3.6.2 was already perfect for my use case (choir practice videos). I'd also say that the implementation of smooth panning was better than any other tool available (Finale, Sibelius, Dorico, etc), for the purpose of recording your screen whilst playing back. The MS 3.6.2 smoothPan advanced preferences allow you some control of position the playhead too, and the scrolling is smooth. The current MS4.2-master implementation seems to jump at the start of each bar. I for one would really appreciate this feature working as it did in MS 3.6.2! |
Bug description
Smooth panning (auto-scrolling) should work as good as in MS3.6.2 (or better)
Steps to reproduce
See #19169 (comment)
Screenshots/Screen recordings
263736995-de98b124-a341-4240-ae11-ddeabe003561.mp4
MuseScore Version
4.2.0 master
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
All
Additional context
#18718
The text was updated successfully, but these errors were encountered: