Ripple Edits Keyboard Short-cuts

Rednroll wrote on 9/7/2019, 8:39 PM

From Page 565 of VP16 Manual.

These keyboard short-cuts don't seem to be working.

Post-edit ripple affected tracks = F
Post-edit ripple affected tracks, bus tracks, markers, and regions = Ctrl+F
Post-edit ripple all tracks, markers, and regions = Ctrl+Shift+F

I'm expecting as I use each of these KB short-cuts then Vegas would change the Ripple Mode as defined under the options menu when Auto Ripple is turned on. Except they don't seem to be doing anything. The Ripple mode stays at whichever last setting it was selected under the options menu.

Are my expectations incorrect or are these short-cuts not working?

Back to post

Comments

Former user wrote on 9/8/2019, 7:50 PM

No, it means that the ripple happens after the edit, but is based on the options you choose among: affected tracks, affected tracks, bus marks, etc., or all tracks markers or regions.

Rednroll wrote on 9/8/2019, 9:19 PM

No, it means that the ripple happens after the edit, but is based on the options you choose among: affected tracks, affected tracks, bus marks, etc., or all tracks markers or regions.

Yes, we all understand what it means now. It can have 2 very different meanings is the problem, the manual and the online help do not assist in describing it better so it can't be misinterpreted and typically when you refer to something as being "POST" in A/V terms the use as it applies here can easily be misinterpreted to how it actually functions. Please see the use of "Post Fader Sends" which is a pretty standard understood use of the word "Post" when working with A/V.

Sylk wrote on 9/9/2019, 9:50 AM

@Rednroll

Anyway, please select the solution you want to turn the thread as Resolved. Thanks

michael-harrison wrote on 5/17/2020, 3:39 PM

1) Thank you guys for hashing this out. I ran into this "problem" today and it had me stumped.

2) Look! The forum search actually worked! :-)

While I was also expecting the keyboard "commands" to be a state change, I'm glad that it's not. Using these in conjunction with Unified Remote will really speed up my workflow