Slashdot Mirror


Google Acquiring VP3 Developer On2 Technologies

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."

133 comments

  1. VP3 is old by AKAImBatman · · Score: 4, 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.

    1. Re:VP3 is old by Anonymous Coward · · 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/showArticle.jhtml?articleID=214303691

      This caused plenty of problems for vendors who tried to support VP7 - often making embarissingly optimistic performance promises based soley on On2's press releases. Oops again!

    2. Re:VP3 is old by FooAtWFU · · Score: 3, Insightful

      Even if they don't want to open them up, you can imagine that they'd rather not be utterly dependent on Adobe Flash to deliver their YouTube content. Owning VP7 (and VP8/VP9/VP1234567 and whatnot) can't hurt.

      --
      The World Wide Web is dying. Soon, we shall have only the Internet.
    3. Re:VP3 is old by BlueBoxSW.com · · Score: 2, 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.

    4. Re:VP3 is old by pavon · · Score: 1

      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 that it was impossible for them to pay patent licenses for each copy they distributed. An opened up VP8 would not have that problem. One of Apple's problem with Theora is that they weren't confident that there were no patent liabilities. Since On2 has been commercially licensing it's codecs for a while now, and no-one else has sued for patent royalties, it is on a bit firmer ground than Theora in that regard. Apple's other problem was that there weren't any hardware implementations of Theora. AFAIK, VP8 doesn't either, although there were(are?) VP6 decoders so maybe On2 has some products in development that they haven't announced yet.

      My biggest question is whether On2 holds all the patents for the VP* codecs or whether they are cross-licensing various patents from other folks that apply to many other codecs like VC-1 and H.264. If that is the case then Google will have a very difficult time opening up the On2 codecs any more than the various MPEG codecs already are.

    5. Re:VP3 is old by Anonymous Coward · · Score: 1, Insightful

      I would imagine the overhead costs to run YouTube are pretty much related to the amount of storage and bandwidth required to deliver streaming videos. Reduce either of those, and you reduce the cost of running YouTube.

      Maybe it was cheaper to buy the company and control where it puts its efforts than to wait for something "magical" to happen.

    6. Re:VP3 is old by R.Mo_Robert · · Score: 1

      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...

      --
      R.Mo
    7. Re:VP3 is old by TheRaven64 · · Score: 1

      Google makes a browser. Google employs a load of software engineers. It would be trivial for them to integrate VP6 (for example) into Chrome for the video tag and provide plugins for other browsers (On2 already makes DirectShow and QuickTime plugins, which will be used by IE and Safari). If you want high quality YouTube pictures, you have to use Chrome or install the plugin. And, if you're downloading and installing software anyway, why not try Chrome?

      --
      I am TheRaven on Soylent News
    8. Re:VP3 is old by Anonymous Coward · · Score: 0

      Batman--

      You gas a PASS.

      Yoda-- so what if he farted. He's Batman.

  2. Google probably wants the engineering taltent. by bezenek · · Score: 0

    -Todd

    --
    Omne ignotum pro magnifico.
    1. Re:Google probably wants the engineering taltent. by cryfreedomlove · · Score: 1

      For $100 million dollars? That's what Google paid for On2. Why not just poach the people directly and let On2 die? That would be a lot cheaper for Google.

    2. Re:Google probably wants the engineering taltent. by geekoid · · Score: 1, Interesting

      But that would be evil.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    3. Re:Google probably wants the engineering taltent. by cryfreedomlove · · Score: 0

      Really? Why?

    4. Re:Google probably wants the engineering taltent. by bezenek · · Score: 2, Interesting

      The non-evil, best way to acquire this talent is to buy the company. Sometimes this is not possible because the company has many other assets which make it expensive. This should not be the case with On2.

      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

      --
      Omne ignotum pro magnifico.
    5. Re:Google probably wants the engineering taltent. by Anonymous Coward · · Score: 0

      Thank god I live in a country where non-compete clauses aren't legal. I cannot imagine how much that must create havoc in the startup scene.

    6. Re:Google probably wants the engineering taltent. by Desler · · Score: 1

      Because they probably also want On2's patent portfolio and trade secrets as well as the people.

    7. Re:Google probably wants the engineering taltent. by nine-times · · 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.

    8. Re:Google probably wants the engineering taltent. by n8_f · · Score: 2, Interesting

      That's a bonus. They want the IP. 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. Then they can start pushing people towards HTML5 browsers. I bet they could get a lot of YouTube visitors to upgrade if it meant they could watch clips in HD versus the quality you see now with Flash.

    9. Re:Google probably wants the engineering taltent. by mariushm · · Score: 1

      ... 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

    10. Re:Google probably wants the engineering taltent. by makomk · · Score: 1

      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).

    11. Re:Google probably wants the engineering taltent. by cryfreedomlove · · Score: 1

      Todd,

      Why is buying the company less evil than just hiring the people that work there?

      Have you ever been a hiring manager?

    12. Re:Google probably wants the engineering taltent. by bezenek · · Score: 1

      I have not been a hiring manager, but I have worked with many people who have been. Although, I think this is more of a topic for HR and company lawyers.

      Engineers are considered (or at least they were at one time) an asset, and companies protect this asset in several ways:

      1. They restrict people from working for a direct competitor for some period of time after leaving a company.

      2. They restrict people from hiring co-workers away from a company from which they have recently left.

      3. Leaking information about the people who work for a company can be grounds for termination.

      If you are unfamiliar with these issues, perhaps you have never been in a position which makes you not easily replaceable. Some of the least replaceable people are analog and VLSI circuit designers (which I am not).

      -Todd

      --
      Omne ignotum pro magnifico.
    13. Re:Google probably wants the engineering taltent. by cryfreedomlove · · Score: 1

      Todd,

      Non-compete clauses 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.

    14. Re:Google probably wants the engineering taltent. by bezenek · · Score: 1

      You are correct. I guess when professors I know at a top-10 school are not allowed to consult for company B because they have consulted for company A in the past, this is not related.

      Also, when Intel goes to court to keep one of their engineers from working for AMD, this is not related.

      I believe IBM often participates in this sort of court battle.

      But, all of this is off topic. If you want to get a team that works on a certain type of technology and does it well, the best way is to find a team that has been doing it. Hiring that entire team away from a company without the companies blessing may be legal, but it is not the sort of thing that wins praise outside of the boardroom or a shareholder's meeting.

      Purchasing a company outright is the best way to take control of the technology and get a set of already-trained engineers.

      Perhaps someone who knows someone at Google or On2 can confirm whether or not Google wanted the engineers or just the IP. Then we can quit arguing about this issue.

      -Todd

      --
      Omne ignotum pro magnifico.
    15. Re:Google probably wants the engineering taltent. by TheRaven64 · · Score: 1

      Not to mention, when you get the company, you get all of the code that the people have been working on. Even without non-compete clauses, it's very difficult legally to get people to work on a very similar product because they can easily write something derived from code that they did as work-for-hire at their previous job, opening you up to lawsuits for copyright infringement. If you're in the USA, their former employer may also have files patents relating to the stuff they were working on. By buying the company, you get the code, the patents, and the people. The people are the most important part, but with the code and the patents they can immediately start working at full speed, while without them they may need to spend a long time working around and duplicating old code.

      --
      I am TheRaven on Soylent News
    16. Re:Google probably wants the engineering taltent. by cryfreedomlove · · Score: 1

      Todd poaching people to come work at a company is mutually agreed to by both the hiring company and the the employee. Every participant in the transaction can enter into the transaction or not according to their free will. Why do you persist in maligning that? Should you or I be slaves to the first company that employs us?

    17. Re:Google probably wants the engineering taltent. by TheRaven64 · · Score: 1

      I was suggesting in the previous articles that Google, Apple, and Mozilla corp should jointly approach the MPEG-LA and offer to buy the H.264 patents outright. Buying On2 is probably cheaper, however I wouldn't be surprised if their newer codecs contain algorithms that other people have patented (e.g. Microsoft) which are covered by cross-licensing deals. This would make it impossible for Mozilla to support them, but still make it possible for Apple, Google, and Microsoft.

      --
      I am TheRaven on Soylent News
    18. Re:Google probably wants the engineering taltent. by bezenek · · Score: 1

      Yes. If I am an expert in branch prediction and I work for Intel on their branch predictor (which was one of their most-guarded secrets when I worked for Intel Labs), then if AMD hires me, I am going to have a hard time working on AMD's branch predictor.

      Now, if AMD wants to hire me to work on something different from branch prediction, fine.

      I do not think Google is going to ask the On2 engineers to work on anything other than CODECs, as least at first.

      -Todd

      --
      Omne ignotum pro magnifico.
    19. Re:Google probably wants the engineering taltent. by cowbud · · Score: 1

      For the uninformed a quick google on non-compete for the state of California reveals, they are illegal: http://www.google.com/search?q=non-compete+california&ie=utf-8&oe=utf-8&lr=lang_en

    20. Re:Google probably wants the engineering taltent. by evilviper · · Score: 1

      They want a codec that is as efficient as H.264 that they can open source and get into HTML5.

      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).

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    21. Re:Google probably wants the engineering taltent. by n8_f · · Score: 1

      Perhaps "open sourcing" was an imprecise choice of words. Obviously part of that would be royalty-free licensing of the patents on VP8. Presumably Google now owns most or all of those; any they don't they can either acquire or get a license that allows anyone to use it. The point is that Google doesn't care about making money off of licensing the codec; what they want is something open that has virtually no barrier to entry, everyone can use, and is widely available on clients. Just like with browsers and OSes, they view this as the platform for their advertising and they want as many users as possible.

    22. Re:Google probably wants the engineering taltent. by evilviper · · Score: 1

      Obviously part of that would be royalty-free licensing of the patents on VP8.

      On2 disclaimed their patents to VP3 as well. What I already said continues to apply...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  3. So what is the reason for this? by bogaboga · · Score: 1, 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.

    1. Re:So what is the reason for this? by Neon+Spiral+Injector · · Score: 5, Informative

      No speculation, I submitted this story also, with a quote from Google's Blog:

      Because we spend a lot of time working to make the overall web experience better for users, we think that video compression technology should be a part of the web platform. To that end, we're happy to announce today that we've signed a deal to acquire On2 Technologies, a leading creator of high-quality video compression technology.

      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.

    2. Re:So what is the reason for this? by 0racle · · Score: 4, Funny

      "Why are we going to acquire this company Google?"

      "For the same reason we acquire every other company, to try and take over the world!"

      --
      "I use a Mac because I'm just better than you are."
    3. Re:So what is the reason for this? by NoCowardsHere · · 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 company with a history of standing up to bad lawsuits and consumer rights, who has just come forward and put a big target on their head. Nobody wants to sue Google, at least not unless they know they've got a really great case, because they know that Google isn't gonna settle. If Google starts pushing Theora advocacy hard, starts using it heavily, and nobody sues them, other companies are likely to be comforted and will be much more likely to follow suit.

      That's my theory. Though I've gotta say, I could also see them opening up some of On2's newer codecs. I didn't know about those.

    4. Re:So what is the reason for this? by mzs · · Score: 1

      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 that there was some lawyer writing letters to libavcodec from On2 about patent infringement and what not regarding VP6/7. Maybe google will make some assurances about putting an end to that sort of behavior.

    5. Re:So what is the reason for this? by R.Mo_Robert · · Score: 1

      ...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:

      Although we're not in a position to discuss specific product plans until after the deal closes, we are committed to innovation in video quality on the web, and we believe that On2 Technologies' team and technology will help us further that goal.

      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 push for any in HTML 5. (If anyone has the power to do this, it's Google with YouTube. Whatever YouTube chooses, browsers must support to keep users happy.)

      --
      R.Mo
    6. Re:So what is the reason for this? by mad.frog · · Score: 1

      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.

    7. Re:So what is the reason for this? by pslam · · Score: 1
      You can decode H.264, MPEG4, WMV and most similar codecs at QVGA (320x240) in about 300MHz of ARM-9, purely in software. That's well within the reach of most mid and high-end smartphones. This isn't speculation, I've done the above.

      It doesn't matter if there's no commodity hardware support for a codec - it'll run just fine in software anyway.

    8. Re:So what is the reason for this? by hkmwbz · · Score: 1

      Apple has specifically announced that they won't support Theora for exactly this reason.

      They are being dishonest about it. There's no bigger danger of such issues with Theora than with their codec of choice.

      --
      Clever signature text goes here.
  4. Chrome, HTML5 disaster coming by FlashBuster3000 · · 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).

    1. Re:Chrome, HTML5 disaster coming by Shatrat · · Score: 4, Insightful
      I would predict:
      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.

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    2. Re:Chrome, HTML5 disaster coming by clone53421 · · Score: 1

      LOL, you might be onto something there.

      --
      Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
    3. Re:Chrome, HTML5 disaster coming by maxume · · 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)).

      --
      Nerd rage is the funniest rage.
    4. Re:Chrome, HTML5 disaster coming by ianare · · Score: 4, 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.

    5. Re:Chrome, HTML5 disaster coming by seizurebattlerobot · · 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 Apple's closed, locked down, and tightly controlled vision for the future. Internally, Apple attributes their closed platform philosophy for their current successes. They realize also that trouble for Google is good for Apple.

      The backdrop for all this is the entire telecommunications industry on the verge of a paradigm shift. A growing number of people are foregoing landlines for owning cell phones only. Cell phones themselves have become ubiquitous. Cell phone lag, audio compression artifacts, and frequent drop outs have reduced the phone service expectations of the general public to a point that modern voice over IP, with a modern internet connection is a valid competitor in the phone service arena.

      Today's smart phones are basically VOIP clients on a proprietary, closed network (the phone carrier's network), with access to a larger, also closed, network (the international telephone system). Carriers profit tremendously from the closed nature of the network. Byte for byte, a data feed to the moon is cheaper than the text messages on most phone carrier networks. Apple also profits from this closed arrangement via its iPhone exclusivity deal with AT&T, who pays them handsomely for the privilege.

      Google aims to open the phone network by implementing its functionality using open Internet based protocols. Google Talk will replace SMS messages and traditional phone calls. Other Google services will be tied in for a richer communications experience than what the telephone networks can provide on their own. Eventually, any phone with Internet connectivity will be able to use Google's services. Once this happens, the phone networks will be mere data providers for an open network, instead of gatekeepers of a closed network. This will drive down prices, telco profits, and the cost of accessing Google's services. Apple will have lost a source of revenue, as networks will not be able to afford to pay them for exclusivity.

      Apple pays lip service to open source philosophies when it benefits them, but have no intentions to further these philosophies or their influence. By this, I mean that they love being able to use the work of others, and will contribute back to open source projects they've used (BSD, KHTML, etc.), but it will be a cold day in hell before we ever see an open source version of iTunes because they do not believe in the ideology. Apple is committed internally to the closed platform vision of the future, where they are the sole gatekeeper. Open formats and standards are a threat to the dominance of the gatekeeper model that Apple is committed to. This is also why we'll never see official support for FLAC, Ogg, Theora, Matroska, or any other open codec in iTunes, Safari, or iPhoneOS.

    6. Re:Chrome, HTML5 disaster coming by Anonymous Coward · · Score: 0

      Chrome 3 already supports OGG and mp4 in <video>. It's unlikely they will backpedal on that, and even if they do, hey, it's open source. (They didn't include the codecs in Chromium for some legal reason, but on Windows it's just a matter of copying three DLL files.)

      IE will support HTML5... in 2022. Or 2222.

    7. Re:Chrome, HTML5 disaster coming by badkarmadayaccount · · Score: 1

      Mod parent up.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  5. Google owns YouTube, yes... by cnvandev · · 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.

  6. An open web standard? by CopaceticOpus · · Score: 1

    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 for Google.

    1. Re:An open web standard? by geekoid · · Score: 0

      "We are star stuff."

      Yeah, but so are rocks.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:An open web standard? by oodaloop · · Score: 0, Offtopic

      I thought that was kinda the point. Like, all we, and everything, is is star stuff, and not the special created-by-god things some people say. Just self-organized star matter, like rocks and such.

      --
      Tic-Tac-Toe, Global Thermonuclear War, and relationships all have the same winning move.
    3. Re:An open web standard? by Lostlander · · Score: 0

      It is sort of see: http://www.imdb.com/title/tt0105946/quote for the origin of that quote.

  7. Cisco anyone? by Em+Emalb · · 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.)

    --
    Sent from your iPad.
    1. Re:Cisco anyone? by Anonymous Coward · · Score: 0

      So what? As long as cool stuff keeps being made, it doesn't matter who owns it. Unless it's Disney, and they lock it away for decades.

    2. Re:Cisco anyone? by Duncan3 · · Score: 1, 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.

      --
      - Adam L. Beberg - The Cosm Project - http://www.mithral.com/
    3. Re:Cisco anyone? by danpritts · · 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 scratch, and after the Internet commercialized it was one of the best tier-1 ISPs. (internal slogan: we suck less)

      Worldcom let us wither on the vine. They did basically nothing to integrate us into the business, and ignored the talent we had. Folks drifted away. It's probably true that they bought us not for our staff, but because we came with a contract to run AOL's dial business; however, it was negligent of WCOM to ignore the rest of the quality asset they'd purchased.

      OTOH i've heard stories of companies being acquired by cisco. cisco knows how to do it right; they pay attention to what they are buying. They integrate the staff and put them to work on something useful.

      on a related note, I've got a friend who works for IBM who says that his best shot at a "promotion" (from a high to a very high level) is not to do something inside IBM, but to go to a startup, and get acquired by IBM.

    4. Re:Cisco anyone? by Em+Emalb · · 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.

      --
      Sent from your iPad.
    5. Re:Cisco anyone? by ChrisMounce · · Score: 0, Offtopic

      People innovate, not companies -- a company is just an abstract legal construct. And innovative people are "bought" with high salaries and environments which accept their innovation.

      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).

    6. Re:Cisco anyone? by Enderandrew · · Score: 1

      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 service that allowed you to really create content, easily upload your content, and share it. Wave is also built around collaboration. Myspace allows you to customize your page, but you have to know HTML. Facebook won't let you customize your page. Wave could be Facebook mixed with Youtube, mixed with Myspace, mixed with Flickr, mixed with Office Live. Except it would be better, and completely free.

      Seriously, don't sell Google short with Wave. I really think that if and when Google started to push it, it could become the biggest thing on the web.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    7. Re:Cisco anyone? by Anonymous Coward · · Score: 0

      yeah: I really miss the muppets.

    8. Re:Cisco anyone? by Anonymous Coward · · Score: 0

      Well you're looking at it from the perspective that only the brick is innovative but the structure built with it isn't. Google is buying companies and using their technology to innovate the way people use the Web. Would it really be very valuable for them to develop their own codec in house? Or to develop a Jabber clone (for Google Wave), or even google analytics that was Urchin. They buy these technologies and adapt them to their infrastructure to enhance their bottom line and future growth. I actually like this approach better since Google has been known to use a lot of open (no necessarily open source but open standards too) technologies which is a shift from the Microsoft way of doing things that has been reinventing the wheel in their own fashion.

    9. Re:Cisco anyone? by infinityxi · · Score: 1

      Well actually what makes wave so awesome is the decentralization that it offers. Google is working on wave with the intent that other people put up their own wave servers and then can usurp the whole walled garden that facebook pretty much has. So instead of having Google running a facebook type service solely competing on a 1 to 1 basis. Google could be one of many services where, no matter what non-Google wave service you are using, you can still communicate with a Google wave user and vice versa.

      --
      Turn based strategy game that runs over XMPP. Phalanx
    10. Re:Cisco anyone? by Enderandrew · · Score: 1

      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, and Blogger implements Wave, and GTalk ties into Wave, you'll suddenly be hooked on Wave and introduced to Orkut. The point is that Google has all the tools to put together the absolute killer network that could take down giants like Facebook.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    11. Re:Cisco anyone? by Duncan3 · · Score: 1

      Webmail has been around a lot longer then Google.

      --
      - Adam L. Beberg - The Cosm Project - http://www.mithral.com/
    12. Re:Cisco anyone? by Duncan3 · · Score: 1

      Which is why I used the term "in-house". The companies are not people thread is down the hall.

      --
      - Adam L. Beberg - The Cosm Project - http://www.mithral.com/
    13. Re:Cisco anyone? by TheSunborn · · Score: 1

      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.

    14. Re:Cisco anyone? by Anonymous Coward · · Score: 0

      Google seems to buy some software companies and run them just to mine their data. Orkut for example has been popular in Brazil, but I have never seen Google push it on me as a US customer. I feel like they just need sandboxes for their engineers to tinker with and mine data from as they work on their not-so-evil master plan.

    15. Re:Cisco anyone? by ChrisMounce · · Score: 1

      In the second part of my last post, I mentioned Google News, which was developed in-house. According to Wikipedia, half of their new products resulted from that 20% free time. If it was invented and developed while the employee was at Google, I'd say that counts as in-house, don't you agree?

      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 having new good ideas once they were Google employees.

    16. Re:Cisco anyone? by ChrisMounce · · Score: 1

      True, but Gmail was a reinvention of webmail. At the time, nobody else had a webmail application which used AJAX to such a great extent. No other webmail had Gmail's conversation interface. Most other webmail used folders instead of tags. And Google really pushed the storage limits -- I think Yahoo Mail was around 6 MB at the time.

      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!

    17. Re:Cisco anyone? by sketerpot · · Score: 1

      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.

    18. Re:Cisco anyone? by infinityxi · · Score: 1

      Google won't be the sole company running a wave server. When wave gets released you will be able to run your own wave server. Hell it is open source so you can even make enhancements (though I think that's that the plugins really are for). If facebook really wanted to, they could implement wave on their site but I doubt Microsoft will look kindly upon that. I can't speak for their other online APIs but reading Google's terms of use, I think facebook could use Google maps if they wanted. The site IS free for consumers and it doesn't say anything about paying them if you make money off your site. I could be wrong.

      Point is, wave is meant to be used like XMPP and similar to email. My wave server should be able to talk to your wave server by default.

      --
      Turn based strategy game that runs over XMPP. Phalanx
    19. Re:Cisco anyone? by badkarmadayaccount · · Score: 1

      Who is the dipshit who modded this down?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  8. No suitable codec? by nvrrobx · · Score: 3, Insightful

    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.

    That's a bit misleading. There are several suitable codecs. The problem is the major players involved with their "Not Invented Here" mentalities.

    1. Re:No suitable codec? by geckipede · · Score: 1

      Does it count as being invented here if over 90% of the work done on it was before the company was bought and became part of "here"?

    2. Re:No suitable codec? by Anonymous Coward · · Score: 0

      It is about patents and rights. That is the real problem.
      If Google opens the sources of the VP8-codec which is highly efficient, even better than h264, and declares that they would not enforce the patents then I see VP8 as the new HTML5 quasi standard. Google wants all information as accessible as possible to show more people more ads. So this is a logical step.

    3. Re:No suitable codec? by gr8_phk · · Score: 4, Insightful

      There are several suitable codecs. The problem is the major players involved with their "Not Invented Here" mentalities.

      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.

    4. Re:No suitable codec? by Frenchman113 · · Score: 1

      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.

    5. Re:No suitable codec? by nine-times · · Score: 3, 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.

    6. Re:No suitable codec? by R.Mo_Robert · · Score: 1

      The "no suitable codec" blurb is a quote from Hixie. 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.

      --
      R.Mo
    7. Re:No suitable codec? by Anonymous Coward · · Score: 0

      The problem with Theora isn't quality, it's the lack of available hardware decoders. This makes it a non-starter for mobile devices where software decoding kills battery life. The browser vendors that objected to Theora, Apple and Google, were concerned with implementing HTML5 functionality on the iPhone/Android platforms.

    8. Re:No suitable codec? by rcw-home · · Score: 1

      Actually the problem isn't "NOT Invented Here" it's "Invented Here - please pay us"

      Wouldn't Bilski render all of these patents invalid and therefore make this all moot?

    9. Re:No suitable codec? by sadler121 · · Score: 1

      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.

    10. Re:No suitable codec? by H3g3m0n · · Score: 1

      It's not the "Not Invented Here", its more Apple trying to keep vendor lockin, and everyone getting videos from iTunes rather thn YouTube. MS trying to gain a monopoly over the internet with a priopratart wmv format and SilverLight. And everyone else trying to stop MS from gaining the monopoly while they have %75 browser penetration and %95 OS share. Haven't heard much from Adobe other then there attempts to keep flash in the game by opening up to phone vendors (which Apple ignored of course). Also the fact that Theora isn't a great codec compared to the commercial ones, just the open one Fortunately Google own YouTube.

      No one seems to mention Dirac or SNOW although they are newer and might require more cpu usage (problematic for phones and such).

      --
      cat /dev/urandom > .sig
  9. Used by Youtube by magister159 · · Score: 3, Insightful

    When I was researching creating my own video upload site I contacted On2 for information about licensing their flash video encoder. They claimed that "All major user submitted flash websites used their encoder", I assumed they were hinting at YouTube. Knowing this, an acquisition seems like a smart decision.

    They're already buying the milk. Might as well just pay for the cow.

    1. Re:Used by Youtube by Satanicolas · · Score: 0

      mod this way up, we have the real motivation here

    2. Re:Used by Youtube by kill-1 · · Score: 3, Informative

      YouTube has never used the VP6 codec.

    3. Re:Used by Youtube by aztracker1 · · Score: 1

      What is their flash video encoded to?

      --
      Michael J. Ryan - tracker1.info
    4. Re:Used by Youtube by kill-1 · · Score: 2, Informative

      Sorenson Spark and H.264

    5. Re:Used by Youtube by evilviper · · Score: 1

      YouTube has never used the VP6 codec.

      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

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    6. Re:Used by Youtube by kill-1 · · Score: 1

      Never heard of videos-dl.com. But it seems they got it wrong. All Youtube HD videos are H.264 encoded.

    7. Re:Used by Youtube by evilviper · · Score: 1

      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.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    8. Re:Used by Youtube by kill-1 · · Score: 1

      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?

    9. Re:Used by Youtube by evilviper · · Score: 1

      So would you call Dan an idiot, too?

      Yes.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  10. My guesses for why by jschottm · · Score: 1

    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 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.

  11. Google wanted VP8 because it is a great ARM codec by Anonymous Coward · · 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.

  12. On2's modern codec - vp8 by Jdodge99 · · Score: 2, Interesting

    Actually they have vp6 and vp8 http://www.on2.com/index.php?564 which -- surprise, surprise -- on2 claims is better than h.264 -- if google decides to open up vp8 -- it would change the equation radically. Particularly the ogg/vp8 combo. It's also possible some vp3 diffs (theora) would still be useful when applied to vp8 -- although what the chances of this are, I couldn't say. It does solve the h.264 patent license problem for google with android and chrome os. A theora / vp8 release and a move to primacy of vp8 or derivative for youtube would reshape the whole playing field. I'm hopeful, but not gleeful yet.

  13. news+opinion == modern news by Anonymous Coward · · Score: 0

    The heavy referencing of Ogg, which has advanced more than it's roots in On2 is like calling Linux is based on Unix.
    Article is too biased to Ogg. I would think google would develop their own standard, much like Android and OpenSocial. Ogg is history.

    1. Re:news+opinion == modern news by BrentH · · Score: 1

      If we're being pedantic, OGG is just a container and as such not interesting. Although opensourcing VP8 may halt work on Theora, Vorbis is going nowhere, as it's considered among the best audo codecs out there, if not the best.

  14. FFmpeg support by DarkHelmet · · Score: 3, Interesting

    As a developer using FFmpeg, I run into problems with our clients trying to encode / decode VP6 and VP7. I'm hoping that Google will subsequently offer open source implementations of these. It will make my life a whole lot easier.

    --
    /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
  15. Googled OWNED video by Enderandrew · · Score: 2, 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.

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    1. Re:Googled OWNED video by BlueBoxSW.com · · Score: 1

      Actually On2 has a commercial hosting arm.

    2. Re:Googled OWNED video by funkatron · · Score: 1

      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.

      --
      "Welcome to our world. We are the wasted youth. And we are the future too." Yes, I know these are stupid lyrics.
    3. Re:Googled OWNED video by prozaker · · Score: 1

      hulu is a USA only site.
      while youtube can be seen worldwide (with a few exceptions).

  16. Re:Google wanted VP8 because it is a great ARM cod by yupa · · 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.

  17. Why Google is doing this by steveha · · Score: 3, Insightful

    Google can now use On2 codecs such as VP8 in YouTube, for free. No more royalties. But the royalties are not that expensive so this isn't likely a big deal for them. (Google could save more money by using smarter settings on their H.264 encoder.)

    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 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

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
    1. Re:Why Google is doing this by evilviper · · Score: 2, Interesting

      So, Google won't save much money and won't make much money by buying On2. I think they are up to something else.

      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 Google bought-up an unprofitable company, just to make sure their competitors don't get control of it first...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  18. Question... by mmaniaci · · Score: 2, 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.

  19. Re:Google wanted VP8 because it is a great ARM cod by Svartalf · · Score: 2, 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...

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  20. This is a big money saving move. by BikeHelmet · · Score: 1

    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)

  21. Somewhat OT: Chrome beta "Even More" section by RobertB-DC · · Score: 0, 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 advertising, but I wonder if they've got something else up their sleeve?

    (FWIW: the Incognito "new tab" is still nice 'n blank, except for the obvious warning against issues like "people standing behind you".)

    --
    Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
  22. It's about silicon by bill_mcgonigle · · Score: 1

    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, but the non-free aspect of that is turning around to bite us now.

    I'm working on a project that could really use hw-accelerated free codecs and the current tech is a patent minefield developers are afraid to step into. Send me a beta test unit, OK guys?

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    1. Re:It's about silicon by Anonymous Coward · · Score: 0

      The whole "h.264 has hardware decoders" thing is nonsense. All the latest generation of mobile media players use DSPs to decode h.264. Now, DSP programming is something of a black art, but it *is* possible to use them to decode other formats, theora included. So my guess is Google will put some of their brains into implementing DSP based decoders for the codecs they have aquired.

    2. Re:It's about silicon by Dr.Dubious+DDQ · · Score: 1
      "implementation in silicon (hardware acceleration)."

      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 Theora mailing list had someone who was working on FPGA-based Theora decoding or encoding some time back...].)

      ("Damned kids get off of my lawn" etc....)

  23. Discontinuity by mcrbids · · Score: 1

    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 mish-mash of poorly integrated pieces, and while they are doing some cool stuff, I need a bit more stability and completeness to do much with them. See, when I write software, the software becomes infrastructure for my clients. They use and depend on my software. I have hosting contracts for PHP apps I wrote 10 years ago, and the fact that the PHP guys have done so well at backwards compatibility means that I've transitioned from PHP 3 to 4 to 5 with so little porting that I didn't even charge the end users for the effort!

      I can't spend weeks/months working on software with a platform that's 'cool' but won't be supported in a year or two!

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
    1. Re:Discontinuity by ajs · · Score: 2, 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 app on the iPhone can get your location.

      Chrome is nice but Windows only, there's now (finally!) a Linux version, but it's so buggy that it often crashes X windows.

      OK, seriously are you just trolling?! I've run Chrome under X and never seen this happen. Are you using an experimental X server?

      And now they have their own O/S!? Two?! But which one should I use?

      Ah, you are trolling. OK, sorry, nevermind.

      PS: For the readers who are confused: Google has one released OS and it's currently supported on phone handsets only (Android). Google Chrome OS has not been released and there's no indication of exactly what niche it will fill once it is, so there's no sense in getting worked up over "choices" that don't exist.

    2. Re:Discontinuity by Joe+Tie. · · Score: 1

      It crashes X for you? I've been using chromium on linux for months, and I don't think that's ever happened for me. Not to say it's not a problem, but given that it's not even at an alpha state yet platform specific bugs are to be expected.

      --
      Everything will be taken away from you.
    3. Re:Discontinuity by Anonymous Coward · · Score: 0

      Crashes X windows? Uh first off alpha software, second off what kind of shitty distro are you running ive yet to experience this crashing and as a good OSS user you should probably report bugs ;) I don't use chrome constantly because it doesn't have adblock once that comes out bye bye firefox and welcome to speedy webpages again. Firefox is the new mozilla, it is good but it has gotten slow.

    4. Re:Discontinuity by jsight · · Score: 1

      Chrome is nice but Windows only, there's now (finally!) a Linux version, but it's so buggy that it often crashes X windows.

      "If an X server crashes, its a bug in the X server"

    5. Re:Discontinuity by Khyber · · Score: 1

      "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.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    6. Re:Discontinuity by ajs · · Score: 1

      "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 of either of those standards, so a full-featured API was created and deployed. It's very much the same API that Google uses for Calendar and App Engine and so on. They're very consistent across their tools and sites.

  24. No there wasn't. by pavon · · Score: 2, 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 crap that YouTube currently serves, rather than being content to be almost as good as the worst H.264 implementation available (the Flash implementation). Dirac is in an even worse position, and it processing requirements would be very undesirable for handheld devices.

    So all but one (Theora) were absolutely not suitable for implementation by the browsers, and even that one was questionable. I don't know if VP8 will be any better - it's technology seems to be much more similar to the modern MPEG codecs than Theora, which makes me think that On2 is probably cross-licensing patents which Google will not be able to open up, but I may be wrong.

    1. Re:No there wasn't. by Anonymous Coward · · Score: 0

      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.

      Both Mozilla and Opera could have reached some agreement with the H.264 patent-holders if they wanted to. (Yes, even Mozilla. All Mozilla code is LGPL-compatible and could be linked to code that's patent-encumbered; anyone who wanted to redistribute under the GPL could just leave that part out.) The patent-holders aren't stupid, they'd have been happy to work out something within Mozilla's/Opera's price range. The reason Mozilla and Opera refuse to implement H.264 is on principle: they're only willing to support open standards unless they absolutely have no other choice (e.g., Flash). They're the two vocal holdouts on EOT with root strings too, even though that's now publicly published with all patents disclaimed. Why? They think DRM is bad for the web and don't want to have anything to do with it.

      Apple and Google are both much more pragmatic about what standards their browsers support. Both are committed to open standards, but not to the exclusion of closed standards where useful, even if not absolutely necessary.

    2. Re:No there wasn't. by Anonymous Coward · · Score: 0

      Could you or someone explain why the concern about submarine patents is legitimate?

    3. Re:No there wasn't. by Anonymous Coward · · Score: 0

      There is no difference in possible submarine patents for Theora or any other codec. Whether you're using a free license or pay for it, the liability will be yours if a patent surfaces so the risk is pretty much exactly the same whether it's H.264 or Theora.

    4. Re:No there wasn't. by hkmwbz · · Score: 1

      Both Mozilla and Opera could have reached some agreement with the H.264 patent-holders if they wanted to.

      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.

      The reason Mozilla and Opera refuse to implement H.264 is on principle: they're only willing to support open standards unless they absolutely have no other choice (e.g., Flash).

      Uh, no. Flash is not an example of that. Flash is a PLUGIN using a plugin API. There is no specific Flash support in Mozilla or Opera. The plugin API is an open standard.

      Apple and Google are both much more pragmatic about what standards their browsers support.

      Actually, Apple wants to protect QuickTime from competition. Pragmatic my ass.

      --
      Clever signature text goes here.
  25. On2? by Anonymous Coward · · Score: 1, Funny

    Personally, I would have spent my money on at least Onlogn stuff.

    No, I didn't read the summary, what of it?

  26. This could be a good thing for web video by jonwil · · Score: 1

    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 to push Silverlight instead)

    And, by using VP8 for YouTube instead of H.264 (which means they dont have to pay any royalties to MPEG LA), Apple and others will be forced to support it.

  27. Apple still *might* support Theora by ianmacfarlane · · Score: 1

    Actually, Apple might well implement Theora, but they are worried about the patent issues. Amongst other things, that the patent agreement from On2 for VP3 might not be watertight. See this post by Apple employee on the Xiph mailing list - it really shows Apple's stance and worries on this issue.

    1. Re:Apple still *might* support Theora by Anonymous Coward · · Score: 0

      Yeah, i posted that exact thread here on Slashdot the last time the HTML5 video debate came up.

      Got my hopes up for a while; it's too bad that Xiph seemed not to care enough to ever respond to the Apple employee's questions.