Moving the edit point of a clip with shortcut keys the selection is lost after one movement

[BrianLevin]

When you are CMD+dragging or Shift+clicking edit points to select the trim points, and then moving them with ALT+Shift+arrow keys, after you move them one time the selection is lost and you need to make the selection again to continue editing. This happens on both audio and video.

Demonstration is here:

https://www.dropbox.com/s/04aeclv87sqhkiz/230124_trim%20selection%20bug.mov?dl=0

As far as I can tell this behavior is new to 23.1.

Happens on two machines, both M1 fully specced out RAM. Happens in all sequences, doesn't matter what codec is being used or what type of clips I have in there.

[Moderator note: confirmed behavior so moved to bug section of forum.]

[R Neil Haugen]

I can replicate the "it loses connection to both" after on move on my PC. But it still can be used to select both and move again.

So I think this may be more of a Macb based bug. And yea, it would seem buggy.

Neil

[BrianLevin]

It shouldn't lose the connection at all, that's the bug part of it. Can certainly select it again, but that's a pain in the butt of course as you wouldn't want to have to keep selecting every time you move it one frame if you are auditioning an edit point. So I think even on PC you've got the same bug that I've got on my end, thanks for chiming in!

[DJP2014]

Thank god it's not just me.

It's been doing it on my M1 MacBook Pro since 23.1. Definately a bug. Really annoying as it's a core shortcut I use all the time. 

[Kevin-Monahan]

Hello @BrianLevin,

Thanks for the message. It’s been a long time since you filed this bug. I apologize for the lack of a response. Are you still having this issue? If so, the team will need more info from you to reproduce the bug. Can you provide the information required here? How do I write a bug report?

I'll move your post to the Discussions board while we await your information.

Thanks,


Kevin

[BrianLevin]

I believe you guys actually fixed this really quickly after I posted about it, I don't remember it lasting more than one dot release. If I'm remembering correctly at the time I was going back and forth with Wes Howell a lot on various bugs and workflows and this came up in conversation so I think he made sure it got reported on the back end. All good now on 24.1.