Issue: Duplicating audio track, Trim enabled, automation error

Nuendo
,
1

I have seen this several times and never could figure out what it could be, but finally ‘got it’.

Repro:

  1. Create audio track in empty project
  2. Set track to “Touch” automation and write some level changes.
  3. Duplicate the track.
  4. Select the first / source track again.
  5. Enable “Trim” and duplicate the track a second time.
    (I have tracks set to follow global automation settings and set trim there)

Outcome:

image
image657×1158 48.5 KB

As you can see the track we got when “Trim” was enabled has a flat line and no automation, whereas the other track is fine. In addition to that the track with the error seems to point us in the direction of the problem - the fader is located at the position we find it when trim is enabled. Compare the mixer section above to what it looks like when I re-enable trim:

image
image531×578 18.6 KB

Next:

6: On the track with the error write automation.

Turning trim off you can see the result below;

image
image1026×433 26.1 KB

The ‘double’ line looks just like “Trim” is enabled, but it isn’t. The thicker line is the one I wrote without “Trim” enabled and after I got the lighter line. The lighter line is what the fader then plays back, with a significant offset.

Deleting automation on that track using the automation panel command does indeed delete the automation and allows me to reset the fader, but writing automation again just results in the same thing, an offset and incorrect playback.

image
image801×221 11.7 KB

Would love it if someone could confirm this bug.

System specs in my sig. I believe it was the same in n12.

2

Could anybody please just try to replicate this? Just to make sure it isn’t just me.

3

I’m on N12 so unfortunately can only do it for that version, if that is useful. I can do it tomorrow, I have some time then.

4

I’d appreciate it. As far as I recall the problem also existed there.

5

Hi,

I can reproduce and confirm this behaviour with Nuendo 12.0.70 on my Win10 machine.

Cheers,
Dirx

1 Like
6

Thank you. Appreciated.

Hopefully the SB team can take a look at this. It’s a bit of a nasty bug if you run into it.

7

Confirmed I could also replicate this in Nuendo 12.0.60 on Mac, OS Ventura 13.6.3

1 Like
8

Hi @MattiasNYC I can confirm this in N13.0.20 and N12.0.70 on Mac Monterey.
Thank you for nailing this bug, I ran into this multiple times but couldn’t figure out what it was. Hopefully Steinberg can dive into this.

Best, Alan

1 Like
9

Thanks Exeter and Alan!
Appreciated.

2 Likes
10

I’ve had this behavior for ages on the mac, with much confusion and frustration. I never knew what was causing it, just that it would happen. I can’t seem to find a work-around.

Here’s a post I made about it back in 2021:

Thank you!

11

This might be because you have WRITE enabled on the tracks before duplicating. Might not be indended behavior though but worth a try to duplicate tracks without WRITE enabled to see if that helps

12

That’s not it. Read the thread.

13

not sure why you would assume I didn’t. I was offering a suggestion and said “might”. Glad you repo’d it.

14

I assumed you didn’t because I thought it was clear in my posts that automation write on/off isn’t the problem.

15

yeah no worries, I think the pictures you shared showing the “write” on made me think of it. My thought process there was maybe on initially duplicating the track if write was enabled it maybe would have forced something into the xml of the track data that might be causing some weird issue. Nasty bug though, glad you figured it out.

1 Like
16

Did anyone figured out a workaround for this? Version N13.0.51 still going strong with this issue.

Best, Alan

1 Like