Bug? CPU spikes and lag when using Ctrl+arrow to position elements
When I open the attached score and edit one of its parts, and try to position for example a rehearsal mark with selecting it and pressing Ctrl+arrow keys, the positioning happens very slowly, causing CPU spikes and is freezing the entire UI for up to 1-2 seconds.
This is Musescore 2.2.1.0, Windows Store version.
| Attachment | Size |
|---|---|
| Sing To The Moon.mscz | 73.92 KB |
Comments
Which really is MuseScore 2.2. while MuseScore 2.2.1 in the Windows store is 2.2.2.0 (availabe since a few hours)
I don't see CPU spikes though, not on Windows 7 nor on Windows 10, not with a plain score, but indeed with yours, which has quite a view linked parts, which most probably is the reason for this (it shouldn't be, as movin that rehearsal mark should not change any of the parts)
In reply to Which really is MuseScore 2… by Jojo-Schmitz
That seems incorrect, I got this version from the Store on 28 March.
Edit: Sorry I understand now. Musescore 2.2 is displayed in Store as 2.2.1.0, and 2.2.1 will be displayed as 2.2.2.0 but the real version number is shown in Help/About
In reply to That seems incorrect, I got… by marczellm
No, that is an idiosyncrasy of the Windows Store, Microsoft insists in 4 digit version number and dosen't allow change the last digit for some stupid reason.
2.2.2.0 (2.2.1) got into the store today, 2.2.0.0 was the first 2.2, than a fix was needed to get the icons right, so there was a 2nd 2.2, now named 2.2.1.0 in the store.
In reply to Which really is MuseScore 2… by Jojo-Schmitz
I get the lag on my computer also. I'm still using 2.1. I'm waiting for the notification that 2.2.x is available to see that "Check for updates" works.
In reply to I get the lag on my computer… by mike320
Indeed, I don't think this is a 2.2 regression, won't be surprised if even 2.0.0 shows this behavoir
In reply to Which really is MuseScore 2… by Jojo-Schmitz
Rehearsal marks are linked to all parts so actually, that would be one of the slowest changes even if we didn't relayout all parts on every change, which I believe we do.
FWIW, the file seems unnecessarily large, like there are tons of duplicated elements in there, but I'm not actually seeing anything in particular. Chord symbols seem especially problematic - removing them all speeds things up noticeably - but I don't see any obvious reason why this should be.