Ableton Forum

hi was having real problems getting live 6 to run smoothly over the past 2 weeks since i got the program.

everytime i would start a set with a good ammount of clips in it it would just skip and pop all the time, especially after being left alone for while.

i optimized the laptop with all- i mean all- the tips posted over the 140 odd so pages of bug hints, but still i was stuck with the problem. (it got better with optimization but was never perfect)

but today i've managed to get it to run rock solid never missing a nanobeat even as i opened reason as a slave in the background and tried to crash it with my a few dodgy vsts.

the secret?

2 new 1 Gig sticks of Kingston Value Ram and virtual memory turned off! (cheap as chips)

paid only $120 for em both and now i'm actually worrying about the music again.. so happy i registered and decided to say to all those who are having problems after trying everything else (Eg. changing 4pin fw to external pcmcia/ disabling midi/ changing fw soundcard)


a good test i found was to run what you would consider a "stressful" live set and have ableton running in a mini window. then press f11 repetedly. if your music starts glitching then you need more ram.

i hope this works for anyone having similar problems.



Original setup-POD XT Live/Presonus Firebox/ Ableton/ Lappy 1.8Ghz 512MB ram/-Korg Trinity-

I also received a huge performance boost when going to 2GB and turning off Page File.

However, please beware that if your session goes over the 2GB ram limit, it will crash - terribly. And don't try turning the page file off with less than 2GB, it will cause many, many problems.

ive had to do this too!

but for me i found you can avoid some nasties in terms of hitting memory barrier and instant crash by setting the page file to like 10MB and then using the option in this thread: http://www.ableton.com/forum/viewtopic. ... he+options

hmmm.. so is this something to do with the amount of R. A. M. space the audio you've played is occupying? In other words, once I've hit play on a Gb worth of audio files, they're all in the R. A. M, so when I hit play on the next one, will it hang momentarily as it reallocates R. A. M. space or something?

this is the sort of problem I'm having &, now that I think about it, it only seems to occur after I've played about 1 Gb worth of files. I originally posted a different thread about this because I didn't think my problem was the same as the one in this thread, as I'm only DJing from Live & hence don't have a "good ammount of clips" open really - it's only about 12 or 13 or so that I'll have to hit play on before I start getting this problem, but that's about a Gb!

now that I think about it, I only have about a Gb of hard disk space left as well... the cache option you linked to, if I switch it off as described in that thread, will it access the R. A. M. or hard drive?

Funkstar De Luxe wrote:I also received a huge performance boost when going to 2GB and turning off Page File.

However, please beware that if your session goes over the 2GB ram limit, it will crash - terribly. And don't try turning the page file off with less than 2GB, it will cause many, many problems.

So, is it the 2 gigs of RAM, or turning off virtual memory? Because I have 2 gigs of RAM, I rarely get any stutters right now even using the on-board sound until I get a decent firewire soundcard (viz, Ultralite). But on the XP side, I have my paging file set to 3024 (as musicxp.net says it should be strictly allocated at 1.5-2x RAM.

Best,
AB

i believe the problem is to do with windows internals.

despite live's request of the use of the file cache (page file/vm) windows will take requests of information from disk and post it to the VM temporarily confusing live ..

dont need 2 gigs, just turn off page file and use the -usesystemcache option thingie