cpu pegged at 100 after opening .als

[ntr0py]

hey there.

running into an annoying problem, and i'm hoping to gain a little insight or maybe even find a solution.

i've created a live setup using 6 short clips, but chock full of f/x, half-bundled, and half 3rd party...about 12 plugin instances in all.

during the creation of this setup, my cpu hovered around 60 percent usage...during play, it maxxed at 78. the interface became sluggish, but i still got audio out of it.

my problem is that after saving my setup and re-opening, my cpu is instantly pegged, and i cannot start the audio. the cpu monitor in live shows some cpu usage at first, but then drops to 0 and becomes unresponsive. none of the clips will play, even if i begin disabling f/x.

one would think that if you could have put this all together in realtime, have it playing, and be able to tweak parameters, one would be able to save and re-open the document and do it all over again.

so...any ideas? is there a way to check vst plugin chains to see if something specific is just choking?

woohoo8

[cderum]

Hello--

I have crashes just like this all the time, and I've never been able to figure out what the problem is. For me, the problem usually occurs on start-up when firing up a scene with several clips. If I just select one small clip to play, rather than an entire scene, this does not happen as frequently. Could be just some type of cpu stress that is unique to starting up the program?

[Alex]

Hi ntr0py,

if Live's CPU usage goes to 0 it indicates a problem with the audio hardware. On which platform do you use Live and what the audio interface you use?

regards,
Alex

[ntr0py]

hi there.

i'm using an adi soundmax, chipset 1981a on winxp pro.

all the drivers are up to date, no system conflicts, acceleration to 'full'.

its a less-than-optimal pro audio solution...so i wouldnt doubt it is just the card choking. anyway i can test this?

thanks!