Score saving & "lost / damaged" scores

• Apr 2, 2023 - 14:34

I completely empathize with users who work on a composition, only to find it 'vanishes', gets corrupted, or whatever breaks the score. This is an for-your-information suggestion. Sorry if it's after-the-fact for you.

For me, when a work-in-progress score blossoms into a 'keeper', I do the following. Maybe it's excessive, but it gives me the comfort of SOME safety. Pretend my WIP score is for strings and brass. The score name is "str_brass.mscz".

After I get successful playback of the score, and have saved it SUCCESSFULLY, I exit MuseScore. I go to the location where "str_brass.mscz" was saved. I COPY "str_brass.mscz" to a 2nd file "str_brass_safe1.mscz".

Next time around, after more is done with "str_brass.mscz", I save it as is typical. Then exit MuseScore, and COPY "str_brass.mscz" to a 3rd file "str_brass_safe2.mscz". Yes, the 'safe1' file has less score and is older, but on the extremely unlikely chance the original and 'safe2' files blow up / get deleted, at least I have one last redundancy.

This is in addition to the 'autosave' trait of MuseScore. It's extra work. Sometimes I end up with 5-7 'safe' copies. But this has saved my a-- a number of times.

BY THE WAY. If your operating system has a back-up program, you might consider activating some sort of configured backup, for even more score safety.

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