Comments

j-v wrote on 7/11/2020, 2:57 AM

Did you made the right choice for what you want?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.77 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Marco. wrote on 7/11/2020, 3:24 AM

There are several odd things happening with the ripple mode. This unexpected movement of markers in front of an event is one of it. Vegas Pro sticks this marker to the event internally which may be technically correct but I doubt it meets the user's logic.

JPK wrote on 7/11/2020, 4:27 AM

Did you made the right choice for what you want?

Yep, the marker should not be jumping forward in time when the start time of the event does not change. No matter which Auto Ripple mode you are in.

j-v wrote on 7/11/2020, 5:13 AM

Strange, this how it goes with me trying to do the same as you showed


What build of 17 are you using?

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.77 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

vkmast wrote on 7/11/2020, 5:17 AM

@j-v same here as for you in this case (release/current build 143 of VMS 17 P).

JPK wrote on 7/11/2020, 5:18 AM

Strange, this how it goes with me trying to do the same as you showed


What build of 17 are you using?

 

I'm using All Tracks, Markers and Regions mode.

vkmast wrote on 7/11/2020, 5:23 AM

Did you try @j-v's suggestion, see his screenshot you quoted above.

JPK wrote on 7/11/2020, 5:27 AM

Did you try @j-v's suggestion, see his screenshot you quoted above.

No, because it's not relevant to my situation. I simplified the example video for demonstration purposes.

In reality, I have many more events and markers later in the timeline. I need all of those to move with the edits.

 

vkmast wrote on 7/11/2020, 6:33 AM

Have you tried Post-Edit Ripple instead of Auto Ripple?

JPK wrote on 7/11/2020, 6:41 AM

Have you tried Post-Edit Ripple instead of Auto Ripple?

It has the same bug. :)

Marco. wrote on 7/11/2020, 6:45 AM

I completely agree with JPK. It's the same odd misbehaviour as when deleting the first event in the timeline (from timecode zero up), rippling also deletes the events of other tracks at same position instead of preventing any event of getting moved more than to the timeline's zero position.

It's the same with post-edit rippling. The logic isn't made for users.

vkmast wrote on 7/11/2020, 6:57 AM

https://www.vegascreativesoftware.info/us/forum/unexpected-rippling-behaviour--120350/

JPK wrote on 7/11/2020, 9:32 PM

https://www.vegascreativesoftware.info/us/forum/unexpected-rippling-behaviour--120350/

Unfortunately, the legacy ripple logic has the same bug.

JPK wrote on 7/11/2020, 10:07 PM

I completely agree with JPK. It's the same odd misbehaviour as when deleting the first event in the timeline (from timecode zero up), rippling also deletes the events of other tracks at same position instead of preventing any event of getting moved more than to the timeline's zero position.

It's the same with post-edit rippling. The logic isn't made for users.

Yes, I did notice other ripple edit oddities but was neck deep in project delivery, so didn’t have time to investigate further.

I believe one of them was the deleting events rather than preventing them moving beyond the zero position you are describing. 

I had no idea a huge number of grouped events had disappeared from the start of my project after inserting a new event. Was not until after 10 to 20 edits later that I discovered what had happened. 

Some frantic undoing got everything back, but it's a big jolt when something like that happens.

john_dennis wrote on 7/11/2020, 11:06 PM

@JPK

I went back to Vegas Pro 9.0e and the behavior is the same as your example no matter the setting of the new event delete ripple logic switch. I could go back to version 4 and/or 8 but it appears that Auto Ripple has worked that way for a long time.

Anecdotal Detritus

Most of the time in my editing experience when I've hit Control + Z it's been from having Auto Ripple switched on. I normally work with it turned off and only switch it on when I want to pull some downstream event forward in time. I'm sure the logic of how it works makes perfect sense to some developer somewhere, but it doesn't fit my expectations.

JPK wrote on 7/11/2020, 11:23 PM

Yeah @john_dennis I feel it has to be a bug that has slipped through the cracks. Think they are moving markers that are > or = to the events start time, they need to only move markers that are >.

I can't see how the current behaviour would be anything other than a nuisance to anybody.

I'm not usually a frequent user of Auto Ripple, the project involved many different sections of voiceovers that all required editing. Had to move these markers back to the right spot what felt like a hundred times.

EricLNZ wrote on 7/12/2020, 12:10 AM

https://www.vegascreativesoftware.info/us/forum/unexpected-rippling-behaviour--120350/

Unfortunately, the legacy ripple logic has the same bug.

Yes. I've forgotten which ripple problem Marco's suggestion attended to. The 'bug' in the link is a real pain if you trim the end of a long clip, such as a piece of music, and forget that all your events that start after the music start will waltz down your timeline.

john_dennis wrote on 7/12/2020, 1:48 AM

@JPK

"I feel it has to be a bug that has slipped through the cracks. Think they are moving markers that are > or = to the events start time, they need to only move markers that are >.

I can't see how the current behaviour would be anything other than a nuisance to anybody."

You are correct about the logic. If you look at the Edit Details Window, the marker and the start of the clip that you're resizing are at the same location on the timeline.

A possible workaround:

Make the marker and the start of the clip you're resizing have different locations on the timeline by dragging the clip (and everything beyond it) to the right before you resize it. Grab it anywhere except the left edge.

Sardonic Humor

Try to remember that workaround in the middle of a hot, steamy editing session. Or, when you're half asleep. Or, on any Monday before 1030. Or, ...