[bug or feature] auto-ripple affects also unaffected events

Foo-Bar wrote on 3/2/2023, 6:51 AM

Is this behavior the correct way of implementing / executing auto-ripple?

https://i.ibb.co/cFH0YQ8/ripple.gif

In my opinion it's not, but maybe I am holding it wrong...

Let me explain

In the attached GIF (above) I did mark a point in the audio and created a volume-envelope around it.

When I resize the event AFTER both this marker and envelope, the auto-ripple moves them; making the envelope mute (soften / lower) the wrong part of the audio and the marker does point to a wrong timecode now.

The setting is "adjust all affected tracks / events / etc..." but in my opinion the elements BEFORE the resized event are (or should) not be affected at all?

BTW : Vegas 20

 

Comments

DMT3 wrote on 3/2/2023, 8:36 AM

It may not be what you want, but according to the HELP file, it is the intended behaviour.

Foo-Bar wrote on 3/2/2023, 9:34 AM

It may not be what you want, but according to the HELP file, it is the intended behaviour.

Yes, but it states "affected".

And every event chronological placed before an edit, is not affected by the edit.

Graphical;

- A - B - C - D - E -

Let's say I cut out "C", this will become;

- A - B - | - D - E -

Timeline-wise only D and E are affected;

- A - B - | - D - E -

So in my opinion A and B should not be altered, when chancing something between B and D.

Why would an envelope or marker placed at B be affected when you cut out C?

That doesn't make sense, from a timeline-point-of-view...

 

DMT3 wrote on 3/2/2023, 9:44 AM

I would make a feature request. Notice it says "ripples events, keyframes, and envelopes on tracks where you perform the edit". So like I said, it is working as designed.

Foo-Bar wrote on 3/2/2023, 10:22 AM

Well, it explicitly says affected.

And a marker or event chronically placed before an edit, is never affected.

I mean, you have a timeline / event like this;

  • __mumble__mumble__SHOUT__mumble__mumble__

Than you do two things;

  1. Soften the shout by an envelope
  2. Cut of the last mumble (or is it "mumbling"?)
  • __mumble__mumble__shout__mumble__

The envelope that changes the SHOUT to shout should not be affected by cutting the last __mumble__ but it is in my example (first post).

vkmast wrote on 3/2/2023, 10:26 AM

"Affected tracks" as @DMT3 pointed out.

DMT3 wrote on 3/2/2023, 10:26 AM

I was attempting to answer your inquiry as to whether this is a bug or a feature. The documentation provided by the developer indicates this works as expected. So it is not a bug. "on tracks where you performed the edit". So again, if you would like it to work differently a "feature request" would be warranted.

bvideo wrote on 3/2/2023, 12:35 PM

That help says " the contents of the timeline are rippled after the edit according to the option (etc.)". So it doesn't sound like the OP scenario is working according the the help.

Foo-Bar wrote on 3/2/2023, 12:38 PM

That help says " the contents of the timeline are rippled after the edit according to the option (etc.)". So it doesn't sound like the OP scenario is working according the the help.

Like I said : I am holding it wrong.

But in my opinion an envelope placed before a cut is never affected, thus should not move at all.

bvideo wrote on 3/2/2023, 2:25 PM

Maybe even though it is the end of the event that is being edited, the whole event is judged to be the beginning of the edit, and the ripple proceeds from the front of the event. That is an inconvenient corner case that would need to be better tuned.

Foo-Bar wrote on 3/2/2023, 2:54 PM

Maybe even though it is the end of the event that is being edited, the whole event is judged to be the beginning of the edit, and the ripple proceeds from the front of the event. That is an inconvenient corner case that would need to be better tuned.

Yeah, something like a toggle;

  1. Affect ALL events
  2. Affect only when the event is BEFORE* the edit
  3. Affect only events AFTER* the edit

*) I mean "before" and "after" solely based on there placement on the timeline. Not before, or after doing some editing

  • __A_B_x_C_D__

So "x" is the "edit", A / B are placed before, C / D are after and A / B / C / D are both.

You can select whether A B (before) are affected when editing x, C D (after) that same edit or simple the complete range (A B C D).

It looks difficult, but this way auto-ripple comes more predictable for many edits.

9 out of 10 I (audio-)edit "from left in the timeline to the right", so when I do an edit, almost never I want the events "before" (on the left) of that edit to be affected.