Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web
Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web
Posted Jan 26, 2010 21:30 UTC (Tue) by Trelane (guest, #56877)In reply to: Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web by __alex
Parent article: Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web
http://robert.accettura.com/blog/2010/01/21/youtube-html5...
http://robert.accettura.com/blog/2009/07/06/debating-ogg-...
http://weblogs.mozillazine.org/roc/archives/2009/06/direc...
Of particular interest to you is Mozilla Bug 422540,
https://bugzilla.mozilla.org/show_bug.cgi?id=422540
"GStreamer backend for HTML5 video element" which seems well underway.
The gstreamer backend has been a part of the plan from the beginning, see Mozilla bug tagged "video" https://bugzilla.mozilla.org/show_bug.cgi?id=video "Implement WHATWG Video spec"\
So everyone can quit with the grandstanding, mozilla-bashing, and drama queening and get back to work. Synopsis: Using platform-specific media systems will not work, at least because of DirectShow (see the mozillazine link above). To fill the gap, Moz is integrating gstreamer support into Gecko. They can't provide MPEG-LA licensing to downstream users, so they used a patent-free codec for an initial implementation and hoped others would go along with it. In addition, they have been working on gstreamer, in order to support additional codecs. If you want to write an h.264 deocder, then, you can do so and write it for the gstreamer backend. Meanwhile, with GStreamer in place, Dirac and other future Free codecs can also be implemented without as much necessary work.
