Saving files ....

Gradually nailing the problems with MU4 [and probably also MU3] file saving.

I'm trying to make definitive templates for use with MU4 - which others round here may realise I have a love hate relationship with.

Today I almost pinned it down. It really is a total pain.

The problem is that the program tries to protect users from themselves, but in so doing causes additional problems. I think it detects if changes are made to a score, but then if the score is saved using Save As that's where problems come.

If there's still an instance of MU4 running, for example, it will sometimes [often] try to save files if the program is closed down - but there's a strong chance it will save the unwanted version, not the wanted one.

This is very hard [seemingly] to explain to others, but it has bugged me for the last few years. I am absolutely sure I have lost scores because of this.

If I have generated a new score with a new name I may or may not want the previous score saved. At the very least MuseScore should let me look at the score which it is trying to rescue, as responding to the warning about losing files if they are not saved is as likely to overwrite a wanted score with one which doesn't need to be kept, as not. Whether or not this is due to interactions with the OS I can't say - maybe. I'm using MacOS Ventura currently, and possibly MU4 uses OS level commands to find "recent" files.

Despite this I'm still hoping to have the new template files ready soon.