Cinema 4D Takes and Tokens with Redshift (2026): Output Paths for Multi-Camera, Multi-Format Renders and AOVs
Give every take its own folder by putting tokens in the save path, such as renders/$take/$camera/$prj. Cinema 4D replaces each token at render time and creates the folders. Then check that Redshift Direct Output AOVs follow the same path.
- Tokens: $take, $camera, $rs, $res, $prj and $pass are replaced at render time.
- Folders: the last token is the file name; earlier tokens become folders, created if missing.
- Redshift AOVs: Direct Output has its own path per AOV; the AOV name becomes the $pass token.
- Rendering: render all or marked takes from the Take Manager, or add them to the Render Queue as separate jobs.
Takes let one Cinema 4D scene hold many versions of a shot: different cameras, aspect ratios, materials or render settings. The catch is the output path. If every take writes to the same path with the same file name, each take overwrites the last one. Cinema 4D’s tokens solve this by turning parts of the path into variables that change per take.
This guide lists the tokens that matter for multi-take work, gives a path pattern that keeps every take separate, explains how Redshift’s Direct Output AOVs fit in, and shows how to render many takes at once.
Checked against Maxon’s Cinema 4D documentation for Tokens, the Take Manager and the Render Queue, and Maxon’s Redshift AOV documentation, November 2026.
1. Why do multi-take renders overwrite each other?
Because takes share the scene’s output path unless something in the path changes per take. If the path is a fixed name, every take writes the same file names to the same folder. Put tokens such as $take and $camera in the path, and Cinema 4D replaces them with the take and camera names at render time, so each take lands in its own place.
Maxon’s token documentation adds two rules that make this work: the last token in a path is always the file name, and the tokens before it become folder names, which Cinema 4D creates if they do not exist.
How to read the figure. The left panel is the usual cause of lost renders: both takes resolve to the same file, so whichever take renders last wins and nothing warns you. The right panel uses the same scene with a tokenized path, and the two takes can no longer collide.
Cinema 4D tokens for multi-take output
Tokens Maxon documents for render paths, and what each is good for.
| Token | Replaced with | Use it for |
|---|---|---|
| $take | Current take name | A folder per take |
| $camera | Current camera name | A folder or suffix per camera |
| $rs | Current render setting name | Separating formats or quality presets |
| $res | Image resolution, e.g. 800X600 | Separating aspect ratios |
| $prj | Scene file name | A readable file name |
| $pass | Multi-pass or AOV name | A folder or suffix per pass |
| $take_hierarchy | Parent take names joined by _ | Nested take setups |
2. Which save path keeps every take separate?
A path such as renders/$take/$camera/$prj works for most projects: one folder per take, one subfolder per camera, and the scene name as the file name. Cinema 4D adds frame numbers to image sequences. Tokens can be used in the Render Settings Save tab, in the Render Queue’s output path, and in the -oimage and -omultipass command-line options.
Keep the path relative to the project, or point it at a folder that exists on every machine that renders the scene, so the same scene file works on your workstation and on a render server.
How to read the figure. The figure shows what Cinema 4D builds from that one path. Every token before the last becomes a folder, and Cinema 4D creates missing folders at render time, so you never prepare them by hand. Redshift AOVs left on their default Direct Output path follow the main save path, so they land in the same take and camera folders as the beauty.
Practical tip: keep take and camera names short and free of spaces and slashes, because they become folder names. A take named “Wide 4K / final” makes a path that is hard to read and to script against.
3. How do Redshift AOVs fit into a tokenized path?
Redshift can write AOVs through Cinema 4D’s Multi-Pass system, through its own Direct Output, or both. Maxon notes that Direct Output gives per-AOV save options and consistent output across Redshift DCCs, and that the name you give each AOV is used as the $pass token in its path. If both systems are enabled on the same AOVs, both sets of files are written.
On a Maxon developer forum example, the Direct Output path of an AOV is shown as $filepath$filename_$pass, built from the main save path (developer forum). If an AOV path was typed as a fixed folder instead, it will not follow your takes; add $take to it, or return it to the default.
4. How do you render many takes in one go?
Use the Take Manager’s Render menu to render all takes or only the marked ones in the Picture Viewer, or send them to the Render Queue. Maxon’s Render Queue documentation says its Open With All Takes and Open With Marked Takes commands add each take as a separate job; if no take is marked, the Main take is used. The Queue renders saved scenes only, so save before you start.
Step 1: Set the save path once
In the Render Settings Save tab, use a tokenized path such as renders/$take/$camera/$prj for the image, and a matching path for multi-pass if you use it.
Step 2: Check the Redshift AOV paths
Open the Redshift AOV Manager and make sure each Direct Output AOV uses the default path built from the main save path, or contains $take.
Step 3: Render one frame per take
Render a single frame of every take and check that each lands in its own folder with the expected AOVs beside it.
Step 4: Queue the takes
Save the scene, then render all or marked takes from the Take Manager, or add them to the Render Queue with Open With All Takes.
How to read the figure. The badges follow Steps 1 to 4 above. Badge 1 is the tokenized Regular Image path in Render Settings › Save, badge 2 is a Direct Output AOV path in the Redshift AOV Manager, badge 3 is a test frame landing in its own take and camera folder, and badge 4 is Render All Takes in the Take Manager, with the Render Queue as the alternative. The take and camera names are examples.
Rendering the takes from the command line
The Cinema 4D Commandline renderer can render one take per call with -take, so a short batch file renders every take in the background with the save path already set in the scene (Maxon: Cinema 4D and the Command Line).
Because the save path holds $take and $camera, each call writes to its own folder. Save the scene before you run the file; the command line renders the saved version.
Common take and token problems
- Takes overwrite each other: the save path has no $take. Add it to the Regular Image path, and to the Multi-Pass path if you use one.
- All AOVs end up in one folder: a Direct Output path was typed as a fixed folder. Return it to the default, built from $filepath and $filename, or add $take.
- The Render Queue ignores your latest change: the Queue renders saved files. Save the scene, then add the takes again.
- Each AOV appears twice: both Multi-Pass and Direct Output are enabled for the same AOVs. Keep one unless you need both.
Sources: Maxon: Variable Path and File Names (Tokens); Maxon: Render Queue; Maxon: Redshift Intro to AOVs.
Checklist: multi-take output
Tick each line before you queue the takes.
5. When does a multi-GPU server help with multi-take renders?
Takes multiply the work: five formats of a 300-frame shot are 1,500 frames. Redshift renders each frame on all the GPUs in a machine, so a 4- or 8-GPU server shortens every frame of every take, and the tokenized path keeps the results sorted.
A SaaS render farm renders submitted jobs with its own setup, which suits scenes whose takes and paths are final. An IaaS server is a whole machine you control: you open the scene in Cinema 4D, check each take and its paths, and render the queue as on your workstation.
SaaS or IaaS render farm for multi-take renders?
Both farm models can render every take once the save paths hold $take and $camera. The difference is how you check that each take lands in its own folder before the long renders start.
Rendering many Cinema 4D takes on a farm
How the two farm models fit depending on how ready the takes are.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| Paths are tokenized and every take is tested | A good fit: upload and the farm renders the takes across its nodes | Works as well: render all takes from the Take Manager on 2x to 8x GPUs |
| You want to see one frame of every take first | Usually a test job, then the full job | Render one frame per take on the exact server and check the folders |
| Your takes use your own plugins or scripts | Check that the farm supports each one | Install them yourself; they stay on your server between sessions |
A test workflow on an iRender server
How to read the figure. The top row is the setup: your own PC or Mac connects by remote desktop to a whole bare-metal server with 1, 2, 4 or 8 GPUs, so you open your Cinema 4D and Redshift project there exactly as at home. The numbered row is the order of a session: register and top up, upload to iRender Drive before the server runs, start and connect, render a test frame and the job, then shut down so billing stops.
- Upload the project to iRender Drive before you start the server; uploading is free and does not use rental time.
- Start a server with 2, 4 or 8 RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs. Cinema 4D and Redshift are pre-installed.
- Render one frame of every take and check that each lands in its own folder with its AOVs.
- Render all takes from the Take Manager or the Render Queue, then shut down; billing is per minute.
Frequently asked questions
1. Why do my Cinema 4D takes overwrite each other when rendering?
All takes write to the same output path unless the path contains something that changes per take. Add the $take token to the save path, for example renders/$take/$camera/$prj, so each take gets its own folder.
2. Which tokens can I use in Cinema 4D render paths?
Maxon lists tokens such as $prj, $camera, $take, $rs, $res, $pass, $frame and $take_hierarchy. They work in the Render Settings Save tab, the Render Queue output path and the -oimage and -omultipass command-line options.
3. Does Cinema 4D create the folders in a token path?
Yes. The last token is the file name and earlier tokens become folder names; Maxon says Cinema 4D creates those folders if they do not already exist.
4. How do Redshift Direct Output AOVs use tokens?
Each Direct Output AOV has its own path, and the AOV name is used as the $pass token. By default the path is built from the main save path, so tokens there carry over; a fixed path will not follow your takes.
5. Should I use Multi-Pass or Direct Output for Redshift AOVs?
Maxon notes that Direct Output offers per-AOV save options, Deep EXR support and output consistent with other Redshift DCCs. If you enable both on the same AOVs, both sets of files are written.
6. How do I render all takes at once?
Use the Take Manager’s Render menu to render all or marked takes in the Picture Viewer, or add them to the Render Queue with Open With All Takes or Open With Marked Takes, which creates one job per take.
7. Can I render many takes on an iRender server?
Yes. Cinema 4D and Redshift are pre-installed. Render one frame per take to check the paths, then render all takes on 2, 4 or 8 GPUs. Billing is per minute.
Render your Cinema 4D 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. 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.




