[b7] [win] [Edit] Replace command- Playhead/selection vs IN

Hello all,

See the image attached.

unable-to-replace-no-clip-in-active-track-bug.jpg (266.4 KiB) Viewed 655 times

This may not be a bug as such, but the behaviour isn't as expected.

to repeat:
1/ click to select a sequence clip
2/ mark an IN point later in the timeline, beyond that selected clip
3/ position the Playhead at the head of the selected clip
4/ position Source viewer Playhead at desired spot
5/ Replace command

result:
The replace takes place at the in point, not at the playhead and not at the selected clip.
It seems that to be consistent with other aspects of Resolve where selecting a clip over-rides track dominance etc, selection should also be first priority here too.

Thanks,
Mark.

With Replace, playhead position in timeline and source viewer determine how and where the replacement occurs (just like Premiere, FCP, etc.). You don't need in/out points unless you're doing a replace to an empty track and want to limit the amount of the source clip which goes in.

The "del" key performs a ripple delete. Backspace is "cut".

You're asking beginner's questions in a forum for reporting beta issues to BMD staff. In a word, RTFM.

With Replace, playhead position in timeline and source viewer determine how and where the replacement occurs (just like Premiere, FCP, etc.). You don't need in/out points unless you're doing a replace to an empty track and want to limit the amount of the source clip which goes in.

The "del" key performs a ripple delete. Backspace is "cut".

You're asking beginner's questions in a forum for reporting beta issues to BMD staff. In a word, RTFM.

No need to be rude John. You're making false assumptions.
The point of the report is consistency, not confusion about how to use the feature, did you read my report?

Also, I've mapped delete and ripple delete elsewhere, but that's completely besides the point. Did you read the report that talked about use of those keys to remove effects?
Mark.

Sent from my SM-N950F using Tapatalk

It's fairly standard that a marked in-point takes precedence over a clip selection or timeline cursor position. This behaviour is common to editing operations in Resolve and other editing software.

It's fairly standard that a marked in-point takes precedence over a clip selection or timeline cursor position. This behaviour is common to editing operations in Resolve and other editing software.

Hi Peter
Yes, IF the clip under the cursor is NOT click-selected, then the In point has priority.
But, if you select the clip at the cursor position, it should be consistent with the way other parts of Resolve works, for example, when you have IO points but click-select an clip not within the IO range and then use a command like Cut or Copy or Delete... the operation happens to the click-selected clip, not to the area between the IO points.

See the video here:

https://videoblurb.com/mp/selected-clip ... points.mp4

What I am arguing here is consistency. I don't mind if IO points always have priority, but then they should in all parts of Resolve IMO.

tx
Mark.