major Live audio problem : please help
major Live audio problem : please help
alright, I am not sure if this is the right part of the forum to post on, but here's my problem anyway. I have been pushed to the point of almost wanting to throw my laptop out the window and gettin a one man band set up like the dude down at the county fair. Well, on to the problem. First off, I am running a HP laptop, Pentium 4, 2.4ghz, and 1 gig of RAM (brand new). - Now, while working in Live I have about 25 tracks or so, but only about 10 playing sound at any one time, with like 6 or 7 effects. The thing is, when I open up the set and play it though the first time, my computer runs at about 30-50% throughout and there are no rough spots. Mind you that I have to run at 32000 sample rate to lower the CPU load. So, all is fine and dandy, not the best sounding, but I can sequence a song and get the structure nice and worked out. Now heres the main problem, after stopping and replaying the exact same song over and over, the CPU usage goes constantly up. The same section of the song that was playing at 30% cpu before is now playing at 75+% and the audio is completely getting mangled so much I have to either shut down my computer manually of wait a few minutes till it ends. I can't for the life of me figure out whats goin on. I have purchased a brand new hard drive, upgraded my RAM, and am pretty much running a virus free computer. Can anybody point me out to as why my computer is behaving so glitchy? Is this an Ableton problem, or do I maybe have a bad processor? Any help would be appreciated.
based on your computer description, what you're describing isn't too far out of line with what i've experienced on mine. fortunately i rarely need more than a couple of tracks, so i never get too hot under the collar.
the part that is disturbing is that the cpu usage climbs. i'm not sure what to make of that.
tips to lower cpu usage: do not use complex warp mode unless it's really necessary. certainly you should never have this as your defauld warp mode!
bounce vsti tracks to audio, keep a midi track for each one, and then delete the vsti's from your set.
set your reverbs to economy mode until you need to render or resample. use return/sends to use a single effect, rather than having multiple instances on several tracks (for appropriate things, i.e. delays,verbs=yes, compressor=no)
there's the track freeze feature but i'm a bit scared of it myself. this may be completely irrational. people often complain about it though so i stay clear.
the part that is disturbing is that the cpu usage climbs. i'm not sure what to make of that.
tips to lower cpu usage: do not use complex warp mode unless it's really necessary. certainly you should never have this as your defauld warp mode!
bounce vsti tracks to audio, keep a midi track for each one, and then delete the vsti's from your set.
set your reverbs to economy mode until you need to render or resample. use return/sends to use a single effect, rather than having multiple instances on several tracks (for appropriate things, i.e. delays,verbs=yes, compressor=no)
there's the track freeze feature but i'm a bit scared of it myself. this may be completely irrational. people often complain about it though so i stay clear.
thanks for the quick reply. I just ran the Live 5 performance test and heres what happened. It started fine, but was all the way up at 70%......I let it play for about a minute and all of a sudden the program started squeakin and burpin like a little rotten baby. So I stopped it, and pressed play again. Same settings and all, and it starts floatin around 80% until it complety goes bonkers again. Then I pressed play again and the song wont even run without comletely sounding like audio constapation. I have no clue what is goin on here, it can't be a bad hard drive, because I have a brand new one, can't be the RAM cause thats new also, and my computer is relatively fast at 2.4ghz. I can't figure it out at all.
-
DeadlyKungFu
- Posts: 3603
- Joined: Tue Aug 09, 2005 8:26 pm
Mess around with the audio buffer size and the plug in buffer size in the Options->Preferences menu, the higher these are the more MIDI latency you'll have but the audio will flow better. I only run 512 Mb RAM (I need to up that, but I'm lazy) and I tend to change this depending on what kind of project I'm doing.
Don't use 33kHz sampling, use at least 44.1, you owe yourself that much.
Make sure there aren't any programs running in the background. Reading a PC optimisation guide can really help This one is really good.
Don't use 33kHz sampling, use at least 44.1, you owe yourself that much.
Make sure there aren't any programs running in the background. Reading a PC optimisation guide can really help This one is really good.
-
sweetjesus
- Posts: 8803
- Joined: Wed Mar 31, 2004 3:12 pm
- Location: www.fridge.net.au
- Contact:
-
DeadlyKungFu
- Posts: 3603
- Joined: Tue Aug 09, 2005 8:26 pm
I forgot this:
Options -> Preferences -> Audio -> (very bottom) CPU Usage Threshold. That's the setting at which Live let's your PC crap out.
With a set that big you don't want to hit the RAM button in Clip View. Live doesn't know what you're gonna launch next so it has to have at least the start of all the clips in RAM, putting a single clip entirely into RAM eats uses it up.
Is there ANYTHING running in the background?
if that doesn't work, get a kick drum, tie it to your back, put strings from your feet to drumsticks on each side, get an accordion...
Options -> Preferences -> Audio -> (very bottom) CPU Usage Threshold. That's the setting at which Live let's your PC crap out.
With a set that big you don't want to hit the RAM button in Clip View. Live doesn't know what you're gonna launch next so it has to have at least the start of all the clips in RAM, putting a single clip entirely into RAM eats uses it up.
Is there ANYTHING running in the background?
if that doesn't work, get a kick drum, tie it to your back, put strings from your feet to drumsticks on each side, get an accordion...
-
sweetjesus
- Posts: 8803
- Joined: Wed Mar 31, 2004 3:12 pm
- Location: www.fridge.net.au
- Contact:
yes this has happened to me but only with hyperthreading ON which you say you dont have (but id like you to double check in the bios)Phokus wrote:Tried the ASIO4ALL drivers, and not much changed. Still same problem. When I first start the test its as low as 45%, then jumps to 60 and up from there. Has this happened to anyone else? I have ruled out the hard drive, sound card, and RAM, what else other then the program itself could it be?
cheers.
-
theshaggyfreak
- Posts: 89
- Joined: Tue Mar 28, 2006 4:32 pm
- Location: DC Metro
- Contact:
I think I am definitely on the same path as you. My next computer will surely be a Macbook or Imac, they seem to have much sturdier hardware, and much fewer problems such as viruses or driver issues.
By the way, I looked through my BIOS and can't seem to find anything out about hyperthreading, is there something special I should look for? Only thing I can find is video buffer settings and a few other things.
Well, its just time to wait til I can save up some money for the Mac!
By the way, I looked through my BIOS and can't seem to find anything out about hyperthreading, is there something special I should look for? Only thing I can find is video buffer settings and a few other things.
Well, its just time to wait til I can save up some money for the Mac!
