PxF_VectorEdgeBlur
HTML-код
- Опубликовано: 30 янв 2023
- A newer version of PxF_VectorEdgeBlur is available. See this video:
• PxF_VectorEdgeBlur 2.0
This Nuke gizmo is part of the Pixelfudger suite available here:
www.pixelfudger.com
www.nukepedia.com/gizmos/filt...
You can find more videos about Pixelfudger gizmos (including installation instructions) here:
• Pixelfudger Nuke Gizmos
About the Author:
Pixelfudger gizmos are created by Xavier Bourque
/ xbourque 
Кино
I wish all Canadian compositors knew their shit as much as you do, Xavier... great tool and tutorial, thank you!
I am using your tools since 2016 Thank you
WONDERFUL
nice one
I was usually using the normal motion blur then overlay the key over the one with motionbur
this will save me a lot of time!
thank you!
Glad it helped!
great
brother may you please give motion blur practice plate
I cant find the source of this exact plate but you can find lots of practice footage on pexels.com
www.pexels.com/search/videos/basketball/
Need to footage link for practice please sent the footage link.
I can't find the exact clip but I think this is stock footage from pexels.com.
It's throwing me this error - C:/Users/joshm/.nuke/gizmos/PxF_VectorEdgeBlur.gizmo:
PxF_VectorEdgeBlur7.Viewer1.monitorOutOutputTransform: Bad value for monitorOutOutputTransform : rec709
Working in ACES - any idea on how to fix this?
Looks like I left a Viewer node in the group... As a quick fix you can open the PxF_VectorEdgeBlur with Ctrl+Enter, find the Viewer1 node and delete it.
Are you getting the error on startup or when trying to use the gizmo?
@@pixelfudger Hi! So it still works - it just dumps the nodes at the top of your node tree after the error (Bloody good node btw! Thank you).
But yes removing the viewer node worked with removing the error!
Thanks man.
@@pixelfudger I had the same error(obviously ) and deleted the viewer nodes lines from the python file, now there is "blank error message '' window popping up but I don't think it will affect the node's performance. I just downloaded it because I was looking for a solution for a hard roto. Thanks a lot!
I just updated Pixelfudger to version 3.1 and removed all the stray Viewer nodes that were left in various PxF groups (including PxF_VectorEdgeBlur)... this should take care of your problem. You can download the update on pixelfudger.com or on Nukepedia.