Delay Time Compositer Node
This would be a compositer node which would delay the current frame by a specified amount.
Why: I've been interested in auto exposure or eye adaptation which video games use for realistic exposure shifts and I checked out blender posts trying to achieve the same effect. Main issue seemed to always be that there is no way to actually delay the exposure while staying realtime so no keyframe/video baking. Some would resort to python code which would not update during render time so it would just be a viewport effect. So this node would be like a stutter type effect which would delay the current frame by a specified amount and you could also ideally choose how to jump to the next frame via 3 interpolation options: constant linear or bezier.
devtalk.blender.org/t/autoexposure-for-the-viewport/6829
reddit.com/r/blenderhelp/comments/1ljbacd/auto_exposure_in_blender_compositor_realtime_only/
pedroplopes.itch.io/autoexposure
ui and naming is crued. Other names could be Delay: scene,frame,view, but this is a actual screen space effect not a image texture only node so the name would have to reflect that so it doesn't get confused with the retime node. Alternatively this could be part of the already existing exposure node and just add in a eye adaption option.
1 Comment
I was thinking simulation zones in compositor would be great, especially because it would be a more "logical" way (in blender's overall node logic, considering simulation zones already exists) to do a similar effect like the exposure node. I'm thinking for example you could evaluate the overall brightness of an image overtime and softly adjust the exposure compared to the brightness value from the previous frame inside in the simulation zone.
The way I'm saying it is a bit confusing, but I believe your node proposal seems a bit complex, because compositor nodes in blender usually just do an operation on the image, it can't really know what's before and after in the timeline. I'm not denying how cool this could be of course, but I'm just not quite sure how it could be implemented with a proper design. That's why I mentionned another feature that could work for auto-exposure, yet it's not the same thing as a retime node