W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2009

[whatwg] Codecs for <audio> and <video>

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 2 Jul 2009 11:37:03 +1200
Message-ID: <11e306600907011637u6b17db99lb447648a81f82e9d@mail.gmail.com>
On Tue, Jun 30, 2009 at 4:50 PM, Ian Hickson <ian at hixie.ch> wrote:

>  - has off-the-shelf decoder hardware chips available
>

I don't think this should be a requirement.

As written, this requirement primarily means "need to be able to build
devices today that play back with minimal power consumption". Obviously this
is desirable, but why is it *necessary* for a baseline codec? Why would a
vendor refuse to support a format because of high power consumption? It
seems to me that using up power can't be worse than refusing to play the
content at all. Does Apple block iPhone apps because they max out the CPU
while they're running?

It seems to me that this requirement forces HTML5 to merely document the
codec preferences of device vendors. I think HTML5 could be proactive
without being obnoxious, by recommending that Theora be supported wherever
possible. That would encourage the consumption and production of Theora
content, which would increase pressure on device vendors to support it well,
which would increase the chances us all getting a codec with good universal
support.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090702/d17cd586/attachment.htm>
Received on Wednesday, 1 July 2009 16:37:03 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:13 UTC