Bake node for Compositor
When you are editing nodes in the Compositor, you have to wait for it to calculate all the nodes before seeing the result, make a small adjustment to one of the final nodes and you have to wait to calculate everything, sometimes it takes longer to wait for these calculations than editing the nodes.
One solution would be a Bake, Proxy or Cache node.
Like the Bake node in the Geometry Nodes, a Bake node would be necessary for the Compositor Editor to set a series of already calculated nodes.
This could be saving or exporting an image as a Proxy, or storing data in a file, internal or external, I really can't say the best solution. In the image I have put some examples at the same time.
This would save a lot of time when editing in the Compositor, since you wouldn't have to keep calculating all the nodes every time you make a small adjustment.
3 Comments
I thought it would be nice to have it in the shader editor as well.
Proxies could be implemented with a switch node, but having a cached compositor would be ideal. Get compositing performance closer to Nuke's.
Caching was added in version 5.3, but this still doesn't solve the problem, as the cache is cleared whenever any modification is made. Could a cache-saving node be implemented? Or perhaps a group cache? At this point, I’m not sure which option would be best, as I don't know exactly how the cache handles performance optimization—which is, after all, the goal: improving workflow performance. I’m also unaware if there is another discussion thread regarding this development.