Musescore 3.0 is not a good starter

• Jan 6, 2019 - 13:22

I must say I like version 3.0.
However, I always have problems when starting the program up.
Either the splash screen stays up for ages with the wheel spinning, or the Musescore icon turns up in the taskbar and then disappears for a long time until the program finally starts up
It never crashes completely, but always takes a very long time to start up.
I use Musescore 3.0 on Windows 10 64-bit.

Another thing (or should I mention that in another topic?): I find it very unfortunate that version 3 is able to load version 2 files but not the other way round.
Thank you.


As to the 2nd issue: this is by design and deliberate decision. Is easier the same between 1.x and 2.0 and most probably will be the same between 3.x and 4.0, if and when that happens

As to the 1st issue, it's that happen ever since the install? I'd doesn't for me and that problem has been unheard of since release of 3.0 Beta 1

In reply to by Jojo-Schmitz

Mystery solved.
I had accidentally installed that Musescore Drumline, and just as it did in version 2, it also causes trouble in 3.0.
Now I have removed the blasted thing Musescore 3.0 starts up perfectly and keeps working without a hitch.
Your hint made a bell ring.
Thank you ever so much and keep up the good work.

In reply to by mrfdes

Loading MDL requires loading a lot of data, so it takes time. On a dinosaur like mine, it takes too long to load a feature I rarely think about using. If your main purpose is to write percussion music, then waiting for MDL to load is a minor inconvenience. If you sometimes write percussion music, then you have to decide for yourself if it's worth the wait every time or if you would rather use the normal percussion in MuseScore.

Perhaps an command line option to ignore extensions should be considered. You could then have one shortcut that starts with MDL and one shortcut that starts without it.

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