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

andrewp6078904
Participant
January 24, 2023
Yeah I have definitely noticed this. It is driving me nuts. I loved being able to do that. Please bring back the previous functionality of Ripple Trim to Previous Edit!!!!
Participating Frequently
January 24, 2023
I also use this on a daily basis! Unfortunately, as it often happens with Adobe upgrades, the "bug" is the fix!
Participating Frequently
January 24, 2023
Hello Adobe's Team,

Hope this finds you well and safe.

The solution that Adobe is proposing makes us go through 3 steps instead of one. So, you can understand our frustration with a software we are paying for and at every upgrade makes us face similar challenges.

To use a previous version of Premiere Pro should never, and I mean, never be suggested as a solution, because:

1) We pay for the service, so we expect it to be working 100% and that we will be able to install the latest version as soon as it's released (unfortunately, that rarely happens);

2) We as editors have to be up to date with the latest versions, because most of our clients/agencies today, do have their Premiere Pro also installed, so can you imagine how "nice" it is for us to have to explain to them or even warn them not to install the latest updates due to bugs? If it looks bad for us, can you imagine how bad does it look for Adobe?

3) Editing is a beautiful and ever evolving craft, therefore the workflow keeps changing, because we are always finding new ways to improve it. Thus, the normal protocol is not always the best protocol, because in this case, it makes us spend 3x the time we would, should we have this feature available. Can you imagine, if we were to go back in time and tell Dziga Vertov, Sergei Eisenstein, and Thelma Schoonmaker that they shouldn’t make the changes to the way that they did things because they were breaking protocols? I don't think so, therefore the explanation we received from Adobe on why this feature was removed does not work for me either!

Thanking Adobe’s Team in advance for their time, because I am sure you will speed this up and get this sorted for us, before we reach 2022.

Cheers!
Participating Frequently
January 24, 2023
Installed the new v22 update. Checked to see it functionality had been restored. Deleted.
Participant
January 24, 2023
*use of a translator

I also very much agree.
This fix is ​​really the worst fix ever.
If this is a bugfix, why hasn't this bug been fixed for a long time?
This was a very useful feature when doing precise 1f edits, but now it's completely trash.
Known Participant
January 24, 2023
This change actually makes it so ripple trim is less handy in another way.

Say I have a clip in V1 and a clip in V2 in picture 3. If I want to ripple trim and remove the excess in V1, I can't do it in one stroke anymore.

I used to be able to go one frame back, then ripple trim (picture 2). And end up with picture 1.

Now, I have to use Add Edit and then manually delete.
Participant
January 24, 2023
You are absolutely right, this is the reason why I've not upgraded because it makes the edit process slower.
CiscoLC
Participating Frequently
January 24, 2023
FIX!
AntonioGreen
Participant
January 24, 2023
Yes, please fix this
Inspiring
January 24, 2023
I use E/R as frame advance left one right one frame and keep Q/W as ripple trim so if you have it mapped like that you just have to bounce between R and Q on the keyboard with the left hand. Its not so bad but yeah I can see how this is annoying if you are left on default keyboard mapping.

My keyboard shortcuts are loosely based on this guy's. Sort of changed my life ha.

https://www.youtube.com/watch?v=lB_-WaDsTlE