LIVE 5.02 Causing CPU spikes!

s[riteboy · Post by **s[riteboy** » Mon Oct 10, 2005 10:11 pm

Hi There,

I am getting CPU spikes/glicthes which I experience when I installed 5.01.

I remember there was some old preferences which need to be deleted which corrected this between version 4 and 5.

Has anyone else experienced this and if so have they found a solution?

My setup

- Celeron 2.4
- 512mb Ram
- Windows xp service pack 2

Thanks

ed

Atomikat · Post by **Atomikat** » Mon Oct 10, 2005 10:28 pm

I was getting those CPU spikes/glitches with Live 5.01 but when updated to 5.02 they're all gone...no problems at all.

munn · Post by **munn** » Wed Oct 12, 2005 2:27 am

i'm experiencing some serious spikes too. no problems at all with L4, but 3 or 4 tracks of audio loops in L5.0.2 are causing my CPU to spike to 95% or more! this in no good at all!

i understand that there is a way to dedicate CPU space in OSX 10.4 to certain apps. how do i do this? and will it help?

any ideas?

imac G5
2ghz
2GB ram

s[riteboy · Post by **s[riteboy** » Wed Oct 12, 2005 11:08 am

I have a work around for this issue:---

I uninstalled everything and cleared up all reg entries etc..

I loaded up my set and I was still getting spikes.

The spikes only happening on the initial lauch of some clips. So what I've done is before I started my set I made sure to launch each session down through my set which only took a few moments. When I went back to the start all clips seem to play fine without any spikes/glitches.

Hope this helps people.

ed

whathappened · Post by **whathappened** » Wed Oct 12, 2005 11:38 am

munn wrote:i'm experiencing some serious spikes too. no problems at all with L4, but 3 or 4 tracks of audio loops in L5.0.2 are causing my CPU to spike to 95% or more! this in no good at all!

i understand that there is a way to dedicate CPU space in OSX 10.4 to certain apps. how do i do this? and will it help?

any ideas?

imac G5
2ghz
2GB ram

EXACTLY.... just a few audio tracks causes CPU to shoot thru the roof....
this has been happening for a while now. Each small audio file launched raises the cpu roughly 12% - so as u can imagine it basically makes using Live USELESS as a serious program to complete any task... until this is fixed somehow. and forget about plugins..LOL. you know - this might be funny - but i remember when this was not the case with live. furthermore I have been PAYING to use live for years. this is BS. Ableton customers deserve better than this.

12" Powerbook G4
1.5ghz
1.25GB ram

Post by **Alex** » Wed Oct 12, 2005 11:53 am

Hi munn,

i'm experiencing some serious spikes too. no problems at all with L4, but 3 or 4 tracks of audio loops in L5.0.2 are causing my CPU to spike to 95% or more! this in no good at all!

If the CPU usage goes to such a high value it is clear that it will produce dropouts too. As you write it did not happen with the same Set in Live 4 I would really like to get hands on such a set.

So is this behavior always reproducible in Live 5? Everytime you play certain clip in some certain tracks you get this high CPU usage?

regards,
Alex

s[riteboy · Post by **s[riteboy** » Wed Oct 12, 2005 12:19 pm

Hi Alex,

It seems to be an issue with the clip initial cache.

If a clip is new the cpu spikes sometimes which then causes the drop out.
After all the clips are initialised and you go back to launch them it is no longer an issue.

Edwin

Nixon · Post by **Nixon** » Wed Oct 12, 2005 12:30 pm

that's exactly what i've been whitnessing on my powerbook...when I open a live set and start a clip, the cpu spikes...when I have started all clips once the problem doesn't occur anymore...

Post by **Alex** » Wed Oct 12, 2005 12:35 pm

Nixon and s[riteboy,

does the red "D" LED flashes too when this CPU spike happens?

does it happen in large Live sets only or also in small ones or sets with only one clip?

regards,
Alex

buzzlegs · Post by **buzzlegs** » Wed Oct 12, 2005 12:37 pm

Exactly the same thing is happening to me

Powerbook 1Ghz with 1Gb RAM, OS 10.3.9 with Live 5.0.2

Nixon · Post by **Nixon** » Wed Oct 12, 2005 12:45 pm

I can't check the red led now (i'm at work, hehe, browsing the ableton forum..

but it happens in small live set's as well

s[riteboy · Post by **s[riteboy** » Wed Oct 12, 2005 1:51 pm

Alex in work here also. Will check later on and post back

Thanks

forge · Post by **forge** » Wed Oct 12, 2005 3:48 pm

I'm getting the same thing - I have a large set (all session view) with lots of full length tracks for DJ style mix and if I fire a new one I get the overload with droupout

like Edwin said, it doesnt seem to happen the next time I fire that clip - as if it is to do with it being loaded into ram - but of course I can enable ram mode for all of those clips with only 1GB!!

In 5.01 I was getting blue screens, but I didnt want to say it was definitely live as it's been heating up here in Brisbane so it could just be the heat, but it doesnt seem to be happening any more but now I get the spikes

at the moment I wouldnt be able to play live with it

Nixon · Post by **Nixon** » Wed Oct 12, 2005 4:05 pm

Alex,

I just tried, and the red D led doesn't come on when I play the samples...

this way I really can't use the program, it's just to unreliable, do you have any suggestions?

ow and it seems to happen quite random I might add: I never now wich sample in wich set will spike, and it isn't making things any more clear...

s[riteboy · Post by **s[riteboy** » Wed Oct 12, 2005 4:08 pm

have you tried launch each scene of 1 bar
and then going back to the start:-

1. Before you being ur set launch scene 1 - XX
2. After all screne / clips have been activated the CPU spikes should be gone