A standard Dolby Vision deliverable is the Dolby Vision Metadata delivered as an XML file alongside the HDR graded master.
To export Dolby Vision L2 Metadata (CMv2.9) with an HDR master:
Right-click the sequence and select Export.
The sequence must have an HDR track set as the Primary track, with the Dolby Vision analysis performed on every shot.
In the Export window, navigate to the destination folder.
Select Export > Distribution Package.
Select Format Preset > Autodesk > Dolby Vision > Dolby Vision 2.9 Master (12-bit Apple ProRes 4444).
Click Export.
Once the export is done, you have a package that includes a MOV master and a Dolby Vision XML file.
What you deliver depends on the requirements from your customer (director, producer, studio...). The Distribution Package presets should cover most cases, but as always, you can always amend and create new export presets.
Overall, you can create the following deliverables when working in the context of a Dolby Vision pipeline:
Mezzanine Master
HDR/SDR Preview
A Dolby Vision XML file
The XML contains all the Dolby Vision metadata.
Use the Autodesk > Dolby Vision XML presets to export this set of deliverables.
You can also export the XML from:
You export the result of your HDR work in the form of an XML file from:
The Dolby Vision XML file contains all the sequence-based data required for final delivery with Dolby PQ master.
The XML contains the following data:
Application and Version
Creation Date
User-defined comment
Sequence Aspect Ratio
Colour Encoding
Dolby Vision version (2.9 or 4.0)
Mastering and Target Displays (Level 0)
Shot-based Image Characteristic (analysis) (Level 1)
Target Display Specific Trims (Level 2)
Offset to Level 1 (Level 3)
Aspect Ratio (Level 5)
Advanced Target Display Specific Trims (Level 8)
Source Content Primaries (Level 9)
Frame based trims animation
Frame-based animation for dissolve transitions
Autodesk products proprietary data (which could be read by Autodesk Flame products only)
When exporting a Dolby Vision XML file:
Use MediaHub to export both media and Dolby Vision XML file using the Distribution Package export type.
The following presets are available for both Dolby Vision 2.9 and 4.0 formats:
As always, you can create your own export presets if those included with the product do not match your needs.
Some options are specific to the Dolby Vision distribution package deliverables.
Format: Set to Dolby Vision XML
Mode: Select the Dolby Vision version of the Content Mapping to use. Note that version 4.0 includes the version 2.9 for backward compatibility. Same as Source uses the version defined in the HDR track.
Composition: The name of the title of the program, which might be different from the actual package name. Tokens can be used to define the composition name.
Comment: Text included in the Dolby Vision XML file in the comment field.
Filename: Use the Pattern Field to define the name of the package. Tokens can be used to define the composition name and folders can be created using the / character.
Export Video Media: Enable to export video media.
Export Audio Media: Enable to export audio media.
These options are the same as Movie Export mode.
These options are the same as File Sequence mode.
These options are the same as Audio File Export
You can ignore these options for Distribution Package Export formats.
You can always export your content as a regular movie or file sequence.
In this case, make sure the Primary track is set on the HDR track, and the HDR FX is set to iCMU. This ensures the exported media files are encoded using the output of the iCMU.
If you export a Dolby Vision XML file from a sequence without including a 100-nits target display, you get an error message.
This error message appears because Dolby requires data for an 100-nits Target Display, in addition to other Target Displays.
To fix this, go back to the sequence an perform a Dolby Vision analysis with the 100-nit Target Display selected in the HDR effect. You can then export the Dolby Vision XML file again.
You cannot export a Dolby Vision XML from a sequence where two Target displays share identical luminance (nit) values. This can happen if you're using custom Target displays. If this happens, you must reset the Dolby Vision Trims for one of these displays, such as example 600-nit, P3-D65 and 600-nit, BT.2020.