Trouble with 4.1

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
beateater
Posts: 43
Joined: Sat Sep 11, 2004 9:16 am

hmmm....

Post by beateater » Mon Mar 14, 2005 8:50 am

Well, it worked well for a while, then the CPU spiking began all over again.
I really am stumped here. Is it possible that something is making the app (live) less stable the more I use it?
It is REALLY starting to annoy me. I've just wiped the computer and re-installed every so that's not really something I want to do, but I'm clean out of ideas.
Is anybody else having CPU problems on sets that ran fine on 4.0?

warabunga
Posts: 215
Joined: Wed Feb 25, 2004 6:17 pm
Location: bern - switzerland
Contact:

Post by warabunga » Mon Mar 21, 2005 1:06 pm

fuck. just had 2 gigs last week-end and live quit on me twice!!!
I was very precaucious and tested all the songs at home, but still live was gone after the first song!!! and I had some dropout when changin scenes...

maybe it's because I am synchronized with an other computer? some tempo issues maybe?

the other person is using live 4.04, I use 4.1.1...

please!!! make your soft STABLE befor adding ANYTHING new!!!
I send you all the logs if you want! peace s
--
macbook pro | Leopard | 2.33 Ghz | 3 Gig Ram | Lemur | Monome 256 | BCF/BCR2000 | Faderfox LX2
I'm Spoiled!

bytheriver
Posts: 360
Joined: Wed Mar 16, 2005 3:53 pm

Post by bytheriver » Thu Mar 24, 2005 12:24 am

Think i'm getting this.

Got just the factory 'hip hop' loop going and playing 'junglist' on a midi keyboard (pcr30) goes rock solid for a while, then huge CPU spikes and the audio drops out.

Weird thing is when I stop playing, lives CPU metre goes down to 20 or so, but the task manager says its taking a good 60-65 for a while afterwoulds.

happens on korgs legacy collection as well.

I was really looking forward to playing live over my DJ sets :(

beateater
Posts: 43
Joined: Sat Sep 11, 2004 9:16 am

hey guys. two things

Post by beateater » Thu Mar 24, 2005 4:53 am

Two things:
1/ I think the CPU meter in Live relates to the % of resources that have been allocated to Live that are being used, not Live's % usage of overall available resources on your machine. That would explain the difference.

2/ I had Live 4.0 and Live 4.1.1 installed at the same time. Thing was there were no undo or preference files in the 4.1.1 application folder.
Things really improved when I deleted those files from the previously installed version (in this case Live 4.0) which in turn forced 4.1.1 to create it's own prefs file when next I rebooted it.

see if that works for you.
Goog Luck

Locked