The Not Enough Memory Issue

[Int Feel]

The set in question does use quite a few Spectrasonics Onmisphere plugins that are memory hogs, but I have created similar Live sets the past without issues.

I had no idea that I was limited to 4gig memory regardless of my computer memory and that is my mistake for been ill informed.

Can you recommend a reliable program to measure the ram i am using in real time before I send over the Live set as Activity monitor in OSX shows I am only using just over 2 gig when the problems starts and on reading this thread I do think there may well be a bug.

[Debrecini]

Hey Ableton - how about fixing this fundamental liability BEFORE coming up with brand new features for Live 9?! I think we'd all just be happy with a perfectly working - non-crashing - version of Live 8... call that "Live 9" if you want (and then charge us a ridiculous amount for the upgrade).

Haha I agree I'd happily pay a price for a stable 64bit version of Live that could address loads more RAM. Live 9 had better deliver on this issue. I run out of memory all the time as I do use VST's like Omnisphere that hog tonnes of RAM. I'm running Snow Leopard and have 8 gigs of physical RAM in my Mac Pro. Its just a massive shame that Ableton cant quite use my system to its full potential.

I cant think of anything more important on the list of features Live 9 should have. The industry as a whole is starting to come around to 64bit now. More and more sound card and hardware manufactures are starting to release 64bit drivers. Its high time the DAW of our choice Ableton did something about it too.

Until that time it looks like we are all restricted in what we can achieve with each Live set... Unfortunately

[danger]

Same happens with me too, high clip count, 6-7 synths and Live goes mad... Bring the 64bit version please!!!

[zee verkawound]

Live is just a toy until this issue gets fixed, it seems like everyone knows this except Ableton. What's really sad and down right infuriating is that Ableton will not admit as much, but rather dodge the all too real issue by referring to it as a "quality" issue and not an out and outright obsolete design. You can't make a silk purse out of sow's ear and you CANNOT expect Live to perform worth a damn until it's 64bit. 1.8 gigs of usable ram before the program crashes is a complete joke. It pisses me off that I spent so many years learning this program and buying one version after another only to be stopped dead in my tracks because Live's present antiquated status.

[danger]

Same here, around 1,6 - 1,8 Gb of ram and virtual memory it goes crazy, actually i think this must be a bug but give us 64 bit version to be sure! Not just out of memory error but when i try to load a vst(i) Live says: Failed to create VST "xxx". The VST Plug-in could not be located. Please check your File/Folder Preferences.

[Adamove]

Hmm. Is there anybody out there who uses an Windows XP3 with an Quadcore Q9400 with 4GB RAM
and Omnisphere and Trilian, RMX who has these problems with Live 8?
I use still Live 6 as this works perfect since. I would like to use the Akai APC40 but for
that I must upgrade to 8 and as I read this thread.... I can`t help myself to do it as I read
this problems and all the trouble.
Please, if there is anybody outside who has similar setup which works with Live 8, let me know.
Thank you very much in advance for your information.

[danger]

git this answer from Ableton:

On Windows XP Professional, Live can now address 3GB of memory, if the /3GB flag is set according to:

http://www.microsoft.com/whdc/system/pl ... AEmem.mspx

Find the boot.ini here:

Start > control panel > system > advanced > startup & recovery settings > edit button

Paste (overwrite existing) this into the boot.ini file and save it:


[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro with /3GB" /3GB


Now restart your machine.

[monkey72]

hmm. so I thought I was the only one having this problem. I had it on 8.0 and ableton told me to update to 8.1.4.... and guess what.. Same problem. I cant even open my live set and freeze a track without it saying "out of memory". Whats up with this? I have have a bunch of 16 battery set ups with ableton triggering midi clips and it simply cant do it. My cpu monitor is telling me I am using 2.68gig of ram on my 4 gig macbook pro 2.4ghz. How come I can run 10 channels or more of battery on logicpro without any issues whatsoever.
I just spent 3 days programming my live set for an overseas tour and now I am buggers.
I am now considering going back to my original set up... My trusty AKAI MPC3000 which have never crashed once in the 13 years I have owned it....

Help ableton...sort this out..

[taylortronic]

I have been having this problem, myself. My CPU meter is cool, but my RAM is through the roof resulting in crashes before my set even loads up.

However, I have found that by eliminating unnecessary scenes I stopped getting crashes. In one case I had been copying long tracks into my set from other sets with long clip counts and wound up with thousands of scenes. By dragging the tracks into a new set and deleting the long empty scenes each time I was able to reconstruct my set (in very little time) and the same set that crashed my Live loaded up and behaved itself rather nicely.

In cases where this didn't work, highlighting the track's clips in the browser and dragging them into the set didn't also copy in the empty scenes that had been saved in the source set.

I haven't seen any responses along the lines of checking your scene count... but that was the straw that broke my Thinkpad's back so I thought I'd share. I also, set my paging file to 1.5 times my RAM and switched to windows classic theme. Who knows? It didn't help me until I brought the scene count down.

One other thing... ideally Ableton would allow a virtually infinite scene count without taxing your RAM, and ideally it would support 64-bits so that I could spend an ungodly amount of RAM on my set alone and never worry about RAM overloads. But not having to write my own software that does all the things that Ableton has pioneered since the first release is closer to ideal than not having the program, so thanks to Ableton and good luck at a smarter RAM management update. I know it's frustrating, but I'll take it.

[hexatron]

i've been having this problem constantly lately, for the first time. on a brand new macbook pro, running far less than i usually put in my sets. trying to finish tracks for a show coming up and i've wasted at least 2 hours on this issue tonight. really sucks.

[wrongun]

Yep, me too. Windows XP sp2, 2G ram. Once a set gets beond the initial stages and I start building it up into a song this happens. If I try to freeze a track, it happens. If I try to export audio, it happens. Very annoying, I cannot go any further with my music. Using a fair chunk of 3rd party VST's, no loopers, nothing loaded into ram.
Never had this problem with L7. And im getting nowhere near to the size of the sets I was doing then.

[Ableton_David]

What versions of Live are you using?

[wrongun]

Happens on all versions ive tried, presently on 8.2.1
Thanks

[NF]

First of all, the reason for the crashes is maybe live caused by so many looper instances.

In the other hand it also could be the OS!

I´m a semiprofessional live act. together with a friend we use my pc(32bit XP sp3 4GB installed and 3GB used RAM) and his mac osX 10.5.X.

pasteing the projects into one set was not possible either with mac nor with pc.
especially my pc showed me the "fatal error - out of memory" message and just droped the session as live never been opened before.

after serveral tries I recognized that windows XP sp3 32bit was not able to give live the ram for its instances. everytime live crashes when the RAM was filled up to 2GB.

The funny thing is that my mate was ill and I had to take out two laptops to perform live for 1.5h

after a while I installed Windows 7 64bit and I tried the same. pasting both sets together. and...

TADAAA my RAM is filled till 3,79GB and everything is fine.

So a one 1.5h set with synths clips and FX is running now on one mashine.

Please stop flaming on the Ableton guys. Allocation is also an issue of the OS as you can see on the registry trick.

With XP I found out that the programm stack of windows was full. the OS has a programm stack and it was filled with the instances of synths FX and at least with the clips and its warping algorithms.

then I disabled the sound drivers. the set opened fine and used 2GB. I recogniced that the sound drivers were not able to be loaded into the windows programm stack. so it seems to me that the os had no capabillities and limitated the RAM.

let live work 32bit, the allocation is a OS thing. the OS gives live the space it wants. btw live uses internally a 64bit audio engine. so where is the problem??
thats the windows side.

I don´t know if a 32bit OSX has the same allocation problems with its programm stack.

any ideas?

[gosuyun]

i have the same problem, when i load my track ableton completely slows down and after doing anything the error message appears and ableton shuts down.

what the hell is wrong here??