<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [whatwg] The issue of interoperability of the
<video></title></head><body>
<div>At 22:55 +1200 27/06/07, Robert O'Callahan wrote:</div>
<blockquote type="cite" cite>On 6/27/07,<b> Nicholas Shanks</b> <<a
href="mailto:contact@nickshanks.com">contact@nickshanks.com</a>>
wrote:<br>
<blockquote>On 27 Jun 2007, at 09:28, Maik Merten wrote:<br>
> Browsers don't rely on the OS to decode JPEG or PNG or GIF
either<br>
<br>
In my experience that seems to be exactly what they do do-rely on
the<br>
OS to provide image decoding (as with other AV media).<br>
I say this because changes that had occurred in the OS (such as<br>
adding JPEG-2000 support) are immediately picked up by my
browsers.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
You do not know what you are talking about. Firefox does not use OS
image decoders.<br>
</blockquote>
<blockquote type="cite" cite><br>
<blockquote>likely to be slower and buggier than the free decoding<br>
component written by the codec vendor themselves<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
We use official Ogg Theora libraries.<br>
</blockquote>
<blockquote type="cite" cite><br>
<blockquote>and detracts from the time available for implementing
other browser changes.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>No-one's suggesting reimplementing
codecs. We're talking about integrating existing codecs into the
browser, and shipping them with the browser.</blockquote>
<div><br></div>
<div>I'm not sure where this discussion is going.
However...</div>
<div><br></div>
<div>clearly a browser vendor is free to include audio and video
functionality in the browser if it wishes. However, this is
generally a little more complex than image codecs, in that container
(file) formats, synchronization of media streams, and extensibility at
the format and codec level, are ideally addressed somehow. Media
frameworks tend to do these things (libavcodec, Windows Media,
QuickTime). </div>
<div><br></div>
<div>In the mobile world, using resident codecs can give power-usage
advantages, in that they have sometimes been carefully optimized
(sometimes with hardware assist) by the platform developer.</div>
<div><br></div>
<div>Nonetheless, the browser could do this, or use a hybrid approach,
or be fixed in function for a specified environment. It's really
irrelevant to the spec. (which is what we are working on).</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div>David Singer<br>
Apple/QuickTime</div>
</body>
</html>