Why South Beach's Color Philosophy Favors Fluid Cycles Over Fixed Gates

Every colorist has felt the pain of a fixed gate workflow: you lock a grade, deliver a reference, and then the director asks for a subtle warmth shift across all scenes. Suddenly you're re-rendering every shot, praying the LUT chain stays intact. South Beach's color philosophy argues that fluid cycles—where grades evolve through iterative passes rather than being sealed behind rigid gates—save time, preserve creative momentum, and actually produce more consistent results. This guide explains why we favor fluid cycles, how they work under the hood, and when you might still want a fixed gate.

Why This Topic Matters Now

Post-production pipelines have grown more complex in the last few years. With remote collaboration, multiple delivery formats (Rec. 709, DCI-P3, HDR10, HLG), and tighter turnaround times, the old model of 'grade once, lock, deliver' no longer fits. Many teams report that fixed gate workflows—where each shot is graded to a final look and then 'closed'—lead to a cascade of rework whenever a creative note arrives. A single tweak to the primary grade can force a full re-export of every affected shot, breaking continuity and eating hours.

Fluid cycles, by contrast, treat grading as a continuous process. Instead of locking each shot after a single pass, the colorist works in layers: a base grade that handles exposure and white balance, a creative grade for the look, and a trim pass for shot-specific adjustments. When a note comes in, only the relevant layer needs updating, and the downstream pipeline re-renders only what changed. This approach aligns with modern non-destructive workflows in tools like DaVinci Resolve, Baselight, and Nuke.

The stakes are real: a 2023 survey of post-production houses (industry-wide, not from a single vendor) found that projects using iterative grading cycles reported 30% fewer re-renders compared to those using fixed gates. While the exact number varies, the pattern holds across narrative features, commercials, and streaming series. For independent colorists and small studios, fluid cycles can mean the difference between delivering on time and burning out on overtime.

Who This Is For

This guide is for colorists, DITs, and post supervisors who want to streamline their workflow. If you've ever felt that your grading pipeline fights against creative exploration, or if you're tired of explaining to clients why a 'small' change requires a full re-render, fluid cycles offer a better path.

Core Idea in Plain Language

A fluid cycle is any grading workflow where the colorist can adjust a shot's grade at multiple points without needing to redo the entire pass. Think of it like a layered Photoshop file versus a flattened JPEG. In a fixed gate workflow, you grade a shot, render it out, and that's it—any change means going back to the source and starting over. In a fluid cycle, you keep the project file open, and each adjustment lives on its own node or layer.

The key insight is that most grading changes are not global—they target specific ranges: shadows, midtones, highlights, or particular hues. A fluid cycle lets you isolate those ranges and modify them without touching the rest of the grade. For example, if the client wants the skin tones warmer, you can adjust the hue vs. hue curve on the skin range alone, leaving the background and wardrobe untouched. In a fixed gate, you'd have to re-grade the entire shot to achieve the same effect, risking unintended shifts in other areas.

South Beach's philosophy extends this idea to the entire project timeline. Instead of locking each scene as you finish it, you keep all scenes in a 'live' state until the final color review. This allows for global look adjustments—like a subtle teal-and-orange push—that propagate consistently across every shot. The result is a cohesive grade that evolves organically rather than being stitched together from isolated locks.

Why Fixed Gates Persist

Fixed gates aren't all bad. They provide a clear checkpoint: once a shot is locked, you can move on without second-guessing. They also simplify handoffs to VFX or conform, because the reference is stable. But the cost is flexibility. In practice, most projects change after the first lock—client feedback, directorial revisions, or technical adjustments for different deliverables. Fluid cycles embrace that reality rather than fighting it.

How It Works Under the Hood

At a technical level, fluid cycles rely on a few key pipeline components: non-destructive grading nodes, version management, and smart rendering. Let's break each down.

Non-Destructive Nodes

In Resolve, every correction is a node. A fluid cycle organizes nodes into a hierarchy: a pre-grade node for input transform and noise reduction, a primary node for exposure and contrast, a creative node for the look, and a trim node for shot-specific tweaks. When a note arrives, you adjust only the relevant node. The software re-renders only the affected portion of the image, not the whole shot.

Version Management

Fluid cycles also require a versioning system that tracks changes without overwriting. Baselight's 'layers' and Resolve's 'versions' both allow you to save multiple iterations of a grade within the same timeline. You can compare versions side by side, revert to an earlier look, or blend them. This is impossible in a fixed gate workflow where each render is a flat file.

Smart Rendering

Modern grading applications support partial rendering: they only re-render frames where the grade changed. Combined with background caching, this means a fluid cycle doesn't necessarily slow down the pipeline. In fact, it often speeds it up because you avoid full re-renders for small tweaks. For example, adjusting a single node's gain by 0.1 stops triggers a cache update only for that node's output, not the entire chain.

One common concern is that fluid cycles create a mess of unresolved versions. To avoid this, we recommend a naming convention: base grade = scene_shot_base, creative pass = scene_shot_creative_v1, trim = scene_shot_trim. At the end of the project, you flatten the final version and archive the project file for future reference.

Worked Example or Walkthrough

Let's walk through a realistic scenario: a 30-second commercial with 15 shots, graded for both broadcast (Rec. 709) and cinema (DCI-P3). The client wants a 'golden hour' look with warm highlights and cool shadows.

Fixed Gate Approach

You'd grade each shot to the golden hour look, render all 15 shots to Rec. 709, and deliver a reference. Then the client asks for the highlights to be less yellow. You adjust the hue vs. hue on each shot's highlights, re-render all 15 shots, and deliver again. Then they want a version with more contrast. Another full re-render. By the end, you've rendered each shot four or five times, and the timeline is bloated with redundant files.

Fluid Cycle Approach

You build a shared grade structure: a pre-grade node for input transform, a primary node for exposure, a creative node for the golden hour look (using power windows and curves), and a trim node for each shot. The creative node is shared across all shots via a group or shared grade. When the client asks for less yellow highlights, you adjust the creative node once. The software updates all shots automatically. When they ask for more contrast, you adjust the primary node. No re-renders until the final delivery. For the DCI-P3 version, you add an output transform node at the end of the chain, which applies to every shot without re-grading.

Trade-Offs

The fluid cycle saved time on revisions, but it required upfront planning. You had to design the node tree carefully to ensure the shared grade didn't break shot-specific trims. Also, the project file became larger because it stored all the versions. But for a 30-second spot, the trade-off was overwhelmingly positive: three rounds of client notes were handled in a single afternoon, with only one final render per deliverable.

Edge Cases and Exceptions

Fluid cycles aren't a silver bullet. Here are situations where they can struggle, and how to adapt.

HDR and Wide Color Gamut

When grading for HDR (PQ or HLG), the dynamic range is much larger, and small adjustments can have outsized effects. A fluid cycle that works well for SDR may produce clipping or banding in HDR if the node order isn't correct. The fix is to keep the HDR grade in a separate layer that applies after the SDR grade, or use a dedicated HDR node tree. South Beach's advice: test the HDR pass early in the cycle, not at the end.

Log Footage with Heavy Noise

If your source is log with significant noise (e.g., high-ISO Alexa or RED footage), a fluid cycle that applies noise reduction in a pre-grade node can interact poorly with later creative nodes. The noise reduction may need to be tuned per shot, which breaks the shared-grade model. In this case, we recommend a hybrid: use a fixed pre-grade for noise reduction on each shot, then a shared creative node for the look.

VFX and Conform Handoffs

When handing off graded shots to VFX, fixed gates are often required because VFX artists need a stable reference. You can still use fluid cycles internally, but export a locked reference for VFX. Once VFX returns the shots, you re-import them into the fluid cycle and adjust the grade to match the original look. This adds a step but preserves flexibility for the rest of the project.

Limits of the Approach

No workflow is perfect. Fluid cycles have real downsides that you should consider before adopting them wholesale.

Project File Bloat

Storing multiple versions and layers increases project file size. For a feature film with thousands of shots, the project file can become unwieldy, slowing down saves and autobackups. Some teams mitigate this by archiving older versions to a separate database, but that adds complexity.

Learning Curve for Collaborators

If you work with assistant colorists or DITs who are used to fixed gates, they may struggle with the layered approach. Miscommunication about which layer to adjust can lead to inconsistent grades. Clear naming conventions and regular sync meetings help, but the friction is real.

Rendering Overhead for Final Delivery

While fluid cycles reduce re-renders during revisions, the final render can be slower because the software has to compute the entire node tree for each shot. In practice, this is usually offset by the time saved on revisions, but for projects with very tight delivery windows, a fixed gate might be faster for the final pass.

When Fixed Gates Win

Fixed gates are still the right choice for: (1) projects with no expected revisions (e.g., a one-off social media clip), (2) workflows where the colorist is not the final decision-maker and needs to hand off a stable reference, and (3) very short timelines where any learning curve is unacceptable. South Beach's philosophy is not to abandon fixed gates entirely, but to use fluid cycles for the majority of projects where iteration is expected.

Reader FAQ

Does a fluid cycle require special software?

No. Most professional grading tools support non-destructive nodes and versions. DaVinci Resolve, Baselight, and even Premiere Pro's Lumetri panel can be used in a fluid cycle. The key is how you organize your workflow, not the software itself.

How do I handle LUTs in a fluid cycle?

Apply LUTs in a dedicated node at the end of the chain, before the output transform. This way, you can change the LUT without affecting the underlying grade. Avoid baking LUTs into individual nodes, as that makes adjustments harder.

Can I use fluid cycles with remote collaboration?

Yes, but you need a shared project file or a versioning system like Resolve's collaboration feature or Baselight's remote grading. Be careful with latency: if two colorists adjust the same layer simultaneously, conflicts can occur. Use a 'check-out' system for layers.

What about round-tripping with offline editing?

Fluid cycles work well with round-tripping because you can re-conform the timeline and reapply the grade via the project file. However, if the offline editor changes shot lengths or adds new clips, you may need to rebuild the grade for those shots. Keep your node tree modular to simplify this.

Do fluid cycles affect reference monitor calibration?

No. Calibration is independent of the grading workflow. However, if you switch between SDR and HDR deliverables within a fluid cycle, ensure your monitoring chain is set up to display the correct color space for each pass. Use a LUT box or software monitoring that can switch dynamically.

Practical Takeaways

Here are three actions you can take starting today to move toward fluid cycles.

1. Audit your current node tree. Open a recent project and see if you have a clear separation between pre-grade, primary, creative, and trim nodes. If everything is on one node, start splitting it. Even a simple two-node structure (base + look) is a step forward.
2. Set up a versioning system. Use your software's built-in versioning or a manual naming convention (e.g., v01, v02) for each shot. Save the project file after each round of notes so you can revert if needed.
3. Test on a small project first. Pick a short form piece—a 30-second spot or a music video—and try the fluid cycle approach. Note where you save time and where you hit friction. Adjust your node tree and naming conventions based on that experience.

Fluid cycles aren't about being trendy; they're about respecting the reality that creative work is iterative. By building your grade in layers, you give yourself permission to explore without fear of breaking what's already working. That's the core of South Beach's color philosophy.