Re: [rtcweb] Platforms that support H264 (was: Congratuiations on the Cisco announcement - but we still prefer VP8)

"Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com> Sat, 02 November 2013 22:49 UTC

Return-Path: <jlaurens@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 E888311E8255 for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 15:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.409
X-Spam-Level:
X-Spam-Status: No, score=-10.409 tagged_above=-999 required=5 tests=[AWL=0.189, 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 qyK1tjuU7lbM for <rtcweb@ietfa.amsl.com>; Sat, 2 Nov 2013 15:49:20 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E838611E8105 for <rtcweb@ietf.org>; Sat, 2 Nov 2013 15:49:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8501; q=dns/txt; s=iport; t=1383432560; x=1384642160; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=URqrZMdNa4ZFhwtDSbZhOfgue/jaclPsmgvPUnZ/HZw=; b=WuQVDdqgV20rwYP1DgOpOZ0Ba6crKgB5RqrszEUpeEXOdIGmUTuFUX7g BsZZK9vVBSCp0Kbb+SxDQSgECsKnSay4EO5e/ikZ7zX+BrzdPKUnNpEGh hXKIpnFppdvhv+8mtsTsaH3Te/l0BnLBvAAvyLLr+MBdNUMAlaJ5HPuud A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFADiAdVKtJV2c/2dsb2JhbABZgwc4wAVLgRsWdIIlAQEBAwEBAQFrCwULAgEIDgojBAchBgsUAwENAgQOBYdvAwkGDbMbDYlnBIxogmwEB4MggQ4Dlh+Ba4xShTeBaIE+
X-IronPort-AV: E=Sophos; i="4.93,624,1378857600"; d="scan'208,217"; a="276920437"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 02 Nov 2013 22:49:19 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rA2MnJM5023865 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 2 Nov 2013 22:49:19 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.33]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Sat, 2 Nov 2013 17:49:18 -0500
From: "Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com>
To: Emil Ivov <emcho@jitsi.org>
Thread-Topic: [rtcweb] Platforms that support H264 (was: Congratuiations on the Cisco announcement - but we still prefer VP8)
Thread-Index: AQHO2BkpBk13xO4pgUCS+AgMzHheL5oS2TOA//+yB14=
Date: Sat, 2 Nov 2013 22:48:56 +0000
Message-ID: <AB122953-5A83-4F99-9A02-D257F4E11C19@cisco.com>
References: <CAOqqYVEER_HprgauRawO+_gGdLdMY1MUY8jrMhhi3yVDL31bFg@mail.gmail.com> <52740478.6030109@nostrum.com> <CAOJ7v-2+_4QZwc8vEtdwVDWSP-d-z+ggB0u+VM6WnA=f-k4-XA@mail.gmail.com> <BLU404-EAS261C783EDA4575EE1A7E53593F40@phx.gbl> <52750E3C.9060206@bbs.darktech.org> <CABkgnnVR9=oWVzRaRuD701tvZCtp+SO1n6c65hJELLVfB8QcOA@mail.gmail.com> <C21C6AC2-29F8-4DFF-BB48-5E3D625DCD65@phonefromhere.com> <CAPvvaaK-bKt-zDEq2qibRrm51VbRGAV=95JShKFdCpJszw5Tww@mail.gmail.com> <CABcZeBMG1ApkN7u_uyO_9H9se22ixLhaYc6pZsncvc6d+k8rEQ@mail.gmail.com>, <CAPvvaa+eDRkDk5XNDh2QcgLy4wDjrNeCmGJvqac_z+F4r_ev5Q@mail.gmail.com>
In-Reply-To: <CAPvvaa+eDRkDk5XNDh2QcgLy4wDjrNeCmGJvqac_z+F4r_ev5Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_AB1229535A834F999A02D257F4E11C19ciscocom_"
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Platforms that support H264 (was: Congratuiations on the Cisco announcement - but we still prefer VP8)
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: Sat, 02 Nov 2013 22:49:25 -0000

I don't think this is the case.

The rationale is that H.264 can be accelerated by hardware.
Some rightly question how much this is actually the case natively today.
To Ekr's point, if Cisco works with the top providers to enable true acceleration....
Or in the case of Apple, if ultimate delivery of true h/w acceleration of 264 is ultimately delivered through WebRTC...
Then at least we' have *more* h/w acceleration than we do today

Sent from my iPhone

On Nov 2, 2013, at 6:28 PM, "Emil Ivov" <emcho@jitsi.org<mailto:emcho@jitsi.org>> wrote:


I'd encourage you to read back.

This part of the thread started with the claim that most of the time it won't come to downloading Cisco's binary because there is already widespread OS support for H.264 encoding on all OSes.

--sent from my mobile

On 2 Nov 2013 23:17, "Eric Rescorla" <ekr@rtfm.com<mailto:ekr@rtfm.com>> wrote:
If only there was some piece of software that you could download
that provided H.264 encoders for those platforms.

-Ekr



On Sat, Nov 2, 2013 at 10:14 AM, Emil Ivov <emcho@jitsi.org<mailto:emcho@jitsi.org>> wrote:

Same questions for OS X and Windows actually. Last time we checked (which was also some time ago) there was no way to get the OS to *encode* H.264 for you.

--sent from my mobile

On 2 Nov 2013 17:57, "tim panton" <tim@phonefromhere.com<mailto:tim@phonefromhere.com>> wrote:

On 2 Nov 2013, at 15:02, Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.com>> 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.

Martin, can I ask you to talk with your Skype engineering team and check up on
the exact way that works on iOS. Last time I looked, it seemed you couldn’t use the
Apple supplied (hardware accelerated) h264 library for realtime encode/decode and
it wasn’t at all clear to me that the hardware encoder licence covered any soft implementation of h264 we
added.

I’d like to caveat that:
 1) it was a while ago. 2) I’m not a lawyer. 3) it was a thought experiment.
So it would be interesting to get a current view from the trenches.

T.

_______________________________________________
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