Quote:
Originally Posted by ivansc
good news but for the long term a newer interface would make your life a lot easier.
And did you ever get round to running that latency checker I suggested? What sort of results did you get?
If it finds anything and it can be fixed that will help your performance in general, not just with reaper and kontakt. Good luck!
|
All looks fine to me and my limited knowledge. Currently using the WASAPI drivers as suggested and seem to be achieving reasonably low latency and good performace. What is the best way you have found to measure only Reaper round-trip latency?
__________________________________________________ __________________________________________________ _____
CONCLUSION
__________________________________________________ __________________________________________________ _____
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:03:53 (h:mm:ss) on all processors.
__________________________________________________ __________________________________________________ _____
MEASURED INTERRUPT TO USER PROCESS LATENCIES
__________________________________________________ __________________________________________________ _____
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 205.220411
Average measured interrupt to process latency (µs): 2.973935
Highest measured interrupt to DPC latency (µs): 182.985696
Average measured interrupt to DPC latency (µs): 1.019831
__________________________________________________ __________________________________________________ _____
REPORTED ISRs
__________________________________________________ __________________________________________________ _____
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 160.639085
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.106425
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.128142
ISR count (execution time <250 µs): 211916
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0
__________________________________________________ __________________________________________________ _____
REPORTED DPCs
__________________________________________________ __________________________________________________ _____
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 321.549296
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 388.13 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0.121396
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.252649
DPC count (execution time <250 µs): 1119001
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 4
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0
__________________________________________________ __________________________________________________ _____
REPORTED HARD PAGEFAULTS
__________________________________________________ __________________________________________________ _____
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.
Process with highest pagefault count: none
Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0