Live 11 Sudden CPU Spikes

[Calagan]

As i mentioned before: error analysis hints to an OS failure
as it happens with other daws, too.

Sorry, maybe its the language barrier but I don't get what you mean.
Could you explain more in details ?

[c1c2]

I am sorry that my English is too bad, so: It does not seem that Ableton Live
is causing the spikes.. They also happen with Bitwig e.g.

I would not be that concerned if I did not plan to go for a live set up..

[Calagan]

I am sorry that my English is too bad, so: It does not seem that Ableton Live
is causing the spikes.. They also happen with Bitwig e.g.

I would not be that concerned if I did not plan to go for a live set up..

ok thanks for the additional explaining (by the way, i was speaking about "my" language barrier ah ah ah)
mmm... So it means there is quite an issue... How could we fix such an issue ?

[c1c2]

By adding useful information. And by error analysis. Most of the posts in this thread are missing
basic information like the OS on which Live is being used. If it is Windows 10 or 11, which measures
were taken to solve the problem, etc. Keep on going.

[c1c2]

Meanwhile I have found a good lecture more detailed than anything I have read before:
https://www.cantabilesoftware.com/glitchfree/

[c1c2]

OK guys, I have found the final solution:
https://www.youtube.com/watch?v=sbXzM60ad8I&t=549s

Most important part is this:
powercfg -attributes 54533251-82be-4824-96c1-47b60b740d00 0cc5b647-c1df-4637-891a-dec35c318583 -ATTRIB_HIDE

You can do the settings for core parking yourself then.

But give the video a try, no bullshit, Latency fixe for me, no spikes at 64 samples... Gone!

[cotdagoo]

Saw this on reddit posted by someone who uses RME Babyface Pro audio interface - https://www.reddit.com/r/ableton/commen ... sues_when/

Sounds like using an older Windows 7 driver resolved a few stuttering issues, might be worth trying if you run out of ideas

[wilfsdad1965]

i'm also seeing this.
what i see in win task manager is the indexer going bananas.
My guess is that after you've done a bit of recording or consolidating of clips, the ableton indexer runs and is in the same execution class as ableton itself. it should run as a lower priority task so it gets less cpu if it's going to randomly start in a the middle of a recording session and run in the background simultaneously. what i do is just take a break to let it do it's thing, and then it settles down and i can get back to work.

[emilioasstevez]

I've been dealing with this problem since building a new workstation in April. Only recently did I upgrade to Live 11, but nothing changed, so I submitted a ticket on Monday and haven't heard anything back yet.
Windows 11, Intel i5-13600K, 32GB RAM, and an Intel Arc A770, which might raise some eyebrows but doesn't seem to be in anyone else's system who's having this issue. My audio interface is a PreSonus Quantum 2626, a thunderbolt interface, which has two expansions bringing the total in/out to 26/26.
I've noticed that when trying to record an occurrence of this with OBS, it has mitigated the problem, until today. CPU is often spiking above 1000% (one thousand percent) in Live while task manager reports about 5% usage. It doesn't seem to matter what my block/buffer size is set to, if it's 32 or 4096, doesn't make a difference. The session I'm trying to work with today currently has four tracks and two EQ plugins.
I should mention everything was fine with Live 10 on my old machine, with the same audio interface - Windows 10, Intel 6700K, 32GB RAM.
Now, for others with a PreSonus thunderbolt interface, this might help you: In Universal Control, if I go to Settings, then Options, in the General tab there is an option to "Enable optimized PreSonus power plan for Thunderbolt audio streaming". With this option enabled, Live behaves much better, with the caveat that my CPU is pegged at 100% which makes the fans very loud. Not ideal for a studio environment, but it's something. Maybe this information can help somebody, hopefully the developers too.
Anyway, this is really frustrating. This isn't some hobby for me, it's what I do to make money. It's disheartening to see a bunch of stuff I don't need and will never use in the release notes, while this problem isn't being acknowledged here or, apparently, by support.

Did you ever find a solution for this? I'm in the same boat with the same audio interface on Windows.