I love you Ableton, but you're killing me

[The Coil]

This is what I get, constantly.
I've got 12 gb of RAM, 6 cores, a 3.33 ghz processor, every other possible process and program turned off while I'm using Live, anti-virus disabled, and I still get this at least 4 or 5 times a day.
I should be able to have 50 instances of Kontakt running God's very own saxophone library.
I've tried everything. Notice the CPU load meter at a whopping 15%.
That meter is about as useful at giving you the status of your CPU load as the reception bars on an iPhone are at telling you whether you're about to drop a call.
Any ideas?

[Theo Void]

Idea : get a Mac !!!

I have a 2008 Macbook Pro and have NEVER EVER had one single problem w/ it!!!

Just sayin'.

[Spectral_Gate]

Sorry I probably can't be very helpful, as I've never gotten this error in Ableton, but I'm primarily a Logic user and have to deal with this occasionally. What fixes it for me at least is: reducing the number of instrument tracks / freezing tracks / running 64bit (I assume you are already though) / repairing disk permissions etc (running a "spotlight cleanup")(maybe a mac only thing).

Also make sure you're not warping a shitload of clips on RAM mode.
And of course update to the latest Live / or try older versions / restart .
And your CPU meter...meters CPU and can't indicate memory errors.

I should be able to have 50 instances of Kontakt running God's very own saxophone library.

Made me laugh

[ian_halsall]

Which o/s are you on?

[Theo Void]

Dude!!!! With those specs you should NOT be having memory issues!!

I'm on Leopard w/ 4 GB RAM and a core 2 duo 2.4 gHz. and Live runs smooth as ever for me. I use Massive amts. of VST's and my sets get pretty ridiculous.

Freezing tracks and shit like that to save CPU shouldnt even apply when you have 6 cores and 12 gb RAM.

There's def something else going on here.

[memes_33]

mail the abes your track(s) that do this and they should be able to help you figure out what's going on. definitely should have enough juice to run a lot of tracks with a lot of plugins & shit.

[bobland]

Not an expert, but 90% of the crashes I get (PC) are me misusing an instrument, vst or trying to open something that shouldn't be opened. Perhaps, Live shouldn't crash but I can avoid most of them by paying a little more attention.

[ian_halsall]

The operating system and version are critical here.

No use for instance having 12gb of ram if you are running xp or xp pro.

[Warrior Bob]

Isn't Live 32-bit? Which is to say, isn't going to see a whole lot more than about 4GB of RAM? I thought I read that somewhere but I may be wrong.

[Theo Void]

Oh ya. I forgot about that!
I think live does only see 4gb

[The Coil]

Isn't Live 32-bit? Which is to say, isn't going to see a whole lot more than about 4GB of RAM? I thought I read that somewhere but I may be wrong.

I've read, and this may be wrong, that since Live is 32-bit, that it can only use 2 gb of RAM, and that if/when they release a 64-bit version it will of course be able to utilize 4 gb. Also, is Live currently threaded for multiple cores, or is that something that may be in development?

[Fanu]

ah yeah, oh crap, i had the same thing today...i made a new thread, too
killing me, too, as i can't be expanding my live set.
it's got 10 songs with 120 tracks in total (so that makes 12 tracks per song in average).
i'm not using anything super huge.

ive got the very latest macbook pro with 8gb ram, quad-core 2.2GHz cpu...

[Warrior Bob]

Also, is Live currently threaded for multiple cores, or is that something that may be in development?

I believe Live can use two cores, but not more. I think there's an option in the preferences to enable this multicore support. I'd check but I don't have it in front of me at the moment.