Still getting Audio dropouts in Live 4.1

AdamJay · Post by **AdamJay** » Fri Feb 18, 2005 12:33 am

any update on this?
i just picked up a 1.5ghz 12" PB and right out of the box i'm getting the same behavior.
wiped the hd and reinstalled, same behavior.
i've done as many tweaks as i can find, and still i get random peaks and audio drops when the cpu meter is generally hovering at 26%.

vince watson · Post by **vince watson** » Fri Feb 18, 2005 1:07 am

adam, your not still using the maudio that your using on the pc are ya?

AdamJay · Post by **AdamJay** » Fri Feb 18, 2005 1:15 am

nope

all stock.

i just reinstalled OSX and started from scratch.

i just removed all FX too and i'm getting some serious drop outs. i dont know what the hell is going on 10.3.8 and 4.1 (though 10.3.7 did it too). using stock CoreAudio onboard soundcard. 20ms output latency, 44.1khz, no inputs, highest cpu performance.

8 stereo channels... then lets say i trigger another scene of 8 channels and the cpu meter goes to 380% or 500% or something insane, audio is gone. Mind you with just 8 channels going cpu meter is at 14%. i'd really love to fix this. i dont have enough ram to load all the clips into ram, with no clips loaded into ram activity monitor shows live at 175MB ram occupancy. ( i have 512mb).

this is absolutely 100% unacceptable.
i bought this thing for some software development, some of which refers to 3rd party plugins in Live. and i can't even get worry free operation at 14% cpu?

is this an apple issue or an ableton issue? can anyone help?

smutek · Post by **smutek** » Fri Feb 18, 2005 12:21 pm

I don't think it is an Apple issue, there is a thread over in the general section that sweetjesus started. He is on a Windows box and seems to be having the same problem.

http://www.ableton.com/forum/viewtopic. ... highlight=

by-pass · Post by **by-pass** » Fri Feb 18, 2005 12:49 pm

hi Adam,

512 mb of memory is not much.....
If you consider Macosx take with one alleged config (see the sniffio thread)
170-250 mb of memory........ live take with one empty set 50 mb.....
you are directly at 300mb of memory without nothing......
If you change your latency for less that use more cpu and more memory)...
Upgrade your memory for 1g or more ......
for have one comfortable work

see ya

fil

Hardtoe · Post by **Hardtoe** » Fri Feb 18, 2005 7:35 pm

I think this is all bullshit.....why should we need more than 500 megs of ram to run an audio program that streams off the hard drive??? I have been having these problems with Live 4 and my motu 828 for quite awhile, and it is very frustrating and unacceptable when you get one of these "Glitch's" when performing live somewhere...I used the same soundcard and previous versions of Live for years on my lowly os9 iMac g3-400 and NEVER had an audio problem....Is this crap audio dropout the glorious future of "powerful" machines and operating systems??? Is Live 4 the culprit....I feel this should be resolved immediatley, but none of the companies involved seem to willing to admit the fault....

(BTW I regularly run system optimization scripts - SOX - and clean up my harddrive....I also run ONLY Live when playing a show....)

Grrrrrrrr,

Orion

smutek · Post by **smutek** » Fri Feb 18, 2005 10:20 pm

I'm surprised to not have seen a response from Ableton regarding this matter.

I plan on emailing tech support when I get home. I'm interested to see their angle on it.

smutek · Post by **smutek** » Sat Feb 19, 2005 9:33 pm

Interesting development on my end.

I have not restarted my computer since Thursday.

Today, before launching live, I went through my vst and au folders and deleted a bunch of plugs that I do not use, including some expired demos that were sitting in there. I also deleted the iSight audio plugin.

I launched the live set I have described above, ran through all of the scenes, and did not get any glitches.

The behavior is too erratic to consider the problem fixed by cleaning out my plugs folder but considering that 99.9% of the time I get glitches when first launching live I must say that this is a good sign.

Thanks to all who have been helping and I will keep you posted.