Is live meant to crash THIS often?!

[3dot...]

it amazes me that for the clusterfuck that Ableton have let Live become there's still no autosave built in.

THIS x1111111111......

[n8tron]

I haven't had a crash since early 8.0.X versions. Contact tech support.

[JuanSOLO]

Live was running crash free for me since 8.2.2, then I got a new laptop, and then built some new m4l devices, and I've gotten quite a few crashes and sent in reports.

Some crashes seemed to be related to my Audio 8 being used as a midi port for my MS2000, others seemed to be related to midi routing, MOST definitely some are related to m4l patching.

HOWEVER, my new computer locked up a few times trying to use soundflower to send internet audio out through my Audio 8 into my monitors. So it could just be a funky Audio 8, or even the new Laptop.

I agree, many crashes are related to other things working in conjunction with Live, it's silly to try and just blame one culprit.

I do SO wish there was an autosave, or crash file you could reopen.

[sporkles]

Been having relatively smooth sailing here, since updating to 8.2.2. I've had some bad crashes when using the Launchpad, but I've just stopped using it, and now everything's running fine.

[3dot...]

they're probably still thinking of an elegant way to make it almost perfect...

[remute99]

I haven't had a crash since early 8.0.X versions. Contact tech support.

[oblique strategies]

L
HOWEVER, my new computer locked up a few times trying to use soundflower to send internet audio out through my Audio 8 into my monitors. So it could just be a funky Audio 8, or even the new Laptop.

Soundflower can be flaky too. It is not 100% error free.

[Khazul]

I still get "A serious error has occured," on a very regular basis and random crashes when opening GUIs - particularly Nexus or Waves plugs.
New to 8.2.2 has been Live, when instantiated with a project, just hanging when trying to load a new project and having to Force Quit on my Mac.
I just save regularly - it amazes me that for the clusterfuck that Ableton have let Live become there's still no autosave built in.

This is the usual story for running it on windows, on OSX (2011 mbp) I find it way better - only ever had it die once from these random death while dragging and UI type errors. On windows - (various computers) several times a day is typical.

As for auto save - +1 in theory, -1 in practice - unless each auto save is to a new file (I dont want it over-writing/corrupting a perfectly good older version), and its a complete pain in the ass that the undo history that it uses to recover doesnt seem to track settings on 3rd party plugins.

[3dot...]

+1 autosave should write to a backup file...

[Syncretia]

"822 and no crash for a long time. and i use lots of plugins"

Yes. They are probably well tested stable plugins.

it amazes me that for the clusterfuck that Ableton have let Live become there's still no autosave built in.

Well, one thing I'll say in defence of Ableton here is that Ableton always recovers my work when it crashes. I'm using the legit version of 8.2.2. So, don't know what you're talking about here.

To recreate crashing problem:

Open several Reaktor or Max For Live patches in sequence
Watch it die

The problem is that the programming team has focused solely on making sure that there are no crashes in the Ableton codebase. That's necessary but doesn't solve the underlying problem: that Ableton can't deal with something external crashing. When a VST crashes, or a sound card it turned off Ableton @#$#s itself. Ableton needs to be able to handle a VST crash and keep going. It should simply tell the user that a VST crashed and that they will need to reload the VST. Of course the other big problem is that in Windows, when Ableton crashes, it crashes hard. It's the only software I know of where you can't kill the process and you have to reboot after a crash. Seriously painful stuff

[Tone Deft]

auto save would just piss me off.

I know when to save. sometimes I want to play and definitely not save. what about the guy that gets his set all dialed in to play out, he plays out, gets his drunken freak on at the gig, wakes up the next day and his set was autosaved and screw up?

[H20nly]

auto save would just piss me off.

I know when to save. sometimes I want to play and definitely not save. what about the guy that gets his set all dialed in to play out, he plays out, gets his drunken freak on at the gig, wakes up the next day and his set was autosaved and screw up?

then there's the other side of the coin - the time you are working with Live... you leave everything open... come back few days later (for some reason) and find that you have 150 new .als files in your folder...

if there is going to be an autosave feature it needs to have several options/requirements IMO.

1. user decides to turn it on... not default
2. auto save only saves if changes have been made
3. incremented by (optional) time... i.e. every 5, 10, 20, 30 minutes
4. overwrite is either optional, not possible at all, or rotational i.e. after x number of copies + changes (see #2)
5. auto save file is separate from user created file

[Syncretia]

auto save would just piss me off.

I have no idea what the hell you guys are talking about.

Ableton simply saves a copy of your work in a temp folder every few seconds. Then, if you get a crash, it asks you whether or not you want to restore that autosaved version. It doesn't overwrite your actual project. Ableton already has Autosave but it doesn't suffer from the hypothetical problem you have mentioned. Jesus, talk about attacking a straw man.

Perhaps you guys need to upgrade your version.

[Tone Deft]

is it really worth getting all bitchy?

I haven't lost a song to Live in years.

with all the whining up in here I can see users turning Live into a Nanny DAW.

[H20nly]

auto save would just piss me off.

I have no idea what the hell you guys are talking about.

Ableton simply saves a copy of your work in a temp folder every few seconds. Then, if you get a crash, it asks you whether or not you want to restore that autosaved version. It doesn't overwrite your actual project. Ableton already has Autosave but it doesn't suffer from the hypothetical problem you have mentioned. Jesus, talk about attacking a straw man.

Perhaps you guys need to upgrade your version.

so to you the perfect auto save... saves your last version?

well then, you're all set.