Google Acquiring VP3 Developer On2 Technologies 133
R.Mo_Robert writes "BetaNews is reporting that Google is acquiring On2, the video codec company and original developers of the VP3 codec from which Theora is derived. The article suggests that this may mean Google is backing Ogg Theora as the HTML5 video standard, but this is likely not the case--with Theora already being open-source and On2 having disclaimed all rights and patents, there is no reason Google should have needed to do this to push Theora. You may recall from some time back that HTML5 no longer specifies which video codec(s) a browser should support due to there being, unfortunately, no suitable codec at this time. But Google (known for supporting H.264) practically owns Web video with YouTube in most people's minds, so their influence could really swing the future of HTML5 video either way. It remains to be seen whether Google's acquisition of On2 has any bearing on their plans for video on the Web."
VP3 is old (Score:5, Interesting)
Theora was based on one of On2's earliest codecs. VP6 & VP7 have been far more successful and are even used as the Flash video codecs. If Google is acquiring On2, it could mean that they're looking to open up the formats that have defined Flash as the media player of choice.
Re: (Score:2, Interesting)
Except VP7 is way too slow to decode on SIMD processors. The problem isn't the total amount of processing, but the amount of processing that is sequential in nature (ie not SIMDizable). So they didn't notice until they tried to optimise for concurrancy (as found in X86 media extensions as well as most DSPs and low power media processors). By then it was too late - oopsie!
Cue a massive backpedal with VP8 which runs in a little over half the cycles compared to equivilant VP7. See http://www.dspdesignline.com/
Re:VP3 is old (Score:4, Insightful)
Re: (Score:2)
Owning VP7 can't hurt.
How would it help? Google is pretty much entirely dependent on other software to get video content to the user, whether it is Flash, video plugins or the browser alone. Owning the codec means nothing if they can't convince the browsers to implement it. As things stand now VP8 is in an even worse position to be adopted by browsers than either H.264 or Theora.
If they do open it up, with a royalty-free transferable patent license, then it has a pretty good chance. Mozilla's and Opera's problem with H.264 was t
Re: (Score:2)
Discontinuity (Score:2)
As a developer, I can say that Google's product suite is unsettlingly dynamic. There's a new API every week or so, and no asssurance of futures. For example, I was all excited about using Google's JS extensions (with the ability to load/save data locally) but I've yet to see this working anywhere but Windows. Chrome is nice but Windows only, there's now (finally!) a Linux version, but it's so buggy that it often crashes X windows. And now they have their own O/S!? Two?! But which one should I use?
It's a mis
Re: (Score:3, Informative)
As a developer, I can say that Google's product suite is unsettlingly dynamic. There's a new API every week or so,
Yes, new APIs are a serious problem... Sorry, what?!
and no asssurance of futures.
This is different from... what? If Google goes away or (more likely) drops a project, the APIs aren't going to be worth much, but if [company X] goes away or drops a project the same is true. Was there a point in that?
For example, I was all excited about using Google's JS extensions (with the ability to load/save data locally)
That's a standard HTML5 feature now. Bad choice.
but I've yet to see this working anywhere but Windows.
Firefox 3.5.x on all platforms. I believe IE has committed to this or possibly even shipped, but for now you can use gears under IE. Latest Safari also supports HTML5, which is why the Latitude
Re: (Score:2)
"Yes, new APIs are a serious problem... Sorry, what?!"
Think of it like the legal system. Too many fucking laws nobody can be bothered to remember them all.
Too many fucking APIs nobody can be bothered to settle on one implementation, let alone support multiple implementations, let alone remember which API does which, etc., etc.
AGREE ON A FUCKING *STANDARD* AND STICK TO IT.
Re: (Score:2)
"Yes, new APIs are a serious problem... Sorry, what?!"
Think of it like the legal system. Too many fucking laws nobody can be bothered to remember them all.
Too many fucking APIs nobody can be bothered to settle on one implementation
You've gone off the rails. Google's APIs are many and various, but I'm actually not aware of any API that they have that's redundant.
What two APIs are you having to choose between, exactly? The only example I can think of is very much required: Blogger has a full-featured API, but it also offers feed-oriented access through RSS/Atom. A blogging site that didn't offer RSS/Atom wouldn't have many users, so there's nothing they can do there. However, it's not possible to provide a full API within the context o
Re: (Score:2)
Re: (Score:2)
"If an X server crashes, its a bug in the X server"
Re: (Score:3, Informative)
Batman--
You gas a PASS. And the original article gets a FAIL.
I wish they would do a little more research before posting these articles.
This is about taking the codecs in the latest version of Flash and merging them into Chrome/HTML5.
Re: (Score:2)
Exactly: as the submitter of this story, I thought it was odd that BetaNews seems to think it has something to do with Google liking Theora. On2 really has nothing to do with it anymore; they disclaimed and open-sourced VP2 long ago. (If there are any supposed patent issues with Theora, On2 certainly has nothing to do with it.)
What is, of course, more interesting is the relationship of On2's newer formats to Flash...
So what is the reason for this? (Score:2, Redundant)
So can we speculate the reason for Google's action? Let's speculate. I'd like to see what is on minds of slashdotters.
Re:So what is the reason for this? (Score:5, Informative)
No speculation, I submitted this story also, with a quote from Google's Blog:
So it doesn't remain to be seen whether Google's acquisition of On2 has any bearing on their plans for video on the Web.
Re: (Score:2)
...So it doesn't remain to be seen whether Google's acquisition of On2 has any bearing on their plans for video on the Web.
Actually, their blog seems to be pretty vague:
I get that they want to do something with video and the Web...but that really doesn't tell us anything about their future plans, the most interesting one of which could be whether they plan to open any of these formats or
Re:So what is the reason for this? (Score:5, Funny)
"For the same reason we acquire every other company, to try and take over the world!"
Re: (Score:1)
Lots of big companies have already worked out who they need to pay off to use Mpeg4, but are suspicious about Theora because they're worried about patent trolls with all sorts of wacky claims coming out of the woodwork as soon as Theora takes off. Which is particularly difficult for companies that have a history of settling every lawsuit that comes their way rather than spend the money to fight. Apple has specifically announced that they won't support Theora for exactly this reason.
Now, enter Google, a comp
Re: (Score:2)
They are being dishonest about it. There's no bigger danger of such issues with Theora than with their codec of choice.
Re: (Score:2)
One aspect is that Flash 8 adopted VP6. VP6 runs adequately on punier cpus (single threaded 500-800 Mhz or so little cache) like those used by Android compared to H.264 at similar resolutions and bitrates. Another reason is that going forward the licensing for VP6 is going to be free for google compared to using H.264 (there are currently some rates that are essentially 0 for H.264 for those streaming rather than devices but that is set to expire).
One good thing that may come as a side effect of this is tha
Re: (Score:2)
VP6 runs adequately on punier cpus
There is no codec that will run adequately on typical smartphone CPUs of today, VP6 included.
Acceptable video performance requires hardware acceleration.
Hardware for running H.264 is commonly available.
AFAIK there is no commodity hardware available for On2 codecs.
Chrome, HTML5 disaster coming (Score:2, Interesting)
So now Chrome can support only VP6/7 in die tag, Apple does it's quicktime thing, MS does .wmv and Firefox OGG. Hooray!
Honestly, i don't think that would happen, i hope that it may be open sourced and that Android will get some "high quality" video stuff (as far as you can get that on mobile displays).
Re:Chrome, HTML5 disaster coming (Score:5, Insightful)
Chrome supports anything it can legally
Firefox supports anything it can legally
Safari supports anything it can legally
IE tries using only WMV for a little while, then opens up to other formats to slow the exodus.
I could see Google and Apple using their websites to push one codec or another, but I think they want their browsers to be as capable as possible.
Re: (Score:2)
LOL, you might be onto something there.
Re:Chrome, HTML5 disaster coming (Score:5, Informative)
No, apple has stated they have no intention of supporting Ogg.
FTFA
Apple is the only vendor that will not be supporting Ogg.
MS is out of the debate because they will not be supporting <video> at all.
Re: (Score:2, Interesting)
I agree that Chrome and Firefox will support anything they can legally, but I do not think that Safari will implement Theora. Here's my rationale:
Right now, Apple sees Google as a threat, as evidenced by the recent hostility Apple is showing toward Google. Specifically, Apple's blocking of Google Voice and Lattitude on the iPhone. They are "partners" in name only.
This is because the smart people at Apple realize that Google's philosophy of inexpensive lowest bidder open platforms is the antithesis of App
Re: (Score:2, Interesting)
How would a situation that is slightly better than the situation that exists today in any way constitute a disaster?
With the iPhone supporting H.264, plenty of websites are going to follow, and it is reasonably likely that some third party will come up with a shim that enables H.264 in Firefox (using FFMPEG, some derivative of FFMPEG, or maybe Windows internal codecs (if there is support there, I'm not paying attention)).
Google owns YouTube, yes... (Score:1)
But Google (known for supporting H.264) practically owns Web video with YouTube in most people's minds, so their influence could really swing the future of HTML5 video either way.
I'm not so sure. I doubt the vast majority of people who believe Internet Explorer to be the internet noticed that there was some kind of takeover. YouTube owns web video in most people's minds, yes, but it was difficult to tell anything happened even for those who did know what was going on. Even now, the bottom of the page says "© 2009 YouTube, LLC." Either way, I'm waiting for the day when YouTube uses the tag for displaying media and I can finally forget about FLV forever. Long time coming.
An open web standard? (Score:2)
Google has a lot to gain by upgrading or replacing Ogg Theora in order to create a codec which is suitable as a web standard. The biggest item which could get in the way of Android taking off is proprietary video embedding using Flash and (especially) Silverlight.
I hope they pour huge resources into the development of such a standard, and release it as open source. This would not be out of character for Google, based on what they did with Chrome. It would be a benefit for end users, and a competitive gain f
Re: (Score:1)
"We are star stuff."
Yeah, but so are rocks.
Re: (Score:1, Offtopic)
Re: (Score:1)
Cisco anyone? (Score:1)
Google is starting to remind me of Cisco.
For years, Cisco innovated, created, well, MADE really cool things.
Now, they just buy them. I see Google heading that route.
(cue someone saying that Google still innovates, etc. Yeah, I know. So does Cisco. But all their major stuff in the past, oh, I dunno, 5 years at least, has been purchases of other companies making cool stuff.)
Re: (Score:2, Informative)
Sadly, your statement was never true. Everything you think of as from Google was bought except the original Pagerank (obsoleted about a week after they started using it), which is licensed from Stanford. And AdSense, responsible for 99.9999% of their revenues, feeding the rest of the company, was bought and started from work at Brown University.
Please provide evidence for anything you think Google invented in-house.
Re: (Score:2, Interesting)
Gmail? I'd say that's pretty key.
I also didn't say it was a bad thing, it just reminds me of Cisco.
Re: (Score:2)
Webmail has been around a lot longer then Google.
Re: (Score:2)
Just because they didn't invent the components doesn't mean the whole wasn't innovative. Either that, or you have some *really* high standards for innovation!
Re: (Score:2)
Remember when Google announced that they were going to offer a webmail service, with a 1 GB storage quota? Everybody thought it was a hilarious April Fools Day joke, and there was no way Google would do something so ridiculous and implausible. Turns out the joke is that they were serious.
Re: (Score:1, Offtopic)
So from that, yes, Google doesn't innovate at all, and neither does any other company. But Google seems to be pretty friendly toward innovators and seems to be encouraging innovation (like the 20% free time policy, which I've heard led to Google News).
Re: (Score:2)
Which is why I used the term "in-house". The companies are not people thread is down the hall.
Re: (Score:2)
I'm not going to be a Google fanboy and claim they invented everything, but somehow I find it odd that Google would bring in lots of people who had good ideas in the past, and that those people would magically stop hav
Re: (Score:1)
it's the way of things with large companies. They can, and do, innovate. But they also know that there is a lot to be said for whipping out their checkbook.
The important thing with this is that they keep the assets & people of the acquired company. I worked at ANS Communications, which was sold by AOL to Worldcom in the mid 1990's.
ANS had a top-notch team, the best I have ever worked with. It had built the NSFNet (http://en.wikipedia.org/wiki/National_Science_Foundation_Network) more or less from sc
Re: (Score:2)
Google has recently unveiled Google Voice, Android, Chromium, Wave and announced they are making Chrome OS. Purchasing a codec shop doesn't invalidate the fact that Google is still making some awesome products.
Facebook is supposedly the single most popular site on the web right now. And doesn't Microsoft own a big share of Facebook?
Facebook usurped Myspace's spot, and Myspace arguably was the successor to Geocities.
Who could knock Facebook from their perch? Google could with Wave.
Imagine one integrated serv
Re: (Score:2)
Wave can be implemented into other sites, because Google is cool like that. Except I'm sure it will be like their other APIs.
You can post a Google map on your business site if you only get X number of hits. But Facebook couldn't simply implement Wave without paying Google for it. And Microsoft also wouldn't stand for it.
So Orkut will likely be the first (and perhaps only) social network built around Wave. Well, no one you know is on Orkut, which somewhat kills that you say?
Well, when Gmail implements Wave,
Re: (Score:2)
Facebook can easily implement wave without paying Google. They just need to run their own wave server. Wave have been designed with the explicit goal to allow users on different servers(Called federations) to talk to each other as if they were with the same Wave provider.
So facebook just have to develop their own wave server, or compile and install the opensource(bsd style) wave server that google have released.
No suitable codec? (Score:4, Insightful)
That's a bit misleading. There are several suitable codecs. The problem is the major players involved with their "Not Invented Here" mentalities.
Re: (Score:2)
Re:No suitable codec? (Score:5, Insightful)
Actually the problem isn't "NOT Invented Here" it's "Invented Here - please pay us". So Theora doesn't have the quality, but H.264 is patented. Neither is suitable to all interests for those reasons. Those were the leading contenders, others suffer from the same issues. So now that Google owns a good codec, clearly they'll use it. The question is weather they'll let others use it and on what terms. IMHO they should allow anyone to use it for free. Adding yet another proprietary codec to the web would be detrimental, while the upside of codec licensing is probably small potatoes to Google. Freeing a good codec would mean easy access to Google video for everyone and not-as-easy access to MS and Apple.
Re: (Score:2)
Wouldn't Bilski [wikipedia.org] render all of these patents invalid and therefore make this all moot?
Re: (Score:2)
Whatever codec Google chooses for Youtube, then that codec will end up with hardware support. If that is VP8, then there will be hardware decoders for VP8.
The problem *is* quality, H.264 is the best codec by far, the only thing holding it back is it's patent licensing. If VP8 delivers on it's better quality than H.264, then that would be a great thing for video on the Web.
Re:No suitable codec? (Score:4, Insightful)
Well I don't think that's quite right, either. You have to choose between a poorer-quality codec with no hardware support and a widely-supported codec with better quality but requires a licensing fee.
No there wasn't. (Score:3, Informative)
There was no codec that was suitable to all the needs of the major browser developers. Having to pay royalties was an impossibility for Mozilla and Opera, and thus made H.264 (or any of the official MPEG codecs) unsuitable for them. Apple's concern about submarine patents on Theora technology was legitimate, as was the lack of hardware implementation (although that would've been resolved in time). Furthermore, Google's concerns about quality were legitimate if the goal is to move things forward beyond the c
Re: (Score:2)
That doesn't matter. For HTML5 to become a W3C recommendation, it cannot contain licensed technology. There is nothing Opera or Mozilla can do about that.
Uh, no. Flash is not an example of that. Flash is a PLUGIN using a plugin
Re: (Score:2)
The "no suitable codec" blurb is a quote from Hixie [whatwg.org]. I (the submitter) left out the part that qualified this statement with "no suitable codec that all browser vendors are willing to ship," which is more or less what you mentioned. I probably should have mentioned that to make the meaning of "suitable" more clear.
Re: (Score:2)
Re: (Score:2)
In what way is VP8 "highly efficient, even better than h264"? I hope you're not reading their press releases based off of imaginary information.
Used by Youtube (Score:3, Insightful)
They're already buying the milk. Might as well just pay for the cow.
Re:Used by Youtube (Score:4, Informative)
YouTube has never used the VP6 codec.
Re: (Score:2)
What is their flash video encoded to?
Re: (Score:3, Informative)
Sorenson Spark and H.264
Re: (Score:2)
You are quite wrong. In fact "Youtube VP6 HD downloads" is a trumpeted feature in youtube-dl.
Or see: http://www.videos-dl.com/en [videos-dl.com]
Re: (Score:2)
Never heard of videos-dl.com. But it seems they got it wrong. All Youtube HD videos are H.264 encoded.
Re: (Score:2)
The fact that you haven't seen them doesn't change their existence. You also clearly refuse to research the issue at all, since I've provided numerous tips you could easily follow.
Yes, you can find VP6 videos on YouTube. Only a small number have been encoded to that format, compared to Spark and H.264, but they still exist, and you just make an idiot out of yourself repeatedly claiming they do not.
Re: (Score:2)
Numerous tips? You only gave one reference.
Let's see what the streaming and online video expert Dan Rayburn has to say:
http://blog.streamingmedia.com/the_business_of_online_vi/2009/08/debunking-some-more-myths-of-the-googleon2-deal.html
"YouTube has not used VP6 for their videos. They originally started off by using H.263, Spark, and added H.264 support for their HQ and HD videos."
So would you call Dan an idiot, too?
Re: (Score:2)
Yes.
My guesses for why (Score:2)
1. They're getting a good patent portfolio that they can use to defend their investment in YouTube with. They're fairly heavily invested in using ffmpeg which may [ffmpeg.org] have patent issues.
2. They're getting some very smart people and a user base that they can use to help steer the direction of video they way they want it to go.
3. VP7's being used for video chat by Skype and AIM - they might find it useful for their expanding telecommunications offerings.
Google wanted VP8 because it is a great ARM codec (Score:3, Informative)
VP8 was designed to deal with ARM chips and we know that Google Chrome OS will run on ARM chips. Why isn't this being connected in reports? Tech journalists are incompetent.
Re:Google wanted VP8 because it is a great ARM cod (Score:2, Insightful)
But lot's of media oriented ARM platform already got h264 (and other) hardware accelerator...
It will be difficult to beat them with pure software.
Re: (Score:3, Insightful)
Actually, many of those ARM Media-Oriented SoC's (Read: anything from TI, Qualcomm, NVidia, etc...) actually have media DSPs and they're doing the h.264 decode with the DSP core instead of dedicated hardware...
In any case where you see one of the new ARM Cortex-A8/A9 based media chips, you'll be able to implement h.264 or VP3-VP8 in the system with relative ease. Including the iPhone...
On2's modern codec - vp8 (Score:2, Interesting)
FFmpeg support (Score:4, Interesting)
Googled OWNED video (Score:3, Interesting)
YouTube still loses money hand over fist, where as Hulu is growing in revenue and popularity.
It is extremely easy to rip videos from YouTube, which might be a sticking point in YouTube getting more mainstream/commercial content. Frankly, I don't want to see adds for lame user-generated content on YouTube. And I do find most YouTube content lacking. But at the end of the day, if both YouTube and Hulu had say, full Simpsons episodes, I'd rather support Google's site rather than NBC's site.
These developers could perhaps tweak their existing code to develop a closed, DRM-laden codec that would allow YouTube to stream commercial content. And if YouTube doesn't make a move like this, it may just continue to hemorrhage money from here to eternity.
Re: (Score:2)
Actually On2 has a commercial hosting arm.
Re: (Score:2)
YouTube still loses money hand over fist, where as Hulu is growing in revenue and popularity.
There are limits to how much Hulu can grow. Unless they get their international issues sorted they'll never reach the size of audience that youtube has.
Having said that, spreading a few servers around the world or buying content distribution service isn't exactly difficult.
Why Google is doing this (Score:4, Insightful)
Google can now use On2 codecs such as VP8 in YouTube, for free. No more royalties. But the royalties are not that expensive [businessinsider.com] so this isn't likely a big deal for them. (Google could save more money by using smarter settings on their H.264 encoder [xiph.org].)
Do you think Google will seriously try to make money by selling codecs? I don't. $100 million is small change to Google, and if that's all it cost to buy On2, then the On2 revenue stream must be trivial by Google's standards.
So, Google won't save much money and won't make much money by buying On2. I think they are up to something else.
What I think is more interesting is the possibility that Google will give On2's latest technology to the Theora guys. Just as Sun started giving away OpenOffice.org after buying StarOffice, it's likely that Google will give away some or all of the On2 technology.
Despite being based on technology that is nearly a decade old, Theora is already fairly competitive [mozillazine.org] for web video. (Theora is better than H.263, which has actually been used for years, so it's difficult to argue that Theora is not usable for web video.) Now imagine that Theora gets the best technology bits from a modern On2 codec, and integrates those, such that Theora really is as good as H.264, or even better.
Now imagine that this improved Theora is bundled with Google Chrome and Firefox, bundled with Android, and bundled with Google Chrome OS. Within a few years, Theora could become firmly established everywhere as a baseline standard that anyone can use.
Google likes things that make it easier for Google's customers to use Google's services. They like their customers not being locked into proprietary technologies not owned by Google. It will be impossible for Google to take the market away from H.264, but it is very possible that they could make sure their customers can always easily access their services.
Note that this scenario utterly depends on the new Theora being free software. Google could try to sell a proprietary On2 codec and gain a significant market share; well, if they try it, all I can say is "good luck with that." It's hard to push out an established standard; to do it, you need to be significantly better, not just a little bit better. Better technology, with Google behind it, completely free (and with no need to even keep track of how many codecs you ship out) might succeed.
steveha
It's about silicon (Score:2)
such that Theora really is as good as H.264, or even better.
H.264 has a major advantage - implementation in silicon (hardware acceleration).
Google owning On2, and convincing vendors that YouTube on GoogleOS on Google Devices is going to need silicon, providing purchasing commitments, and having the team onboard that knows how to do things like re-write the codec for devices without FPU's can create the necessary momentum to bury the MPEGLA. Steve Jobs did us a short-term favor a few years back on h.264, bu
Re: (Score:2)
I'd argue that's far less of an issue for Theora than people make it out to be. Theora is nearly a decade old, remember, and was quite usable on the now-nearly-decade-old computers. Most modern CPU's - even embedded ones - have got to have more power than my K6-2/300 did, and it decoded Theora video with Vorbis audio just fine.
(That said, I would expect to see a lot more "firmware" decoding to become common using DSP's and FPGA's [I would have sworn the
Re: (Score:3, Interesting)
On2 bought Flix... On2 became the one-stop shop for Flash video encoding.
It's readily apparent that Youtube was and is using Flix for Linux, based on all the capabilities and limitations YouTube encoding shares with the open source MPlayer project (http://multimedia.cx/eggs/poking-at-youtube/), which is used by Flix for Linux (http://support.on2.com/gpl/mplayer/).
It wouldn't be the first time Goo
Question... (Score:3, Insightful)
How is a company that makes video codecs worth $106.5 M? I for one am very confused.
And for God's sake please give me a Slashdot 1.0 theme! I can't take this JavaScript-laden hell.
This is a big money saving move. (Score:2)
106.5 million? Look how little that is compared to the amount of money they'd lose, licensing H.264!
VP8 should give similar results to H.264 as used on Youtube. (Lots of quality enhancing features turned off to speed up encoding)
Somewhat OT: Chrome beta "Even More" section (Score:1, Offtopic)
I was hoping to see a Slashdot article on the latest Chrome beta, but that's probably a bit much. So can someone tell me what they think will show up in the new "Even More" section of the Chrome browser's New Tab screen?
In 3.0.195.4, the thumbnails have been rearranged (2 rows, 4 cols). Along the bottom is "Recent Activities", which includes closed windows/tabs and downloads. And next to that is "Even More". The content of that box is the simple text, "What will we put here?" My guess: targeted adverti
This could be a good thing for web video (Score:2)
If Google are smart, they will open up VP8 and create a new format with OGG container, VP8 video and Vorbis audio. And then use it for YouTube and in Chrome (I dont know how much it costs google to pay royalties on H.264 but it would definatly be more than VP8 would cost them)
Mozilla (FF/SM/etc) would support it if it was free (and if a good decoder was available under a license Mozilla can accept)
Opera would also likely support it if it was free
Microsoft wont be supporting anytime soon (because they want
Re: (Score:2)
Re: (Score:2, Interesting)
But that would be evil.
Re: (Score:1)
Re: (Score:2, Interesting)
Also, maybe the original investors in On2 were smart enough to put non-compete clauses in the contracts of the engineers they hired for their start-up. After all, when you invest millions of dollars in a start-up, you usually want to protect your investment.
-Todd
Re: (Score:2)
Why is buying the company less evil than just hiring the people that work there?
Have you ever been a hiring manager?
Re: (Score:2)
Non-compete clauses [wikipedia.org] are not legally enforceable in the State of California.
Given that fact, please explain why the world changing success of 'Silicon Valley' happened and is still happening in California? Google, Apple, EBay, etc, all seem to be doing just fine without the Non-complete clauses that you refer to.
Re: (Score:2)
Re: (Score:2)
Re: (Score:1)
Re:Google probably wants the engineering taltent. (Score:5, Insightful)
Yeah, it's likely that they want the company's IP, too. Go back and look at the whole HTML 5 and Theora debate. Apparently Google is paying some kind of licensing fee for h264 for both YouTube and Chrome, probably for Android and ChromeOS too if they're providing support. Theora is an open source version of On2's codec that is both old and doesn't have any hardware support.
I don't think it's too much of a stretch to guess that Google wants to open up On2's most recent codecs and try to push other companies to support it. That way they could use the same video formats for all their products without paying additional licensing fees. Plus, they can move YouTube to using HTML5's "video" tag without having to keep a Theora copy to support Firefox/Linux and a h264 copy to support Safari/iPods/iPhones/AppleTVs. Think of what they'll save on transcoding and storage.
Re: (Score:2)
... and they no longer have to pay a fee to On2 for each encoded video if what I hear (that they licensed some custom servers made by On2 for processing videos) is true
Re: (Score:2)
Re: (Score:3, Interesting)
Re: (Score:2)
YouTube lives or dies by Adobe Flash. They want a codec that is as efficient as H.264 that they can open source and get into HTML5. Google says Theora isn't; apparently they think VP8 is.
Except the only reason VP3/Theora is relatively patent-safe is that it's a design mostly based on ideas that date back to the earliest video codecs. I'm not convinced that any newer codec would have the same guarantees; modern codec designers seem to quite like copying bits of h.264 (Real are, IIRC, particularly fond of this).
Re: (Score:2)
VP3 was open sourced. Google open sourcing VP8 will do NOTHING to obviate Apple's supposed concern with submarine patents. Forming a patent-pool around Theora, or any other codec, would (or at least, should).
Re: (Score:2)
Re: (Score:2)
On2 disclaimed their patents to VP3 as well. What I already said continues to apply...
Re: (Score:2)