I’m seriously tired of dealing with this issue version after version.
This has been happening for several Nuendo generations, possibly since Nuendo 13, and it is still present in Nuendo 15.
Screenshot 1 shows just one scene from a feature film. Only three tracks are selected, with a relatively small number of dialogue/boom events. I press F7 → Direct Offline Processing.
Screenshot 3 shows what happens next: Nuendo suddenly starts processing more than 4,000 events. In this particular case it is 4,050 events.
These events were never selected. As far as I can tell, Nuendo is going through events elsewhere in the project that have some DOP history associated with them.
Screenshot 2 shows what I see when I click one of the selected events: a huge amount of RX 11 De-hum processing/history appears in DOP.
If I remove De-hum, close the project without saving, reopen it, and select events where De-hum was never used, everything can initially work correctly.
For example, I select 39 events and Nuendo processes exactly 39 events.
Then I apply another offline plugin, for example an Accentize plugin, to the same selection.
Nuendo may suddenly start processing 800+ events again, even though the selection has not changed.
The strange part is that after all this recalculation, the new processing is still actually applied only to the events I selected.
So the question is simple:
Why is DOP recalculating hundreds or thousands of unrelated, unselected events?
In a real film post-production project with thousands of events, this is not a minor inconvenience. A simple DOP operation can turn into an extremely long wait. With 4,000+ events it can become completely impractical.
I do not believe this is only an RX De-hum issue. De-hum is just one clear example where I can reproduce it. I have seen similar DOP behaviour with other processing as well.
And this is not the only long-standing plugin/DOP-related issue.
There is also the problem with Supertone Clear, where processing can produce phase/timing-related issues. Clear has even changed ownership since then, but from the Nuendo side this still has not been properly addressed.
Even if the root cause is plugin latency or incorrect latency reporting by a third-party plugin, Nuendo should at least be able to detect the resulting offset and compensate for it correctly. Instead, users are left dealing with the consequences manually.
So from my perspective this is becoming a pattern: serious problems around offline processing and plugin handling remain unresolved across multiple Nuendo versions.
This is especially frustrating in professional film post-production, where timing accuracy and predictable offline processing are absolutely critical.
Please investigate this as a core Direct Offline Processing problem, not just as a plugin-specific issue.
After several Nuendo versions, this really needs to be fixed.
2 Likes