Very slow saves & slow view/hide instruments

• Jun 26, 2025 - 15:11

I'm on MuseScore 4.5.2, Mac Sonoma 14.6.1. I'm working on a score that's about 125 bars and 25 instruments. I'm on a decent machine -2.6 GHZ 6-core Intel core i7, 32 GB RAM and lots of room on the HD.

Problems:
1. Saves are very slow, estimated 30-60 seconds
2. Earlier every operation triggered the multicolored wheel; however a restart seems to have cured that
3. When I click on the eye to open/close an instrument display in a part, that is also very slow.
4. Two earlier versions had key errors for specific instruments. The first time my trumpet2 appeared in a different key than trumpet 1; it seemed to happen randomly. Cured by deleting trumpet2, re-adding it and pasting in the part from a slightly earlier version. Same thing happened a few versions later for flute. Neither of these instruments was changed - e.g. flute was always flute and never changed from a transposing instrument.

I don't know that #4 relates to the slowness but I'm including in the interest of thoroughness. #4 happened when my collaborator was working on it, rather than to me, so I can't detail the operations that happed immediately before. I have had this happen to me a while ago as well, but I haven't done any serious arranging for a year or more so I can't provide details or even version #'s.

Attachment Size
Working Les Mis-Rev 1.6.mscz 2.73 MB

Comments

As an update - if I reboot the computer things become almost normal with the exception of very slow saves. As I continue working on the score it slows down again. It appears that it is auto-saving at random frequently intervals (at least I assume that's the case) even though I had set autosave to 10 minutes.

"lots of room on the HD". HD, not SSD?. On my machine it makes a difference - took about 20s to save to SSD, nearly 40 to HD.

OS: Ubuntu 22.04.5 LTS, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250721848, revision: 7c55023
i7-7700K @4.20GHz, 32 Gb RAM.

Do you still have an unanswered question? Please log in first to post your question.