# AudioProcessorGraph Latency paths **URL:** \ **Category:** General JUCE discussion\ **Created:** [August 11, 2023, 1:15pm UTC](https://forum.juce.com/t/audioprocessorgraph-latency-paths/57403 "2023-08-11T13:15:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![railjonrogut](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/railjonrogut/32/505_2.png) [@railjonrogut](https://forum.juce.com/u/railjonrogut)\ **Post date:** [August 11, 2023, 4:28pm UTC](https://forum.juce.com/t/audioprocessorgraph-latency-paths/57403/2 "2023-08-11T16:28:11Z")
The host is totally responsible for taking care of the Delay Compensation. Each plugin should report its latency to the host. Some plugins like FabFilter have differing latency values depending on the preset loaded or some of the options. See this thread: > [@AudioProcessorGraph PDC and changing latency](https://forum.juce.com/t/audioprocessorgraph-pdc-and-changing-latency/18121/1): > > I have an AudioProcessorGraph which includes some 3rd party plug-ins… when I add the connections to the plug-in and the graph is rendered it calculates the PDC okay… the problem is that some plug-ins will change their latency when you change a preset (iZotope Ozone for example) – and the PDC isn’t recalculated for the AudioProcessorGraph. Is there any way to have the graph re-calcuculate it’s delay (DelayChannelOp) when the latency of one of the plug-ins in the graph changes? Thanks, Rail The latest version of the AudioProcessorGraph has a rebuild() method to force a recalculation. Rail --- _[View the full topic](https://forum.juce.com/t/audioprocessorgraph-latency-paths/57403)._