Re: [rtcweb] There are no legacy WebRTC devices (Was: Comment on Straw Poll replies)

Ron <ron@debian.org> Tue, 14 January 2014 14:50 UTC

Return-Path: <ron@debian.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 035D51AE0E0 for <rtcweb@ietfa.amsl.com>; Tue, 14 Jan 2014 06:50:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIBZp_0uTakU for <rtcweb@ietfa.amsl.com>; Tue, 14 Jan 2014 06:50:54 -0800 (PST)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:7]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4D91AE0DF for <rtcweb@ietf.org>; Tue, 14 Jan 2014 06:50:54 -0800 (PST)
Received: from ppp118-210-34-29.lns20.adl2.internode.on.net (HELO audi.shelbyville.oz) ([118.210.34.29]) by ipmail07.adl2.internode.on.net with ESMTP; 15 Jan 2014 01:20:42 +1030
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id 072164F8F3 for <rtcweb@ietf.org>; Wed, 15 Jan 2014 01:17:08 +1030 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Oyr5k8Mjbqh1 for <rtcweb@ietf.org>; Wed, 15 Jan 2014 01:17:07 +1030 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id 1456B4F902; Wed, 15 Jan 2014 01:17:07 +1030 (CST)
Date: Wed, 15 Jan 2014 01:17:07 +1030
From: Ron <ron@debian.org>
To: rtcweb@ietf.org
Message-ID: <20140114144706.GU3245@audi.shelbyville.oz>
References: <10390_1389365676_52D009AC_10390_2407_1_2842AD9A45C83B44B57635FD4831E60A06CBE540@PEXCVZYM14.corporate.adroot.infra.ftgroup> <52D0222F.4010006@bbs.darktech.org> <949EF20990823C4C85C18D59AA11AD8B112238@FR712WXCHMBA11.zeu.alcatel-lucent.com> <52D42709.1070500@bbs.darktech.org> <949EF20990823C4C85C18D59AA11AD8B113664@FR712WXCHMBA11.zeu.alcatel-lucent.com> <52D4721F.5030204@bbs.darktech.org> <949EF20990823C4C85C18D59AA11AD8B1148DF@FR712WXCHMBA11.zeu.alcatel-lucent.com> <52D49D3E.5090201@bbs.darktech.org> <CABcZeBNrfE76z3X9SYEX1MoysF16+xLu5BnxgYnmQM9kkE98PQ@mail.gmail.com> <52D54680.1090704@bbs.darktech.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <52D54680.1090704@bbs.darktech.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [rtcweb] There are no legacy WebRTC devices (Was: Comment on Straw Poll replies)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 14:50:56 -0000

On Tue, Jan 14, 2014 at 09:15:28AM -0500, cowwoc wrote:
> I stand corrected:
> http://developer.android.com/guide/appendix/media-formats.html
> 
> Both H.264 and VP8 encoder/decoders are supported. Thanks for catching that.
> 
> I'm still curious if anyone has seen a public API for hardware
> encoding/decoding of video outside of Android...

The more interesting question to me would be if someone could give us an
estimate of what proportion of Android devices actually have either ASIC
hardware support for both of these, or sufficiently capable CPUs to do
them in software?

If access to both of these is guaranteed on that platform, then it almost
doesn't matter what the others are doing, if we choose VP8 then we have
support on something like 80% of the mobile device market.[1]

The others will either follow along soon enough, or ...  burn their
platforms I guess.[2]

What am I missing that nobody has pointed this out for us already?

  Cheers,
  Ron


[1]  And most (or all?) of the rest have no support for using the onboard
     acceleration for either case anyway.

[2]  Unless they get a belated interest in H.261 maybe.