MS4 performance degrades in larger scores
I began creating a score with RC1 a couple weeks ago and am now using the first official release: 4.0.0.223362132. As the score content grew, the screen and editing performance became increasingly sluggish. I am now being forced to export the score as .mxl and continue in MS 3.6.2.
Small scores work great! Congratulations. I just re-tested a score with 5 parts and 30 measures (fast). My unfinished score currently has 16 parts and 187 measures. Many editing features are becoming unusably slow, such as in score pan and zoom, note entry and navigator use. The instrument track view switching takes many seconds to add or remove the track's visibility and can hang the software if multiple switches are attempted before the previous command responds (which may never complete). The same score exported to MS 3.6 performs fine.
I apologize for this being such a non specific post, but I have tried many different scores and this issue seems obvious when large scores with multiple tracks are used, such are common in symphony works.
My own system should not be an issue and I see no preference setting in MuseScore which can increase CPU threads or memory. Below is a summary of my machine and I hope this report is useful.
Thanks from Chris and good luck!
Windows 10 Pro 21H2
AMD Ryzen Threadripper 2990WX 32-Core Processor 3.00 GHz
100 GB ram
SSD (s)
PS: I was unable to find this as a known issue with my effort.
Comments
https://github.com/musescore/MuseScore/issues/14693 and https://github.com/musescore/MuseScore/issues/14546 look related.
In reply to https://github.com/musescore… by RobFog
I agree that this is probably the same issue.
The specific score I mentioned was first created with MS4 RC1. Once that degraded, I exported the music XML and opened it in MS3. The performance returned to an acceptable level. Other MS3 scored imported to MS4 show the same symptoms. When I look at my CPU and system resource monitor, it seems like there is little to no activity and no resources are being over used.
I really hope this can be looked at. It might be a show stopper. I will be checking back and will happily help wherever possible.
BTW, the SSD MuseScore and everything is working on has 65GB available additional storage.
As of 12/14/22, my Windows 10 install was updated by Microsoft. I was just amazed to find that the same score I have been complaining about is now very responsive in MS4! Switching track visibility is still a bit slow but also greatly improved and usable. I would not have posted this issue if the performance was what I am enjoying now. I hope this updated comment is useful.
I am also having significant hits in performance when writing on a large score with MS4. The more I work on it the slower my system in general becomes. I am using the new Muse soundpacks.