How to Denoise AOVs Effectively

Arnold Denoiser Fundamentals

The Arnold denoiser is one of the render engine's most underutilized tools. It can cut render times by 30–50% while maintaining or improving final image quality — but only if you set up your AOVs (Arbitrary Output Variables) correctly.

We process thousands of Arnold renders monthly on Super Renders Farm, and the difference between a properly denoised render and a noisy one often comes down to one thing: whether variance AOVs are enabled. Many artists skip this step, assuming the denoiser will magically clean noisy renders. It won't. The denoiser needs reference data — your variance AOVs — to work effectively.

How Arnold Denoising Works

Arnold's denoiser uses machine learning to intelligently reduce noise in your beauty pass. For technical details on Arnold's denoising implementation, consult the official Autodesk Arnold documentation. But it requires two critical components:

1. Beauty AOV — Your final render (required)
2. Variance AOVs — Pixel variance data for diffuse, specular, transmission, and SSS (required for denoising)

The variance AOVs tell the denoiser where noise is happening and what type of noise it is. Without them, the denoiser has no reference and can't function.

The Two Denoiser Options

Arnold offers two denoising backends:

OptiX Denoiser (NVIDIA-powered)

• Faster: processes in seconds
• Requires NVIDIA GPU (RTX 20-series or newer recommended)
• Better for complex scenes with multiple light bounces
• Uses AI trained on physical rendering samples
• Recommended for most production workflows

OIDN Denoiser (Intel Open Image Denoise)

• Slower: processes in 10-30 seconds depending on resolution
• Works on any hardware (CPU, AMD GPU, Intel GPU)
• Better for stylized or non-photorealistic rendering
• Open-source and transparent
• Use when OptiX isn't available

Most studios default to OptiX for speed, but OIDN is equally valid for archviz and animation.

Setting Up Denoiser Variance AOVs in Maya

Follow this workflow to enable denoising in your Arnold Maya setup.

Step 1: Enable Arnold Render Pass Outputs

1. Open Arnold > Arnold Render View
2. In the Properties panel, go to Render tab
3. Expand Output
4. Enable the checkbox for Enable Output Denoising AOVs

This tells Arnold to compute the variance data during render.

Step 2: Create Variance AOV Outputs

In Maya's Render Settings:

1. Go to Arnold > Render Settings (or use Arnold RenderView menu)

2. Navigate to AOVs tab

3. Look for output drivers. You should see your beauty output already configured

4. Add a new output driver:

   • Click the "+" button to add an AOV
   • Set Name to: variance
   • Set Type to: RGB (or Utility)
   • Set Quantize to: None (keep full precision for denoiser)
   • Set Format to: EXR (required for variance data)

5. Configure filter for variance:

   • Locate the Filter dropdown for the variance output
   • Select Variance (not gaussian, not box, specifically variance)

This creates a separate variance pass that Arnold will populate during rendering.

Step 3: Enable Denoiser in Render Settings

1. In Arnold Render Settings, go to the Main tab

2. Expand Denoiser section

3. Enable the checkbox: Denoise Beauty AOV

4. Under Denoiser Type, select:

   • OptiX (if you have NVIDIA GPU) — preferred
   • OIDN (if using CPU or AMD GPU)

5. Set Denoiser Radius: 1 is standard; increase to 2 for stronger denoising (slower)

Step 4: Reduce Sample Count (Optional but Recommended)

One advantage of denoising is that you can reduce your overall sample count and let the denoiser clean up noise. This saves significant render time:

1. In Render Settings > Main > Sampling
2. Reduce Camera AA from (default 3-5) to 2 or even 1
3. Reduce Diffuse Samples to 2–3 (instead of 4–5)
4. Arnold will render noisier, but the denoiser will clean it

Test on a 200-frame animation: standard settings (3 camera AA, 4 diffuse) vs denoised low samples (1 camera AA, 2 diffuse). The denoised version often renders 40% faster with comparable final quality.

Advanced: OptiX vs OIDN Comparison

When to Use OptiX

• Scenes with complex global illumination (many light bounces)
• Interior archviz with occlusion-heavy geometry
• Photorealistic product renders
• GPU available on your render node (e.g., Super Renders Farm RTX 5090)
• Timeline: must denoise in seconds

OptiX produces cleaner results in complex lighting scenarios because its neural network was trained on physically-based render samples. It handles caustics, subsurface scattering, and indirect light better than OIDN.

When to Use OIDN

• Stylized or non-photorealistic renders (animation, motion graphics)
• Simple scenes with direct lighting only
• CPU-only render nodes
• No NVIDIA GPU available
• No time pressure (denoising adds 10-30 seconds)

OIDN is deterministic and transparent — it applies mathematically-defined filtering rather than neural network inference. Some artists prefer this for final VFX compositing where consistency matters.

Arnold AOV Setup for Cloud Rendering

When submitting Arnold renders to a cloud farm like Super Renders Farm, your AOV setup must be portable. For more details on packaging Maya scenes for render farms, see our comprehensive guide to rendering Arnold on cloud infrastructure.

1. Use relative paths for all outputs:

   • Instead of: /Users/yourname/renders/shot_001.exr
   • Use: ./renders/shot_001.exr or just shot_001.exr

2. Ensure variance filter is set correctly:

   • Many submissions fail because variance AOV is set to "gaussian" or "none" instead of "variance"
   • Double-check before uploading

3. Confirm denoiser availability on the farm:

   • Super Renders Farm supports OptiX on our RTX 5090 GPU fleet
   • OptiX is not available on CPU-render nodes (use OIDN instead)
   • Specify your preference in render job settings

4. Test locally first:

   • Render 1 frame locally with denoiser enabled
   • Verify variance AOV and beauty AOV both write correctly
   • Check that the denoised output matches your expectations
   • Then submit the full job

Complete Maya Arnold Denoiser Workflow

For a 300-Frame Animation

1. Local test render (1 frame, full settings):

   • Enable denoising
   • Enable variance AOV output
   • Render at full resolution
   • Check beauty and variance outputs exist
   • Verify denoised frame quality

2. Adjust sample counts if needed:

   • If test frame is clean enough with reduced samples, update settings
   • If test frame is too noisy, increase samples back

3. Package and submit:

   • Ensure all textures/assets referenced with relative paths
   • Export to EXR with denoiser enabled
   • Upload to farm with proper job configuration

4. Receive results:

   • Beauty pass (fully denoised)
   • Variance pass (reference, can be discarded)
   • All other AOVs (diffuse, specular, etc.) for compositing

Common Denoising Mistakes

Mistake 1: Variance AOV Set to "None"

The denoiser won't work. It needs the variance data. Double-check your AOV output filter is set to Variance, not None or any other option.

Mistake 2: Variance Output Missing Entirely

If you forget to add the variance output driver, Arnold will still render and apply the denoiser, but it will use lower-quality generic variance estimation. Always explicitly add a variance AOV for optimal results.

Mistake 3: Using JPEG or PNG for Variance Output

Variance data requires full floating-point precision. Save variance to EXR 32-bit (not JPEG, not 8-bit PNG). Otherwise, precision loss prevents proper denoising.

Mistake 4: Denoising Local GPU Renders But Submitting to CPU Farm

If you denoised locally on your GPU (OptiX) but submit to a CPU-only farm, the farm can't apply OptiX denoising. Switch to OIDN in your job settings, or leave denoising to the farm.

Denoiser Strength and Radius Settings

Denoiser Radius

• Radius 1 — Conservative denoising, preserves fine details, slower
• Radius 2 — Aggressive denoising, smooths over details, faster
• Default (1) is recommended for most production work

Increasing radius helps when:

• Render is very noisy despite low sample counts
• Scene has heavy volumetrics or motion blur
• Animation has temporal flickering you want to reduce

Decrease radius if:

• Details (hair, fabric textures) are being smoothed excessively
• You prefer to live with slight noise rather than lose fine features

Beauty AOV Threshold

Some Arnold versions allow you to set denoiser aggressiveness per channel (color, alpha, etc.). Stick with default unless you have a specific reason to customize.

FAQ

Q: Do I have to use the denoiser? A: No. Denoising is optional. Many studios prefer non-denoised output for full control in compositing. But if your goal is fast renders with minimal noise, denoising is a huge timesaver.

Q: Can I denoise after render instead of during render? A: Yes. Save the noisy beauty and variance passes to EXR, then use Arnold's post-render denoiser or third-party tools (Nuke, Substance Alchemist). This gives you flexibility to adjust denoiser settings after the fact.

Q: Does OptiX denoiser on a render farm change my results? A: Yes, slightly. OptiX produces slightly different results than OIDN because the neural networks are different. For consistent results across jobs, stick with one denoiser (recommend OptiX on GPU farms like Super Renders Farm).

Q: What if the denoised frame looks worse than the noisy one? A: Reduce the sample count less aggressively. Your original sample count might not have been low enough to benefit from denoising. The denoiser works well when samples are 30-50% below quality threshold.

Q: Can I use Arnold denoiser in Houdini or other software? A: Arnold's denoiser is specific to Arnold in Maya, Houdini, and Katana. Houdini users can enable it in the Arnold ROP. Other software requires OIDN or third-party denoisers.

Q: How much does denoising add to my render time? A: OptiX: 2-5 seconds. OIDN: 10-30 seconds (depending on resolution and CPU). Denoising time is negligible compared to the render time saved by reducing samples.

Q: Should I enable denoising for preview renders or only finals? A: Enable it for everything. Since denoising reduces render time, it's especially useful for previews. You get faster feedback with less noise.

Q: What other Arnold features should I know for production rendering? A: Check our detailed guide on Arnold cloud rendering for optimization tips and farm-specific configurations.