Hello everyone,
I´ve bought a laptop and I´m extremely disappointed about the capability to work with low buffer size in Ableton Live 12. Here the specs:
AMD Ryzen 7 8845HS
AMD Radeon 780M
32 GB LPDDR5X-6400 (Dual Channel)
2 TB Samsung 990 PRO | PCIe 4.0 x4
I´ve debloated Windows 11 PRRO following this guide: https://www.kvraudio.com/forum/viewtopic.php?p=8820694#p8820694
I´ve a Audient ID 4 sound card. In an empty project, as soon as I set the buffer size to 32 or also 64, the CPU usage goes to 20% (32) and 10% (64).

Since for some reasons I would like to stay on the Windows side, even tho I know that Mac OS is way better for music production, I would like to build a desktop computer with probably an PCI-Express card like the RME Raydat.
As far as I know Ableton needs single thread power. As reference I´ve tried to "copy" a XMG workstation and those are the components:
https://de.pcpartpicker.com/list/hsVY74
I live in germany and the grand total is around 1.500€.
Is this gonna be a good long term investment or with the new CPUs, there are out there better options?
Also if this build is way too much, I would be happy to buy a build around 1000€ and save some money.

Thank you!

 

What are you doing in Ableton that you think is necessary to run 32/64 samples buffer and being overall concerned with latency?

 

I don’t program synths, I prefer to play notes on the keyboard. Plus I’ve a TD3 and soon a Nava 909. I would like to run all of them nice in sync without latency

 

That laptop should be fast enough to do way more than you are describing, so something doesn't sound right.

Ableton 12 + Windows 11 brand new install, sounds like a recipe for possible latency issues to me. Do you have Ableton set to use the correct Audient driver? I think I would try another DAW, or even wave editor to test. Fastest way to rule out Ableton as your problem. Then check your audio interface after that, if needed. Install maybe Reaper and Audacity to test.

 

@sk23sk23, Set the buffer size to 128 or 256 and you'll be free of your problems.

Ableton says: Buffer Size
We recommend using a buffer size of one of the following: 128, 256, 512 or 1024 samples.

Optimizing Windows for Audio

For the best performance in Ableton Live, it’s helpful to make some adjustments to Windows settings, as explained in this guide. Taking the time to set up your Windows PC according to these tips will greatly reduce the chance of crashes and audio interruptions.
https://help.ableton.com/hc/en-us/articles/209071469-Optimizing-Windows-for-Audio

LatencyMon 7.31

The LatencyMon software analyzes and identifies which device, which driver or which service is causing audio dropouts or malfunctions. Real-time audio suitability checker for Windows 10/8.1/8/7/2016/2012/2008 (x86 and x64)
Scroll Down to: System Monitoring Tools www.resplendence.com/downloads

 

as mentioned before, I´ve DEEEEPLY optimised windows for audio, following this tutorial:
https://www.kvraudio.com/forum/viewtopic.php?p=8820694#p8820694
With latencymon I get always really good results, I can post it here in a bit.

 

More Links:
Don't let audio glitches ruin your performances! www.cantabilesoftware.com/glitchfree/
The Ultimate Guide to Optimize your Windows PC for the Stage
https://gigperformer.com/docs/ultimate-guide-to-optimize-windows-for-stage/index.html
Ableton - Optimizing Windows for Audio
https://help.ableton.com/hc/en-us/articles/209071469-Optimizing-Windows-for-Audio

 

thanks but the optimisation that I did is way more drastical then those windows settings

 

If Windows is de-bloated, working perfectly, and not influencing the latency at all; what does that do for Ableton 12 if it has either a cpu issue, a metering or reporting issue, or a latency issue caused by Ableton 12 itself?

 

yeah good question.. it´s not easy to understand! I also use process lazo. There I did "by myself" the configuration, where the debloating I´ve followed absolutely every step of the various tutorials.

 

@sk23sk23, Set the buffer size to 128 or 256 and you'll be free of your problems.

Ableton says: Buffer Size
We recommend using a buffer size of one of the following: 128, 256, 512 or 1024 samples.

 

Think it's kinda normal for DAW's like Live/Bitwig who are already on higher CPU side because of the way their uninterrupted real-time buffers work. Just tried setting 32 buffer on my M1 with Bitwig and it's the same thing, project with few tracks and whole mastering chain is hitting 20-50% of DSP usage, CPU spikes are crazy, but with buffer I usually work (256) it's barely hitting 20% of DSP usage, no spikes or anything.

 

This is Latencymon. The soundcard was set to 44100 @ 128 buffer

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:10:35 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-M9R85AK
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: SCHENKER VIA 14 Pro (M24), SchenkerTechnologiesGmbH
BIOS: 12.08
CPU: AuthenticAMD AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 28478 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 3801 MHz
Reported CPU speed (registry): 3793 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution
of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 464,90
Average measured interrupt to process latency (µs): 8,354118

Highest measured interrupt to DPC latency (µs): 444,0
Average measured interrupt to DPC latency (µs): 1,367202


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 145,457949
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0,002798
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0,002798

ISR count (execution time <250 µs): 869880
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 603,060902
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0,129108
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0,145074

DPC count (execution time <250 µs): 1335611
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 43
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk
while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: msmpeng.exe

Total number of hard pagefaults 21625
Hard pagefault count of hardest hit process: 10605
Number of processes hit: 22


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 24,165263
CPU 0 ISR highest execution time (µs): 145,457949
CPU 0 ISR total execution time (s): 0,284418
CPU 0 ISR count: 869880
CPU 0 DPC highest execution time (µs): 603,060902
CPU 0 DPC total execution time (s): 14,376168
CPU 0 DPC count: 1223708
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,274684
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 69,668336
CPU 1 DPC total execution time (s): 0,159897
CPU 1 DPC count: 34346
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,867883
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 20,257316
CPU 2 DPC total execution time (s): 0,003088
CPU 2 DPC count: 1271
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,871623
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 20,016873
CPU 3 DPC total execution time (s): 0,003134
CPU 3 DPC count: 1154
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,821628
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 22,521487
CPU 4 DPC total execution time (s): 0,007471
CPU 4 DPC count: 2502
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,822893
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 44,972845
CPU 5 DPC total execution time (s): 0,002722
CPU 5 DPC count: 816
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,069645
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 28,552597
CPU 6 DPC total execution time (s): 0,032361
CPU 6 DPC count: 12493
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,229611
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 40,955444
CPU 7 DPC total execution time (s): 0,018911
CPU 7 DPC count: 6757
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 1,031072
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 65,330345
CPU 8 DPC total execution time (s): 0,024631
CPU 8 DPC count: 9530
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 1,227746
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 27,180069
CPU 9 DPC total execution time (s): 0,011536
CPU 9 DPC count: 4290
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 0,993169
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 64,669127
CPU 10 DPC total execution time (s): 0,039889
CPU 10 DPC count: 15568
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1,174036
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 52,075929
CPU 11 DPC total execution time (s): 0,018345
CPU 11 DPC count: 7681
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 0,866599
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 61,563406
CPU 12 DPC total execution time (s): 0,018949
CPU 12 DPC count: 6544
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 0,989587
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 48,990245
CPU 13 DPC total execution time (s): 0,010890
CPU 13 DPC count: 3272
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 0,759063
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 53,889270
CPU 14 DPC total execution time (s): 0,013164
CPU 14 DPC count: 4189
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 0,769044
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 19,926707
CPU 15 DPC total execution time (s): 0,004515
CPU 15 DPC count: 1533
_________________________________________________________________________________________________________

 

Process Lazo:

Ableton Live 12 suite and ID (audient driver)
CPU priority = always -> real time (highest)
I/O priority = always -> high
Memory priority = always -> normal (highest)

44100 @ 128 buffer = 5% CPU usage in an empty Ableton Live 12 suite set
44100 @ 64 buffer = 10% CPU usage in an empty Ableton Live 12 suite set
44100 @ 32 buffer = 20% CPU usage in an empty Ableton Live 12 suite set

I´ve the latest windows updates, latest integrated video card ATI 780 drivers and latest Audient ID4 drivers and firmware.

All the other processes are at the default settings.

 

THE WINNER IS:
128 buffer = 5% CPU usage in an empty Ableton Live 12 suite set

 

I´ve updated the ATI Video Driver to Adrenaline 25.5.1 and then run Lantencymon again for 41 Minutes. Apparently the values are way better!
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:41:00 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-M9R85AK
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: SCHENKER VIA 14 Pro (M24), SchenkerTechnologiesGmbH
BIOS: 12.08
CPU: AuthenticAMD AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 28478 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 3801 MHz
Reported CPU speed (registry): 3793 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 372,60
Average measured interrupt to process latency (µs): 9,601693

Highest measured interrupt to DPC latency (µs): 337,80
Average measured interrupt to DPC latency (µs): 3,342652


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 92,239916
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0,002836
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0,002836

ISR count (execution time <250 µs): 3648833
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 512,063274
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0,134499
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0,146319

DPC count (execution time <250 µs): 5191121
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 145
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: id.exe

Total number of hard pagefaults 18029
Hard pagefault count of hardest hit process: 8168
Number of processes hit: 25


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 89,901679
CPU 0 ISR highest execution time (µs): 92,239916
CPU 0 ISR total execution time (s): 1,116307
CPU 0 ISR count: 3648833
CPU 0 DPC highest execution time (µs): 512,063274
CPU 0 DPC total execution time (s): 57,402604
CPU 0 DPC count: 5138624
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 3,978045
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 71,121012
CPU 1 DPC total execution time (s): 0,006408
CPU 1 DPC count: 1146
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3,322156
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 16,590562
CPU 2 DPC total execution time (s): 0,000361
CPU 2 DPC count: 221
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,305538
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 19,355655
CPU 3 DPC total execution time (s): 0,000087
CPU 3 DPC count: 29
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 3,116839
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 16,350119
CPU 4 DPC total execution time (s): 0,000511
CPU 4 DPC count: 122
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 3,104359
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 18,734511
CPU 5 DPC total execution time (s): 0,000247
CPU 5 DPC count: 82
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 3,633540
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 79,706828
CPU 6 DPC total execution time (s): 0,019386
CPU 6 DPC count: 5887
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 4,515247
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 71,341418
CPU 7 DPC total execution time (s): 0,037805
CPU 7 DPC count: 9195
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 3,796237
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 102,037965
CPU 8 DPC total execution time (s): 0,013093
CPU 8 DPC count: 3580
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 4,265760
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 98,110730
CPU 9 DPC total execution time (s): 0,017401
CPU 9 DPC count: 4684
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 4,024724
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 139,817559
CPU 10 DPC total execution time (s): 0,060187
CPU 10 DPC count: 16653
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 3,973171
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 75,619299
CPU 11 DPC total execution time (s): 0,031782
CPU 11 DPC count: 8055
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 3,299603
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 94,584234
CPU 12 DPC total execution time (s): 0,005001
CPU 12 DPC count: 1263
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 3,549923
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 25,456894
CPU 13 DPC total execution time (s): 0,004183
CPU 13 DPC count: 1127
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 2,857046
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 29,644608
CPU 14 DPC total execution time (s): 0,001344
CPU 14 DPC count: 322
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 2,798062
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 42,458212
CPU 15 DPC total execution time (s): 0,000922
CPU 15 DPC count: 276
_________________________________________________________________________________________________________

 

Your AMD CPU has a base clock speed of 3.8 GHz, which should be fine for you; those are very good values.
You don't need to buy anything new; you already have everything.

 

128 is the sweet spot with Ableton 12 in my findings as well. 32/64 works sometimes but bigger projects choke.
M4 MAX beast here with RME drivers.. I use 32 when I track only 1 instrument for myself, every other project is a minimum of 128 and it's just great, I don't think about it anymore
my 2ct

 

Another question, how shared RAM I should assign to the iGPU? Until now it was 4Gb now I’m trying with 16Gb (maximum).

In the bios there are some settings that I don’t know if could help with the performances:
1) AMD IPU DPM - disabled
2) AMD fTPM switch - disabled
3) NX Mode - enabled
4) SVM Mode (AMD-V) - enabled
5) IOMMU (AMD-Vi) - enabled
6) AMD SMT (hyper-trading) - enabled
7) core performance boost - enabled
Internal sound card, webcam, Bluetooth and card reader are disabled.
8) secure boot - disabled

I’ve all cores manually unparked.

Is everything correct as it is now or I should change something?
Thanks

 

Buffer at 128 is good enough even for the pros with external gear. Trying 64 is a stretch...anything lower is not realistic when using multiple tracks.