Dolby Vision Profile 8.4 Update

First of all, color management. We’d stick with one of Dolby Professional’s recommendations:

DaVinci YRGB Color Managed (auto)

Color Processing Mode – HDR. Output Color Space – HDR HLG. 

DaVinci YRGB Color Managed (auto unchecked)

Color Processing Mode – HDR Rec.2020 HLG. Output Color Space – Rec.2020/Rec.2100 HLG

“For the Color Management setting, there are many options for this use case using different color science settings in Resolve. The key setting is to set the output color space as Rec.2020 HLG.” – Dolby Professional

Secondly, do not perform Dolby Vision analysis or a trim pass if your deliverable is Profile 8.4.

Our advice is to disregard our previous post (since deleted) and to watch the tutorial we’ve linked to at the bottom of this post. We’ve copy/ pasted a few relevant passages pertaining to metadata, all of which can be found over at Dolby Professional:

Does Dolby Vision 8.4 also have dynamic metadata? If so, where/how is it created?

Yes, like all Dolby Vision profiles dynamic metadata is embedded in every Dolby Vision 8.4 encoded media file. In the main workflows for creating or distributing content for Vimeo, this metadata is automatically computed during the video capture process (for example, in iPhone 12) or by automatically analyzing the video frames prior to the encoding process (for example, in FCP or Compressor). For these common workflows, there are currently no additional user controls for the creation of this metadata, with the exception of the initial choice to include Dolby Vision metadata.

I’m used to creating Dolby Vision mezzanine files for delivery to an OTT service such as Netflix, can I use the same workflow?

The workflows established for delivering content to services such as Apple TV+, Disney+ and Netflix are quite different from those focused on delivering content in Dolby Vision for Vimeo. For most use cases when delivery of a profile 8.4 file is required it is simpler to go back to the HDR master grade, export this to an HLG master, then encode using Apple Final Cut Pro or Apple Compressor directly to Dolby Vision profile 8.4. However, it should be noted that this workflow does not currently support any trim metadata for specific target displays. Any existing trim metadata (as well as shot based analysis metadata) in a project would not be included in the encoded Dolby Vision file.

source

“Use Profile 8.4 if you haven’t created any Dolby Vision metadata, as it will be generated on a frame-by-frame basis during the encode and if you’re going to upload the encode to an online platform like Vimeo or Bilibili where you also need cross compatibility with HLG devices.”

source

Export Dolby Vision Profile 8.4 using Dolby Vision encoding from Resolve

  • Navigate to the delivery workspace and set the Format and Codec as QuickTime H.265. Set the encoding profile as Main 10 in the Encoding Profile drop down.
  • Go to the Advanced Settings and set the Dolby Vision Profile as Profile 8.4. Resolve will then calculate frame-by-frame metadata for the HDR image during the export process.

Best Practices: Create Dolby Vision Profile 8.4 using DaVinci Resolve with an external HDR display

4 thoughts on “Dolby Vision Profile 8.4 Update

Add yours

  1. Hi,

    Do you know if 8.4 profile can be accessed in Davinci Resolve Studio with windows 11 desktops? or is it only enabled in Macs?

    Thanks in advance!

    1. It works on macOS and Windows PC but apparently not all Windows laptops support Dolby. I’m a Mac user, don’t know much about Windows desktops.

      1. thanks for your reply, I’m able to do it via Mac, but in my windows desktop (custom made) there is no option; it only shows the mapping option. 😦

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Blog at WordPress.com.

Up ↑