Slashdot Mirror
The Ambiguity of "Open" and VP8 Vs. H.264
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."
Well I learned something new. Perhaps "liberated" would be a better term since the software, like Seamonkey, Songbird, OpenOffice.org, have been liberated from the clutches of single companies (i.e. Microsoft).
Google also has a WebP standard based on VP8, to replace GIFs/JPEGs, but it seems like it's reached a deadend. So WebM is the container.
--- VP8 is the video
--- Vorbis is the audio
Versus h.264:
--- MPEG4 AVC for video
--- plus some audio codec, like MP3 or AAC or HE-AAC
MPEG4/h264 vs. VP8 comparison (h264 slightly better - specially on low bitrate connections):
- http://compression.ru/video/codec_comparison/h264_2010/vp8_vs_h264.html
HE-AACplus vs. Vorbis (HE-AAC wins):
- http://listening-tests.hydrogenaudio.org/sebastian/mf-48-1/results.htm
JPEG vs. WebP (WebP wins):
- http://englishhard.com/2010/10/01/real-world-analysis-of-googles-webp-versus-jpg/
"I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
Ok I'll come clean I havent RTFA, but it strikes me weird that a 15 year old is going to grasp all sides commercial and technological nuances of a very complex issue.
Anyone else feel the same way?