Node tree for a 'simple' AI sky replace that turned into 31 nodes (annotated)

by @hanaleepro in c/vfx-breakdowns · · Node Tree

Node tree for a 'simple' AI sky replace that turned into 31 nodes (annotated)
Posted the full annotated Nuke script screenshot. What should've been a Keyer->Merge turned into roto, a horizon-line relight, a reflection pass on the wet road, and temporal denoise because the AI plate shimmered. 'Simple' sky replace.
github.com

Posted the full annotated Nuke script screenshot. What should've been a Keyer->Merge turned into roto, a horizon-line relight, a reflection pass on the wet road, and temporal denoise because the AI plate shimmered. 'Simple' sky replace.

104 points · 7 comments

Comments

  • @ravisuzuki_films158 · · 100 points

    31 nodes for a sky replace is honestly restrained once you add the horizon relight. The ground has to KNOW the sky changed or it floats.

  • @rileynguyencreative · · 80 points

    this. 90% of bad sky replaces are a perfect sky over ground that's still lit for the old sky. the relight pass is non-negotiable.

  • @avahoffmann_films · · 55 points

    that temporal denoise node tucked in the corner doing the lord's work on the AI shimmer

  • @dianapark_vfx5446 · · 69 points

    beautiful script. readable. labeled backdrops. you're a better person than me, my scripts look like a crime scene.

  • @kaiharris · · 48 points

    labeled backdrops are self-care. future-you is a client too.

  • @henryharris_ai · · 24 points

    Technical Q since you've clearly done this - do you denoise the AI plate before or after the sky merge?

  • @charlotteschneider_fx · · 40 points

    Before. Always before. Denoise the dirty element in isolation, THEN comp. Denoising after the merge smears your clean sky too.