MuseScore 4 autosave not working. MACOS Monterey 12.6.3
The autosave feature is not working. MACOS Monterey 12.6.3
I checked the session folder and only found a .json file. It doesn't seem to make any difference if you change the interval in Preferences. Is this the only place where autosaved files could be?
| Attachment | Size |
|---|---|
| Screen Shot 2023-02-23 at 9.55.07 am.png | 152.23 KB |
Comments
Autosave files are no longer in the old MU3 location, they are now in the same folder as the score itself, with the word "autosave" appended, and normally marked hidden.
In reply to Autosave files are no longer… by Marc Sabatella
Thank you. The autosave file is indeed in the same folder. It isn't hidden but looks like this:
1 Terzetto.mscz.autosave_saving
If you remove "autosave_saving" you can then open it with MU4.
Not sure if I was doing something wrong before, but it's working now.
In reply to Thank you. The autosave file… by Left Bank
The auto file does not have the word "saving" in it. If you are seeing that, it's something else (maybe e a temporary file also created during the process).
As a further comment the autosave was working for a while - as noted below - but now is not working. My workaround is a smartphone app that reminds you to save every 3 minutes. It is a shame as MU4 works perfectly otherwise.
In reply to As a further comment the… by Left Bank
Can you be more specific? What exactly is happening to lead you to believe that autosave is not working?
Of course, you should be saving often anyhow, in any computer program, that's just plain common sense. Again, autosave is not a substitute for saving normally, it's just a failsafe in the event of crash.
In reply to Can you be more specific? … by Marc Sabatella
Just now I was working on a score for about 20 minutes. The autosave is set at 3 minutes in preferences. The attached screenshot shows the hidden backup folder and file, but there is no 'autosave' file. Recently, I was seeing an autosave file as well, but it isn't happening now.
In reply to Just now I was working on a… by Left Bank
Is the file still open, and you've actually made changes to it? The other file you were seeing was, I think, a red herring - as I said, the "saving" should not be seen normally at all as far as I know. It shows up very briefly during the save and then gets deleted, or renamed anyhow. I just tested again and that's how it works _ iwas able to watch the "saving" flash briefly before the real autosave file appeared.
In reply to Is the file still open, and… by Marc Sabatella
The screenshot I sent was made after the file was closed. i had made extensive changes during the 20 minutes. After recieving your reply I opened it again and made some changes and an autosave file did appear - see attached, which was made when the file was open.
Ah! I think I get it. When I closed the file, the autosave file disappeared. I guess this is how it is meant to work - as you say the autosave only comes into play if there is a crash. I was confusing it with how Sibelius autosave works - the files stay there & end up cluttering up your hard drive. Thanks for your prompt attention. I'll continue to save frequently.
In reply to The screenshot I sent was… by Left Bank
Precisely - since the autosave is there solely to allow you to recover unsaved work in the event of a crash, once you successfully close the file, the autosave no longer serves a purpose and is deleted.
There is a separate backup file that does indeed stick around "forever". You can see it in your original screen shot, in the ".mscbackup" folder. This one is created at the beginning of an editing session, the first time you save a file, to record the state of the file before you started editing. That way if something bad happens during the editing session, you can always get back to the way it was at the start of the session.