It would be interesting to have the light groups denoised too:
I'm normally rendering interiors doing a huge exr with everything inside, 3 or 4 light groups (sun, night light, extra light on sofa/desk, something more... leds ecc...) and then manually compositing and tweak it adding lights.
Is it in the plan?
Thank you,
Rickyx
OpenImageDenoise
Re: OpenImageDenoise
Good idea, can be added in the future.
I made an issue for these ideas: https://github.com/LuxCoreRender/BlendL ... issues/241
I made an issue for these ideas: https://github.com/LuxCoreRender/BlendL ... issues/241
Re: OpenImageDenoise (RAM leaks?)
Sadly am short on time, tho i managed to do a bit of play-testing yesterday and got regular crashes on one of the larger scenes.
Thus i have no data gathered to support my experience, just a description:
While observing RAM consumption in Task Manager I noticed quite a large spike, once OIDN kicks in (tho lower than with BCD). That's when the crash occurred. After further inspection I found out that RAM builds up with each & every OIDN 'action' by a some amount (?), until crashing (took 3 renders, every 4th crashed).
I also noticed this denoiser quite softens the image.
Maybe it's nothing (designed behavior) or might just be an 'early' implementation.
I'm just wondering, if anyone else experienced similar issue or knows in detail how OIDN works?
Thus i have no data gathered to support my experience, just a description:
While observing RAM consumption in Task Manager I noticed quite a large spike, once OIDN kicks in (tho lower than with BCD). That's when the crash occurred. After further inspection I found out that RAM builds up with each & every OIDN 'action' by a some amount (?), until crashing (took 3 renders, every 4th crashed).
I also noticed this denoiser quite softens the image.
Maybe it's nothing (designed behavior) or might just be an 'early' implementation.
I'm just wondering, if anyone else experienced similar issue or knows in detail how OIDN works?
Re: OpenImageDenoise
I haven't noticed any softening, denoiser works great here on windows and linux too.
However regarding memory consumption:
I needed to denoise 5K image and once denoiser starts it fills up ram.
On windows it eventually finishes job anyway, but on linux it crashes blender. I don't know though if this can be handled better by denoiser itself.
However regarding memory consumption:
I needed to denoise 5K image and once denoiser starts it fills up ram.
On windows it eventually finishes job anyway, but on linux it crashes blender. I don't know though if this can be handled better by denoiser itself.
-
- Donor
- Posts: 790
- Joined: Thu Oct 04, 2018 6:06 am
Re: OpenImageDenoise (RAM leaks?)
Yes, noticed that too.
With a proper albedo map there is only minimal softening (when you inspect at 1:1) but it needs a little sharpening with very small radius like 0.1.
Without an albedo map it gets worse.
Especially when compared with the more aggressive detail reconstruction of the Cycles denoiser which does not need any sharpening.
Re: OpenImageDenoise
Me too I had a "painted look":
this is quite fine but in some cases sharp edges would be better (ex in the corner between walls and ceiling).
this is quite fine but in some cases sharp edges would be better (ex in the corner between walls and ceiling).
Re: OpenImageDenoise
Please show pictures and how many samples you rendered. More samples should improve the denoised result.
Re: OpenImageDenoise
It would be helpful if we had the autorefresh interval for the OIDN denoiser during final render when DENOISED PASS is selected.
Re: OpenImageDenoise
Thanks for the suggestion, with the quick denoising time of OIDN this actually makes sense, I added it to the issue linked above.
Re: OpenImageDenoise
Are there any settings for OIDN? To be able to adjust the radii and stuff, as in the usual bvd denoiser?