1 Correct answer
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 playhea
...
100
Replies
Dear Artpechka,
Hi.
yup
Rock on, then!
Kevin
Hi Josh,
Sorry for the frustration. I believe your thread expresses the concerns of a good number of Premiere Pro editors, so thanks, in advance.
It is disappointing that we are all being directed to the UserVoice page, but after months and months, still nothing has been done about it.
Did you upvote on the User Voice page yet? That's the best course of action you can take. Sorry for the impact on your work and that you had to move back to the previous version.
Not sure where you learned about this hidden feature, but I never knew about it and I edit daily. Granted, it is pretty cool, but I've never seen such a thing fly under the radar for so long. There is nary a mention of it within this community, on YouTube, or any blog post since the Q/W functionality was introduced around 4 years ago. We both know it is not listed in official documentation: the Premiere Pro User Guide.
To reiterate: Ripple Trim to Playhead didn't work as designed and trimmed off an extra frame every time you used the tool: that's not cool, and I'd think anyone would agree with that.
In fixing the bug, the undocumented hidden feature (AKA the Q bug/ripple trim frame by frame to playhead at the head of a clip) was removed in the process. Why? The code is different now. The team had no idea about how you and others were using the tool and did not test against a hidden function. Sorry. Things like that do happen from time to time.
I hope you approve that Ripple Trim to Playhead got fixed to work as designed. Just sorry it cut off a function you used in the process, a function devs or support had no idea about.
it's hard for me to verbalize why exactly this functionality is so important.
You don't need to. I like the hidden feature too. Pretty cool once I tried it. Like many others, this feature is not documented in the User Guide. I and many others had no idea it was ever there.
It's frustrating that a problem is being presented from a lot of accomplished editors, and there is either no response, or the response is: "That was a bug.
I've been responding to this issue. Right? Who were you expecting, Adobe Sensei himself? 😉
I'm the support guy who feeds the issues to the team, so they know about this issue brought about by the bug fix, and yes, a feature request for the hidden feature (ripple trim to playhead: frame by frame) is filed, but the team actually is not found on these user to user forums, so it seems like silence. They are engaging over on User Voice, but their participation tends to be somewhat sparse since they are so busy. Sorry about that - you're stuck with me on these forums; that's my gig.
So what do users want? They want the hidden feature back in addition to the bug fix for Q that won't delete an extra frame. Additional development needs to occur in order to get both of these things working as you would like, and unfortunately, that takes time.
Speed and efficiency are our jobs. With the new update, Premiere is asking us to be less efficient in order to do things correctly.
Adobe Sensei is pretty awesome, but I don't think there was a way Adobe could read your mind when you used a hidden feature. This is just one of those occurrences you have to live with until a some kind of new feature or fix arrives. It's nothing Adobe did on purpose to ruin your workflow. Devs didn't know...
I understand that these things happen sometimes. It's really just the silence that is so frustrating.
Again, these are user to user forums. The devs do not visit these forums, they are not being silent on purpose - they simply aren't here.
There is one guy in this thread who works for Adobe, but all he's able to do is link us to a page that Adobe hasn't responded to in over 2 months, though it's the top result on the "Hot" tab.
If the post is #1 in the "Hot" tab, that's a good sign that devs need to pay attention to the issue. It's the best we as users can do! Because it's at the top, it's a very good sign! So this "one guy" here (me) thinks the community is doing a good job by upvoting and commenting in the post.
It's not like we're even asking for anything "new." We just want to be able to toggle something in Preferences that restores the previous functionality. That's it.
Great idea for how you'd like to see the feature implemented. Make sure you add that comment to the User Voice post. When you say, "that's it," you make it sound like the feature would be simple to implement and should be done immediately.
Unfortunately, that is not how software development works. New features to take a lot longer to implement than users expect as said features can need a lot of testing within the skunkwerks to make sure that other things do not get broken, or new bugs do not get created, in addition to having the new feature functioning the way users expect. These are the dangers of adding new features, by the way, something I would never have known had I (as an editor) not worked internally at places like Apple and now Adobe. I'll share this with you: in software dev, you can't just add a feature willy-nilly - especually if it might break an important hunk of the software, referred to as risk.
There is a broad misunderstanding of how NLE software dev actually works amongst editors, it's freakin' tricky at times!
I hope to close the gap in helping folks understand how stuff works, how stuff breaks, how stuff gets fixed, and how everyone can remain calm and understanding when such issues occur. Feel free to ask questions.
There is a lot of mystery behind the doors of NLE software dev, and some of it, no, most of it, is necessary because of business protocol. For users, you do have to be persisitent in expressing the faults of their NLE, but also understanding that devs are only human and are working as hard as possible on a tool they are very proud of. Be vocal, but do remember to be kind, as well.
it's disheartening the longer we hear nothing from Adobe.
I hope I have shown you that Adobe is listening. I'm "that guy" you will hear from on these forums. To get in touch with devs, leave a comment in the appropriate user voice post. If you were hoping to hear, "hey, we'll put that hidden feature back in the next release," I'm sorry. "When" questions cannot be answered because of the business protocol I mentioned earlier. The best thing you can do is have others upvote the feature request. OK? I do appreciate your patience and understanding, so thanks.
Regards,
Kevin
AdChoices