I more and more think that the ASUS mainboard is not quick enough for real time processing.
It's a consumer grade X390 chipset, mostly designed for gaming and overclocking capacities.
This you could eventually find out with the help of LatencyMon, although I have to say that I am not
very familiar with the values that I got approx 2 years ago with LatencyMon under Win10.
Because of changes in Windows they had to change the measurement methodology which
delivers other results, not anymore down to 1 microsecond, more smth in the range of 100 microseconds,
so to say factor 100 less accurate (IMHO).
Consumer Mainboard does not necessarily mean that it does not work reliable.
The problem is simply that there are chipsets / products on the market which perform well,
and some that doesn't.
I made myself this experience with an MSI mainboard approx 6-8y ago.
I could optimize everything, OS and BIOS, but still I got kernel latency timer results not better than 60-100 microseconds.
Then I bought the same board with the letter "A" behind. Same board/chipset, only with a few improvements in terms of SATA6 and USB3 support.
The same installation (I swapped only the board, kept the same installation on same disks) of all sudden had kernel latency timer values down to approx 2 - 20 microseconds.
There are 2 different measuring tools. The DPC Latency Checker tells you everything with spikes up to 1000 microseconds is fine (more or less), The truth is, the more occupied the CPU is by other priotized taks the less agile / responsive it is to serve audio in time with lower ASIO settings and increasing system load.
As a rule of thumb I can only tell, to optimize BIOS and System to get DPC latency as low as possible and that you get a stable / steady CPU clock, that does not change as even clock changes introduce a little latency.
On Win7 I have the information and tools to build such a system. On Windows 10 the problem 2y ago was, that you can not use LatencyMon anymore to measure kernel latency timer which is in my opinion the best measurement, as you get values down to 1 microseconds and by this kind of higher accuracy in your measuring.
Am not sure whether this changed now with latest versions of Win10 and LatencyMon. 2y ago you could only measure on (I had the feeling) process scheduler level and with a resolution over 100 microseconds. Which is simply factor 100 worse.
This is one of the things why I personally tend to stay still on Win7 for a recording system, as I have the experience to differntiate, whats ok and whats not ok.
And there are other things which make me think about whether Windows 10 is already mature enough, like I put together in a blog article 9 month ago:
https://www.tonstudio-forum.de/blog/ind … s-7-EN-DE/
At a certain point also I will have to change to Win10, but I want to move this point as long as possible to the future.
BTW .. last time I bootet my test system I had under Win10 of all sudden issues with audio loss, which was not the case before. This is still not solved. I am not 100% sure whether it came with the latest patches / updates to 1809.
Therefore I will have to restore my golden image of 1804 (or 1803) and look whether it is still ok there and retry the upgrade. The audio loss I got when simply playing back FLAC file via MusicBee using RME ASIO driver, usually no issue.
Which brings me to another point ? I would propose that you buy a 2nd SSD/DISK to perform a Win7 parallel installation and use Win7 for recording purposes, shall your mainboard still has Win7 drivers.
Otherwise I can still recommend my mainboard and CPU (use the v4 it's better in terms of producing less heat), because then you can still run Win7 and its proven. The bad thing today is, that with newer CPUs Intel tells, no Windows 7 support anymore and this draconic decision I personally regard as very bad for customers esp. for us in the recording area, as I see still a certain demand being able to deploy on Win7 simply to have a peace in mind as the deployment cycles of Win10 seem to be too tough even for Microsoft, you can see the decreasing quality definitively here:
https://www.heise.de/newsticker/meldung … 82651.html
To sum up, possible solutions
- BIOS WIN tuning
- Win7 parallel installation and comparing with Win10 on same HW
- Trying to make use out of LatencyMon for the measurements (for Win7 I recommend to take the old version 4.02 to ensure, that you get really compareable values, as I am not 100% sure, what changes they made in the tool for Win8/10 compatibility), you can get the older version from my dropbox: https://www.dropbox.com/s/imcbu6lcac5vg … 2.exe?dl=1
MD5 checksum here: https://www.dropbox.com/s/9h6uoqgcaqqvd … e.md5?dl=1
X10SRi-F, E5-1650v4, Win10 Pro 2004, Cubase 10.5.20, UFX+, XTC, ADI-2 Pro FS R BE, ARC USB