Part I: Project settings
Part II: BT.2020 or P3-D65 Limited?
Part III: HDR Palette, project render settings, generate MaxCLL and MaxFall HDR10 metadata
Part IV: HDR to SDR Conversion LUT for YouTube
Part V: RAW
Part VI: The Grade
Part VII: The State of HDR Film Emulation LUTs & Plugins
Part VIII: Why HDR Production Monitors Matter
For HDR projects, steer clear of recording XAVC S-I 4:2:2 internal if at all possible. Art Adams explains:
“The Y’CbCr encoding model is popular because it conceals subsampling artifacts vastly better than does RGB encoding. Sadly, while Y’CbCr works well in Rec 709, it doesn’t work very well for HDR. Because the Y’CbCr values are created from RGB values that have been gamma corrected, the luma and chroma values are not perfectly separate: subsampling causes minor shifts in both. This isn’t noticeable in Rec 709’s smaller color gamut, but it matters quite a lot in a large color gamut. Every process for scaling a wide color gamut image to fit into a smaller color gamut utilizes desaturation, and it’s not possible to desaturate Y’CbCr footage to that extent without seeing unwanted hue shifts.
My recommendation: always use RGB 4:4:4 codecs or capture raw when shooting for HDR, and avoid Y’CbCr 4:2:2 codecs. If a codec doesn’t specify that it is “4:4:4” then it uses Y’CbCr encoding, and should be avoided.”
This is the consensus of industry professionals, including post production houses, who prefer to see RAW for HDR projects. This is also why streaming platforms like Netflix use the ICtCp color space. For those wanting to future-proof their material or who might need to create a Dolby Vision master in the future:
“Dolby Laboratories recommends using certain types of source material for creating high quality Dolby Vision content. In general, the best source material for Dolby Vision best retains the native color gamut and original dynamic range of the content at the time of its origination.
Original camera footage
For mastering first run movies in Dolby Vision, the original camera raw files or original film scans are ideal.
- Film: Original Camera Negative (OCN)
- Digital: Camera RAW”
Matthew Bilodeau provides further grounds for preferring 12-bit RAW to 10-bit Log:
“… if you’re considering which codecs to use as intermediates for HDR work, especially if you’re planning on an SDR down-grade from these intermediates, 12 bits per channel as a minimum is important. I don’t want to get sidetracked into the math behind it, but just a straight cross conversion from PQ HDR into SDR loses about ½ bit of precision in data scaling, and another ¼ – ½ bit precision in redistributing the values to the gamma 2.4 curve, leaving a little more 1 bit of precision available for readjusting the contrast curve (these are not uniform values). So, to end up with an error-free 10 bit master (say, for UHD broadcast) you need to encode 12 bits of precision into your HDR intermediate.”
“Converting one 10-bit format into another 10-bit format will reduce the performance of the signal and should be avoided whenever possible.” – HDR: A Guide to High Dynamic Range Operation for Live Broadcast Applications, Grass Valley
In our own experience, and from watching countless videos uploaded by others, RAW will give significantly better results and there’s no way we’d go back to shooting Log for HDR. Not to mention that the a7s III 4.2K ProRes RAW files contain nearly 25% more resolution, with no baked-in denoising, lens corrections, in-camera sharpening or other enhancements applied.

Click on image below to enlarge.


HDR tends to amplify existing noise in the image, particularly in shadow areas. De-noising in post with either Resolve’s own built-in denoising software or Neat Video will give better results.



The noise is more organic and the stepping has disappeared.
And here’s the same ProRes 4444 clip with a small amount of spatial noise reduction in addition to the temporal. Mode faster – radius small – Luma 2 – Chroma 2.

There’s also more color information to work with in the RAW clip than in the XAVC S-I internal clip:


“If you’re using a prosumer or entry level professional camera, taking a few preparatory steps to set up how you’ll actually be capturing the image can mean the difference between getting footage that can be used in HDR mastering, vs. footage that can’t.
- 16 bpc > 14 bpc > 12 bpc > 10 bpc > 8 bpc: 10 bpc should be your minimum spec.
- RAW > LOG > Linear > Gamma 2.4: avoid baking in your gamma at all costs!
- Camera Native / BT.2020 > DCI-P3 > Rec. 709 color primaries
- RAW > Compressed RAW > Intraframe compression (ProRes, DNxHR, AVC/HEVC Intra) > Interframe compressed (AVC/H.264, HEVC).” – Samuel Bilodeau, Mystery Box
Mark Spencer demonstrates how, with the same extreme grade applied, the Sony internal XAVC file falls apart much more easily than the ProRes RAW one:


It should be mentioned here that traditional lift/gamma/gain wheels are unsuitable for grading HDR, just one reason why DaVinci Resolve, with its HDR Color Palette, is preferable to Final Cut Pro.
“It is also worth bearing in mind that the traditional lift, gamma, and gain operators are particularly unsuitable for acting on ST 2084 image data, where 0-1 represent zero to 10 000 cd/m2. Highlights, in particular, can swing uncontrollably into extreme values as a result of small changes. Modern grading systems offer alternate grading operators tailored to the needs of HDR grading.” – Nick Shaw
For Color Gamut for RAW Output, select either S-Gamut3/S-Log3 or S-Gamut3.cine/S-Log3. For what it’s worth, S-Gamut3.cine/S-Log3 is the most common color space used on Sony FX9, F55, FS7, F5 and FX6 Netflix productions (which also happen to use the P3-D65 color space in post-production). We’ve also been informed that key mastering engineers at Sony Pictures in Culver City recommend selecting the S-Gamut3.cine/S-Log 3 settings in Resolve. S-Log3 is recorded as Full range. There is no option to select Legal range. RAW is sensor native data and does not apply any color space or log curve – only the color space metadata is saved. RAW is recorded as 16-bit linear which is then compressed and recorded in the Ninja V as 12-bit ProRes RAW. The color space is applied to the RAW data during the de-Bayer process.


Exposure is critical. Avoid blown-out highlights and overexposed skin at all costs.


In order to work with ProRes RAW footage in DaVinci Resolve, first you’ll want to convert it to cDNG. Download RAW Convertor from the Apple App store.

Project settings:

After dropping the folders onto the timeline of the Edit page, you’ll be able to make adjustments to the clips in the Camera RAW tab on the color page of DaVinci Resolve. If you’re grading with an OLED TV, we recommend reducing exposure beforehand to avoid frying your display!

Here’s a comparison between lossless, 3:1 and 5:1 cDNG:
Alternatively, you can transcode ProRes RAW to ProRes 4444 XQ. Import your ProRes RAW files into Apple Compressor and select ProRes 4444 XQ.

Compressor will automatically choose S-Log3/S-Gamut3. If you would prefer to work with S-Log3/S-Gamut3.cine, in the video tab, select S-Log3/S-Gamut3.cine for the RAW to Log conversion. Compressor will then automatically choose S-Log3/S-Gamut3.cine for the Camera LUT.

After importing your ProRes 4444 XQ files into DaVinci Resolve, you’ll need to change the Input Color Space to Same as Timeline.

RED Komodo Project Settings





Wondering why the RAW transcode defaults to Rec 2020PQ. Have you tried any other settings like not changing it from SLOG3/SGamut i.e. what came from the camera? Let Resolve handle it?
Apple Compressor is applying the manufacturer-specified processing. Your other choices are rec.601, rec.709, rec.2020, rec.2020 HLG and P3D65 PQ. There is no advantage to not applying the S-Log3/S-Gamut3 Camera LUT in Compressor. You can learn more about ProRes RAW here: https://www.apple.com/final-cut-pro/docs/Apple_ProRes_RAW.pdf
All RAW clips are by definition HDR.