CPU use
Re: CPU use
Could you please share your system info and Ableton version? One explanation might be that Ableton is still indexing...
Mac Studio M2 Max and MacBook Pro M1
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Re: CPU use
Thank you for getting back to me and apologies for forgetting the obvious.
MacMini M2 Pro
32 GB RAM
1TB internal SSD
2x 2TB external SSD for samples etc.
Live Standard 12.0.2
Logic Pro 10.8.1
MOTU 828 audio interface
Cheers, Bob.
MacMini M2 Pro
32 GB RAM
1TB internal SSD
2x 2TB external SSD for samples etc.
Live Standard 12.0.2
Logic Pro 10.8.1
MOTU 828 audio interface
Cheers, Bob.
Re: CPU use
Thanks Bob!
Best to open Ableton, give it 10/15 minutes to do all the indexing (1st launch only) and then give it another try...
On my Mac Studio with the same Ableton Live CPU usage with a new project is 1% so their should be something specific going on in your situation
When you say CPU usage are you referring to Activity Monitor in macOS or the CPU meter in Ableton?
Best to open Ableton, give it 10/15 minutes to do all the indexing (1st launch only) and then give it another try...
On my Mac Studio with the same Ableton Live CPU usage with a new project is 1% so their should be something specific going on in your situation
When you say CPU usage are you referring to Activity Monitor in macOS or the CPU meter in Ableton?
Mac Studio M2 Max and MacBook Pro M1
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Re: CPU use
Note: If you compare the idle performance of Live 12.0 or 11.3.25 with earlier versions on an Apple Silicon computer, you might notice a higher % CPU value in Activity Monitor. This is because while Silicon Macs offer both performance cores and efficiency cores, Live attempts to schedule all audio threads on performance cores, to ensure consistent and predictable performance. This may result in a higher percentage of the relevant cores being used, and thus a higher value listed in % CPU. This increase may be expected, and does not necessarily indicate a problem with Live.
https://help.ableton.com/hc/en-us/artic ... d-on-macOS
https://help.ableton.com/hc/en-us/artic ... d-on-macOS
Mac Studio M2 Max and MacBook Pro M1
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Re: CPU use
Thanks so much for this thorough explanation which makes everything clear!
I was referring to the CPU meter in Apple's Activity meter. I now checked the CPU meter of LIVE itself and when idle it reads 0%, going up to about 6-8% when playing some instruments. So I guess all is well.
Thanks again, cheers, Bob.
I was referring to the CPU meter in Apple's Activity meter. I now checked the CPU meter of LIVE itself and when idle it reads 0%, going up to about 6-8% when playing some instruments. So I guess all is well.
Thanks again, cheers, Bob.
Re: CPU use
Sounds good!songman wrote: ↑Wed May 15, 2024 1:41 pmThanks so much for this thorough explanation which makes everything clear!
I was referring to the CPU meter in Apple's Activity meter. I now checked the CPU meter of LIVE itself and when idle it reads 0%, going up to about 6-8% when playing some instruments. So I guess all is well.
Thanks again, cheers, Bob.
Mac Studio M2 Max and MacBook Pro M1
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Re: CPU use
Best to read the conversation, as indexing had nothing to do with the initial post
Mac Studio M2 Max and MacBook Pro M1
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2
Genelec M030; Live 11.3.x and Live 12; macOS Sonoma
UAD Apollo Twin
Ableton Push 2