Google drops the bomb on H.264

Glaucus

Active Member
Member
Joined
Apr 12, 2005
Messages
4,767
Reaction score
697
Google opens VP8 codec, aims to nuke H.264 with WebM

Ever since Google announced its purchase of video codec company On2 in August 2009, there's been an expectation that On2's VP8 codec would someday be open-sourced and promoted as a new, open option for HTML5 video. An open VP8 would offer comparable quality to H.264, but without the patent and royalty encumbrances that codec suffers.

Last month, this speculation seemed confirmed, with inside sources claiming that Google would announce the open-sourcing of the VP8 codec this month at the company's I/O conference.

Today, Google, Mozilla, and Opera announced the launch of the WebM Project. The goal of the project is to develop a high-quality, open-source, royalty-free video format suitable for the Web. WebM video files do indeed use VP8 for their video compression, coupled with Vorbis audio compression. The video and audio data will be combined into container files that are based on the open-source Matroska container.

A host of other companies are also collaborating on the project. Of particular importance are companies like AMD, ARM, NVIDIA, and Qualcomm. Google is working with these companies to get WebM acceleration built into hardware on as broad a range of devices as possible; having a broad range of GPU and embedded CPU manufacturers on board will greatly aid that effort.

Even without hardware acceleration, Google claims that low-end hardware will still perform well with WebM.

Nightly builds of Mozilla and Chromium (the open source project used for development of Chrome) will include WebM support starting today. The Chrome early access release dev channel will include WebM support as of May 24. A beta of Opera with WebM support is also available.

WebM support in Android is expected in Q4 2010, and Broadcom announced today that its motion video acceleration solution for mobile phones, VideoCore, should gain WebM support by Q3 2010.

Adobe is also on board. The company will incorporate WebM support into Flash, and Adobe CTO Kevin Lynch said that the company wants to deliver WebM support to "a billion" users within a year.

Flash support is particularly valuable, as it negates one of H.264's current practical advantages: the same compressed H.264 video can be served to users via both Flash and HTML5 video. This allows sites to target non-Flash devices alongside Flash-enabled ones without having to encode their video files twice.

A browser that supports WebM content isn't much use if there's no WebM content to play, and Google has that covered too. Anyone opting into YouTube's HTML5 front-end will be able to use WebM for video playback by appending "&webm=1" to the URL.

For content creators, patches for the open source FFmpeg encoder/decoder were released today, as were filters for use with Microsoft's DirectShow framework. Installing these filters will enable WebM support in a wide range of audio/video applications on Windows, including Windows Media Player, as well as third-party software such as Media Player Classic.

So pretty much overnight we have browsers that support it and all of YouTube can be in VP8. Hardware acceleration is also on the way. A big win for open source.
 
X264 developer says Google's new VP8 WebM codec is a mess
Despite the unbridled enthusiasm among bloggers for Google's newly announced free WebM codec, a digital video expert has reviewed the new VP8 specification and delivered a severely deflating technical analysis, noting that it decodes video slowly, is buggy, and copies H.264 closely enough to all but guarantee patent issues.

http://www.appleinsider.com/articles/10 ... _mess.html
 
The patent threat is perhaps the big worry and it can keep other companies away. However, it seems that there are many that have already jumped on the bandwagon so that's a good sign. If a patent suit does come along Google is again in a position where it can defend it.
 
Glaucus said:
The patent threat is perhaps the big worry and it can keep other companies away. However, it seems that there are many that have already jumped on the bandwagon so that's a good sign. If a patent suit does come along Google is again in a position where it can defend it.

The guy writing that also noted that there's code in there going back a ways demonstrating that this is an evolution from previous code. There may be some protection in that. There may also be some protection in the fact that most software patents are crap. Google was already able to run over copyright holders "for the greater good", we'll see what they can do here. However, indemnity is what they should be offering. If they are confident in their claim then they should back it up. What they really need to do is either have someone come forward with their patent and then give the patent such a shit kicking that other holders won't go near them, or do effectively the same by scaring off even a single challenge - thus diluting the patents.

But hanging the little guy out there to face the threat alone is bad. The little guy can get beat up easier and that would strengthen the patent holders claims because they'd me more likely to a) afford to litigate, b) able to win. Google already lost an Android phone maker because they wouldn't indemnify.
 
So what would go well with my free WebM video codec? Well, I think I'll order a side of open-source Google web fonts!

Google offers Web designers hosted, open-source Web fonts

Web typography just got a shot in the arm from Google, as the company has announced a free, open-source library of 18 typefaces that Web designers will now have at their disposal. Google hosts all the fonts on its servers, and offers a simple Web-based API that handles all the browser differences behind the scenes. Furthermore, Web font service provider TypeKit has partnered with Google to offer an additional open-source JavaScript library called WebFont Loader for even more control over how fonts are loaded by the browser.

Mmmm... Delicious!
 
Back
Top