Blackmagic Forum

Hi guys,

as you can tell, I'm new to Davinci Resolve.

My problem is:
- I have a white background (Solid Color, Composite mode: normal)
- I have a logo which is mainly white too (.jpg, not transparent, Composite mode: normal or multiply, same result)
- Stacking them to create sort of an introscreen creates an black one-pixel-wide frame around the logo.
- The frame shows in video playback and after rendering.
Adressing the obvious: the logo-picture has no frame in it. It is white at all 4 edges


What I want:
- I want a seamsless transition between the logo and the background, which are the same white color. The edge of the logo should be invisible.

Did some of you experience the same issue? Has someone a solution or an idea what could cause the problem and what could fix it?

After a lot of web research, I'm still pretty clueless. Please help me change that.
Thank you very much.

Johannes

I've also had this issue. I haven't tested it with the latest release, but noticed it around the same time I was having all the issues with png scaling mentioned in another thread.

If I get a moment I'll have a test again. Have you tried different scaling filter options to see if it improves depending on those settings?

By try and error, I have found a quick and dirty solve for the issue.

By cropping the edges a little (2.000), the frame disappears.
Quick, yes. But dirty because I lost a bit of image information.

Extending the image in advance with some white boarder should do the trick here.

This might be the least "best practise" way to do it, but in my case, it worked.

I seem to remember my issue was with a few transparent PNGs layered together on a white background (using the color generator) within DR, then that was made into a compound clip to allow me to scale everything within the scene equally. The compound clip was then put on top of another white background generator, which was when the black box appeared. Not 100% sure on that though. Will try and recreate and see if that was the setup.

I'm seeing the same here in Studio 17.1 for Windows.

I would consider this a bug.