Resolve 17 inspector keyframe bug + crashing

Thank you in advance for your help. I installed Resolve Studio 17 on my 2017 iMac five days ago. Everything worked great for the first three days but I am suddenly having an issue with keyframes on every tool in the inspector panel in the edit tab.



The issue:



I’ll add a transform keyframe to frame 12 (for example), then I’ll step back one frame to add another keyframe to frame 11. The transform does not apply to that keyframe (even though it turns red) and will apply to frame 10.



The issue only affects frames directly before a frame with an existing keyframe. Sometimes, this causes the Resolve to crash as well but I don’t even get a “resolve has quit unexpectedly” notification.



Computer specs:



iMac (late 2017 model)
Big Sur 11.2.2

Processor: 3.8 GHz Quad-Core Intel Core i5

Memory: 32GB 2400 MHz DDR4

Graphics: Radeon Pro 580 8GB



I have hundreds of hours of roto work saved in these projects. Even though I believe I have my old Resolve 16 DB backed up correctly, rolling back would cause me to lose many hours of work from the past several days.

Should I try reinstalling Resolve 17 or update to 17.1? 

Any help would be hugely appreciated. 


There has been a development: I discovered that this issue is almost certainly occurring becuase I reorganized my media a week ago and used the "change source folder" option to relink to the media. (In an old project where I did not move the media's original location, I do not get the keyframe bug.)

I have found I can fix the bug if I replace the media. Unlinking and relinking does not work. Unfortunately, on the clips I've tested this on, the replaced media becomes offset by a frame or more. I have done so much rotoing and keyframe work in this massive project that this could really mess things up.

Does anyone know how I might replace my media while preserving effects, retimes and roto work? Or does anyone have an alternative suggestion to fix this extremely weird bug?

[Rohit Singhal]

Hello. Can you please send us a copy of your project which shows this issue?