# Latency reporting in Logic Pro X

**URL:** <https://forum.juce.com/t/latency-reporting-in-logic-pro-x/56809>\
**Category:** Audio Plugins\
**Created:** [June 27, 2023, 7:41am UTC](https://forum.juce.com/t/latency-reporting-in-logic-pro-x/56809 "2023-06-27T07:41:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aapo](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/aapo/32/12195_2.png) [@Aapo](https://forum.juce.com/u/Aapo)\
**Post date:** [June 27, 2023, 7:41am UTC](https://forum.juce.com/t/latency-reporting-in-logic-pro-x/56809/1 "2023-06-27T07:41:27Z")

</div>

Hi everyone,

I’m having a weird issue where Logic Pro X doesn’t update latency compensation for a plugin during playback. For example, if I enable linear-phase filters while listening to the track I’m working on, the audio gets delayed due to the latency not being compensated by the DAW. As soon as I pause the playback and hit play again, the latency gets properly compensated. I tried set the latency async, as described [here](https://forum.juce.com/t/how-to-report-plugin-latency/55869), but that didn’t change the behaviour. I haven’t encoutered this issue in any other DAW yet, so I’d be very curious to know what Logic is doing differently.

Cheers,  
Aapo

---

<div class="post-metadata">

**Author:** ![pflugshaupt](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/pflugshaupt/32/13206_2.png) [@pflugshaupt](https://forum.juce.com/u/pflugshaupt)\
**Post date:** [June 27, 2023, 11:05am UTC](https://forum.juce.com/t/latency-reporting-in-logic-pro-x/56809/2 "2023-06-27T11:05:01Z")

</div>

To my best knowledge, this is a limitation of Logic Pro X. It needs to stop playback to adjust for latency changes. Which is understandable. Only few hosts can do it and often it comes at the code of noise when adjusting.  
If you just need small adjustments you can just report the max latency to the host and then do minor changes yourself with a delay.

---

<div class="post-metadata">

**Author:** ![baKno](https://avatars.discourse-cdn.com/v4/letter/b/ac91a4/32.png) [@baKno](https://forum.juce.com/u/baKno)\
**Post date:** [June 27, 2023, 11:17am UTC](https://forum.juce.com/t/latency-reporting-in-logic-pro-x/56809/3 "2023-06-27T11:17:28Z")

</div>

Hello Aapo

In my experience, Logic does not call “prepareToPlay” when you start Logic and play immediately. So it affect many other initializations. What I do is call these initializations on the first timerCallback.

Andres

---

<div class="post-metadata">

**Author:** ![Aapo](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/aapo/32/12195_2.png) [@Aapo](https://forum.juce.com/u/Aapo)\
**Post date:** [June 29, 2023, 4:12am UTC](https://forum.juce.com/t/latency-reporting-in-logic-pro-x/56809/4 "2023-06-29T04:12:32Z")

</div>

This indeed appears to be the case. However, I also had an issue where latency didn’t get reported on startup. To fix this, I basically just had to do the reporting via the message thread. For some reason, Logic doesn’t use prepareToPlay as other DAWs do, as @baKno mentioned. I used an APVTS listener for the latency reporting, but doing it inside a timerCallback should work just as well.