Thank you so much! I've been trying to do this for so long but never took the time to figure it out. This is perfect and now I can use the absolute values from CG depth passes. Your gizmo will be my go to for that now. Again thanks
Yes it should work fine in Nuke 13. The only thing that would need to be updated is support for Camera3 class nodes in the "Get Selected Camera" python script button.
Love this tutorial. But unfortunately I am ran into some issues. Soon as I set my focal length I am getting an error ""OpticalZDefocus._ZDEFOCUS_:Kernel not found in cache and source is missing" . Any idea why this happening ?
thank you for this. How can I install the OpticalZDefocus gizmo? i put it in the .nuke folder but didnt work. dragged it in but gives me error. im not a nuke pro so im sorry and i tried to look it up no luck
Hey Mo! Yeah I think the default dropHandler doesn't actually import .nk files, which is pretty dumb. A couple options - Make a folder named "ToolSets" in your .nuke folder. Any *.nk files you put in there will be available in the ToolSets menu in the node bar, and searchable in the tab menu. - Or copy the contents of the .nk file and paste it into your node graph. Turning the .nk toolset into a gizmo is a bit more complicated and probably not needed for your use-case. Hope that helps!
@@jedsmith thank you for your quick response. I followed ur instructions and tested but I think I need to fix my z Depth from RS or grade it better for better results. I was looking into how to turn that into gizmo and made me wonder why there isnt a gizmo version along side .nk version?
@@bensasi It's worth noting that it is very important that the z-depth is rendered with real-world scene-units as absolute distance from camera. Or pre-processed to be this before it goes into the OpticalZDefocus tool. Make sure the depth units are set accurately based on your scene-scale in the node, and that your camera geometry is set correctly on the node as well. If you do this, your dof results will be physically correct. If you don't, all bets are off. As for a gizmo version, feel free to do that yourself if you need that functionality. All you need to do is change the node class from Group to Gizmo : Change this line: Group { To this: Gizmo { and save it as a .gizmo file, then put it in your $NUKE_PATH somewhere. Best of luck!
@@jedsmith thank you thank you . I'm trying to use your script on renders from RS. I'm not importing cameras nor a 3D scene into nuke. and yes my maya scene is 1:1 real world units.
Fantastic overview and gizmo, thanks! Question though, doesn’t having a “max defocus” slider negate the whole point of simulating a real world lens, because depending on where that value is set, the amount of defocus at the maximum far defocus value can change dramatically. In theory, shouldn’t that value also be determined by a particular lens’ geometries (fstop, aperture size, focal length, and focal plane)? This becomes especially critical in close focus situations where defocussed areas can become very blurred. How do we determine what value to set that to to most closely simulate an actual lens?
Consider the max defocus value like a safety maximum. It's a safety to prevent coc sizes greater than the threshold you specify. If you use max defocus to control your defocus size, then absolutely you will not get physically correct results. The user should set the bokeh size with the aperture, just like with a real lens. If you're worried about it you can just set that to a very high value and remove it from the tool. You may get freezing and strange behavior though if the plugin comes in contact with a pixel that has a very small depth value.
Great video. Very useful. Thank you very much for your time and effort. One little suggestion to make better stuff is to practice your oratory skills. But still this is the best video on this subject I've ever seen.
Best thorough breakdown on DOF. Thanks so much. I see you haven't updated the channel. I hope you do more vids. This one was great.
Thanks for the feedback! I don't get spare time very often but I'll try to make more soon :)
Thank you so much! I've been trying to do this for so long but never took the time to figure it out. This is perfect and now I can use the absolute values from CG depth passes. Your gizmo will be my go to for that now. Again thanks
I swear I just find you in the most random places on the internet lol
@@InLightVFX haha hello Jacob! Glad to see you on this gem of a video x)!
Great Breakdown... much appreciated from anyone interested in this topic ;) Thank you
You sovled my problem...thanks man 'every artist must watch this video'
Good work, please continue, make this kind of tutorials. thank you so much.
19:36 Yeah, the bokeh is really cool! =)
Hi, I wanted to know if I can use this tool with nuke 13? It's really awesome
Yes it should work fine in Nuke 13. The only thing that would need to be updated is support for Camera3 class nodes in the "Get Selected Camera" python script button.
Love this tutorial. But unfortunately I am ran into some issues. Soon as I set my focal length I am getting an error ""OpticalZDefocus._ZDEFOCUS_:Kernel not found in cache and source is missing" . Any idea why this happening ?
is there any way to get right defocus edge on front and on the back of the object? can't find a way
This is really useful, thank you so much!
Thank you for this!
Very informative. Thank you
Absolutely amazing video. Fascinating subject, thx
Nice and helpful tutorial, thx Jed!!
Thanks ! dude really awesome tool you made !
Hey there!
What a nice tutorial, thank you so much! I have only one question which tool you're using to change the AOV passes right in the viewer?
Thanks! It's Falk Hoffman's Channel Hotbox
www.nukepedia.com/python/ui/channel-hotbox
This is 💎
thank you for this. How can I install the OpticalZDefocus gizmo? i put it in the .nuke folder but didnt work. dragged it in but gives me error. im not a nuke pro so im sorry and i tried to look it up no luck
Hey Mo! Yeah I think the default dropHandler doesn't actually import .nk files, which is pretty dumb. A couple options
- Make a folder named "ToolSets" in your .nuke folder. Any *.nk files you put in there will be available in the ToolSets menu in the node bar, and searchable in the tab menu.
- Or copy the contents of the .nk file and paste it into your node graph.
Turning the .nk toolset into a gizmo is a bit more complicated and probably not needed for your use-case.
Hope that helps!
@@jedsmith thank you for your quick response. I followed ur instructions and tested but I think I need to fix my z Depth from RS or grade it better for better results.
I was looking into how to turn that into gizmo and made me wonder why there isnt a gizmo version along side .nk version?
@@bensasi It's worth noting that it is very important that the z-depth is rendered with real-world scene-units as absolute distance from camera. Or pre-processed to be this before it goes into the OpticalZDefocus tool. Make sure the depth units are set accurately based on your scene-scale in the node, and that your camera geometry is set correctly on the node as well.
If you do this, your dof results will be physically correct. If you don't, all bets are off.
As for a gizmo version, feel free to do that yourself if you need that functionality. All you need to do is change the node class from Group to Gizmo :
Change this line:
Group {
To this:
Gizmo {
and save it as a .gizmo file, then put it in your $NUKE_PATH somewhere.
Best of luck!
@@jedsmith thank you thank you .
I'm trying to use your script on renders from RS. I'm not importing cameras nor a 3D scene into nuke.
and yes my maya scene is 1:1 real world units.
I'm also getting an Error: Kernel not found in cache and source is missing. :(
Fantastic overview and gizmo, thanks! Question though, doesn’t having a “max defocus” slider negate the whole point of simulating a real world lens, because depending on where that value is set, the amount of defocus at the maximum far defocus value can change dramatically. In theory, shouldn’t that value also be determined by a particular lens’ geometries (fstop, aperture size, focal length, and focal plane)? This becomes especially critical in close focus situations where defocussed areas can become very blurred. How do we determine what value to set that to to most closely simulate an actual lens?
Consider the max defocus value like a safety maximum. It's a safety to prevent coc sizes greater than the threshold you specify.
If you use max defocus to control your defocus size, then absolutely you will not get physically correct results. The user should set the bokeh size with the aperture, just like with a real lens.
If you're worried about it you can just set that to a very high value and remove it from the tool. You may get freezing and strange behavior though if the plugin comes in contact with a pixel that has a very small depth value.
Best teaching. Thank y-u so much
cool video , good job.! can i request? ( if u not busy ofcourse) the camera tracking tutorial?
Love it!!
nice vedio ,so i just wanna know that which plugin you have used to change the aov pass by a hotkey ,some cute little box ，during the vedio 。thanks ！！
😉👍thank you so much !!!
Thanks Man ! This is really useful :)
Thanks
Thanks. Nice tutorial! How did you change your rgba to depth by just using keyboard?
Great info, thanks for sharing!
Good Job Man !!
Great video. Very useful. Thank you very much for your time and effort. One little suggestion to make better stuff is to practice your oratory skills. But still this is the best video on this subject I've ever seen.
*he got pretty good by the end... He was ace by the time he was roto paiting bokehs! :D
thx!
谢谢
could you please make a tutorial in short ,for just 5-10 minutes,it should relates only to video composting, with minimum points
❤🔥 wow
Your clicky keyboard tho
very well explained, thx!