November 18, 2026 Maddie Quach

Maya Render Setup Layers with Redshift AOVs: Multi-Part EXR, Light Groups and Output Names

Layers & AOVsRender layers and AOVs for Maya + Redshift
From Autodesk and Maxon documentation

Render Setup splits a shot into layers; Redshift AOVs split each layer into passes. Check these before a batch:

  • Overrides: Render Settings and AOVs opened while a layer is selected show that layer’s settings
  • AOV tab: Redshift AOVs live in the Redshift Render Settings; Batch Only skips them in interactive renders
  • Multi-Part EXR: set in Maya’s Common tab; stores all AOVs of a layer in one EXR per frame
  • File names: <RenderLayer> and <Scene> tokens keep layers apart
  • Batch: -rl renders a named layer; -im sets the file name prefix

Compositing-heavy Maya shots usually combine two systems: Render Setup layers to split characters, environment and effects, and Redshift AOVs to split each layer into lighting, utility and matte passes. Set up well, the result is a tidy folder of EXRs that a compositor can rebuild; set up loosely, it is thousands of files with names that collide between layers.

This guide covers how Render Setup layers and Redshift AOVs work together in Maya, how to set them up step by step, how file naming and Multi-Part EXR keep the output manageable, and how to render one layer at a time from the command line.

Checked against Autodesk Maya documentation (Render Setup, render tokens, command-line rendering) and Maxon Redshift for Maya AOV documentation, November 2026.

1. How do Render Setup layers and Redshift AOVs fit together?

A Render Setup layer decides what renders and with which overrides. In Autodesk’s words, if you open the Render Settings while viewing a layer, that layer’s settings are shown, and the same applies to AOVs and lights; you create Render Settings, AOV or light overrides there (Autodesk: Render Setup editor). Redshift AOVs then decide which passes each layer writes: Maxon describes integrated AOVs for shading elements and light group AOVs for per-light control in post (Maxon: Intro to AOVs (Maya)).

iRender
Render Setup Layers, Redshift AOVs and the Files They Produce
Schematic
shot010.mbRender SetupLayer: charscharacters, own overridesLayer: envset and skyBeautyDiffuse LightingSpecularCryptomatteLight groupsBeautyDiffuse LightingSpecularCryptomatteLight groups5 AOVs per layerMulti-Part EXR: ON1 file per layer per frame2 layers × 240 frames = 480 filesMulti-Part EXR: OFF1 file per AOV per layer per frame2 × 5 × 240 = 2,400 filesFile names: <RenderLayer>/<Scene> in the File name prefix keeps each layer in its own folder
render layerAOVfile count
Schematic · example counts; settings from Autodesk and Maxon docs

The file count is where the two multiply. In the example, two layers with five AOVs over 240 frames are 480 files with Multi-Part EXR on, or 2,400 with it off. Maxon places the Multi-Part EXR option, with its depth, compression and storage settings, in Maya’s Common tab; by default Redshift AOVs use scanline storage (Maxon: AOV – Production (Maya)).

2. How to set up layers and AOVs (step by step)

Settings checklist (copy or follow line by line):

Settings checklist
Render Setup editor
Layers → one per element (chars, env…) with collections and overrides
Overrides → open Render Settings / AOVs while a layer is selected to override per layer
Render Settings › Redshift › AOV
AOV mode → Enabled, or Batch Only to skip AOVs in interactive renders
AOVs → Beauty, lighting AOVs, Cryptomatte, light group AOVs
Render Settings › Common
File name prefix → <RenderLayer>/<Scene>
Multi-Part EXR → On // one EXR per layer per frame
Depth → Half Float for color, Float for data passes
Check → one frame per layer opened in comp

Step 1: Build the layers

In the Render Setup editor, create one layer per element you will composite separately, add collections for the objects, and create overrides for anything that differs per layer, such as visibility or a light’s intensity.

Step 2: Add the AOVs

In the Redshift Render Settings, open the AOV tab and add the AOVs your compositor needs: lighting AOVs, Cryptomatte and light group AOVs. With the AOV mode set to Batch Only, AOVs render only in batch renders (Maxon: AOV settings), which keeps interactive look-dev faster.

Step 3: Name the files

In the Common tab, set the File name prefix with tokens: <RenderLayer> adds the layer name and <Scene> the scene name, and a slash creates subfolders (Autodesk: Subfolders and names of rendered images).

Step 4: Turn on Multi-Part EXR

Enable Multi-Part EXR, choose Half Float for color passes or Float for data passes, and pick a compression. For how Cryptomatte and multi-part EXRs behave in compositing, see our Redshift multi-layer EXR and Cryptomatte guide. For the color space those EXRs are written in, see ACES 2.0 and OCIO in Maya 2026 with Redshift.

Step 5: Check one frame per layer

Render one frame of every layer and open it in your compositor before the full range.

3. Rendering layers from the command line

Batch rendering splits naturally by layer. Autodesk’s common flags include -rl to render render layers separately and -im for the image file name, which can carry the same tokens as the Common tab (Autodesk: command-line flags; Autodesk: render tokens). First find the exact layer names:

iRender
Find the exact render layer names
python
1# 1) in Maya's Script Editor (Python): list the render layer node names
2import maya.cmds as cmds
3print(cmds.ls(type="renderLayer"))
Use the names it prints with -rlAutodesk: Maya command-line rendering

Then render one layer per command, so each layer can go to a different GPU group or machine and be re-rendered on its own if a note comes back:

iRender
Render one Render Setup layer in a batch
cmd
1:: 2) render one layer from the command line, one folder per layer
2"C:\Program Files\Autodesk\Maya2026\bin\Render.exe" -r redshift -rl chars -s 1 -e 240 -proj "D:\proj" -rd "D:\proj\images" -im "<RenderLayer>/<Scene>" -log "D:\proj\logs\chars.txt" "D:\proj\scenes\shot010.mb"
Replace chars with a name from step 1Autodesk: -rl, -im flags and render tokens

Keep the File name prefix in the scene and the -im on the command line the same, so interactive and batch renders write to the same folders.

iRender
One batch per Render Setup layer with -rl
Schematic
1 · List layer namescmds.ls(type="renderLayer")File name prefix (Common tab)<RenderLayer>/<Scene>a slash makes a subfolder2 · Batch, layer charsRender -r redshift -rl chars shot.mb2 · Batch, layer envRender -r redshift -rl env shot.mbchars/shot.1001.exr …env/shot.1001.exr …Use the same tokens with -im on the command line, so batch and interactive renders write to the same folders.Split the batch by layer, and let the prefix tokens keep the files apartAutodesk: command-line flags (-rl, -im); Subfolders and names of rendered images
Command lineFiles written
Schematic, not to scale

4. Light groups and AOV clamping in Maya

Light group AOVs give per-light control in comp without a re-render. The setup idea is the same as in Cinema 4D: name lights into groups, add a light-group-capable AOV such as the beauty, and check that the groups plus the remainder add up to the beauty; our Redshift light groups guide walks through it. Maxon also notes that Redshift’s Output and AOV tabs can clamp color and AO AOVs separately from the beauty (Maxon: Intro to AOVs (Maya)), so a clamped AOV may not sum exactly to an unclamped beauty.

TroubleshootSymptom to setting

When layers or AOVs come out wrong

Based on Autodesk and Maxon documentation

SymptomLikely causeFix
Layers overwrite each otherNo <RenderLayer> token in the file nameAdd it to the File name prefix and -im
AOVs missing in an interactive renderAOV mode set to Batch OnlyExpected; render in batch, or set Enabled
A layer renders the wrong camera or settingsOverride created on the wrong layerOpen Render Settings with that layer selected and check overrides
Comp does not match the beautyAOVs clamped separately from the beautyCheck AOV clamping in the Output and AOV tabs
Too many files to manageMulti-Part EXR offTurn it on in the Common tab
-rl renders nothingLayer name does not matchList names with cmds.ls(type="renderLayer")

For rebuilding the beauty from Redshift AOVs in comp, see our Redshift AOV compositing guide.

5. SaaS or IaaS render farm for layered Maya shots?

CompareNeutral guide

Which farm type fits a layered Maya shot

Both farm types render Render Setup layers; the difference is control over how layers are split.

SituationUsually a better fitWhy
Standard layers and AOVs, one submitSaaSThe farm’s submitter handles layers and collects the files
Layers split across GPU groups or machines with your own commandsIaaSYou run Render.exe with -rl exactly as you want
Re-rendering one layer after notesEitherBoth can render a single layer; check naming first
Studio pipeline with its own submit toolsEitherPick the farm that supports your submit workflow

Rule of thumb: if the layer split is standard, a submitter is simplest; if you script the split per layer and per GPU, a machine you control fits better.

Rendering layered Maya shots 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

An iRender server is a full Windows machine, so Render Setup and Render.exe behave as on your workstation:

  1. Upload the project to iRender Drive before you start a server; uploading is free and does not use rental time.
  2. Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs, install your Maya version and the matching Redshift build once. Setup details are in Redshift for Maya on a multi-GPU render server.
  3. Render one frame per layer, open the EXRs in your compositor and check names and passes.
  4. Render each layer with Render.exe -rl, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.

Maya layers and AOVs checklist

Tick each item before you start the full range.

ChecklistMaya layers and AOVs checklist
0 / 10 done
Tip: tick each item as you set up the job; the ticks reset when the page reloads.

Frequently asked questions

1. How do I give each Render Setup layer its own Redshift settings?

Select the layer in the Render Setup editor and open the Render Settings or AOVs from there; Autodesk notes the settings shown are that layer’s, and changes become layer overrides.

2. How do I stop layers from overwriting each other’s files?

Add the RenderLayer token to the File name prefix in the Common tab, for example RenderLayer/Scene with a slash for subfolders, and use the same prefix with -im in batch renders.

3. Where is the Multi-Part EXR option for Redshift in Maya?

Maxon places it in Maya’s Common tab, with depth (Half Float or Float), compression and storage settings. It writes all AOVs of a layer into one EXR per frame.

4. Why do my AOVs not appear in the Render View?

The AOV mode may be set to Batch Only, which renders AOVs only in batch renders. Set it to Enabled if you need them interactively.

5. How do I render only one layer from the command line?

Use Render.exe with -rl followed by the layer name. List the exact names in Maya with cmds.ls(type=”renderLayer”).

6. Why does my comp not add up to the beauty?

AOVs can be clamped separately from the beauty in Redshift’s Output and AOV tabs. Check the clamping settings, and make sure light groups plus the remainder are all rendered.

7. Should I use Cryptomatte or ID passes?

Cryptomatte gives per-object and per-material mattes without setting up IDs by hand; add it as a Redshift AOV and check one frame in your compositor.

8. Can I render layered Maya shots on a multi-GPU iRender server?

Yes. iRender servers have 1, 2, 4 or 8 RTX 5090 or RTX 4090 GPUs; you install Maya and Redshift once and render each layer with Render.exe as on your workstation.

Render your Maya and Redshift projects 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. Maya is not pre-installed: you install the Maya version your scene uses with your own Autodesk license, and it stays in your image. Prime accounts get Redshift licenses pre-activated 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 connect to it:

A full Maya and Redshift session we recorded on an 8x RTX 4090 server:

New users get a 100% bonus on the first top-up (minimum $50). See plans on the Maya render farm for Redshift 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:
, , , , , , ,

Maddie Quach

Maddie Quach, from iRender's customer support team, has written more than 100 articles for the iRender blog on Maya, Houdini, Arnold, Karma XPU and Redshift.
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
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →