Windows 11 Pro CPU Overload

[Javagenki]

I downloaded Ableton Live 12 this morning, gave it a few hours to index everything, and then kicked off the demo song. However, I'm getting CPU overload warnings while Task Manager shows Ableton Live 12's CPU usage barely reaching 10%. I have a high-performance computer and have closed all non-system related applications, including antivirus software. While Ableton Live 11 wasn't much better in this regard, I thought Ableton had addressed compatibility with multi-core processors by now. Is anyone else experiencing similar issues? My system specifications are as follows:

Processor: 13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz
RAM: 64.0 GB (63.8 GB usable)
OS: Windows 11 Pro
C Drive: WD_BLACK SN850X NVMe SSD 1TB
D Drive: WD_BLACK SN850X NVMe SSD 2TB (Ableton Live 12 installed here)

[kitekrazy]

Demo project used up to 33%. It uses 16% before it's played.

I'm on Windows 10

I guess it's just like every new version of DAWs. There are still optimizations to work on.

[Javagenki]

I built this new PC specifically to handle Ableton Live 11's CPU overloads, but the issue persists. Hoping for better performance with Live 12. @Ableton, any suggestions?

[login]

are you using an audio interface? if so which?

Some stuff that can fix performance: configure energy settings to max performance, check you have any GPU drivers up to date.

[H20nly]

Edited for hope

[murry61]

It appears to happen just with the demo project.
It seems the "Rainstorm" track is the problem.
If you delete this track, and leave all other tracks, CPU returns to normal.
If you delete all tracks and leave only the "Rainstorm" track, CPU usage is high.
I have Standard 12, but I could not find a sound or instrument named "Rainstorm". So I could not identify it .

[Javagenki]

I'm a bit embarrassed to admit that I hadn't updated my Focusrite (Scarlett Solo 3rd Gen) and Nvidia drivers for several months. Once I did, I saw a significant performance improvement, maybe even exceeding what I experienced in Live 11. I'll do some further testing and tweaking to see if I can squeeze out any additional performance gains.