Intel Open Image Denoise released for 2.81

@Atair, did you use albedo and normal buffers for these images? It seems to me that you didn’t (there shouldn’t be such artifacts at object borders if a normal buffer is specified too). Or maybe there was some issue with them (e.g. aliasing). Either way, using such a trivial scene (which doesn’t even have textures!), and a single image, is hardly a good way to test final-frame rendering.

1 Like

as @marcoG_ita pointed out it looks like the LuxRender implementation i used was buggy - I guess its best to wait a bit for a proper release from them

Why wait? The denoiser is released as a fully functional tool on its own with its own reference implementation.

Is intel open denoicer feature available in latest builds.

Is it possible to integrate this with Blender?

FYI this is included in E-Cycles.

1 Like

E-Cycles and OIDN rocks indeed.

1 Like

For those who don’t want to convert images to / from PFM:
I added OpenEXR (.exr) support for the command-line-interface
and a pull request on GitHub accordingly.
There is no response so far, but you can build it yourself already.

3 Likes

Thank you. Is there any chance for prebuild binaries for ordinary people? :slight_smile:

1 Like

I mean with exr support

1 Like

I am using macOS so that is the only platform I have a binary (with OpenEXR support) for right now.

@skw hi, i’ve noticed in recent 2.79 nightly builds there are OIDN passes (AOVs) in the compositor, there is not the Denoise filter though.

Any ideas? Would be great to get OIDN in experimental builds

Denoising data is here since very long, it’s the passes from Lukas’s denoiser.

The OIDN patch is still in review, it has not been committed to master or the 2.79 branch.

LordOdin has provided a build.

Stefan(skw) made that build :sweat_smile:

@skw @bliblubli
That’s right, my bad. I thought denoising passes were part of the OIDN patch

Its OIDN not ODIN :stuck_out_tongue_closed_eyes:

Oops, thanks for the clarification.

OIDN, son of Intel

8 Likes