Cakewalk reported latency different than what it should be?

[tlaskows]

I have this as reported by Cakewalk. I am not complaining as that's pretty low. But why is the round trip so long when the buffer size is set at 64 samples. Any Sonar users out there?

Thanks,

-Tom

[garyb]

latency isn't set in Sonar with ASIO Scope....

[tlaskows]

I understand. I guess I should be just happy because that's still pretty low. I can't tell the difference between real time.

Thanks!

-Tom

[garyb]

latency in Sonar is set via ULLI, in Scope when using ASIO.
what is your ULLI setting? i'll bet it matches the reported latency...

[tlaskows]

Yes, I know. It's set to the lowest setting...

-Tom

[jksuperstar]

All A/D converters have some delay, about 1-1.5ms (conversion is more like a pipeline with an FFT filter, than it is an instant sample & hold). Notice those calculations say "includes buffer and hardware latencies".

I don't have any programs that report this, so I don't know if it is truly reported by SCOPE to Sonar as part of the ASIO communication (just like it says what the software buffer.latency is), or if Sonar makes this up.

Either way, it is truer to reality *for a signal coming thru ADC and DAC*, but not true for signals generated within scope. I don't think that Sonar has any reason to *use* a number like this, other than to guide the sound engineer in situations like monitor while recording, and adjusting track latencies if you want them to be phase coherent with an external signal.

[tlaskows]

Ahh, ok.

Thanks for the explanation JK

-Tom

[jksuperstar]

I found this tool that measures these things. Could be good to know what the round trip times are in/out of scope IOs, through scope, etc.

https://centrance.com/downloads/ltu/