Re: [rtcweb] MTI Video Codec: a novel proposal

"Cavigioli, Chris" <chris.cavigioli@intel.com> Mon, 10 November 2014 18:56 UTC

Return-Path: <chris.cavigioli@intel.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 83ED81A90F3 for <rtcweb@ietfa.amsl.com>; Mon, 10 Nov 2014 10:56:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.495
X-Spam-Level:
X-Spam-Status: No, score=-7.495 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] 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 z5p3a4NbQ_OH for <rtcweb@ietfa.amsl.com>; Mon, 10 Nov 2014 10:56:46 -0800 (PST)
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by ietfa.amsl.com (Postfix) with ESMTP id DE7D51A86E0 for <rtcweb@ietf.org>; Mon, 10 Nov 2014 10:56:44 -0800 (PST)
Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 10 Nov 2014 10:56:18 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.07,354,1413270000"; d="scan'208";a="634616185"
Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by orsmga002.jf.intel.com with ESMTP; 10 Nov 2014 10:56:16 -0800
Received: from fmsmsx117.amr.corp.intel.com (10.18.116.17) by ORSMSX106.amr.corp.intel.com (10.22.225.133) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 10 Nov 2014 10:56:16 -0800
Received: from fmsmsx118.amr.corp.intel.com ([169.254.1.180]) by fmsmsx117.amr.corp.intel.com ([10.18.116.17]) with mapi id 14.03.0195.001; Mon, 10 Nov 2014 10:56:16 -0800
From: "Cavigioli, Chris" <chris.cavigioli@intel.com>
To: cowwoc <cowwoc@bbs.darktech.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] MTI Video Codec: a novel proposal
Thread-Index: AQHP/RP3t1Us8NWOVUi3Mlc5jH+l4pxaM8fA
Date: Mon, 10 Nov 2014 18:56:15 +0000
Message-ID: <E36D1A4AE0B6AA4091F1728D584A6AD2400B2DE3@fmsmsx118.amr.corp.intel.com>
References: <54601E19.8080203@nostrum.com> <6689CD42-C046-45DE-9871-16538A799810@phonefromhere.com> <5460ECFE.4000900@gmail.com> <C1BE48EE-726C-42FC-B6B7-11BEFDD175DE@phonefromhere.com> <54610389.7060103@bbs.darktech.org>
In-Reply-To: <54610389.7060103@bbs.darktech.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.200.106]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/j8CMloVb22gysrOa25hioL10fJ0
Subject: Re: [rtcweb] MTI Video Codec: a novel proposal
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: Mon, 10 Nov 2014 18:56:48 -0000

As a preview of future devices, see this page: http://wiki.webmproject.org/hardware/socs showing several chips (SoCs) supporting full HD VP8 (and H.264) encode AND decode hardware acceleration.
Intel launched phone/tablet platforms at MWC in February that demonstrated hardware WebRTC.  Thus our codec neutrality in this debate.
-chris

-----Original Message-----
From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of cowwoc
Sent: Monday, November 10, 2014 10:27 AM
To: rtcweb@ietf.org
Subject: Re: [rtcweb] MTI Video Codec: a novel proposal

On 10/11/2014 12:40 PM, Tim Panton wrote:
> The realities I'm thinking of are the ones facing someone building a 
> video enabled pet phone (for example). I can get H264 hardware very 
> cheaply (eg a raspberry Pi) and have it communicate with an ios App or 
> firefox on a laptop without any license (as far as I can tell).
> Getting the same setup to work with VP8 will consume significantly 
> more battery power at both ends.
>
> I wish this were not the case, but that's the reality I see.

I was/am under the impression that this reality will change over the coming year as devices roll out with hardware VP8 support.

According to http://wiki.webmproject.org/hardware/devices Raspberry Pi already supports hardware decoding. The assumption is that they are working on hardware encoding in a future release.

Gili

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