Cross dissolve at begin/end of clip with RCM in 17b4

I'm still having this issue even with 17b4. I saw it first in B1 and I'm surprised it hasn't been addressed yet.

If I want to fade up the beginning of a timeline I add a cross dissolve transition to the first clip in the timeline. If the new 17 version of RCM is being used the cross dissolve at the start does not start at black or nearly black (0% opacity), despite what the inspector says for the transition curve.

Comparing the cross dissolve transition to just an opacity keyframing, it seems the cross dissolve starts at around 2% (29.97fps timeline, 30 frame transition).

Switching to non-color managed, the transition works appropriately.

I can confirm this with 17 b4 on Windows 10 20H2.

RCM - Resolve YRGB Color Science

Still not addressed in b5

Check it out in b6 - looks like it's fixed... can anyone confirm?

I'm still seeing it with 17b6 if RCM is on.

What I am seeing now (in 17b6) is that the very first frame of the clip is black (which is wasn't in 17b5 and earlier), however, stepping one frame forward in the clip suddenly shows an unexpectedly high opacity (this is using the fader handles on the clip, not a video transition).

Without RCM, I need to advance several frames in for the same clip before I see any noticeable increase in opacity. I don't understand this behavior - as you observed, it does seem wrong.

Add - With a 'Cross Dissolve' transition, I'm not seeing this odd behavior - Can you provide a bit more detail as to what looks wrong with a cross dissolve? Thx.

With a cross dissolve between two completely different clips the behavior is very similar. The incoming clip has a higher opacity in the first frame or two then should be expected.