Another autocrossfade criticism :
And when recording with punch outs it is even worst :
The autocrossfade at the end of the record is in fact a fade out followed by a fade in. But probably because autocrossfade does not show up graphically, nobody did detect it even when zooming on the crossfaded events.
But audio is affected. And the bad thing is that it is a “silent” audio quality destruction. You don’t see it graphically, and eventually you do not hear it because there still is a fade out followed by a fade in that will remove any click.
Punch ins autocrossfades are not affected. They are right (thanks to the prerecord buffer).
I did detect this bug, did describe it, and did explain from where it does come from :
And here :
I did not test with the latest Nuendo version, but i did not remember a note about a correction in the changelogs. I discovered it inside Nuendo 7.1.40 but i suspect it is here since a long time.
But nobody seems to care, and take it as a serious bug. Except probably PT guys that should laugh when they read this. Protools does not have this bug because it does have a record post buffer, so that the autocrossfade is correctly managed.
I say it again, such a bug that affect audio quality should be addressed as a top priority thing, regardless the complexity at the code level.