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.
中也 後藤 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.
Josh Taylor commented
Adobe Team... please restore this functionality. I'm using plugins that aren't playing nice with the old version of Premiere, but I literally cannot upgrade until this is fixed. It makes something that took one key stroke now take two keystrokes. I see that this post is on the top page of requests, so I really hope you see this and respond soon. It's been months and months and still no word from you all. Please fix this.
Going into 2022 with no fix for this?
Can someone please post here if they have any updates.
I cant keep updating the new version just to find out that it has not been fixed and then having to roll back again.
santiago saltor commented
We need a fix for this, NOW! IT'S RUINING MY WORKFLOW!
Zachary Spence commented
Need this feature back, I'll be stuck on PPro 2021 forever as I use it all the time.
선혁 이 commented
I hope the tool can turn this off and on again.
David Goodliffe commented
Please fix. Can't use any new versions until you do and it feels like a rip off.
Russell Hasenauer commented
Please fix this! Was excited to upgrade to 22 until I realized I couldn't hit Q to delete a frame at a time at the beginning of a clip. Use this constantly in my work and having to work around it slows things down considerably.
Andrew Parker commented
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!!!!
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.