Scrolling score is slow and jerky.
Reported version
3.0
Type
Graphical (UI)
Severity
S4 - Minor
Status
closed
Regression
No
Workaround
No
Project
Scrolling is not as smooth or fast as it was in versions 2.x. Scrolling is almost unusable and is not affected (good or bad) by pressing the shift key to change scroll direction. I'm contemplating just dragging the score around the screen.
I'm on Windows 10 and tested it in both 3.0 and 2.3.2 opened at the same time.
Comments
I hate bugs like this. All of a sudden, without closing and reopening MuseScore or changing any other scores open, scrolling is as smooth as version 2.x. I've changed the status to needs info since I can figure out what caused the issue.
Any chance it happened pretty soon after opening musescore? Perhaps it was still quite busy unpacking the soundfont?
I don't think so, but I'm not sure. I'm very much in favor of MuseScore having a dialog box that tells you when it's doing something behind the scenes that will cause such a problem.
In reply to I don't think so, but I'm… by mike320
I've had my score open for a very long time and scrolling is a bit slow and jerky. It's not unusable like it was earlier, but once again the scrolling is slow. It's remained that way all day today, but I've cause it to crash so many times, this is the first I've kept it open long enough to be sure the soundfont is unpacked. I also created a score in 3.0 with the same 43 parts and 100 measures. The response is far worse than a score with the same specs in version 2.x.
I have further information that I hope will help and perhaps be reproduceable by others.
When is entered this score: input example.mscz from scratch it slows way down as I'm entering the score.
I started with this score with no notes, lyrics etc.
I entered all of the notes and slowdown was minimal but it did exists.
I started to enter the lyrics and about half way through input and scrolling response really started slowing down.
By the time this was all entered the slowdown was intolerable.
This is only 13 measures of notes. Slowdown should be non-existent or unnoticeable. That was my experience in version 2.x.
As you will see, when I close this file and reopen it, the slowdown is nearly non existent. I still have the same basic file open with over 100 measures in it as well as a couple of other much smaller files. The only difference between slow and fast is saving, closing and reopening the file. This leads me to believe there is one of those pesky memory problems that are a PITA to debug. While writing this, I also tested the other version of this with 120 measures of notes, lyrics and figured bass along with 52 additional empty measures by saving, closing and reopening it and it responds like it's almost an empty score.
Is this fixed by https://github.com/musescore/MuseScore/pull/4731? Or do some scrolling issues still persist?
I would say that something fixed this during alpha and beta development. I don't notice poor scrolling any more.