#MACRIUM REFLECT WINDOWS 10 1903 DRIVERS#

#MACRIUM REFLECT WINDOWS 10 1903 DRIVERS#

Device drivers seem to affect the measured latency of NTOSKRNL, on my system the NVidia driver seems to have the biggest impact, though. There are several different scenarios at play.ġ. Well, things are a bit more complicated and I am not convinced that the measured latencies are 'real'. I suspect some of it is connected to usb3 but it certainly is not the whole solution. Having said that, I'd rather have a super stable low latency version where I didn't have to run this app first and didn't get any spikes every so many seconds.Ĭlearly there is a windows problem somewhere. just google it to download and try for yourself. Projects I couldn't even play on 28 ms with asio guard now plays fine on 2ms with this TimerResolution tool. Every 15-30 seconds I would see a spike to 499 us but I can run Cubase with 2ms latency no problem with my RME pci on an pci-x to pci adapter. BUT my latency did fall to numbers between 15 and 24 us in latency. then I would run Latency Checker again and it would now blast out 499 all the time. I found an old tool called 'TimerResolution.exe' - basically I run that first of all, press the maximum button. When I run Latency Checker it blasts out 999 us all the time and my latency was around 1020 with spike up to 1350. The AMD card is better for latency then Nvidia like by 40 us according to LatencyMon. I have a Ryzen 2700x, 32 gb ram, Asus ROG Strix x470 with mvme m2 disk and tried both Nvidia and AMD graphics cards. my system blasts 1000 us and once in a while it would jump to 1350 us latency.

I have the same problems described by all you guys.

Macrium reflect windows 10 1903