Cursor Frame Behavior (Affecting In Out, Ripple Edits)

We have added the desired functionality, Ripple trim of first frame when you are at the head of a clip, as a new shortcut - Ripple Delete Head Frame. This is in the current Premiere Pro 22.5 Beta (build 032+) available in Creative Cloud.

Back by popular demand you can ripple delete one frame at a time with your preferred keyboard shortcut. To use it, set up a Keyboard Shortcut (Option-Command-K) and search for “Ripple Delete Head Frame.” Once you have designated your KBS, position your playhead before the extraneous frames, press your chosen KBS and delete one frame at a time until you land on your ideal first frame. Try it out and let us know what you think!

https://community.adobe.com/t5/premiere-pro-beta-discussions/ripple-delete-frame-shortcut/m-p/12953527#M5937

Please just allow the play head and shortcuts to act like it do in version 15.4.1

It cant be that hard to resolve this...

Sometimes you need to take a few more frames off after Ripple Previous Edit to Playhead and sometimes you need to put a few frames back.

I wouldn't mind if pressing Q a second time after doing "Ripple Previous Edit to Playhead" switched to "Select Nearest Edit Point as Ripple In" or pressing W a second time after doing "Ripple Next Edit to Playhead" switched to "Select Nearest Edit Point as Ripple Out" which allows the editor to use Trim Forward (option right) or Trim Backward (option left) to ripple forward or backward.

please please please please please please please please
fix it.
fix it.
fix it.
fix it.

I feel like this will nit get resolved so I am sticking with 2021 ...

this is the sole reason I am not updating to 2022! it was such an incredible help when doing fine selects. trimming one frame with ripple trim at the clip's begin absolutely needs to come back

Reposting Stepen Gardner's exact idea because this STILL HAS NOT BEEN ADDRESSED.

Cursor Frame Behavior (Affecting In Out, Ripple Edits)
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.

Adding my name to the sea of voices. I can't believe something I originally thought was an error just got completely worked into my workflow.

Adobe. Fix this or be slapped.