Create a Supplemental IMF in Dolby Vision - Shot addition/replacement

Create a Supplemental IMF in Dolby Vision - Shot addition/replacement

The purpose of this tutorial is to explain you how to replace or add an entire shot with its new Dolby Vision metadata. This method creates a supplemental version which will add or replace part of the Dolby Vision OV package .

For details on how to perform certain operations, please refer to the MIST user manual.

In this tutorial we have the following sources:
  1. An Original Version IMF in Dolby Vision (Meridian)
  2. Netflix' logo in JPEG2000 UHD P3D65 PQ 23,976fps.
  3. A Dolby Vision MDF file for the Netflix' logo.
  4. A stereo audio track in PCM 24bits 48kHz wave file.
  5. A 5.1 audio track in PCM 24bits 48kHz wave file.
The files used for this example are not exhaustive. Source material must be of a quality that is equal to or greater than the one required by Netflix. In case of doubts about the quality of your sources, please refer to the technical specifications of Netflix in force.

I. Start with importing the original version IMF

When importing an IMF Package, MIST will automatically create a new project.

Start by importing the original version IMF :



You can then inspect the package:



Then process to a validation, either using MIST validation tests or Photon.

In this case our source is an Application 2E with Netflix specifications. for this reason we can see warnings regarding the other applications:


 
By clicking on OK, MIST creates a new timeline with the package's assets.



One video track and a 5.1 soundfield are packaged in one segment. 



We can also see the presence of Dolby Vision metadata thanks to the white bar on the clip. This bar tells us that the clip is read-only. If we look in the CMS tab into the COMPOSITION SETTINGS, we can see that MIST has detected Dolby Vision technology:



II. Performing shot addition/replacement

In this tutorial, we seek to add the Netflix logo and its audio tracks at the beginning of the content. This manipulation requires the Dolby Vision metadata of the new clip to add. 

Import media into the Quick Library

First, we need to import our logo into the project.
In our case, it is a JPEG2000 UHD P3D65 PQ image sequence. JPEG2000 files have metadata indicating their frame rate. It is therefore not necessary to specify it into MIST.

We can browse through the Windows file browser to drag and drop the media into the Quick Library.

Add media in the timeline

Select your media from the Quick Library .
First your video file then the audio channels of the two audio configurations in order of pasting.
Take the assets using the function of carrying (select the clip then drag it by holding left click). 

Before placing them, verify the insertion method is INSERT by clicking the REPLACE / INSERT button on the top left of the timeline:



Check that your playhead position is at the desired location and that the tracks where the media should be pasted are active and selected (the track name is highlighted in cyan).

For audio tracks, just click on the first audio channel, here it is the left channel of our 5.1:



Use `Ctrl + Alt + V` to paste the media (stacked at cursor).

Fit the timeline

We can notice that the media is longer than the composition and the reel. We need to fit them:



First, fit the composition by calling the timeline hotbox `Ctrl + right click`. Then go to the COMPOSITION tab:




Second, we need to modify reels because of the new composition range.
What is not covered by a reel will not be exported.
To do this we can use the Auto Reels function and use the FIXED REEL COUNT method to obtain a single reel covering our whole content:






Import new Dolby Vision metadata

As we can see, our IMF has Dolby Vision metadata (white bar) while the logo we just inserted does not have any (no bar on the clip):



To import Dolby Vision metadata, select the clip. Right-click on it then in the menu DOLBY VISION METADATA choose Import ...



Once in the import window, select your MDF file and finish by clicking OK.
We can see that our sequence has been split according to its Dolby Vision metadata file:



Remember to make sure of your composition settings before accessing the export tool. Check if the active area aspect and the mastering display settings are matching the one used by the Dolby Vision metadata file imported.

III. The IMF export module

To access the IMF export module, click the IMF button at the bottom left of the timeline.

Once in the IMF Export Tool, in the GENERAL tab, name your IMF and select the Netflix HDR Dolby Vision template from the drop-down menu:



On the ESSENCE and VIDEO tab, make sure that the Dolby Vision check box is checked and prefer the GPU engine to the CPU one in the drop-down menu on your right:



In the AUDIO tab, make sure that both 5.1 and stereo audio configurations are present. Name them, change the language if necessary and check the mapping of the audio channels:



Then copy and paste the composition name into the packing list annotation:



In the Naming tab, we can use some tags to name the assets and find them easily. Here we want that each asset takes the name of the composition.
For that, we need to use the $PackageName$ tag:



In the OUTPUT tab, choose the destination of your packet and select Differential as the package type:



It is advisable to check one last time using the summary on your left, the settings of your package. As soon as you are ready, click on the MAKE IMF button.

IV. Import and Q.C of the supplemental version

As soon as your supplemental version has been exported, you can import into MIST to check that everything is correct.

From your current project you can import the new package version of your IMF from the Library ( `F2` ).

In the CONTENT tab, we can see all metadata of our package.
Track files written in red indicate the absence of media in the package. This is normal because it is an additional version containing only the new assets specific to the VF. The missing ones are those related to the OV. To control a VF, you must first import its OV.



This will not be necessary in our example because the OV is already existing in our project.

We advise you to launch a validation test from the VALIDATION tab in order to check the integrity and the application used by your IMF. 

In the case of using PHOTON, remember that to date it is not yet able to validate Dolby Vision packages. You should therefore have warning messages about this that are quite normal.

If your two IMF packages are in the same project, you can toggle between them using the composition drop-down menu into the timeline:





    • Related Articles

    • Create a Supplemental IMF in Dolby Vision - Frame replacement

      The purpose of this tutorial is to explain you how to replace image frames in a packaged IMF in Dolby Vision, without requiring an update of the Dolby Vision metadata. This method creates a supplemental version. For details on how to perform certain ...
    • Create an Original Version IMF in Dolby Vision

      The purpose of this tutorial is to introduce you to the main steps of making an Original Version package in Dolby Vision according to Netflix specifications. For this tutorial, we will use existing Dolby Vision metadata. For details on how to perform ...
    • Create a Supplemental IMF in SDR

      The purpose of this tutorial is to introduce you to the main steps for creating an additional package from an existing IMF according to Netflix specifications. For details on how to perform certain operations, please refer to MIST user manual. In ...
    • Create an iTunes delivery in Dolby Vision

      This article will guide through the basics steps to follow in order to create an iTunes package in Dolby Vision. For this example we will use the following sources : Apple Prores 4444 in UHD 12 bits with P3 D65 as primaries, Rec 709 as transform ...
    • Creating an IMF Supplemental Package

      I. Prepare the IMF Project With Mist, you can directly import an IMF Package, that will create automatically the project will all the CPLs listed in Compositions. You can then inspect the package: and possibly perform a validation: In this case our ...