How to give Live 8 more memory

[OtherJesus]

How do I give Live 8 more memory. (I'm a new user)

I've got a very fast PC and the CPU meter is below 30, yet the D keeps lighting up.

And just a few moments ago I tried to load up 3 drum kits.
I loaded 2 just fine, the 3rd kit crashed Live.

Upon restart I loaded a 3rd different kit but Live told me there wasn't enough memory and that I should "save and quit".

What can I do/settings should I use to allow Live the resources it needs?

Much thanks!

(EDIT)
This same bug (error message) happened to me again a few minutes ago.

This time it was when I tried to open a project that didn't use the same sample/bit rate as the previous project.

I had to open default live set and then change the sample/bit rate to match the project I wanted to open...

Is this correct behavior for live prior 8?
It makes no sense that live can't "detect" that my audio settings are different from project to project and adjust on it's own.

Help?

http://www.myspace.com/waxthedecks

[Kirb]

What kind of computer and what processor does it have, what kind of hard drive, and how much RAM? The D lighting up means disk overload, 'not enough memory' message means a lack of RAM. How big is your project?

[Hervé]

I've got a very fast PC and the CPU meter is below 30, yet the D keeps lighting up.

what's your setup ?

The D lighting thing have been repported as a bug during the beta already
http://forum.ableton.com/viewtopic.php?f=25&t=108659
But no official words for now.

[OtherJesus]

I've got a Open Labs TSE Miko.

Also, that live set won't even open without crashing Live 8.
Thank goodness I had a previous version saved.

[sparklepuff]

I've been complaining about this same issue. Look at my specs, clearly it isn't a hardware problem.

What is up with this "Not enough memory, Save and Quit" bullshit. It's wearing me the fuck out.

[OtherJesus]

"It's wearing me the fuck out."

I'm a new user, so I'm not to that point yet, but I do appreciate how you summed up my thought in a single compact sentence.

IF I had lost my project (not had a previous/backup version) then, yes, I would have been completely worn out.

[sparklepuff]

Well, I've been using Live since V. 4 and have never encountered this error, and as soon as I install 8, I get it almost daily. Makes no sense.

[OtherJesus]

This same bug (error message) happened to me again a few minutes ago.

This time it was when I tried to open a project that didn't use the same sample/bit rate as the previous project.

I had to open default live set and then change the sample/bit rate to match the project I wanted to open...

Is this correct behavior for live prior 8?
It makes no sense that live can't "detect" that my audio settings are different from project to project and adjust on it's own.

Help?

[OtherJesus]

BUMP!

HELP?

[UKRuss]

Like the guys say, it is a reported bug, you may have to wait for the next update for some of these early issues to get fixed.

[tw1nstates]

Live is 32 bit, which means that it can only address 2 gig of ram.
If you try to lead more into live then it usually crashes.

So your 3 kits a re probably more than 2 gigs in total.

It sucks, Live is way behind the curve with this, especially as everyman and thei dog is releasing bigger and bigger libraries.

Ableton have a 64 bit version ready to go but are waiting for rewire I think (this is what i was told by them)

I don't understand why not release the 64 bit version without rewire and if you want to use rewire use the 32 bit version.

Compromise, yes, but better than the current compromise (not being able to addres much ram)

Come on Ableton, let us at that 64 bit version of live you have got gathering dust in the office. .

[darkenedsoul]

If you're running Windows XP and have been to http://www.tweakxp.com and http://www.musicxp.net for tweaking your system (If it hasn't been tweaked yet) to get better performance. I run XP Pro SP3 and 4Gb in the DAW system and it (XP) sees 3.5Gb of the 4Gb). So 32 bit seeing only 2Gb is incorrect.

Also go to start->run->msconfig and hit return and select startup tab. Look to see if there are some processes/programs that have things like adobe quick launch (or whatever it's called) and uncheck the boxes to those programs *you* know you can disable. Then reboot, check the box on reboot to NOT remind you (unless you want to be reminded that you disabled some programs) and that should free up some resources (if this was applicable to your system).

But sounds also like there's a memory issue with Live 8. I haven't done anything heavy to hit this...yet.

Mike

[dancerchris]

It all depends on what you are doing....

You don't give a lot of info in your OP.

What are your drum kits? I use a fully sampled kit (Superior 2) and typically are 600+ megs per kit. 3 of these plus Live would blow out any computer with only 2 megs (including any computer with more memory running XP 32 bit.) Just 2 of these will likely pull down your disk loading, even with fast SATA or SCSI drives. BTW, there are kits out there that exceed 2 gigs with full up miking and bleed that Superior offers. Just one of these will pop just about any system. I have never been clear on whether running Vista or XP 64 will solve this problem because Live (PC version) is a 32 bit application and therefore subject to the 32 bit application limit (seemingly) even when on a 64 bit OS.

If you are just loading 1 hit sampled kits then you may have a real problem.

My suggestion is find out how much memory your samples are loading, this both effects the physical memory and the swap file space (disk loading) used in Live.

My $0.02

[OtherJesus]

They were live Drum kits/racks using the drag drop method from library onto midi tracks.

[whitegirllust]

This addresses something about kits I never thought about. I built a couple hundred kits in drum rack using the upwards of 100 samples per kit. Is this slowing down live when I load them even if I only use a few hits?

What if I delete the unused samples?