Panasonic GH6 V-Log Import Settings for DaVinci Resolve

Does the GH6 record full V-Log, or is the official LUT slightly off?

This is the question that separates a GH6 workflow from every other Panasonic V-Log camera, and it's worth understanding before you trust a static LUT the way you might on an S5 II or S1H.

RedShark News's review describes GH6 footage as "Full V-Log/V-Gamut (not V-Log L)," distinguishing it from the reduced-range V-LogL profile Panasonic shipped on the GH5. That framing is accurate as far as naming goes: Panasonic never labeled GH6 footage with the V-LogL tag the way it did on the GH5. But a detailed discussion on DPReview's own user forum, titled directly "Panasonic GH6 V-log LUT is lost. Where is the real one?", and mirrored on Blackmagic's forum with the same title, points to something more specific: DPReview's own technical review reportedly showed a dynamic range curve where the GH6's actual recorded values diverge from what the standard, official Panasonic V-Log to Rec.709 LUT assumes, even though Panasonic dropped the V-LogL naming distinction it used on the GH5 for a curve that isn't identical to VariCam's reference V-Log either.

In practice, that mismatch doesn't break the Color Space Transform workflow covered above; the preset still gets you to a workable starting grade close enough to build a real correction from. What it does mean is that a static third-party LUT built against the textbook V-Log curve, one that might look perfect on an S1H or a VariCam clip, can land slightly hot, slightly crushed, or slightly off-hue on GH6 footage specifically, and that a colorist grading by eye and scopes rather than trusting a LUT at face value will catch it faster than one who doesn't.

Panasonic dropped the V-LogL naming distinction on the GH6 that it used on the GH5, but independent testing and Blackmagic's own user forum suggest the camera's actual V-Log curve still isn't a perfect match for the reference curve its official LUT assumes. A manual Color Space Transform using the Panasonic V-Gamut/V-Log preset, followed by grading against your scopes rather than trusting a LUT blindly, is the more reliable default on this specific camera.

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

Both reach the same finished image. The choice depends on how consistently your project was shot and whether Resolve is actually tagging your clips correctly on ingest.

Resolve Color Management, set under Project Settings, Color Management, with Color Science set to DaVinci YRGB Color Managed, lets you assign Panasonic V-Gamut and Panasonic V-Log as a clip's input color space directly through Clip Attributes, and every downstream node inherits the conversion automatically with no Color Space Transform effect anywhere in your tree. That's the faster setup for a project built almost entirely from GH6 footage shot the same way.

It doesn't always tag automatically. A discussion on Blackmagic's own user forum, Input Color Space Panasonic V-Log not automatically set, covers exactly the situation where Resolve leaves V-Log clips sitting in Rec.709 as though they were untagged rather than recognized V-Log sources. When that happens on a GH6 project, set the tag manually through Clip Attributes, once per clip or per bin, rather than trusting automatic detection every time.

A manual Color Space Transform node gives you more control per clip or per group, which matters the moment you're cutting GH6 footage against a different camera in the same timeline. Our guide to color matching different cameras in DaVinci Resolve covers that multi-camera normalization step in more depth, and it lists V-Gamut with V-Log as Panasonic's standard input pairing for exactly this reason, GH6 included.

What is Dynamic Range Boost, and how is it different from Dual Native ISO?

Dynamic Range Boost isn't the same feature as the Dual Native ISO on Panasonic's S1H and S5 II, and mixing them up is the fastest way to expose a GH6 clip wrong.

On the S5 II and S1H, Dual Native ISO gives you two selectable, fixed sensitivity points, ISO 640 and ISO 4000 for V-Log on the S5 II, and the camera switches between two entirely separate gain circuits depending on which one you pick. The GH6 works differently. Per DPReview's own technical explainer on the mechanism, the GH6's Dynamic Range Boost mode "blends a high-gain and low-gain output from each frame into a single result," reading both signal paths from the same exposure simultaneously and combining them in real time, rather than switching between two discrete ISO settings the way Dual Native ISO does. Panasonic itself describes it as real-time HDR composition from a single exposure.

That distinction changes your base ISO math directly. Per Panasonic's own DC-GH6 operating instructions and confirmed across multiple independent reviews, V-Log's base ISO sits at 250 with Dynamic Range Boost off, and jumps to a minimum of ISO 2000 the moment you switch Dynamic Range Boost on, since the feature needs headroom on both the high-gain and low-gain reads to blend cleanly. You can't dial Dynamic Range Boost down to ISO 800 or 1000 in V-Log; 2000 is the floor. Dynamic Range Boost also caps your frame rate at 60fps, so if you need 120fps slow motion, you're shooting without it regardless of ISO preference.

Dynamic Range Boost on the GH6 blends two gain reads from a single exposure into one frame, while Dual Native ISO on the S5 II and S1H switches between two separate, selectable ISO points, and treating the two as interchangeable is a common but avoidable exposure mistake. If you've been dialing in ISO 640 out of habit from an S5 II project, that number does nothing useful on a GH6; the camera's own floor with the feature engaged is 2000, not 640.

How much dynamic range does GH6 V-Log actually deliver?

Panasonic's marketing number and an independent lab's measured number rarely match exactly on any camera, and the GH6 is no exception, though its real-world result still holds up well for its sensor class.

Panasonic quotes roughly 12 stops of dynamic range for V-Log with Dynamic Range Boost off, and 13+ stops with it on. CineD's own lab test of the GH6 measured that claim directly with IMATEST analysis. With Dynamic Range Boost off at ISO 250, CineD found the image "very noisy," clipping at 80% IRE, with a measured 9.4 stops at SNR 2 and 10.5 stops at SNR 1, well under Panasonic's marketing figure at that setting. With Dynamic Range Boost engaged at ISO 2000, the same test found roughly 11 stops at SNR 2 and 12.2 stops at SNR 1, plus what CineD described as a faint 13th stop and a hint of a 14th above the noise floor. "Those are really good results for a Micro Four Thirds sensor camera, state of the art!" CineD wrote of that result, a genuinely strong measured figure for a Four Thirds sensor even before accounting for the marketing gap.

The gap between Panasonic's stated number and CineD's measured one is normal and worth expecting on every camera brand's spec sheet, not a defect specific to the GH6. What it tells you practically is that Dynamic Range Boost isn't optional if you actually need the highlight latitude V-Log is supposed to buy you. Shooting V-Log at ISO 250 with Dynamic Range Boost off gives up nearly two full stops of usable dynamic range compared to shooting it properly at ISO 2000 with the feature engaged, a bigger practical difference than the ISO number alone suggests.

The GH6's dynamic range claim holds up better with Dynamic Range Boost engaged than without it, and an independent lab measured its boosted result as genuinely competitive for a Micro Four Thirds sensor, not just a marketing figure. If your delivery needs the highlight latitude V-Log promises, treat Dynamic Range Boost as part of the V-Log workflow, not an optional add-on you can skip to save a stop of noise elsewhere.

Should you shoot V-Log at all, or does HLG or a standard profile make more sense?

V-Log isn't the only high-dynamic-range option on the GH6, and it's the one that demands the most from your Resolve workflow, so it's worth knowing when to skip it.

The GH6 also shoots HLG (Hybrid Log-Gamma), a profile built for HDR delivery that displays reasonably close to correct on an HDR monitor without a Color Space Transform doing the heavy lifting first, unlike V-Log, which looks deliberately flat and grey until it's converted. A discussion thread on DPReview's forums comparing the two for GH6 shooters lands on a practical distinction worth carrying into your own decision: HLG suits projects headed straight to an HDR delivery with minimal grading, while V-Log suits anything getting an actual color pass, since it holds more information in the shadows and highlights for a colorist to pull from later.

Editors on DPReview's GH6 V-Log video noise thread also note a visible magenta push in V-Log footage on a vectorscope, more pronounced than the same shot in Rec.709, which is expected behavior for a flat log curve and not a sign anything is broken; it corrects itself once the Color Space Transform and your primary white balance are both dialed in. Treat that magenta cast as confirmation you're actually looking at unconverted V-Log, not as a fault to chase down separately.

HLG is built to look reasonably close to finished on an HDR display with no Color Space Transform standing between you and delivery, and V-Log is built to look flat and slightly magenta until you apply one. If you've defaulted to V-Log out of habit on a project that's really just an HDR HLG delivery with a light touch-up, you may be adding a grading step you don't actually need.

Does the GH6 ship with a V-Log to Rec.709 LUT?

No, not preinstalled, and this is a gap the GH6 shares with the rest of Panasonic's hybrid lineup rather than something unique to it.

The GH6 includes V-Log View Assist, which lets you load LUT data to preview a graded look live on the rear screen or over HDMI while you're still shooting flat. Like the rest of Panasonic's hybrid bodies, the camera arrives with nothing loaded into that feature; you supply the LUT yourself.

Panasonic does maintain a public LUT library, the VARICAM LUT LIBRARY, offering 35 conversion and creative LUTs including a genuine V-Log to Rec.709 conversion. That page states plainly the library is built "to VariCam cinema cameras and the AU-EVA1," Panasonic's cinema and compact cinema lines, not the GH6's Four Thirds hybrid sensor. Given the curve mismatch covered earlier in this guide, even that official LUT is a rougher starting point on GH6 footage than it would be on genuine VariCam source, since it's built against a reference curve the GH6's actual recorded values don't perfectly match.

That combination, no first-party LUT and an official one that's a loose fit at best, is exactly why a manual Color Space Transform using the Panasonic V-Gamut/V-Log preset is the steadier default on this camera specifically. It doesn't depend on any external file, and it's the version of the conversion Resolve's own preset was actually validated against. Our guide to installing LUTs in DaVinci Resolve covers the mechanics of loading a .cube file into Resolve's LUT folder if you do want to test a third-party GH6-specific LUT against your own footage before committing a project to it.

The GH6 gives you a way to preview a LUT on set and points you toward a V-Log to Rec.709 conversion built for a different camera line, but nothing built specifically for the GH6's own sensor. A manual Color Space Transform, graded by eye against your scopes rather than trusting a static file, sidesteps that gap entirely.

Does DaVinci Resolve import GH6 footage cleanly, or does it show Media Offline?

If a GH6 clip shows up as Media Offline, refuses to thumbnail, or stutters on scrub, that's a decode problem, not a color problem, and it's worth ruling out before you touch a single Color Space Transform setting.

Blackmagic's own free version product page caps its stated support at, in the company's words, "virtually all 8-bit video formats," on the free product page, and every one of the GH6's V-Log recording paths, ProRes and both H.265 modes alike, is 10-bit. In practice, plenty of 10-bit 4:2:0 H.265 footage decodes fine in the free version. The GH6's 4:2:2 H.264-adjacent C4K/4K mode and its higher-bitrate ProRes files are the ones more likely to actually hit the wall, the same pattern documented across other 10-bit mirrorless bodies.

Windows adds a second, separate wrinkle for the GH6's H.265 clips specifically. Microsoft doesn't ship HEVC decoding natively with Windows, so even Resolve Studio needs the "HEVC Video Extensions" package from the Microsoft Store installed at the OS level before any H.265 file decodes at all. Filmmaking Elements' guide to fixing HEVC media offline errors walks through that install directly. Mac users skip that particular step, since macOS has included HEVC decoding at the OS level since Sierra, though they can still hit the free-versus-Studio 10-bit wall regardless of platform. ProRes decodes natively on Mac with no extra install; on Windows, ProRes decode support depends on your specific setup and is worth confirming before you build a GH6 ProRes workflow around a PC edit bay.

You have three real options if a V-Log clip won't come online:

1. Upgrade to Studio. Puget Systems' breakdown of hardware decoding support in DaVinci Resolve confirms Studio adds hardware-accelerated H.264 and H.265 decoding on supported GPUs, resolving both the 10-bit decode gap and, on Windows, still requiring the separate Microsoft HEVC extension for H.265 specifically.
2. Transcode before you import. Convert the offending clips to an intraframe codec like ProRes or DNxHR outside Resolve first, using whatever converter you already have, then import the transcoded files instead of the originals.
3. Generate proxy or optimized media inside the free version, though this path is inconsistent for 10-bit 4:2:2 sources specifically on Free, since Resolve still has to decode the original once to build the proxy, the exact step that's 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, everything from moved files to a missing render cache, if the fix above doesn't fully resolve your case.

A GH6 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 decode limitation tied to bit depth, chroma subsampling, and codec. Confirm which Resolve version you're running and which exact recording path captured the clip before you spend time troubleshooting a Color Space Transform on a file that hasn't actually decoded yet.

Do you need proxies for 5.7K ProRes or H.265 editing?

Often yes, and the reason splits depending on which of the GH6's three recording paths you shot.

The internal ProRes 5.7K files are large by codec design, since ProRes trades file size for editing-friendly intraframe compression, and a 1.9Gbps bitrate adds up fast on a laptop SSD. The H.265 modes are smaller on disk but lean on Long GOP inter-frame prediction that's expensive to decode in real time without a dedicated hardware decode block, especially on an older laptop GPU. Both situations respond to the same fix: build a lower-resolution stand-in before 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 local proxy copy in the background, at a resolution and codec you set under Project Settings, Master Settings, Optimized Media and Render Cache. For 5.7K 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 5.7K clip into a quarter-resolution proxy on a 4K timeline automatically, dropping further to eighth resolution manually if playback still stutters.

Codec choice follows your platform. 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 a GH6 clip doesn't change or skip the Color Space Transform step covered earlier in this guide; Resolve relinks to your full-resolution originals automatically for the final render regardless of what you cut with, so your Panasonic V-Gamut/V-Log tagging applies exactly the same way it would without proxies in the pipeline.

Is there a Blackmagic RAW or ProRes RAW workflow for the GH6?

Yes, and unlike the S5 II, the GH6 unlocks both RAW paths through free firmware updates rather than a paid upgrade key, though you still need an external recorder either way.

Firmware version 2.0, covered by CineD's report on the update, added the ability to output 4K/120p RAW over HDMI to an Atomos Ninja V or Ninja V+, recorded as Apple ProRes RAW. Firmware version 2.3, per Newsshooter's coverage, added a second RAW path entirely: 12-bit Blackmagic RAW output over HDMI to a Blackmagic Video Assist 5-inch or 7-inch 12G HDR recorder, at resolutions up to 5.7K, including anamorphic capture modes. That same firmware added 4K/120p and 100p HDMI output more broadly, independent of the RAW workflow.

DaVinci Resolve decodes both resulting formats natively once you have the files. Blackmagic RAW decodes with no plugin required on any platform, since it's Blackmagic's own format. ProRes RAW decodes natively on Mac; Windows support depends on your specific setup and is worth confirming before committing a shoot to that path on a PC. Either format opens through Resolve's Camera RAW panel rather than a standard Color Space Transform node, giving you post-capture control over white balance, ISO, and exposure that a baked-in V-Log MOV file doesn't offer.

The practical tradeoff is external hardware, not licensing cost the way it is on the S5 II. The GH6's internal V-Log recording already gives most projects enough dynamic range and color latitude for a standard delivery. RAW over HDMI adds real value when you're pushing toward a heavier VFX pipeline or need post-capture ISO and white balance flexibility beyond what Log offers, but it means carrying an Atomos or Blackmagic recorder on set, plus the extra cabling, battery, and monitor real estate that comes with it.

Both RAW paths on the GH6 are free firmware unlocks rather than paid upgrades, unlike the S5 II's paid Software Upgrade Key, but you still need an external recorder either way to actually capture the signal. Check whether your delivery spec genuinely needs RAW-level latitude before adding a recorder to your kit for a shoot that would have looked fine straight off the internal V-Log codec.

Is the Panasonic GH6 still worth buying now that the GH7 exists?

Yes for a lot of hybrid shooters, but know what you're giving up first, since Panasonic no longer sells the GH6 new.

Panasonic launched the GH6 in February 2022 at $2,199 body-only, per PetaPixel's coverage of the announcement, built around a 25.2-megapixel Four Thirds sensor with no low-pass filter, active internal cooling for unlimited recording, and 7.5 stops of 5-axis Dual I.S. 2 stabilization. The GH6 was discontinued in Japan in June 2024, reported by 4K Shooters ahead of the announcement, and Panasonic released the GH7 that summer as its direct successor, sold today at retailers like B&H explicitly as the "Replacement for Panasonic GH6."

The GH7 brings real upgrades the GH6 never got, even on its final firmware: a hybrid phase-detect and contrast-detect autofocus system, replacing the GH6's contrast-only implementation, internal ProRes RAW recording with no external recorder required, Open Gate shooting, 4K/120p, and 32-bit float audio recording. None of that changes how a GH6 clip you already own, or one you buy secondhand, behaves in DaVinci Resolve.

Every Color Space Transform setting, every Dynamic Range Boost consideration, and the LUT mismatch covered earlier in this guide apply to GH6 footage exactly the same way whether the camera is Panasonic's current flagship or a two-generation-old body on the used market. If your budget points you toward a secondhand GH6 rather than a new GH7, you're giving up autofocus performance, internal ProRes RAW, and a couple of newer conveniences, not color accuracy in Resolve.

A GH6 you already own, or one you buy used, doesn't lose a single Color Space Transform setting in this guide just because Panasonic replaced it with the GH7. The autofocus and internal RAW gap between the two cameras is real, but it's a shooting-day tradeoff, not a reason to distrust the color workflow you've already built around GH6 footage.

Can you intercut GH6 footage with other Panasonic V-Log cameras?

If your kit mixes a GH6 with an S5 II, S1H, or older GH5, this decides whether you're running one Color Space Transform setup or several.

Panasonic has stated directly that GH6 footage shares its color science with the rest of the V-Log lineup. Per Newsshooter's coverage of the GH6's launch, "according to Panasonic, the GH6's recorded footage is compatible with V-Log footage recorded by VariCam or other cameras such as the GH5/GH5S/GH5 II, S5, S1H, and S1." A separate technical breakdown of the camera makes the same point from the color science side, noting that "the LUMIX GH6 offers the renowned colorimetry of the VariCam line of cinema cameras and uses their V-LOG picture profile and wider V-Gamut." RedShark News's Simon Wyndham summed up the GH6's position in the lineup bluntly: "it is effectively an S1H with an MFT sensor. It is, as a result, a much smaller and lighter camera than the S1H, but in video terms, it is no less capable," he wrote in his review.

Our sibling guide to Panasonic S5 II V-Log import settings in DaVinci Resolve covers the same Color Space Transform preset from the full-frame side of the lineup. The math is identical: Panasonic V-Gamut in, Panasonic V-Log gamma, DaVinci Wide Gamut and DaVinci Intermediate as the intermediate stop. What differs between the two cameras isn't the preset, it's the sensor underneath it. A Four Thirds GH6 sensor and a full-frame S5 II sensor differ in noise floor, in how much dynamic range each one actually delivers before and after Dynamic Range Boost or Dual Native ISO, and in the curve mismatch issue covered earlier that's specific to the GH6. Treat the shared preset as your correct starting point on every clip, then still cross-check skin tones and neutral grays on your scopes once footage from two different bodies sits in the same scene, the same normalization step covered in our guide to color matching different cameras.

Panasonic's own claim is that V-Log footage from a GH6, an S5 II, an S1H, and even its VariCam cinema line all start from the same Color Space Transform preset, and RedShark News called the GH6 an S1H with a smaller sensor. That's a genuine head start on a mixed Panasonic shoot, but a starting point for matching, not a guarantee that skips the matching step, especially once the GH6's own curve mismatch enters the picture.

Do you need DaVinci Resolve Studio for any of this?

Not for the core V-Log color workflow. The Panasonic V-Gamut/V-Log Color Space Transform preset, Resolve Color Management's tagging once it's correctly applied, and native Blackmagic RAW decoding all work in the free version, with no functional restriction on the color math itself.

Studio genuinely enters the picture in three places. First, reliably decoding some of the GH6's 10-bit files, particularly the C4K/4K 4:2:2 mode and the high-bitrate ProRes files, since Blackmagic's free version page caps its stated support at "virtually all 8-bit video formats," per the free product page. Second, 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, relevant if you're delivering the GH6's HLG footage as true HDR rather than a Rec.709 conversion. Third, noise reduction, which matters more on Dynamic Range Boost footage shot at its ISO 2000 floor than on a lower-ISO clip, since Resolve's Temporal and AI Spatial noise reduction tools are Studio-only.

Getting GH6 V-Log 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 Studio just to make your V-Log footage look right, unless you've 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 GH6 V-Log clip from flat to Rec.709

Here's the full sequence in order, from a fresh GH6 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. Right-click the clip, check Clip Attributes, confirm it's V-Log, note which of the three recording paths captured it (internal ProRes 5.7K, C4K/4K H.265, or open gate H.265), and check whether Dynamic Range Boost was on (ISO 2000 floor) or off (ISO 250 base).
2. Build optimized media if the clip is stuttering on scrub. If it's a large 5.7K H.265 or high-bitrate ProRes file playing back roughly, generate optimized media at Quarter or Eighth Resolution before you touch color.
3. Node 1, Color Space Transform in. Set Input Color Space to Panasonic V-Gamut, Input Gamma to Panasonic V-Log, Output Color Space to DaVinci Wide Gamut, Output Gamma to DaVinci Intermediate.
4. Check Tone Mapping and Gamut Mapping if highlights look harsh. Try DaVinci or Luminance Mapping and Saturation Compression, especially on a Dynamic Range Boost clip pushed toward the top of its exposure range.
5. Node 2, Noise Reduction, if the shot needs it. If the clip was shot at ISO 2000 with Dynamic Range Boost and shows visible grain once it's out of Log, add a Temporal or Spatial Noise Reduction node here, right after the Color Space Transform, before any contrast or saturation moves.
6. Node 3, primary correction. With the clip sitting in DaVinci Wide Gamut, set your white balance using an eyedropper on a neutral reference if you have one, correcting for the magenta push V-Log carries before conversion, then bring your black point and white point in toward the edges of your waveform, watching for clipping on the scopes.
7. 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 GH6 footage behaves like footage from any other camera.
8. 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.
9. Check the result against the troubleshooting table below before calling the grade final, particularly if a third-party LUT was involved anywhere in your workflow, or if this clip is intercut with footage from a different camera or a different GH6 recording path.

Five nodes handle the entire mechanism from flat V-Log source to finished Rec.709 delivery, with Noise Reduction as the one optional insertion depending on how the clip was shot. A common mistake worth naming directly: adding a third-party LUT "just to compare" against the Color Space Transform, then forgetting to remove one of the two. Given the curve mismatch covered earlier in this guide, that stacking error is more likely to produce a visibly wrong result on GH6 footage than on footage from a Panasonic camera whose curve tracks the reference LUT more closely.

Why does V-Log 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 wrong preset. Confirm you picked Panasonic V-Gamut specifically for Input Color Space and Panasonic V-Log specifically for Input Gamma, not a visually adjacent option from a different brand's menu section.

Second, 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 third-party 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 transforming the same clip. Given the LUT mismatch covered earlier, a GH6 clip run through both a third-party LUT and a Color Space Transform is especially prone to producing a visibly wrong result, since neither one alone perfectly matches the camera's actual curve, and stacking them compounds the error rather than canceling it out.

Third, confirm the clip is actually V-Log. The GH6 offers HLG and standard profiles alongside V-Log, and a clip shot in one of those can look flat enough to mistake for Log footage, especially deep into a long shoot day. Applying a V-Log Color Space Transform to an HLG or standard clip produces a specific kind of wrong, washed-out and low-contrast or oddly clipped depending on the source profile, that looks like an incomplete conversion because it is one, applied to the wrong input.

Fourth, the Dynamic Range Boost variable. A clip shot with Dynamic Range Boost on at ISO 2000 and one shot with it off at ISO 250 both tag as Panasonic V-Log, but they carry different noise floors and slightly different highlight rolloff. If two GH6 clips from the same scene look subtly different after an identical Color Space Transform, check whether Dynamic Range Boost was consistent across both before assuming the grade itself needs adjusting.

Fifth, timeline color space mismatch. If your project's overall Color Management is set to a working space your output node doesn't 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.

Sixth, 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 relinked to full-resolution media before export.

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

Everything in this reference is a settings problem with a settings answer, but finding the right menu on a deadline is its own kind of friction, especially when you're bouncing between Project Settings, the node graph, and Clip Attributes trying to confirm exactly what a GH6 clip is, and whether Dynamic Range Boost was on, before you touch its color.

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 is my GH6 footage still 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 it's 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, the TryUncle app is the more direct tool for that specific job. Guided help inside Resolve beats pausing a tutorial shot on a different camera's menu to compare against your own.

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

Before the table, here's the one-line version of everything above. Use Resolve Color Management if your project is entirely GH6 footage shot the same way, but verify the tag actually applied. Switch to a manual Color Space Transform node the moment you're mixing camera brands, and prefer it over a static LUT on this camera specifically, since the GH6's actual V-Log curve doesn't map perfectly onto the reference curve behind the official Panasonic LUT. Shoot with Dynamic Range Boost on at its ISO 2000 floor when you need real highlight latitude, and remember that's a different mechanism than the Dual Native ISO on the S5 II or S1H, not just a different number. Consider a RAW-over-HDMI path only if your delivery genuinely needs it, since either option needs an external recorder even though the firmware unlock itself is free. And if a clip won't come online at all, that's a decode problem tied to bit depth and chroma, not a color space problem.

Match Panasonic V-Gamut and Panasonic V-Log to your first node, shoot at ISO 2000 with Dynamic Range Boost on when you need the dynamic range V-Log promises, grade against your scopes rather than trusting a static LUT given the GH6's own curve mismatch, and confirm the clip actually decoded before you blame the color. Most GH6 footage that looks wrong in Resolve isn't broken. It's one preset, one missing LUT the camera was never going to ship with, or one exposure setting away from correct, and now you know which one to check first.