switch6343 wrote:ramses, thanks for your feedback. Sorry for the misunderstanding, I now understand the difference between a driver and the madifaceuse.exe app. Thanks.
In the meantime I purchased Process Lasso Pro, lifetime license, entire home (max 5 PCs), excellent software.
I implemented a plethora of tweaks on my NUC11, both in BIOS as well as in Windows 10 Enterprise LTSC to reduce jitter, elimiate electro smog to the maximum, reduce idle times, allocate CPU (Affinity) and prioritze madeifaceusb.exe, etc. etc. The improved sound quality is stellar. I only now realise how extremely bad Windows (10) is as OS to run any Media Software to play and reproduce music albums. I don't know how it compares to Linux or macOS, but to what I listened until applying all those tweaks. It is almost unthinkable that I was listening to absolute crap, garbage music reproduction for many years. It's a waste of money to try to improve music reproduction by investing in expensive hardware e.g. DACs, amplifiers, expensive speakersystems, expensive headphones. The root of all evil is Windows. I just found out. Glad I found out that a few very good tweaks makes a difference between day and night.
I came across an older post of yours because you highly praised an (overpriced) USB cable last recently and claimed sound differences by better USB cable (which is completely impossible).
Here you mentioned significant sound differences due to Windows optimization, optimizing driver processes, and similar tweaks.
To put it plainly: also this is simply incorrect.
Windows is typically optimized for audio production with DAWs to prevent audio dropouts—if they occur at all. In rare cases, this can happen during audio playback, but often it’s enough to adjust the power settings in Windows.
However, in none of these cases does it result in improved sound quality. It is to avoid clear audio drops that happen because the CPU was not fast enough processing.
If you believe you're hearing sound quality differences, it's most likely due to perception (psychoacoustics).
Regarding jitter reduction, every RME device already handles this automatically with SteadyClock FS. There's nothing left to optimize. Especially in this setup, jitter suppression has nothing to do with process prioritization or similar tweaks.
Windows is not that bad as you claim. Typically, only a little has to be changed for DAW work, in even rarer cases for pure listening to audio. Process Prioritization, Windows Tuning and perceptible audio quality (sound) are two different things.
Windows tuning is for solving issues if the CPU was e.g., blocked for too long by bad drivers. The effect of such issues is even higher when the CPU runs with reduced power in energy saving modes. But this is not about sound.
Audio gaps on Windows can also be solved by making the ASIO buffer size bigger. For pure music listening, this has no impact. Only people who are doing DAW work this can disturb in certain use cases in terms of monitoring (RTL).
BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub14