DaVinci Resolve 17 adds border to overlay

Screenshot of border from rendered video

DaVinci Resolve 17 Added border to overlay.jpg (458.53 KiB) Viewed 1410 times

Hello,

My wife records PowerPoint Zoom lectures for the bioethics courses she is teaching. I have been using DaVinci Resolve 16 to do some basic editing of her videos for about a year (trimming the end, splicing two takes together if her internet connection zonks out in the middle of recording). I am not a power user by any means. Most of what I know how to do is pretty simple.

I run DaVinci Resolve under Windows 10, with 24 GB of RAM, and render the videos at 1280 x 720, 25 frames per second, MP4. When she finds something on a PowerPoint slide that she wants to change after she has recorded the video, I redo that slide in PowerPoint, and then screen capture part of the new slide as a JPG image. Then, I simply drop the JPG on "Video 2," move it and scale it to fit the area on the video, and in Resolve 16 it always blended in beautifully, covering the old text with the new text with no blemishes of any kind. We couldn't even tell it had been edited.

Recently, I updated to Resolve 17, build 39. Yesterday I changed a PowerPoint slide and used the exact same methods that I had done in Resolve 16 several times (always completely successfully). When I dropped the JPG (let's call it an overlay) into the Video 2 slot, I noticed a thin black border around the overlay (that never happened in Resolve 16). There is definitely no black border in the JPG itself. As I was adjusting the timing of the overlay to exactly fit the display of the slide, I was previewing and the black border seemed to disappear in the upper right "preview" window, so I thought that I was going to be OK. However, the border did appear in the final, rendered video (see screenshot).

Does anyone know what is causing this in Resolve 17 and what I can do to fix the situation so that a border does not appear around the overlay?

If the solution turns out to be to upgrade to 17.1, do I need to uninstall first (I don't have anything important in any Resolve database) or will it update successfully without uninstalling (I uninstalled 16 completely before switching to 17)?

By the way, my computer is about five years old (i5-4570 CPU with NVIDIA GeForce GT 755M GPU). I don't do enough work in Resolve to mind too much if rendering takes longer, but my impression is that rendering is taking longer in 17 than it did in 16. Does 17 "require" more resources and will just take longer on my old computer or is there a setting that I don't have correct that may be affecting my speed.

I don't mind going back to 16 if that is the solution. I am sure that I don't really use any of the latest and greatest features.

Thank you for any help in solving this.

There was indeed a problem with overlays in 17.0. Upgrading to 17.1 solved the issue I was having. I did uninstall 17.0 first, but I couldn't say whether you have to between those two versions. It certainly wasn't a problem. Resolve remembered all of its settings and reloaded the database.

There are a couple of workarounds, but you would be best served by upgrading to see if that solves your issue first.

Thank you for responding Bruce.

I took your advice and upgraded to 17.1, build 24 by uninstalling first.

At this point, the overlay is behaving the same way in 17.1. When the video is stopped with the cursor over a section where the overlay occurs, the black border can be seen in the upper-right preview window. When the video is playing with Resolve, the black border disappears from the upper right preview window. I tested a short render by setting in/out marks and the border is still there in the rendered video. Any other suggestions at this point?

What's the TL;DR Lawrence?

This seems to be a remnant of an old alpha issue that was mostly fixed in a previous version. If you switch to the Fusion Page, and just drag and move the MediaIn node a little and switch back. I think that should fix your issue.

Thank you very much, Eric. Going to the Fusion Page and moving the MediaIn node does solve the problem.