How to Set Up REDWideGamutRGB and Log3G10 in Resolve

Most RED color problems in Resolve come from one mistake: the same picture gets converted twice. The image suddenly looks too contrasty, highlights get crunchy, skin shifts, and a monitoring LUT that should be subtle looks twice as strong. Resolve gives that mistake four places to hide. The conversion can happen in Resolve Color Management, in a Color Space Transform node, in an IPP2 output LUT, or through RED RAW metadata. So be explicit about where it happens. Pick one path and keep the rest out of the way. The rule underneath everything below is one input interpretation, one output transform. Decode the camera originals as REDWideGamutRGB and Log3G10, grade in that log state, then convert once to the delivery color space.

Why REDWideGamutRGB and Log3G10 are the normal starting point

RED’s current IPP2 workflow is built around REDWideGamutRGB, shortened to RWG, and Log3G10. REDWideGamutRGB is the camera color space. It's designed to contain the colors RED cameras can record without clipping them prematurely. Log3G10 is the log encoding that carries that tonal range in a grading-friendly way. The value is consistency. Older RED workflows leaned on camera-specific combinations like REDgamma and DRAGONcolor variants. IPP2 gives you a common working state across current and past RED cameras: RWG for color, Log3G10 for tone. Once the footage is in that state, the grade and the output transform become predictable. Think of the IPP2 path as three stages:

A clean three-stage IPP2 path keeps RAW development, grading, and display output separate.

Primary RAW development into REDWideGamutRGB and Log3G10
Creative grading while the image is still in that log/wide-gamut state
Output transform to Rec.709, P3, Rec.2020, HDR, or whatever the delivery requires

Resolve can do all three. It will also let you do the same stage in multiple places. That flexibility helps when you know what is happening. It hurts when a project arrives carrying inherited LUTs, RAW metadata, or mixed camera settings, often after an XML round trip from another system.

Start by deciding who owns color management

Before touching clip settings, decide whether the project will be managed at the project level or at the node level. For most teams, there are two clean Resolve approaches:

Resolve Color Management: Resolve handles input transforms and output transforms based on project settings and clip input color spaces.
DaVinci YRGB with manual transforms: You decode RED RAW as RWG/Log3G10, grade manually, and use a Color Space Transform node or approved output LUT near the end of the node tree.

Both paths produce correct results. The hybrid is what breaks. Resolve Color Management transforms the footage, RED RAW settings apply an IPP2 output transform as well, and someone adds a Rec.709 LUT on top because the image still looks flat in one viewer. For editorial turnovers and assistant-driven conforms, Resolve Color Management is easier to standardize. For colorists who want explicit control, manual CST nodes are easier to audit, because the transform is visible in the node graph. Everyone on the job needs to know which path your team is using.

Workflow path	Input handling	Where the output transform happens	Best fit	Main risk
Resolve Color Management	Tag RED clips as REDWideGamutRGB / Log3G10, or let Resolve assign them correctly	Project output color space	Assistant-driven conforms, mixed-camera timelines, standardized facilities	Adding extra CST nodes or Rec.709 LUTs on top of project color management
DaVinci YRGB with manual CST	Decode RED RAW as REDWideGamutRGB / Log3G10 in Camera RAW settings	A visible CST node, timeline node, or approved output LUT near the end of the grade	Colorist-controlled grades where every transform needs to be visible	Hidden transforms in group nodes, timeline nodes, compound clips, or LUTs
RED RAW or IPP2 metadata-driven viewing	Camera or RMD metadata may carry look settings or monitoring choices	Sometimes through an IPP2 output look or LUT, depending on setup	Matching a production reference or preserving a DP-approved monitoring intent	Treating a viewing transform as if it were the final color pipeline

Set the RED RAW decode to RWG and Log3G10

In Resolve, RED RAW settings live under Camera RAW in Project Settings. You can also adjust individual clips from the Camera RAW controls when needed. For a clean IPP2-style grading setup, set the RED RAW profile so new R3D clips decode into REDWideGamutRGB and Log3G10. A typical project-level RED RAW setup looks like this:

Camera RAW profile: RED
Decode using: Project, if you want one consistent decode across the job
Color science: IPP2, where available
Color space: REDWideGamutRGB
Gamma curve: Log3G10
ISO, color temperature, tint: Camera metadata unless the color team wants project-level defaults
Decode quality: Set for playback during editorial or grading
Force debayer to highest quality: Enabled for final render when performance allows

The two settings that decide the image are color space and gamma curve. RED’s own Resolve guidance recommends working with the RAW footage in a logarithmic gamma space. That keeps flexibility and gives colorists a familiar starting point. RWG/Log3G10 is that starting point.

REDWideGamutRGB and Log3G10 are source interpretation settings attached to the RAW clip.

Decode quality is a performance setting, not a look decision. If a system can't play 6K or 8K R3D smoothly, lowering decode quality for work sessions is normal. For final output, use the highest practical debayer quality so you aren't baking a lower-quality decode into the master. If you change Camera RAW project settings after media is already imported, verify that existing clips are actually following those project settings. Some clips will be set to Clip instead of Project. That happens most in conformed timelines and in projects that have passed through multiple hands. The media isn't broken, but clip-level RAW settings are overriding the project.

Respect camera metadata, but don't let it surprise you

Because R3D is RAW, many image decisions are metadata-driven and non-destructive. Camera color space, gamma, and ISO travel with the clip. So do white balance, tint, and look information. RED also uses RMD sidecar files to store non-destructive adjustments without changing the original R3D. That's useful, but it can confuse a conform if nobody knows which metadata should be honored. Common metadata sources include:

In-camera look settings
REDCINE-X PRO changes written to RMD
Clip-level RAW changes made in Resolve
Camera RAW project defaults inside the Resolve project
LUTs or output transforms added for editorial viewing

The cleanest finishing workflow treats the R3D as the source of truth for capture metadata. From there, decide deliberately which metadata should affect the grade. White balance and ISO metadata make good starting points. What your team must not do is treat a baked-looking editorial LUT or viewing transform as the final color pipeline. If the DP created a show LUT or IPP2 monitoring look on set, ask whether it's a creative reference or a required transform. Those are different things. A creative LUT may belong before the final output transform, assuming it was designed for RWG/Log3G10. An output LUT that converts RWG/Log3G10 to Rec.709 must never sit on top of another Rec.709 output transform.

Using Resolve Color Management

If you're using Resolve Color Management, the project settings describe both the source and the destination. Three steps:

Check that RED clips are tagged as REDWideGamutRGB and Log3G10. Resolve often recognizes them on its own. If it doesn't, assign the input color space manually.
Set the destination to match your monitoring and delivery target.
Add no separate CST from RWG/Log3G10 to Rec.709 on those clips, because Resolve is already handling that conversion.

For a normal SDR broadcast or web master, the destination is Rec.709 Gamma 2.4. Web-only teams sometimes choose Gamma 2.2 instead, depending on their display assumptions. For theatrical or HDR the output decision changes, but the shape of the pipeline doesn't: RWG/Log3G10 in, delivery color space out. A color-managed project earns its keep on mixed-camera jobs. Tag RED as RWG/Log3G10, ARRI as LogC/Wide Gamut, Sony as S-Gamut/S-Log, and so on. Everything then works into a common timeline space and outputs to the target. The same warning applies: don't add camera-to-Rec.709 LUTs just because the footage started as log.

Correct input tagging lets mixed camera sources enter one shared managed path before delivery.

A properly configured viewer or external monitor should now show a normal display image, with no extra viewing LUT on each RED clip. If the image is still log-flat, one of three things is wrong: the clip isn't tagged correctly, the output color space isn't set, or the viewer path isn't what you think it is.

Using manual CST nodes

Manual transforms are straightforward if you keep the node tree disciplined. Decode the R3D as RWG/Log3G10. Do your balancing and creative work while the image is still in that state. Then use one output transform near the end. A simple node structure might be:

RAW decode: REDWideGamutRGB / Log3G10 in Camera RAW settings
Early nodes: exposure balance, white balance trim, noise reduction if needed
Middle nodes: contrast shaping, secondaries, look work
Late node: Color Space Transform from REDWideGamutRGB / Log3G10 to delivery space
Final trim nodes: legalizing, small display-referred adjustments, if required

For an SDR Rec.709 delivery, set the CST output to Rec.709 with the appropriate gamma, commonly Gamma 2.4 for broadcast-style monitoring. Set tone mapping and gamut mapping deliberately. Those two settings control highlight rolloff and how the transform brings saturated camera colors into the smaller output gamut. The advantage of this method is visibility. If a producer asks why the highlights look different from the offline, you can point to the exact output transform and tone mapping choice. If a shot looks double transformed, disable the CST and you immediately see whether another transform is active somewhere else. The cost is that every timeline, group, shared node, and compound clip needs discipline. A CST hidden in a group post-clip node, plus another CST on the timeline, creates the same double-transform problem as bad project color management.

Choosing the output transform

The output transform is the technical mapping from RWG/Log3G10 into the space where the master will be viewed. RED’s IPP2 output stage exists to map wide-gamut camera data into an output color space with tone mapping, highlight rolloff, and gamut mapping. Common output targets include:

Rec.709 Gamma 2.4 for SDR broadcast-style mastering
Rec.709 Gamma 2.2 for some computer-display-oriented work
P3 variants for cinema or certain display pipelines
Rec.2020 or HDR transforms for HDR delivery
A log intermediate if you're handing the grade to another finishing system

Don't choose Rec.709 just because the footage looks flat. Choose it because the deliverable or monitoring path is Rec.709. If the job needs HDR and SDR, you may need separate output transforms or separate trims. A single Rec.709 transform baked into the grade won't preserve an HDR path. Also be careful with LUTs. In IPP2, classify every LUT as either a creative LUT or an output transform LUT. A creative LUT changes the look while staying within RWG/Log3G10 assumptions. An output LUT converts the image to a display space. Apply an output LUT and then also use Resolve Color Management or a CST to output Rec.709, and you have converted twice.

A single output transform preserves the scene; stacked transforms can crush highlights and shadows.

How double transforms usually happen

Double transforms happen because every department needs to see a pleasing image. The camera team monitors with an IPP2 look. Editorial cuts with a Rec.709 LUT. The assistant editor bakes proxies with a viewing LUT. The colorist inherits a Resolve timeline with project color management enabled. No single one of those choices is wrong. Stacking them is. Typical failure modes look like this:

Highlights clip or roll off too aggressively even though the RAW has detail
Saturated colors shift, especially reds, LEDs, wardrobe, or neon
A LUT that should be subtle looks extreme
Switching a RED clip between Project and Clip decode changes more than expected
The viewer looks right, but exports are darker or more contrasty

When you see these symptoms, work backward. Disable these one at a time until the RED image returns to a flat RWG/Log3G10 state:

Timeline LUTs
Group nodes
Output LUTs
CST nodes
Project color management

Then rebuild the intended path with only one output transform. A healthy RWG/Log3G10 image looks flat before display conversion. That is expected. What it should not do is already look like finished Rec.709, unless an output transform is active somewhere.

Matching project settings to camera originals

The best time to prevent RED color confusion is before anyone makes the first proxy or editorial transcode. Ask for the camera report, confirm the RED camera model and color pipeline, and preserve the R3D folder structure during ingest. R3D clips can be split into multiple file parts during recording, so sloppy file handling creates relink and conform problems later. For Resolve finishing, your conform should reconnect to the original R3D files rather than to editorial proxies with transforms already baked in. Proxies are fine for cutting, but document how they were made. Were they flat RWG/Log3G10, or did they carry a Rec.709 viewing transform? If the editor cut against Rec.709 proxies, send the colorist a reference export. They can then compare intent without inheriting a hidden transform. Project-level consistency counts most when multiple assistants import media over time. Set the Camera RAW profile to RWG/Log3G10 before import, and new R3D media enters the project in the expected state. If people import first and configure later, check whether the older clips follow project decode settings or carry clip-level overrides. The same applies to shots adjusted in REDCINE-X PRO. RMD sidecars can carry non-destructive look changes. Decide whether those are production-approved looks, temporary viewing adjustments, or values to reset before grading.

Export settings and monitoring are part of the color pipeline

The final render should match the output transform and the monitoring target. If you're mastering SDR Rec.709 Gamma 2.4, monitor that way and render with tags and codec settings that fit the delivery spec. If you're making a mezzanine for another facility, don't bake a Rec.709 transform into a file they expect to be log. Resolve format support for RED is mature. Recent versions include RED SDK support and GPU-accelerated RED workflows, depending on hardware and Resolve edition. Performance still depends on your GPU, storage, and decode quality, plus resolution and whether you're using Studio-only features. If playback is the issue, lower decode quality during work. Don't change color management just to make playback easier. For final output from R3D, force the debayer quality as high as practical. Confirm that the output transform is exactly the one your team intends for the master. If a timeline contains both RED and non-RED cameras, verify that Resolve is interpreting each source type correctly before judging the final output. A perfect RED transform won't fix a Sony or ARRI clip with the wrong input-space tag.

A default for most RED finishing jobs

For a standard SDR grade from RED camera originals, a clean default is:

Conform back to original R3D media
Set RED RAW decode to IPP2, REDWideGamutRGB, Log3G10
Use camera metadata for ISO and white balance unless the colorist chooses otherwise
Grade in RWG/Log3G10 or in a managed timeline space
Apply one output transform to Rec.709 Gamma 2.4 for SDR monitoring and delivery
Keep editorial LUTs and viewing LUTs out of the final transform path unless your team intentionally makes them part of the look

That setup preserves RED RAW flexibility while keeping the color pipeline easy to explain. When the image is wrong, only a few places can be at fault: the RAW decode, the input assignment, and the output transform. After those, check creative LUTs and export tags. The habit that holds all of it together is separating input interpretation from output display. REDWideGamutRGB and Log3G10 describe what the camera data is after RAW development. Rec.709, P3, or HDR describes where the finished image is going. Keep those roles separate and transform once.

FAQ

Yes. For most modern RED IPP2 workflows, decoding R3D media as REDWideGamutRGB and Log3G10 is the safest starting point. REDWideGamutRGB preserves the camera color gamut. Log3G10 keeps the tonal range in a grading-friendly log state. From there, apply a single output transform to the required delivery space, such as Rec.709, P3, or HDR.

Set RED RAW decode options in Project Settings under Camera RAW, using the RED profile. Choose IPP2 where available. Then set the color space to REDWideGamutRGB and the gamma curve to Log3G10. Clip-level RAW settings can override the project settings, so check any conformed or inherited timelines carefully.

Yes. In a Resolve Color Management workflow, RED clips should be assigned or detected as REDWideGamutRGB and Log3G10 at the input stage. Resolve then maps them through the selected timeline and output color spaces. If Resolve is already doing the output conversion, avoid adding a separate RWG/Log3G10 to Rec.709 CST or output LUT on the same clips.

A common cause is a double transform. It happens when an IPP2 output LUT, a Color Space Transform node, or project-level color management gets stacked with timeline LUTs or baked proxy looks. The result can be crushed shadows, clipped highlights, and dense skin tones with color shifts. Disable transforms one at a time until the image returns to a flat log state, then rebuild the intended path with only one output transform.

Not always. Some IPP2 LUTs are output transform LUTs, designed to convert REDWideGamutRGB and Log3G10 into a display space such as Rec.709. Creative LUTs instead shape the look while staying within the expected working color space. Applying an output LUT and then also using Resolve Color Management or a CST to Rec.709 will transform the image twice.

Treat proxies as editorial viewing media, not as the color source, and document whether they were made flat or with a Rec.709 viewing transform. Aspect can keep the camera originals, editorial exports, and generated viewing media together, including proxies and previews.