As shown here, when bouncing, the audio is actually changed - anyone else run in to this?
EDIT: It’s only the waveform image cache updating, the audio is unaffected.
Yes, I’ve run into this multiple times, since N13 at least, perhaps earlier.
It used to happen mainly with RX Connect and Acon plugins in DOP. But there were others which I don’t remember.
I’ve since changed a lot of my workflow and haven’t been using “Make DOP Permanent” or bouncing edits lately, so I haven’t run into it in a long time.
Just tested a file in a session I’m working on, in N14, and the audio didn’t move with either RX Modules, Acon plugins nor Supertone Clear.
What Nuendo Version are you on?
This does happen, indeed. But usually it is just a visual shift that happens in certain zoom levels only, and doesn’t correspond to the actual waveform. Many times I bump into this and am forced to zoom in and undo to make sure it is just this visual artifact.
Yes, you can’t work like this.
It would be great if more people, specially those on N15, could try to reproduce it and post their results.
The bane of my editing existence, I have been doing the exact same thing haha!
Zooming in to make sure it isn’t now out of phase, but it gets old really quick when you have a large project.
I just recently discovered a really problematic issue as well, which was really a downer.
Some of my master tracks had unexplained DC Offset in them, and after a few hours of searching and troubleshooting I discovered that if you edit the audio, it causes DC Offset - which is crazy.
Editing as in, just cutting, or moving the start or end of a clip - no plugins.
I have another post in the nuendo forums called “serious bug: cutting a clip/event causes DC Offset” - I have a video in that post showing it as well.
I really hope these issues can be fixed, cause I absolutely love Nuendo otherwise, it feels like home to me and I would hate to switch to another DAW.
Hmm, I just tested this and could reproduce this with stereo clips.
Even just adjusting the event size and bouncing produces different amounts of DC offset as per the “Statistics” panel.
I couldn’t reproduce the issue on mono clips, however.
I’m “glad” it’s not just me, at least it seems like something the developers can investigate - not just my setup.
Here is a side-by-side comparison of what happens to peaks when you bounce them within the project.
Some of them look like they become vertically flipped almost, super weird.
The audio slips to one side a fraction, and the peaks get warped.
Note: I of course had no plugins, a fresh session, and hadn’t touched the audio - I only imported it, cut a piece out and bounced it.
Aren’t the peaks moving due to that visual artifact we talked about? Flipping through both images it seems to me the waveform was just adapting itself to the pixels in the new position.
Can you try it with more zoom, please? zoom enough that we can see the waveform clearly, without the solid color.
I zoomed to the maximum on those that the scroll-in would allow.
But you know what, it seems to be nulling consistently now, even though the waveform display changes, so it seems to be just a visual image cache updating thing - the only time it doesn’t null is if:
- The clip gain of the original signal is altered
- The track is duplicated
- Part of that duplicated clip is bounced
- Phase flipped and measured against the original, which still has the clip gain applied
(the clips are all the same volume of course, because they’ve only been copied and bounced)
That will produce a difference, but as I mentioned it’s still down at -150dB or more, so I suppose that’s a non-issue.
I’ll mark this one as solved by you!
However: I would really like to get peoples attention regarding the DC Offset issue, because that is actually a problem.