Forum Post

ERH (customer) asked a question.

2022+ TVs: Chroma Weight Metadata doesnt work.
As the title says, Chroma Weight in CMv2.9 (TV-LED) does not work on all TVs manufactured after 2022.

I’m aware this was already a known issue in LLDV CMv2.9 and it was corrected in the cmv4.0 SOC, but I don’t understand how the same bug has now also appeared in TV-LED mode. Interestingly, it still works correctly in CMv4.0 except for 2025 LG TVs, where not only Chroma Weight doesnt work but the saturation gain also appears to be non-functional. 2017-2021 TVs TV-LED are fine.

How can tone mapping work correctly if some metadata is not working?

thank you.

  • ERH (customer)

    This was tested with many different players and the TVs internal player.
    • Nmcfarlin (Dolby)

      Hi there! Thanks for reaching out - just to clarify, are you seeing the same behavior with both external players & the TV's built in player? Any additional details on the testing setup/hardware is very helpful as we look into this.
  • ERH (customer)

    Hi, thank you for the reply.

    We first noticed that something was missing while previewing our grade on the G5, which prompted us to investigate further. We then created a test file using the maximum and minimum Chroma Weight values in DaVinci Resolve. The extreme values were not visible in cmv2.9 on the LG C2, C3, C4, C5-G5 and a Hisense TV from 2022. The same Chroma Weight variations were clearly visible on the older LG C1, CX, C9, and C8.

    We tested with multiple playback devices, including the Sony X800M2 Blu-ray player, Oppo players, the Nvidia Shield, and the TV's built-in media player, and obtained the same results.

    As for the Saturation Gain metadata, it does not appear to function on the G5, while it remains functional on the C4 and G4 or earlier TVs. I don't know about the 2026 models.
    Expand Post
  • Nmcfarlin (Dolby)

    Thanks for the additional information. And you're generating your encodes directly from Resolve as well I'm assuming?
    • ERH (customer)

      We tried Resolve and the Dolby Encoding Engine. We also confirmed that the metadata was present in the XML (attached in this reply).