Cinema Targets Missing in DaVinci Resolve Studio v18.1 After Dolby Vision Configuration File Import

Reading time: ~2 minutes

Summary

If Cinema Targets disappear in DaVinci Resolve Studio v18.1 after importing a Dolby Vision configuration file, the cause is a version conflict between the configuration file and the application. This article explains why this happens and how to resolve it.

Who this is for

Colorists and post-production professionals using DaVinci Resolve Studio v18.1 or later with a Dolby Vision trims license.

Background

What is cm_config?

cm_config passes Dolby-defined master and target display information to partner software applications. Partner applications are typically bundled with the version of cm_config appropriate to their functionality.

Important: Do not install a newer version of cm_config or move a cm_config file from one application to another unless directed to do so by Dolby Support. Loading a newer version into an unsupported application can cause unexpected behavior, particularly with Cinema targets and trims.

Cinema targets in DaVinci Resolve Studio v18.1

DaVinci Resolve Studio v18.1 introduced new Cinema targets and trims, enabling mapping from an HDR grade to DCI and Dolby Cinema targets. Trim controls for both the new Cinema targets and the existing Home targets are unlocked by the Dolby Vision trims license.

Symptom

Cinema Targets are missing or do not appear in DaVinci Resolve Studio v18.1 after a Dolby Vision configuration file has been loaded.

Cause

Until the end of November 2022, Dolby Vision license packages included both a Dolby Vision license file and the Dolby Vision configuration file version 1.3 (cm_config_v1.3.bin). This configuration file is compatible with DaVinci Resolve Studio versions prior to v18.1.

When cm_config_v1.3.bin is loaded into DaVinci Resolve Studio v18.1 or later, the new Cinema Targets disappear.

Resolution

If you have loaded the v1.3 configuration file in DaVinci Resolve Studio v18.1, delete the following file and restart Resolve:

~/Library/Application Support/Blackmagic Design/DaVinci Resolve/DolbyVision/config_v2.bin

Important: Do not load cm_config_v2.4.bin into DaVinci Resolve Studio versions prior to v18.1. Those versions don't support the new processing pipeline for Cinema targets and trims.

Going forward

New Dolby Vision license packages no longer include a Dolby Vision configuration file. All configurations are now delivered directly via DaVinci Resolve Studio.

Summary and closing

Cinema Targets disappearing in DaVinci Resolve Studio v18.1 is caused by a version conflict with the legacy cm_config_v1.3.bin configuration file. Deleting config_v2.bin and restarting Resolve restores the Cinema Targets. New license packages from Dolby no longer include a configuration file, so this issue should not affect new installations.

If you have any questions about Cinema Targets in DaVinci Resolve Studio, feel free to post them in our Dolby Vision Forum or share your findings with the Dolby Creators Community on Discord.