PT 2023.6 & Windows Performance Improvements

[take77]

Thought I'd start a thread based on the "Windows OS performance improvements" listed in the release notes.
The exact improvements I'm not sure of but I did notice the system requirements seem to be a bit more accommodating without higher recommendations.

My modest i5 system has run just fine on previous versions and I'd just like to be aware of any bug discoveries among W10 users before getting current again.
I imagine things will work just fine and it would be great to hear of the noticeable improvements as well.

In any event, please share your own discoveries here.

[junkgear]

This was posted on Pro Tools Expert and describes the Windows changes:

Improved Windows Performance
Pro Tools 2023.6 benefits from Microsoft Multimedia Class Scheduler Service (MMCSS) Implementation for the Avid Audio Engine. This improves processor resources scheduling for smoother playback. And it allows AAE to run at a higher priority than some other processes, but not at the highest possible priority. This prevents multimedia applications from monopolising system resources, while still giving them enough CPU time to function properly

[take77]

Originally Posted by junkgear

This was posted on Pro Tools Expert and describes the Windows changes:

Improved Windows Performance
Pro Tools 2023.6 benefits from Microsoft Multimedia Class Scheduler Service (MMCSS) Implementation for the Avid Audio Engine. This improves processor resources scheduling for smoother playback. And it allows AAE to run at a higher priority than some other processes, but not at the highest possible priority. This prevents multimedia applications from monopolising system resources, while still giving them enough CPU time to function properly

Thanks for that info Will. Much appreciated.

I'm also keeping my eye on the main PT forum section. Would like to get current again after things play out for a while.

Have a nice weekend!

[EGS]

Originally Posted by junkgear

This was posted on Pro Tools Expert and describes the Windows changes:

Improved Windows Performance
Pro Tools 2023.6 benefits from Microsoft Multimedia Class Scheduler Service (MMCSS) Implementation for the Avid Audio Engine. This improves processor resources scheduling for smoother playback. And it allows AAE to run at a higher priority than some other processes, but not at the highest possible priority. This prevents multimedia applications from monopolising system resources, while still giving them enough CPU time to function properly

Wow sounds good

[junkgear]

I've never really has issues with my Windows system before, but things are very smooth on 2023.6. I would also suggest that if you follow the old optimization setting of having Windows favor background services over programs that you try switching that setting back to programs. MMCSS threads already run at a higher priority, so switching it to programs will give the Pro Tools application higher priority, which should give you better performance overall.

[EGS]

Originally Posted by junkgear

I've never really has issues with my Windows system before, but things are very smooth on 2023.6. I would also suggest that if you follow the old optimization setting of having Windows favor background services over programs that you try switching that setting back to programs. MMCSS threads already run at a higher priority, so switching it to programs will give the Pro Tools application higher priority, which should give you better performance overall.

^^^Cool. What about manually setting the affinity switch? Manually setting priority above normal? Still needed with 2023.6 & MMCSS?

Originally Posted by junkgear

.... if you follow the old optimization setting ...

How about new AVID recommended optimization/troubleshooting docs for Windows 11? Looong overdue.

[Skwaidu]

Hmm. It seems other DAWs have had massive problems with MMCSS since Win 10 limited it to 32 threads (or in Cubase's case, anything over 6c/12T). There seems to be a ton of discusion about it on GS from way back. See TAFKAT's replies at the bottom of this page, it has links to the old discussions:

https://gearspace.com/board/music-co...hmarks-40.html

I haven't yet been able to test the new version (I would definitely need the Atmos updates!) - but it's looking like high core systems might have degraded performance unless Avid have incorporated it well... (And I'm on 24c/32T which would be in the danger zone already)

[Skwaidu]

Initial testing on Win 11 22H2 / HDX2 / i9-13900K

Performance seems roughly the same, but CPU Package Power use seems to have gone up when I did a few comparisons. So not really an improvement. It could be an improvement for non-HDX users though.

[junkgear]

Originally Posted by EGS

^^^Cool. What about manually setting the affinity switch? Manually setting priority above normal? Still needed with 2023.6 & MMCSS?.

I can’t really say when it comes to processor affinity since that seems to only be needed by some processors and only on some systems. I would think setting the priority higher than normal would not be needed. It’s best to try these things one at a time and see how your system responds.

[Skwaidu]

Originally Posted by Skwaidu

Initial testing on Win 11 22H2 / HDX2 / i9-13900K

Performance seems roughly the same, but CPU Package Power use seems to have gone up when I did a few comparisons. So not really an improvement. It could be an improvement for non-HDX users though.

This was PT 2023.3 vs 2023.6.

As an example, an DAWBench DSP -style "wide" session could run 916 TDR Kotelnikovs on Audio tracks with audio on 2023.3.

It was 920 Kotelnikovs on 2023.6. BUT

I tried the same 916 Kotelnikovs on the new version, according to HWiNFO64, the CPU Package Power went from around 220W to 230W on the newer PT.

Another test, a huge score mix project used 35% of CPU in Task Manager on 2023.3, the exact same spot (same parameters for playback etc) used 39-40% on 2023.6.

I didn't see much difference in thread allocation. So, no significant performance uplift on HDX, possibly even slightly worse - but it seems they didn't at least botch the MMCSS update totally, like some DAW makers had done in the past (apparently).