Latency checker is designed as a driver response test and not a load test. You run it on a bare desktop, not with applications running to get a baseline.ataraxia89 wrote: Edit: Just done a DPC Latency check whilst running Cubase (with my biggest project open), Adobe Premiere Pro CC (the hungriest application I have, whilst loading 37 4K videos into memory), a media server and a full system scan with Norton antivirus and the highest reading I got was 1317ms, it averages around 200-300ms on normal running
If it works fine at desktop, but shit goes south when you open an application, you take it up with the application developer. Well, you delve into the application and disable anything that calls back, or is likely to hog the system resources... and then when that fails, you take it up with developer.
Either way, you don't thrash it like that!
T.B.H I'd expect any anti-virus that does in-depth heuristic scanning like Norton to error the result which is why I tend to no advise them on an audio box. If that's the only thing that's tipping the rig over the read, you can be pretty sure it's working as intended.
. As long as you know there aren't spikes, caused by misbehaving drivers etc, you will most probably never have to deal with it in any manner. To get an ultra low reading something like the 20-30 on the workstation I posted a screenshot from, you either need to be lucky or the whole system needs to be planned component by component for realtime operation, referencing other known successful builds and so on, like with that machine. But seriously, as long as it's predictably staying at any reasonable level and not spiking intermittently (the most common actually noticeable problem), and your audio interface has high quality drivers, you're sorted for low latency use.
... The truth is, if you need good realtime performance, it's the system as a whole that counts -- and the interface with its drivers is a very important part of that. Otherwise one is literally paying for resources they can't use (a fast high-end CPU and a bottlenecking interface is a common combination).
