IETF Logo Mail Archive

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

Steve McFarlin <steve@tokbox.com> Tue, 14 January 2014 18:00 UTC

Return-Path: <steve@tokbox.com>
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 C44411ADF28 for <rtcweb@ietfa.amsl.com>; Tue, 14 Jan 2014 10:00:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 W6CPYjpTXrRt for <rtcweb@ietfa.amsl.com>; Tue, 14 Jan 2014 10:00:38 -0800 (PST)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA6D1AE153 for <rtcweb@ietf.org>; Tue, 14 Jan 2014 10:00:37 -0800 (PST)
Received: by mail-pa0-f54.google.com with SMTP id fa1so2482376pad.27 for <rtcweb@ietf.org>; Tue, 14 Jan 2014 10:00:26 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=x5Jt7IuwFsuoQQ6K3pH1ZxjrUcCNdi7+CMs+IVBjAxo=; b=grknLIQ7BwsgYaglQ6UwDcfDSuJvSy0E1AWx+KgI+6BxdUnaailVwtgcawNUcibH9/ PbpnUt5sF0CDB4WDYHVl9OcR/2OS8Zc3iQP7GnzRV5oAlmkTcYFDsYFAO9BpyRfmHZF1 /7iM4v/PC2vbyZwmU3LD0TtwMEnlarieeIDcWtqEt+wAR77Ss2aHymdNm3grqWmb4a4+ La7YuTwNsp1Y9zjO8bxCH7+QpMtYFNG6EwFtUfuS+vA7iwP7Qvsbzgx4lAEXjRmQOf5B eeXrSX/Nt9PQme6id2HcKf1e8qDWv+1u1navYm2kkXCXBjLFqUcumQR7+cO8aPx2SDIf /B7Q==
X-Gm-Message-State: ALoCoQlorEHS5bbpfUFxTK4cT6NcyXHX7CIQrq+YfVj3PmAX/fIpHbnjmKc/KpnC8HL0lZkYA7GV
X-Received: by 10.68.211.1 with SMTP id my1mr3296690pbc.55.1389722426685; Tue, 14 Jan 2014 10:00:26 -0800 (PST)
Received: from steves-mbp-2.tokbox.com ([216.38.134.120]) by mx.google.com with ESMTPSA id os1sm3298439pac.20.2014.01.14.10.00.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Jan 2014 10:00:25 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_23DA9EAC-97D0-4A62-8D0D-54E9D2BE29F5"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Steve McFarlin <steve@tokbox.com>
In-Reply-To: <52D54680.1090704@bbs.darktech.org>
Date: Tue, 14 Jan 2014 10:00:23 -0800
Message-Id: <E4B95457-FB76-4141-AE1E-FD45243A8662@tokbox.com>
References: <CAHp8n2kq+_uG=9XwoAGtRgqYU2Asc2Fv6RZ0aCW6cJi-LnhD+A@mail.gmail.com> <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>
To: cowwoc <cowwoc@bbs.darktech.org>
X-Mailer: Apple Mail (2.1827)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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 18:00:39 -0000

It looks like Blackberry has API’s for H.264 encoding/decoding [1], and windows phone also looks like it may have API’s (I don’t have enough time to really look) [2]. 


[1] http://developer.blackberry.com/native/reference/core/com.qnx.doc.camera.lib_ref/topic/manual/camera_h264avc.h_enums_overview.html

[2] http://msdn.microsoft.com/en-us/library/windowsphone/develop/windows.phone.media.capture.h264encoderprofile(v=vs.105).aspx


On Jan 14, 2014, at 6:15 AM, cowwoc <cowwoc@bbs.darktech.org> 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...
> 
> Gili
> 
> On 13/01/2014 11:04 PM, Eric Rescorla wrote:
>> On Mon, Jan 13, 2014 at 6:13 PM, cowwoc <cowwoc@bbs.darktech.org> wrote:
>>> To date, Android is the only operating system that I've come across which
>>> exposes a public API for hardware video encoding/decoding, but it only
>>> supports hardware encoding for VP8.
>> Can you please provide a reference for this claim? That does not match
>> my understanding.
>> 
>> -Ekr
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email