automation doesn't follow fade dragging

[kosmokrator]

@Avid:
It's really upsetting that this bug is still around after what - more than 2 years now?

Especially with Atmos mixing this is just such a showstopper.

What's the reason this doesn't make the list of bugs being addressed?

[nednednerb]

That doesn't sound like a bug..... What does an automation of an insert or send level have to do with clip edges? Sure, maybe a feature request.. "IF there is one or more breakpoint on a fade edge, MOVE breakpoint(s) with any edits on edges."

Otherwise, I could move fade edges and move breakpoints all day long and I never thought it was a bug. It seems natural to not accidentally move clips and then find breakpoints all over the wrong place. That's what I mean by "feature request" and by saying I don't experience this as a bug. If it was an option to turn on and off at whim, and THEN it wasn't working, I would call that a bug.

For now, I want my breakpoints to stay where I put them, so thanks, Avid! (Sincerely).

[marsian]

ned,

you may have noted that it IS a feature already.
But it acts buggy when "automation follows edit" is switched on. As kosmokrator mentioned.
It's a real bummer when mixing and writing automation in preview.


Best
Maik

[smurfyou]

Yes ned I think you misunderstand. It is an existing feature that stopped working correctly ages ago. Is completely necessary in post.

[nednednerb]

What happens to breakpoints behind the fade you drag passed? What happens to them, do they auto delete? Does automation spike back up after the breakpoint at fade end gets moved "with edit"?

For me, if I copy and paste a clip, automation moves just fine. The "edge case" of moving the edges seems to me like one of a programming choice, and one where the behaviour as described makes me question as above.

AT LEAST, this seems to be an adaptation or interpretation of Automation Follows Edit, where there could be a potential issue like the breakpoint now after the clip making automation unintended, after the breakpoint on the fade gets moved with the fade drag.

If you don't understand this possibility, maybe the bug isn't well expressed and I don't get it. Seems to do what I would expect now. Maybe there was a way or could be a way to deal with that, maybe they decided it wasn't the best idea sometimes, but didn't go back on the feature? And that's why I express that they chose one option, you want the other as default. I can totally accept both as desirable. There are always issues, and I'd rather have both than call what's now a bug, because I'd have to call both buggy from the other intended functionality.

[kosmokrator]

Originally Posted by nednednerb

I don't get it..

This sums it up.
It’s a well-documented bug that is a complete PITA in Post Production mixing.
If you don’t understand the issue, that’s fine, it means you don’t have a problem with it.
There are other threads on the DUC explaining it. Go there to see what we’re talking about.
But please stop diluting my thread.
It was a question to Avid.

Thanks.