Improved Autosave Logic

[Matthew Simon Fletcher]

Hi friends - my suggestion would be some improved logic around the autosave functionality.

I'm unsure if the functionality of this is fairly basic, i.e. "count down from seconds and save regardless of what is happening" or if there are just bugs/workflows that it doesn't cater for.

A few things I've noticed are:
Autosave causing crashes (think this has been resolved in a recent build but not 100% - including as relevant example)

Autosave happening whilst project is playing - reducing performance and possibly a risky thing to do

Autosave happening whilst in the middle of user operations such as drags/copies/highlighting midi notes/deletes - one of my bandmates specifically asked me to bring this up as it regularly disrupts his workflow - at best it's confusing and at worst he's lost changes and had to undo work due to it not being clear what had happened or the wrong thing happening.

Autosave occuring immediately after a regular save - not a critical issue but would be better to factor in user saves and reset the timer once these are done. This allows the user to avoid being disrupted twice. We all know how important creative flow is and sometimes an idea can disappear, especially if saving a bigger project.

I'm sure there will be other things I've missed.

To my mind the really simple logic should be, "have X seconds elapsed since last save - manual or automatic and is any other task going on? If yes and no respectively proceed with autosave, if not, wait till condition is met".

Putting this in the minor impact category, but it's one of those that over the years has just begin to get more and more bothersome, and my bandmate specifically asked that I raise it if I haven't already