Power Window/In Out offset by 2 frames after upgrade

Window 10, 32GB ram, GTX 1070, Davinci Resolve Studio

Hi,

I am reporting a potential bug after I upgraded from 15.3.1 to 16.1.

The issue:

This is a little hard to explain so please bear with me: The project started in 15.3.1. After completing the project, I upgraded to the next version 16.0. Obviously the database was upgraded as well. The clip's in/out points were fine, as well as the Power Window's positions. All was well in 16.0.

I then updated to 16.1. Then, clips within a compound clip, within their own timelines, and have Power Windows seem to have shifted the 'out point' of said clips by 2 frames. The 'in' point seems fine. Also, the Power Windows shifted or changed (probably adapting to the new frames). So now the Power Window is offset and masking the wrong areas. I also noticed the pure "blue" (green 0, red 0 and Blue 255) were looking more purple than blue.

See attached.

I realize you will have a hard time understanding this issue but I upgraded/updated all the way to 17.1 and the issue is still there so I don't think it's been discovered.

To reproduce:
- start in 15.3.1
- add an MP4 clip (no idea if it has to be MP4 but that's what I use) and convert it to a compound clip (mine was about 2 seconds long)
- in Color, add a couple of power windows to mask out an area (my masks were animated)
- upgrade to 16.1
- observe the masks are now offset and the clip's 'out' point has changed

Anyway, I am mostly wondering if you can repro this or are aware of it because it means I have to redo my entire project if there is no fix...

Thanks.

p.s. After this post, I uninstalled version 16.1 and installed 16.0 and the clips/power windows (or whatever is causing the frame offsetting issue) is gone and the clips/power windows are back in their proper place. Hopefully this helps a little more...

Let me know if you need more info (I'm sure you do) or if you can actually reproduce this.

Thanks again...

Given that we're up to 17.1, it's unlikely you'll see a fix in any version of 16.

I would recommend updating to 17.1 and testing that.

Standard backup protocols apply, as always.