Octane AOVs in Cinema 4D: Rebuild the Beauty Pass for Compositing
Octane AOVs (called render passes in older versions) add back up to the beauty when the stack and the math are right. The main points from OTOY's docs and guides:
- Additive: Standard beauty or lighting stacks are added from black; with the Post Processing AOV they form the beauty.
- Raw AOVs: Raw divides out the surface color; multiply each raw AOV by its matching filter AOV, then add.
- One stack: Use either the beauty-surfaces stack or the light stack, not both added together.
- Inside Octane: Output AOVs let you composite in real time inside Octane, with multiple composites per scene.
- Many AOVs, more memory: Each beauty pass needs its own film buffer on the GPU; iRender RTX 5090 servers with 32 GB per GPU leave more room for large AOV stacks at high resolution.
Render passes are only useful if they add back up to the render you approved. When an Octane comp comes out too bright, too dark or missing glare, the stack or the blend math is usually wrong. This guide follows OTOY’s documentation for Octane in Cinema 4D.
Checked against the Cinema 4D and OctaneRender documentation, November 2026.
1. How do Octane beauty passes add up to the render?
OTOY describes merging standard AOV stacks as additive: you start with black, and each pass adds its contribution (OTOY: Render Series, Render Passes).
Each layer in the figure is one beauty pass. Stacked with an Add blend, diffuse gives the base color, reflection and refraction add the shiny and transparent parts, emitters and environment add light sources and sky, and the Post Processing pass adds bloom and glare. The sum is the beauty.
Octane AOV groups and what they are for
From OTOY's "AOVs and Composites" page for Octane in Cinema 4D.
| Group | Contains | Use |
|---|---|---|
| Beauty – surfaces | The passes that make up the beauty, such as diffuse, reflection, refraction, emitters, environment | Rebuild and grade the render by material component |
| Light | Lighting contribution per light ID | Relight in comp; an alternative stack to beauty passes |
| Auxiliary | Process and post AOVs such as Alpha and Shadow | Shadows, post effects, alpha |
| Info | Mostly unshaded data passes | Masks, depth, normals, driving effects |
| Denoised | Denoised versions of beauty passes from the Spectral AI Denoiser | Clean stacks for comp |
| Output AOVs | Composites built inside Octane from Render AOVs | Real-time compositing and multiple composites per scene |
2. How to set up Octane AOVs and composite them (step by step)
Settings checklist (follow line by line):
Choose one stack ........ beauty AOVs OR light AOVs, not both
Render Settings > Octane Renderer
Render AOV Manager .... add the beauty AOVs: diffuse, reflection,
refraction, transmission, SSS, emitters,
environment, post processing
Raw ................... only if you will multiply by filter AOVs
Light stack ........... Light pass ID on every Octane Light tag,
one Light AOV per ID, Ambient for an HDRI
Masks ................. Cryptomatte AOV
Render AOV Group ...... Enable ON, format EXR (Octane), not C4D EXR
Compositor .............. start from black, Add/Plus every AOV
Raw AOV ............... × matching filter AOV first
Step 1: Choose a stack
Decide whether you will grade by material component (beauty AOVs) or by light (light AOVs). Pick one; adding both counts the same light twice.
Step 2: Add the beauty AOVs
Current Octane for Cinema 4D uses an AOV system that replaced the older Render Passes (OTOY: AOV Introduction). Add the AOVs you need in Render Settings > Octane Renderer > Render AOV Manager (OTOY: Render AOV Checklist for Post). An older scene that still uses Render Passes can be converted with Convert Render Passes to AOVs in the Render AOV Group tab (OTOY: Render AOV Group tab). Turn on Raw only if you plan to change lighting separately from surface color: it is a toggle in the AOV parameters that converts the beauty AOVs to raw by factoring out the color of the surface hit by the camera ray (OTOY: Render AOV Group tab).
Step 3: Set Light pass IDs for a light stack
Each light gets a Light pass ID in its Octane Light tag; lights with the same ID end up in the same light AOV (OTOY: Octane Light Tag). Add one Light AOV, or a Light Direct and Light Indirect pair, for every ID you use, and if an HDRI lights the scene add a light AOV set to Ambient (OTOY: Render AOV Checklist).
Step 4: Add Cryptomatte for masks
For object or material masks, add a Cryptomatte AOV under Add Render AOV > Auxiliary > Cryptomatte. OTOY notes that Cryptomattes only render correctly in the EXR (Octane) format, and the Enable toggle in the Render AOV Group tab must be on (OTOY: Cryptomatte). For a full matte workflow see our guide to Octane Cryptomatte in Cinema 4D.
Step 5: Save one multilayer EXR (Octane)
In the Render AOV Group tab, set the path and choose EXR (Octane), not Cinema 4D’s own EXR: OTOY explains that Cinema 4D does not correctly write certain parts of the EXR format that Octane relies on (OTOY: C4D Octane plugin overview). If you also use this output for the final beauty, enable Save Beauty (OTOY: Render AOV Manager tab). Keep the data linear so the compositing math works. OTOY notes that 32-bit EXR is maximum quality but makes the files quite large, so check the bit depth before a long sequence (OTOY: Render AOV Group tab).
Step 6: Rebuild
Add the AOVs from black. With Raw AOVs, multiply each by its matching filter AOV first (OTOY: Beauty Passes, raw and filter).
Step 7: Verify, then grade
Compare the rebuild with the beauty using a wipe, and only then start adjusting individual AOVs.
3. Rebuild the AOVs in Nuke, After Effects or Fusion
Every compositor does the same math: split the multilayer EXR into one image per AOV, multiply each raw AOV by its filter AOV if you rendered raw, add everything together from black, then compare the result with the beauty. Only the tools differ.
Nuke
- Read the EXR (Octane) file with one Read node; all AOVs come in as layers of that one node.
- Split each AOV out with a Shuffle2 node. Foundry notes that Nuke 12.1 introduced Shuffle2, which makes the old Shuffle and ShuffleCopy obsolete (Foundry: ShuffleCopy).
- Combine raw and filter AOVs with a Merge set to multiply, then chain the results with Merge nodes set to plus, the same pattern Foundry uses in its own beauty-rebuild example (Foundry: Channels).
- Leave the Read node in linear, Nuke’s default for EXR, and wipe-compare the rebuild with the beauty (Maxon: AOV Tutorial).
After Effects
- Import the EXR sequence and duplicate the layer once per AOV.
- On each copy, apply the EXtractoR effect and pick one AOV layer. Adobe ships EXtractoR and IDentifier, from fnord software, with After Effects for multichannel EXR files (Adobe: 3D Channel effects).
- Set every AOV layer above the bottom one to the Add blend mode, so the stack sums from black like the Plus merge in Nuke.
- Toggle the original beauty on top to compare. If the sum is brighter or darker, check the project’s color settings before blaming the AOVs: compositing EXR data in the wrong color space gives wrong results.
Fusion (Fusion Studio or the Fusion page in DaVinci Resolve)
- Add one Loader per AOV. A single Loader outputs only one set of RGBA channels, so each pass needs its own Loader; the EXR file is only read once even with many Loaders (Fusion 18 manual: beauty passes).
- In each Loader’s Format tab, map the AOV’s channels to red, green and blue (Resolve 18 manual: multi-part EXR).
- Combine the Loaders with Merge nodes, or Channel Booleans, set to an additive mode; the manual notes both allow additive combining of render passes (Resolve 18 manual: combining passes).
- Compare with the beauty in the viewer’s A/B buffers before grading.
Prefer to stay in Octane? Output AOVs let you build the composite inside Octane itself, in real time (OTOY: AOVs and Composites).
4. Why does the Octane comp not match the beauty?
- Double counting: adding a combined pass and its direct and indirect parts, or mixing the beauty and light stacks.
- Missing Post Processing pass: bloom and glare live in their own pass and must be added.
- Raw without filter: raw passes look flat and grey until multiplied by their filter pass.
- Saved as Cinema 4D’s EXR: AOV layers or Cryptomatte data are missing or wrong; save with EXR (Octane).
- Empty light AOV: the light has no Light pass ID, or no light AOV uses its ID; an HDRI needs a light AOV set to Ambient.
- Noisy masks or data AOVs: info AOVs are sampled separately, up to the Max Info Samples value, because they usually need fewer samples than the beauty; raise it if mask edges look rough (OTOY: Render AOV Manager tab).
- Wrong color space: treat EXR data as linear in the compositor.
- Noise: pass-level noise shows when you push a single pass; use the denoised passes from the Spectral AI Denoiser (OTOY: AI Denoiser).
OTOY also documents a reconstruction formula for the beauty passes in its other host manuals (OTOY: Beauty Passes, reconstruction), and the same additive logic applies in Cinema 4D.
5. SaaS or IaaS render farm for pass-heavy Octane shots?
Both kinds of render farm write the same AOVs, because the AOV list, Light pass IDs and output format are saved in the .c4d file. What differs is where you prove that the AOVs rebuild the beauty, and how many rounds that takes. A first AOV setup usually needs a few: a missing Post Processing AOV, a light without an ID or the wrong EXR writer only shows up when you rebuild a real frame.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| The AOV list and comp are already approved on your workstation | A good fit. Upload the scene and the farm renders the EXR sequence, often spread across many machines, with no server to manage. | Also works, but you start, use and stop the server yourself. |
| You still need to prove the AOVs add up to the beauty | Each check is a job: render a test frame, download the EXR and rebuild it in your compositor at home. | Render one frame on the server, rebuild it with Octane’s Output AOVs or a compositor you install there, fix the AOV list and render the frame again. |
| Many AOVs at 4K or higher resolution | Depends on the GPU memory of the farm’s machines; check their specs before you submit. | Each beauty AOV needs its own film buffer on the GPU, so test the full AOV list at final resolution on RTX 5090 cards with 32 GB per GPU. |
| Light pass IDs, Cryptomatte or custom AOVs to check | Set and verify them at home before you upload. | Open the scene on the server, check every Octane Light tag ID and the Cryptomatte AOV, and fix them in place. |
| Large multilayer EXR frames | Frames come back through the farm’s download system. | Frames are written to the server’s 2 TB NVMe SSD; check a few in comp there, then move them with iRender Drive. |
A comparison of how the two farm models work for this task, not a speed test. A SaaS farm takes your project as a job and renders it on its own pipeline; an IaaS farm rents you the whole server and you work on it over remote desktop. Film buffer note: OTOY, Beauty Passes (Cinema 4D).
A simple rule: if you can rebuild a test frame at home and it matches the beauty, either model will render the sequence correctly. If you still need to prove the setup, or your own GPU cannot render a frame with the full AOV list at final resolution, an IaaS server lets you test, rebuild and render in one place, on the same hardware.
A test workflow on an iRender server
- Upload the project to iRender Drive before you start the server, so upload time is not billed.
- Start a 4x or 8x RTX 5090 server (packages 5i or 9i); both are billed per minute. Sign in with your OTOY account.
- Check the AOV list, every Light pass ID and the output format, EXR (Octane).
- Render one frame at final resolution and rebuild it, with Output AOVs in Octane or in your compositor, then compare it with the beauty.
- Fix the AOV list and render that frame again until it matches; note the per-frame time.
- Render the sequence. For a tight deadline, rent several servers and give each one part of the frame range; with per-minute billing the total cost stays about the same while the wait gets shorter.
Frequently asked questions
1. How do I rebuild the beauty from Octane AOVs?
Start from black and add the beauty AOVs together with an Add or Plus blend: diffuse, reflection, refraction, transmission, SSS, emitters and environment, plus the Post Processing AOV if bloom or glare is used. Compare the result with the beauty render.
2. What does the Raw option do for Octane beauty AOVs?
Raw divides out the color of the surface hit by the camera ray, so the AOV holds only lighting. To get the full result back, multiply each raw AOV by its matching filter AOV.
3. Why is my Octane AOV composite brighter than the render?
A common cause is adding both the beauty-surfaces stack and the lighting stack, or adding a combined AOV and its direct and indirect parts together. Use one stack and one level of detail.
4. Do Octane beauty AOVs use more VRAM?
Yes. OTOY notes that each beauty pass needs its own film buffer stored on the device in addition to the main buffer, so many AOVs at high resolution increase memory use.
5. Why are AOV layers or Cryptomatte missing from my EXR?
Check the output format. OTOY says Cryptomattes only render correctly in the EXR (Octane) format and that Cinema 4D does not correctly write certain parts of EXR that Octane relies on. Also make sure Enable is on in the Render AOV Group tab.
6. Can I composite inside Octane instead of Nuke or After Effects?
Yes. Octane’s AOV compositing system with Output AOVs allows real-time compositing with color adjustments, blur, glows and more, and a scene can have several composites.
7. Can I get denoised AOVs in Octane?
Yes. The Spectral AI Denoiser writes denoised versions of beauty passes into separate AOVs when it is enabled.
Render your Cinema 4D + Octane AOV shots on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 or RTX 5090 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. Cinema 4D and OctaneRender are installed; sign in with your own OTOY account (OTOY’s Studio+ plan has no GPU limit for multi-GPU servers). Your server image is saved between sessions.
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, so they keep their boost clocks. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start Cinema 4D and Octane on an iRender server:
On a 4x RTX 5090 server, a 300-frame Cinema 4D + Octane animation rendered in 1 hour 18 minutes. The second clip runs the same kind of scene on 4x RTX 5090 and 4x RTX 4090:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Octane render farm page, download the iRender GPU app, or read Redshift AOV compositing in Cinema 4D.
Sources: OTOY: Render Series, Render Passes, OTOY: Render AOV Checklist for Post, OTOY: AOV Introduction (C4D), OTOY: AOVs and Composites (C4D), OTOY: Render AOV Manager tab, OTOY: Render AOV Group tab, OTOY: Beauty Passes (C4D), OTOY: Beauty Passes, raw and filter, OTOY: Beauty Passes, reconstruction, OTOY: Octane Light Tag, OTOY: Cryptomatte (C4D), OTOY: C4D Octane plugin overview, OTOY: AI Denoiser, Foundry: Shuffle2 / ShuffleCopy, Foundry: Channels (beauty rebuild example), Maxon: AOV Tutorial (Nuke rebuild), Adobe: 3D Channel effects (EXtractoR), Blackmagic Fusion 18 manual.




