commit | eb9cb95d5190a2130cc0159893f7949f6afc9b96 | [log] [tgz] |
---|---|---|
author | Drew Davenport <ddavenport@chromium.org> | Tue Jan 31 00:29:39 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 31 00:29:39 2023 |
tree | 2b78e02075bc9eedc3abfc858e5e7e63dfa63198 | |
parent | dafd640267652734d1ab3a2cbfb68b6aeab96ea5 [diff] |
Revert "media/gpu: Support VP9 resolution changes to smaller w/o dropping ref frames" This reverts commit 2c14d4b2f528aacadfe4e48740a733141b9ece4c. Reason for revert: Started regression tracked in b:262058997 Original change's description: > media/gpu: Support VP9 resolution changes to smaller w/o dropping ref frames > > VA-API VideoDecoders support resolution changes mid-stream to smaller > (without a keyframe), however VP9Decoder thinks this is not supported > and drops all the reference frames, causing some WebM test vector > MD5SUMs to fail. > > This CL adds a parameter to VP9Decoder to avoid dropping said reference > frames when the resolution change is to a smaller one, and sets it to > true from VaapiVideoDecoder only. > > Tested on Intel (TGL volteer) and AMD (guybrush). > > Bug: b:207057398 > Change-Id: I21c50795ba26732b91563255330d79eb1168835d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4032552 > Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org> > Commit-Queue: Miguel Casas-Sanchez <mcasas@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1074245} Bug: b:207057398 Change-Id: I39ccf0239b8a2202de27fa14934cff451eab4d72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4205690 Reviewed-by: Miguel Casas-Sanchez <mcasas@chromium.org> Commit-Queue: Miguel Casas-Sanchez <mcasas@chromium.org> Auto-Submit: Drew Davenport <ddavenport@chromium.org> Cr-Commit-Position: refs/heads/main@{#1098997}
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.