Hello,
The denoiser is just great, works very welll, but needs a lot of extra channels.
Would it be possible to have the option to save the denoised image directly in the RGB channel (which it can now), but not save all the extra-channels needed afterwards ?
It would save some HD space (images are 3x bigger on some tests)
And, is it possible to have DR calculate the denoiser ?
Thanks
Yes, this came up before; I can do it, but you won’t be able to re-denoise the image, if it is needed for whatever reason.
And, is it possible to have DR calculate the denoiser?You mean to distribute the denoiser calculations across many machines? It is not impossible, but it might be easier just to get a good GPU.
Best regards,
Vlado
Hello Vlado,
Well, the way i see it for most of my scenes, usually once the denoise setup is OK, i won’t touch it afterwards (i use mainly the “mild” setup which is quite enough for the small noise). So not saving another extra 100mb per image would be great.
I could get some more powerfull CPU or better GPU (planned, just need to find out the right config), but in the meantime if it could be done (maybe on the fly in each DR bucket?) and use all the DR nodes, it would be great!
Thanks anyway for the denoiser, works amazingly well !
Are you aware that you can save just the denoised layer from the VFB?
Yeah, but when u batch render or do animations…
one shuffle and one save node?
Yeah of course, that’s not the problem.
just HD space 50mb/file > 150 mb/file 
Oh, i hear you, that’s why i kept thinking “post process”: upon conversion, delete and recover the -anyway overly cheap today- disk space.
The thing is, do we really want ANOTHER save option in the VFB/render settings?
For each user which wants one more checkbox, there’s at least one which wants one less.
Which has a sort of beautiful, universal law-like balance, but makes the choice, and allocation of resources, more difficult.
Why ANOTHER save option in the VFB/render settings?
What about the VrayDenoise only using the layers internally without saving them out into the EXRs?
Yes, that’s probably what we’ll do…
Best regards,
Vlado
I mean the option to overwrite the RGB with the denoised is there, and nothing stops you from saving from the max output an RGB-only version of your image in any of the Max supported formats, AND a split version of your layers, WHILE saving out or not the full set of layers as EXR or VRIMG.
You want to have the purpose-built, layered EXR format to behave exclusively like a PNG one, and you make it V-Ray’s task to allow for it through an option.
It’s mighty fine as it is for it already does what you wish it to.
If you can’t make max do what you wish with three concurrent outputs, i doubt the one option will make your life better in the long run.
But maybe Vlado’ll see benefits to coding such an approach: this is my very personal opinion.
And I wanna save denoised version with flares 
Yes, will fix that.
Best regards,
Vlado
That’s a good idea - I would be happy with that, too.
I’m digging all these suggestions. Already I’m committing the mild denoise as part of my process. And since almost all my work is batch rendered on the farm with DR - I don’t get to do any denoise tweaking besides what I do initially at my workstation. Agree with all the points about ways to reduce the filesize yet maintain the denoising.
If I kept the passes - it would help me at least if there was a Nuke gizmo that let me pipe in the passes and tweak the level of denoise at that point. But without the other channels denoised it would be a problem.