Speed Editor needs Ripple Trim Start/End to Playhead

Dynamic trimming on the Speed Editor is a ton of fun, but kind of useless when you want to trim a large portion of a long clip.

Currently I know of two ways to do it on the Speed Editor:
1. Use the jog wheel to very slowly trim a long clip. For e.g., you'd have to scroll all the way towards the end of the clip to get the Smart Insert indicator in the right place, then hold Trim Out and scroll all the way back. This is just stupidity. Nobody is actually going to do this.
2. Split the clip, position the playhead over the excess clip and Ripple Delete it. Not terrible, but not ideal. 3 actions to take when one should do.

Please just let us tap or double-tap the Trim In/Out buttons to ripple trim to playhead. You can already do this with standard keyboard shortcuts (Ctrl+Shift+[ or ]), but we want to stay on the Speed Editor as much as possible.

Thanks.

As you say, you can use keyboard shortcuts - I have mapped F7 & F8 for just this task. My Speed editor is right beside the keyboard so this is a quite natural two handed edit.

I wonder if anyone is using a macro keypad like the Elgato streamdeck or Loopdeck for extending the Speed Editor's functionality?

+1 I hear you. I use ripple edit all the time and having on the speed editor would be nice.

I'm getting by with just using split clip and delete on the speed editor. On the edit page I have ripple trim mapped to the two side buttons on my mouse and my third extra mouse button mapped to split clip.

As you say, you can use keyboard shortcuts - I have mapped F7 & F8 for just this task. My Speed editor is right beside the keyboard so this is a quite natural two handed edit.

I wonder if anyone is using a macro keypad like the Elgato streamdeck or Loopdeck for extending the Speed Editor's functionality?

I’m using a streamdeck, and plan to use it to fill in the gaps. So far, I’ve only been messing around with old footage for a few days, trying to identify what’s missing, and what would be helpful on the streamdeck. I’ve also been trying to familiarize myself with the cut page, which I’ve largely ignored until now. I start my next editing project tomorrow, so that’ll be a better test.

It also took a while to fix all of the shortcuts that broke with the R17 update, but I think I’ve got most of them ironed out now.

I was using a modified version of the shortcut set that shipped with SideshowFX’s Icon set for the streamdeck, but that set also included a lot of strange departures from Resolve’s defaults.

To get back to a more factory-friendly set, which included the customizations I liked but excluded the ones I didn’t, I exported R17’s default set, exported the customized, outdated R16 set, alphabetized them both in Python, did a line-by-line diff comparison, and took notes on what to change, then made the changes to streamdeck, keyboard maestro, and Resolve.

The moral of this story is that it’s easy to waste more time fiddling with streamdecks and macro software than they’re likely to save you over the long run, especially considering all of the shortcuts you’re going to want to change when the next doodad or Resolve version comes out.

And so far, the thing I wish they’d included most on the speed editor is a normal overwrite edit. It’s weird that they included so many buttons that you use infrequently, and so few of the ones you use frequently.

It’s weird that they included so many buttons that you use infrequently, and so few of the ones you use frequently.

This, exactly. I get that it's a version 1 product, but some of the decisions are just headscratchers - the dedicated Smooth Cut button particularly stands out.

A lot of that, however, can be mitigated with a software update that allows us to reconfigure the buttons to our own commands. That would significantly up its value proposition.

2. Split the clip, position the playhead over the excess clip and Ripple Delete it. Not terrible, but not ideal. 3 actions to take when one should do.

I second that. That is sooooooooooooooooooooo important....

The speed editor is obviously about editing fast. Needing 3 actions instead of one is NOT increasing the speed but its the most basic task that you have to do hundreds if not thousands of times per day. If you multiply that by 3 it is a pretty significant waste of time or the other way around, one very minor change (doubble tap in and out for ripple trim) for a ton of time saving.

2. Split the clip, position the playhead over the excess clip and Ripple Delete it. Not terrible, but not ideal. 3 actions to take when one should do.

Please just let us tap or double-tap the Trim In/Out buttons to ripple trim to playhead. You can already do this with standard keyboard shortcuts (Ctrl+Shift+[ or ]), but we want to stay on the Speed Editor as much as possible.

I second that too!!

++1
Yes, double-tap the Trim In/Out buttons to ripple trim to playhead. I need this to start using Speed Editor more often!

Agreed, double-tapping trim in/out would be awesome!

I suppose there has been no news yet from BM regarding this?

Sorry for OT but at this point all of this is just a joke to me. Clearly they don't read anything in this forum and they barely use their own software, or many many major things would long have been fixed.
There is at least 10-20 things or even bugs in this Forum that are fairly simple and got requested over and over again for years but they clearly don't want to have a good software for the majority of modern content creators. Instead they want to troll us. There is no other explanation. How can speed ramping stay the way it is if this is not true? Some one please explain.


Actual relevant comment: please include a "redo" button too. That is also very very annoying and a reason I constantly have to switch between the speed editor and my regular keyboard.
Many others are suffering from this too. Guaranteed.

Sorry for OT but at this point all of this is just a joke to me. Clearly they don't read anything in this forum and they barely use their own software, or many many major things would long have been fixed.
There is at least 10-20 things or even bugs in this Forum that are fairly simple and got requested over and over again for years but they clearly don't want to have a good software for the majority of modern content creators. Instead they want to troll us. There is no other explanation. How can speed ramping stay the way it is if this is not true? Some one please explain.


Actual relevant comment: please include a "redo" button too. That is also very very annoying and a reason I constantly have to switch between the speed editor and my regular keyboard.
Many others are suffering from this too. Guaranteed.

Ok, if the devs or Grant don't read this forum what is the next best way to get our message through? Should we all start pushing tweets to Grant, emails to customer service and upping these threads? Make it a steady campaign until we get some answers
We would need a cool hashtag to tight it all together, any suggestions?

Agree on the Trim in/out doubletap.

mapping ripple trim to playhead works and would on a streamdeck as well I guess.

However I have a OT question if I may: On the cut page, ripple trim also affects any sound track added below the main track. Why? Also if I split a clip and want to ripple delete one of the parts it leaves a gap instead of doing a ripple. This only when there is a sound track on A1. Mouse clicking on the gap clip and then pushing ripple del again works but there must be a better way. Locking the track does not help any of these issues. Any hints?

/Johan

@PauliJ

Great idea. I already thought about making a video to start a movement or something. But most certainly it wouldn't work. Twitter might actually be an option.

@johanwagner

That gap situation on the cut page is an absolute pain. Happend to me over and over again and many people complained about it, but no one seems to know what causes it. It's not necessarily the audio. In the beginning of a project, it usually works with the audio as well.

I ended up not using the cut page any more after I did my initial footage selection and rough cut. Once I start with music and fine tuning on the edit page, I avoid going back to the cut page for that exact reason. The only thing I'm missing on the edit page, that some times makes me still switch is the "move" feature on the cut page with the speed editor. Its just the most convenient/efficient way to re arrange parts of the story at a later stage, at least as far as I know.

+1

trim to playhead

+1 for being able to double click the Trim In and Trim Out button to Trim Start and Trim End. These are the most important tools in Resolve, which I use all the time with 3rd party controller hotkeys. Having these functions in the Speed editor would make it significantly more optimal editing piece of kit.

3 years later, and it seems the Blackmagic design team has been ignoring community requests to improved the functionality of the Speed Editor. It is quite odd because it seems the team is full on addressing community bugs/requests for the software, but not for the hardware?

Trim start/end to play head can be integrated so easily into the controller. Just add double-click behaviour to the "Trim in" and "Trim out" buttons. Sell the new ones with the updated graphics and release a clear explanation in the release notes. Or forget it, if it is too much expense to update the button graphics, just place it in the release notes! Still so much better to have the additional functionality in there than to ignore the value of the community suggestion because the existing hardware may not have the most up-to-date labels.

Or give us the option in the Control panels software to add our own customisation! That would be an absolute killer feature!

These days, I am using just the search dial of the speed editor, rotated sideways next to my keyboard so it takes up less space, as I still need all essential functionality not available on the Speed Editor, especially the trim start/end to playhead

I just got my Speed Editor and I am shocked that a simple Trim From and To playhead is simply not possible with it. 90 % of my workflow is based on this feature.

Please, BlackMagic, enable it for double Tap on "Trim in" and "Trim out", both in Cut and Edit page.

+1
the only reason .. why i got speed editor is trim to playhead with the scroll...so i can set on my bed and do this....now I basicly did nothig with my purchase...I have to use the keyboard OMG..
BM please ... ripple delete to the play head in Speed editor...or call it the slow editor.

+1

+1

Seeing an extremely valid and presumably easy to implement request just sitting here unacknowledged for this many years, especially with a feature that would make the product more attractive and possibly generate more sales.. gives me Adobe vibes :-/

I bought it and i dont use it or the cut page anymore because its just slower compared to ripple trim start/end to playhead. Add the fact that its impossible to do ripple edits in the cut page when there is a fixed underlying music track make both completely useless to me. And both problems could be fixed easily.

+1
Same here with my Speed Editor, amazing tool.
When we edit, we often search for a moment in the timeline with the playhead.
When we find it, we don't want to move it and do anything else, we need ONE key (Ripple To The Playhead Start or End, mostly End) that could make our life much better.
That's why we need the one key to do the job to trim out after (or before the playhead). The playhead IS THE TOOL WE USE ALL THE TIME.
-
I don't think they don't care about this. In the past, they implement some features we strongly asked for, for example the grey UI after making it dark blue a few years ago. But surely they are busy creating new products. Personally, I would prefer to have less but great and optimized products than to have more not-perfect ones.
-
By the way some keys from the Speed Editor don't work anymore after the update to Resolve 19.01, like the TRANS. I used to click it it trims automatically to make the transition work.

Guys, my workaround is to use the ripple delete function by having the parts that I want to remove within an IN and OUT range then pressing ripple delete. Usually, I only need one of them since I'm trimming at the start or at the end and it's quite fast.

The problem is if you've already used the IN and OUT ranges for its actual intended purpose and don't want to move them anymore but wanted to trim to start or end, then you can't use my workaround.

Seeing an extremely valid and presumably easy to implement request just sitting here unacknowledged for this many years, especially with a feature that would make the product more attractive and possibly generate more sales.. gives me Adobe vibes :-/

I bought it and i dont use it or the cut page anymore because its just slower compared to ripple trim start/end to playhead. Add the fact that its impossible to do ripple edits in the cut page when there is a fixed underlying music track make both completely useless to me. And both problems could be fixed easily.

When we edit, we often search for a moment in the timeline with the playhead.
When we find it, we don't want to move it and do anything else, we need ONE key (Ripple To The Playhead Start or End, mostly End) that could make our life much better.
That's why we need the one key to do the job to trim out after (or before the playhead). The playhead IS THE TOOL WE USE ALL THE TIME.

Exactly! With the addition of this two functions alone i would use the speed editor way more often. Right now i use it as a nice jogwheel, and even there its not very helpful to me because there is no "loop in to out" etc etc etc

+1

Very sad... Just got my Speed Editor and I am really dissapointed with lack of this feature.... And this topic is 4 years old...

+1 would be so useful. Right i am just using it as a jogwheel.

+1

can't stress this enough. double clicking trim in / out should ripple trim start / end

+1 for TAP to trim as per keyboard shortcut, and TAP+HOLD to use detail trim as currently exists in the Speed Editor.

No sure how we got fixated on DOUBLE tap ? Sound like a military-gamer-badzombiemovie meme.

But maybe there is a good reason?