Page 1 of 1

AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 1:09 pm
by hipur66
I have one specific node tree that is giving me issues when rendering the final export. Here is it below.
Screenshot 2025-05-13 093943.png
Screenshot 2025-05-13 093943.png (66.79 KiB) Viewed 764 times


The effects using AI Depth Map's alpha input are lagging on the final render. Preview inside DR is flawless.
I've exported in both H265 and ProRes to double check and it still persists. H265 using NVIDIA, native and Intel Quick Sync renderers.

Below is the issue on the same frame. Left is exported ProRes file playing in PotPlayer and right is DR viewer with node tree next to it. I've tried playing on VLC, iPad and Samsung S23 Ultra, still the same issue.
Screenshot 2025-05-13 094644.png
Side by side
Screenshot 2025-05-13 094644.png (626.17 KiB) Viewed 764 times


Any suggestions on how to fix this?
I'm rendering on a computer running W11 24H2 Build 26120.3964, RTX 4070 NVIDIA Studio Driver 576.02, i9-13900H, 48gb RAM. DaVinci Resolve Studio v.20 Beta 3.

Re: AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 1:21 pm
by akcivan
Yes, i do live that same issue. I've decided to not use that effect on moving objects :lol:

Re: AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 2:46 pm
by Jim Simon
I've used the Magic Mask combined with Defocus Background to excellent result. Maybe try that approach?

Re: AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 3:46 pm
by akcivan
Jim Simon wrote:I've used the Magic Mask combined with Defocus Background to excellent result. Maybe try that approach?


That is different stuff bro. Of course we have lots of solutions to replicate what we need to do but depth map is very useful for most of works instead of MM.

Especially feature films, MM needs to re-track for each scene, But on depth map you can just copy-paste it for same result. Huge time gain

Re: AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 3:47 pm
by Jim Simon
akcivan wrote:depth map is very useful...
When it works. ;)

Re: AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 5:53 pm
by hipur66
akcivan wrote:Yes, i do live that same issue. I've decided to not use that effect on moving objects :lol:

Oh no. And I was believing it was something related to my setup not being able to render it in real time. But yours is way better and still lags.

Re: AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 5:57 pm
by hipur66
Jim Simon wrote:I've used the Magic Mask combined with Defocus Background to excellent result. Maybe try that approach?

I guess that's my only option for now.

Or maybe render the Depth Map Alpha as a matte and apply that render to the clip? Not sure if that approach makes sense.

Re: AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 7:05 pm
by hipur66
I followed what was suggested in this thread:
https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=172442

Moved the Depth Map and related nodes to the end of the tree (after CST) and it rendered correctly.
Here's the updated node tree for reference. The compound node has the ones that I moved.
Screenshot 2025-05-13 160133.png
Node Tree
Screenshot 2025-05-13 160133.png (46.06 KiB) Viewed 348 times

Re: AI Depth Map node exports with frame delay

PostPosted: Tue May 13, 2025 10:53 pm
by akcivan
hipur66 wrote:I followed what was suggested in this thread:
https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=172442

Moved the Depth Map and related nodes to the end of the tree (after CST) and it rendered correctly.
Here's the updated node tree for reference. The compound node has the ones that I moved.
Screenshot 2025-05-13 160133.png


Hmm, gonna try that. Yeap, btw. It doesn't related to hardware power, its just bugging that frames :)

same issue appears on magic mask with neat denoiser too, when neat denoise is up. Magic mask also glitching frames just like "depth map" does. I really dont know who is responsible for that becoz Resolve's native denoise doesn't make that glitch either.