Implement platform-level checks/querying for VP9 profiles |
||||||||
Issue descriptioncrbug/580623 adds support for vp9 in mp4. The codec string contains profile information. That information is not used. We need to add platform-level querying to check if a given VP9 profile is supported.
,
Apr 21 2016
,
Oct 4 2016
,
Nov 15 2016
,
Feb 17 2017
Will fix as part of MediaCapabilities work.
,
Mar 17 2017
Is there an ETA on this issue will be fixed?
,
Mar 18 2017
I expect to fix it this month. Waiting on a new API in libvpx to get rolled from upstream.
,
May 16 2017
,
Oct 26
FYI, for encrypted VP9, we have chosen not to support profile 1 and 3. So only checking for profile 2 is needed. See issue 898298 .
,
Oct 26
For non-EME this was fixed a while back for HDR demos. https://cs.chromium.org/chromium/src/media/base/decode_capabilities.cc?l=103&gs=kythe%253A%252F%252Fchromium%253Flang%253Dc%25252B%25252B%253Fpath%253Dsrc%252Fmedia%252Fbase%252Fdecode_capabilities.cc%2523kkFc0iwKSSJiYqSZzfreo91z7twgg55rtuEvOVTE3dM%25253D&gsn=IsVp9ProfileSupported&ct=xref_usages Support for ARM and MIPS chips is limited to profiles 0 and 1. Otherwise all profiles are supported. https://cs.chromium.org/search/?q=%22CONFIG_VP9_HIGHBITDEPTH+1%22&m=100&type=cs https://cs.chromium.org/search/?q=%22CONFIG_VP9_HIGHBITDEPTH+0%22&type=cs |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by kqyang@chromium.org
, Apr 19 2016