# How do DAW's report input and output latency?

**URL:** <https://forum.juce.com/t/how-do-daws-report-input-and-output-latency/33868>\
**Category:** Development\
**Created:** [June 12, 2019, 5:47pm UTC](https://forum.juce.com/t/how-do-daws-report-input-and-output-latency/33868 "2019-06-12T17:47:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DavidCNAntonia](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/davidcnantonia/32/3293_2.png) [@DavidCNAntonia](https://forum.juce.com/u/DavidCNAntonia)\
**Post date:** [June 12, 2019, 5:47pm UTC](https://forum.juce.com/t/how-do-daws-report-input-and-output-latency/33868/1 "2019-06-12T17:47:57Z")

</div>

I’ve been wondering, how do DAW’s report input and output latency without sending audio out for a round trip test? Is it just an arbitrary estimate? I’m talking about the values given in a device setup screen (sample rate and block size settings).

Any pointers on how to do this (if they aren’t arbitrary values that is) would be very much appreciated.

---

<div class="post-metadata">

**Author:** ![xenakios](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xenakios/32/4047_2.png) [@xenakios](https://forum.juce.com/u/xenakios)\
**Post date:** [June 12, 2019, 5:50pm UTC](https://forum.juce.com/t/how-do-daws-report-input-and-output-latency/33868/2 "2019-06-12T17:50:34Z")

</div>

Some driver systems have a way to query that. The reported values may of course be completely wrong. The DAW should additionally allow the user to manually adjust the figures.

Juce’s AudioIODevice provides the methods  
getInputLatencyInSamples and getOutputLatencyInSamples.