clips and CPU spiking

[Rawray7]

Right now my set up involves 6 tracks, two set to channel A, two to B, two to neither. I've been able to map keys on my M-Audo O-Zone to start + stop loops, navigate scenes, and crossfade between A + B. I initially was running into trouble, because I only had 1GB RAM, but when I upgraded to two, my CPU meter went down to about 15% before any clips were launched. I was able to successfully launch 6 clips at a time, load at least 30 scenes, all with the CPU meter staying under control, and the audio sounding fine.

For some reason, right now if I load even 5, 32-bar warped samples I can't even play two or three simultaneously before my computer freaks out. I have tried "save as self-contained set", and (though I still don't understand this option in Live completely) to increase the size of my decoding cache. The only thing that seems to lower the CPU usage is to delete a track.

I am working with very short samples, and am rather confused as to why my computer is freaking out, because only weeks ago it could handle 10 times the number of samples flawlessly. Any ideas? Are there any general tricks for lowering CPU load?

I am not working with any plug-ins (to my knowledge), just directy mapped MIDI commands in live. my setup is: macbookpro 2.0 ghz, 2.0 gb RAM, audio interface: firewire 410, MIDI controller: oZone

[evilxsystems]

I'm having a similar problem with my macbook...I'm waiting to hear back from Ableton about it...it seems like a weird bug or something.

How much free space do you have on your drive?

-jason

[sweetjesus]

Right now my set up involves 6 tracks, two set to channel A, two to B, two to neither. I've been able to map keys on my M-Audo O-Zone to start + stop loops, navigate scenes, and crossfade between A + B. I initially was running into trouble, because I only had 1GB RAM, but when I upgraded to two, my CPU meter went down to about 15% before any clips were launched. I was able to successfully launch 6 clips at a time, load at least 30 scenes, all with the CPU meter staying under control, and the audio sounding fine.

For some reason, right now if I load even 5, 32-bar warped samples I can't even play two or three simultaneously before my computer freaks out. I have tried "save as self-contained set", and (though I still don't understand this option in Live completely) to increase the size of my decoding cache. The only thing that seems to lower the CPU usage is to delete a track.

I am working with very short samples, and am rather confused as to why my computer is freaking out, because only weeks ago it could handle 10 times the number of samples flawlessly. Any ideas? Are there any general tricks for lowering CPU load?

I am not working with any plug-ins (to my knowledge), just directy mapped MIDI commands in live. my setup is: macbookpro 2.0 ghz, 2.0 gb RAM, audio interface: firewire 410, MIDI controller: oZone

although i suggest only doing this at ur own risk, turning off virtual memory within osx may help ur problem. try it out, but read up on it so u dont break ur os.

[southernsteppa]

Unfortunately I have to put up my hand for this one as well. The problem I outlined here: http://www.ableton.com/forum/viewtopic.php?t=60934 seems to be a little more... problematic.

On loading, my CPU meter already reads 10%. Doing anything as simple as moving the cursor in arrangement view makes it jump to 45% and then once play has stopped, it will idle at around 20% - all very new and worrying behaviour.

[southernsteppa]

Rawray - do you have many instances of reverb on your tracks? I tried slowly removing pieces of my project without any luck until I took out the reverb.

Could Live be monitoring the reverb even when it isn't in use?

Edit: I have tried the same project on a PC and a PowerBook G4 - both projects idle CPU usage changes from around 10% to 1% when all the reverb is removed.

[peeddrroo]

maybe try to increase the buffer size of your soundcards and see if you still have issues.