Skip to main content
Participant
January 24, 2023
In Development

Cursor Frame Behavior (Affecting In Out, Ripple Edits)

  • January 24, 2023
  • 65 replies
  • 2441 views
Cursor Frame Behavior (Affecting In Out, Ripple Edits).

Ok team, I know you had some guy complain about how the Cursor works in the timeline, and now you changed how it works, which completely screwed over the Ripple Trim to Previous Edit.

What WORKED before yesterday was if you were on the front of a clip in the timeline, and you hit the Ripple Trim to Previous Edit, it would remove the first frame and obviously move the entire timeline up a frame to compensate.

THIS WAS INSANELY HANDY because if you're trimming a clip, you could just hit that button a few times and make it work right.

Now, because you guys changed how the cursor works, I have to hit Right on my keypad, and then hit the Ripple edit button, and it'll remove that first frame.

Guys, you seriously screwed over an entire generation of editos who know how editing works. I know some people complain about how the cursor works, but this sucks.

Why not just create a preference option where you can make the Cursor act like FILM or act like it is now. All NLEs were based on film editing, which lots of people expect and relied upon. Now, I have to hit an extra keystroke all the time which is massively time consuming.

Can you please just put in a preference option to revert back or not? That would solve this issue for everyone instead of bowing to people that don't understand NLE history.

65 replies

Known Participant
January 24, 2023
I second this. At the very least can we get a toggle? I have nearly 6 years of muscle memory using ripple trim to adjust clips one frame at a time and this won’t be a trivial thing to get over. Thanks for your consideration!
Known Participant
January 24, 2023
Any chance we can get confirmation on whether this is a bug or a feature? I can't find it listed anywhere in the change notes listed here: https://helpx.adobe.com/premiere-pro/using/whats-new/2022.html

This has to be a bug, right? Why would anyone change this after it's been this way for so many years?

EDIT: Turns out it's neither and it's actually supposed to be a bug fix:

"Ripple Trim shortcut will slip one frame."

https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html
Participating Frequently
January 24, 2023
Yes I agree.

I am reverting back to the old version until they change this.

The definitely need to fix this ASAP. This is easily my most used shortcut and speeds up my workflow an enormous amount. 


How is there now option to delete/trim just one frame in front of the playhead!
Participant
January 24, 2023
Agreed!
Participant
January 24, 2023
I second this!! I've been trimming for years this way and now the entire workflow is slowed down big time