Re: [rtcweb] H.261
Stefan Slivinski <sslivinski@lifesize.com> Sun, 24 November 2013 08:18 UTC
Return-Path: <sslivinski@lifesize.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 404A91AE03B for <rtcweb@ietfa.amsl.com>; Sun, 24 Nov 2013 00:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 1bVytohbLa81 for <rtcweb@ietfa.amsl.com>; Sun, 24 Nov 2013 00:18:06 -0800 (PST)
Received: from na3sys009aog114.obsmtp.com (na3sys009aog114.obsmtp.com [74.125.149.211]) by ietfa.amsl.com (Postfix) with SMTP id E76FB1ADFEC for <rtcweb@ietf.org>; Sun, 24 Nov 2013 00:18:05 -0800 (PST)
Received: from mail1.lifesize.com ([207.114.244.10]) (using TLSv1) by na3sys009aob114.postini.com ([74.125.148.12]) with SMTP ID DSNKUpG2NCFqdNp50LEEQq2BIKQ/YHoyN00G@postini.com; Sun, 24 Nov 2013 00:17:58 PST
Received: from ausmsex00.austin.kmvtechnologies.com ([fe80::edad:d9e3:99d1:8109]) by ausmsex00.austin.kmvtechnologies.com ([fe80::edad:d9e3:99d1:8109%14]) with mapi; Sun, 24 Nov 2013 02:10:32 -0600
From: Stefan Slivinski <sslivinski@lifesize.com>
To: Ron <ron@debian.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Sun, 24 Nov 2013 02:10:30 -0600
Thread-Topic: [rtcweb] H.261
Thread-Index: Ac7o4BmbvmEFNmkISO2UMCfmUphuHQACcv3Q
Message-ID: <7949EED078736C4881C92F656DC6F6C130EA9E677C@ausmsex00.austin.kmvtechnologies.com>
References: <528FBD13.5040801@gmail.com> <528FD429.7090002@nostrum.com> <528FDE5E.5080301@librevideo.org> <CE523335-0146-4FA5-A735-1EB4A8B3F1EF@apple.com> <20131123003548.GD3245@audi.shelbyville.oz> <529006BB.609@nostrum.com> <7949EED078736C4881C92F656DC6F6C130EA9E6760@ausmsex00.austin.kmvtechnologies.com> <529057EB.3060704@bbs.darktech.org> <7949EED078736C4881C92F656DC6F6C130EA9E677A@ausmsex00.austin.kmvtechnologies.com> <CAGgHUiTE31Fes8Dhw5ZttfxhonzyTd_x0Vt-jLh2+C3U+mkVDw@mail.gmail.com> <20131124064011.GK3245@audi.shelbyville.oz>
In-Reply-To: <20131124064011.GK3245@audi.shelbyville.oz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [rtcweb] H.261
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: Sun, 24 Nov 2013 08:18:08 -0000
I'm not suggesting H.261 in software is going to consume less power than H.264 720p in hardware but apples to apples in terms of resolution it's unlikely software is going to come out ahead in very many architectures. It's not about changing the laws of physics, it's about cutting out what you don't need. General purpose instruction sets don't necessarily map well to every algorithm, not to mention these hardware acceleration engines can put lots of on chip memory to limit how often they need to go to external memory, and generally speaking hardware acceleration engines run at much lower clock speeds than their host processors. But don't take my word for it, intel and apple seem to think they saved power: Comparison on hardware codec vs software codec http://software.intel.com/en-us/articles/power-benefits-using-intel-quick-sync-video-h264-codec-with-sorenson-squeeze apple: see: 'Fourth, there's battery life' http://www.apple.com/hotnews/thoughts-on-flash/ -----Original Message----- From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Ron Sent: Saturday, November 23, 2013 10:40 PM To: rtcweb@ietf.org Subject: Re: [rtcweb] H.261 On Sun, Nov 24, 2013 at 08:02:36AM +0200, Leon Geyser wrote: > If we fallback to a software H.261 encoder/decoder then will it really > use so much CPU that devices will be unusable or the battery will > deplete early? No, it won't. You're pretty much certain to get better battery life doing software H.261 than hardware H.264 on all but the most retarded of architectures (ie. something with _no_ powersaving ability at all). And both of them pale into insignificance against the power your display will use. http://www.yosefk.com/blog/its-done-in-hardware-so-its-cheap.html tldr; something that take 100x more operations to perform _still_ takes ~100x more operations to perform, and about the same amount of power, regardless of whether it's run on a "custom processor" (aka 'hardware acceleration') or a general purpose processor (aka CPU). If you want it to actually go faster too, that will generally use MORE power, not less. Ye cannae change the laws o' physics. Nobody who has actually measured this, or understands anything about the details of it peddles this kind of snake oil about hardware accel. > I didn't know that H.261 was so CPU intensive... It's so CPU intensive that it ran on phones from 25 years ago ... So I guess we can add "power saving and longer battery life" to the list of pros for H.261, and reasons someone might deliberately choose to use it, even if other options are available! If we keep thinking, the list just keeps growing :) Ron _______________________________________________ rtcweb mailing list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] H.261 Mo Zanaty (mzanaty)
- Re: [rtcweb] H.261 Leon Geyser
- Re: [rtcweb] H.261 Steve Kann
- Re: [rtcweb] H.261 bryandonnovan
- Re: [rtcweb] H.261 Justin Uberti
- Re: [rtcweb] H.261 Maik Merten
- Re: [rtcweb] H.261 bryandonnovan
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Martin Thomson
- Re: [rtcweb] H.261 Maik Merten
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Maik Merten
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Martin Thomson
- Re: [rtcweb] H.261 Daniel-Constantin Mierla
- Re: [rtcweb] H.261 David Singer
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Eric Rescorla
- Re: [rtcweb] H.261 Basil Mohamed Gohar
- Re: [rtcweb] H.261 Daniel-Constantin Mierla
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Maik Merten
- Re: [rtcweb] H.261 Basil Mohamed Gohar
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Basil Mohamed Gohar
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 David Singer
- Re: [rtcweb] H.261 Basil Mohamed Gohar
- Re: [rtcweb] H.261 David Singer
- Re: [rtcweb] H.261 David Singer
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Lorenzo Miniero
- Re: [rtcweb] H.261 Bjoern Hoehrmann
- Re: [rtcweb] H.261 Steve Kann
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Eric Rescorla
- Re: [rtcweb] H.261 Mo Zanaty (mzanaty)
- [rtcweb] Opinions are fine, bypassing a vote is n… cowwoc
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 Lorenzo Miniero
- Re: [rtcweb] Opinions are fine, bypassing a vote … Eric Rescorla
- Re: [rtcweb] H.261 bryandonnovan
- Re: [rtcweb] Opinions are fine, bypassing a vote … Stefan Slivinski
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] Opinions are fine, bypassing a vote … Ron
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Lorenzo Miniero
- Re: [rtcweb] H.261 Daniel-Constantin Mierla
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Daniel-Constantin Mierla
- Re: [rtcweb] H.261 Eric Rescorla
- Re: [rtcweb] H.261 Daniel-Constantin Mierla
- Re: [rtcweb] H.261 - taking a longer view of thin… Ron
- Re: [rtcweb] H.261 - taking a longer view of thin… Martin Thomson
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 - taking a longer view of thin… Ron
- Re: [rtcweb] H.261 Leon Geyser
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Maik Merten
- Re: [rtcweb] H.261 Florian Weimer
- Re: [rtcweb] H.261 Florian Weimer
- Re: [rtcweb] H.261 - taking a longer view of thin… cowwoc
- Re: [rtcweb] Opinions are fine, bypassing a vote … cowwoc
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 David Singer
- Re: [rtcweb] H.261 - taking a longer view of thin… Ron
- Re: [rtcweb] H.261 - taking a longer view of thin… cowwoc
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Stefan Slivinski
- Re: [rtcweb] H.261 Cullen Jennings (fluffy)
- Re: [rtcweb] H.261 Cullen Jennings (fluffy)
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 Stephan Wenger
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Hrishikesh Kulkarni
- Re: [rtcweb] H.261 Leon Geyser
- Re: [rtcweb] H.261 Hrishikesh Kulkarni
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 Cullen Jennings (fluffy)
- Re: [rtcweb] H.261 tim panton
- Re: [rtcweb] H.261 tim panton
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Stephan Wenger
- Re: [rtcweb] H.261 tim panton
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 Eric Rescorla
- Re: [rtcweb] H.261 tim panton
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 Eric Rescorla
- Re: [rtcweb] H.261 cowwoc
- Re: [rtcweb] H.261 Engel Nyst
- Re: [rtcweb] H.261 Ron
- Re: [rtcweb] H.261 Adam Roach
- Re: [rtcweb] H.261 Basil Mohamed Gohar
- Re: [rtcweb] H.261 Randell Jesup