DaVinci Resolve Canon R1 C-Log3 Import Settings

What Color Space Transform settings does R1 C-Log3 footage need in DaVinci Resolve?

This is the core mechanism, and on the R1 it's a shorter list of decisions than on most other recent Canon bodies, because there's only one color space to account for.

Add a Color Space Transform to your first node. Set Input Gamma to Canon Log 3. Set Input Color Space to Canon Cinema Gamut. There's no camera menu to check first, no clip-by-clip verification of which color space was selected on a shoot day, because the R1's Custom Picture presets for both Canon Log 2 and Canon Log 3 lock to C.Gamut with no alternative. Set Output Color Space to DaVinci Wide Gamut and Output Gamma to DaVinci Intermediate. That moves the flat Log source into Resolve's own working space, where your actual grading happens.

On your last node, before final output, reverse it: Input Color Space DaVinci Wide Gamut, Input Gamma DaVinci Intermediate, Output Color Space Rec.709 (or Rec.2100 for an HDR delivery), Output Gamma Rec.709 (or ST 2084 / HLG for HDR).

If the clip was shot on the C2 preset instead of C3, the only change is Input Gamma: set it to Canon Log 2 rather than Canon Log 3. Everything else in this two-node pattern, Input Color Space, both Output settings, stays identical, since both presets share the same Cinema Gamut lock.

This "in, grade, out" structure is the same two-node pattern used across every recent Canon Log camera, from the R5 to the R6 Mark II to the Cinema EOS line, with DaVinci Wide Gamut as the shared intermediate stop. What changes camera to camera is step one, confirming Input Color Space. On the R1, that step doesn't require confirming anything beyond which Custom Picture preset was active, since Cinema Gamut is the only answer either preset gives you.

Does the R1 let you choose BT.709, BT.2020, or Cinema Gamut like the R6 Mark II?

No, and that's a real, sourced difference from Canon's own hybrid mirrorless lineup, not a guess carried over from a different camera's menu.

The Canon R6 Mark II records Canon Log 3 with an independent, selectable color space, BT.709, BT.2020, or Cinema Gamut, chosen separately from the Log gamma itself. The Canon R3, the R1's direct predecessor in Canon's sports-focused flagship line, works the same way: its own Canon Log settings menu, documented in Canon's R3 manual, states plainly that "YCbCr 4:2:2 (10-bit) color sampling and the BT.709/BT.2020/Cinema Gamut color space are used in Canon Log recording," with all three selectable for card recording. The R1 doesn't carry that menu forward. Its Custom Picture presets pair Canon Log 2 and Canon Log 3 each with one fixed color space, C.Gamut, and there's no separate dropdown to change it.

This isn't a limitation so much as a different design choice, and it removes an entire category of mistake that shows up on the R6 Mark II: a clip tagged with the wrong Input Color Space because nobody checked which of three options was selected in-camera on the day of the shoot. On the R1, that question has one answer regardless of which Log preset was active.

The R1 shares its Custom Picture system, and its Cinema Gamut lock, with the EOS R5 Mark II, not with the R3 it succeeds in Canon's sports lineup or the R6 Mark II most C-Log3 guides are written for. If you're used to checking a camera's color space menu before building a Color Space Transform, that step simply doesn't exist on the R1, and building a habit of checking it anyway costs nothing.

Why does R1 footage look different recorded over HDMI than internally?

If you're pulling a clip from an external recorder over HDMI rather than the R1's own card slots, the color space it needs in Resolve is not the same one you'd use for internal footage, and the underlying reason is a limit of HDMI itself, not a quirk specific to any one Canon body.

Rodrigo Polo, who has tracked Log-to-Rec.709 conversion behavior across Canon cameras for years, documented that "the HDMI standard does not allow this color space," referring to Cinema Gamut, and that HDMI defaults to Rec.2020 instead, in his writeup on the EOS R5's HDMI output. He found the same behavior on the EOS R6, and traced it directly to Canon's own R6 Mark II manual, which states outright that Cinema Gamut only applies to internal recording, with HDMI output "always" reading as Rec.2020. His separate writeup on the R5 confirms the same limitation there.

Canon hasn't published an R1-specific statement on this the way it did for the R6 Mark II, and this guide isn't going to claim a camera-specific confirmation that doesn't exist yet in Canon's own R1 documentation. What is verifiable is that HDMI as a signal standard doesn't carry Cinema Gamut tagging at all, which is a protocol-level limitation, not a per-camera one. Since both of the R1's Log presets lock to Cinema Gamut internally, and Atomos confirms the R1 outputs ProRes RAW over HDMI at up to 6K (6000x3164) through its recorder line, the safer working assumption for standard HDMI video output, not ProRes RAW, is the same one that applies to the R5 and R6: tag it Rec.2020, then confirm against your own footage rather than assuming Cinema Gamut carried through the cable.

Cinema Gamut is a color space HDMI itself doesn't carry, which is why footage recorded externally over HDMI from any recent Canon Log camera, the R1 included, needs a different Input Color Space than the same shot recorded internally. Confirm this against your own R1 files before committing to it as a blanket setting, since Canon's R1 manual doesn't state it as directly as the R6 Mark II's does.

What ISO should you shoot Log at on the R1?

The dynamic range figures below assume the footage was exposed the way Canon Log was built for, and a Color Space Transform can't repair an ISO chosen wrong on the shoot day.

Canon documents ISO 800 as the floor for Canon Log's designed dynamic range across its recent EOS R bodies, and the R1's own ISO range, 100 to 102,400 native, 50 to 409,600 expanded, doesn't change that baseline; it changes how far above or below it you can push. Shoot Log below ISO 800 and you're not just recording a darker image, you're giving up the extra highlight headroom that's the entire reason to shoot Log instead of a standard picture profile in the first place.

The R1's stacked sensor and DIGIC Accelerator processing give it a wider usable ISO ceiling than most hybrid bodies before noise becomes the limiting factor, which matters for the sports and photojournalism work this camera is built around, arena and stadium lighting rarely sits at a comfortable exposure. That headroom doesn't move the floor. ISO 800 remains the point where Canon Log's dynamic range actually starts behaving the way the curve was designed around, on the R1 the same as on every other recent Canon Log camera.

Exposing Canon Log below ISO 800 on the R1 throws away highlight headroom regardless of how far the camera's ISO range technically extends above it. If R1 footage clips highlights or crushes shadows after a correct Color Space Transform, check the original ISO before spending more time on the color node; a curve exposed below its designed floor won't grade the way one exposed at or above it will.

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

Every stop above the R1's ISO 800 Log baseline buys correct exposure in dim arenas and stadiums at the cost of more visible noise once that flat image gets stretched into a normal-contrast grade, and the Color Space Transform itself does nothing to reduce it.

DaVinci Resolve's Temporal and Spatial Noise Reduction tools, including the AI-driven UltraNR mode, are Studio-exclusive, listed among the Neural Engine features on Blackmagic's own Studio product page. Our full guide to DaVinci Resolve's noise reduction settings covers the specific Temporal frame counts, threshold values, and the tradeoff between denoising strength and softened detail in more depth than fits here.

Node placement matters as much as which mode you choose. Apply Noise Reduction on a node before your Color Space Transform pushes the clip out of Log, while the image is still flat and the noise pattern is closer to what the sensor actually captured, rather than after contrast and saturation have already amplified it. Sports and event work shot at high ISO under stadium lighting is exactly the situation this matters most for; a well-lit interview or daylight exterior near ISO 800 rarely needs this step at all.

Staying as close to ISO 800 as the shooting conditions allow keeps most R1 footage out of the noise reduction workflow entirely, and that's a shooting-day decision, not a Resolve setting. When the light genuinely won't allow it, place Noise Reduction before the Color Space Transform node, not after, so it works on the flatter, less-amplified signal.

What does independent lab testing show about the R1's rolling shutter and dynamic range?

Everything up to this point in this guide is about Resolve settings. This section is about what the sensor and codec actually deliver before any of those settings touch the image, since a Color Space Transform can't fix a physical property of the camera.

CineD's lab testing measured the R1's rolling shutter directly in video mode, separate from the 2.8ms stills-mode readout figure cited earlier in this guide. Per CineD's lab test of the R1, 6K CRAW at 25fps measured 8.3 milliseconds, which the review called "a very good result for 6K readout," and standard 4K at full frame width also measured 8.3ms. At 4K 120fps, rolling shutter dropped to 4.1 milliseconds, a figure CineD described as "astonishing." For comparison, the same test measured Canon's own EOS C400 cinema camera at 9.5ms in a comparable mode, meaning the stills-focused R1 actually out-reads a dedicated Canon cinema body on this specific measurement.

On dynamic range, CineD's IMATEST analysis of 6K CRAW developed to CLog2 at ISO 800 found 11.3 stops at a signal-to-noise ratio of 2, and 12.7 stops at SNR of 1, with waveform analysis showing 13 stops of usable range above the noise floor and faint additional detail visible into a 14th and 15th stop within the noise. The compressed 4K XF-AVC format performed slightly better in this specific test, at 13.3 stops (SNR 2) and 14.2 stops (SNR 1). Exposure latitude, CineD's measure of how much a shot can be pushed or pulled in post before it falls apart, came in around 9 stops, putting the R1 on par with the Sony A9 III and Panasonic LUMIX S1II, and roughly a stop ahead of the EOS C400 by the same test's numbers.

An 8.3-millisecond rolling shutter at 6K and 4K, dropping to 4.1 milliseconds at 4K 120fps, are physical properties of the R1's stacked sensor and readout speed, not settings a Color Space Transform, Resolve Color Management, or a noise reduction node can change after the fact. For a sports body specifically, that fast readout is arguably a bigger practical win than any single color setting in this guide, since it's what keeps a whip pan of a sprinting athlete or a fast puck from visibly skewing on the timeline.

How long can you record before the R1 overheats?

Sports and event coverage often means longer continuous takes than a typical hybrid shoot, and the R1's heat behavior determines how long a single clip can actually run before the camera stops you, separate from anything a card's capacity allows.

Per Canon's own General Movie Recording Precautions page for the R1, a ten-level temperature indicator appears on screen during recording. Levels one through seven display in white, the indicator changes color at level eight, and level nine flashes to warn that the camera will soon shut off automatically to protect itself. Canon's manual also notes that after a heat-triggered shutdown and a cooling period, resuming the same recording settings can trigger overheating again quickly, the same pattern documented on Canon's other recent EOS R bodies.

recordinglimits.com's testing of the R1, measured from a cold start at 23°C (73°F), found 4K 29.97p without crop runs unlimited, meaning it isn't heat-limited in that mode at all. Full HD at 179.82p (a high frame rate slow-motion mode) records for roughly 60 minutes or longer. 4K 59.94p with a crop applied runs about 50 minutes or longer, and 4K 59.94p without crop, the highest processing load of the group, runs approximately 40 minutes or longer before heat becomes the limiting factor.

A continuous 4K 59.94p uncropped take on the R1 has roughly a 40-minute heat ceiling before the camera warns you, then shuts down, which matters for anyone covering a full quarter, set, or period without a natural break to let the camera cool. Dropping to a cropped 4K mode, or to 4K 29.97p where heat isn't a factor at all per recordinglimits.com's testing, is the practical fix for coverage that has to run longer than that, not a Resolve setting.

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

Both reach the same destination, and on the R1 specifically, the choice is simpler than it is on a camera with a selectable in-camera color space.

Resolve Color Management, set under Project Settings, Color Management, with Color Science set to DaVinci YRGB Color Managed, lets you tag a clip's Input Color Space and Input Gamma once through Clip Attributes, and Resolve applies the conversion automatically on every node downstream, no manual Color Space Transform effect required. Because the R1 has exactly one color space, Cinema Gamut, regardless of which Log preset was active, batch-tagging a folder of R1 clips carries almost none of the risk it does on the R6 Mark II, where a folder can silently mix three different color spaces from different shooters or menu settings.

The one variable RCM doesn't sort automatically on its own is gamma: a folder mixing Canon Log 2 and Canon Log 3 clips, shot on different presets during the same event, still needs each clip tagged with the correct Input Gamma individually, since that's the one setting the R1's own menu structure does let you vary. A manual Color Space Transform node forces you to confirm gamma per clip or clip group, which is marginally slower for a single-gamma shoot but catches a mixed C2/C3 folder that automatic batch tagging by color space alone wouldn't flag.

Because the R1 locks every Log clip to Cinema Gamut, the color space half of Resolve Color Management's batch tagging is effectively risk-free on this camera; the gamma half, Canon Log 2 versus Canon Log 3, is still worth checking per clip if a shoot mixed both presets. That's a meaningfully lower-risk setup than the R6 Mark II's three-way color space menu, even before accounting for gamma.

What happens if you intercut R1 footage with R3 or R5 Mark II footage?

Sports and event teams running multiple camera bodies is common enough that this is worth walking through directly, especially since the R1 and its closest relatives don't all share the same in-camera color space behavior.

R1 footage sits in Cinema Gamut regardless of Log preset, as covered earlier in this guide. R5 Mark II footage, built on the same Custom Picture system as the R1, also locks to Cinema Gamut for both Canon Log 2 and Canon Log 3. R3 footage is different: its independent Canon Log menu lets a shooter select BT.709, BT.2020, or Cinema Gamut separately from the Log gamma, so an R3 clip dropped into the same bin as R1 and R5 Mark II footage might carry any of three color space tags depending on what was selected in that camera's own menu on the day.

Grade a mixed bin with one Color Space Transform preset built for Cinema Gamut and any R3 clips recorded with BT.2020 or BT.709 selected will show a visible color shift the wheels won't fully correct, because the node is decoding the wrong gamut into DaVinci Wide Gamut before you ever touch a wheel. The practical fix is the same one that applies across Canon's mixed-color-space lineup: sort clips by their confirmed source camera and, for R3 footage specifically, by whatever color space was actually selected, before building a single Color Space Transform preset and applying it broadly. Resolve's Color Groups, applied per camera or per clip group, let a correctly configured Color Space Transform live at the group level so every clip in that group inherits it, while an R3 group with a different Input Color Space setting is handled separately.

If the mixed footage needs a shared creative look on top of correct color management, not just a technically accurate conversion, our guide to color matching different cameras in DaVinci Resolve covers building that consistent look once each source is individually corrected to DaVinci Wide Gamut, the step this guide's two-node pattern gets every camera to regardless of which body or color space it started in.

R1 and R5 Mark II footage share the same fixed Cinema Gamut behavior, which makes them safe to batch-tag together, while R3 footage from the same event needs its own confirmed color space before it joins that same Color Space Transform preset. That's the specific failure point in a multi-body sports or event shoot that costs the least to catch before grading and the most to fix after.

Does DaVinci Resolve import the R1's internal 6K RAW footage?

Yes, and it's a genuinely different import path from every standard Log clip covered so far in this guide, because RAW footage doesn't carry a fixed Input Color Space and Input Gamma the way a C-Log3 clip does.

The R1's internal 6K RAW mode records in Canon's Cinema RAW Light codec, the same format used across Canon's Cinema EOS C-series line. DaVinci Resolve has decoded Cinema RAW Light natively since Resolve 14, with no plugin required, dragging and dropping a .CRM file into the Media Pool the same as any other clip. By default, per ShareGrid's breakdown of the Cinema RAW Light workflow, "the footage is debayered into the gamma Canon Log 2 and Cinema Gamut," which happens to be exactly the intermediate gamma and color space this guide's Color Space Transform settings are built around for standard R1 Log footage, even though RAW footage reaches that point through a different mechanism.

In the Media Pool, a Cinema RAW Light clip opens its own Camera RAW tab in the Clip Attributes or Color page inspector, rather than exposing Input Color Space and Input Gamma the way a standard C-Log3 clip does. That's where debayer resolution and decode settings live for a RAW clip; a standard Color Space Transform node isn't the right tool for it, and stacking one on top of an already-decoded RAW clip double-converts the image the same way stacking a LUT on top of a Color Space Transform does on a standard Log clip.

Externally, the R1 also outputs ProRes RAW over HDMI at up to 6K (6000x3164 pixels) to a compatible Atomos recorder, at frame rates up to 59.94fps, per Atomos's own EOS R1 compatibility page. ProRes RAW and internal Cinema RAW Light are two different RAW codecs from two different companies; Resolve decodes both natively, both through the same Camera RAW tab rather than a Color Space Transform, but they aren't interchangeable files, and confirming which one a given clip actually is, internal .CRM versus external ProRes RAW .mov, matters before you build a workflow around either.

A Canon R1 clip shot internally in 6K RAW debayers into Canon Log 2 and Cinema Gamut by default in DaVinci Resolve, the same endpoint this guide's Color Space Transform settings target for standard Log footage, but it arrives there through a Camera RAW decode, not a Color Space Transform node. Confirm which import path a given R1 clip took before applying either workflow to it.

Do you need DaVinci Resolve Studio for any of this?

No, not for the core Log grading workflow this guide covers. The Color Space Transform effect, Resolve Color Management's automatic tagging, and native Cinema RAW Light decoding all work fully in the free version, 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, per Blackmagic's Studio product page, is Temporal or Spatial Noise Reduction on high-ISO sports and stadium footage, Dolby Vision metadata authoring or HDR10+ analysis for a specific delivery target, or the 45 additional Resolve FX filters Blackmagic reserves for the Studio license.

Getting Canon R1 Log footage to grade correctly is a color management problem, and Blackmagic doesn't gate color management behind the Studio license. Don't let a general free-versus-Studio comparison talk you into a $295 upgrade just to make R1 footage look right, unless you've actually hit the noise reduction or HDR delivery walls above. Our full DaVinci Resolve Studio price breakdown covers exactly what the license changes 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 R1 clip in the Media Pool to a delivered Rec.709 grade.

1. Confirm the source. Check whether the clip's Custom Picture file was C2 (Canon Log 2) or C3 (Canon Log 3), and whether it came from the R1's card slots or an external HDMI recorder. Both Log presets lock to Cinema Gamut internally, so this step is about confirming gamma and recording path, not color space.
2. Build optimized media if playback is stuttering. For 6K RAW or oversampled 4K footage, generate proxy media at Quarter or Automatic resolution before touching color.
3. Node 1, Color Space Transform in. Set Input Gamma to Canon Log 3 (or Canon Log 2, matching the source). Set Input Color Space to Canon Cinema Gamut for internal footage, or Rec.2020 for footage recorded externally over standard HDMI video. Set Output Color Space to DaVinci Wide Gamut, Output Gamma to DaVinci Intermediate.
4. Node 2, Noise Reduction, if the shot needs it. For high-ISO footage from a dim arena or stadium, add Temporal or Spatial Noise Reduction here, right after the Color Space Transform, before any contrast moves.
5. Node 3, primary correction. With the clip in DaVinci Wide Gamut, set white balance from a neutral reference if available, then bring black point and white point in using the Lift and Gain wheels, watching the scopes for clipping.
6. Node 4, creative grade. Contrast shaping, color balance, secondary qualifiers, and power windows as the shot needs.
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 against a second R1 clip, or footage from another camera on the same shoot, before calling the grade final, especially on a multi-body event where R3 footage might be sitting in a different color space in the same bin.

Five nodes handle the mechanism end to end, with Noise Reduction as the one optional insertion depending on ISO. Because the R1 doesn't require a color space check per clip the way the R6 Mark II or R3 do, step one here is faster than on either of those cameras; it's mainly about confirming which of two possible gammas, not which of three possible color spaces, a given clip carries.

A second worked example: the R1's internal 6K RAW workflow

The five-node sequence above is for standard Log footage. An internal 6K RAW clip takes a different path from the first node onward, and it's worth walking through once so the two workflows don't get mixed on the same timeline.

1. Confirm the file is actually RAW. In the Media Pool, a Cinema RAW Light .CRM clip opens its own Camera RAW tab in the Clip Attributes or Color page inspector, rather than exposing Input Color Space and Input Gamma the way a standard C-Log3 clip does. If an R1 clip doesn't show that tab, it was recorded in a standard Log or non-Log mode instead, and belongs on the first worked example's path.
2. Check the default decode. Cinema RAW Light debayers by default into Canon Log 2 and Cinema Gamut, per ShareGrid's documented workflow cited earlier in this guide. Confirm the Camera RAW panel reflects that, or adjust it if a different decode gamma is needed for the project.
3. Set the debayer resolution for editing. Choose a lower debayer quality, Half or Quarter Resolution, for smooth scrubbing while cutting, separately from the resolution used for final render, which can go to Full or Premium if the GPU can handle it.
4. Grade from the decoded RAW, not through a second Color Space Transform. Once the Camera RAW panel has set the clip's working color space, stacking a Color Space Transform node on top of it the way you would a standard Log clip double-converts the image.
5. Match it back to any standard Log clips on the same timeline. With both sources sitting in the same DaVinci Wide Gamut working space, RAW decoded through Camera RAW, standard Log converted through a CST-in node, grade both against the same reference or scopes target so a cut between a RAW shot and a standard Log shot from the same event doesn't show a visible seam.

An internal R1 RAW clip's color space is set through the Camera RAW panel at the point of debayer, not through a second Color Space Transform node stacked on top of it. Treating a RAW clip like a Log clip that needs its own CST-in node is the most common way this specific workflow goes wrong, and it produces a double-converted image that's hard to diagnose without knowing to check for it first.

Is the Canon R1 actually worth buying just for video?

This is worth answering honestly rather than assuming, since the R1's price and marketing both point at stills first, and a reader landing on this page for Color Space Transform settings deserves a straight answer on whether the camera itself is the right tool.

Canon built and prices the R1 as a $6,299 flagship for sports photography and photojournalism, with its 40fps burst rate, cross-type autofocus across the full sensor, and dual CFexpress Type B slots doing most of the work in that pitch. Chris Niccolls, reviewing the camera for PetaPixel, put the video side in that context directly: "CLog 2 is also present and provides a good amount of dynamic range to work with, it is our preferred Canon log profile," he wrote, and separately noted that "the Canon R1 seems to be far more reliable than the R3 when it comes to following the action in video mode overall." That's a real endorsement of the R1's video autofocus specifically, not a claim that video is the camera's primary job.

For a buyer choosing between cameras specifically for video work, at or near the R1's $6,299 price, an EOS R5 Mark II offers the same Custom Picture system, the same Canon Log 2 and Canon Log 3 options, and a higher-resolution sensor for less money, while a dedicated Cinema EOS body trades stills autofocus speed for video-first ergonomics, XLR audio inputs, and built-in ND. The R1 makes sense as a video source specifically when its stills capability, the reason most buyers choose it, is also part of the job: a sports or news outlet shooting both stills and highlight video from the same body during the same event, where carrying one camera instead of two matters more than any single video spec.

One of the recurring questions in our 100,000+ member editing community is whether a camera's headline video specs, RAW resolution, frame rate, dynamic range, actually predict how well it fits a specific job, and the R1 is a clean example of where the answer is no. Its video specs are genuinely competitive with dedicated cinema bodies on paper, and CineD's own lab numbers back that up. What the specs sheet doesn't show is that Canon designed the autofocus, the ergonomics, and the price around a photographer who occasionally needs video, not a videographer who occasionally needs stills.

A camera's rolling shutter and dynamic range numbers can rival a dedicated cinema body without that camera being the right buy for a video-first editor, and the R1 is a case where both of those things are true at once. If you already own an R1 for its stills capability, everything in this guide gets its footage grading correctly. If you're choosing a camera specifically for video and stills autofocus isn't part of the job, the R5 Mark II or a Cinema EOS body will usually serve you better for the same or less money.

Why won't some R1 clips import into DaVinci Resolve at all?

If a clip won't come online or won't generate a thumbnail, that's a different failure mode from a wrong-looking grade, and it's worth ruling out before assuming a color setting is to blame.

Standard R1 Log footage uses XF-AVC rather than the H.264 codec found on the R6 Mark II, which means it doesn't share the H.264 body's advantage of sidestepping Windows' native HEVC decode requirements, and it doesn't share the specific H.265 free-version wall that trips up some other Canon bodies either, since XF-AVC is a different codec family entirely. Internal 6K RAW footage in Cinema RAW Light decodes natively in both the free and Studio versions of Resolve, with no plugin required, so a RAW clip failing to import is rarely a codec-support issue on Resolve's end.

Check these instead, roughly in order: a corrupted or partial card-to-drive transfer, which is the most common cause of a clip that shows a thumbnail but won't play or won't come fully online; a project timeline resolution set for standard 4K trying to preview a 6K RAW clip before Resolve has generated the right proxy or cache; or, for footage pulled from an external Atomos recorder, confirming the file is actually the ProRes RAW variant Resolve expects rather than a standard ProRes video file that happens to share a similar filename pattern. Our general DaVinci Resolve media offline guide covers the broader set of causes, moved files, missing render caches, and drive permission issues, if none of the R1-specific checks above resolve it.

A Canon R1 clip that won't come online in Resolve is more often a corrupted transfer, a missing render cache, or a mismatched timeline resolution than a codec Resolve can't decode. Confirm the file itself copied correctly and that its actual format, standard Log video versus internal RAW versus external ProRes RAW, matches what you're assuming before troubleshooting further.

Do you need proxies to edit R1 6K footage smoothly?

Often, yes, and for a different reason depending on whether you're cutting internal 6K RAW or the standard XF-AVC 4K modes.

Internal 6K RAW is real GPU and CPU work regardless of file size on disk, since every frame needs a debayer pass before Resolve can display it at all, the cost any RAW format carries on any camera. Standard 4K, especially the oversampled-from-6K modes at higher frame rates, leans on XF-AVC decoding, which is lighter than RAW but still meaningful load on a lower-powered laptop.

For RAW footage, the debayer resolution setting in the Camera RAW panel, covered in the second worked example above, is the first lever to pull, Half or Quarter Resolution for editing, full resolution reserved for final render. For standard Log clips, right-click a clip or bin in the Media Pool and choose Generate Optimized Media to transcode a local proxy copy in the background, at a resolution and codec set under Project Settings, Master Settings, Optimized Media and Render Cache. Our guide to setting up DaVinci Resolve proxy media on a slower laptop covers resolution and codec choices, ProRes on a Mac, DNxHR on Windows, in more depth than fits here.

Proxies and a lower debayer resolution fix playback performance, not color. Building optimized media or dropping the debayer setting from R1 footage doesn't change or skip the Color Space Transform or Camera RAW steps covered earlier in this guide; Resolve relinks to full-resolution originals for the final render regardless of what you cut with.

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

Before the table, the one-line version. Input Gamma matches whichever Custom Picture preset was shot, Canon Log 2 or Canon Log 3. Input Color Space is Cinema Gamut for internal footage on every Log preset the R1 offers, no camera menu check required, and Rec.2020 for anything recorded externally over standard HDMI video, not ProRes RAW. Stay at or above ISO 800. Internal 6K RAW takes a different path entirely, through Camera RAW, not a Color Space Transform node. Plan long uncropped 4K takes around the roughly 40-minute heat limit. And when a clip won't come online, check the file transfer and format before assuming Resolve can't decode it.

If the menu hunting mid-session is the actual friction, not the settings themselves: 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.

The Canon R1's Log setup is one of the more forgiving ones in Canon's current lineup, not because the camera is simple, but because it removes a decision other Canon bodies force on you. Cinema Gamut is the only color space either Log preset records to, so the Color Space Transform question that trips people up on the R6 Mark II or a mixed R3 shoot mostly doesn't apply here. What still needs checking, gamma preset, recording path, whether a clip is standard Log or internal RAW, matters more on this camera than on most, precisely because everything else has already been decided for you.