Panasonic S1H V-Log Settings for DaVinci Resolve

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

Both reach the same finished image. Which one fits your project depends on how consistently your S1H footage was shot and whether Resolve is actually tagging it 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 S1H 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 an S1H 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 S1H footage against a different camera, or mixing V-Log clips with the same camera's own HLG or anamorphic footage 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.

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

No conversion LUT for post-production grading ships preloaded, and this is the gap that trips up more S1H shooters than the Color Space Transform math itself, since the camera does carry something that looks like a LUT solution at first glance.

The S1H includes V-Log View Assist, a feature that lets you preview a graded look on the rear monitor or over HDMI while you're still recording flat. Per the camera's own operating instructions, the feature "means you can show images with LUT data applied on the monitor/viewfinder and output them via HDMI," and it ships with a built-in preset the manual calls Vlog_709, plus room to register up to four of your own custom LUT files on top of it. That's more than the GH6 and S5 II offer out of the box, since both of those cameras ship with nothing loaded until you supply your own file.

What that built-in preset doesn't give you is a file you can pull into Resolve. Vlog_709 lives inside the camera's monitoring pipeline, applied only to what you see on the screen or send over HDMI, not baked into the recorded file and not exportable as a .cube you can drop into a Color Space Transform node. Confirm a clip's Photo Style through Clip Attributes before you assume that flat gray image is somehow already carrying a conversion; it isn't.

Panasonic does offer a genuine downloadable .cube file for the S1H, but it solves a different problem entirely. The file, named VLog_RAWGamut_to_VLog_VGamut_forS1H_ver100.cube on Panasonic's own support site, converts RAW output gamma back into standard V-Log/V-Gamut, useful if you're working with the camera's RAW HDMI output covered later in this guide, and it's compatible across a long list of Panasonic bodies despite the filename, not something built exclusively for the S1H. It is not a V-Log to Rec.709 conversion LUT, and using it in place of one produces footage that's still flat and still needs the Color Space Transform covered above.

Panasonic's public VARICAM LUT LIBRARY offers 35 conversion and creative LUTs, including a genuine V-Log to Rec.709 conversion, but 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 S-series hybrid mirrorless bodies. Treat any LUT pulled from that library as a starting point to check against your own footage, not a guaranteed match.

The S1H is the rare Panasonic body with a built-in monitoring LUT preset, Vlog_709, and it still ships with no file you can actually apply to a clip in post. A manual Color Space Transform using the Panasonic V-Gamut/V-Log preset covered earlier sidesteps the entire gap, since it depends on no external file at all, and it's the more reliable default unless you've specifically vetted a third-party S1H LUT against your own footage first.

What ISO should you shoot V-Log at?

The Color Space Transform math assumes you exposed the footage the way V-Log's curve was designed for, and the S1H's sensor gives you exactly two ISOs that setup was actually built around.

CineD's own lab test of the camera confirms the S1H uses a dual native ISO sensor for V-Log/V-Gamut, with native points at ISO 640 and ISO 4000, maxing out at ISO 51,200 in that mode. The lab's IMATEST results found dynamic range at SNR=2 measured 12.7 stops at ISO 640 in 6K and 5.9K modes, dropping only slightly to 12.3 stops at ISO 4000 in the same modes. In 4K DCI, the gap was even smaller: 12.3 stops at ISO 640 against 12.2 stops at ISO 4000, described in the test as "almost no difference between ISO640 and ISO4000 in 4K DCI mode, only 0.1 stops of dynamic range are lost."

That's a genuinely unusual result. CineD's writeup called the S1H the first camera in its testing to show nearly identical dynamic range across both settings of a dual-gain sensor, meaning you can push up to the higher native ISO in dim conditions without the usual dynamic range penalty other dual-ISO cameras carry. The lab rated the S1H's 12.7-stop result at ISO 640 as "the second-best result that we have ever measured, right after the ARRI Alexa (14 stops at SNR=2)," a genuinely notable benchmark for a camera in this price bracket at launch.

Panasonic's own marketing claims 14+ stops of dynamic range for V-Log, a figure CineD's stricter SNR=2 measurement doesn't quite match at 12.7 stops, though the gap narrows at the more permissive SNR=1 threshold, where the lab's result climbed to 13.8 stops, close to Panasonic's number. That gap between a vendor's marketing figure and an independent lab's measured figure is normal across the camera industry, not a defect specific to Panasonic. Matthew Allard's Newsshooter review reached the same practical conclusion from a different angle, writing bluntly: "The overall dynamic range of the S1H is good and if you can't work with the DR the camera has you are doing something very wrong."

V-Log's dynamic range on the S1H is real and well-tested, and the number on the spec sheet and the number an independent lab actually measures rarely match exactly, though this camera's dual native ISOs come unusually close to each other in practice. Expose at or near ISO 640 or ISO 4000, watch your scopes rather than the spec sheet, and you'll get the dynamic range the sensor can actually deliver regardless of which figure you read going in.

Should you shoot V-Log, HLG, or Cinelike D2/V2 on the S1H?

V-Log isn't the only gamma curve on the S1H built around dynamic range, and each option carries its own dual native ISO pair and its own Color Space Transform decision, so it's worth knowing what you're choosing before you commit a shoot to one.

Per CineD's specs breakdown, the S1H's standard Photo Style profiles use dual native ISOs of 100 and 640, maxing out at ISO 204,800. Switch to V-Log and the native points shift to 640 and 4000, capped at ISO 51,200. Switch again to HLG for an HDR-native workflow and the native points shift once more, to ISO 400 and 2500, still topping out at ISO 204,800 since HLG isn't as aggressively flat a curve as V-Log. Three genuinely different exposure targets depending on which gamma curve you picked before rolling, and mixing them up on set means every clip in that scene was exposed for the wrong ISO pair.

Cinelike D2 and Cinelike V2, the same contrast-priority and dynamic-range-priority profiles Panasonic carries across its whole S and G lineup, don't need a Color Space Transform at all. Both are built to look close to a finished Rec.709 image straight off the sensor, and most editors treat them as a normal delivery-ready source with a light grade layered on top. V-Log needs the full Panasonic V-Gamut/V-Log transform covered earlier before it looks like anything at all, and HLG needs a different transform entirely, since it's designed for HDR delivery rather than an SDR intermediate.

Cinelike D2 and V2 are built to look finished with no Color Space Transform at all, HLG is built for HDR delivery with its own native ISO pair, and V-Log is built to look flat until you apply the transform covered throughout this guide. If you've been defaulting to V-Log out of habit on a project that's actually headed for an HDR master, HLG may be the more direct path, and if the project never gets graded at all, the Cinelike profiles save you a step without costing you footage quality.

Does the S1H need a paid upgrade key for V-Log, the way the base S1 does?

No, and this is a genuine differentiator worth knowing if you're weighing a used S1 with the paid Log upgrade against a used S1H for the same budget.

Panasonic's base S1 shipped without V-Log at all, requiring a separate Upgrade Software Key, DMW-SFU2, to unlock it, a paid add-on Panasonic later bundled free with new S1 purchases for a limited window. The S1H carries V-Log as a standard, built-in Photo Style with no key purchase required, alongside a wider set of video specs the upgraded S1 doesn't match. DPReview's own comparison of the two cameras found the upgraded S1 still can't capture DCI 4K the way the S1H can, and it's limited to Long GOP recording at up to roughly 150Mbps where the S1H reaches 400Mbps in All-Intra.

That gap matters for a Resolve workflow specifically because bitrate and compression scheme change how forgiving a file is to grade. All-Intra footage, where every frame is compressed independently, holds up better under heavy color correction and multiple passes than Long GOP footage, where frames depend on neighboring frames and can show compression artifacts sooner once you push saturation or contrast hard in a grade. An upgraded S1 clip and an S1H clip both tag as Panasonic V-Gamut and Panasonic V-Log identically in Resolve's Color Space Transform dropdown; the difference shows up in how much room you have to push the grade before the underlying compression starts to show.

The S1H includes V-Log standard with no paid key required, and its higher-bitrate All-Intra recording gives a colorist more room to work than an upgraded base S1's Long GOP files, even though both cameras use the identical Color Space Transform preset in Resolve. If you're choosing between the two on a budget, the color science costs you nothing either way; the codec and bitrate ceiling is where the real difference in grading flexibility lives.

Why was the S1H the first Netflix-approved mirrorless camera, and does it matter for your color workflow?

The S1H is, per Netflix's own camera approval process, the first mirrorless or DSLR-style camera certified for shooting Netflix Original 4K content, a fact that shapes how the camera gets marketed but not how you'd grade a single clip differently.

DPReview's coverage of the certification confirms Netflix added the S1H to its approved camera list alongside cameras like the ARRI Alexa LF, Canon C700, RED Weapon Dragon 8K, and Sony F55, camera systems that, at the time, cost many times the S1H's launch price. Matthew Allard's Newsshooter review put the achievement plainly: "The S1H is the first-ever mirrorless or DSLR camera to obtain Netflix approval." No Film School's coverage of the related BS1H box camera's approval noted the significance extends beyond one camera body, since it established that a mirrorless form factor could meet Netflix's technical bar for resolution, dynamic range, and codec robustness at all.

It's worth reading that achievement for what it actually measures. Netflix's approval process checks technical specifications: sensor resolution, codec robustness, dynamic range, and color science consistency, not whether a specific clip looks good once you've graded it. Allard's own review added the necessary caveat directly: "While the approval for the S1H is significant, I highly doubt many Netflix original productions are going to start using an S1H." The certification tells you the camera's raw signal meets a professional bar. It says nothing about your specific Color Space Transform settings, your exposure on set, or how well you've matched it to other cameras in your kit, all of which still determine whether your footage actually looks broadcast-ready once it's through your node tree.

Netflix's approval of the S1H is a real technical milestone for the mirrorless camera category, and it changes nothing about the Color Space Transform settings covered throughout this guide. A Netflix-approved sensor still needs the same Panasonic V-Gamut/V-Log conversion, the same correct ISO exposure, and the same careful grading any other camera's Log footage requires; the certification is a floor on the camera's technical capability, not a shortcut past the color work.

Does the anamorphic 4:3 mode change your Color Space Transform settings?

No, and it's worth separating this question from the resolution and lens question, since the two get confused constantly on set and in post.

The S1H's anamorphic mode, covered earlier in this guide, records a squeezed 3328x2496 4:3 image meant to be desqueezed with a Resize node or Camera RAW panel setting matching your anamorphic lens's specific ratio, 1.3x, 1.5x, or 1.8x depending on what glass you shot with. That squeeze and desqueeze step happens entirely in the resolution and geometry domain. It has nothing to do with color space, and a clip shot in anamorphic V-Log still tags as Panasonic V-Gamut and Panasonic V-Log in Clip Attributes exactly the same as a spherical 6K V-Log clip shot the same session.

The practical order of operations matters more than the settings themselves here. Desqueeze the image first, either by setting the correct anamorphic ratio in Camera RAW or Clip Attributes, or with a Resize effect early in your node tree, before you apply the Color Space Transform covered earlier in this guide. Some Resolve tools, particularly anything involving vignette correction, distortion, or scopes-based analysis, behave more predictably when they're reading a properly desqueezed image rather than a still-squeezed one, and it's simpler to build the habit of desqueeze first, color second, than to remember which specific tool cares about the difference on any given project.

Anamorphic footage on the S1H changes your resolution and geometry workflow, not your Color Space Transform settings. Treat the desqueeze as a separate step that happens before color, and the same Panasonic V-Gamut/V-Log preset covered throughout this guide applies whether the clip in front of you is spherical or squeezed.

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

Yes, though the S1H needs external hardware to reach either RAW format, since it has no internal RAW recording of its own, a limit worth planning around before a shoot day rather than discovering mid-production.

Matthew Allard's Newsshooter review documented Panasonic's plan directly at launch: "While there is no internal RAW recording in the S1H, Panasonic did confirm to Newsshooter that they are working with Atomos to deliver ProRes RAW via HDMI to an Atomos recorder." That partnership shipped as a firmware update, and per Newsshooter's hands-on coverage of the resulting workflow, the S1H can output 5.9K 12-bit RAW over HDMI to an Atomos Ninja V at up to 30p, alongside 4K Super35 and 3.5K Super35 anamorphic RAW options, all recorded and playable straight from the Ninja V. Getting there requires toggling HDMI RAW Data Output on in the camera's Video menu, then matching the Ninja V's input settings to Camera: Panasonic, Gamma: V-Log, Gamut: Panasonic RAW.

Blackmagic RAW followed later through a different piece of hardware entirely. Per EOSHD's coverage of the update, the S1H gained support for recording Blackmagic RAW directly on a Blackmagic Video Assist 12G HDR external monitor/recorder, at resolutions up to 5.9K, giving S1H shooters a second RAW path that decodes with zero plugin requirement in Resolve, since BRAW is Blackmagic's own native format.

DaVinci Resolve decodes both resulting formats natively once you have the files. Blackmagic RAW decodes with no plugin required on any platform. ProRes RAW decodes natively on Mac; Windows support for ProRes RAW depends on your specific setup and is worth confirming before you commit a shoot to that path on a PC edit bay. Either way, RAW footage from an S1H 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. If your RAW workflow used the RAW-to-V-Log conversion LUT covered earlier, apply that first, then follow it with the standard Panasonic V-Gamut/V-Log Color Space Transform, the same two-step chain the LUT was built for.

The S1H needs an external recorder for either RAW format, unlike its own newer siblings that added internal RAW years later, but it reaches two independently maintained RAW ecosystems, Atomos's ProRes RAW and Blackmagic's own format, through firmware rather than a paid upgrade key. For a standard delivery, the camera's internal V-Log recording already gives most projects enough dynamic range and color latitude; reach for RAW when a heavier VFX pipeline or post-capture exposure flexibility genuinely justifies carrying an external recorder.

Does DaVinci Resolve import S1H V-Log footage cleanly, or does it show Media Offline?

If a V-Log clip shows up as Media Offline, refuses to generate a thumbnail, or plays back as a stuttering mess, 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," per the free product page, and every one of the S1H's V-Log recording modes is 10-bit or higher. In practice, plenty of 10-bit 4:2:0 footage decodes fine in the free version. The camera's higher-bitrate 4:2:2 All-Intra 4K DCI files and its 6K/5.9K modes, which use H.265 (HEVC) compression, are more likely to actually hit the wall, the same pattern documented across other 10-bit-and-up mirrorless bodies from this era.

Windows adds a second, separate wrinkle specifically for the S1H's H.265 clips. Microsoft doesn't ship HEVC decoding natively with Windows, so even Resolve Studio needs the separate "HEVC Video Extensions" package from the Microsoft Store installed at the OS level before any H.265 file decodes at all. Filmmaking Elements' guide to fixing HEVC media offline errors walks through that install directly. Mac users skip this particular step, since macOS has included HEVC decoding at the operating system level since Sierra, though they can still hit the free-versus-Studio 10-bit wall regardless of platform.

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 demanding 10-bit 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.

An S1H 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 mode 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 6K or 5.9K V-Log editing?

Often yes, and the reason splits depending on which of the S1H's recording modes you shot and what machine you're editing on.

The S1H's 6K and 5.9K files are large by resolution alone, and their H.265 Long GOP compression leans on inter-frame prediction that's efficient for storage but expensive to decode in real time without hardware acceleration, especially on a laptop GPU with no dedicated HEVC decode block. The C4K/4K DCI 4:2:2 All-Intra mode is easier to decode frame by frame but carries its own cost from sheer bitrate at 400Mbps. Both situations respond to the same fix: build a lower-resolution stand-in before you start a heavy multi-clip edit.

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

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

Proxies fix playback performance, not color. Building optimized media from an S1H 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.

Do you need DaVinci Resolve Studio for any of this?

Not for the core V-Log color workflow this guide covers. The Panasonic V-Gamut/V-Log Color Space Transform preset, Resolve Color Management's automatic 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.

Where Studio genuinely enters the picture is threefold. First, reliably decoding some of the S1H's 10-bit files, particularly the higher-bitrate 6K, 5.9K, and 4:2:2 All-Intra modes, since Blackmagic's own 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, relevant if you shot the HLG option covered earlier, both listed on Blackmagic's Studio product page as Studio-exclusive. Third, noise reduction, which matters more on this camera than most once you push toward its ISO 4000 native point, and Resolve's Temporal and AI Spatial noise reduction tools are Studio-only.

Getting Panasonic S1H 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 $295 of software just to make your V-Log footage look right, unless you've actually hit one of the specific decode, HDR, 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 V-Log clip from flat to Rec.709

Here's the full sequence in order, from a fresh S1H 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, and confirm it's V-Log rather than HLG or a standard Photo Style, note which recording mode captured it (6K, 5.9K, C4K/4K DCI, or anamorphic), and check whether it was shot near ISO 640 or ISO 4000.
2. Desqueeze first if the clip is anamorphic. Set the correct desqueeze ratio in Camera RAW or Clip Attributes, or add a Resize node, before touching color, so your scopes and any geometry-sensitive tools read a properly proportioned image.
3. Build optimized media if the clip is stuttering on scrub. If it's a large 6K or 5.9K file playing back roughly, generate optimized media at Quarter or Eighth Resolution before you touch color, so you're not fighting playback performance and grading decisions in the same pass.
4. 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.
5. Node 2, Noise Reduction, if the shot needs it. If the clip was shot at ISO 4000 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. This is the node where S1H footage behaves like footage from any other camera; nothing about V-Log changes how you grade once you're in a normal working space.
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 you call the grade final, particularly if this clip is intercut with footage from a different camera or from the S1H's own HLG or anamorphic modes.

Five to six nodes handle the entire mechanism from flat V-Log source to finished Rec.709 delivery, with the desqueeze step and Noise Reduction as the two optional insertions depending on how the clip was shot. Everything else, from the creative color decisions to the specific tool choices in node 4, is the same grading work you'd do on footage from any camera once it's sitting in a normal working space. A common mistake worth naming directly: adding a third or fourth Color Space Transform "just to compare," then forgetting to remove it. 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 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. Resolve's Color Space Transform dropdown lists presets for a lot of manufacturers, several with names that look similar at a glance. 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. This is exactly the layered-conversion trap covered in the LUT section above: since the S1H ships no post-production conversion LUT of its own, editors reaching for a third-party pack sometimes forget to remove the manual Color Space Transform once the LUT is in place, doubling the conversion.

Third, check that the clip is actually V-Log to begin with. The S1H offers Standard and HLG Photo Styles alongside V-Log, and HLG footage in particular can look flat enough at a glance to get mistaken for V-Log deep into a long shoot day. Applying a V-Log Color Space Transform to HLG footage produces a specific kind of wrong: contrasty, oddly clipped color that looks like an incomplete conversion because, in a sense, it is one, just applied to the wrong input curve entirely.

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.

Sixth, for anamorphic clips specifically: if the image looks stretched, squeezed, or subtly off in proportion after grading, you likely applied the Color Space Transform before the desqueeze step rather than after, or picked the wrong anamorphic ratio in Camera RAW.

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

If your kit mixes an S1H with a GH6, a GH7, or an S5 II, 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," naming the S1H directly as part of that compatibility claim. 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."

Our sibling guides to Panasonic S5 II V-Log import settings and Panasonic GH7 V-Log import settings cover this same Color Space Transform preset from the newer, full-frame and Micro Four Thirds sides of the lineup respectively. The math is identical across all three: Panasonic V-Gamut in, Panasonic V-Log gamma, DaVinci Wide Gamut and DaVinci Intermediate as the intermediate stop. What differs isn't the preset, it's the sensor and generation underneath it. The S1H's full-frame sensor, the GH6 and GH7's Four Thirds sensors, and the S5 II's newer full-frame sensor all differ in noise floor, in exactly how much dynamic range each delivers at its native ISOs, and in generation-to-generation tuning even within the same sensor format.

Panasonic's own claim is that V-Log footage from an S1H, a GH6, a GH7, and an S5 II all start from the same Color Space Transform preset, spanning five years of camera generations and two sensor formats. 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 once footage from a 2019 sensor sits next to footage from a 2024 one in the same scene. Our guide to color matching different cameras in DaVinci Resolve covers the scopes-based cross-check worth running before you call a multi-camera Panasonic timeline finished.

Is the S1H still worth buying in 2026, or should you wait for a successor?

The Color Space Transform settings in this guide haven't changed since the S1H shipped in 2019, and that stability is worth weighing against the camera's age before you decide whether to buy new, buy used, or hold out for whatever comes next.

CineD's original review called the S1H, at launch, "currently... the best mirrorless camera that can shoot video in the market," adding that any competitor wanting to top it "will have to work harder to achieve this." That verdict aged into a genuinely long production run: six years after launch, Panasonic hasn't replaced the S1H, and as of March 2026, the company's own leadership confirmed a true successor is still in active development with no announced release date. Toshiyuki Tsumura, Executive Vice President at Panasonic, told PetaPixel directly: "Currently we hear the needs of the customer is that they're expecting a follow up model for the S1H and we're thinking that developing a product geared toward that need is more of a priority for our brand." Tsumura went further on direction, describing the successor's positioning as one where "the successor to the S1H will evolve into a new category with a view to the full-fledged cinema realm," suggesting Panasonic's next move for this line pushes further toward dedicated cinema camera territory rather than staying a hybrid stills-and-video body.

What that means practically for a buyer weighing a used or clearance S1H against waiting: the camera's known weaknesses are unrelated to color. Matthew Allard's original review flagged the camera's contrast-detect-only autofocus as its clearest limitation, noting it "is very noticeable especially when trying to follow moving objects," a gap the newer S5 II and GH7 both close with hybrid phase-detect systems. Rolling shutter is the other soft spot CineD's own testing flagged as comparatively "less" impressive than the camera's dynamic range results. Neither weakness touches the Color Space Transform settings in this guide, which apply identically to a brand-new S1H, a six-year-old used one, and whatever successor eventually ships, per Panasonic's own stated V-Gamut and V-Log continuity across its camera generations.

A used or clearance Panasonic S1H in 2026 gives up modern autofocus and internal RAW recording, not color science accuracy, and Panasonic's own executives confirm a true successor remains undated as of March 2026. If your priority is grading flexibility and dynamic range on a fixed budget, an older S1H with the settings in this guide still delivers the same Color Space Transform result a newer camera in the same lineup does; if fast-moving subject tracking matters more than color latitude, that's the actual reason to look at the S5 II or GH7 instead.

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 the first few times you're bouncing between Project Settings, the node graph, and Clip Attributes trying to confirm exactly what a clip is 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 V-Log 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, 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 S1H 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 HLG from the same body, or if RCM isn't tagging your clips correctly. Skip third-party LUTs entirely unless you've vetted one specifically against S1H footage, since the camera's own Vlog_709 preset is monitoring-only. Desqueeze anamorphic footage before you color it, not after. And if a clip won't come online at all, that's a decode problem tied to bit depth and codec, 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, keep your exposure near ISO 640 or ISO 4000, confirm the clip actually decoded before you blame the color, and the rest of this workflow is two Color Space Transform nodes doing exactly what they're built to do. Most S1H footage that "looks wrong" in Resolve isn't broken. It's one preset, one monitoring-only LUT preview mistaken for a post-production file, or one codec extension away from correct, and now you know which one.