The culprit: ACES color configuration wasn't matching between the cloud server and my local system.
Let me tell you about the morning I wasted debugging colors. I rendered 500 frames overnight on iRender, downloaded them, imported into After Effects and every frame looked washed out with a green-yellow tint. The animation looked perfect on the iRender server. On my local AE it looked wrong. The culprit: ACES color configuration wasn’t matching between the cloud server and my local system. The cloud render used ACES 1.2 OCIO config; my local AE was set to ACES 1.1. That version mismatch produced a subtle but visible color shift across every frame. Fixing it took 5 minutes once I understood the problem, but those 500 frames needed zero re-rendering. The issue was display, not data. This is the kind of gotcha nobody warns you about with cloud rendering, and iRender is the only farm type where you can control ACES settings directly.
| Color Pipeline | iRender Setup | GarageFarm Support | Risk Level |
|---|---|---|---|
| ACES 1.2 (latest) | Install OCIO config | Farm nodes may vary | Low (if matched) |
| sRGB (default) | No setup needed | Default | None |
| Linear Workflow | Configure per engine | Usually works | Low |
| Custom OCIO config | Upload your config | Not supported | iRender only |
| DaVinci Resolve grading | Install Resolve | Not supported | iRender only |
How Do I Set Up ACES Correctly on iRender?
The key realization that saved me: ACES color management lives in the OCIO configuration file, not in the render engine itself. If your local machine uses ACES 1.2, your iRender server needs the exact same OCIO config version. Here’s my setup process – takes about 10 minutes once and then it’s saved to your server image forever.
Step 1: Download the ACES OCIO config package (the same version you use locally, check via $OCIO environment variable or your DCC’s color management panel). Step 2: Upload it to iRender, place it in C:\OCIO\aces_1.2\. Step 3: Set the OCIO environment variable on the cloud server to point to your config: C:\OCIO\aces_1.2\config.ocio. Step 4: In your DCC (Blender/C4D/Maya), verify the color management settings match your local setup; render color space, display transform, view transform.
That’s it. After saving the server image, every future session boots with the correct ACES config. My renders now match my local system pixel-for-pixel.
What If I Don’t Use ACES?
If you work in sRGB (the default for most DCC apps), you probably won’t hit color issues on cloud. The sRGB pipeline is standard across all operating systems and render engines. Both iRender and GarageFarm handle sRGB without any special configuration. Your cloud renders will match your local renders out of the box.
Where things get tricky is linear workflow without ACES; some studios use a custom linear pipeline with their own LUTs and gamma curves. On GarageFarm, you can’t upload custom LUTs or OCIO configs; whatever their nodes have is what you get. On iRender, you install your custom pipeline exactly as you would on any workstation.
My recommendation for animators just starting with color management: stick with sRGB for your first few cloud renders. Move to ACES once you’re comfortable with the cloud workflow itself. Debugging ACES color shifts while also learning cloud rendering for the first time is a recipe for frustration. Get the rendering workflow smooth first, then introduce ACES. That’s exactly the order I followed and I’m glad I didn’t try to do both simultaneously.
Set up your ACES pipeline on iRender → View GPU servers on iRender
FAQ
Do cloud render farms support ACES color management?
IaaS farms (iRender) fully support ACES: you install the OCIO config on the server and set the environment variable. SaaS farms (GarageFarm) have limited ACES support. Their nodes may not match your local ACES version, causing subtle color shifts. For custom OCIO configs or studio-specific LUTs, iRender is the only option.
Why do my cloud-rendered frames look different from my local renders?
Most likely an ACES or OCIO version mismatch. If your local machine runs ACES 1.2 and the cloud server has ACES 1.1 (or no ACES config at all), you’ll see color shifts, typically a washed-out, green-yellow tint. Fix: match the OCIO config version exactly. If rendering in sRGB (default), color shifts are extremely rare.
How do I set up ACES on iRender?
Upload your ACES OCIO config folder to the server, set the OCIO environment variable to point to config.ocio, verify DCC color settings match your local setup. Takes 10 minutes. Save the server image afterward; every future session boots with correct ACES. If you don’t use ACES, sRGB works out of the box with zero configuration.
You may want to read other articles of mine here.
Image source: BlenderNation
COMMENTS