Musescore 3.0 is not a good starter
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.
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
In reply to As to the 2nd issue: this is… by Jojo-Schmitz
It's a shame, though, when I exchange files with friends who are still on version 2.
Not dramatic, because I just do a version 2 version too, but would have been better if they were backwards compatible.
Thank you for the explanation.
In reply to In see. It's a shame, though… by mrfdes
It would blow up the code base and turn into a maintenance nightmare for a comparably small team as MuseScore has vs. e.g Microsoft
In reply to It would blow up the code… by Jojo-Schmitz
Yes, I do understand that.
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 As to the 1st issue, it's… by Jojo-Schmitz
Yes, I have had this issue since day one.
Apart from that, once it is loaded, Musescore 3.0 works flawlessly, it is just the startup that can be very annoying.
By the way, Happy New Year.
In reply to Hi, Yes, I have had this… by mrfdes
Yeah, happy new year ;-)
Is it maybe starving for RAM? Or loading some huge soundfont or score (unlikely if it does this since 1st start)?
You could try using the -s or -w CLI options to check whether sound or Web Access is the culprit
In reply to Yeah, happy new year ;-) Is… by Jojo-Schmitz
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 Mystery solved. I had… by mrfdes
So it wasn't happing since the very firts start, actually MDL was the reason I asked ;-)
In reply to So it wasn't happing since… by Jojo-Schmitz
Yes, I must have forgotten about the very first time (Using MS 3.0, I mean :-) ), so, you must have had your suspicions about MDL too.
As I said, now MS 3.0 starts up like a flash of lightning.
Thanks for your help.
In reply to Yes, I must have forgotten… by mrfdes
Yep, MDL is know for it's extreme delay in startup
In reply to Yep, MDL is know for it's… by Jojo-Schmitz
Yes, and, who knows, maybe in due time something might be found to cure that.
Believe it or not, but in spite of everything, MDL does interest me in some way.
In reply to Yes, and, who knows, maybe… 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.
In reply to Loading MDL requires loading… by mike320
Thank you for your ever golden advice.