I have a hard time believing, as long as BiaB has been around, that timed backups were never added to this program's features. What can possibly be the reason for not including them? A false belief that BiaB never crashes? Because it does. Just recently I've dealt with two -- well, they weren't crashes, they were lockups, but they amount to the same thing when you have to manually shut down the program using the Task Manager, and you LOSE YOUR WORK!

I know that sometimes BiaB can pull itself out of (not responding) lockups, but not always. I confirmed this today when it locked up. I left it alone for a half hour and it was still in a (not responding) state. I had to manually shut it down, losing about an hour's worth of work I'd put into a file I'd been working on.

If I may use Cakewalk as an example, it actually uses two backup features -- one is a timed backup where the user can set the interval, and the other is a utility that activates after Cakewalk unexpectedly crashes. This utility asks the user if they would like a backup made of the current file(s), and when the user indicates "yes," the file(s) are saved to the same directory they came from. I deal with Cakewalk crashes on an all-too-frequent basis and I've found this last minute file rescue to be very useful. Essential. Because it saves the file from the last second the program was running, whereas the timed backup feature saves the file from the last 'save' interval.

So, BiaB folks, please give this request some serious consideration. It is way past due for BiaB to have a timed backup feature. And having the post-crash file save feature, like what Cakewalk does, is also a very handy thing to have. It's saved me mountains of work.

Best,
Michael

My Music:
https://soundcloud.com/michaelmcbroom/albums