I upgraded to SL last night & since, My cpu is reading 29% with a blank Ableton project open.
Thing is, Activity monitor shows that Ableton is causing the cpu meter to rise to 29%.
Within Ableton, Abletons cpu monitor reads only 1% ?
Then My fan starts to kic in when I run a loop..
Any ideas guys?
Macbookpro 2.4 Intel dual core
SL 10.6.7
Ta.
Get a PC!
(Sorry but I dont get to say it much!!)
thanks W… lol
check your preferences. make sure your sample buffer is up.
weird …
checked the pref, all audio settings are as normal, 256 buffer & 44.1 sample rate! … fixed permissions, installed the Ableton 8.2.2b6 beta too…
no joy…
?
call ableton. put your buffer to 512. 256 is pretty low for normal use.
yeah tried that too...
Its just Ableton .. all else is completely smooth as normal on SL..
very smooth infact ! seems like a nice smooth upgrade indeed..
A more responsive system for sure !
I left it as long as I could b4 upgrading to SL but Cubase 6
dropped support for Leopard so felt it was time now to take the plunge so to speak
& upgrade to the Snow..
Even Reason is smooth & sits at 2% ... hm ?
yes, will contact Ableton support,
Ta.
let me know what they say. Im curious as to their solution. they are always really helpful too.
Are you running Snow Leopard in 32 or 64 bit mode? Ableton is 32 bit only so if you are in 64 bit mode the computer might be using processing power to run in compatibility mode…
thanks,
Does SL not boot up in 32 by default ?
& how can I tell?
Here is My System overview… does this make any sense ?
System Software Overview:
System Version: Mac OS X 10.6.7 (10J869)
Kernel Version: Darwin 10.7.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Computer Name: Lenners’s MacBook Pro
User Name: lenners (lennylen)
Secure Virtual Memory: Enabled
64-bit Kernel and Extensions: No
Time since boot: 1 day3:02
Does the above ‘64-bit Kernel and Extensions: No’ mean that the system is currently running in 32bit mode ?
:w00t:
:hehe::hehe: am a lit confused …
seriously?!
[quote]…Get a PC…[/quote]
…and embrace the blue screen of death 
I have Snow Leopard 10.6.7 running on my MacBook Pro 2.4Ghz Core 2 Duo without any CPU issues.
Just curious…
- Do you have 4 GB 1067 MHz DDR3 of memory?
- What version of Live are you on? (e.g. 8.2.1)
- Do you have any cracked or expired demo plug-ins still showing up in your plug-in devices folder? (If so try deleting–this involves looking in library/Application Support, library/audio, library/caches, and library/preferences folders for that plug-ins files and moving them to the garbage)
I was able to reproduce the 29% cpu in Ableton & SL by leaving it running over night (with one plugin on a midi track). However, after I close the app and opened it again the cpu was back to 0%, but when I added the plugin back it went to 10%. That suggests there may be a memory leak in the app.
Now logging off my Mac account and seeing if that makes a difference.
ta…
yes I may have some demo plugs for sure…
yes to the ram & yes to live version …
will check it out now…
ta
Yes Ableton got back …
its completely normal apparently for My macB.Pro
to be in the 29’s at start up…
I think its completely mental tbh… 
Ableton said
“Live is at the moment still a 32 Bit application and not capable of hyperthreading. Therefore Live might use more CPU power from the start than Cubase.
As i said, if you are experiencing any problems in your workflow feel free to send us in a status report, but so far it all seems to be normal here and i am sure that you will be able to enjoy the use of Live on your machine, even if it is using more CPU power on starting up.”
hmm?
I still dont really understand or know whats going on… if I am being truly taxed of 29% cpu…
All I know is yesterday in Leopard I was not taxed so to speak, today after upgrading to SL I’m taxed big time :w00t:
all to do with the way Ableton talks to SL regarding the core’s, multi cpu support.
SL opens the doors to Open CL, type of open-source code that allows the developer to hyperthread the cores. Ableton does not support this as yet but does support multi core processing since version 6 or7 cant remember as such…
Well, its all too confusing for lit old guitar fingers me …
what ever happened to the ease of stringing a instrument & playing.
Music making is a different universe since back in the day…
looks like I need to buy another cpu… (which I might add… is completely normal:hehe::w00t:)
mad :crazy::w00t:
sorted 
From Ab Support & Some good info here …
- “CPU meter” in Live:
This is actually not a real CPU meter but an audio engine load meter. It shows the headroom that is available to process all audio data in the required time. The more this value goes up to 100% the more unlikely it gets that all data is processed in time.
The information that this value will add up the usage when running multiple cores was wrong. Please apologize! Indeed this meter can show values above 100% percent but that means only that not enough processing power is available.
So, the name “CPU meter” is technically not completely correct and I hope that at least the documentation gets corrected accordingly, soon.
- In the Activity Monitor it’s true that a machine with for example 4 cores has a maximum CPU load of 400%. So, here every single core is calculated with 100%.
- I also think that 29% idle CPU usage in the Activity Monitor is a bit to much. Please rename Live’s preferences file temporarily. Please make sure that Live is not running while renaming this file. If you have older version of Live installed please rename/remove the Preferences.cfg of these versions, also.
The file can be found here:
/Users/[Your User Name]/Library/Preferences/Ableton/Live 8.2.1/Preferences.cfg
Then restart Live."
& I did & now… cpu sitting between 8 & 11 % (same as Cubase 6)
:w00t: