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.
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...
Warren Heaton commented
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
Mike Lukavecz commented
I feel like this will nit get resolved so I am sticking with 2021 ...
David Gesslbauer commented
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
Travis Tessmer commented
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.
David Goodliffe commented
Adobe. Fix this or be slapped.
I think the easiest way for Adobe to "fix" this would be to add two more shortcuts, and name them thusly:
Ripple Trim Next Edit To Playhead (repeat to trim 1 more frame)
Ripple Trim Previous Edit To Playhead (repeat to trim 1 more frame)
So, editors who are used to working the old way, could assign "Ripple Trim Previous Edit To Playhead (repeat to trim 1 more frame)" to Q, and "Ripple Trim Next Edit To Playhead" to W.
Also, editors could try putting "Ripple Trim Next Edit To Playhead (repeat to trim 1 more frame)" on W and see if it's just as useful as the complementary shortcut is on Q.
Anyway. So long as experienced editors know about it, this will make everyone happy. No need to add another weird setting. All we need are two extra shortcuts to use. (or just the one for Q, but now I'm curious to know how useful the same functionality would be on W.)
Adobe, I hope this makes sense! Okay, bye! Sorry for talking about the console! (They don't like that)
I also greatly miss this "feature." Even though it only ever worked with Q. That is, hitting W multiple times does not and has never trimmed off one frame at a time from the RIGHT side of a clip. So I can see that maybe Adobe wanted some consistency up in here.
Anyway, I wanted to be able to tell you guys that I found a fix for this in the console debug database, but I didn't.
If you don't know, you get to it by hitting CTRL F12, clicking the triple line "hamburger" on the panel that appears, and selecting "debug database view."
WARNING: THIS IS DANGEROUS. DO NOT FIDDLE AROUND IN HERE OR CHANGE ANY DEFAULTS UNLESS YOU REALLY KNOW WHAT YOU'RE DOING. IF PREMIERE CRASHES HORRIBLY, IT'S YOUR OWN FAULT. DON'T CALL ADOBE ANDD WHINE ABOUT IT. HERE BE DRAGONS.
Anyway, the only setting I've ever changed in here was "FE.AllowMultipleOpenProjects" to false. Though, these days, I leave it at "true," as I actually prefer it now.
I was hoping that perhaps this behaviour change would also have been added to the console.
I took screenshots of the entire console database in Premiere 2021, and also of Premiere 2022. Then I stitched them together in photoshop, and sent the whole thing through a free online optical character recognition program. Now I have the plain text of both. Putting them into notepad++ and running the "compare" plugin, now I can see what items were added, deleted, or had their default values changed!
"Use AdobeCleanUX in V7" is a new item, for example. I tried changing its value from TRUE to FALSE, but the ripple trim behaviour was unaffected. Maybe you'd have to restart premiere before it'll actaully take effect. I have no idea.
I tried changing several other commands, but each time, the ripple behaviour remained unchanged. It is POSSIBLE that it's in here, but might even need multiple lines to be changed... but it's just not worth the risk.
I've put all of mine back at the default values. Someone else may wish to continue my "research," which is why I uploaded the lists. Good luck! Be super careful!
中也 後藤 commented
Please reinstate this bug as a formal feature. Longing for it!
Alex Dedof commented
Guys, come on! It's a choice of preferences. Give us the option to just turn this feature on!
I want to work in new versions of the program that have this feature. It's very easy to do, just 1 checkbox.
Does anyone know if this has been fixed yet or if they are even looking at doing it...?
David Goodliffe commented
FOR THE LOVE OF ALL THAT IS HOLY, FIX THIS, ADOBE
How is this still not resolved?....
Cameron LaPrairie commented
Matthew Sturrock commented
Please please PLEASE revert this back to how it was. This should never have been considered a bug but rather the way it should work and is driving me insane. It's taking twice as long to complete this task for absolutely no reason. Why would Q not delete a frame at the start if it does it one frame forward? Makes no sense.
Mike Lukavecz commented
Do we have ANY news on this one ? I rly rly need that feature for may daily work! That speeds things up so much.
Emile Rizk commented
Jesus why has this not been fixed yet? When you think that something most of your user love is a bug and you "fixed" it, how can you not revert it back ASAP when people are clearly upset how this "fix" negatively impact their workflow and is a step backward. ITS BEEN MORE THAN 2 MONTHS, DO SOMETHING
Sanal Stanly commented
revert back pls
Zachary Spence commented
This is a critical function for my editing workflow, I can't use Premiere Pro without it.