Open a file on the older version of Musescore
I'd like to open a score - that I created on MuseScore 3 (Alpha) - on the older version MuseScore 2. It doesn't work and I dislike working on MuseScore3.
Also, I was working on a score when suddenly there was a crash and now it says it's impossible to open this score (MuseScore3) and I cannot work on it again.
Can you solve the problems ?
I'd also like to copy/paste from MS3 to MS2.
Comments
The only way to move a score from version 3 (which is still in testing) to version 2 is to save the score as MusicXML and open it in version 2. Since the internal formats are different, you can't copy between the two.
If you attach the score you can't open here, then it's possible that someone can repair it.
In reply to The only way to move a score… by mike320
Thank you !
This is the score I can't open, fortunately I have another copy on MS2 which contains other modifications but on this one I had made a few things I coudn't get back
In reply to Thank you ! This is the… by TonyVBlue
Oh and sometimes it says it's corrupted (not only this score) because time signature doesn't correspond but I can't understand what I'm doing wrong, it's not possible to write something mathematically impossible
Open in 3.0, export to MusicXML, import that in 2.x.
That score you can't work on anymore: we'd need so see it to be able to check what went wrong and whether it is fixable.
But what exactly doesn't work on 3.0 Alpha (and is it the 1st or 2nd) and what do you dislike (except from the bugs it surly has, that's why it is an Alpha)?
In reply to Open in 3.0, export to… by Jojo-Schmitz
Thanks !
Yes so there are things like for example irregular division (triplets,...), I used to use Ctrl+number and it doesn't work, I have to select it by mouse and makes me lose a lot of time ; + the disposition of the adds on the left changed and are disordered, and it works very slowly, it keeps crashing or it takes 5 seconds for each move I make, all of that is not happening on MS2
About the score I can't work on its' not really a problem because I only made a few changes but I m just anxious it could happen to any of my scores I worked really hard on
In reply to Thanks ! Yes so there are… by TonyVBlue
The sole reason for putting out an Alpha release is to get things like this reported. Best with clear steps to reproduce.
Tuplets should work the same as ever before, when exactly don't they?
Yes, the pallets may look somewhat different, but not by much, can you be more specific?
Slowness and crashes should not happen, but in order to investigate and fix clear descriptions are needed.
In reply to The sole reason for putting… by Jojo-Schmitz
The pallets I guess we just have to get used to it, no problem with that ;
For slowness I don't really not what to say, sometimes it just doesn't respond fast, I have to use Ctrl+S very often to be sure it's not gonna crash at the wrong time, but even using that move makes it nearly crash like you know the mouse get loading and the screen gets whiter and you cannot act for like 10-15 seconds, then it works, or sometimes it closes... I cannot be more specific, but I really appreciate your reactivity :)
In reply to Open in 3.0, export to… by Jojo-Schmitz
I succcessed opening the score by exporting to XML but I cannot add Pizzicato now, it doens't exist anymore on the voices/canal suggestion for the chords
In reply to I succcessed opening the… by TonyVBlue
There are a few things to be aware of. Apparently when you export to xml and import to MuseScore the channels get lost on the strings. To fix this, right click the staff, select Staff properties and then click the "Change Instruments" button and change it to the same instrument. This will restore the channels. I don't know if the channels can be included in xml or not.
The corruptions are likely due to rounding errors in the tuplet algorithms in either the export or import process. If these corruptions were not present in the original version. they really need to be looked at so if the problem is with export it can be fixed. If the problem is import, we need to assure the problem is not present in 3.0 alpha also. MuseScore should never cause itself it have a corruption.
In reply to I succcessed opening the… by TonyVBlue
workaround to get pizzicato back; change the violins to violins (right-click, staff properties, change instrument, looks strange but works)