Panasonic GH7 V-Log Import Settings for DaVinci Resolve

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, whether Resolve is actually tagging your clips correctly on ingest, and whether any clips in the mix used the ARRI LogC3 upgrade instead of standard V-Log.

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 GH7 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 GH7 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 GH7 footage against a different camera, or against a handful of GH7 clips shot with the ARRI LogC3 upgrade instead of standard V-Log. 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, GH7 included.

What is Dynamic Range Boost on the GH7, and how is it different from the GH6's version?

Dynamic Range Boost isn't new to the GH7, but where you're allowed to turn it on changed, and that change is the single biggest practical upgrade for anyone coming from a GH6 workflow.

The underlying mechanism is the same one Panasonic has used since the GH6. Per Panasonic's own GH7 product page, "Dynamic Range Boost function acquires two types of images with a single exposure and synthesizes them in real time to create composite images with rich tonal range." Newsshooter's coverage of the GH7's announcement describes that blend more specifically: "One circuit using ISO 800 absorbs the richness of the visible spectrum while maintaining detail in the highlights, and ISO 2000 captures low-noise gradients of black in the shadows." Two internal gain reads from the same exposure, blended into one frame, rather than a dual native ISO sensor switching between two selectable, discrete sensitivities.

Where the GH7 pulls ahead of the GH6 is availability. The GH6 could only engage Dynamic Range Boost once you'd pushed V-Log's ISO up to a floor of 2000, dropping to a base of 250 with the feature off. The GH7 expands that. Panasonic's own operating instructions list V-Log's standard base ISO at 500 for sensor output at 60fps or lower, dropping to 250 at 61fps or higher, and multiple reviews confirm Dynamic Range Boost is now available across that full range, including right at the 500 base ISO, up to 60fps. You no longer have to accept a forced jump to ISO 2000 just to get the extra stop of highlight and shadow latitude the feature buys you.

Dynamic Range Boost on the GH7 works at the camera's actual base ISO instead of forcing you up to a fixed floor, and that alone removes the noise-versus-dynamic-range tradeoff that defined the same feature on the GH6. If you learned to treat Dynamic Range Boost as a "only above ISO 2000" feature from a GH6 project, that habit costs you nothing but latitude on a GH7; you can leave it on by default at base ISO and only think about it again when you push into a dim interior.

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

Panasonic's marketing figure and an independent lab's measured figure rarely land on the exact same number for any camera, and the GH7 is no exception, though the measured result still holds up well for a Four Thirds sensor.

Panasonic quotes 12+ stops of dynamic range for V-Log with Dynamic Range Boost off, rising to 13+ stops with it engaged, a figure printed directly on the GH7's product page as "13+ stop dynamic range boost for vibrant, detailed photo/video." CineD's own lab test of the camera measured that claim with IMATEST analysis. For 5.7K ProRes HQ V-Log at ISO 500, the lab found 11.3 stops at SNR 2 and 12.6 stops at SNR 1, a genuinely strong result at the camera's base ISO. Rolling shutter came in at 13.2ms for 5.7K and 4K DCI modes, rising to 20.8ms for the full 5.8K open gate 4:3 sensor readout, a figure CineD described as "very similar to the predecessor, the LUMIX GH6, as well as the LUMIX G9 II."

One counterintuitive finding is worth flagging before you assume RAW automatically measures better than V-Log on this camera. CineD's same test measured 5.7K ProRes RAW HQ at ISO 500 slightly lower than V-Log at the same ISO, 9.85 stops at SNR 2 and 11.6 stops at SNR 1, with a faint 12th and 13th stop visible in the noise floor. The gap traces back to processing, not to the RAW format capturing less information. V-Log applies in-camera noise reduction before it's written to the file, smoothing high-frequency detail in a way that tests as slightly more dynamic range on paper. CineD noted that with ProRes RAW, "the amplitudes never drop below 0.5 even at the highest frequencies," meaning the RAW file preserves more actual sensor noise and fine detail rather than baking in a smoothing pass, which is exactly what most colorists shooting RAW actually want, even if the raw lab number reads a touch lower.

An independent lab measured the GH7's V-Log dynamic range at its new base ISO of 500 as genuinely competitive for a Micro Four Thirds sensor, and the fact that ProRes RAW measured slightly lower than V-Log in the same test says more about in-camera noise reduction than about which format actually holds more real information. Don't chase the higher number on a spec sheet or a lab chart alone; RAW's advantage on the GH7 is post-capture control, not a guaranteed dynamic range win over V-Log at the same ISO.

Should you shoot V-Log or ARRI LogC3 on the GH7?

This is a decision the GH6 and S5 II never asked their shooters to make, and it's the clearest way the GH7 stands apart from the rest of Panasonic's V-Log lineup in a DaVinci Resolve workflow.

Panasonic licensed ARRI's LogC3 curve for the GH7 through a paid Software Upgrade Key, DMW-SFU3A, priced at $200. Per No Film School's coverage of the unlock, the same key also works on the GH6, though without the GH7's added Real Time LUT function. With this upgrade you can utilize ARRI's LogC3, which Panasonic states enables you to seamlessly color match the GH7 with ARRI's digital cinema cameras. The image processing behind the curve has been certified by ARRI, not just licensed as a name.

ARRI LogC3 comes with real limits worth knowing before you buy the key. It's restricted to ProRes 422, ProRes 422 HQ, and ALL-Intra codecs only, so it's not available if you're shooting internal ProRes RAW. Its base ISO sits at 320, lower than V-Log's 500, which changes your exposure math on set. And it opens through a completely different Color Space Transform preset in Resolve than the one covered earlier in this guide. Instead of Panasonic V-Gamut and Panasonic V-Log, colorists working with ARRI Log-C footage set Input Color Space to ARRI Wide Gamut 3 and Input Gamma to ARRI LogC3, with Output Color Space and Output Gamma landing on DaVinci Wide Gamut and DaVinci Intermediate exactly the same as the V-Log workflow. It's the identical intermediate destination, just a different door to reach it.

The GH7's Real Time LUT function makes the case for LogC3 stronger than it would be on a spec sheet alone. Per Newsshooter's reporting, "it is also possible to store the LUT package for 709 conversion, ARRI Look Library LogC3 to Rec709 3D-LUTs, in the LUT Library of the LUMIX GH7, and combine it with the Real Time LUT function to capture videos with ARRI LUTs straight out of the camera," giving you access to 87 ARRI Look Library LUTs baked in on set if you want them, a feature the GH6's LogC3 upgrade doesn't include.

V-Log works with every recording mode the GH7 offers including its internal RAW path, and ARRI LogC3 buys you a certified color match to real ARRI cinema cameras at the cost of $200 and a narrower set of compatible codecs. Reach for LogC3 specifically when your delivery needs to intercut with genuine Alexa footage; for a GH7-only project, standard V-Log and the Panasonic V-Gamut/V-Log preset remain the simpler, more flexible default.

Does the GH7 ship with a V-Log to Rec.709 LUT, or a real-time one?

No first-party conversion LUT ships preloaded, the same gap the GH6 and S5 II both leave for you to fill, but the GH7 adds a genuinely new tool for handling that gap on set.

Like its predecessors, the GH7 includes V-Log View Assist, which lets you load LUT data to preview a graded look on the rear screen or over HDMI while you're still shooting flat. That feature now supports both .CUBE and .VLT LUT formats for real-time preview, more flexible than the GH6's format support, but it's still a monitoring tool. You supply the LUT yourself, and the camera arrives with nothing loaded into it.

What's genuinely new is the Real Time LUT function, which goes a step further than View Assist by baking a loaded LUT directly into your recorded file rather than only showing it on a monitor. That's the feature Newsshooter's coverage highlights as GH7-exclusive when paired with the ARRI LogC3 upgrade, letting you record with an ARRI Look Library LUT applied straight out of the camera instead of grading it in afterward. It works with any LUT you load, not only ARRI ones, so it's just as usable if you've built your own V-Log to Rec.709 look in DaVinci Resolve and want to commit to it on set for a fast-turnaround job.

Panasonic's public LUT library, the VARICAM LUT LIBRARY, remains the same resource it's always been, offering 35 conversion and creative LUTs including a genuine V-Log to Rec.709 conversion. That page states the library is built "to VariCam cinema cameras and the AU-EVA1," Panasonic's cinema and compact cinema line, not the GH7's hybrid Four Thirds sensor, so treat any LUT pulled from it as a starting point to check against your own footage rather than a guaranteed match. Our guide to installing LUTs in DaVinci Resolve covers the mechanics of loading a .cube file into Resolve's LUT folder if you want to build or test one before committing a project to it.

The GH7 still ships no first-party V-Log to Rec.709 LUT, but its Real Time LUT function is the first time this camera line lets you commit a graded look, including ARRI's own Look Library, straight into the recorded file rather than only previewing it. A manual Color Space Transform using the Panasonic V-Gamut/V-Log preset covered earlier remains the more reliable default in post, since it doesn't depend on any external file, but Real Time LUT is worth knowing about for delivery timelines that don't leave room for a full grading pass.

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

If a GH7 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 GH7's V-Log recording paths, ProRes RAW, ProRes, and both H.265 modes alike, is 10-bit or higher. In practice, plenty of 10-bit 4:2:0 H.265 footage decodes fine in the free version. The GH7's 4:2:2 H.265 C4K/4K mode and its higher-bitrate ProRes and ProRes RAW files are the ones more likely to actually hit the wall, the same pattern documented across other 10-bit-and-up mirrorless bodies.

Windows adds a second, separate wrinkle for the GH7'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 and ProRes RAW decode natively on Mac with no extra install; on Windows, ProRes and ProRes RAW decode support depends on your specific setup and is worth confirming before you build a GH7-heavy 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 or RAW 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 GH7 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.8K open gate or internal ProRes RAW editing?

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

The internal ProRes RAW and ProRes 422 HQ files are large by codec design, since both trade file size for editing-friendly intraframe compression, and a 5.7K ProRes RAW file adds up fast on a laptop SSD, whether it's writing to a CFexpress card or an external USB-C SSD. The H.265 modes, including the 5.8K open gate path, 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. All of these 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 and 5.8K 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.8K 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 GH7 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 or ARRI Wide Gamut 3/ARRI LogC3 tagging applies exactly the same way it would without proxies in the pipeline.

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

Yes, and it's the one area where the GH7 offers three separate RAW paths instead of just the two the GH6 has, since internal ProRes RAW now sits alongside two external HDMI-out options.

The internal path is the simplest: ProRes RAW or ProRes RAW HQ, recorded straight to a CFexpress Type B card or a USB-C SSD, no external recorder required. That alone is the headline upgrade over the GH6, which needed an Atomos Ninja V and a firmware unlock just to output ProRes RAW over HDMI at all.

The GH7 also keeps both of the GH6's external RAW paths available. Per the Panasonic operating instructions on RAW video data output, the camera can send 12-bit RAW over HDMI to a compatible external recorder, saved as ProRes RAW on an Atomos Ninja V, Ninja V+, or similar recorder. Separately, CineD's coverage of Blackmagic's Video Assist 3.15 firmware update confirms the GH7 gained Blackmagic RAW recording support, at resolutions up to 5.8K, on the Blackmagic Video Assist 5-inch and 7-inch 12G HDR recorders specifically.

DaVinci Resolve decodes all three 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, whether recorded internally or captured externally, 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. All three open 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 GH7 is the first camera in this lineup where ProRes RAW needs no external hardware at all, a genuine step past the GH6 and S5 II, both of which still require an Atomos or Blackmagic recorder just to reach any RAW format. That doesn't make internal V-Log obsolete; it already gives most projects enough dynamic range and color latitude for a standard delivery. Reach for internal ProRes RAW when a project specifically needs post-capture white balance and ISO flexibility, and save the external HDMI paths for the rare case where you're already carrying an Atomos or Blackmagic recorder for another camera on the same shoot.

How does the GH7 compare to the GH6 for a DaVinci Resolve workflow?

If you're deciding between a used GH6 and a new GH7, or wondering whether upgrading changes anything about the color pipeline you already know, the short version is: the Color Space Transform math stays identical, and almost everything around it improves.

Panasonic discontinued the GH6 in Japan in June 2024, reported by 4K Shooters ahead of the announcement, the same month the GH7 launched as its direct successor. The GH7 brought 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, a Dynamic Range Boost mode usable at base ISO instead of forced up to ISO 2000, a Real Time LUT function, and the optional ARRI LogC3 color science upgrade covered earlier in this guide. Cameralabs' review of the camera by Gordon Laing called it a camera that "builds upon a strong series to become one of the most compelling cameras for videographers and hybrid shooters at this price point," awarding it a Highly Recommended verdict.

None of that changes how a GH6 clip you already own, or one you buy secondhand, behaves in Resolve. Every Color Space Transform setting covered in this guide applies to GH6 footage exactly the same way it applies to GH7 footage, since both cameras share the identical Panasonic V-Gamut and V-Log color science. If your budget points you toward a secondhand GH6 rather than a new GH7, you're giving up autofocus performance, internal RAW convenience, the wider Dynamic Range Boost range, and the LogC3 option, not color accuracy in Resolve. Our sibling guide to Panasonic GH6 V-Log import settings covers the GH6 side of that same preset in full detail.

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, internal RAW, and Dynamic Range Boost gap between the two cameras is real, and it's meaningful on a demanding shoot day, but it's not a reason to distrust the color workflow you've already built around GH6 footage.

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

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

Panasonic has long stated that its V-Log implementation shares color science across the GH, S1, and S5 lines, tracing back to the VariCam cinema camera family. Covering the GH6's launch, Newsshooter reported that "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 GH6 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." The GH7 continues on that same sensor family and color pipeline, sharing its V-Gamut and V-Log math with every camera in that list.

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 GH7 and an S5 II or S1H isn't the preset, it's the sensor underneath it. A Four Thirds GH7 sensor and a full-frame S5 II sensor differ in noise floor, in how much dynamic range each one actually delivers before and after their respective Dynamic Range Boost or Dual Native ISO implementations, and in generation-to-generation tuning even within the same sensor format. 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 GH7, a GH6, an S5 II, and even its VariCam cinema line all start from the same Color Space Transform preset. That's a genuine head start on a mixed Panasonic shoot, but it's a starting point for matching, not a guarantee that skips the matching step, especially the moment a GH7's Four Thirds sensor sits next to an S5 II's full-frame one in the same scene.

Do you need DaVinci Resolve Studio for any of this?

Not for the core V-Log or ARRI LogC3 color workflow. The Panasonic V-Gamut/V-Log Color Space Transform preset, the ARRI Wide Gamut 3/ARRI LogC3 preset, Resolve Color Management's tagging once it's correctly applied, and native Blackmagic RAW and ProRes 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 GH7's 10-bit files, particularly the 4:2:2 H.265 C4K/4K mode and the high-bitrate ProRes and ProRes RAW 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 HLG footage from the GH7 as true HDR rather than a Rec.709 conversion. Third, noise reduction, which matters more on Dynamic Range Boost footage shot toward the upper end of the ISO range than on a lower-ISO clip, since Resolve's Temporal and AI Spatial noise reduction tools are Studio-only.

Getting GH7 V-Log or ARRI LogC3 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 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 GH7 V-Log clip from flat to Rec.709

Here's the full sequence in order, from a fresh GH7 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 and not ARRI LogC3, note which recording path captured it (internal ProRes RAW, ProRes, C4K/4K H.265, 5.7K H.265, or 5.8K open gate H.265), and check whether Dynamic Range Boost was engaged and at what ISO.
2. Build optimized media if the clip is stuttering on scrub. If it's a large 5.8K H.265 file or a high-bitrate ProRes RAW 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. If the clip was shot with the ARRI LogC3 upgrade instead, use ARRI Wide Gamut 3 and ARRI LogC3 here instead.
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 a higher ISO 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 in frame if you have one, then bring your black point and white point in toward the edges of your waveform with the Lift and Gain wheels, watching for clipping on the scopes rather than trusting your eyes alone.
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.
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.

Five to six nodes handle the entire mechanism from a flat source to a 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 or fourth Color Space Transform "just to compare" a LUT against the manual conversion, then forgetting to remove one of them. Two conversions per clip, one in and one out, is correct. Three is almost always leftover from experimenting, and it's the fastest way into the log-on-log problem covered next.

Why does GH7 V-Log footage still look wrong after 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 entirely. The GH7 is the one camera in this lineup where you might genuinely have two valid presets to choose between, Panasonic V-Gamut/V-Log for standard footage and ARRI Wide Gamut 3/ARRI LogC3 for clips shot with the paid upgrade. Applying the V-Log preset to a LogC3 clip, or the reverse, produces color that's close enough to look plausible at a glance and wrong enough to fight you on every grading move. Check Clip Attributes to confirm which curve actually captured the shot before you pick a preset.

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, or the GH7's Real Time LUT bake-in, is stacked on top of a Color Space Transform doing the same conversion. Since the GH7 ships no first-party static LUT, editors reaching for a third-party pack, or one baked in on set with Real Time LUT, sometimes forget a manual Color Space Transform is also converting the same clip, doubling the conversion.

Third, check that the clip is actually V-Log or LogC3 to begin with. The GH7 offers other Photo Style profiles beyond its two Log options, and a clip shot in a standard profile can look a little flat and get mistaken for Log footage on a long shoot day. Applying a Log Color Space Transform to non-Log footage produces washed-out, low-contrast color that looks like an incomplete conversion because, in a sense, it is one, applied to the wrong input.

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 finding the right menu on a deadline is its own kind of friction, especially now that the GH7 gives you two Log curves and two Color Space Transform presets to keep straight instead of one.

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 out loud "which Color Space Transform preset does my LogC3 clip need" instead of scrolling back up through this page mid-session, that's a faster route to the right dropdown. 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, on-screen guidance is the more direct tool for that specific job. Guided help inside Resolve beats pausing a tutorial video 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 GH7 footage shot the same way, but verify the tag actually applied since it doesn't always set itself automatically. Switch to a manual Color Space Transform node the moment you're mixing camera brands, mixing V-Log with ARRI LogC3 clips from the same GH7, or if RCM isn't tagging your clips correctly. Reach for internal ProRes RAW when a project needs post-capture flexibility and you don't want to carry an external recorder. Consider the ARRI LogC3 upgrade only if you're actually intercutting with real ARRI cinema camera footage, since it costs $200 and narrows your codec options. 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, and belongs in the import-failure section above, not in your node tree.

Match Panasonic V-Gamut and Panasonic V-Log to your first node, or ARRI Wide Gamut 3 and ARRI LogC3 if that's the curve you actually shot, keep an eye on which recording path captured each clip, and the rest of this workflow is two Color Space Transform nodes doing exactly what they're built to do. Most GH7 footage that "looks wrong" in Resolve isn't broken. It's one preset, one Log curve mixed up with the other, or one codec extension away from correct, and now you know which one.