Managing CPU overload

rbro · Post by **rbro** » Sun Apr 02, 2006 1:10 am

Well that seems to be the biggest issue for me and probably many others. I downloaded 5.2b9, but I'm still having major problems. It's almost impossible for me to have even 4 or 5 midi tracks with VST plugins and be able to get any work done. Has Ableton addressed these issues at all, or is this as good as it's going to get until version 6? Any pointers on lowering the cpu load? I've tried freezing tracks, turning off Airport etc., but just get minimal positive results.......sigh......What are the top 10 things I can do to lower the CPU load? I'm running a 1.25 GHZ Powerbook G4, w/1gb RAM

longjohns · Post by **longjohns** » Sun Apr 02, 2006 1:23 am

record those vsti's to audio tracks. keep a midi track for each one in case you want to change things later, but delete the instruments from your set

do not use complex warp mode unless you really need to

slowlygrowl · Post by **slowlygrowl** » Sun Apr 02, 2006 4:11 am

disable dashboard

use shadowkiller for osx(turns of shadows)

hmmm? i am trying to learn more on this subject as well.

anyone else have pointers?

Michael-SW · Post by **Michael-SW** » Sun Apr 02, 2006 2:30 pm

Freezing the tracks *should* fix things. After a freeze you are only playing back pre recorded wav files.

Strange that you don't get any improvments.

rbro · Post by **rbro** » Mon Apr 03, 2006 1:53 am

Michael-SW wrote:Freezing the tracks *should* fix things. After a freeze you are only playing back pre recorded wav files.

Strange that you don't get any improvments.

Freezing helps, but having all those VST's running was killing me. Recording them as Audio and then turning off the VST's in the midi tracks made things workable again. Big thanks to longjohns!

longjohns · Post by **longjohns** » Mon Apr 03, 2006 2:14 am

i still haven't worked up the nerve to freeze a track. it scares me! thankfully i don't really need to since i don't really push the limits of the program.

glad it's working better!

longjohns · Post by **longjohns** » Mon Apr 03, 2006 2:15 am

i still haven't worked up the nerve to freeze a track. it scares me. thankfully i don't really need to since i don't really push the limits of the program.

glad it's working better!

leisuremuffin · Post by **leisuremuffin** » Mon Apr 03, 2006 2:24 am

like others have said, the best thing to do is bounce the track to audio.

remember you can use the "live clips" feature to save the original for editing later if needed.

so bounce, save the original as a live clip, then delete the midi track to free up all the resources.

.lm.

rbro · Post by **rbro** » Mon Apr 03, 2006 3:43 am

leisuremuffin wrote:like others have said, the best thing to do is bounce the track to audio.

remember you can use the "live clips" feature to save the original for editing later if needed.

so bounce, save the original as a live clip, then delete the midi track to free up all the resources.

.lm.

I'm actually leaving all the midi tracks and instruments right where they are. I'm just disabling each instrument and muting each track. The tricky part is knowing when to bounce to audio...I'd rather not have to go back and redo any midi data, so I want to be sure that it's ready enough to bounce to audio.......