Many normal apps don't care if there are slight stutters as the system say pages in some memory.
This all has caused some controversy with those users upset at Apple. but the paging is so extensive it can decrease drive life). The sign to some folks that they are not running in memory is the load on that internal SSD, with some users noticing that the paging to that drive has reduced the expected wear life of the drive (something not an issue for normal use. the Apple Silicon Macs have an impressive fast memory paging to the internal very fast SSD drives, and impressive fast memory compression with their Arm based processors, and for many apps that gives the illusion that the small memory configuration Macs are running in memory. Running plugins can make that worse, and autotune is not going to help. If you can run at 32 samples on a good day with a properly spec/configured system you are doing well. Unfortunately you are likely just working in a configuration where these errors are going to be expected. not HDX) is all about optimizing the IO buffer size down to the whatever level the DAW will run with without being unstable (in the case of Pro Tools throwing AAE CPU errors). Tracking at lowest latency with native DAWs (i.e. All I know is that I wasn't crashing every 5 min on 2022.4 I am very sure that my problems are coming from 2022.6 also, I won't get any error codes if I was to command-s the program would just freeze up and give me the spinning beach ball. the memory pressure chart is shown in the yellow area while using pro tools.
I have a Focusrite Scarlett Solo 3rd gen I recently updated the driver for the interface. I am tracking within pro tools I use an 1176 and auto-tune to track, my buffer size is 32 when tracking.