Editing MS 1.3 Files with MS 2+
I am starting a project to correct MS 1.3 files which, when opened by MS2+, report corruptions to the file.
I am running into strange happenings, Foe example, in the below file, when I select a whole rest to fix the corruption in M86, Staff 3, MS2 does not act right or enter my new rests to fix the measure. This also happened on M45, Staff 20. Question: Would it be better to just fix my Anasazi Opera files in 1.3 after the corruptions are found by MS2+? Then transfer the 1.3 file to MS 2 afterward? The "corrupted" files do fine on playback, but Marc says I should not risk allowing the corruption to exist/ Could that cause a crash or something later on when I might wish to print the files or extract parts, Etc? P.S. MS2 won't even let me close the file ,save the changes I tried to make, without also going to save and replacing over the existing file--I already know how risky that would be! ??????????? This inability to close without replacing the existing file in my documents is scary. I did make a copy of the file, so as not to lose it, but it seems you should be able to make 1 change in a score without having to save it by replacing the whole file??
I thought that fixing these files would be not hard at all, but as usual with me, it's turning into a tech nightmare. Ideas, anyone?
| Attachment | Size |
|---|---|
| -213.mscz | 99.16 KB |
Comments
While it shouldn't be necessary to go back to 1.3 to fix corruptions, it's a clever idea if it happens to work better, and sure, 2.0 will like correct 1.3 scores more than it likes corrupt ones.
But you are mistaken - you can *certainly* save your changes without replacing your old file. In fact we have advised over and over you do exactly that. Not sure how that point became confused; I thought we were extremely clear about that. To restate then: you absolutely positively should, immediately upon importing an older file, save it somewhere *other* than on top of the old file. MuseScore even tries to help prevent you from accidentally overwriting the old version - if you simply do a "save", it will prompt you to enter a new name, precisely so you *won't* simply overwrite the original. If I were you, I would immediately copy all your important files to a separate drvie - perhaps a USB flash drive as we have mentioned before - so be absolutely sure tthat even if you do get confused again and accidentally tell MuseScore to overwrite your original, you can still restore it from the flash drive.
Anyhow, when I load the file you attached into 2.0, I don't see any corruptions reported. measure 86 looks fine to me in all staves, as does measure 45.
In reply to While it shouldn't be by Marc Sabatella
Well, Thanks for looking at the measures--since you did not see any corruptions reported or actually see them in the measures, it means somehow my corrections went through and were saved, since both measures were missing 1/8 th of a beat in 4/4 time on rests.However, when I closed the file and reopened to check, MS2 was still saying file corrupted and pointed out the errors again. Puzzling. I had a very bad time getting MS2 to enter a whole rest for me to fix the measures. It kept entering one and a half whole rests, 8th rests, and half rests, and kept fighting me on entering the rest I wanted!
OK--I'll work at being absolutely clear about the saving, closing. I always save your comments, but this one I will copy somewhere and try to memorize it. and keep referring to it. Sorry.and yes, I have the files copied to a flash drive for safekeeping. I assume if you select "make a copy" under File, MS2 must make a copy of it in my Documents. Then you would have extra copies sitting around in Documents? (Or maybe Downloads.) On the prompting you mentioned, All I remember seeing is the title of original file in blue- then you should rename your new one by typing in version2 or something.? Is that the prompt? Hope I got that right. Really, music tech is much harder for some people than others.
In reply to Well, Thanks for looking at by delhud2
If you find another score where entering a rest does something other thasn you expec,t just post it and preicse steps to reproduce. it should work, and does normally, but perhaps the corruption in your score was preventing it - that is part of what corruptions do.
"Make a Copy" does indeed create a separate copy.
When you save, call it whatever you want - it's your computer. I'd be more likely to give it the same name but put it in a different folder. You might consider seeinbg if any local community organizations offer basic computer literacy courses - these things are not at all MuseScore specific, or even music tech specific - all computer programs work essentially the same ways in these respects.
In reply to If you find another score by Marc Sabatella
OK--I'll probably consult Windows help more, for one thing.