Musescore running really slowly after Mavericks update
Just updated my Mac's OS to the current release (Mavericks) and Musescore is now really slow and laggy. Note entry takes considerably longer and scrolling through the slow is very choppy and slow. Curiously, I don't have any problems when I set my magnification to ~400%, but then I work with large scores alot so that isn't very optimal.
Any suggestions/help?
Comments
Have you tried a factory reset?
http://musescore.org/en/handbook/revert-factory-settings
In reply to Have you tried a factory by ChurchOrganist
Yes I have, to no avail :(
Can anyone else offer any advice? I'm in my third year of uni studying music and I sorta need Musescore to write my music for composition courses haha
In reply to Can anyone else offer any by Unbekannt1
There have been a number of bug reports involving MuseScore on Mavericks that leads to me to suspect that even if you get past this slowdown, the frequent crashes will still prevent you from getting much done. It seems somethng in MuseScore - i'd be inclined to think it's the Qt libraries it uses - is just not compatible with mMavericks. Anyhow, assuming backing out of the upgrade isn't an option, I'd probably focus on finding a another computer to use with MuseScore until the compatibility issue ps can be sorted out (either by Apple releasing an update that improves backwards compatibility, or the next version of MuseScore comes out, which presumably will be tested and work on Mavericks).
In reply to Can anyone else offer any by Unbekannt1
Hey Herr,
I'll keep an eye on this issue in particular. It may take some time though before we really find the cause of the problem. And as Marc explained, MuseScore is built with Qt. MuseScore stands on the shoulders of this project to offer platform independent releases.
Have you ever tried out the nightly build for the next MuseScore release? If not, you can download it via http://musescore.org/en/download#Nightly-versions
Run it and tell us whether you have the same issue with this nightly build.
Note: the nightly builds are still considered unstable for serious work.
In reply to Testing with nightly build by Thomas
Thomas,
I've tried downloading one of the nightly builds and it works fine. (I just wish I knew how to change the instrument sounds to the original musescore ones if that's possible!)
In reply to Thomas, I've tried by Unbekannt1
Original MuseScore sound for 1.x means TimGM5MB, for the niglty builds it is a far better one, FluidR3_GM. No idea why you'd want to have the inferior default sound of 1.x?
In reply to Thomas, I've tried by Unbekannt1
See:
http://musescore.org/en/handbook/soundfont
Original MuseScore 1.3 soundfont is TimGM6...etc.
Regards.
In reply to Testing with nightly build by Thomas
For the record, this is probably the problem https://bugreports.qt-project.org/browse/QTBUG-34358
Good to know it works fine in nightlies.
Unfortunately the problem with the sluggishness is still there after upgrading to 10.0.1.
For the sluggish performance of MuseScore on Mac OS X Mavericks, could you try the following:
Could you comment back if this solve the issue?
In reply to Try this workaround and report back by Thomas
Yes! This seems to have fixed the problem! Thank you!
In reply to Try this workaround and report back by Thomas
Yes, I too can confirm, that this helped. It helps only until the next reboot, but still much better than nothing. Many thanks to you!
It has come to my attention that the latest Mavericks update (i.e. 10.9.2) may fix the sluggishness of MuseScore 1.3. It would be great if someone can confirm. This would mean that the "send the Mac to sleep" workaround is not needed anymore.
In reply to Mavericks 10.9.2 update available. by Thomas
I just installed the update 10.9.2 and I can confirm, that the "send the Mac to sleep" workaround is not needed anymore.
For large scores the note entry remains sluggish, but this may have other reasons (e.g. the internal use of data structures whose management becomes slow when they grow).
In reply to Yes, 10.9.2 fixes the problem by sturzi
Yes, sluggish editing on large scores is a general problem, not Mavericks-specific.