Updated partner tools will allow users to trim Dolby Vision home grades to cinema targets by using the new cinema target displays and trim controls.

The Dolby Vision cinema targets/trims gives creatives the option to derive a mapped cinema version at 108nit HDR (Dolby Cinema) or 48nit SDR (DCI), from their fully graded ‘home’ HDR master – similar to how people leverage the power of the Dolby Vision mapping for the SDR Rec 709 100nit home master. When compared to using a color managed or LUT based static mapping process, this is a great way to quickly derive cinema versions with creative controls for red carpet events, press screenings or for screenings at other special events or venues, especially when the HDR Master grade has been completed and a cinema version requires a quick turnaround.

Learn about the following topics in this article:

• Application types
• Cinema target displays
• new XML version 5.1.0
• Best practices on trimming to cinema targets
  • Creating a 48nit DCI and a 108nit Dolby Cinema version
  • Creating a 108nit Dolby Cinema version, only
  • Cinema first delivery
  • Delivery of a Dolby Vision mapped cinema version
  • Dolby Vision metadata XML delivery
• Dolby Vision XML version delivery overview

All target displays will be updated with an application type denoted in the name which can either be ALL, HOME or CINEMA. Therefore, all target displays will contain a new metadata field <applicationtype> in the XML. To support this field, the new XML version 5.1.0 is introduced when exporting metadata with new cinema targets used.

Application types:

• ALL:                 the target display is utilized for ALL application types (reserved for future use)
• HOME:             the target display is utilized for HOME target displays
• CINEMA:          the target display is utilized for CINEMA target displays

The application type enables users to independently trim to home targets and cinema targets and deliver a single XML or mezzanine deliverable.
For home distribution (encoding), displays that contain the application type CINEMA are filtered and removed from the bitstream since all bitstreams are for HOME distribution, only.

When rendering to a target with application type = HOME, if the target is an interpolated target, i.e. does not have an associated trim in the XML, Cm_offline and updated partner tools will only use the existing trims with application type = HOME. Any existing trims with application type = CINEMA, will be ignored and vise versa.

 

New Cinema Target Displays:

New Cinema Target Displays with <applicationtype>CINEMA</applicationtype>

• 48-nit, P3, DCI-white, Gamma 2.6
• 48-nit, P3, D65, Gamma 2.6
• 48-nit, P3, D60, Gamma 2.6
• 108-nit, P3, D65, ST. 2084

 

XML version 5.1.0

XML version 5.1.0 is supported in the Dolby Vision Professional Tools from version 5.2. upwards and the Dolby Vision Pro Encoder SIDK version 6.0 and upwards.
 


 

XML version 5.1.0 example with new cinema target displays

 

Best practices on trimming to cinema targets

Using the new cinema targets follows the already established Dolby Vision workflow:

• Grade in HDR first
• Create Dolby Vision dynamic metadata by running the Dolby Vision analysis
• Map and optionally trim to a HOME and/or CINEMA target- starting with the respective lowest target first (100nit for HOME, 48nit for CINEMA)

   

Creating a 48nit DCI and a 108nit Dolby Cinema version

Following the established Dolby Vision workflow, follow these basics steps to create a mapped version for a DCI and Dolby Cinema delivery:

• Grade in HDR first
• Create Dolby Vision dynamic (shot-by-shot) metadata by running the Dolby Vision analysis
• Map to a CINEMA 48nit target (choose desired white point)
• Trim for this CINEMA 48nit DCI target
• Map to the CINEMA 108nit Dolby Cinema target
• (optional) trim for this (interpolated) CINEMA 108nit target
• Export a 48nit DCDM or DCP
• Export a 108nit DCDM or DCP

Creating a 108nit Dolby Cinema version, only

If you just need a Dolby Cinema version from your finished HDR grade, you might skip the mapping and trimming to 48nit and start directly with the 108nit mapped version

• Grade in HDR first
• Create Dolby Vision dynamic (shot-by-shot) metadata by running the Dolby Vision analysis
• Map to the CINEMA 108nit target
• Trim for this CINEMA 108nit target
• Export a 108nit DCDM or DCP

 

 

Cinema first delivery

If your primary distribution isn’t OTT, but theatrical/cinema, it’s advised to start the grading in a dedicated grading cinema using a DCI or Dolby Cinema projection.
For such workflows, we recommend using a color managed workflow, that will allow the colorist to grade in a scene-referred space and use an output transform to map to the projector’s characteristics – either DCI or Dolby Cinema.

Once the cinema grade is finished, change the output transform to suit for an HDR HOME distribution (ST.2084 (PQ), 1000nit minimum) and adjust the grade to suit the intended HDR output.
Having finished the HDR version, follow the established Dolby Vision workflow by running the Dolby Vision analysis and the creation of any desired HOME versions.






 

Delivering a mapped cinema version

The mapping to a cinema target, either DCI (SDR) or Dolby Cinema (HDR) is described via Dolby Vision dynamic metadata. However, the intended cinema delivery must be rendered as a stand-alone mezzanine or master, like a Digital Cinema Distribution Master (DCDM) or a Digital Cinema Package (DCP).

There is no integrated media block (IMB) in a cinema that would allow for display mapping to the respective characteristics of the DCI or Dolby Cinema projector in use. The metadata is used to render the above-mentioned deliverables, either directly from the color corrector, or from a mastering tool that supports XML version 5.1.0.


 

Dolby Vision metadata XML delivery

The new Dolby Vision XML version 5.1.0 might not yet be supported by all partner products and services. Therefore, make sure to double check the delivery specifications of the studio you’re delivering to.

Separation of a Dolby Vision XML version 5.1.0 to version 4.0.2 XMLs

If you have created an XML version 5.1.0 containing both HOME and CINEMA application types, you might want to create separate version 4.0.2 XMLs for application type HOME and for application type CINEMA. Use Metafier to separate a single version 5.1.0 XML into two 4.0.2 XMLs.

 

Creation of 4.0.2 XML containing application type HOME:

Creation of 4.0.2 XML containing application type CINEMA:

 

 

Dolby Vision XML version delivery overview

 

Dolby Vision Version	Trims Done	Deliverables	XML Version	Add. Info
Dolby Vision CM v2.9	Rec709 – 100 nit (HOME) P3/Rec2020 – 600 nit (HOME)	Dolby Vision Master/Mezzanine (HOME)	2.0.5
Dolby Vision CM v4.0	Rec709 – 100 nit (HOME) P3/Rec2020 – 600 nit (HOME)	Dolby Vision Master/Mezzanine (HOME)	4.0.2
Dolby Vision CM v4.0	DCI – 48 nit (CINEMA) Dolby Cinema – 108 nit (CINEMA)	Dolby Vision derived Master/Mezzanine (CINEMA) 48nit/DCI Dolby Vision derived Master/Mezzanine (CINEMA) 108nit/Dolby Cinema	5.1.0	CINEMA targets must be rendered as stand-alone DCDM or DCP
Dolby Vision CM v4.0	Rec709 – 100 nit (HOME) P3/Rec2020 – 600 nit (HOME) DCI – 48 nit (CINEMA) Dolby Cinema – 108 nit (CINEMA)	Dolby Vision Mezzanine (HOME) Dolby Vision derived Master/Mezzanine (CINEMA) 48nit/DCI Dolby Vision derived Master/Mezzanine (CINEMA) 108nit/Dolby Cinema	5.1.0	CINEMA targets require XML version 5.1.0 or two separate 4.0.2 XMLs, one for HOME and another for CINEMA