elkins.alex wrote:Can we talk about the
Next Clip/Edit shortcut please?
It's something that has been mentioned by numerous people for years and yet I never see any acknowledgement from BMD that there is a problem.
I'm talking about the issue where having a clip selected in the Edit page and using the 'next clip/edit' shortcut (
down arrow)
doesn't jump to the next edit point unless you deselect clips first. It's completely counter-intuitive to anyone coming to Resolve from an editing background. See below.
Here's a timeline. A clip is selected but the playhead is further forwards.
1.jpg
I press the down arrow and this happens:
2.jpg
Notice how the CTI has gone BACK IN TIME. WHAT!?
Here's what should happen:
3.jpg
On the edit page the down arrow shortcut should
always move the CTI to the next clip in the timeline, not the next clip after the selection. The CTI is king. I should be able to navigate around the timeline using up/down arrows without clip selection changing. This is how all the other NLE's work.
This simple issue is literally the only thing that has stopped me making Resolve my main NLE for the past couple of years. It's that much of a show stopper because I'm being asked to relearn 15+ years of muscle memory.
I can't stress how counterintuitive it is to have your playhead jump back in time to the next selected clip rather than forwards in time to the next edit point in the timeline. I always expect the down arrow to move me forwards in time to the next shot in the timeline. It's that simple.
I'll add that track selection shouldn't have any bearing on this either. Pressing the down arrow should
always jump to the next edit point on any track, and there should be a
separate shortcut or preference to factor in track selection as well.
Yes, I completely understand that this behaviour is preferable in the Color page, but we're not in the Color page.
Please don't tell me that all I need to do is deselect the clip first. There are many reasons why I wouldn't want to deselect a clip while I jump around the timeline. I've been using Resolve since v9 and I get it. I know how to work around this problem. However, with the massive improvements coming up in DR17 I'm absolutely certain that BMD are going to find more and more editors hitting a major stumbling block here.
I desperately hope they finally recognise this issue because it's a major time suck. I can't be the only person who thinks this, can I?!