Ableton Forum

take a look at the 'impulse' thread ive posted and look at what 'fax-01' says about ht. it looks like these 2 threads are coming together.

nuperspective wrote:

stinky wrote:I'd be interested in finding out if that's true... as far as i'm aware, you can only enable/disable HT in the BIOS.. i'd like to know how you disable HT after boot, when BIOS takes precedent... anyone?

ill give it a try. im only going off a reply from a thread alex answered.

yeah, I'm curious about that - let us know how you got on

as I said in the impulse thread, there has to be something obvious like that causing your problems

but as for freeze - I have found it to be totally useless from the start and never use it, it takes a ridiculous amount of time and is actually quicker to just do a proper render and give it a new audio track then disable everything on the other one - you can group the FX then hold alt when you turn off the power on one of them & it will disable them all

im beginning to agree. ive got plenty of drive space so it wont make much difference if i render dry or with fx. ive tried switching ht off today. it didnt make any difference. still pushed 75 - 80%. its the drop outs that are pissing me off. 70% cpu load basically means live is rendered useless for audio. thats not a very high max top end.

another thing - what's your CPU max threashold set to in Lives prefs?

I upped mine from 50 to 80 and it made a difference


you still didnt tell your buffer! not sure it will make THAT much difference, but stll...

ive done that. upped the buffer. upped the latency. etc, etc. no real differences. the audio dropouts have eased a little. im now officially out of ideas.

one thing i dont have happening is the problem moving clips in the arrange page. i can move 40 - 50 clips no problem. weird.

man, you have exactly the same problem as me, crazy we both just brought it up recently. I am seriously confused. Strange how you have the same exact problem where you have a pretty descent processor putting out indescent audio performance.

thanks god im not alone.

haha. Yeah man, this problem is really killin my inspiration right now....I come up with some great ideas and then my freakin CPU overloads before I can finish sequencing or even adding any really cool effects. It really sucks that no one else seems to be experiencing the same problems, or at least they haven't spoke up. Its OK guys, you can come out of the internet closet and share your pain.

yeah. my names nuperspective and ive been a long term suffer of cpu abuse.

ive got it down to decent levels by ditching all instances of complex warping in the session. the audio glitches have stopped and the load is down to around 60 - 65%. i dont know how much more i can put in this session before it happens again. of course all the clips using complex now sound completely different. but hey its a start. i still think the pc should eat this for breakfast though.

Complex = bad news for your cpu.

If you -must- have something in complex mode, consolidate it as complex then run the consolidated track in beats mode & Voila! Complex track with no cpu overhead anymore.


-tim


PS Lee we gotta hook up soon, I'll swap you tricks...

good thinking man. i was going to bug you today over messenger but got quire a bit of traffic from these threads. its been giving me maximum trouble man.

give me a shout when your free and we'll hit the pub. did you get the vocals down last week?

lives freezing IS really anoying. totally independend from the speed of the Computer. it is freakin' slow, compared of what others deliever. plus only one track at a time... grrrr...... ancient.

as much as i like live, but you developers at ableton get yourself together, really. forget about new functions, fix the whole CPU issue first, dual core support, screenredraw, track freezing, plugs, damn these are issues like driving a Trabant. no matter how fast the maschine, even on a tripple core 10ghz liquid cooled CPU, live is freakin' slow. a really great apps, but slooo...w
and that's not funny!

what exactly is freezing a track doing that makes it takes up more resources than bouncing to a track and disabling everything on the previous track? I thought this is what freezing was suppose to do for you -- automatically in the background???