Re: [rtcweb] Platforms that support H264

"Mo Zanaty (mzanaty)" <mzanaty@cisco.com> Tue, 05 November 2013 08:56 UTC

Return-Path: <mzanaty@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CED511E810D for <rtcweb@ietfa.amsl.com>; Tue, 5 Nov 2013 00:56:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNYyOL4-Bt8y for <rtcweb@ietfa.amsl.com>; Tue, 5 Nov 2013 00:55:59 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id CB9DD21F9E9F for <rtcweb@ietf.org>; Tue, 5 Nov 2013 00:55:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10610; q=dns/txt; s=iport; t=1383641755; x=1384851355; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=DqJTm9PUa9FxWlz7ij5+GJAEWRzrAh4Kas9fw5Doc7c=; b=RFLKLXKmtwJnjAuMrGNti9+ectFfrGEbgulvg0DiMWy5KDz9t1ssVAXS MY+lnD51RFIo4qhgmX4LSQTQ7eapv2u5/CcBOKC5a7MSgo2meM+RaTCSf 84bkzuFMMjuFvz4Rcvxc2MoYPgRBvIJogi183j1TcWrvhSI4mK67p4f1h Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FALaxeFKtJV2a/2dsb2JhbABagkNEOFO+b0uBJRZ0gicBBAEBAWsdAQg/KAYLFBECBAESCQsHh1QDDw20EQ2Ja4xYD4J5hC8Dlh+Ba4xShTeDJoIq
X-IronPort-AV: E=Sophos; i="4.93,638,1378857600"; d="scan'208,217"; a="280818225"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-3.cisco.com with ESMTP; 05 Nov 2013 08:55:53 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rA58trro003174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 08:55:53 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.50]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 02:55:52 -0600
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: cowwoc <cowwoc@bbs.darktech.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Platforms that support H264
Thread-Index: AQHO2gTU0OsOgTLqXE2Wnbsc3UuMdA==
Date: Tue, 5 Nov 2013 08:55:52 +0000
Message-ID: <CE9E0E33.1B9A4%mzanaty@cisco.com>
In-Reply-To: <52788BDC.90109@bbs.darktech.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.82.211.238]
Content-Type: multipart/alternative; boundary="_000_CE9E0E331B9A4mzanatyciscocom_"
MIME-Version: 1.0
Subject: Re: [rtcweb] Platforms that support H264
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Nov 2013 08:56:04 -0000

I’m serious. Name a device in mass production that is relevant to rtcweb but does not have H.264 hardware.

Your second point is valid; hardware is useless without supporting software. OS APIs to access codecs (both hardware and software, real-time and buffered) is an important issue. Android is the dominant OS on the planet. If you are not happy with its OS APIs, just change them; it’s open source like VP8 right?

Mo


On 11/5/13, 1:10 AM, cowwoc <cowwoc@bbs.darktech.org<mailto:cowwoc@bbs.darktech.org>> wrote:


    I'm not sure if you're being sarcastic or not...

    In any case, I had a question regarding BlackBerry 10. Are you implying that every BlackBerry 10 phone includes an API for real-time encoding/decoding of H.264 video streams? If so, which API is it? I took a quick look but couldn't find it.

Thanksm
Gili

On 04/11/2013 9:52 PM, Mo Zanaty (mzanaty) wrote:
I think you meant *every* phone, tablet, laptop, desktop, set-top, camera…


On 11/2/13, 7:41 PM, Kaiduan Xie <kaiduanx@gmail.com<mailto:kaiduanx@gmail.com>> wrote:

Every BlackBerry 10 phone has H.264 hardware encoder/decoder.

/Kaiduan


On Sat, Nov 2, 2013 at 6:18 PM, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.com>> wrote:



On Sat, Nov 2, 2013 at 1:01 PM, Gili <cowwoc@bbs.darktech.org<mailto:cowwoc@bbs.darktech.org>> wrote:
Martin,

    I fully understand why Firefox would be happy but as someone who plan to integrate WebRTC into a non-browser application, especially on iOS, Cisco's solution simply does not work. I appreciate their contribution, but again, it simply doesn't help my use-case.

I haven't seen  you explain how your use case is different from that of
a browser. Could you please do so?

-Ekr

Gili


On 11/2/2013 11:02 AM, Martin Thomson wrote:
On 2 November 2013 07:37, cowwoc <cowwoc@bbs.darktech.org<mailto:cowwoc@bbs.darktech.org>> wrote:
     I can't think of a single platform that supports real-time H.264
encoding/decoding natively today.
That's a very strange way to put the question.

Let me put another spin on it, and please excuse the example...

Skype runs on more platforms than you might think.  Those platforms
can all support H.264 to the extent that Skype requires.

Cisco's generous offer opens almost the same capability to anyone,
with the caveat that some platforms currently remain closed.  Of
course, you could let your ideals get in the way of progress.  Me, I'm
a pragmatist.  This gift represents a great opportunity for people who
actually care about the practical outcomes.

There's been a lot of mouth-gazing of gift horses on this list of
late.  I sure hope that this isn't representative of the real
sentiment of the community.  I'd like to think that people are better
than that.

(BTW, I understand and respect Harald's position.  From where he sits,
I'm sure that his conclusion makes perfect sense.)

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb


_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb





_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>https://www.ietf.org/mailman/listinfo/rtcweb