how often is L8 crashing theese days?

[Sibanger]

Since 8.2.2, I have had no crashes......yet

Just about to test with M4L

[Khazul]

i just wanted to know if i am the only one that has still too much crashes because ableton seems to have finished theire work on L8..
So i wondred wether my computer is maybe broken.. but ... as this poll shows.. L8 is just still not stable..
Or as unstable as it was all the time.

My co-producer has nearly same machine as you and same audio interface and seemed crash free. He does however have latest rme drivers and latest OSX version.

If your sig is upto date then you might need to update. The other thing while he does use some of the plugins that people seem to associate with crashes he doesnt do much in the way of complex routing or processing nor are his tracks counts high. (he leaves the production and mixing to me) so perhaps that why he does not seem to get any crashes?

[dr_loop]

A crash a few times a year, but i'm using Live-Intro so it probably does'nt count..

haven't had a crash in a long time, leave it open all the time with devices connected. about once a week I have to restart to get a device to reconnect.

In these days we should first of all be concerned not to crash our homebase, i.e planet earth. In this respect I would not consider this responsible behaviour.

[jtdj]

im certain that most of the people who dont get many crashes arent pushing Ableton as hard as those who are. Soon as track count gets to around plus 40 and there is plenty of 3rd party VST's on the go Ableton seems to crumble like a sand biscuit at dawn on a friday.

[Khazul]

im certain that most of the people who dont get many crashes arent pushing Ableton as hard as those who are. Soon as track count gets to around plus 40 and there is plenty of 3rd party VST's on the go Ableton seems to crumble like a sand biscuit at dawn on a friday.

Yes - its probably 100% reliable for making minimal bleepy shit with only two tracks each containing an instance of operator and some native live fx

[Synthbuilder]

im certain that most of the people who dont get many crashes arent pushing Ableton as hard as those who are. Soon as track count gets to around plus 40 and there is plenty of 3rd party VST's on the go Ableton seems to crumble like a sand biscuit at dawn on a friday.

No crashes yet on my i5 PC running WinXp SP3 and Live 8.2.2. Loads of plugs including Vaz modular and Reaktor and rewiring Reason 5. Average track count around 30 to 40. Longish songs - typically 12 to 15 minutes - with a lot of automation going on. I only use the session window for mixing.

Live 8.2.1 was a bit crashy with about one crash a month. But these were for the most part repeatable. Crash reports sent to Ableton.

I use Live on average an hour a day - but gave it a real good thrashing during January and February finalising the new album.

[Khazul]

I use Live on average an hour a day - but gave it a real good thrashing during January and February finalising the new album.

OK that translates to about 2 crashes a week for me as I use it about 8-10 hours a day, 5+ days a week - just to put some of the 'it rarely crashes' numbers in perpective.

Crashes over days/months etc doesnt mean alot without knowing use pattern, crashes per continous actual hours of use means alot more. This alone might explain alot of the differences in perception and annoyance - full time job vs occasional hobby use, etc.

[Synthbuilder]

This alone might explain alot of the differences in perception and annoyance - full time job vs occasional hobby use, etc.

Yep, this is why I added how much I actually use it.

I have to say that Live doesn't, for me at least, feel like a crashy programme. Especially when I think of the bad old days with Win3.1 apps. Although, threads like these do make me use Ctrl+s more often than I would normally and have me reaching for Reaper to try it out yet again.

[twisted-space]

8.2.2 has been pretty stable for me in that it's only actually crashed 5 or 6 times (maybe 6 or 8 hours use a week). What I do find however, is it does some strange stuff. E.G. working on an idea last night, I had a drumrack with a 2 bar looping midi clip on a track that reset the loop length to 0 bars everytime I did anything on any other track, save, close and reopen solved it.I've had a track routed to sends only, spontaneously reset to master and numerous occassions where the timing will go t*ts up for no apparent reason and only a restart will get it back to normal.

The problem with things like this is there isn't a crash, and they aren't repeatable, so there is no way you can report it. The last bug I did report is an issue with Analog's envelopes (see here) and the response back was that it was confirmed, but as it was down to AAS to address the problem there was no idea of a time frame for a fix.

It seems to me that the Abes are getting there with Live 8 but I think there's still a long way to go before it's the program it should be.

[hoffman2k]

The problem with things like this is there isn't a crash, and they aren't repeatable, so there is no way you can report it.

Actually, Ableton solved that problem. If you go to the Help menu, you will find an option called "Get Support...".
Clicking on this will create a Status Report Pack. Its like a crash report pack, but you don't need to crash Live to get it. They're very useful for these strange bugs. Just make a pack just after the weird thing happened and tell Ableton where, when and what to look for. If they know its the last thing that happened before you made the Status Pack, they could see the problem immediately.