Google Git
Sign in
chromium / chromium / src / eebde65c8889f95e83d42dbcb72b9bf5559a1c35
commiteebde65c8889f95e83d42dbcb72b9bf5559a1c35[log] [tgz]
authorSida Zhu <zhusida@bytedance.com>Wed Feb 19 02:37:03 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Feb 19 02:37:03 2025
treef31730c387793eb2c31b4cf59ae1baab0f7dca3b
parent0f641455b6a1a76bd1e517417de3ee1406d28003 [diff]
Video: Support H26x per-frame QP for VTVEA

This CL add per-frame QP support for H.264 & H.265.

Querying `kVTCompressionPropertyKey_SupportsBaseFrameQP`
is the way Apple recommends to test whether per frame QP
is supported by a given encoder.

Based on tests on Intel and Apple Silicon Macs, the
property `kVTCompressionPropertyKey_SupportsBaseFrameQP`
will only report `supported` for encoders created with
`kVTVideoEncoderSpecification_EnableLowLatencyRateControl`
set to `true`. and, the per-frame QP support is actually
limited to the below encoders:

1. Apple H.264 (HW) Encoder
(com.apple.videotoolbox.videoencoder.h264.gva) (x64)

2. Apple RealTime Video Coding HEVC (HW) Encoder
(com.apple.videotoolbox.videoencoder.hevc.rtvc) (arm64)

3. Apple RealTime Video Coding H.264 (HW) Encoder
(com.apple.videotoolbox.videoencoder.h264.rtvc) (arm64)

Bug: 40941481
Change-Id: I829b22fe0cc7159b1031b4b9620286e10e412741
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6273883
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Reviewed-by: Jianlin Qiu <jianlin.qiu@intel.com>
Commit-Queue: Sida Zhu <zhusida@bytedance.com>
Cr-Commit-Position: refs/heads/main@{#1421750}
2 files changed
tree: f31730c387793eb2c31b4cf59ae1baab0f7dca3b
  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. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. 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.