Please edit the denoiser to remove denoising layers after the denoiser has done it's job.

[JD3D_CGI]

I mentioned this in the main forum already - but I want to make this point again.

When I process hundreds of large EXRs and de-noise them - there's no reason to keep ~10 layers of de-noising data on an already de-noised file.

Please remove these layers after de-noising.

Also, better compression options after de-noising would be nice.

These EXR sequences are getting huge.

[JonasNöll]

I think the idea with keeping the denoising data in the EXR is that you can do denoising also in Nuke based on the data stored in those layers. But I agree that an option to chose if you want to store those would be nice!

[JD3D_CGI]

Just to be clear - I mean the denoising layers in the files that have already been denoised.

I don't mean the actual rendered EXR files, I mean the EXR files that have already bee denoised.

[JonasNöll]

Maybe I misunderstand again, but the denoising is only applied to the RGB_color and not to the individual elements. So if you combine the different elements from the multichannel EXR in Nuke the result would contain noise. But with the additional renderelements from the denoiser you can then afterwards denoise them in Nuke again. Or do I missunderstand again?

[JD3D_CGI]

In order to generate information for the denoiser, Vray will write several layers into the EXR so the standalone denoiser can use all of those layers to accurately denoise the image. Those layers are render elements specific to the denoiser.

Once the standalone denoiser has done it's job, those layers are no longer necessary.

I am saying that frames that have been outputted from the denoiser no longer need those layers, and they should be removed to save space.

[JonasNöll]

Does the standalone denoiser also denoise the render elements such as lighting, gi, specular, etc.? If it doesn't then those denoise related elements are possibly needed down the line for example in Nuke for denoising the assembled layered image
But I would advocate to add an option to simply let the user decide if those are needed

[JD3D_CGI]

If the denoiser isn't denoising then I don't know what it's doing.

Presumably if you are denoising in Nuke, then you'd be doing it all at the same time, not producing an entire separate frame sequence of denoisied images, only for you to manually denoise some later. It seems absurd.

[JonasNöll]

It's pretty common practice. Nobody for example in a VFX compositing environment workflow will care about your denoised RGBcolor. It's merely for you as artist to preview the denoised result.
For compositing you EITHER pass them already denoised renderelments OR you enable them to do the denoising by themselves using the data stored in the render elements so that they can handle that part by themselves.
In your case you will pass them a denoised RGBcolor (which they don't use) with un-denoised AOVs which they also won't be able to denoise by themselves because the data elements are missing if you remove that.

[JD3D_CGI]

OK, then it's likely you never use the denoiser and none of this applies to you.

Not everyone is sending work to a compositing team, some of us are just freelancers and small teams.

[JonasNöll]

Alright, I think my missunderstanding is that you only seem to be referring to the standalone denoiser. Which you are correct: I never use
Anyway a simple option to keep or remove would satisfy everyones needs and workflows.

[vlado]

So does the original request only apply to the standalone denoiser? I didn't quite understand what exactly is needed.

Best regards,
Vlado

[JonasNöll]

I think the request ist that AFTER the Standalone Denoiser was executed the automatically generated passes from the denoiser are removed from the multi channel exr in order to reduce file size. (I would keep it optional though)
Oh, and additionally is there an option when splitting out separate channels (instead of multichannel exr) to also save those passes? Somehow it only saves the denoised image in the RGBcolor but doesn't save out the the helper layers (noiseAmount, WordPos, etc.)

[JD3D_CGI]

Hopefully this (over) explains what I mean.

Basically, once the standalone denoiser has generated it's output files, we no longer need to have the denoiser elements in the files.

On large HD and 4k animations, all that data really adds up and there's no need to be so

wasteful.

[vlado]

Ok, that makes it clear, thanks a lot! Will see what can be done about that.

Best regards,
Vlado