Intel denoiser - visible seam

[lollolo]

Hi

I'm not sure if you are aware of this issue, I don't even know if this is a corona thing or a limitation of the denoiser.
I noticed last summer already, that Intel denoiser leaves a visible seam in the middle of the image. (to be more precise, a few pixels to the right, see example)

To give you some information: I rendered the image two times.
At 3240 X 2160 gives the result I expect. When I try it with something higher than that, then I get always a visible seam. Happens in all scenes, every time.

Version: 7.0 daily Jan 22 2021
Cinema version: R20.059 CINEMA 4D Studio
Win 10

Thanks for bug hunting :)

[TomG]

Not seeing that happening here, same daily, using R23.

Are you perhaps running out of RAM? How much do you have, is there a low memory warning, are you rendering any MultiPass elements (e.g. LightMix, or others)? May be best if you send in a scene where it is happening for you, so we can be sure to be testing the same scenario.

Also, what happens if you use the Corona denoiser instead?

[TomG]

I rendered at 19506 x 13000 to make it run low on RAM during Intel Denoising, but still no seam.

[lollolo]

Thank you for your reply.

I don't think it is a RAM issue, I don't get a warning, and I'm not running out of RAM. (around 50 GB not used)
Corona and NVIDIA denoiser are working fine, only Intel denoiser is affected by this issue. Multipass isn't activated in this scene.

Can you check it on R20 as well? Or could it be that something Intel denoiser needs  isn't updated correctly on my system? Is there a way to check this?

Successfully uploaded as 1613032026_Issue-IntelD.zip

[mmarcotic]

Hello,

not in your scene and not in any of mine i get this intel line, not even in R20..

Can't really say what's the cause from here, sorry.

Thanks,
Jan

PS:I'll ask around if someone knows within the company

[mmarcotic]

Would it be possible to render more passes and report to us that behaviour? It is simply possible that 2 passes are not enough for quality and denoiser is powerful but it's not magic.

Thanks,
Jan

[lollolo]

Thank you, Jan, for your reply.

You are right. The seam gets almost invisible when I render more passes. I rendered just two passes to show you my problem.

 
But can you check another issue? When I choose Nvidia denoiser, activate multi pass, virtual beauty and set denoise amount to 0, the pass still gets denoised.
It happens only when Nvidia is activated. 

Thanks and have a good day.

[TomG]

- No denoiser is expected to function as expected with just 2 passes :)

- Best create a separate post for when it's a separate issue (otherwise it will get lost). Can post a link to the new thread here once you have one set up.

- I am not sure the NVIDIA AI Denoiser is capable of having different settings in different multipasses (it does the same thing in Max), I would use the Corona denoiser (NVIDIA one is generally intended only for IR).

[lollolo]

Thank you, Tom, for your reply.

I started another topic to discuss the Nvidia issue. https://forum.corona-renderer.com/index.php?topic=32404.0

[lollolo]

Hi

I had the time to build a new threadripper machine. Fresh installed Win 10, C4D R20 and Corona (latest daily). Nothing else on my pc.
But I still get this seam when I use Intel denoiser...! How can this be? New hardware and new installed software... I'm a bit confused to be honest.

I found only one case on Google where someone had the same issue as I have. (not Corona related)
https://github.com/OpenImageDenoise/oidn/issues/62
This issue was fixed in Intel denoiser v1.2.1 (Corona uses v1.2.0)

Thanks!

Hope you can enjoy these days!

[mmarcotic]

Hello,

thank you for your investigation.
I'll talk to the team whether it is possible to update the intel denoiser that Corona uses, and we can take it from there.

Thanks,
Jan

[lollolo]

Thank you, Jan, for your response.

Would be nice, if you could update it.
According to https://www.openimagedenoise.org/ they improved denoising quality as well.

[mmarcotic]

Hello,

I spoke with the developers and apparently, they are already aware and you should expect us using 1.2.1 in the next full version (v7)

Thanks,
Jan

[lollolo]

Hi

Thank you for updating Intel denoiser to 1.3.0 it resolved my issue! Everything is denoising as expected now :)

Thanks again!