Indigo Renderer Forum

Hey there,

since I am very very happy with the new features, speed and quality of our beloved renderer, let's talk about features that would push Indigo more and more to a production proved product.

An old request here is, imho to be honest, simultaneous rendering and output of multipasses.
That would help a lot in a compositing workflow and will lower the inhibition level to use Indigo with animation, and in general.

I learned a lot of things from my last animation project; and one thing that consumpted quite some time was to set up all scenes (20+) for output beauty, matID and depth pass, which were needed to satisfy the client's wishes.

Considering production safety in a narrow production timeline, with corrections at the end, multipass output is a huge focus in a professional workflow.
You can do a lot with postwork without the need and time to render it again.
Especially animations.

So I would be very happy if Indigo provides me simultaneous multipass rendering.
Plus, a new and also important request for post production, a normal pass for adjusting light and shadows in post production.

Thank you in advance!


Cheers, zeiti

+1

+1

If it does not compromise the speed (much) that Indigo runs now than +1.
If yes...than +0.25

+1 with separate exr ouput for each pass.
Passes in indigo are rendered really fast, so maybe solution not to compromise speed (rendering passes forever) is to run them at the beginning or at the end of rendering process or set them separate timer or "samples" level.

... or with a limited set of threads; maybe single-threaded.
Of course without consumpting more RAM; maybe only when saving.


Cheers, zeiti

a thought...
https://github.com/Psyop/Cryptomatte
Could this be supported and ease the process?

burnin wrote:a thought...
https://github.com/Psyop/Cryptomatte
Could this be supported and ease the process?

Looks awesome! Let's go with this.

Eneen wrote:+1 with separate exr ouput for each pass.
Passes in indigo are rendered really fast, so maybe solution not to compromise speed (rendering passes forever) is to run them at the beginning or at the end of rendering process or set them separate timer or "samples" level.

I also think this might be the best approach

I'm curious about the other passes: why is there any noise in them at all? Surely a single sample of - say - a Material ID pass would yield the correct pixel color right away? Is it because of the sampling filter?