Re: CPU usage in Live 10
Posted: Tue Mar 06, 2018 7:11 am
My suggestion is that all those that are experiencing CPU usage issues with 10 need to contact support and show them the problem. That is the only way we can get this fixed.
How must that be clear when, for example, it's not clear to me? While other forums but Feature Wishlist might be read by the support team, Ableton are relying on users to report issues they have in order for support to address the concerns at hand. These issues does not go away by magic, but by cooperation.JAMM wrote:Think it, s pretty clear now for support that there is a big CPU problem.
Maybe they should communicate that they are working on a solution or update or something.
Maybe then i can install live 10 because on a duocore MBP it,s a waste of time.
ExactlyMcAnix wrote:My suggestion is that all those that are experiencing CPU usage issues with 10 need to contact support and show them the problem. That is the only way we can get this fixed.
Testing is never wrong.Nokatus wrote:Agreed. Also, in the mean time, it's good to have this information visible like this also on the public forum, so that people who are contemplating a move to Live 10 know that it is currently this problematic for many users, and so they will test it very thoroughly on their own system before committing to a purchase.
You disagreeing with it doesn't change the amount of individual users reporting abnormal CPU use here and elsewhere. Like you said, testing is never wrong, and when there is such an amount of independent reports of a new major version of a software package causing problems like this, it's of course sensible to test very thoroughly and not be in a hurry to upgrade until appropriately certain of being in the clear. This also lowers the probability of disgruntled user posts after the fact, heh.Stromkraft wrote:I disagree with "problematic for many users". You don't know that. You assume. That's the shape of the thing.
I never claimed it does. I just disagreed with your use of the term "many users". It's a number of users of course, but I've seen worse numbers trough the last 5 years.Nokatus wrote:You disagreeing with it doesn't change the amount of individual users reporting abnormal CPU use here and elsewhere.Stromkraft wrote:I disagree with "problematic for many users". You don't know that. You assume. That's the shape of the thing.
And this amount is in actual numbers?Nokatus wrote:when there is such an amount of independent reports of a new major version of a software package causing problems like this
Well, I agree with all of that.Nokatus wrote: it's of course sensible to test very thoroughly and not be in a hurry to upgrade until appropriately certain of being in the clear. This also lowers the probability of disgruntled user posts after the fact, heh.
What I'm confident of, Ableton will have it working better eventually. This is just the initial release.
That's the main thing , the rest (also this post) is just idle talk around the matter, basically. Like I said, v10 is just at the initial release, and I'm confident Ableton will improve it down the line; they have done so with worse releases, and all in all I think v10 is a very good one. Right now, it's cool just to acknowledge there's a realistic possibility of having CPU issues on a system that runs v9 and other audio software very well, and testing v10 thoroughly before upgrading is the way to avoid that sort of disgruntlement -- in any case.Stromkraft wrote:Well, I agree with all of that.
You need to contact support.buj818 wrote:I hope Ableton is reading these.
What about Enabling "high performance" in the CPU power settings, as Moonsea shared?buj818 wrote:I been keeping up with this thread thinking man, im glad i dont have this problem! Well, it hit me tonight, and hit me hard. A few projects, some 2 track, some up to 9 tracks, all exibit the same CPU usage behavior. Beginning of song, 45-53%, peak of song, 70-90% with crackling then going passed 103% with extreme dropouts. Yes, changed sample to 41, changed from 128 to 256+, flip flopped from ext sound card to internal sound card, and nothing is helping. Only recent change was installing a Waves EQ last night. Removed that, being it was my only change in weeks, and it did not help one bit. CPU in TM shows max of 39% at worst sound quality with a max of 17% RAM used, 0 to 1% disk used. Ive skimmed this an a few other CPU usage threads, no others are finding cures for it. Only difference is that mine started suddenly whereas others had the problem from the get-go after installing 10. Like the rest, I hope Ableton is reading these.
You either set the high performance power plan or go into the advanced setup and set processor power management/minimum processor state from 5% to 100% in the power plan you are using and it will solve the issues.buj818 wrote:
I been keeping up with this thread thinking man, im glad i dont have this problem! Well, it hit me tonight, and hit me hard. A few projects, some 2 track, some up to 9 tracks, all exibit the same CPU usage behavior. Beginning of song, 45-53%, peak of song, 70-90% with crackling then going passed 103% with extreme dropouts. Yes, changed sample to 41, changed from 128 to 256+, flip flopped from ext sound card to internal sound card, and nothing is helping. Only recent change was installing a Waves EQ last night. Removed that, being it was my only change in weeks, and it did not help one bit. CPU in TM shows max of 39% at worst sound quality with a max of 17% RAM used, 0 to 1% disk used. Ive skimmed this an a few other CPU usage threads, no others are finding cures for it. Only difference is that mine started suddenly whereas others had the problem from the get-go after installing 10. Like the rest, I hope Ableton is reading these.
What about Enabling "high performance" in the CPU power settings, as Moonsea shared?