Resolve 17.2 Position Keyframe Snapping

Hey all.

Just updated to Resolve 17.2
In 17.1 and all the Resolve versions I've used prior, by shift + clicking and dragging, I could move a position keyframe backwards or forwards in time in the curve editor without it changing its value. Granted this could prove a little tricky sometimes because shift + clicking enabled snapping on either the time or value axis depending on which direction you drag first.

Now in Resolve 17.2, the snapping still works, but it snaps to a value anywhere between 10 pixels off to 200 pixels off... Editing the timing of keyframes in the curve editor without changing their value in Resolve is integral to our workflow.

I am aware of the existence of the keyframe editor. But we're constantly adjusting interpolation handles and comparing position keyframes with pitch, yaw, zoom rotation etc. We often need to move large groups of keyframes at once. We can't do this at all now with the curve editor because they all get offset together! The keyframe editor won't even allow us to work with arbitrary keyframe groups. The only temporary solution is copy and paste, which is a bad idea for many reasons. If you still think there's benefit in using the keyframe editor for the simple stuff, well...

It's broken too.

But this time not because it's snapping to the wrong parameter value, but to the wrong time. The only indication I have to nagivate this snapping dilemma is the value change offset in the tooltip that shows up.

Here's a short demonstration of the issue for perusal:
https://ibb.co/cvMC9TD

I'd love to know if any of your are experiencing the same issue or have found a workaround.
I may be moving back to 17.1 for now.

I'm not seeing any snap behavior at all.

I'm not seeing any snap behavior at all.

Gosh, that's frustrating. Are you saying that nothing's out of the ordinary for you? Or that the designed snapping behaviour is missing too? What OS are you using, Jim? I tested it on four Windows computers and two different projects. On both projects all the clips were retimed.

I also can not replicate your issue. Everything works fine for my setup.

What OS are you using, Jim?

Studio 17.2 for Windows.

I'm saying that when moving the keyframe, it didn't snap at all.

I don't know if that's a bug or by design, just what I'm seeing.

I didn't test re-timed clips.

Hey guys, I downloaded 17.2.1 on a test machine and can confirm the keyframe snapping issue is still there. I tested some retimed clips and some non-retimed clips and the issue is the same on both.

I've gotta say I'm a little worried...

Our entire company workflow hinges on flexibility in editing keyframes from the curve-editor. If they snap incorrectly or don't snap at all, we're stuffed. We'll be stuck with 17.1.1 until this is fixed or until we change NLE. Resolve does so much perfectly for us! It would suck to throw 10 activations down the drain and begin the futile search for an equally capable NLE - being able to totally retime a clip with transform keyframes, tracked power-windows and keyframed grades without anything breaking is about as flexible as we can ask.

I appreciate this may be a small issue for most but it's a deal-breaker for us.
We really need working snapping in the curve editor.

I'd love some communication from Blackmagic on this.
I'm happy to test the bug further if it helps.

Hey all, just downloaded 17.2.2 today and this issue is still present. I'd really appreciate some acknowledgement of this bug or at least some sort of communication.

It's been a month and a half (three updates later) and still none of our computers can update until this is fixed because it breaks our workflow.

Is anyone else able to test to see if they get this same behaviour?

I also can not replicate your issue. Everything works fine for my setup.

Sorry Peter, I missed you reply. You're running Mac OS? And you're familiar with usual keyframe snapping behaviour in the curve editor? Perhaps it's a Windows specific issue if it's all working normally for you.

Hey BMD, I'd really appreciate some acknowledgement here...

I'm still running 17.1.1 when 17.4.3 is available and this snapping issue remains unfixed.
That's a year and a half of missing out on development; two minor versions and two patches.

I've tested every version in between and the issue has remained:
curve-editor snapping is broken. Moving keyframes horizontally on the curve-editor causes them to jump to arbitrary values. At this stage, I'm holding out for an overhaul of the curve editor in 18 like many are, but without communication I have no idea if I'm still going to be here holding my breath in two years time.

If someone at BMD could please verify my claims or acknowledge that this is indeed an issue, that would be much appreciated.

To replicate my issue:
1. Run latest Resolve on Windows
2. Create some position keyframes with various values on a clip
3. Holding shift, move one of these keyframes to the left or right
4. Observe the value changing in the curve-editor's parameter tooltip that follows the mouse

In Resolve 17.1.1 and prior, holding shift causes the keyframe being moved to snap to an axis. Resolve guesses the axis you're trying to snap to. Moving vertically locks the keyframe time. Moving horizontally locks the keyframe value. This is the feature that's currently broken that I'm desperate to have restored.

I also can not replicate your issue. Everything works fine for my setup.

Sorry Peter, I missed you reply. You're running Mac OS? And you're familiar with usual keyframe snapping behaviour in the curve editor? Perhaps it's a Windows specific issue if it's all working normally for you.

YES. Everything works exactly as it should on my setup.

BTW it's way easier to move a KF in time using the KF editor display instead of the curve editor.

YES. Everything works exactly as it should on my setup.

BTW it's way easier to move a KF in time using the KF editor display instead of the curve editor.

Thanks for the reply Peter. I tested this on the latest version of Resolve on a Mac Mini M1 that has never had Resolve installed just this morning and I can confirm that the incorrect snapping behaviour in the curve editor remains.

The keyframe editor is another story though - in my initial post the KF editor was broken too and exhibiting a similar snapping behaviour where the dragged keyframe would jump backwards. It looks like it's working in the latest version, so thanks for suggesting that.

Also just noticed that Position keyframe creation in the inspector panel is displayed as "ganged" with just one keyframe diamond for both X and Y. While in reality it's only creating a keyframe on the active parameter axis. There need to be two diamonds for position in the inspector panel, one for X and one for Y if the axis are going to be treated independently like this.

Did you ever figure it out? I'm working with a lot of audio, and it would be very nice if this had a solution!

Unfortunately not... Just hanging out for Resolve 18 at this point.

This is so stupid.. Why not just move the selected keyframes horizontally with shift and vertically with shift+option for example. This is what i tried instinctively and the idea that both directions work with the same modifier key just based on which direction you move the mouse first. It's finicky and doesn't work with my super sensitive mouse 50% of the time.

This is so stupid.. Why not just move the selected keyframes horizontally with shift and vertically with shift+option for example. This is what i tried instinctively and the idea that both directions work with the same modifier key just based on which direction you move the mouse first. It's finicky and doesn't work with my super sensitive mouse 50% of the time.

Same here. It's hit and miss and requires multiple attempts most of the time.

This "issue" still remains. It's just a small bug, but it's enough to force me into searching for a solution. So far to no avail.