Run compositor even on prematurely ended renders (such as progressive)
Currently it seems that if you cancel/end a render prematurely it prevents the compositor from running. This is especially annoying when doing an endless progressive render where you consider the image finished even if Blender doesn't.
The usually suggested workaround is to manually save the partially rendered file in EXR format and then invoke the compositing process in another scene or .blend to read the EXR and do whatever to it.
What if there was a checkbox in the Post Processing Render Properties like "Always run post processes [X]" that would tell Blender to always invoke the compositor / sequencer even when a render is cancelled?
4 Comments
I am of two minds here... How could you work on an "not final" image. I have always thought of compositing as more of a "final step" where you have the quality you want then you dress it up with effects, color correction, etc.
However I do like the flexibility and I guess it would give you a chance to do a pre-setup so I up-voted it. Sometimes I just can't make up my minds:)
* @Eric * The primary reason is when using progressive refinement mode in Cycles, where the render will never be "finished", so you have to terminate it when it reaches a level of quality that you're satisfied with.
Today you have to manually save the image and feed it to a separate compositing operation to get your final output. This option would say to just take whatever's there when the render is ended and run it through the comp. Even with tile-based rendering, you might have it half-finished and be interested in seeing the result of the comp rather than just the raw render.
* @gbs * good point.
ATM i made so (for static): export to EXR, second scene only for processing, input from EXR. So render button works only for postprocess