Converting Musescore 3 to Musescore 2
Good morning!
The new version (Musescore 3) works very bad and slowly and I would like to convert my new created file into Musescore 2. How can I do it? Here is this file.
I'm sorry for my english.
Thank you,
Ivan P
| Attachment | Size |
|---|---|
| Золотой_петушок.mscz | 42.9 KB |
Comments
Export as musicxml in 3, import in 2
Can you be more specific about the problem you are experiencing with this score? In general, MuseScore 3 should be at least as fast as MuseScore 2, and I don't see anything going noticeably slow with the score you attached, nor do I see any evidence of other problems aside from an easily-corrected glitch with the formatting of your custom-edited tempo text.
In reply to Can you be more specific… by Marc Sabatella
For me, it takes at least 5 times the time to open up MuseScore 3, and it seems to always crash from actions which are not even that demanding. Id stick to MuseScore 2 for any new projects in the next few months.
In reply to For me, it takes at least 5… by JBMusic87
Slow startup would likely be a large file with no thumbnail in your recent files list, you might try revert to factory settings. If you are experiencing crashes, we would love to fix them, please open bug reports with sample scores and steps to reproduce.
In reply to Slow startup would likely be… by Marc Sabatella
Hi Marc, I'm experiencing something interesting. When I close musescore 3, it crashes. Not a huge deal because I am closing it anyway, but something interesting happens. Anything that has been auto saved is safe, but if I try to close it before saving I get the dialogue asking me if I want to save before I quit. I click save and then as musescore is quitting, it crashes almost immediately. Even though I clicked save, nothing that wasnt already auto saved will remains.
In reply to For me, it takes at least 5… by JBMusic87
same thing for me
it's actual shit cuz it just keeps crashing
musescore 2 wouldn't have done this to me
In reply to same thing for me it's… by Abigail Sandiford
If it crashes often, then it should be easy to give us a sample score and steps to reproduce the problem, and then we will be happy to fix it! Although we would appreciate more polite language here...
In reply to If it crashes often, then it… by Marc Sabatella
Bruh
In reply to Bruh by HorrisHuberdale
I'm not a code contributor so I don't fix issues. However, from my experience, scores made by MuseScore that crash MuseScore are among the highest priority fixes. One of the code contributors will likely drop what he's doing to find a fix and get it deployed for the next release. No one can knowingly fix a crash if they don't have a score to reproduce the crash.
In reply to I'm not a code contributor… by mike320
I'm editing a Musescore 2 file at the moment, and it keeps crashing (I can send if nec). I've had a couple of similar issues in the recent past. I'm not entirely happy with Musescore 3, and it certainly doesn't seem to be able to handle Musescore 2 files well. Why is there a difference anyway?
In reply to I'm editing a Musescore 2… by accipitres
If you want us to investigate a problem, then yes, you need to attach your score.
To answer the more general question:
Enormous improvements in the default layout were made - it's called "automatic placement" - but it means that manual adjustments made in older versions - especially those made to work around deficiencies in those older versions - can turn out to be counterproductive. So indeed older scores might not look the same. Usually it's easy enough to update them, but you can also keep MuseScore 2 on your system for those scores, while continuing to take advantage of automatic placement and other improvements in MuseScore 3 for new scores.