Compositor Python Script Nodes
... even if disabled by default, even if they're slow, it'd be great to be able to embed a custom Python defined node in the compositor that would be called with the inputs and would return the outputs of a calculation; hopefully passed as numpy arrays.
It would be used to do low level manipulation on the images and other channels as part of rendering an image.
In the spirit of, github.com/bitsawer/blender-custom-nodes
and perhaps with an API similar to, docs.blender.org/manual/en/2.79/render/cycles/nodes/types/script.html
I, for example, have a workflow where I use 3rd party libraries to process rendered frames (cv2,etc) and now have this super horrible workflow where I render the animation sub-products (images, depth maps, etc) and the I have to batch process them on VSE with custom scripts to be able to user the f-curves etc. A nightmare!
2 Comments
Unfortunately, even with numby executing on the gpu, the data exchange from cpu to gpu will be a significant slowdown for performant shading. For shading, embedding some kind of GLSL into a text language node would be excellent for custom nodes. For compositing, a python exchange seems plausible, since most image, open cv, ai apis are mainstream for python, and shading efficiency is not that important or available anyway.
why is this still not implemented, I want this desperately! it would open so many doors.