Beachball for 10 minutes +
Hi All,
We have an orchestral score which is admittedly quite large (650kb). Firstly, I can't make any changes now without getting the beachball for minutes at a time. I can't even scroll, or move a single note up or down. Secondly, when writing the score the size seemed to grow exponentially and disproportionately as I continued to write.
Is it possible that something has become corrupt in the metadata as I have tried breaking the score up into shorter sections but this doesn't solve the problem. In fact, by deleting all apart from the first fifth of the score resulted in a larger (1.2MB) file.
Many thanks for any support / ideas...
Comments
Welcome sihen. If possible it would be preferable to attach here the score.
However provide some more details (OS / Ram / available memory).
you can always try https://musescore.org/en/handbook/revert-factory-settings-0
In reply to Welcome sihen. If possible it by Shoichi
Of course. I have tried on two computers with similar results. The more powerful of the two is running OSX 10.10.5, 2.7GHz i7, 16GB ram and is running musescore 2.0.2.
I have attached the score here.
Many thanks,
Simon
In reply to Of course. I have tried on by sihen
I think perhaps you have been hit by the bug in #70146: Explosive accents on Guitar part with linked tab staff, or one similar. Your score is big, but not *that* big. The slowdown is caused by the tens of thousands of spurious slurs that somehow cropped up (16,000 of them on one note alone).
Shoichi, did you manually remove those from the MSCX file or what?
In reply to I think perhaps you have been by Marc Sabatella
Ciao Marc, my methods of simpleton:
I've been waiting that the score be loaded;
I exported it as XML then opened and saved (from 667.77 to 64.43 KB).
It appears corrupt but can be repaired.
I see too many rests hidden...
In reply to I think perhaps you have been by Marc Sabatella
OK, that probably worked pretty well too. Here's my version where I tried to manually remove the spurious slurs from thre MSCX file within the MSCAZ archive. Less foolproof because I might have missed something, but it seems to basically work. Way fewer corruptions, anyhow.
In reply to OK, that probably worked by Marc Sabatella
Thank you so much - definitely things to look out for and your version definitely opens much faster and is workable again!
But yes, very large scores will be slow to work with. I can't imagine one so large that it would take *minutes* per operation, but seconds would be believable in a score of hundreds of measures for fdozens of instruments, especially if the parts have already been generated (saving this step for last helps a lot).
Please do attach the score in question here.
I have added the score to Shoichi's comment above.
In reply to I have added the score to by sihen
I ask too much to an old PC (Vista) while the antivirus works.
Ignore errors and try to open your score
Marc,
I was wondering if you could take the time to let me know the steps you went through to identify and remove the extra slurs?
Si
In reply to Marc, I was wondering if you by sihen
An MSCZ file is a ZIP archive containing a plain text file (MSCX) in an XML type of syntax. I extracted the MSCX and edited in in a text editor, removing suspicious slur elements (16000 of them in a row makes them easy to spot).