commit | 4130a38e27c173f4789fd8b87e73ae082e1599e2 | [log] [tgz] |
---|---|---|
author | Anantanarayanan G Iyengar <aiyengar@nvidia.com> | Fri Nov 01 21:46:33 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Nov 01 21:46:33 2024 |
tree | b7c0762e7bfa43f5048eab161f978219aef383bb | |
parent | e8dc31a292ed93e28e1532652547ceeaa007576f [diff] |
Support HDR Swap Chains without HDR Metadata in Chromium on Windows Currently in Chromium on Windows swap chains with the DXGI_FORMAT_R10G10B10A2_UNORM for HDR 10 content are only created when there is accompanying HDR metadata. For WebRTC video streams, HDR metadata is an optional extension. In addition the gfx HDRMetadata structure https://source.chromium.org/chromium/chromium/src/+/main:ui/gfx/hdr_metadata.h;l=132?q=gfx::HDRMetadata&ss=chromium already has reasonable defaults (the gamut is set to rec2020, minimum luminance to 0 nits, and maximum luminance to 10,000 nits) Without metadata the DXGI swap chain defaults to DXGI_FORMAT_B8G8R8A8_UNORM which is basically downgrading the stream to SDR. This patch provides functionality to allow hdr10 swap chains to be created on Windows if there is no accompanying metadata if the input color space is BT.2020 with the transfer function PQ. We also ensure that the DC overlay processor allows the video overlay to be created if the video format is BT.2020 with transfer function PQ (HDR 10). BUG=376304009 Change-Id: I15edb5ecb0d99359c9038c9505579ab6905753a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5976756 Reviewed-by: Sida Zhu <zhusida@bytedance.com> Reviewed-by: Markus Handell <handellm@google.com> Reviewed-by: Kenneth Russell <kbr@chromium.org> Reviewed-by: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by: Maggie Chen <magchen@chromium.org> Commit-Queue: Anantanarayanan Iyengar US <aiyengar@nvidia.com> Cr-Commit-Position: refs/heads/main@{#1377106}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.