Home > slashdot > The Ambiguity of “Open” and VP8 Vs. H.264

The Ambiguity of “Open” and VP8 Vs. H.264

January 17th, 2011 01:37 admin Leave a comment Go to comments

An anonymous reader writes “With all the talk about WebM and H.264, how the move might be a step backwards for openness, and Google’s intention to add ‘plugins’ for IE9 and Safari to support WebM, this article attempts to clear misconceptions about the VP8 and H.264 codecs and how browsers render video. Firefox, Opera and Google rely on their own media frameworks to decode video, whereas IE9 and Safari will hand over video processing to the operating system (Windows Media Player or QuickTime), the need for the web to establish a baseline codec for encoding videos, and how the Flash player is proprietary, but implementation and usage remain royalty free.”

Source: The Ambiguity of “Open” and VP8 Vs. H.264

Related Articles:

  1. Google To Push WebM With IE9, Safari Plugins
  2. So Much For Standards, Google Says WebM Plugins Coming Soon For Safari And IE9
  3. Breaking Open the Video Frontier, Despite MPEG-LA
  4. Microsoft Offers H.264 Plug-in For Google Chrome
  5. Google WebM Calls “Open Source” Into Question
blog comments powered by Disqus