DJI D-Log to Rec.709 in Final Cut Pro

Final Cut Pro ships a built-in DJI D-Log LUT, which handles most drone footage on its own. The two things that still trip people up: a compact drone's D-Log M curve, and files DJI itself sometimes mislabels as already-corrected.

Confirm the Camera LUT, and check for D-Log M

DJI D-Log is one of Final Cut Pro's built-in Camera LUT options, applied automatically when the app recognizes the log metadata on import. Confirm it: select the clip, open the Info inspector, switch the Metadata View pop-up to Settings, and check the Camera LUT pop-up.

Compact DJI drones often shoot D-Log M, a milder curve than full D-Log, and it needs its own conversion. Apple's built-in list is not confirmed to carry D-Log M as a separate entry, so do not assume Final Cut applied the right one automatically. If a D-Log M clip still looks crunched or over-contrasty after the LUT, that mismatch is the likely cause; set the Camera LUT manually or bring in a manufacturer-provided D-Log M LUT instead.

The metadata trap

Some DJI files tag themselves as Rec.709 in their metadata even though the actual image is log. Final Cut trusts that tag when deciding whether to auto-apply a Camera LUT, so a mislabeled clip sits in your timeline uncorrected while its twin from the same flight gets graded normally. If two clips from one flight refuse to match, check what Camera LUT actually got applied to each one before you touch a color wheel. Judge the image, not the label.

White balance and exposure, in that order

1. White balance with the eyedropper. In the Video inspector's Balance Color section, choose White Balance and click a neutral gray or white area. A drone yawing from sunlit ground to open sky drifts its own white balance between takes, so neutralize per clip rather than trusting one setting for the whole flight.

2. Protect the highlights. Aerials are dominated by sky, which reads brighter to your eye than the scopes show. Use the Color Board's Exposure control against the waveform, protect the highlights, and lift ground detail rather than crushing the whole frame to tame a sky that is not actually clipping.

3. Match to the ground cameras last. Most drone footage sits next to a Sony, Canon, or iPhone in the same project. Match the corrected aerial to the ground camera's baseline on the scopes before any creative look goes on.

Where it still goes wrong

Trusting the metadata tag. The single most DJI-specific failure. A clip that looks already-graded in the browser but flat on the timeline is almost always a mislabeled file, not a settings mistake you made.

D-Log M treated as D-Log. Crunched contrast and skewed color that will not fully correct, even after grading, usually means the milder D-Log M curve got the full D-Log LUT.

The part that is measurement, not taste

White balance, transform, exposure, and cross-camera match are all objective steps, which is why Basecut automates them for a whole card dump at once, locally on your machine. It reads the image instead of trusting DJI's tag, corrects D-Log and D-Log M per clip, and hands a matched Rec.709 baseline to DaVinci Resolve, where the creative grade starts. It exports FCPXML so Final Cut can pick up the same bins and tags, but to be direct about the limit: its automated color correction is built for Resolve, not for a Final Cut library, so if Final Cut is where you finish, the steps above are what catches DJI's mislabeled files by hand.

The 14-day trial (5 free exports, no card) is enough to see the correction on your own footage before deciding anything. See it on real footage.