Octane Takes and Output Paths in Cinema 4D: Render Passes Without Overwrites
Octane writes its own files, separately from the Cinema 4D Save tab. Set these before a batch:
- Octane path: set the Render Pass File in the Render AOV Group tab and enable Save Beauty
- C4D Save: turn Save and Multi-Pass save off, but keep the Multi-Pass toggle on
- Tokens: put $take (and $camera if needed) in the path so takes do not overwrite each other
- Format: EXR(Octane) for multilayer passes and Cryptomatte
- Test: render two frames of every take and check every file name
Takes let one Cinema 4D file hold several cameras, product colours or lighting versions, and the Render Queue can render them all overnight. With Octane there is a trap: Octane saves its beauty and passes through its own file path, not through the Cinema 4D Save tab, so a path that works for one take can make every take overwrite the same files.
This guide explains where Octane writes its output, why OTOY advises against the Cinema 4D save route, how to use tokens such as $take in the path, and how to check a batch before it runs all night.
Checked against the OctaneRender for Cinema 4D manual (plugin overview, Render AOV Group tab), OTOY’s Render AOV checklist and Maxon’s Render Settings Save documentation, November 2026.
1. Where does Octane save its output in Cinema 4D?
Octane for Cinema 4D can save through two routes: the standard Cinema 4D Save tab, or its own file options in Render Settings > Octane Renderer > Render AOV Group. OTOY recommends the second. Its plugin overview explains that Cinema 4D’s save routines can interfere with file types Octane users rely on, and lists known problems: unwanted response curves, incomplete AI Denoiser output, incomplete or corrupted multilayer EXR files and issues with some EXR compression options. With its own path, Octane writes files directly to disk without Cinema 4D in between.
The settings that make this work, from OTOY’s pages:
- Render Pass File: the path and name for Octane’s output, set with the ellipsis button.
- Save Beauty: must be enabled if Octane’s path is your final beauty output.
- Multilayer File: TIFF, PSD, EXR and EXR(Octane) can hold all passes in one file; turn it off to get the Folders option, which writes each pass into its own folder.
- Separator: the characters between the file name and the frame number, an underscore by default.
In the Cinema 4D Save tab, turn Save and the Multi-Pass save options off, but keep the Multi-Pass toggle enabled: OTOY says that toggle is the only way Octane can save multipass files. Our guide to Octane AOVs for compositing covers which passes to enable.
2. Tokens: one path for every take and camera
Cinema 4D tokens are variables in a file path that are replaced at render time. Maxon’s documentation uses the example Results/$take/$rs: the last token becomes the file name and the earlier ones become folders, which Cinema 4D creates if they do not exist yet.
Cinema 4D tokens that keep Octane output apart
From Maxon’s Render Settings Save documentation; test each one in a short render.
| Token | Becomes | Use it to separate |
|---|---|---|
| $prj | the project (.c4d) file name | output of different scene files |
| $take | the active take name | takes rendered in one batch |
| $camera | the camera name | multi-camera renders |
| $rs | the render setting name | versions that use different render settings |
| $res | the output resolution | the same shot at several sizes |
Token support in the Octane pass path arrived years ago, and the Octane plugin developer has recommended using tokens there rather than routing passes through the Cinema 4D Save tab. Because the Octane path and the Cinema 4D path are separate fields, put the tokens in the Octane Render Pass File path itself; a token only in the Cinema 4D Save tab does nothing for Octane’s files.
Why $take matters
Without a take token, every take resolves to the same path, and the last take to render wins. With $take in both the folder and file name, each take writes its own set of frames.
For product configurators and multi-camera shots, add $camera or $rs as needed. Keep paths short and avoid spaces in take names; they become folder and file names.
3. Takes that need different Octane settings
A take can switch the render setting it uses, and each render setting has its own Octane Render AOV Group with its own path. That gives a second way to separate output: one render setting per take, each with a fixed path. Before token support was reliable, this was the workaround users on OTOY’s forum described, and it is still useful when takes need different passes, kernels or resolutions.
Takes also change scene preparation. On OTOY’s forum, users have reported longer preparation per frame when takes switch scene content; rendering each take as its own Render Queue job keeps that cost predictable. See why Octane gets slower each frame for measuring it.
4. Test the batch before the overnight run
OTOY’s Render AOV checklist adds two practical points. If you render from the Live Viewer with Save image sequence, the Cinema 4D frame range must cover at least two frames; with a single frame set, OTOY notes that Octane renders every frame. And the Picture Viewer route supports tokens, which makes it the safer choice for batches.
Before starting the full Render Queue, render two frames of every take and check the output folders:
- one folder or file set per take, with the expected names;
- frame numbers after the separator, in the right padding;
- the beauty file present, and the denoised beauty if you use the denoiser (OTOY adds the suffix DeMain before the frame number);
- every enabled pass, either as layers in the EXR or as folders.
5. Render every take from the command line
The Render Queue is convenient on a workstation; on a render machine, a batch file is easier to restart and leaves a log per take. Maxon’s Commandline renderer, installed next to Cinema 4D, takes the arguments needed for this:
-renderwith the scene path, and-takewith a take name to render that take instead of the main scene;-framewith start, end and step;-noguito start without the interface, which Maxon recommends for render farms;g_logfileto save the console output and render progress to a text file.
OTOY documents background Octane rendering with the same Commandline application, with a g_modulePath argument so the plugins folder is loaded, and notes that it needs a valid command line license. In a .bat file every % in that argument is doubled:
Edit the take names to match the Take Manager exactly, including capitals. Run the file once with -frame 0 1 1 to check every take before the full range, then look at the logs: a take that stops early shows the reason at the end of its own file.
Sources: Maxon: Cinema 4D and the Command Line, Maxon: Understanding Commandline Rendering Arguments, OTOY: Command Line Rendering.
6. SaaS or IaaS render farm for multi-take Octane batches?
Which farm type fits a Takes-based Octane job
Both render takes; the difference is how the output paths are checked.
| Situation | Usually a better fit | Why |
|---|---|---|
| Paths and takes already tested at home | SaaS (managed farm) | Submit the Render Queue as is |
| Paths use tokens you have not tested | IaaS (remote workstation) | Render two frames per take and inspect the folders |
| Absolute paths pointing at your local drive | IaaS | Change them to the server drive in one pass |
| Each take needs different render settings | IaaS | Check every render setting’s Octane path |
| Short one-off still | SaaS | No setup time |
Rule of thumb: if every take already writes to its own path at home, either type works. If paths are absolute or untested, fix and test them on the render machine first.
Rendering Octane Takes on an iRender server
On iRender you rent a whole Windows workstation with Cinema 4D and OctaneRender installed and sign in with your own OTOY account:
- Upload the project and textures through iRender Drive.
- Start a 2x, 4x or 8x RTX 5090 server and open the scene.
- Point the Octane Render Pass File path at a folder on the server, with $take in it, and turn off the Cinema 4D Save options.
- Render two frames of every take and check the folders.
- Queue all takes in the Render Queue and download the results through iRender Drive.
Octane output checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Why do my Octane takes overwrite each other?
Every take resolves to the same output path. Add $take to the Octane Render Pass File path so each take writes its own folder and files.
2. Should I save Octane renders with the Cinema 4D Save tab?
OTOY advises against it. Cinema 4D’s save routines can add response curves, cut off denoiser output and corrupt multilayer EXR files. Use the Render Pass File path in the Octane Render AOV Group tab.
3. Do Cinema 4D tokens work in the Octane render pass path?
Token support was added to the Octane pass path in earlier plugin versions, and OTOY’s plugin developer recommends using tokens there. Put them in the Octane path itself and test with a two-frame render.
4. Why is the Octane beauty pass missing from my output?
When Octane’s own path is your final output, Save Beauty must be enabled in the Render AOV Group tab.
5. What does DeMain mean in an Octane file name?
OTOY adds the suffix DeMain to the denoised beauty file, before the frame number.
6. Why does Octane render every frame when I set one frame?
OTOY’s checklist notes that with Save image sequence from the Live Viewer, the frame range must cover at least two frames; otherwise Octane renders every frame.
7. Multilayer EXR or folders for Octane passes?
Multilayer keeps all passes in one file per frame. Folders write each pass separately, which makes it easy to delete a pass you do not need. EXR(Octane) is the format OTOY provides for direct saving.
Render your Cinema 4D + Octane takes 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 Octane AOVs for compositing.




