DaVinci Resolve Canon R6 Mark II C-Log3 Import Settings

What Color Space Transform settings does each color space need?

This is the core answer, and because the R6 Mark II gives you three real choices, there are three real answers, not one.

For every option, your first node's Color Space Transform starts the same way: Input Gamma is always Canon Log 3, Output Color Space is always DaVinci Wide Gamut, and Output Gamma is always DaVinci Intermediate. What changes is Input Color Space, and it has to match exactly what you selected on the camera when the clip was recorded.

If you shot with Cinema Gamut selected:

1. Input Color Space: Canon Cinema Gamut
2. Input Gamma: Canon Log 3
3. Output Color Space: DaVinci Wide Gamut
4. Output Gamma: DaVinci Intermediate

If you shot with BT.2020 selected:

1. Input Color Space: Rec.2020
2. Input Gamma: Canon Log 3
3. Output Color Space: DaVinci Wide Gamut
4. Output Gamma: DaVinci Intermediate

If you shot with BT.709 selected:

1. Input Color Space: Rec.709
2. Input Gamma: Canon Log 3
3. Output Color Space: DaVinci Wide Gamut
4. Output Gamma: DaVinci Intermediate

On your last node, before your final output, reverse whichever version you used:

1. Input Color Space: DaVinci Wide Gamut
2. Input Gamma: DaVinci Intermediate
3. Output Color Space: Rec.709 (or Rec.2100 for HDR delivery)
4. Output Gamma: Rec.709 (or ST 2084 / HLG for HDR)

This "in, grade, out" pattern, one Color Space Transform converting into DaVinci Wide Gamut and one converting back out to your delivery space, is the same underlying mechanism Shootlab's walkthrough of grading Canon C-Log footage in Resolve documents for Canon Log workflows generally. What's specific to the R6 Mark II is that first Input Color Space field, and it's worth building a habit of checking it clip by clip, or at least shoot by shoot, rather than assuming last week's project setting still applies.

If you're delivering HDR instead of Rec.709, only the output half of your last node changes, to Rec.2100 with an HLG or ST 2084 Output Gamma. The input side of that node stays DaVinci Wide Gamut and DaVinci Intermediate regardless of delivery target. Confirm your Project Settings Timeline Color Space and your monitoring setup actually support HDR before committing to that path; grading toward Rec.2100 on an SDR reference monitor is a reliable way to end up with a delivery that looks wrong everywhere except your own room.

A Color Space Transform set to the wrong Input Color Space produces a result that looks close but not right, and on the R6 Mark II specifically, "close but not right" usually means someone grabbed Cinema Gamut out of habit on a clip that was actually shot BT.2020. That single mismatch is the single most avoidable mistake this whole guide exists to prevent.

Resolve Color Management or a manual Color Space Transform node, which one?

Both get you to the same place. Which one fits depends on whether your R6 Mark II footage was all shot with the same color space selected, or whether it's a mix.

Resolve Color Management, set under Project Settings, Color Management, with Color Science set to DaVinci YRGB Color Managed, lets you assign a clip's input color space directly through Clip Attributes or the Camera RAW tab, and Resolve applies the conversion automatically to every downstream node. That's the faster setup when every R6 Mark II clip in your project shares the same in-camera color space selection, since you tag once per clip or per batch rather than building a node for each one.

A manual Color Space Transform node gives you more control per clip or per group, and it's the safer default the moment your project mixes clips shot with different color space settings, which happens more often on this camera than you'd expect. A run-and-gun shoot where the operator forgot to check the menu between setups, or a multi-day project where someone changed the setting halfway through, both leave you with a mixed batch that Resolve Color Management's automatic tagging won't sort out for you. You still have to know which clip is which; a manual node just makes the mismatch visible in your node tree instead of hidden in a Clip Attributes panel you're not actively looking at.

To set up Resolve Color Management on an R6 Mark II project, open Project Settings, the gear icon in the bottom right or Shift+9, and go to Color Management. Set Color Science to DaVinci YRGB Color Managed, Timeline Color Space to DaVinci Wide Gamut / Intermediate, and Output Color Space to Rec.709 or your actual HDR target. Select your clips in the Media Pool, right-click, open Clip Attributes, and assign Input Color Space and Input Gamma there, once per clip or per group of clips that share a setting.

If your project mixes R6 Mark II footage with another camera brand entirely, normalize each camera's native color space independently before applying one shared creative grade. Our guide to color matching different cameras in DaVinci Resolve covers that multi-camera step in more depth.

Resolve Color Management is faster when every clip agrees on a color space, and a manual Color Space Transform node is safer the moment you can't be certain they do. On the R6 Mark II, where the camera itself hands you three choices instead of locking you to one, that second scenario is common enough to plan for from the start.

Why does HDMI-recorded C-Log3 footage default to BT.2020 even if you picked Cinema Gamut?

Because Cinema Gamut cannot physically travel over an HDMI connection, and Canon says so directly in its own R6 Mark II manual.

This is the single most common cause of "I matched my internal and external footage carefully and it still looks different" on this camera, and it has nothing to do with your Color Space Transform math. Rodrigo Polo, who has published Log-to-Rec.709 conversion LUTs and detailed color science breakdowns for Canon cameras, documented Canon's own admission of the issue directly: "Canon finally address the issue in the EOS R6 Mark II user manual...which clearly states that even though you can select 'Cinema Gamut' in their menu, it will only use Cinema Gamut with internal recordings, the HDMI output will always be Rec/BT.2020," he wrote in an article specifically about this limitation.

Canon's own manual backs this up in plain language. Per the R6 Mark II's Canon Log Settings page, the camera's HDMI output undergoes color space conversion "to suit the device," and a clip recorded with Cinema Gamut selected converts to Rec.2020 over HDMI if the connected recorder supports it, or to Rec.709 if it doesn't. That means a clip recorded internally to your card, tagged Cinema Gamut, and a clip recorded at the exact same moment to an external recorder like an Atomos Ninja V, come from the identical sensor and identical exposure, but need two different Color Space Transform inputs to match once they're in Resolve.

Polo's related writeup on the closely related R5, which shares the same HDMI hardware limitation, found the practical result directly: he documented comparing a clip recorded internally with Cinema Gamut against one recorded externally with Rec.2020, and found they looked the same "even after applying Canon's own technical LUTs," once each source got its correct input tag, but not before. That's the mechanism working correctly. The failure mode is applying Cinema Gamut to the HDMI clip anyway, out of habit or because that's what you selected in the camera menu, without accounting for what the HDMI port actually does with it.

A Canon R6 Mark II clip recorded to an external recorder over standard HDMI needs Rec.2020 or Rec.709 as its Color Space Transform input, not Cinema Gamut, regardless of what the camera's own menu says you selected. Miss this one setting and internal and external footage of the same scene, shot seconds apart, will grade to visibly different color no matter how carefully you match everything else.

Should you use Canon's official LUT instead of a Color Space Transform?

You can, and it's genuinely faster for a single-setting shoot, but it's not a drop-in fix the moment your project mixes color space selections or recording methods.

Canon publishes free LUT packages built for its Canon Log formats, downloadable from the Software & Drivers tab on the camera's page at Canon's regional support sites. These are standard .cube files, the same format Resolve reads natively. Our guide to installing LUTs in DaVinci Resolve covers the mechanics of getting a .cube file into your LUT folder if you haven't set one up before.

Drop a matching LUT onto a node and you get a usable Rec.709 image in one step, no Input Color Space dropdown, no Output Gamma menu, done. That speed is exactly why editors reach for it on same-day turnarounds or dailies nobody's going to grade further.

Where it breaks down is the same place the HDMI mismatch breaks down. A LUT built to convert Cinema Gamut and Canon Log 3 to Rec.709 bakes in an assumption about the input color space it's converting from. It doesn't know or care whether your specific clip actually recorded Cinema Gamut, BT.2020, or BT.709, since the R6 Mark II's three-way menu means any given clip could be any of the three. Feed the wrong LUT to the wrong clip and you get the same mismatch a manual Color Space Transform would throw if you picked the wrong Input Color Space, except a LUT gives you no dropdown menu to catch the mistake in before it's baked into your grade.

A one-step LUT and a two-node Color Space Transform solve the same math, but only the Color Space Transform gives you a separate, checkable control for Input Color Space when a clip needs something other than the default you're used to. On a camera that hands you three color space choices instead of one, that checkable control matters more than it would on a camera locked to a single gamut.

What ISO should you shoot C-Log3 at for these settings to work correctly?

ISO 800 or higher. Below that, C-Log3's dynamic range narrows, and no Color Space Transform setting recovers highlight detail the sensor never captured.

Per Canon's own R6 Mark II manual, "Canon Log offers a dynamic range of approx. 1600% at ISO 800 or higher," and the same page states directly that "manually setting the ISO speed to 100-640 will make the dynamic range narrower." Expanded ISO options below the 800 floor exist, running from ISO 100 up through 640, and they're genuinely usable when you need a brighter exposure in controlled light. What they don't give you is the full dynamic range the C-Log3 gamma curve was built around.

That ISO 800 floor is consistent across Canon's current C-Log3 implementation. The original R6 shares the identical number: per Canon's own manual for the original EOS R6, Canon Log 3 on that camera also offers "approx. 1600% at ISO 800 or higher," while plain Canon Log, the option the R6 Mark II dropped entirely, tops out lower at "approx. 800% at ISO 400 or higher." Whichever Canon body you're comparing against, C-Log3's design point is the same ISO 800 baseline.

Exposing C-Log3 below ISO 800 doesn't just make footage darker, it throws away the extra highlight headroom that's the entire reason to shoot C-Log3 instead of a standard picture profile. If your R6 Mark II footage still clips highlights or crushes shadows after a correct Color Space Transform, check your original ISO before you spend more time on the color node. A curve that never got the exposure it was designed for won't grade like one that did, no matter how precisely you match Input Color Space to what you shot.

Does noise get worse at higher ISO, and how do you fix it in Resolve?

Yes, every stop of ISO you add above C-Log3's 800 baseline buys correct exposure at the cost of more visible noise once the flat Log image gets stretched into a normal-contrast grade, and the Color Space Transform itself does nothing to reduce it.

DaVinci Resolve's dedicated noise reduction tools, both Temporal and the DaVinci Neural Engine-driven Spatial and UltraNR modes, are Studio-exclusive. Blackmagic's own Studio product page lists these among the features that separate Studio from the free version. If you're already on Studio for the decoding reasons covered further down this guide, you already have access to them. If you're not, denoising a noisy high-ISO C-Log3 clip inside Resolve itself isn't something the free version offers.

Node placement matters more than which specific mode you pick. Apply Noise Reduction on a node before your Color Space Transform converts the clip out of Log, while the image is still flat and the noise pattern is closer to what the sensor actually recorded, rather than after you've already pushed contrast and saturation back in through the grade. Denoising after a heavy grade means fighting noise that's already been amplified by every contrast and saturation move downstream of it, asking far more of the same tool for a worse result.

Our dedicated guide to DaVinci Resolve's video noise reduction settings covers the specific Temporal, Spatial, and UltraNR parameters and the tradeoffs between denoising strength and softened detail in more depth than fits here.

C-Log3's noise floor is a shooting-day problem first and a Resolve problem second. Staying at or near ISO 800, rather than pushing several stops over it just because the expanded range technically allows it, keeps most R6 Mark II footage out of the noise reduction workflow altogether.

C-Log vs C-Log3 vs C-Log2, which one does the R6 Mark II actually shoot?

Just C-Log3. The R6 Mark II is the only camera in this specific lineage that offers exactly one Log option, which is actually simpler than the choice facing R5 or R6 Mark III shooters, and worth confirming before you go looking for a setting the camera doesn't have.

The original EOS R6 supports two Log options side by side. Per Canon's own manual for that camera, you can select "On (C.LOG)" or "On (C.LOG3)," with the color space choice, BT.709, BT.2020, or Cinema Gamut, available "(On (C.LOG3) only)." Plain Canon Log on the original R6 tops out at roughly 800 percent dynamic range at ISO 400, the least forgiving of the family and locked to a fixed color space rather than the three-way choice C-Log3 unlocks.

The R6 Mark II dropped plain Canon Log entirely. It shoots C-Log3 only, at the same roughly 1600 percent dynamic range and ISO 800 floor as the original R6's C-Log3 option, but with the three-way color space menu available on every C-Log3 clip rather than gated behind picking the wider Log variant.

The newer R6 Mark III moves further still. According to Digital Camera World's comparison of the three cameras, the Mark III adds Canon Log 2 alongside Canon Log 3, the same wider-range option Canon has offered on some of its higher-end bodies. Canon's own comparison of all three cameras confirms the R6 Mark III's expanded Log lineup sits alongside its Mark II predecessor's single-Log approach.

If you're following a tutorial or forum thread that mentions C-Log2 on an "R6," check which R6 it's actually describing, because the R6 Mark II doesn't have that option at all. Every Color Space Transform setting in this guide assumes Canon Log 3, since that's the only Log gamma the R6 Mark II can record.

Does DaVinci Resolve import the R6 Mark II's 6K RAW footage?

Yes, but only if you captured it externally. The R6 Mark II records no RAW internally at all; RAW only exists once you've routed the camera's HDMI output through a compatible external recorder.

Per CineD's coverage of the camera's announcement, the R6 Mark II outputs "6K RAW output" over its HDMI port, and 4K Shooters' testing of the format confirms it as genuine 6K ProRes RAW captured through this path. According to Atomos's own compatible camera specifications for the R6 Mark II, the camera outputs "up to 12-bit linear RAW" in three resolution options: 6K at 1.9:1 up to 59.94fps, a 6K CinemaScope 2.4:1 crop at 59.94fps, and a 3.7K 1.9:1 mode across the same frame rate range. The higher frame rate options in each mode require a Ninja V+, Shogun Connect, or a similarly higher-spec Atomos device; the standard Ninja V caps out around 29.97fps on the same resolutions.

This is ProRes RAW specifically, not Blackmagic RAW. Some Panasonic cameras output both formats over HDMI; the R6 Mark II only supports the ProRes RAW path, and it requires AtomOS 10.90.00 or later on the Atomos device before recording will work at all.

Worth separating clearly from the standard C-Log3 workflow covered throughout the rest of this guide: RAW footage opens through Resolve's Camera RAW panel, not through a Color Space Transform node. DaVinci Resolve decodes ProRes RAW natively on Mac; Windows support depends on your specific setup, which is worth confirming before committing a shoot to this path if you're editing on a PC. Once a RAW file is in your Media Pool, right-click it and open the Camera RAW panel to adjust decode settings, white balance, exposure, and ISO after the fact, latitude a standard C-Log3 MOV doesn't give you.

Atomos's own specifications also note that the R6 Mark II can record an internal proxy to a second card slot alongside the external RAW capture, limited to Full HD IPB or IPB Light. That gives you a lightweight backup and a scratch reference you can cut with before your RAW files finish transferring, though it's not a substitute for the optimized media workflow covered later in this guide.

6K ProRes RAW over HDMI is a genuine capability on the R6 Mark II, but it's a paid-hardware add-on bolted onto a camera whose standard internal C-Log3 recording already covers most delivery targets without it. Don't assume you need an Atomos recorder just because the option exists; the internal C-Log3 workflow covered throughout the rest of this guide handles a standard Rec.709 or HDR10 delivery with far less hardware and far less setup.

Why won't some Canon R6 Mark II clips import into DaVinci Resolve at all?

If your C-Log3 clip shows up as "Media Offline" or won't generate a thumbnail, that's a different failure mode than a wrong-looking grade, and it usually traces back to the free version's decode limits, not a color space setting.

The R6 Mark II's C-Log3 mode records 10-bit 4:2:2 footage, per Canon's own manual. DaVinci Resolve's free version has real limits decoding that exact combination. A thread on Blackmagic's own user forum, Canon R6 C-Log3 10bit, documents editors hitting exactly this wall: footage that plays fine elsewhere but won't come online in Resolve specifically because of its 10-bit 4:2:2 chroma. Puget Systems' breakdown of Resolve's hardware decoding support confirms the split runs along Studio versus free lines, noting "the Studio version of DaVinci Resolve has long been able to utilize hardware decoding of H.264 and H.265 (HEVC) media."

Windows adds a second, unrelated wrinkle on top of that for the R6 Mark II's H.265 clips specifically. Microsoft doesn't ship HEVC decoding natively with Windows, so even Resolve Studio needs the separate "HEVC Video Extensions" package from the Microsoft Store installed at the OS level before H.265 files will decode at all, a gap Filmmaking Elements' guide to fixing HEVC media offline errors walks through directly. Mac users skip this particular wall, since macOS has included HEVC decoding since Sierra, though they can still hit the free-versus-Studio 4:2:2 decode limitation described above regardless of platform.

You have three real options if a C-Log3 clip won't come online:

1. Upgrade to Studio. This is the direct fix and the one most editors on the Blackmagic forum thread land on, since it removes the 4:2:2 decode limit and, on Windows, still requires confirming the Microsoft HEVC extension is installed separately.
2. Transcode before you import. Convert the offending clips to an intraframe codec like ProRes or DNxHR outside Resolve first, then bring the transcoded files in instead of the originals.
3. Generate proxy or optimized media from inside the free version, though this path is inconsistent specifically for 10-bit 4:2:2 sources on Free, since Resolve still has to decode the original once to build the proxy, which is exactly the step failing. It tends to work more reliably once you're already on Studio.

Our dedicated DaVinci Resolve Media Offline guide covers the broader set of causes behind that specific error message if the fix above doesn't fully resolve your case.

A Canon R6 Mark II clip that won't come online in Resolve isn't a color science problem, and no Color Space Transform setting fixes it, it's a 10-bit 4:2:2 decode limitation specific to the free version. Confirm which version of Resolve you're running before you spend time troubleshooting a Color Space Transform on a clip that hasn't actually decoded yet.

Do you need proxies to edit 6K RAW or C-Log3 footage smoothly?

Often yes, and the reason differs depending on whether you're cutting RAW or Log footage.

The R6 Mark II's external 6K ProRes RAW files carry a real debayer cost every frame has to pay before Resolve can even display it, a computational expense that has nothing to do with file size or codec efficiency. A compressed 10-bit 4:2:2 C-Log3 H.265 file is smaller on disk but leans on long-GOP decoding instead, its own kind of expensive on a laptop GPU with no dedicated HEVC decode block. Both situations respond to the same fix: build lower-resolution stand-ins before you start a heavy multi-clip edit.

Right-click a clip or bin in the Media Pool and choose Generate Optimized Media to have Resolve transcode a full local proxy copy in the background, at a resolution and codec you set under Project Settings, Master Settings, Optimized Media and Render Cache. For 6K sources specifically, Pixflow's proxy workflow guide recommends leaving Proxy Media Resolution on "Choose Automatically," which sizes proxies proportional to your timeline resolution, turning a 6K clip into a quarter-resolution proxy on a 4K timeline automatically, and dropping it further to eighth resolution manually if playback still stutters on a lower-powered machine.

Codec choice follows your platform, the same rule that applies across every camera brand. On a Mac, ProRes, typically ProRes 422 or ProRes 422 LT, is the standard proxy codec. On Windows, DNxHR fills the same role, with DNxHR LB for the smallest files and DNxHR HQX when storage isn't a constraint, per Beginners Approach's breakdown of Resolve's proxy resolution and codec options. Our full guide to proxy media setup for a slow laptop walks through the exact Project Settings panel and a decision tree for which resolution tier fits your specific hardware.

Proxies fix playback performance, not color. Building optimized media from an R6 Mark II clip doesn't change or skip the Color Space Transform step covered earlier in this guide; Resolve automatically relinks to your full-resolution originals for the final render regardless of what you cut with, so your Input Color Space setting still applies exactly the same way it would without proxies in the pipeline.

Do you need DaVinci Resolve Studio for any of this?

No, not for the core C-Log3 workflow this page covers. The Color Space Transform effect, Resolve Color Management's automatic tagging, and native ProRes RAW decoding on Mac all work in the free version of DaVinci Resolve, with no functional restriction on the color math itself.

Per Blackmagic's own free version product page, the free tier covers professional color grading tools without a Studio license. Where Studio genuinely enters the picture is a delivery target that needs Dolby Vision metadata authoring or HDR10+ analysis and export, both listed on Blackmagic's Studio product page as Studio-exclusive; workflows that lean on Studio-only Noise Reduction for a noisy high-ISO clip, covered earlier; or footage that simply won't decode in the free version to begin with, the 10-bit 4:2:2 H.265 limitation covered above.

Getting Canon R6 Mark II C-Log3 footage to grade correctly is a color management problem, and color management is not a feature Blackmagic gates behind the Studio license. Don't let a general free-versus-Studio comparison talk you into buying $295 of software just to make your R6 Mark II footage look right, unless you've actually hit one of the specific decode or noise reduction walls above. Our full DaVinci Resolve Studio price breakdown covers exactly what the license does and doesn't change if you're weighing it for other reasons.

A step-by-step example: taking one C-Log3 clip from flat to Rec.709

Here's the full sequence in order, from a fresh R6 Mark II clip in the Media Pool to a delivered Rec.709 grade, with every step from earlier in this guide placed where it actually happens in a real node tree.

1. Confirm the source and its color space. Right-click the clip, check Clip Attributes, and recall or verify which color space you selected in-camera, BT.709, BT.2020, or Cinema Gamut, along with whether it was recorded internally or over HDMI. This single check determines your Input Color Space two steps from now.
2. Build optimized media if the clip is stuttering on scrub. If it's a 10-bit 4:2:2 H.265 file playing back roughly, generate optimized media at Quarter or Eighth Resolution before you touch color, so you're not fighting playback performance and grading decisions in the same pass.
3. Node 1, Color Space Transform in. Set Input Color Space to match your camera's actual selection for an internal recording (Canon Cinema Gamut, Rec.2020, or Rec.709), or Rec.2020/Rec.709 if it came in over HDMI. Set Input Gamma to Canon Log 3, Output Color Space to DaVinci Wide Gamut, Output Gamma to DaVinci Intermediate.
4. Node 2, Noise Reduction, if the shot needs it. If the clip was shot at a high ISO and shows visible grain once it's out of Log, add a Temporal or Spatial Noise Reduction node here, immediately after the Color Space Transform, before any contrast or saturation moves.
5. Node 3, primary correction. With the clip sitting in DaVinci Wide Gamut, set your white balance using an eyedropper on a neutral reference in frame if you have one, then bring your black point and white point in toward the edges of your waveform using the Lift and Gain wheels, watching for clipping on the scopes rather than by eye alone.
6. Node 4, creative grade. Do your actual look here: contrast shaping, color balance between shadows and highlights, any secondary qualifiers or power windows the shot needs. This is the node where R6 Mark II footage behaves like footage from any other camera; nothing about C-Log3 changes how you grade once you're in a normal working space.
7. Node 5, Color Space Transform out. Input Color Space DaVinci Wide Gamut, Input Gamma DaVinci Intermediate, Output Color Space Rec.709, Output Gamma Rec.709 or Rec.709-A.
8. Check the result against the troubleshooting table below before you call the grade final, particularly if this clip is intercut with footage shot using a different in-camera color space setting or a different recording method.

Five nodes handle the entire mechanism from flat Log source to finished Rec.709 delivery, with Noise Reduction as the one optional insertion depending on how the clip was shot. Everything else, from the creative color decisions to the specific tool choices in node 4, is the same grading work you'd do on footage from any camera once it's sitting in a normal working space. A common mistake worth naming directly: adding a third or fourth Color Space Transform "just to see" what a different combination looks like, then forgetting to remove it. Two conversions per clip, one in and one out, is correct. Three is almost always a leftover from experimenting, and it's the fastest way to land in the log-on-log problem covered next.

Why does C-Log3 footage still look wrong after you've applied the Color Space Transform?

If you've followed the settings above and it's still off, work through these in order before assuming your footage is somehow bad.

First, the color space mismatch specific to this camera. Confirm your Input Color Space actually matches what you selected in the camera menu, Cinema Gamut, BT.2020, or BT.709, rather than defaulting to whichever one you used on your last project. Since the R6 Mark II genuinely offers all three, this is the single most avoidable mistake covered in this guide, and it's easy to make on a multi-day shoot where the setting changed between sessions.

Second, the HDMI mismatch covered earlier. Confirm you're not applying Cinema Gamut to a clip that was actually recorded externally, since Canon's own manual confirms that color space never survives the HDMI port. This swap is the most common cause of "my C-Log3 grade looks fine on some clips and wrong on others from the same shoot."

Third, log-on-log. If a clip looks oversaturated, hue-shifted, or has crushed color that doesn't respond normally to your color wheels, check whether a LUT is stacked on top of a Color Space Transform doing the same conversion, or whether Resolve Color Management is set to automatic tagging while a manual node is also applying its own transform to the same clip.

Fourth, timeline color space mismatch. If your project's overall Color Management is set to a working space your output node doesn't actually match, Rec.709 versus Rec.2100 being the most common version of this mistake, footage can look correct in isolation and wrong the moment it's viewed against your monitoring setup or exported.

Fifth, and easy to miss because the symptom looks like a color problem: check whether the clip actually decoded, or whether you're grading a low-resolution proxy that never got relinked to full-resolution media before export. A proxy built at Eighth Resolution can mask fine noise or banding that shows up the moment the final render relinks to the original file.

When the menus alone don't get you there fast enough

Everything in this reference is a settings problem with a settings answer, but confirming what a specific clip actually is, which color space, which recording method, is its own kind of friction on a deadline, especially when you're bouncing between Clip Attributes, Project Settings, and the node graph trying to reconstruct a decision you made on set days earlier.

TryUncle is the on-screen assistant for DaVinci Resolve on macOS. Ask in plain words, and Uncle points at the exact control on your screen. If you're on a Mac asking "why does my C-Log3 footage look grey" out loud at your screen, that's a faster route to the Color Space Transform panel than searching this page a second time mid-session. It's a paid app, currently in founder pricing at $29.99 a month for the first 100 seats, and macOS only, so it won't help a Windows editor working through Resolve's menus or the HEVC extension issue covered earlier. Check TryUncle for current pricing before deciding if it fits your workflow.

It's worth knowing the category has other tools built on a different premise. Sottocut, PremiereCopilot, heyeddie.ai, and cutagent.ai automate parts of an edit or answer chat questions about your footage, rather than watching your live screen and pointing at controls. If your goal is automating a cut, those solve a different problem. If your goal is finding the right Color Space Transform setting faster while you're the one making the decisions, on-screen guidance is the more direct tool for that specific job. Guided help inside Resolve beats digging back through a settings reference for the one dropdown you can't remember.

What's the full settings cheat sheet at a glance?

Before the table, here's the one-line version of everything above. Match your Color Space Transform's Input Color Space to whatever you actually selected in the camera's menu, not to a default you're used to from another shoot. Treat any HDMI-recorded clip as Rec.2020 or Rec.709, never Cinema Gamut, regardless of what the camera menu said. Reach for Canon's official LUT only for fast, low-stakes turnarounds where you won't grade further, and only once you've confirmed it matches the specific color space that clip used. Remember the R6 Mark II shoots C-Log3 only, never C-Log2 or plain C-Log. And if a clip won't come online at all, that's a decode problem, not a color space problem, and belongs in the import-failure section above, not in your node tree.

Match your Input Color Space to whatever you actually selected in the camera, not to a guess, keep your exposure at ISO 800 or above, and treat every HDMI-recorded clip as Rec.2020 or Rec.709 rather than Cinema Gamut. That's the entire mechanism, and it's shorter than it looks once you know which of the R6 Mark II's three color space options you're actually holding. If you shoot this camera regularly, it's worth writing your chosen color space on a slate or in your shot log the same day, since it's the one piece of metadata this whole workflow depends on and the one thing nobody remembers correctly a week later.