8.1.3 and CPU overload CALLING ALL FORUM MEMBERS!

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support

Are you having CPU-overload problems? Which hardware?

Yes
23
18%
No
20
15%
MacBook/MacBook Pro: All OS X
18
14%
PC: XP, Vista, 7
19
15%
With dj sets
6
5%
Production
30
23%
Live Act
9
7%
This thing starts with 120% CPU use with 0 tracks! (unusable)
5
4%
 
Total votes: 130

diogo_semedo
Posts: 66
Joined: Sun Jan 24, 2010 11:47 am
Location: PT

Re: 8.1.3 and CPU overload CALLING ALL FORUM MEMBERS!

Post by diogo_semedo » Wed Apr 28, 2010 1:38 pm

alienguts wrote:Gotta say I had cpu overload problems playing around with the software and figured out how to avoid them, so I don't have them any more and only running dual core. but it seems Macintosh is definitely having problems. also I haven't gotten to using the rewire with other programs yet.

predict a lot of these issues are hardware related, especially in notebook users
How did you solve it?

DS
MacBook Pro 15,4" Dual Core 2,4 Ghz, 4 GB DDR3, xiosynth 49, Live 8.1.3 and .4b, Traktor Scratch Pro, Yamaha HSM80.

alienguts
Posts: 22
Joined: Mon Apr 19, 2010 7:34 am

Re: 8.1.3 and CPU overload CALLING ALL FORUM MEMBERS!

Post by alienguts » Wed Apr 28, 2010 10:21 pm

Yeah if you are running VISTA/WIN7 you need to have a lot more CPU/RAM power just to load the OS and ableton on top of those hungry OS makes even higher req's so if your machine is on the borderline you might want to drop to XP which has much less severe requirements as an OS.

people who are having problems are posting little to no info about them... I'm pretty sure you guys can configure your setups to not lag if you have proper computers.

I dropped the quality from 192 to 96, then dropped inputs and outputs I wasn't using when using multiple midi tracks. Reverb fairly consistently overloads the CPU for me with midi synths. so I steer clear of it. do think there is something wrong with the reverb overloading the CPU to 130%. Midi instruments that use reverb/like effects seemed to cause the same problem in 192.

lotta people don't use midi though, so for the straight up audio users turning off any extra ins and outs. use a different session if you are recording and enable the inputs, but disable them for mixing and mastering.

So if you have no effects, tracks, or anything, and can't run ableton, upgrade your commodore 64. If you have lots of tracks and effects going with inputs and outputs and issues then you should change it to only outputs. or drop effects, especially CPU hungry effects. The tone generator is a good indicator of whether you will have problems, try it with input / output configurations and your track playing.



Oddly enough I get the most distortion when I have two input set. Four inputs creates significantly less clicking. But unless I set it to two output only I get distortion with tone generator
Rebooting is overrated.

spanktron
Posts: 294
Joined: Wed Feb 17, 2010 5:17 pm

Re: 8.1.3 and CPU overload CALLING ALL FORUM MEMBERS!

Post by spanktron » Tue Nov 02, 2010 11:19 am

Hi!
I have Ableton Suite 8 with all the updates and whatever.I use a Macbook with intel duo processor 2,16ghz 4 gb ram and 7200rpm harddrive.
.Before the last update(i believe 8.1.4 or something)
i could almost bet that Ableton is gonna crash during the set and this was independent from cpu load.
Everytime i did a live act participating on a exhibition, Live crashed.This is reeeeeaaaalllyyyyy annoying!
The best comes now.I purchased Massive a week ago.I started playing around to learn some things about the synth.
Everything ok.(I use it as a vst pluggin).
Everything ok,,,,,, untill yesterday....
I did all the updates N.I Service center wanted to do.
So...Yesterday i open Ableton and....
i can`t listen not even to one clip of the ones made with massive , i repeat... ONE clip.Cpu goes minimum to 70-80 % and sometimes activity monitor of Mac
shows 140% load? is that even possible?
I then exported the Midi clip as wav and imported it so i have it as audio so Massive would
leave Cpu in peace by not being used.... :-)
The same goes for The Kick-snare combo.
Exported as wav and imported it again.
Surpriiiise! I can't even use these!!!!????? I only have noises.As if Live uses the Redux instrument over all audio data!noises on everything i do, protecting me
that way from being creative.Yeah!
That happens no matter what i set the latency and buffer size to.
Reading this posts and thinking back, I really love Ableton for the possibilities it offers,
But to be honest , i never, and mean NEVER was able to use Live without problems and really lots of stress.
This is not Good.

spanktron
Posts: 294
Joined: Wed Feb 17, 2010 5:17 pm

Re: 8.1.3 and CPU overload CALLING ALL FORUM MEMBERS!

Post by spanktron » Tue Nov 02, 2010 11:31 am

Sorry.Not 8.1.4
I use 8.2 which is the latest update.
Something interesting i discovered right now.
If i open a new set, everything cool.If i use the one with massive Temperature
goes to.... 80-85 degrees!Without even clicking on something or hit play.Nothing.Just opening the project
is enough for the fan to start blowing like crazy.I am really out of ideas here.
This way i don`t even have appetite to do music.Anyone with a hint or a tip out there?

H20nly
Posts: 16113
Joined: Sat Oct 27, 2007 9:15 pm
Location: The Wild West

Re: 8.1.3 and CPU overload CALLING ALL FORUM MEMBERS!

Post by H20nly » Tue Nov 02, 2010 3:40 pm

^ try closing all your other apps and turn off wifi before attempting to make music otherwise you're just sharing whats left of your resources with Live and Massive.
LoopStationZebra wrote:it's like a hipster commie pinko manifesto. Rambling. Angry. Nearly divorced from all reality; yet strangely compelling with a ring of truth.

Threedee.us
Posts: 1
Joined: Tue Apr 26, 2011 6:40 am

Re: 8.1.3 and CPU overload CALLING ALL FORUM MEMBERS!

Post by Threedee.us » Tue Apr 26, 2011 6:44 am

I had this problem. Using a Live session Rewire into Logic for mixing overloaded CPU 7 and all the rest were almost unused. Changing the rewire mode in audio settings to playback mode fixed it. Now I have plenty if power to run the session with a full stack of waves plugins on every aux channel

Locked