Compositor Camera Node
With the announcement eevee will eventually support real-time compositing, there should be an easier way to get different compositing results depending on which camera you are looking through.
Why this matters: Different cameras can have different clipping distances which affects the depth pass, which, in turn, affects things like adding depth of field and atmospheric perspective. You also might want different motion blur settings for different shots using the vector motion blur node. You might even want to fine tune different shots' lighting in the compositor.
Current work-around: Right now this is possible, although cumbersome, for post compositing, by setting keyframes at the same times as camera markers. This node is something that would make this faster and require less cross-referencing. I do not know of a work around for this once the real-time compositor is implemented.
UI Idea, This would be an input node. You would select a camera from a drop down with the different cameras in the blend document as options within the node. The node would output a boolean (a gray string type either 0 or 1) depending on if that camera is being used.
Limitations: You would have to composite in the same blend document as the one you rendered from. Or a copy.
Further thought: With the real time compositor you would also need a parameter on the node for if you aren't looking through a camera and just looking through the viewport. This could perhaps be a check-mark labeled "viewport" which would gray out the camera selector dropdown. This is just a starting UI idea. It could use some fine tuning. I realize it may be months/ years before we have the eevee real-time compositor and this additional parameter would have a reason to be added.
1 Comment
Been just assuming that this real time compositor would be on the camera object as these "camera nodes". But yeah, if its just compositor tree then some scheme for the active camera would be cool