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}
4 files changed
tree: b7c0762e7bfa43f5048eab161f978219aef383bb
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

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.