Re: [rtcweb] Stephan Wenger's choices

Stephan Wenger <stewe@stewe.org> Tue, 31 December 2013 00:04 UTC

Return-Path: <stewe@stewe.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 E32641AE323 for <rtcweb@ietfa.amsl.com>; Mon, 30 Dec 2013 16:04:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 KD2stuDcKBWz for <rtcweb@ietfa.amsl.com>; Mon, 30 Dec 2013 16:04:12 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0184.outbound.protection.outlook.com [207.46.163.184]) by ietfa.amsl.com (Postfix) with ESMTP id 5B33C1AE32C for <rtcweb@ietf.org>; Mon, 30 Dec 2013 16:04:09 -0800 (PST)
Received: from CO1PR07MB363.namprd07.prod.outlook.com (10.141.75.22) by CO1PR07MB364.namprd07.prod.outlook.com (10.141.75.13) with Microsoft SMTP Server (TLS) id 15.0.842.7; Tue, 31 Dec 2013 00:04:00 +0000
Received: from CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.85]) by CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.85]) with mapi id 15.00.0842.003; Tue, 31 Dec 2013 00:04:00 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Tim Panton <tim@phonefromhere.com>, Eric Rescorla <ekr@rtfm.com>
Thread-Topic: [rtcweb] Stephan Wenger's choices
Thread-Index: AQHPA+47RtR1dzKxFEyEOBCHng6RvZppVMYAgACZgACAAA2ZAIAAIp+AgAAHBACAABSxgIAAA/+AgALM+oCAAAhJAIAAFJwA///BjYA=
Date: Tue, 31 Dec 2013 00:03:59 +0000
Message-ID: <CEE748A8.3E85C%stewe@stewe.org>
In-Reply-To: <C13A4510-0542-43EF-BC60-2DB4D47F5301@phonefromhere.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.174.124.99]
x-forefront-prvs: 00770C4423
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(24454002)(189002)(199002)(83322001)(74876001)(15975445006)(19580395003)(19580405001)(47446002)(47736001)(50986001)(56776001)(74366001)(4396001)(81816001)(54316002)(81686001)(90146001)(65816001)(80022001)(31966008)(74502001)(80976001)(56816005)(59766001)(47976001)(49866001)(74706001)(79102001)(76786001)(76176001)(77982001)(76796001)(15202345003)(85306002)(66066001)(36756003)(81542001)(63696002)(85852003)(83072002)(46102001)(74662001)(16236675002)(69226001)(81342001)(77096001)(54356001)(87266001)(53806001)(76482001)(2656002)(87936001)(51856001)(42262001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR07MB364; H:CO1PR07MB363.namprd07.prod.outlook.com; CLIP:50.174.124.99; FPR:; RD:InfoNoRecords; MX:1; A:0; LANG:en;
Content-Type: multipart/alternative; boundary="_000_CEE748A83E85Cstewesteweorg_"
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Stephan Wenger's choices
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, 31 Dec 2013 00:04:16 -0000

It's well known that many SoCs (including the Broadcom chip used in Raspberry Pi and some Qualcomm chipsets) include hardware acceleration for some of the VPx codecs.  That's not really a surprise as the low level functional blocks of H.264 and VP8 (and also H.263 and some of the older Vpx codecs, so I hear) are quite similar.  It doesn't take the HW folks that much surface and engineering cycles to add support.
It's also well known that those who put the chips into system designs, in their vast majority, do not enable that acceleration for the decoding of VPx.  Your guess is as good as mine why that is so :-)
It's very hard to get your hand on data sheets etc. of the SoCs, unless you are buying hundreds of thousands of them.  Those who obtained them, cannot talk without violating NDAs.
Stephan


From: Tim Panton <tim@phonefromhere.com<mailto:tim@phonefromhere.com>>
Date: Mon, 30 Dec 2013 19:47:26 +0000
To: Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.com>>
Cc: "rtcweb@ietf.org<mailto:rtcweb@ietf.org>" <rtcweb@ietf.org<mailto:rtcweb@ietf.org>>
Subject: Re: [rtcweb] Stephan Wenger's choices


On 30 Dec 2013, at 18:33, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.com>> wrote:

2. Mobile devices on which we want to deploy WebRTC but which can't
afford to run a modern codec in software but could perhaps use HW
support (and perhaps could run some older codec).

...
The second category of elements would benefit from H.264 in the
sense that they would be able to play video or have better battery
life or whatever to the extent to which hardware is available and
usable. The extent to which that's a benefit depends on how often
that will be the case; I realize that a lot of people believe that will
be rare, but the evidence I have seen so far seems pretty
equivocal. Sure, if you think you will never be able to use
HW acceleration for H.264, then this doesn't seem like a very
good argument.

There is a subtle assumption there that hardware assist only applies to H264.
I notice that the raspberryPi gained experimental VP8 support using the video GPU
to accelerate it.
http://www.cnx-software.com/2013/01/26/raspberry-pi-now-has-experimental-support-for-vp6-vp8-mjpeg-and-ogg-theora-video-codecs/

What is especially interesting is that this didn't require any hardware changes,
so it may be that many existing 'H264 only' devices could follow suit if there was
a suitable motivation.

Tim.

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