Quote:
Originally Posted by clepsydrae
Personally I prefer it the way it is. What's the use case explanation for wanting it on a hard schedule instead?
Edit: oh, maybe I get it: you're using the backup files as a way to time travel through your project, rather than just insurance against loss?
|
This bad scenario can happen now:
I have autosave set to 10 minutes to a separate rpp-bak file. Working on a project, saving it manually as I am used to. I hit "save" manually every 2-3 minutes. After several days of work, something goes wrong and the file PROJECT.RPP which I am working on gets corrupted. In a good faith that autobackup did its job, I would just attempt to open the last rpp-bak file there is. BUT - there is no rpp-bak file at all, nowhere.
This kind of thing really happened to me and to at least one other user here on the forum.
And yes, "timetravelling" is also the case. Scenario - I unintentionally delete a track I've worked on but do not notice it right away. I only notice that after some time when I play that part of the song where that track should play. As I was hitting "save" manually every 3 minutes, there is no other project file on the disk, only the one I have with the track deleted.
This happened to me as well. Since in Reaper bad things can happen by unintentional misuse of too many action, options, by scrips and so on. Not only by a user error but also by a bug in the API, which was silently destroying my tracks and was fixed when I realized it is a bug, found it and reported.