Don't elide all initial config changes in D3D11VideoDecoder
Previously, we would elide any config change that arrived before the first frame was decoded, since the accelerated decoder sends one even if it matches the container config. Unfortunately, some streams actually do change config before the first frame (e.g., some RTC streams). Eliding it leaves the D3D11 decoder configured for the container config. This CL causes D3D11VideoDecoder to elide the config change, and prevent re-allocating the D3D11 decoder, only if the config matches what the container told us. Bug: 1109397 Change-Id: Ib9c5ec77897b24666118077935f91c541cbdabe2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2585666 Commit-Queue: Frank Liberato <liberato@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#835833}
Showing
Please register or sign in to comment