Accelerated VP9 decoding of profiles higher than 0 is fragile |
||||
Issue descriptionCurrently we don't read VP9 profile from the bitstream and instead just send media::VP9PROFILE_ANY value to all decoders and leave it up to them to interpret what it means. This is problematic because for example DXVAVideoDecodeAccelerator doesn't check which profiles are actually supported (https://code.google.com/p/chromium/codesearch#chromium/src/content/common/gpu/media/dxva_video_decode_accelerator_win.cc&l=1341) and VAAPI simply maps VP9PROFILE_ANY to VAProfileVP9Profile0 (https://code.google.com/p/chromium/codesearch#chromium/src/content/common/gpu/media/vaapi_wrapper.cc&rcl=1458819216&l=128). I guess this means that we might get unexpected VP9 playback failures on DXVA/VAAPI platforms when trying to play VP9 streams with profiles higher than 0, if the corresponding platform decoder doesn't actually support those profiles.
,
Mar 28 2016
,
May 3 2016
guys surely what matters here is youtube videos? Chrome dies here without hardware acceleration!
,
Jun 12 2017
This bug has been stale for > 1 year. If you still want to keep it, please change StaleAssigned label to StaleKeep. If you don't want to keep it anymore, you don't need do anything, I will close it in 30 days. thanks
,
Jul 18 2017
this bug has been stale for > 1 year. resolve as won't fix with label StaleClosed. If you think it's worth to keep, please re-activate and assign appropriately. |
||||
►
Sign in to add a comment |
||||
Comment 1 by servolk@chromium.org
, Mar 24 2016