This looks to me like a clean solution. I personnaly have never used any of those backup files, but am always disturbed by the quantity that can get in a music directory:
No, MS Office (as well as MuseScore) removes autosave files on a clean file close, entirely different thing. needed to be able to recover from crashes (and you can disable those in MuseScore by setting the autosave timer to 0).
MuseScore has a redundant backup system. If you have not changed it, every 2 minutes an autosave file is created so you will not lose all of your work if you suffer a crash. These files are named SC*.mscz where * is a unique name MuseScore will recognize for this session. These are automatically deleted if you successfully close MuseScore. It also creates the invisible backup file called ,score.mscz. that is only visible if you have turned on show hidden files.
It is just a backup, something to recover from after you saved and closed the score.
Finale and Sibelius has this too (I've just learned, never used those myself), several other programs do this too. Those don't hide their backups though, so cause even more clutter
The backup is in case something goes wrong with the main file. For example, you Save as another score on top of it for example. Another situation we see too often is that something goes wrong during the saving of a file and all or most of the file is filled with 0's. The only way to get any of the score back is to either find an auto save file or the backup. Otherwise the entire score is lost if the user has no other backup system
Comments
Related to #125656: Put the backup file in a separate folder.
This looks to me like a clean solution. I personnaly have never used any of those backup files, but am always disturbed by the quantity that can get in a music directory:
![BackupOverload.PNG]( "BackupOverload.PNG")
Or couldn't backup files be deleted on score close?
This is what the MS office suite does isn't it?
No, MS Office (as well as MuseScore) removes autosave files on a clean file close, entirely different thing. needed to be able to recover from crashes (and you can disable those in MuseScore by setting the autosave timer to 0).
MuseScore has a redundant backup system. If you have not changed it, every 2 minutes an autosave file is created so you will not lose all of your work if you suffer a crash. These files are named SC*.mscz where * is a unique name MuseScore will recognize for this session. These are automatically deleted if you successfully close MuseScore. It also creates the invisible backup file called ,score.mscz. that is only visible if you have turned on show hidden files.
2 Workarounds:
@mike320 What is the purpose of the hidden file backup, if there's already a session-wise backup?
It is just a backup, something to recover from after you saved and closed the score.
Finale and Sibelius has this too (I've just learned, never used those myself), several other programs do this too. Those don't hide their backups though, so cause even more clutter
The backup is in case something goes wrong with the main file. For example, you Save as another score on top of it for example. Another situation we see too often is that something goes wrong during the saving of a file and all or most of the file is filled with 0's. The only way to get any of the score back is to either find an auto save file or the backup. Otherwise the entire score is lost if the user has no other backup system
Fixed in branch master, commit ef42b1b4e9
fix #295310: add an advanced preference option of disabling backup file generation
Fixed in branch master, commit ecf63e4777
_Merge pull request #5372 from Howard-C/generate-backup
[Backup File] fix #295310: add advanced preference option of disabling backup_
Automatically closed -- issue fixed for 2 weeks with no activity.