4 ms·
This isn't HTML5 marketing, and proprietary and open are not polar opposites. HTML5 offers a new "video" tag syntax that doesn't specify what file container (t
by Terretta 17y ago
This isn't HTML5 marketing, and proprietary and open are not polar opposites.
HTML5 offers a new "video" tag syntax that doesn't specify what file container (think .flv or .mp4) or codec (think VP6 or H.264) must be able to be played by that video tag.
Flash Player, Windows Media Player, QuickTime Player, and the like, are multimedia playback technologies that can be embedded in a web page using an object or embed tag, each with its own complicated syntax the web browser can try to support. The HTML5 video tag is intended to replace that generic object embed syntax with something more rationally video-specific.
Meanwhile, H.264 is a compression algorithm specification, like MPEG4, VC-1, or VP6.
Flash Player used to decode and playback On2's proprietary VP6 codec, which only a couple vendors were licensed to support. That was not "open" at all.
At present, Microsoft's IE9, Google's Chrome, and Apple's Safari play back H.264-encoded video through the video tag, and Adobe plays back H.264 encoded video in its recent Flash Players. These companies famously compete, yet all are supporting the same video compression specification, suggesting it's documented enough and licensed enough to freely support.
Having to generate an Ogg file containing Theora encoded video to make the HTML5 video tag work across the major browsers is a throwback to the days of having to generate a RealMedia, Windows Media, and QuickTime file. Web video needs to pick a format so the whole ecosystem can optimize around it.
- smackfu 17y agoNot specifying any common required video codec was a real failure by the working group. What good is a standardized video tag if the actual contents can be random? http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-June/020620.html http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-Jun...