October 24, 2026 Vivian Vu

Redshift Automatic Sampling vs Manual Sampling: When to Switch and How to Tune It

Executive SummaryKey Takeaways: Redshift Automatic vs Manual Sampling
Redshift (C4D, Maya, Houdini)

What Redshift automatic sampling does, when to switch it off, and how to check the result:

  • Automatic Sampling: one control, the Threshold. Maxon’s documentation says it is the only parameter that changes the sample count in this mode, and Redshift picks the ray counts per pixel from the shader and scene settings.
  • Manual sampling: turn Automatic Sampling off to get Samples Min / Samples Max for primary rays back, and the samples you set on lights, materials and GI start to count. Maxon recommends raising those per-effect samples, not only Samples Max, for the best performance.
  • Find the noise first: use Show Samples and the lighting AOVs (Diffuse Lighting, Specular Lighting, Reflections, Refractions, Subsurface Scatter, Global Illumination, Volume Lighting) to see which effect is grainy, then add samples only there.
  • On iRender: 1x to 8x RTX 4090 or RTX 5090 servers with Cinema 4D and Redshift installed; tune the sampling on the server that will render the frames and time the hardest frame both ways before you render the sequence.

Redshift automatic sampling is the easiest way to get a clean frame: you set one Threshold and Redshift decides how many rays each pixel needs. It works well on most shots. On some scenes, though, the noise sits in one place, such as a single soft area light, frosted glass or a volume, and the frame gets slow or stays grainy because the whole sampler is pushed harder to clean that one effect.

This guide explains how Redshift’s unified sampling sends rays, what changes when Automatic Sampling is on, when switching to manual sampling is worth it, and how to compare both on your own scene. Every setting name and number below comes from Maxon’s Redshift documentation.

How Redshift unified sampling sends rays

Redshift fires primary rays from the camera through each pixel. They handle anti-aliasing, depth of field and motion blur. Unified sampling is adaptive: Redshift first fires Samples Min rays per pixel and keeps adding rays where it still detects noise, until the pixel is clean enough or reaches Samples Max. The Threshold (Adaptive Error Threshold) decides how sensitive that noise check is. Maxon gives 0.01 as the default and suggests lower values such as 0.003 for production quality.

When a primary ray hits a surface, Redshift fires secondary rays for each effect: area light shadows, glossy reflections and refractions, brute-force GI, ambient occlusion, subsurface scattering and volumes. With Automatically reduce samples of other effects enabled, Redshift divides each effect’s sample count by the number of primary rays in that pixel. Maxon’s example: 4 reflection samples with 2 primary rays gives 2 reflection rays per primary ray.

iRender
How Redshift unified sampling sends rays
primary vs secondary
Floor / nearby surfacesCameraOne pixelPrimary raysSamples Min → Samples Max per pixelHit pointArea light → light samplesGlossy reflection→ material samplesBrute-force GI → GI rays✓ Secondary rays per primary ray = the effect’s samples ÷ the primary rays fired in that pixelWith “Automatically reduce samples of other effects” on (Maxon example: 4 reflection samples ÷ 2 primary rays = 2 per ray)
Primary rays (unified sampling)Secondary rays (per-effect samples)
Schematic, not to scale

This split is the key to the rest of the article. Primary rays are the right tool for edges, depth of field and motion blur; secondary rays clean the shading. You can clean a grainy effect with primary rays alone, but it is the expensive route. Maxon’s documentation gives the example of GI that needs 2,000–4,000 brute-force rays: if the GI rays are left at the default 16, Samples Max has to rise into the thousands to compensate, and every one of those primary rays also shades the rest of the pixel again.

What Automatic Sampling changes

Automatic Sampling was added in Redshift 3.0.11. With it on, Redshift sets the per-pixel sample counts itself from the shader and scene parameters, and the Threshold is the only setting that changes the sample count. Samples Min and Samples Max are hidden. Turn Automatic Sampling off and they come back; the Threshold still works, but only inside the Min/Max range you set.

The Threshold has a strong effect on time. Maxon’s Sampling documentation shows one test scene rendered at four Threshold values:

Threshold Render time (min:sec) What you trade
0.100 0:44 Fastest, visible grain
0.010 3:20 The default value
0.005 7:53 Cleaner, about 2.4x the time of 0.010
0.001 22:50 Very clean, about 6.9x the time of 0.010

Render times from Maxon’s Redshift documentation (Sampling – Production, Automatic Sampling enabled, one example scene). The ratios in the last column are our calculation from those times.

The lesson: lowering the Threshold to clean one stubborn area costs time across the whole frame. That is fine when noise is spread evenly. When it sits in one effect, manual sampling lets you spend the extra rays only there.

When to switch Redshift automatic sampling off

Keep Automatic Sampling for look development, quick previews and shots where the noise is spread evenly across the frame. Consider manual sampling when:

  • One effect stays grainy while the rest of the frame is clean, for example the soft shadow of one large area light, frosted glass, skin with subsurface scattering, or a volume.
  • Lowering the Threshold makes every frame much slower but that one area improves only a little.
  • The shot has strong depth of field or long motion blur. Maxon suggests at least 8–16 Samples Min with depth of field or motion blur, and Samples Max of 256 or more for strong cases. Manual mode lets you set that range yourself.
  • You render a long sequence and a few minutes saved per frame adds up, so the time spent tuning pays back.

Maxon’s own advice for manual mode is clear: for the best performance, raise the individual sample counts of the effects that are noisy, instead of only raising the unified Samples Max.

iRender
Automatic or manual sampling?
SAMPLING
Automatic Samplingone Threshold drives everythingNoisy glassthe problem areaLower the Thresholde.g. 0.01 → 0.003: every pixel works harderGlass improves a littlebut the whole frame got slowerManual samplingtarget the noisy effectFind it in the AOVsShow Samples, raw AOVsRaise that effect's samplesreflection, light, GI, SSS…Rest of the frameunchanged, time rises lessMaxon: default Threshold 0.01, lower values such as 0.003 for productionA faster frame that is grainier is not a win: compare the noise at 100%
AutomaticManualWhere extra rays go
From Maxon: Redshift sampling documentation

Find the noisy effect before you add samples

Two tools in Redshift show where the rays go and where the grain comes from:

  • Show Samples (debug mode in the sampling settings) renders a grayscale map of how many primary rays each pixel received. Darker means fewer, brighter means more, and pure white means the pixel hit Samples Max. Large white areas tell you where the sampler is working hardest.
  • Lighting AOVs split the beauty into its shading parts. Render the frame with the AOVs below, view each one at 100% and look for the one that carries the grain. The “Raw” versions show lighting before it is multiplied by the material colour, which makes grain easier to see.
Noisy AOVWhat it holdsWhere to add samples (manual mode)
Diffuse LightingDirect light on diffuse surfaces, including translucencyThe Samples value of the light that causes the grainy shadow, or the global Light override
Specular LightingReflections of lights onlyLight samples, and the material’s reflection samples for rough surfaces
ReflectionsReflections of the environment and other objectsThe material’s reflection samples, or the global Reflection override
RefractionsLight seen through glass and liquidsThe material’s refraction samples, or the global Refraction override
Subsurface ScatterSubsurface scattering (skin, wax, marble)SSS samples, or the Sub-Surface Single / Multiple Scattering overrides
Global IlluminationIndirect bounce lightBrute-force GI rays in the GI settings
Volume LightingLighting inside volumes and fogVolume samples, or the global Volume override

AOV descriptions from Maxon’s Integrated AOVs page; override names from the Sampling – Production page. Overrides apply to the whole scene: Replace sets a fixed sample count, Scale multiplies the existing counts.

How to tune manual sampling, step by step

This is the order Maxon recommends in its unified sampling documentation, with notes for production:

  1. Turn off Automatic Sampling, depth of field and motion blur. Set Samples Min and Samples Max both low, such as 4 or 16.
  2. Raise the samples of the noisy effects you found in the AOVs (light, reflection, refraction, GI, AO, SSS, volume) until the frame looks acceptable. Change one effect at a time so you know what fixed what.
  3. Turn depth of field and motion blur back on and raise Samples Min and Samples Max together until the blur is clean. Maxon notes this often lands between 32 and 200 or more.
  4. Lower Samples Min back to 4 or 16, so unified sampling only adds rays where the image needs them.
  5. Adjust the Threshold until depth of field and motion blur show no grain, and check with Show Samples that the image is not mostly white.
  6. Render the final in Bucket mode. Maxon recommends Bucket for final renders; Progressive mode ignores the unified sampling and sample-count settings, so it cannot show the effect of your tuning.

If you denoise an animation, Maxon recommends turning off Randomize Noise Pattern to reduce flicker between frames.

iRender
Manual sampling, step by step
TUNING
1BaseDOFMotion blurSamples Min / Max4 – 16DOF and motion blur off,Min/Max 4–162Effect samplesDOFMotion blurSamples Min / Max4 – 16raise light, reflection, GI…for each noisy AOV3DOF + motion blurDOFMotion blurSamples Min / Max32 – 200+turn them on,Min/Max 32–200+4Samples Min backDOFMotion blurSamples Min / Max4 – 200+lower Min to 4–16:rays only where neededLowering Samples Min at the end lets unified sampling add rays only where needed
Change one thing at a time
Source: Maxon, Redshift unified sampling documentation

How to compare both modes on your own scene

Whether manual sampling is faster depends on the scene, so test it instead of trusting a percentage from someone else’s project:

  1. Pick the hardest frame of the shot: the most glass, the thickest volume, the strongest motion blur.
  2. Render it with Automatic Sampling at the Threshold you would use for delivery. Note the render time from the Redshift log or Render View.
  3. Render it in manual mode after tuning with the steps above, at the same resolution and in Bucket mode.
  4. Compare the noise, not just the time. Look at the beauty and the noisy AOV at 100%, side by side. A faster frame that is grainier is not a win.
  5. Multiply by the frame count. The time difference on one frame, times the number of frames, tells you whether the tuning is worth it for this shot.

SaaS or IaaS render farm for tuning Redshift sampling?

Both farm models render the same image, because the sampling settings are saved in your scene. The difference is where you do the testing: tuning manual sampling means several rounds of rendering one frame, checking the AOVs and changing a value.

Your situationSaaS render farmIaaS render farm (iRender)
Sampling is already tuned and the shot is approvedA good fit. Upload the project and the farm renders the frames, often spread across many machines, with no server to manage.Also works, but you start, use and stop the server yourself.
You have a deadline and need to know when rendering starts and endsJobs join the farm’s queue, so the start time depends on how busy the farm is; many farms sell higher-priority plans to start soonerThe server runs only your job from the moment it boots, so you control when rendering starts and can time the whole job
You are still testing sample countsEach test is a job: submit a frame, wait, download the result and its AOVs, then compare.Render the frame in the Redshift Render View on the server, look at the AOVs on screen, change a value and render again.
Your own GPU is slow, or the scene does not fit in its memoryTesting at home is slow or not possible, so every test round moves to the farm.Test and render on the same RTX 5090 cards, with 32 GB of memory on each GPU.
You want the test times to match the final renderYour tests run on your own hardware, and the farm’s hardware may be different.The frame you time is rendered on the same hardware as the final sequence.

A comparison of how the two farm models work for this task, not a speed test.

A simple rule: if your sampling is already tuned and approved on your own machine, a SaaS farm that renders the frames for you is a good fit. If you still need to find the right sample counts, or your own GPU is too slow or too small for the scene, test and render on the same IaaS server.

A sampling test on an iRender server

iRender
How iRender works: your computer controls your own multi-GPU server
IaaS render farm
Your PC or MacNo powerful GPU neededRemote desktopLive screen1:1 like your PCYOUR OWN GPU SERVERbare-metal · not sharedGPUGPUGPUGPUGPUGPUGPUGPU1, 2, 4 or 8 × RTX 5090 (32 GB) or RTX 4090 (24 GB)Threadripper PRO · 256 GB ECC RAM · 2 TB NVMe SSDFull admin access · your setup is saved between sessions1Register, top upFirst $50+ top-up doubled2Upload your projectiRender Drive, free3Start and connectRemote desktop, any OS4Render, shut downBilling stops, per minute✓ Your workstation, just more GPUs: no queue to wait, no farm plugin, no job submission, no settings changed
Your mouse and keyboardServer screen streamed back
Schematic, not to scale
  1. Upload the project to iRender Drive before you start the server; uploading is free and does not use rental time.
  2. Start a 4x or 8x RTX 5090 or RTX 4090 server. Cinema 4D and Redshift are installed, and billing is per minute.
  3. Open the scene and render the hardest frame in the Redshift Render View with Automatic Sampling, and note the time.
  4. Tune manual sampling with the AOVs and Show Samples, render the same frame again and compare.
  5. Render the sequence with the faster setting that passes your noise check. If the deadline is tight, start more servers and give each one a frame range; the total cost stays about the same.

Before you render the sequence on another machine

  • Use the same Cinema 4D (or Maya, Houdini) and Redshift versions as the machine where you tuned the sampling.
  • Check that Automatic Sampling is set the way you tested it; it is a render setting, so a different render preset can change it.
  • Render the final in Bucket mode, not Progressive.
  • Keep the AOVs you used for the check, or at least the noisy one, so you can review the final frames.
  • Render the hardest frame first and compare its time with your test before you start the full range.

Tick list: before the sequence leaves your workstation

The checks above as a list to tick on the render machine.

ChecklistRedshift sampling checklist
0 / 6 done
Tip: tick each item as you set up the job; the ticks reset when the page reloads.

Frequently asked questions

1. What does Automatic Sampling do in Redshift?

It lets Redshift choose the number of rays per pixel from your shader and scene settings. In this mode the Threshold is the only setting that changes the sample count, so you control quality with one value. Lower values give a cleaner image and take longer.

2. Should I use Automatic Sampling or manual sampling in Redshift?

Use Automatic Sampling for previews, look development and shots where noise is spread evenly. Switch to manual sampling when one effect, such as a soft area light, frosted glass, subsurface scattering or a volume, stays grainy and lowering the Threshold slows down the whole frame.

3. What Threshold value should I use?

Maxon gives 0.01 as the default and suggests lower values such as 0.003 for production quality. In Maxon’s example scene, going from 0.01 to 0.005 more than doubled the render time, so lower it only as far as the shot needs.

4. Why are my Samples Min and Samples Max settings missing?

They are hidden while Automatic Sampling is enabled. Turn Automatic Sampling off in the Redshift sampling settings and Samples Min and Samples Max appear again. The Threshold still works, but inside the range you set.

5. How do I find which part of a Redshift render is noisy?

Turn on Show Samples to see which pixels use the most primary rays, then render the lighting AOVs (Diffuse Lighting, Specular Lighting, Reflections, Refractions, Subsurface Scatter, Global Illumination and Volume Lighting) and look for the one that carries the grain. Add samples to that effect only.

6. Can I test Redshift sampling on the same machine that renders the final frames?

Yes, on an IaaS render farm. On iRender you rent the whole server, open the scene in Cinema 4D with Redshift, render test frames in the Redshift Render View and then render the sequence on the same GPUs, so your test times match the final render.

Render your Redshift scenes on iRender

iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. Your server image is saved between sessions, so your plugins and settings stay installed. Cinema 4D and Redshift are pre-installed on every server.

Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.

This quick start shows how to start a server and render Cinema 4D and Redshift on it:

Two Redshift runs we recorded on our servers: 150 frames at 1080p on 4x RTX 5090 at 40.84 seconds per frame (about 1h 42m), and a 301-frame cloth simulation at 1080p on 1x RTX 5090 at 21.3 seconds per frame:

New users get a 100% bonus on the first top-up (minimum $50). See plans on the Cinema 4D and Redshift render farm page or download the iRender GPU app.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , ,

Vivian Vu

Vivian Vu has written nearly 40 articles for the iRender blog, covering iRender news, Maya, Blender and real-time rendering.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →