More useful features would be ... When the OS detects that a certain driver is running too long, that it immediately sends an email to the CEO and shareholders of that company to let them know that their drivers suck and are hindering audio processing
I miss improvements in the process scheduler area to prioritize applications with near real-time requirements.
My computer is quite powerful. But I still have some feeling that once I have heavy I/O on e.g. SATA/SSD, it somehow affects other things on my machine.
Remembering back to the days when I used a really wonderful Unix OS, no matter what load you had, you could just type on the console with no lag. Drivers and process schedulers just did their job. Even under heavy CPU, disk and network loads.
I think Microsoft has been setting the wrong priorities for many years ... and maybe even hiring the wrong people who no longer know what a customer expects from a system and how to design and compute performant operating systems.
We have systems with so many cores these days and in many cases even with a high single thread performance ... and you can produce wonderful benchmark results ... but when it comes to processing audio, I have the impression that all this performance goes "nada nada" ...
As vinark mentioned a few days ago ... the competition between nVidia and AMD can cause GPU drivers to run for too long (to produce the finest benchmark results) and thus produce a too high a DPC load, so audio is again compromised. IMHO this is totally unacceptable for operating systems.
I expect to be able to unpack a system and be able to do what I want, including audio processing, without having to come up with anything (customization, troubleshooting, measuring) especially if I'm spending a lot of money on powerful components.
X10SRi-F, E5-1650v4, Win10Pro21H2, Cub10Pro, UFX+, XTC, 12Mic, ADI-2 Pro FS R BE, RayDAT