Old 03-11-2017, 11:25 AM   #1
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default Autosave bug (FIXED)

Problem - autosave does not save every set time interval.



Expected behaviour: To see one rpp-bak for each minute.
(I have set it to one minute for testing purposes.)

I have recently started a post about this but did not get any definitive answer. http://forum.cockos.com/showthread.php?t=187970
bFooz is offline   Reply With Quote
Old 03-12-2017, 06:55 AM   #2
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

It looks to me like the timer is reset every time the user manually saves the project.
bFooz is offline   Reply With Quote
Old 03-12-2017, 07:03 AM   #3
strachupl
Human being with feelings
 
strachupl's Avatar
 
Join Date: Jan 2013
Posts: 648
Default

Quote:
Originally Posted by bFooz View Post
It looks to me like the timer is reset every time the user manually saves the project.
Yes, I also expected to have each backup no matter if I saved or no.
strachupl is offline   Reply With Quote
Old 03-12-2017, 08:00 AM   #4
James HE
Human being with feelings
 
James HE's Avatar
 
Join Date: Mar 2007
Location: I'm in a barn
Posts: 4,467
Default

I think the clock runs in edit time, not continuously. This may be what you are seeing.
James HE is offline   Reply With Quote
Old 07-09-2017, 10:55 AM   #5
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

Bumping this.

Autosave does indeed watch the overall "last save" time and not "last autosave" time. You can easily watch this behaviour at a timer in the status panel below TCP.

This means that when you hit ctrl+s faster than what a set time for autosave is, you get no rpp-baks at all! Which is a huge problem, work-wise and design-wise.

Last edited by bFooz; 10-28-2018 at 05:01 AM.
bFooz is offline   Reply With Quote
Old 10-28-2018, 10:25 AM   #6
clepsydrae
Human being with feelings
 
clepsydrae's Avatar
 
Join Date: Nov 2011
Posts: 3,409
Default

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?
clepsydrae is offline   Reply With Quote
Old 10-28-2018, 10:58 AM   #7
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

Quote:
Originally Posted by clepsydrae View Post
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.
bFooz is offline   Reply With Quote
Old 10-28-2018, 11:30 AM   #8
clepsydrae
Human being with feelings
 
clepsydrae's Avatar
 
Join Date: Nov 2011
Posts: 3,409
Default

Ah ok. You've convinced me. +1 for reliable autosaving.

I've never had an RPP get corrupt (hopefully you posted about that, because it'd be a serious bug), but I have changed something accidentally and not noticed for a while.

Mostly I use autobackups for the "in case reaper crashes" scenario, which doesn't need hard scheduling of backups, but I do see your points.
clepsydrae is offline   Reply With Quote
Old 10-28-2018, 11:34 AM   #9
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Fixing, thanks! Also fixing autosave when undo is completely disabled (as it is now if undo is disabled it will often miss the autosave because it thinks nothing had changed).

Saving the undo history to a file (with multiple redo paths) is my preferred way to time-travel..
Justin is offline   Reply With Quote
Old 10-28-2018, 12:01 PM   #10
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

Quote:
Originally Posted by clepsydrae View Post
I've never had an RPP get corrupt (hopefully you posted about that, because it'd be a serious bug)
This was not Reaper related, more of a filesystem or bad hardware thing.
bFooz is offline   Reply With Quote
Old 10-28-2018, 12:02 PM   #11
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

Quote:
Originally Posted by Justin View Post
Saving the undo history to a file (with multiple redo paths) is my preferred way to time-travel..
Will check out that, thanks.
bFooz is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 04:12 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.