New issue
Advanced search Search tips

Issue 846120 link

Starred by 2 users
Status: Assigned
Owner:
jrumm...@chromium.org
Cc:
xhw...@chromium.org
liber...@chromium.org
dalecur...@chromium.org
chcunningham@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Use MediaCodecInfo.CodecCapabilities.FEATURE_SecurePlayback to detect secure codec support

Project Member Reported by xhw...@chromium.org, May 23 2018 
Currently we use .secure suffix to detect secure codec support. Now we have MediaCodecInfo.CodecCapabilities.FEATURE_SecurePlayback we should use it instead.

https://cs.chromium.org/chromium/src/media/base/android/java/src/org/chromium/media/MediaCodecUtil.java?rcl=c33471e7ce259ffd374b82cb159beaca48043e8d&l=311

Also see http://b/15587335

Comment 1 by xhw...@chromium.org, May 23 2018 

Also it seems MediaCodecUtil::CanDecode() is only used for EME query now. After we get this fixed, we can remove a lot of old code around CanDecode().

https://cs.chromium.org/search/?q=MediaCodecUtil::CanDecode&sq=package:chromium&type=cs

Comment 2 by xhw...@chromium.org, May 23 2018

Cc: chcunningham@chromium.org dalecur...@chromium.org liber...@chromium.org
As the first step, for L3 where secure decoder is not required, it seems we could just use canned function like:

MediaCodecUtil::IsVp8DecoderAvailable()
MediaCodecUtil::IsH264EncoderAvailable()
...

Comment 3 by xhw...@chromium.org, Aug 27

Labels: -M-70 M-72

Comment 4 by xhw...@chromium.org, Sep 28

Labels: Target-72

Comment 5 by xhw...@chromium.org, Jan 14

Cc: xhw...@chromium.org
Labels: -M-72 -Target-72 M-74 Target-74
Owner: jrumm...@chromium.org
►

Sign in to add a comment