# How To Determine DAWs Output Latency **URL:** \ **Category:** Audio Plugins\ **Created:** [June 22, 2020, 12:32am UTC](https://forum.juce.com/t/how-to-determine-daws-output-latency/40252 "2020-06-22T00:32:44Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![daniel](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/daniel/32/790_2.png) [@daniel](https://forum.juce.com/u/daniel)\ **Post date:** [June 22, 2020, 8:48am UTC](https://forum.juce.com/t/how-to-determine-daws-output-latency/40252/2 "2020-06-22T08:48:56Z")
There are quite a few threads, I’ll link them for reference (some you found already): > [@Output latency](https://forum.juce.com/t/output-latency/10329/4): > > Ah, sorry, I mis-read the OP’s question. Getting the host’s latency is really nasty, and even if there’s something to do it in VST, it’s unlikely to be supported in all hosts, or other plugin formats. I know that tracktion won’t be able to provide that information (and to do so would be surprisingly difficult/impossible depending on how the plugin is being routed). > [@Problem getting the real output latency](https://forum.juce.com/t/problem-getting-the-real-output-latency/7136/2): > > DirectSound is completely useless when it comes to reporting the latency. If you use WASAPI or ASIO, (or anything else, really), then the latency figure will be accurate, but with DirectSound, no chance! I think it’s a fair ask, but I don’t know if hosts will ever report it properly. If you consider e.g. Reaper or FinalCut, which pre-render files, there is no synchronicity at all between the processing time and the playback time. Thanks to latency compensation, a gesture in the editor would have to be transfered in the past to render what you hear accordingly. So doing the gestures is an iterative task by nature, and the result will always fall behind. The other remark I wanted to bring, the typical perceived update rate is 24-25 per second, lets be generous and use 30 Hz. In which case the jitter to the visual frame is 33 ms. In this time in a normal 44.1kHz signal produced 1470 samples, that’s in conservative setups 3 buffers, in more performant ones even more. I understand, if your plugin is just before a crazy one second latency inducing plugin, it would be nice to know, but I think precise numbers is not what we should look for. In that respect I think the device latency is neglible, but the latency compensation would be a good ask. Maybe someone knows, which plugin formats would give that information, and if they can be added to the JUCE API? --- _[View the full topic](https://forum.juce.com/t/how-to-determine-daws-output-latency/40252)._