Is anyone using Iray post denoiser (How to render sharp)

GalaxyGalaxy Posts: 562

How to render eyes sharp with post denoiser or everyone is avoiding it like headlamp.

Comments

  • Matt_CastleMatt_Castle Posts: 3,004

    Personally, my preference is to render with the post denoiser off and do it with a standalone tool afterwards (of which Nvidia's AI Denoiser is an available option, although I generally prefer the results of Intel's OI denoiser).

    This is partly because the denoiser uses a fair chunk of VRAM and can make it more likely to drop to CPU (at which point the denoiser won't work anyway), and partly because it's non-destructive - with separate noisy and denoised files, you can mask and adjust the strength of the denoising in an image editor.

  • barbultbarbult Posts: 26,211

    If I use the denioser, I sometimes do a spot render of certain areas without the denoiser later and use Photoshop to combine them. For the spot render, set it to render to file in the Tool Settings pane.

  • mavantemavante Posts: 734

    the denoiser uses a fair chunk of VRAM and can make it more likely to drop to CPU (at which point the denoiser won't work anyway)

    Seriously? I had no idea this was the case. Is there documentation on this somewhere? I'm trying to understand why iRay can work with CPU, but not the denoiser.

  • SevrinSevrin Posts: 6,313

    Denoisers aren't there to sharpen your images.  They're for speeding up renders.  If fine details are what you're after, denoise backgrounds after rendering normally.

  • outrider42outrider42 Posts: 3,679
    mavante said:

    the denoiser uses a fair chunk of VRAM and can make it more likely to drop to CPU (at which point the denoiser won't work anyway)

    Seriously? I had no idea this was the case. Is there documentation on this somewhere? I'm trying to understand why iRay can work with CPU, but not the denoiser.

    I have several points on denoising. It depends on how you define "fair chunk". For me it takes around 500MB to 1GB.

    It is NOT true that the denoiser will drop you to CPU mode. The denoiser will actually disable itself if the VRAM at GPU capacity. People need to understand this.

    The latest release of the beta also has an additional feature to specify how much VRAM the denoiser is allow to use, so you can limit it.

    The denoiser works better at higher resolutions. The more pixels the denoiser has to work with, the better its outcome.

    Spot rendering can be quite a helpful tool here. A small spot render will render many times faster than a full render, too.

    External denoisers are always an option, too, as gas been pointed out. However my issue is that it takes smart guess work to use if you are trying to save time. If you always render to 95% convergence then it doesn't matter. But if you wish to save time and use the denoiser to fill in the gaps, you need to guess when your picture is going to be good enough to stop the render and denoise externally. However with the built in denoiser you can see this progress in real time and judge for yourself when you think it looks "done".
  • novastridernovastrider Posts: 208

    IT does fine with eyes imo. Now hair on the other hand...

  • GalaxyGalaxy Posts: 562

    IT does fine with eyes imo. Now hair on the other hand...

    Tried with Genesis 8 default eyes? If yes after how many iteration? Worth to mention here that I stopped rendering manually and therefore all iteration not completed.

    Example attached first photo with default materials and second photo with increased mess resolution. Clarity increased with artifacts visibility.

    I tried with other figures and it looks like Genesis 8 eyes are blurrier than other figures. May be my settings are not correct. 

     

    Genesis 8 example.png
    1280 x 720 - 382K
    compare 3.png
    1280 x 720 - 589K
  • GalaxyGalaxy Posts: 562
    edited April 2020

    Now after posting the images here looks like sharpness of eyes are acceptable. With post denoiser images are blurry though the fact is my eyes are tuned to compare the eyes with other genesis figures. NOW it looks like artifacts are creating problems.

    Edit note: Tried to correct grammatical errors.

    Post edited by Galaxy on
  • novastridernovastrider Posts: 208
    edited April 2020

    I think there might be something wrong with the rest of the settings, because I see artifacts in the skintexture too. Did you compress and replace or reformat all the textures or something like it? The bumpmap/normal also seems to be either missing or wrong. Denoiser should be pretty stable sharp after about 250 rendercycles, I go into the thousands but that's not needed for most people. Don't forget to put sharpening from Gaussian 1.5 into Mitchell 1.0. Gaussian is blurry as heck.

    Post edited by novastrider on
  • GalaxyGalaxy Posts: 562

    I think there might be something wrong with the rest of the settings, because I see artifacts in the skintexture too. Did you compress and replace or reformat all the textures or something like it? The bumpmap/normal also seems to be either missing or wrong.

    Only for second image. First image is default Genesis 8 materials without any kind of compression.

  • vagansvagans Posts: 422
    mavante said:

    the denoiser uses a fair chunk of VRAM and can make it more likely to drop to CPU (at which point the denoiser won't work anyway)

    Seriously? I had no idea this was the case. Is there documentation on this somewhere? I'm trying to understand why iRay can work with CPU, but not the denoiser.

     

    I have several points on denoising. It depends on how you define "fair chunk". For me it takes around 500MB to 1GB.

     

    It is NOT true that the denoiser will drop you to CPU mode. The denoiser will actually disable itself if the VRAM at GPU capacity. People need to understand this.

     

    The latest release of the beta also has an additional feature to specify how much VRAM the denoiser is allow to use, so you can limit it.

     

    The denoiser works better at higher resolutions. The more pixels the denoiser has to work with, the better its outcome.

     

    Spot rendering can be quite a helpful tool here. A small spot render will render many times faster than a full render, too.

     

    External denoisers are always an option, too, as gas been pointed out. However my issue is that it takes smart guess work to use if you are trying to save time. If you always render to 95% convergence then it doesn't matter. But if you wish to save time and use the denoiser to fill in the gaps, you need to guess when your picture is going to be good enough to stop the render and denoise externally. However with the built in denoiser you can see this progress in real time and judge for yourself when you think it looks "done".

    Great info, thanks. Now I understand why the denoiser doesn't work all the time.

  • GalaxyGalaxy Posts: 562
    mavante said:

    the denoiser uses a fair chunk of VRAM and can make it more likely to drop to CPU (at which point the denoiser won't work anyway)

    Seriously? I had no idea this was the case. Is there documentation on this somewhere? I'm trying to understand why iRay can work with CPU, but not the denoiser.

     

    I have several points on denoising. It depends on how you define "fair chunk". For me it takes around 500MB to 1GB.

     

    It is NOT true that the denoiser will drop you to CPU mode. The denoiser will actually disable itself if the VRAM at GPU capacity. People need to understand this.

     

    The latest release of the beta also has an additional feature to specify how much VRAM the denoiser is allow to use, so you can limit it.

     

    The denoiser works better at higher resolutions. The more pixels the denoiser has to work with, the better its outcome.

     

    Spot rendering can be quite a helpful tool here. A small spot render will render many times faster than a full render, too.

     

    External denoisers are always an option, too, as gas been pointed out. However my issue is that it takes smart guess work to use if you are trying to save time. If you always render to 95% convergence then it doesn't matter. But if you wish to save time and use the denoiser to fill in the gaps, you need to guess when your picture is going to be good enough to stop the render and denoise externally. However with the built in denoiser you can see this progress in real time and judge for yourself when you think it looks "done".

    Then it does not matter denoiser on or off because if vram is not sufficient, denoiser is automatically off. Or those are disabling denoising due to "denoiser is occupying vram memory" is a myth only.

  • fastbike1fastbike1 Posts: 4,078

    @Galaxy "Or those are disabling denoising due to "denoiser is occupying vram memory" is a myth only."

    Wouldn't be the first time people acted on a forum post without checking for themselves. Not really a myth, the denoiser will occupy VRAM, it just won't be the cause of a drop to CPU.

  • PadonePadone Posts: 4,003

    @Galaxy The iray denoiser doesn't use the albedo and displacement buffers and it only relies on ai. So it is more an advanced blur than a denoiser. This is why you get blurred images with it. External denoisers can't help either for the same reason because iray can't export the albedo and displacement buffers for them to work properly.

    Thus if you want a good and fast denoiser you're out of luck with iray. An option is to go to blender.

    https://diffeomorphic.blogspot.com/p/daz-importer-version-14.html

  • TaozTaoz Posts: 10,254
    Padone said:

    @Galaxy The iray denoiser doesn't use the albedo and displacement buffers and it only relies on ai. So it is more an advanced blur than a denoiser. This is why you get blurred images with it. External denoisers can't help either for the same reason because iray can't export the albedo and displacement buffers for them to work properly.

    Thus if you want a good and fast denoiser you're out of luck with iray. An option is to go to blender.

    https://diffeomorphic.blogspot.com/p/daz-importer-version-14.html

    Or use the Intel version, which some say is better than NVidia's.  You can use this Windows DragNDrop GUI for both:

    https://taosoft.dk/software/freeware/dnden/

  • GalaxyGalaxy Posts: 562

    I learned some new and useful info, thanks.

  • outrider42outrider42 Posts: 3,679
    edited April 2020
    Galaxy said:

    IT does fine with eyes imo. Now hair on the other hand...

    Tried with Genesis 8 default eyes? If yes after how many iteration? Worth to mention here that I stopped rendering manually and therefore all iteration not completed.

    Example attached first photo with default materials and second photo with increased mess resolution. Clarity increased with artifacts visibility.

    I tried with other figures and it looks like Genesis 8 eyes are blurrier than other figures. May be my settings are not correct. 

     

    The main reason those look that way is because of lighting. The light is rather low here and you know that Iray does not like the dark. It takes more iterations for Iray to render dark scenes. The eyes are odd looking because there is very little information for the denoiser to work on. Another denoiser is not going to magically do better at that picture because albedo can only do so much. But it is very easy to test. Just render them with the denoiser turned off and stop at the same iteration count you did before. Then run through one of the external denoisers. You could try several denoisers, they can be different. Then you will have the answer.

    Any denoiser is going to depend on how many pixels have been rendered. The more pixels, the better. The denoiser is also better with non human things, like backgrounds. People are hard.

    For your scene, I would add a little light. You can always go back and darken the picture later. I believe if you do this, it will render faster with better detail.

    BTW, the Iray denoiser has been updated for Iray 2020 in the new Daz beta, I am not sure if Daz has implemented all of its features yet. But the denoiser is a work in progress and will continue to get updates. So if you tried the Nvidia denoiser before and hated it, you might want to try it again for the beta to see if it has changed any for you. How well it works really depends on what you make, so there is no yes or no answer.

    Post edited by outrider42 on
Sign In or Register to comment.