Page tree


This page discusses the workflow for Denoise, if you want to know how to use this from a DCC application and the technical details, take a look at the Denoising page.

When using the Denoise feature in RenderMan, it's important to understand a few things to make your workflow better or even more automatic. Most packages expose this as a dropdown or menu selection. This is a post-render process so an image has to be written out before it can work.

Below is a reference image rendered using 4096 samples per pixel (and then sadly saved as a JPEG).

This image has quite a few things going on:

  • Depth of field
  • Subtle motion blur (as the balloons fall)
  • Glossiness
  • Translucency (also known as diffuse transmission)
  • Lots of indirect lighting
  • Mirrors
  • Carpeting/small details

Each of these may take different amounts of sampling to converge and they're spread unevenly through the scene.

Here we're using the Default Denoise settings but there are other useful settings:

  • Alpha - used to denoise the alpha mask

You can also choose different modes:

  • Frame - denoise a single frame
  • Crossframe - denoise an animation of multiple frames (this requires multiple frames to be available to begin the denoise process instead of each frame immediately as it finishes)

Your pixel filter should be set to "importance". RenderMan for Maya and Houdini turns this on automatically when selecting Denoise on AOVs

Getting Ready to Use Denoise

When rendering scenes using raytracing, the result of poor quality settings or insufficient time to converge shows noise. Users are familiar with this effect when a render just starts up and then converges before their eyes. For a first iteration you may see something like the image below:

More samples will help the image improve, but this takes time. The more powerful your computer (the more processor cores and more modern it is) the faster this will go. When using RenderMan, you can increase the samples taken automatically by the renderer by decreasing the Pixel Variance parameter in small increments. You can get an idea about this looking at the progression below, each slice is a lower Pixel Variance value left to right.

Notice that as sample counts get higher and higher, the difference in quality becomes more and more subtle. This is because convergence over time tends to resemble a curve where eventually it starts to flatten out. This is where the Denoise feature does its work for the artist! By removing this sort-of long "tail" in the convergence curve, you can eliminate having to take more samples and finish your render earlier. Below is a simple illustration of this using the graph.

Chances are you're most interested in when to use Denoise. Choosing to use Denoise too early will result in artifacts and in an animation these can move around and be quite distracting. If you let the image fully converge then you may be letting it render longer than necessary and losing time. Naturally a hard and fast suggestion is preferred but scenes are all unique visually and might even change drastically during a shot. Different effects will take longer in some scenes than others and your overall image contrast can be different based on subject matter, time of day, or even artistic mood. In this image you can tell the balloons take some time to converge compared to other objects because of their diffuse transmission/translucency. So you can assume a scene like this without the balloons would converge sooner and allow you to try Denoise more quickly.

Trying Denoise

Using the simple Checkpointing in Renderman can give you multiple chances to try Denoise on frames as they converge without losing time by starting the render over. Below is a set of examples of trying Denoise at the same strength on different levels of convergence. Keep in mind you want an image similar to the one at the top of the page, which is our reference image fully converged. The bottom image in this section is very similar and with less than 25% of the samples in the reference image needed.

Changing Strength

There are several ways to alter how the filter works but most helpful is the ability to change its strength. By default it operates at a setting of 0.5 but other overrides ship with RenderMan giving you options between 0.2 and 0.7 strength. You can even create your own simple override files to change the strength to a setting you prefer for a specific image or shot you're working on. More information about this can be found on the page regarding the Denoise Tool.

Below is an original and more noisy render.

The following comparison is from Strength 0.2 and Strength 0.7. The default Strength is 0.5 for Denoising. Note that higher strength may work well to clear up a still image with a loss of some details. But too high may look "wobbly" or jittery in an animation. The best solution is a balance between a more converged image and a lower strength Denoise application.

Error rendering macro 'before-after-slider-macro-v2'

Object [id=45749302] was not of the specified subclass [com.atlassian.confluence.pages.Attachment] : loaded object was of wrong class class com.atlassian.confluence.pages.Page; nested exception is org.hibernate.WrongClassException: Object [id=45749302] was not of the specified subclass [com.atlassian.confluence.pages.Attachment] : loaded object was of wrong class class com.atlassian.confluence.pages.Page