Multipass Denoiser performance 2017 vs 2020

[RwVision]

Hi there,

Please correct me, if I'm wrong but the current denoiser version doesn't come near to the multipass performance of the 2017 version. I've tested numerous settings.
I'm honestly surprised. Seems like all behaves like only old rgb denoising, even when all passes are enabled to consider.

Was the original, true multipass denoising abandoned?

Please check the below examples.

Here's the vrimg file if anyone wants to play with it:
https://www.dropbox.com/s/u9wvijmt6n...006.vrimg?dl=0

In the old version we can retain the wall bump details, while smoothing out properly GI noises (vertical curtains). Current denoiser is just way too blurry. When I wanted to retain details, all other surfaces are looking like compressed jpg.

[sirio76]

I’m interested in this as well, old denoiser was superior to the one in Vray5.

[Makushimu]

The previous, old one may have been better, but it provided many artifacts and bugs. At least for me.
The current denoiser suits me because nothing unpredictable happens to it. At least for now.

[shaio]

RwVision are you talking about the V-Ray Denoiser that is within Cinema 4D or the separate Denoise tool that comes with V-Ray? I'm asking because you've attached a multipass vrimg file and I assume that we're talking about the standalone denoiser tool.

[RwVision]

Hi - On both I'm talking about the standalone denoisers.

[shaio]

So you're comparing the denoiser between V-Ray 3.7 and V-Ray 5 right? Can you tell me which V-Ray 3.7 you get the standalone denoiser from? I'm asking because oddly enough we're using the same Denoiser versions for both V-Ray 3.7 and V-Ray 5. Right now I'm comparing the results from the standalone denoiser taken from V-Ray 3.70.05 and V-Ray 5 and get the exact same result from both denoisers using the image you attached.

[RwVision]

No. It's denoiser build from 2017 vs 2020 build or even the 2019 build. Does not matter which Vray version you use.

[shaio]

Yes this is a very old build. It probably doesn't have the UI either. I'll look in to it and see what might have changed.

[RwVision]

Here's my Gui for the older denoiser, might help you faster to check. Saved me time a lot of times

The multipass denoising did a very good job in it. New build is almost unusable, when want to keep details.

https://www.dropbox.com/sh/cp9nyqchx...YC_ieSDOa?dl=0

[RwVision]

Hi Ivan,

Any progress? Should I prepare more info/ examples?

[RwVision]

After extended tests, it's obvious that current standalone denoiser does not even come close to the older version. Multipass denoising is simply not working.

With the older mp denoiser I can get totally noise-free image,without loosing texture or bump details. No compression effect, everything is in place.

The current version blurs everything out, not even handling properly all the grain - simply unusable.

https://www.dropbox.com/sh/3ak1dt7qseoh34a/AABpa1s4z1aB4fnUEEjN4bAca?dl=0
(pay attention to road texture compression, wall bump and top part of the long shades in building)

This is more than needed to look into!

[sirio76]

I have to agree, the old system had more options to fine tune the denoising. I hope developers can reintroduce those options.

[RwVision]

Not to mention the longer frame save times - which I addressed one year ago and still I don't see any progress. There was supposed to be a new version, with setup of strength for each pass - no news there either.

Ivan - what was the latest denoiser version which utilized the true multipass, with no GUI? My old build (Nov 2016) still has the over-bright refraction pass issue. Please let me know where I can get it?

[RwVision]

Yes this is a very old build. It probably doesn't have the UI either. I'll look in to it and see what might have changed.

Almost a month passed, still no info on performance and new denoiser?

Really looking into using new versions and methods.

[aleksandar.kasabov]

Hello,

I apologize for the delayed reply.

We are still looking for the reason for this. The change has happened quite a long time ago and we are looking where the problem is. We will let you know if we have any updates.