Phase misalignment after render when using Supertone Clean

Hello,
I ran into a phase alignment problem when rendering dialog stems.

Inside a dialog stem I use several groups. Some groups have the Supertone Clean plugin which adds latency, while other groups have no processing. During playback inside Nuendo everything sounds perfectly phase aligned and delay compensation seems to work correctly.

However after rendering the groups become phase misaligned in the rendered file.

After testing I noticed that this happens when the Supertone Clean plugin is used. If I remove the plugin the problem disappears.

This behaviour appears both on macOS and Windows. During playback everything sounds correctly aligned, but after rendering the groups become phase misaligned.

So playback inside Nuendo sounds correct, but the rendered result becomes out of phase when the Supertone Clean plugin is present.

It is not clear whether this is a Nuendo delay compensation issue during rendering or a problem with the plugin.

Nuendo version 14.0.41 on both systems.
Supertone Clean 1.1.1
System MacBook M4 Pro.

1 Like

Have you tried doing a real time render?

Clear causes little time shift when I use it with DOP. I did report this to the Supertone crew and they are working on a update that fix this problem.

1 Like

No, I haven’t tried realtime render. To be honest I almost never use it. For the last 10 years I’ve been doing only offline renders. The last time I regularly used realtime bounce was many years ago when working in Pro Tools.

Yes, I see the same behaviour with DOP. I have also contacted Supertone support about this.

What makes this issue particularly problematic is that it cannot be detected during the mixing process.

During playback everything sounds perfectly phase aligned and delay compensation appears to work correctly. There is no audible phase shift while mixing.

However after mixdown the rendered result becomes phase misaligned between groups.

So the problem only appears after rendering, which makes it very difficult to detect during the actual mix. That makes this a potentially dangerous issue in a post-production workflow.

What I’m saying is this is most likely a plug-in specific issue. To help you get working, try a real time render.

It’s up to you of course.

Cheers.

Yes, I tried realtime export and it does fix the problem. A nice band-aid fix :slight_smile:

1 Like

You might want to mark Phil’s post as solution - this way others can see it right on top of the thread :wink:

1 Like