That score got last saved with 2.3.2, has 3173 measures and 25 instruments.
We know that these are a problem in 2.x, and the recommendation is to split such large scores into movements.
It isn't too bad though, not yet, as that score is basically empty and adding notes works reasonably well.
But I guess once it t files it'll become slowere and slower.
So I don't see any problem with that score just yet.
It should be better in 3.0, whether it is remains to be seen though.
Comments
how big is your score? It seems like there is some performance bug. Might just categorize as #280952: Score Editing Slow.
Attach score please?
In reply to how big is your score? It… by ericfontainejazz
Could be #280898: MuseScore 2 and 3 compete for the MIDI input device
That issue certainly is unrelated (with that it doesn't work at all, not just slow), but there are others dealing with slowness
In reply to That issue certainly is… by Jojo-Schmitz
This is it - though I changed the title. Barely can get anything done on it.
I think it was because I was using an older version. I'll try the new one and get back to you guys.
EDIT: My administrator won't let me install the new version, so scratch that.
That score got last saved with 2.3.2, has 3173 measures and 25 instruments.
We know that these are a problem in 2.x, and the recommendation is to split such large scores into movements.
It isn't too bad though, not yet, as that score is basically empty and adding notes works reasonably well.
But I guess once it t files it'll become slowere and slower.
So I don't see any problem with that score just yet.
It should be better in 3.0, whether it is remains to be seen though.