How Do I Render 50 Versions of a Shot for Client Review Without Losing a Week?
How do I render 50 versions of a shot for client review? Fifty versions does not mean fifty full quality renders run one after another, which is what eats the week. Three moves keep it to an afternoon. Render at review quality, not final, since the client is judging the look, not pixel peeping, so lower resolution and samples cut each version many times over. Render the versions in parallel, because each one is independent, so they spread across machines or cloud GPUs and finish together instead of in a queue. And render only what changed, using takes or wedging to vary one element and layers so you re render the affected pass, not the whole frame. Draft quality, in parallel, changed parts only, and 50 versions stops being a week.
The client wants to see 50 variations by Monday. Different lighting moods, a few color directions, two or three FX intensities, all crossed together until it is dozens of versions. Render those the way you render a final, full resolution and full samples, one after another, and you will still be going on Tuesday. The job is not actually 50 finals. It is 50 quick looks, and treating it that way is the whole trick.
Table of Contents
Why People Lose the Week
The time vanishes into rendering review versions at final quality. A client deciding between three lighting moods does not need 4K and full samples to tell them apart, but that is what gets rendered out of habit, so each version costs what a delivery costs. Multiply by 50 and a week disappears. The look is the decision being made, and the look reads clearly at a fraction of final cost.
The Three Moves That Save It
| Move | What it does | Roughly saves |
|---|---|---|
| Render at review quality | Lower res and samples for a look the client can judge | Several times per version |
| Render versions in parallel | Independent versions spread across machines | Scales with machine count |
| Render only what changed | Takes or wedges vary one element, re render that layer | Most of each version |
The parallel part is where the numbers get dramatic. Say each version is a single review frame at roughly 3 minutes in draft. Fifty of them back to back on one machine is about 150 minutes, two and a half hours of sitting and waiting. Spread across eight cloud GPUs, the same 50 versions come back in under 20 minutes, because they have no reason to wait for each other. Variations are the ideal parallel job, since unlike a sequence where you want frames in order, here every version is independent.
Set It Up to Run Itself
- Use takes or wedging. Houdini wedges, Maya render layers and takes, or your DCC’s equivalent let you define the variations once and batch them, rather than hand saving 50 files.
- Drop to review settings. Lower resolution, fewer samples, and a single representative frame per version where motion is not the point. Our test versus final render guide covers which settings to cut.
- Vary one thing per axis. Render the changed layer or element against a cached background, not the entire frame, so each version is cheap.
- Send the batch out in parallel. Hand the independent versions to as many machines as you can so they finish together.
Where Cloud Fits, and Its One Catch
Variations are exactly the job cloud GPUs handle well, since you can spin up several machines, render all 50 at once, and shut down. iRender lets you rent multiple servers to run the batch in parallel and bring the whole review back fast. Running many machines at once carries its own cost, though: parallel servers multiply the billing meter, so 50 versions at full resolution across a stack of GPUs gets expensive quickly. Keep them at review quality, which is the point of the exercise anyway, and the parallel run stays cheap. How the per minute billing works is in our iRender explainer, and SaaS farms that batch variations are in the comparison.
Dozens of review versions due and one machine?
Render them in parallel at review quality with iRender →
Frequently Asked Questions
How do I render many versions of a shot quickly for client review?
Render at review quality rather than final, since the client is judging the look and that reads at lower resolution and samples, render the versions in parallel because each is independent and can spread across machines, and render only the element that changed against a cached background. Draft quality, in parallel, changed parts only, turns dozens of versions from a week into an afternoon.
Should I render client review versions at full quality?
Usually not. A client choosing between lighting moods or color directions is judging the overall look, which reads clearly at lower resolution and fewer samples, so full quality wastes most of the render time on detail the decision does not need. Render reviews at draft settings, then render only the chosen version at final quality once the direction is approved.
What is the fastest way to render shot variations?
Define the variations with takes or wedges so they batch automatically, render them at review quality, and send the independent versions to many machines in parallel, since variations have no reason to wait for each other. Cloud GPUs suit this well because you can spin up several servers, render all the versions at once, and shut down, keeping them at review quality to control cost.
See more: How Do Studios Render Overnight VFX Shots Without Missing Deadlines?
No comments