Google Git
Sign in
chromium / chromium / src / c427644017baeb28d75d10b26ef0ac4eb3d46e7c
commitc427644017baeb28d75d10b26ef0ac4eb3d46e7c[log] [tgz]
authorSida Zhu <zhusida@bytedance.com>Sat Dec 03 03:54:24 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Dec 03 03:54:24 2022
tree7227114629440e214bd7706b523ac1dccb5614d0
parentd0b3f1d10cdd43c3a33fb177b0f4be08132cb7ec [diff]
Video: Support bitstream HDR metadata extraction for Windows

There are several places a HDR metadata may appears:
1. Container 2. Bitstream 3. Both container and bitstream

Our previous logic only use the HDR metadata extracted from
the container, which is okey for VP9 since VP9 doesn't allow
HDR metadata wrote to the bitstream, container is the only
place. but for HEVC/AV1/H264, since the spec allow HDR metadata
wrote to the bitstream, and some muxers choose only write the
metadata to the bitstream, thus if it is the case, then we
will miss the information.

The H264/HEVC/AV1 spec doesn't specify which one should be
preferred, and if both HDR metadata appears in the bitstream
and container, then they should be the same value theoretically.

The CL allow us extract HDR metadata from the bitstream, and
prefer HDR metadata from the bitstream if it appears. Otherwise
use HDR metadata from the container which will make sure we can
get the information completely.

Bug: 1386299

Change-Id: I3ca8c20bf4e964834163fb79b7f082bc8f3f18f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4066720
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: 朱思达 <zhusida@bytedance.com>
Cr-Commit-Position: refs/heads/main@{#1078901}
19 files changed
tree: 7227114629440e214bd7706b523ac1dccb5614d0
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.