I haven't tested this yet, but I can imagine a playhead constantly snapping will make editing very difficult, and I'm not sure what purpose it would serve to snap the playhead to strip ends as a mode? An alternative approach would be to map the goto next/prev function to the mouse wheel, which will make it fast to move the playhead forward and backwards at strip starts/ends.

This is what I wrote about this in the VSE chat: https://blender.chat/channel/vse?msg=zwvwp2GJNfoRuhJCo

As it is quite annoying the multi-tapping on J, K & L for playback speeds are missing from the VSE, an alternative approach could be to look at movement in the 3d space, where +shift alters the speed and +ctrl snaps, that could be translated into the following vse keys/functions: alt + mouse wheel = scrub 1/-1 frame, shift + mouse wheel = scrub 100/-100 frames and ctrl + mouse wheel = next/prev. strip end. Unfortunately + alt can't be overwritten and is locked to +-1, so the +shift can't lower the speed like in the 3d view(but in walk/fly mode +shift adds speed too). In a gif it looks like this:

Download patch: https://blender.chat/file-upload/nP3hixfwjBpqHeEBL/scub_keys_installation_file.zip

Btw. Ctrl + transform is industry standard for snapping in NLEs.

In D11745#302819, @Campbell Barton (campbellbarton) wrote:

There are a few changes in this patch:

• Snapping sequencer strips has a threshold (if users prefer this it seems fine).
• Snapping the current frame has a threshold too (was this intended?)
• Use snapping by default (this is a bigger change).

---

Breaking away from Blender in terms of consistency isn't something to do lightly, and it seems disputable that this is even preferred by users.

I don't see why snapping needs to be enabled by default, if the button is available in the interface users who prefer this can always turn it on very easily.

---

I don't disagree, though I agreed for snapping to be enabled because it's not very intrusive currently.

Suggest to split changing defaults out of this patch since it's more of a design decision and isn't a significant part of this patch which otherwise looks fine for the most part.

By changing defaults, do you mean snapping being enabled? That is not scope of this patch, you can suggest this in D11759. This patch should be only for using snapping settings for current frame snapping changes.

I wanted to gather feedback on devtalk for snapping after this feature is implemented, because it will be possibly most controversial.