Blackmagic Forum

Hello everyone,

I have noticed a very strange behaviour of the programme which I assume is a bug. When importing rasterized graphics with transparent background (such as .png or .tif) into the timeline, the edges look very jagged. It becomes even worse when I use the graphics in a Fusion composition. And it's not just graphics but also text added within Fusion that looks like that.

After lots of trial and error I noticed that the culprit seems to be Resolve Color Management with Davinci Wide Gamut, which I was using for this project. As soon as I switched to Davinci YRGB my graphics looked normal again.

Unfortunately, turning on "Bypass color management" on either the Fusion comp or the graphics themselves doesn't have any effect at all.

So my question is: Am I doing something wrong or is this an actual bug? Because as of now RCM in Resolve 17 is basically unusable for me for this reason alone.

Some additional info on my case:

- I am using Resolve 17.1 Public Beta Build 15 on an Apple M1 Mac Mini with 16GB RAM
- I tried all alpha modes (straight, premultiplied) on my graphics and nothing helps
- When using sRGB as the input color space of my graphics, they look fine by themselves on the timeline, but when I use them in a Fusion Comp it looks horrible.
- It is not only a display issue within Resolve, when rendering the video with the graphics it looks just as bad.

This is what my graphic looks like inside a Fusion Comp on the timeline, the upper one with RCM Davinci Wide Gamut, Output Color Space Rec709 2.4 and the lower one without RCM (Standard Davinci YRGB)

Beta 9 is reported to correct these issue. Try that, report back.

You mean an earlier Beta version of Resolve 17.1 than the current one (build 15)? I don't see how an earlier version would be performing better than the latest one

Beta 9 is actually Build 33.

Oh really? Good to know! However the lastest version I found on the BM website in the support center is build 18 and when checking for updates it says i am on the latest version.

Could you please share where I can get build 33? I am using Resolve Studio btw, in case that's important

I found another bug in RCM 17.1 and I'd rather post it here than in a new thread: I was reviewing a clip, when, I noticed a sudden change in colors, mid-clip, with no aparent reason. I thought I had inadvertently introduced a key frame somewhere but after disabling all nodes the error persisted. I then bypassed RCM and it was gone. Does anybody have an idea what is this all about? That's on a windows PC.

You're the first I've seen report that, Antonis.

What RCM settings?

It is the new "Auto" RCM from the project settings. The footage is BRAW from a pocket 4K transformed to Rec709 gamma 1.4. It's the default option in the new RCM. The clip is rather long, more than one minute but the error appears just a few seconds from the start. The change in colors is not exceedingly obvious but it is serious. I think it appeared after I first graded the clip, or else I would have (probably) noticed it immediately. To fix it I had to bypass the RCM for the clip and emulate it's operation manually as much as I could.

Try changing the Preset to Davinci Wide Gamut. Report back.

The problem persists

Alright.

Any chance you can share the problem clip for testing on other systems?

please send me the contact

Huh?

OK, no need to send anything. The issue is related to the project RCM and goes away with the OFX version. I checked the entire show, and the problem apear in many clips. The new RCM is not fit for use. If you work in BM I think you should check it out, this is a major bug.