Colorfront

You Don't Have to Shoot Log: How to Grade Rec.709 Footage in DaVinci Resolve

Colorist Paul Handley makes the case for Rec.709 as a viable shooting option and walks through his node-based workflow for getting the most out of both 8-bit and 10-bit footage.

Bottle Rocket Content

Bottle Rocket Content

— 4 min read
Share
You Don't Have to Shoot Log: How to Grade Rec.709 Footage in DaVinci Resolve

The pressure to shoot log is real, and for most modern cameras it's good advice. But colorist Paul Handley makes a case worth hearing: Rec.709 is a viable color space today, and for some cameras — specifically older Sony bodies like the a7S II — it can actually give you more usable information than the camera's log profile.

The workflow to get the most out of Rec.709 footage in DaVinci Resolve is more specific than most tutorials cover. Here's how Handley approaches it.

Why Rec.709 Still Holds Up

The standard objection to Rec.709 is that log captures more dynamic range and gives the colorist more latitude in post. That's true for cameras with good log implementations. It's not universally true for every camera on the market.

As Handley puts it: "While it is true you will get more information out of your image if you use camera logs or camera raw, Rec.709 is definitely a viable option today."

The implication is practical: if your camera's log profile is poorly implemented, or if the footage is going through heavy compression anyway, the theoretical advantage of log may not survive to the grade. Rec.709 footage that's well-exposed and handled carefully can outperform poorly-handled log.

The CST Workaround

The first move in Handley's workflow is a Color Space Transform node that converts the Rec.709 footage into DaVinci Wide Gamut / DaVinci Intermediate before any grading begins. That conversion gives him a wider gamut and a more linear gamma curve to work in, even though the source material is Rec.709.

The node structure that follows: Exposure → Contrast → Color → Saturation. Each correction lives in its own node, which keeps the grade readable and reversible. Adjustments compound cleanly rather than fighting each other.

The Bit Depth Split

This is where Handley's approach gets most specific, and where it's most useful.

10-bit Rec.709 footage has enough data to support aggressive manipulation, including keying. Handley uses Vector Red keying on skin tones in 10-bit workflows — isolating the skin tone range to make targeted hue and saturation adjustments without affecting the rest of the image.

8-bit H.264 footage is a different situation. The compressed codec leaves less headroom for manipulation, and keying in 8-bit creates a real risk of breaking the image — introducing banding, artifacts, or unnatural transitions at the key boundaries. Handley's rule for 8-bit is direct: "Because this image is only 8-bit, we need to be mindful of the skin tones and I don't think we should be doing any keying, and I do try to avoid it when working in 8-bit imagery."

The alternative for 8-bit skin tone work is broader adjustments — global color balance moves that shift the image without isolating specific ranges — plus the Film Look Creator OFX plugin, applied at blended settings rather than full strength. Film Look Creator adds grain, halation, and tonal characteristics that help compressed footage feel less digital without putting the kind of computational stress on the image that keying would.

Why This Matters for the Rec.709 vs. Log Debate

The bit depth split reframes the question most colorists ask about Rec.709 footage. The question isn't just "what color space did the camera shoot in?" It's "what codec did the camera record to, and how much manipulation can that codec actually support?"

A camera shooting 10-bit Rec.709 to an external recorder gives a colorist meaningful latitude. A camera shooting 8-bit H.264 internally requires a more restrained approach regardless of color space. Handley's workflow accounts for that distinction explicitly rather than treating all Rec.709 footage as a single category.

Competitive Context

The log-vs-Rec.709 debate has been running long enough that most tutorials land firmly in one camp. The "always shoot log" position dominates the YouTube cinematography space, often without much nuance about which cameras actually benefit from log versus which cameras produce better results in standard profiles. Handley's video is useful specifically because it doesn't argue against log — it argues for understanding when Rec.709 is the better choice, and for handling it correctly when you make that call.

DaVinci Resolve's Film Look Creator, used here as a finishing tool for 8-bit footage, has become increasingly capable since its introduction and is worth understanding as a legitimate alternative to third-party grain and film emulation plugins for compressed source material.

The Signal in the Noise

The most practically useful part of Handley's breakdown is the explicit rule against keying in 8-bit. It's the kind of advice that saves a colorist hours of troubleshooting broken images — not because the technique is wrong in principle, but because 8-bit H.264 simply doesn't have the data to support it cleanly.

For independent filmmakers shooting on cameras that record 8-bit internally — which includes a significant portion of the mirrorless market — knowing where the hard limits of the footage are before starting the grade is more valuable than any specific technique.

Specs & Pricing

DaVinci Resolve is free for the standard version. DaVinci Resolve Studio, which includes some additional OFX plugins and collaborative features, is a one-time purchase of $295. Film Look Creator is included in both versions. Current pricing and download at blackmagicdesign.com/products/davinciresolve.

Resources & Reads

Read more