CUT Page behaviour has changed with DR Studio 17.1.1 Build 9

I recently updated DaVinci Resolve Studio 17.1.1 to Build 9 and suddenly the CUT Page behaviour has changed - for the worse! - from previous builds.

First 'change': The ripple delete functionality when using the Speed Editor no longer ripple deletes only the clip where the playhead is located...it ripple deletes all the clips from the playhead point to the beginning of the timeline.

Second 'change': When I have a timeline based on Camera 1 then go to the Sync Bin to add/replace a clip using Camera 2, it places it randomly along the timeline...where it is no longer in sync with Camera 1. It's actually the correct clip - it's just being placed in the wrong place! This is beyond infuriating since this is one of the main reason the CUT page exists in the first place and the feature that most enticed me to buy the bloody Speed Editor...which is now slowing me down while I figure out how to make it work!!

Breath...

Is there anyone else that is experiencing these new 'features' on the CUT page and, more importantly, that has figured out the tweaks or settings changes required to return the previous (desired) behaviour.

Thanks for any assistance you can provide.

At least one of these sounds like a bug.

First 'change': The ripple delete functionality when using the Speed Editor no longer ripple deletes only the clip where the playhead is located...it ripple deletes all the clips from the playhead point to the beginning of the timeline.

I also experienced this frustrating issue once. I wasn't able to reproduce it again after reloading the same project a few days later ( and after a few system reboots).

Are you able to replicate the issue after a whole system restart?

After trying a DR restart and a system restart - all to no avail - I completely uninstalled DR, re-downloaded the latest version and re-installed it. The CUT page now seems to function as expected.

Interestingly, this experience and the workarounds that I was trying to deal with it, has made me realise that the CUT page is actually a high-functioning 'linear editor'. It's NLE capabilities are pretty limited. When I want to utilise non-linear functionality, I almost always go to the EDIT page (e.g., move a clip to another point in the timeline).

This isn't related to the issue at hand, but...just sayin'...

At any rate, the learning is that when strange behaviour manifests itself, the time-honoured advice of unplug and re-start is still the best course of action.