Why do you think the developers still haven’t implemented automatic plugin delay compensation within Direct Offline Processing (DOP) in Nuendo?
At first glance, this doesn’t seem particularly difficult, since the plugin latency is already known to the application and is displayed in the MixConsole as channel delay compensation. For example, SuperTone Clear introduces about 36 ms of latency in real-time operation. If the same signal is processed through an insert on one track and through DOP on another, the result ends up time-shifted, leading to phase issues. To make them match, I have to manually offset the DOP-processed event by the amount of latency reported by the mixer.
I see the same behavior with other plugins as well, such as AIR and various other processors that introduce noticeable latency.
I’m curious what prevents this from being handled automatically. Are there architectural limitations within Direct Offline Processing, specific aspects of offline rendering, or other technical reasons behind it? Or is it simply a matter of development priorities?
It seems strange that when the host already knows the exact plugin latency, users still have to manually correct the result, especially in workflows where phase accuracy and sample-accurate timing between tracks are important.