BETTER Crash Recovery and Version History

[m.nash]

Ugh...

I swear this happens to me once a project. Ableton crashes, tries to recover, and infinitely keeps crashing while trying to recover. I lose hours of work.

Yes I know – 'command - S' all the goddamn time. But it's inevitable users will forget.

This is mind blowing how much of a design flaw this is. You've got an extremely powerful music app, and yet a flimsy recovery workflow and proven track record of crashing.

As you can probably imagine, this just happened to me. I am steamed.

Ableton – what good is your app if it crashes and is unable to recover work? I literally may as well not be making music at all.

After searching the help section, the best option I have is to send over the crash files to Ableton to debug for me. Thanks but... there goes my entire weekend time slot that I dedicated to finishing the project. I'm better served spending another hour(s) trying to recreate what I lost. What a shitty user experience.

[pencilrocket]

create file every 10 minutes!

[Tagor]

good point!

why not create a function : Record Project History
if activated Live creates a Version-History and best would be to choose an own raster
where you set how often a snapshot will be done.

like the recovery-points of OS, just with some own options for each project.
this set-up is not global but per project

i.E

- make snapshot each time when open a project
- make snapshot each XX minutes
- replace snapshots older then XX month
- never delete any snapshots or associated files
- deactivate snapshots (best on gig?)

[timday]

+1. Pro Tools, Logic and Sonar all do this. It probably wouldn't be great for gigs as they all hesitate when creating the backup but as long as it can be switched off I don't see why it would be a problem.