Since the first round trip should be (and is approximately for this interface) latency compensated, the second round trip is necessary to measure the output to input latency. Turning off low latency monitoring is necessary to enable output for that second round trip.
Quote:
Originally Posted by mesaone
Why are you running cascaded loopbacks to measure latency (output 1 to input 1, track receiving on input 1 feeding output 2, recorded back in through input 2 onto a third track)?
That makes no sense. That's double-round-trip, and there's no indication of why you disabled Low Latency Monitoring - which would certainly affect the return time, doubly so since you're returning twice in series.
I really don't understand what you're testing for, and how this methodology applies. From what I see, you're getting good results on the single loopback, and you're only encountering a sizeable latency when looping back twice.
|