Slashdot Mirror


Mozilla's VP of Engineering On H.264

We recently discussed news that YouTube and Vimeo are each testing their own HTML5 video players using the H.264 format. Firefox does not support H.264, and Mozilla's vice president of engineering, Mike Shaver, has now made a post explaining why. Quoting: "For Mozilla, H.264 is not currently a suitable technology choice. In many countries, it is a patented technology, meaning that it is illegal to use without paying license fees to the MPEG-LA. Without such a license, it is not legal to use or distribute software that produces or consumes H.264-encoded content. Indeed, even distributing H.264 content over the internet or broadcasting it over the airwaves requires the consent of the MPEG-LA, and the current fee exemption for free-to-the-viewer internet delivery is only in effect until the end of 2010. These license fees affect not only browser developers and distributors, but also represent a toll booth on anyone who wishes to produce video content." Mozilla developer Robert O'Callahan has written a blog post on the same subject, following a talk he gave on Friday about the importance of open video on the web.

675 comments

  1. Re:HTML5 Video by Anonymous Coward · · Score: 3, Insightful

    Didn't read the article then?

  2. Re:HTML5 Video by BrokenHalo · · Score: 5, Insightful

    It's mostly just problem for Mozilla

    Only if people insist on using it. I can't see that it would be in YouTube's interest to use H.264 exclusively.

    But in any case, it sounds like a misnomer to call it "HTML5 Video", which sort of implies a standard. If the "standard" involves coughing up a whacking great licence fee to use it, lots of people just won't be interested, and H.264 will be consigned to the same back shelves as some of the ogg codecs.

  3. Re:HTML5 Video by cbreak · · Score: 1

    Apple already has decoders that are properly licensed in QuickTime, so all they have to do is use those in Safari. A technology Firefox can use as well with plugins.

  4. Sigh by Anonymous Coward · · Score: 5, Insightful

    And yet even with a perfectly legitimate, reasonable, intelligent argument against H.264, tons of /. comments will go against FF's decision to promote an open, free (for everyone, not just the end users) and sane video standard over a proprietary one, ensuring that only people with lots of money can create browsers, run video sites, etc.

    It's pretty damn simple, yet no one gets it. Just like seemingly everything else these days. Misguided loyalty to one thing because it's been promoted to the end users by those with lots of money as being "obviously" superior wins out over good things simply because people don't want to use common sense and for some reason trust people/companies with greedy motivations simply because of the idea of "they are famous and rich, they must know what's best for me".

    1. Re:Sigh by ozmanjusri · · Score: 3, Insightful
      tons of /. comments will go against FF's decision to promote an open, free (for everyone, not just the end users) and sane video standard

      I think you underestimate how much commercial influence is being brought to bear on tech networking sites these days.

      --
      "I've got more toys than Teruhisa Kitahara."
    2. Re:Sigh by Anonymous Coward · · Score: 0

      As far as anyone is concerned h264 is an open free video standard. There's open free code for the encoder here and for the decoder here. Don't expectr a few misguided managers who think patents count for shit to change that.

    3. Re:Sigh by beelsebob · · Score: 1, Interesting

      And yet even with a perfectly legitimate, reasonable, intelligent argument against H.264, tons of /. comments will go against FF's decision to promote an open, free (for everyone, not just the end users) and sane video standard over a proprietary one, ensuring that only people with lots of money can create browsers, run video sites, etc.

      You seem to assume that one legitimate, reasonable, intelligent argument against H.264 immediately excludes it from the race. I by contrast can come up with three (at least) legitimate, reasonable, intelligent arguments against Ogg Theora:

      1. It doesn't have hardware accelerated decoding support on desktop *or* (more importantly) mobile platforms
      2. It is patented, and in exactly the same way as h264 will form a toll both on the internet
      3. It's video quality isn't as good as h.264's

      By your logic this rules it out as a choice too.

      I'd rather not view the world in such black and white terms though, and instead weight the two codecs up against each other. Personally, I see h264 as being the better choice, as it has only a subset of the drawbacks that ogg theora has.

      Final note: The best solution ofc would be for google to release a better codec than ogg theora for free, with no patent risk, and with video quality at least comparable to h264's.

    4. Re:Sigh by BenoitRen · · Score: 1

      Mod parent up. People need to get this.

    5. Re:Sigh by Anonymous Coward · · Score: 0
    6. Re:Sigh by drinkypoo · · Score: 2

      Final note: The best solution ofc would be for google to release a better codec than ogg theora for free, with no patent risk, and with video quality at least comparable to h264's.

      For a second there I thought this was the dumbest thing ever, but upon further reflection I decided that you're absolutely right. There must be SOMEONE out there with a great experimental video codec that just needs some love.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:Sigh by CowboyBob500 · · Score: 1, Interesting

      And yet even with a perfectly legitimate, reasonable, intelligent argument against H.264, tons of /. comments will go against FF's decision to promote an open, free (for everyone, not just the end users) and sane video standard over a proprietary one, ensuring that only people with lots of money can create browsers, run video sites, etc.

      It's time Americans stopped thinking of themselves as the centre of world technology. If Mozilla is determined to follow US law only and therefore not implement H.264 because it's encumbered with license fees there due to dumb local laws, then it is going to go the same way as the whole US software industry - it will disappear into a black hole of law suits and legal action and very quickly become irrelevant.

      H.264 is a free and open standard, just not in the US. And to be honest, you can cry me a river. The US got itself into this mess, the US needs to get itself out of it, because quite honestly, the rest of the world is not going to wait around in the meantime.

      My prediction? Canonical will fork it as Mark Shuttleworth's vision of Ubuntu is that "it just works". If the only way for him to achieve that is to fork Mozilla, then that is what I'm sure he'll at least consider doing.

    8. Re:Sigh by FrostedWheat · · Score: 4, Informative

      All of your arguments are irrelevant if the licensing issue can't be solved. Firefox can only use codecs that are not covered by restrictive licensing, no matter how good it looks. (And I agree with you, H.264 does looks good) Their choice is basically:

      • MPEG-1: ancient and horribly outdated. (And may yet be covered by patents?)
      • Theora is good enough and much easier on the CPU than Dirac or H.264.
      • Dirac is (for now) a poor performer at the typical resolutions and bitrates used on the net.

      Theora is the best of these options. It doesn't matter how good H.264 looks, it's simply impossible for Mozilla to use it without dealing with the licensing issue.

    9. Re:Sigh by porneL · · Score: 2, Informative

      It is patented, and in exactly the same way as h264 will form a toll both on the internet

      All known Theora patents have royalty-free license. Only thing that is "exactly same way" here is risk of submarine patents.

    10. Re:Sigh by beelsebob · · Score: 1

      I agree, unfortunately though, they're not going to convince anyone, because it's simply impossible for google and apple to use ogg theora without hardware acceleration for their devices.

      Bottom line –neither codec is suitable. Google and Vimeo have gone for the margionally closer to suitable codec.

    11. Re:Sigh by Rockoon · · Score: 1

      All known Theora patents have royalty-free license

      ..right now. You know that Theora is a work-in-progress, right? That right there says GO AWAY to anyone who wants to incorporate direct support in their software.

      --
      "His name was James Damore."
    12. Re:Sigh by IANAAC · · Score: 4, Insightful

      It's time Americans stopped thinking of themselves as the centre of world technology... H.264 is a free and open standard, just not in the US.

      I agree with the center of the world comment, but...

      "It's a free and open standard, just not there..." isn't completely free and open.

      I see nothing wrong with Mozilla taking that into consideration.

    13. Re:Sigh by Kjella · · Score: 3, Insightful

      Insisting on fighting H.264 will be exactly like refusing to support MP3/AAC and only play Ogg Vorbis files. You know those right, the popular files you see everywhere? H.264 is the standard for all forms of modern video and both Windows 7 and OS X support that out of the box, Theora is if possible even more obscure than Vorbis. All this will do is kill their marketshare and return the market to the proprietary browsers.

      Mozilla think that they can bend a whole market of decoding, encoding, streaming, recording and editing by refusing to add it to their browser. They're not that important. There's fights you can win, and there's fights where you can only mitigate the damage. First time you try to play a HTML5 video, it should give you a nasty disclaimer, put the responsibility of getting a patent license if that applies, and install/cancel buttons.

      --
      Live today, because you never know what tomorrow brings
    14. Re:Sigh by harlows_monkeys · · Score: 3, Insightful

      Firefox can only use codecs that are not covered by restrictive licensing, no matter how good it looks

      Nonsense. Firefox can use any codec that is already installed on the user's system. It's only because they have decided that they should try to force Theora on people that they are rejecting that solution.

    15. Re:Sigh by sopssa · · Score: 1

      it's simply impossible for Mozilla to use it without dealing with the licensing issue.

      That is completely true, they have no way to extend their license to all of the different distro versions (iceweasel and so on). Or they need major changes in their own licensing.

      Google also cannot give it forward in Chrome's open source version, but they have licensed and use it with the closed source binaries. And if the other browsers will go forward and license H.264 anyway, Firefox has a serious problem to solve. Actually this would be a perfect opportunity for the other browsers to gain marketshare from Firefox and kill off its mainstream use (especially for Google, which has its hand over Firefox already by providing almost all of its income)

    16. Re:Sigh by psnyder · · Score: 4, Informative

      There must be SOMEONE out there with a great experimental video codec that just needs some love.

      There are already a lot of video codecs out there, because there's a lot of ways to implement it. They all try to balance numerous factors within performance and quality. It's not easy. There's no one "holy grail" that produces perfect pictures while using a smaller number of resources than all of the others.

      Also...
      The editors of HTML5 are Ian Hickson (Google, Inc.) and David Hyatt (Apple, Inc.) Apple uses h264 in almost everything, so they would probably like to see it as the standard.

    17. Re:Sigh by Anonymous Coward · · Score: 0

      Hardware acceleration - fair enough. That's only because nobody's built it yet. On desktop machines, it should be possible to use OpenCL, Cuda, DirectCompute or similar to use the GPU as a hardware decoder - that's fundamentally what hardware accelerated h.264 or WMV / VC-1 decoding does anyway. Assuming you need it at all, of course. It's just mobile devices where this is an issue.

      Patents... No. There are known patents covering Theora, all of which were owned by On2. On2 developed VP3 avoiding known video encoding patents, so they could actually sell licenses to the thing (and later VPx codecs). On2 issued a non-assertion statement relating to all patents covering VP3. That technology can be used by anyone, for anything, forever. All known patents are free for anyone to use, for any purpose. That only leaves potential unknown patents. Frankly, the risk of an unknown patent is exactly the same for Theora as it is for h.264, or anything else.

      As for video quality... it's true that the encoders aren't as mature as the available h.264 encoders. The original reference Theora encoder actually was the original VP3 encoder, with minimal modifications. The Theora bitstream format changed substantially from VP3, adding new features and more leeway to improve the encoders, but actually improving the encoder didn't happen until Theora 1.1 (Thusnelda). For the kind of content you're likely to find on websites, Theora is actually pretty reasonable.

      Remember that the early h.264 encoders were only marginally better than the best available MPEG-4 ASP encoders, such as Xvid. It took years for them to reach their current quality level. The Theora encoder is only a couple of years old, and is still only at version 1.1.

      Having someone else come up with yet another codec simply will not help. It doesn't matter if it's vastly superior to h.264 - it still won't have any hardware support, the first versions of the encoders will still not be very good, and it'll still have unknown patent risk, thanks to a completely brain-damaged patent system in the US and elsewhere.

    18. Re:Sigh by BZ · · Score: 4, Informative

      > H.264 is a free and open standard, just not in the US.

      Or France or Germany, last I checked (as in, there are H.264 patents that have been granted by those countries; these are not _software_ patents but patents on the design of the codec). I haven't looked into detail for other countries, but I think you're making some unjustified assumptions here (like "h.264 patents are software patents").

    19. Re:Sigh by onefriedrice · · Score: 4, Insightful

      My prediction? Canonical will fork it as Mark Shuttleworth's vision of Ubuntu is that "it just works".

      Haha, yeah right. Anyway, I'm not sure what you're talking about with regards to the US software industry having disappeared into a black hole or become irrelevant. Last I checked, the software industry here is still very much active and relevant, and I haven't seen any real evidence to suggest that that will change any time soon.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    20. Re:Sigh by drinkypoo · · Score: 1

      Apple uses h264 in almost everything, so they would probably like to see it as the standard.

      Apple has no technically competitive advantage over Linux, so they would probably like to see Linux adoption crippled by poor support for "standards" on that operating system. I'm sure it's not the only reason, but they're responsible for pushing a standard which requires licensing fees to be paid, and they must see it as at least a side benefit.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    21. Re:Sigh by TheTurtlesMoves · · Score: 2, Insightful

      With software patents there is no such thing as free from patent risk. Both mepg2 and h264 have had litigation threats......

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    22. Re:Sigh by TheTurtlesMoves · · Score: 1

      Apple has patents that covers h264 (aka its in the MPEG-LA portfolio). So of course they want to see h264 as the standard.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    23. Re:Sigh by Goaway · · Score: 0, Troll

      Hint: Just because people disagree with you, does not mean there is a conspiracy of astroturfers working against you.

      Sometimes, people just don't agree with you.

    24. Re:Sigh by Goaway · · Score: 3, Interesting

      There is someone: Google. They bought On2. It is still unclear why, and what they are going to do with On2's technology.

    25. Re:Sigh by Goaway · · Score: 1

      It is not impossible for Mozilla to use h.264. They have several options for how to use it. None are perfect, but it is not impossible. That would include using OS libraries to play h.264, and using a plugin system.

    26. Re:Sigh by icebraining · · Score: 3, Informative

      Most users with Windows Vista and earlier do not have an H.264 codec installed. So for the majority of our users, this doesn't solve any problem.

    27. Re:Sigh by Antiocheian · · Score: 2, Insightful

      Don't worry. No matter how much astroturfing takes place the fact won't change that any video service who fails to support Firefox would lose a share too large to be underestimated.

      As for the argument against h.264, it's valid. But the full effect of it will be understood after Dec 31 2010

    28. Re:Sigh by tepples · · Score: 3, Interesting

      I by contrast can come up with three (at least) legitimate, reasonable, intelligent arguments against Ogg Theora: [...] It is patented

      What is the number of a U.S. patent covering Theora that hasn't been irrevocably licensed to the public for all uses by On2? The leaders of the Xiph.Org Foundation want to know.

    29. Re:Sigh by tepples · · Score: 2, Informative

      That would include using OS libraries to play h.264

      The article states that the majority of deployed copies of Windows do not come with OS libraries to play H.264 video.

    30. Re:Sigh by Goaway · · Score: 1

      That will soon enough be a minority, and why would it be worse if a minority of Windows machines played h.264 than if no Windows machines did so?

    31. Re:Sigh by tepples · · Score: 1

      On desktop machines, it should be possible to use OpenCL, Cuda, DirectCompute or similar

      Even on the Intel GMA that comes with a new PC if you don't specifically order an NVIDIA or ATI GPU at extra cost?

      It's just mobile devices where this is an issue.

      "Just"? In Japan, a lot of people see no need to own a desktop PC.

      All known patents are free for anyone to use, for any purpose. That only leaves potential unknown patents. Frankly, the risk of an unknown patent is exactly the same for Theora as it is for h.264, or anything else.

      Unlike Theora, H.264 has mutually assured destruction backing it up. If an H.264 licensee runs into an unknown patent, the holder of the unknown patent will probably try suing a licensee with big pockets. Then one or more MPEG-LA member will try a retaliatory lawsuit based on something the holder of the unknown patent is also doing.

    32. Re:Sigh by tepples · · Score: 1

      H.264 is a free and open standard, just not in the US. And to be honest, you can cry me a river. The US got itself into this mess, the US needs to get itself out of it

      Slashdot is in the United States so please don't whine about this on a U.S. site.

      Canonical will fork it as Mark Shuttleworth's vision of Ubuntu is that "it just works".

      The United States market is large enough that "it doesn't just work in the United States" means "it doesn't just work" because the install disc would require onboard GPS so that it won't install on a machine on U.S. soil.

    33. Re:Sigh by Antiocheian · · Score: 1

      Insisting on fighting H.264 will be exactly like refusing to support MP3/AAC

      Mozilla has not supported MP3/AAC all these years and that didn't stop them from getting their marketshare.

      Mozilla think that they can bend a whole market of decoding, encoding, streaming, recording and editing by refusing to add it to their browser.

      On the web ? Yes they can.

    34. Re:Sigh by Kjella · · Score: 2, Insightful

      For a second there I thought this was the dumbest thing ever, but upon further reflection I decided that you're absolutely right. There must be SOMEONE out there with a great experimental video codec that just needs some love.

      It's more in the "and a free pony" department. There are at least 100 patents covering H.264, I know for MPEG2 there was like 600 patent claims. For H.264 pretty much all the usual suspects are on board and part of the patent pool, If a new video format were to arise, you can bet there are patent holders just waiting to see it become great, and be one of the few patents covering it and get a bigger share of the cake.

      There really should be a process, though I don't mean a cheap one to fly under the radar and avoid patents, to make a standard and have it patent-proofed, that is to say all patent holders who think their patents apply must declare it now or lose their right to enforce the patent against that standard. It's all the patents that show up afterwards that is destroying the system.

      --
      Live today, because you never know what tomorrow brings
    35. Re:Sigh by Anonymous Coward · · Score: 0

      > these are not _software_ patents but patents on the design of the codec

      Uh...you're aware that codecs are *software* right??

    36. Re:Sigh by Anonymous Coward · · Score: 0

      IP in software can protect the little guy as much as the big corporations. While it may not work in Mozilla's favor here, I feel good knowing if I ever have a good, original software/algorithmic idea I can protect it.

      It's time Americans stopped thinking of themselves as the centre of world technology. If Mozilla is determined to follow US law only and therefore not implement H.264 because it's encumbered with license fees there due to dumb local laws, then

      Seeing that Mozilla's headquarters are in the U.S. I imagine they would like to continue providing a browser to the U.S.

      H.264 is a free and open standard, just not in the US.

      And Japan and South Korea to name a few more. But, what do they have to do with technology?

    37. Re:Sigh by dogzilla · · Score: 1

      Or Shuttleworth could just switch to a Webkit browser.

      --
      The crimes of eBay are a disgrace to it's pig latin heritage!
    38. Re:Sigh by fandingo · · Score: 2, Insightful

      ...then it is going to go the same way as the whole US software industry - it will disappear into a black hole of law suits and legal action and very quickly become irrelevant.

      It's not like all major operating systems are developed in the US (Windows, Mac, Linux -- US corporations are the primary workers on the kernel, Red Hat, Novell, Oracle, Linus lives in the US). Adobe is based in the US. I'm trying to think of other large software companies that exist completely outside the US, and I'm coming up blank. KDE is the best one that I can think of at the moment (KDE e.V. is German-based).

      For all the stink that people make about software patents, they really aren't used very much. There has been all the cellphone lawsuits lately, but that's not normal.

      I think that if Mozilla would sit down with MPEG-LA they could get a really good license (i.e. no cost). The bigger issue is complying with the GPL. I hope they can work something out because theora is simply inferior to h.264.

      I think that there are patent concerns about theora. While the creators do not hold patents on it, that certainly does not mean that there are no patents on it. That's a very large danger. Google may have to spend $5M for Chrome to support h.264, but if they use Theora and there is a submarine patent, then they will be paying way more than $5M. With H.264, MPEG-LA will be defending those suits, and I'm sure in the licensing terms they guarantee that they are the only body that holds the patents. That basically gives a corporation insurance against patent suits.

    39. Re:Sigh by Anonymous Coward · · Score: 0

      You can't force the willing.

    40. Re:Sigh by CowboyBob500 · · Score: 0, Flamebait

      he United States market is large enough that "it doesn't just work in the United States" means "it doesn't just work" because the install disc would require onboard GPS so that it won't install on a machine on U.S. soil.

      To use a British word - bollocks. Americans would like to think so, and indeed it used to be the case, but it is not the case anymore. If it works in Japan, Europe, China, South Africa and Australasia then the vast majority of the world would perceive it as "just working". Contrary to the belief of Americans, no one elsewhere gives a shit about the problems you have with patents and the litigation that goes along with them. We'll carry on using H.264 and the like just fine and if Americans can't then we don't honestly care anymore.

    41. Re:Sigh by CowboyBob500 · · Score: 2, Insightful

      It's not like all major operating systems are developed in the US (Windows, Mac, Linux -- US corporations are the primary workers on the kernel, Red Hat, Novell, Oracle, Linus lives in the US). Adobe is based in the US

      And every single one of the companies you list is deep in litigation at this very moment and spending millions (perhaps billions) fighting lawsuits. You think that situation can carry on forever?

      Those companies are lucky in that they have a decent warchest in order to keep trading. I suspect it is now next to impossible to start up and run a brand new technology company in the US. The best you can hope for is to be bought out by the big boys, or they're going to sue you into oblivion because there is pretty much nothing that you can do that won't be covered by some patent or other.

      Software patents aren't just bad ideologically, they are going to bring the US IT industry to its knees. Perhaps not now, but give it 10 years...

    42. Re:Sigh by Goalie_Ca · · Score: 2, Insightful

      Firefox should be able to rely on the windows/mac implementation of H.264 and avoid all of these headaches.

      --

      ----
      Go canucks, habs, and sens!
    43. Re:Sigh by mad.frog · · Score: 1

      H.264 is a free and open standard, just not in the US.

      Actually, in most of the industrialized world that actually respects intellectual property rights. Attempting to ignore patent law would get Mozilla banned in pretty much all of Europe as well as the USA and Canada. I think that would be a deal-breaker for them.

    44. Re:Sigh by Anonymous Coward · · Score: 0

      The editors of HTML5 are Ian Hickson (Google, Inc.) and David Hyatt (Apple, Inc.)

      Don't believe everything you read. Ian is the only editor; David Hyatt doesn't edit the spec at all. Don't take my word for it. Take a look at the mailing list archives for last month: 22 posts by Ian Hickson, zero by Dave Hyatt. Actually, I couldn't find any posts on public-html by David Hyatt in the last year, and that's the list where all W3C spec discussion is done (there's no private HTMLWG group). Also notice that the WHATWG spec only lists Ian as editor.

      More directly, just look at the Subversion log for the spec. You'll find that every single commit ever is by ianh, none by David Hyatt. I don't know why he's listed on the W3C version of the spec, but it's not because he does any actual editing.

      Ian Hickson, as it happens, is violently against anything even slightly non-standard, and you can bet he would love to see H.264 die. But his overriding goal is for the spec to reflect reality. He's not going to mandate Theora support when he knows that not all browsers will support it. Likewise, he removed Web Databases from the spec (moving them to a separate spec) when Mozilla said they didn't want to implement them.

    45. Re:Sigh by Anonymous Coward · · Score: 0

      Actually reading TFA would reveal that Windows Vista and earlier do not include the H.264 codec.

    46. Re:Sigh by sourcerror · · Score: 1

      (Windows, Mac, Linux -- US corporations are the primary workers on the kernel, Red Hat, Novell, Oracle, Linus lives in the US)

      Just to nitpick a bit. Suse was a German company, but they got bought up by Novell. But I guess most of Suse users are in Germany.

    47. Re:Sigh by darrylo · · Score: 1

      It's probably worse than that. Mozilla is heavily dependent upon Google's funding, and Firefox competes with Chrome. Long-term, there's really no reason for Google to continue funding of Mozilla (except, perhaps, for goodwill reasons). While I don't see anything changing in the short-term (say, 1-3 years), I think there's a good chance that Firefox will go the way of Netscape within 10 years.

      Also, since both Apple and Google have the marketshare, it doesn't really matter what people here think.

    48. Re:Sigh by iVtec · · Score: 1

      Actually, all modern browsers are eating off internet explorer's market share at the moment, simply by supporting new standards and being better browsers overall. Google going after firefox's market share makes no sense at all.

      This is fact. IE lost 7% marketshare more or less last year, most of which firefox and chrome absorbed. For standards to continue forward, it's crucial that there are alot of competing browsers on the market, each with a good percent of marketshare.

      So, even if HTML5 video were such an issue to the general population (which it isn't until youtube's HTML5 beta comes out of beta), it's more in Google's interest to continue to eat away IE's marketshare while having strong standard-compliant competitors like Opera, Safari and firefox.

      Google's true enemy is IE's poor standard compliance. And frankly it's our (the users) enemy too.

    49. Re:Sigh by Anonymous Coward · · Score: 0

      Nothing stopping them installing one...
      Also, most video cards these days support h.264 in hardware, so i assume the drivers come with appropriate libs anyway.

    50. Re:Sigh by ardor · · Score: 1

      No they can't.

      Mozilla has no real power over the web. They have a browser that is somewhat popular, but that's it. They made money from their deal with Google. Mozilla is no king of the internet. If anything, Google is. Google uses h264, Chrome supports h264. Go figure. As for the MP3 thing, there hasn't been a Youtube for audio, and even if one had existed, it would have used Flash, precisely because mp3/aac playback is a mess with the current browsers.

      Either, the Mozilla developers recognize this, stop their nonsense, and use system codecs, or Firefox will be the browser that "doesn't play Youtube". I doubt this will do its popularity any good. Quite possibly, people will switch to other browsers, like Chrome, or back to IE.

      --
      This sig does not contain any SCO code.
    51. Re:Sigh by tyrione · · Score: 1

      The list of licensees is extensive for H.264. The only Web browsers currently out of the loop are Mozilla, Opera, Konqueror and WebKit browsers for Linux that aren't developed by Google. I'd imagine the list of licensees that includes Apple, Microsoft, Google, Adobe, DirecTV, Samsung, Sorenson, LG, Toshiba, Sony, Mitsubishi, HBO, Fuji, Fujitsu, Sandisk, Sun Microsystems, Facebook, etc:

      http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx

      It's rather obvious that Mozilla pushing Ogg/Theora should target Viacom, Time Warner and other content producers before they license H.264.

    52. Re:Sigh by tyrione · · Score: 1

      And yet even with a perfectly legitimate, reasonable, intelligent argument against H.264, tons of /. comments will go against FF's decision to promote an open, free (for everyone, not just the end users) and sane video standard over a proprietary one, ensuring that only people with lots of money can create browsers, run video sites, etc. It's time Americans stopped thinking of themselves as the centre of world technology. If Mozilla is determined to follow US law only and therefore not implement H.264 because it's encumbered with license fees there due to dumb local laws, then it is going to go the same way as the whole US software industry - it will disappear into a black hole of law suits and legal action and very quickly become irrelevant. H.264 is a free and open standard, just not in the US. And to be honest, you can cry me a river. The US got itself into this mess, the US needs to get itself out of it, because quite honestly, the rest of the world is not going to wait around in the meantime. My prediction? Canonical will fork it as Mark Shuttleworth's vision of Ubuntu is that "it just works". If the only way for him to achieve that is to fork Mozilla, then that is what I'm sure he'll at least consider doing.

      Not to rain on our parade but H.264 is internationally patented up the wazzu, so spare me the American selfish slant. All those companies playing nice outside of US Borders are doing so knowing that the bulk of profiteering is made in the US, period. They were willing to place nice in the EU so they can continue to gain R&D returns on their investments, back within the US.

    53. Re:Sigh by Cyberllama · · Score: 4, Funny

      They just hadn't bought any companies for like, 2 whole days, and so they said "screw it" and bought one at random. That's whole Google rolls these days.

    54. Re:Sigh by slim · · Score: 1

      Open free code that may be illegal to use, depending on what country you're in, without paying MPEG LA.

      Sure, you can probably get away with it for a while for personal use, even for a small-fry web site. As soon as you're big enough to get noticed, they'll come after you with an invoice.

    55. Re:Sigh by slim · · Score: 1

      The best solution ofc would be for google to release a better codec than ogg theora for free, with no patent risk, and with video quality at least comparable to h264's.

      I think the problem is that there are patents for many of the methods that you'd necessarily use in a modern video codec.

      Imagine trying to build a non-patent-encumbered car, when someone held patents on things like tyres, steering wheels, cams...

    56. Re:Sigh by Quantumstate · · Score: 1

      Because then the standard becomes useless as mentioned in the article. What is needed is a video format that will play for everyone within the browser rather than needing a mess of duplicated content on the server. H.264 cannot provide this reasonably because it kills any open source browsers which is hardly a good proposition for an open web standard.

    57. Re:Sigh by Goaway · · Score: 4, Funny

      Look, they can quit whenever they want. It's not like they have a problem or anything.

    58. Re:Sigh by Antiocheian · · Score: 1

      They have a browser that is somewhat popular, but that's it.

      And what "it" means is that nobody would risk locking that userbase out of their service. Let Google try that and we'll resume that debate on Slashdot.

    59. Re:Sigh by Anonymous Coward · · Score: 0

      Firefox can only use codecs that are not covered by restrictive licensing, no matter how good it looks

      Nonsense. Firefox can use any codec that is already installed on the user's system.

      That doesn't solve the problem, just moves it around.

    60. Re:Sigh by slim · · Score: 1

      Surely if Google/Apple were to make the right noises, the chip manufacturers of the world would provide Theora acceleration in a heartbeat.

      You could sell a lot of chips if you were picked to be part of the next iPhone, the next Google phone, or part of Google's transcoding platform.

    61. Re:Sigh by Goaway · · Score: 1

      Yes, it would be great to have such a format, but that format will just not be Theora. It doesn't matter how much Mozilla stomp their feet and puff out their cheeks, that battle is already lost. It just does not offer any meaningful advantages for the big content producers, who can already get video that works almost everywhere by using h.264 and Flash.

    62. Re:Sigh by repetty · · Score: 1

      If Mozilla is determined to follow US law only and therefore not implement H.264 because it's encumbered with license fees there due to dumb local laws, then it is going to go the same way as the whole US software industry - it will disappear into a black hole of law suits and legal action and very quickly become irrelevant.

      The U.S. software industry is irrelevant? I know things are going badly but this is just hype for now.

      Catch your breath, dude.

    63. Re:Sigh by Anonymous Coward · · Score: 0

      As long as Mozilla produces good software they will find funding one way or another. Google is not the only money holder, besides Google backing Firefox is to make their search engine a default and they have a big return on what they pay. Google ditching firefox can only be bad for Google, since in case firefox changes its default search engine to for example Bing and that would hurt Google marketshare even more.

      Nobody uses Firefox because its default search engine is Google, but Google gives funding to Firefox, only because it's the best free browser out there, and has a considerable market share.

    64. Re:Sigh by ElusiveJoe · · Score: 1

      the install disc would require onboard GPS so that it won't install on a machine on U.S. soil

      Now that is a retarded idea. It's like forcing every DVD player manufacturer on the planet to integrate a chip, whose only purpose would be to ensure that DVDs from other countries could not be played... oh, wait...

    65. Re:Sigh by bonch · · Score: 0, Troll

      First off, H.264 is a superior codec to Theora, so what you're wanting is for technology to regress just to match some ideal.

      Second, Flash videos already play H.264, and Firefox doesn't seem to have a problem with that, so I don't understand why they wouldn't just use a plug-in as usual.

    66. Re:Sigh by ElusiveJoe · · Score: 1

      I guess, they were busy with hiring a file system inventor to format their drives. Oh, I heard they also told Linus to start packing just in case their linux boot fails after that.

    67. Re:Sigh by slim · · Score: 1

      It is not impossible for Mozilla to use h.264. They have several options for how to use it.

      But all of them conflict with the Mozilla Foundation's mission, to provide a 100% free web browsing stack, and to encourage a Web that can be fully experienced using that.

      From TFA:

      We want to make sure that the Web experience is good for all users, present and future. I want to make sure that when a child in India or Brazil or Kenya discovers the internet, there isn’t a big piece of it (video) that they can’t afford to participate in. I want to make sure that there are no toll-booth barriers to entry for someone building a whole new browser, or bringing a browser to a whole new device or OS, or making and using tools for creating standard web content. And I want that not only altruistically, but also because I want the crazy awesome video (animation, peer-to-peer, security, etc.) ideas that will come from having more people, with more perspectives, fully participating in the internet. The web is undeniably better for Mozilla having entered the browser market, and it would have been impossible for us to do so if there had been a multi-million-dollar licensing fee required for handling HTML, CSS, JavaScript or the like.

    68. Re:Sigh by Anonymous Coward · · Score: 0

      We ARE the center of world technology. @$$.

    69. Re:Sigh by Anonymous Coward · · Score: 0

      Why does everyone seem to forget about Dirac? The BBC invested a large amount of time and money developing a free and open source video codec to directly compete with H.264 and VC-1 and no one ever mentions it in these discussions.

    70. Re:Sigh by Hurricane78 · · Score: 1

      ensuring that only people with lots of money can create browsers, run video sites, etc.

      You seem to live under the delusion, that someone would actually sue me for this, and even if, that I would actually care.
      The MPEG LA won’t even be able to sue me.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    71. Re:Sigh by mdarksbane · · Score: 0

      I feel like an evil person, but honestly I'm ok with that.

      h.264 is a specific technology - you should able to patent that and charge or not charge what you want for that. The problem with software patents has always been about patenting vague concepts and obvious designs. h.264 is a tech that took a lot of work and made a large jump in quality. There's no reason you shouldn't be able to charge for that. It just sucks that there isn't really a good mechanism for that world and the GPL to interact better.

    72. Re:Sigh by Hurricane78 · · Score: 1

      Well, a real programmer would probably say, that in that case, the holy grail is a codec that combines all functions of those codecs, and automatically selects the proper balance between implementations for any piece of video. ^^

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    73. Re:Sigh by humina · · Score: 1

      It's only because they have decided that they should try to force Theora on people that they are rejecting that solution.

      You can still install a plugin to view H2.64 video in firefox. You are not being prevented from that option, Mozilla is just not forking over the licensing fees and having it available by default.

      You use of the word forced is hilarious. It is like saying that the first amendment to the US constitution forces free speech on its citizens or that a free neighborhood bbq forces food into people's mouths. Nobody is being forced to do anything. Mozilla decided they didn't want to promote a licence that requires a fee (one that can change and is quite substantial). If you want to use it, you are free to do so.

      --
      check out the best blog ever:
      http://oehlberg.com
    74. Re:Sigh by Anonymous Coward · · Score: 0

      Mark most certainly won't fork Firefox. Guaranteed.

    75. Re:Sigh by Nikker · · Score: 1

      I think that if Mozilla would sit down with MPEG-LA they could get a really good license (i.e. no cost)

      Being able to issue licenses means they can be revoked. If you look at the bigger picture you can see by licensing the format of video (if it does become ubiquitous through out) there is control over all video, kinda like that saying about eggs and baskets. When you talk about large companies you talk about power more than money, it would be more rewarding for a company to be able to disable a license (DRM??) to silence someone since it will bring them closer to those who have more power then themselves. Right now not many end users are aware or even care what codec the video they are watching was encoded in but as cameras become more powerful and cheaper they will have more power to disrupt communications, absolute power and all.

      --
      A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
    76. Re:Sigh by Korin43 · · Score: 1

      There was also a patch for Firefox 3.0 that made it use gstreamer. Seems like Mozilla didn't like it though. :(

    77. Re:Sigh by ardor · · Score: 1

      What Google will do is advertise their own browser as the one who CAN playback videos properly, while FF requires an extra Flash plugin for this. Mozilla is hugely dependent on Google, the reverse is not true.

      --
      This sig does not contain any SCO code.
    78. Re:Sigh by BZ · · Score: 1

      Sure. H.264 is something that's absolutely patentable in my book: it's novel, non-obvious, etc. It's just unfortunate, as you say, that the details of the licensing don't coexist well with open-source software (or anything else where the marginal cost of an extra decoder or encoder would otherwise be 0, in some ways).

    79. Re:Sigh by Antiocheian · · Score: 0, Flamebait

      Dependent on Google ? Are you taking 90s style magazines such as PCpro seriously ?

      Name one major open source project that stopped evolving as a result of funding withdrawal.

      In fact name one major open source project that stopped evolving period.

    80. Re:Sigh by gedw99 · · Score: 1

      The EU is rolling out a P2p video streaming system.

      http://www.p2p-next.org/

      There are many test sites.
      This means that the bandwidth problem for many video distribution companies is resolved, and the variosu codes can thrive.
      G

    81. Re:Sigh by Thinboy00 · · Score: 1

      Hint:Miseducation as a result of marketing != astroturfing.
      They're talking about people who have been deceived into thinking that H.264 is absolutely superior to Theora/Vorbis in every way, which isn't the case when you consider patents.

      --
      $ make available
    82. Re:Sigh by Thinboy00 · · Score: 1

      The United States market is large enough that "it doesn't just work in the United States" means "it doesn't just work" because the install disc would require onboard GPS so that it won't install on a machine on U.S. soil.

      Actually, the Canonical way of dealing with that is to pass the buck on to the user (i.e. pop up a dialog box saying "don't install this software if you're not sure it's legal to do so. We won't help you figure out what is(n't) legal in your country.").

      --
      $ make available
    83. Re:Sigh by sunwukong · · Score: 1

      Except that software/algorithms are excluded from patents in Canada.

    84. Re:Sigh by Thinboy00 · · Score: 1

      Software patents aren't just bad ideologically, they are going to bring the US IT industry to its knees. Perhaps not now, but give it 10 years...

      It doesn't have 10 years.

      --
      $ make available
    85. Re:Sigh by Marcika · · Score: 1

      The list of licensees is extensive for H.264. The only Web browsers currently out of the loop are Mozilla, Opera, Konqueror and WebKit browsers for Linux that aren't developed by Google. I'd imagine the list of licensees that includes Apple, Microsoft, Google, Adobe, DirecTV, Samsung, Sorenson, LG, Toshiba, Sony, Mitsubishi, HBO, Fuji, Fujitsu, Sandisk, Sun Microsystems, Facebook, etc: http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx It's rather obvious that Mozilla pushing Ogg/Theora should target Viacom, Time Warner and other content producers before they license H.264.

      But it's extremely predictable that the MAFIAA won't mind at all that their files are distributed in a format where only huge corporations can afford to be "gatekeepers". It's a lot easier to get MS, Google, Apple, Adobe and the hardware OEMs around the table to make sure they conform to some draconian closed-source end-to-end DRM scheme once all the small independent open-source software clients are out of the picture.

    86. Re:Sigh by Goaway · · Score: 1

      But all of them conflict with the Mozilla Foundation's mission, to provide a 100% free web browsing stack, and to encourage a Web that can be fully experienced using that.

      That is a shame, since they need to do it anyway.

    87. Re:Sigh by Eil · · Score: 1

      H.264 is a free and open standard, just not in the US.

      Umm, heh. You do realize that the Mozilla Corporation is a U.S. company, right?

    88. Re:Sigh by Anonymous Coward · · Score: 0

      Did you read the links in the summary? It's not because they are "trying to force Theora on people", it's because it would be a nightmare.

      Horrible cross-platform implementation issues aside, you end up turning platform-specific problems with video playback (bad configuration, missing, broken or outdated codecs) into Firefox problems. That might be fine for you, but your grandma isn't going to want to debug and maintain that stuff just to watch videos of break-dancing kittens. You also expose security bugs in DirectShow filters or Quicktime to the web, and neither of those are exactly unheard of.

      If HTML5 video doesn't provide the user with an experience that's as good as or better than Flash, nobody is going to bother.

    89. Re:Sigh by supernova_hq · · Score: 1

      LOL, Americans...

      So a site is hosted/run from the US, but I doubt more than half the visitors (audience) is American.

      As for it not "just working" in the us being that important, Ubuntu is controlled in England and run with African ethics, good luck getting your oh-so-important US problems involved.

      I'm also pretty sure that while the US does represent a rather large number of Ubuntu users, China, Africa and Europe represent even more.

    90. Re:Sigh by supernova_hq · · Score: 1

      Actually, there are still many good reasons for them to continue funding them. Firefox is still, by a LARGE margin, the most popular non-ie browser out there. In the future your statement may be true, but Chrome does not yet have nearly enough popularity to supply the influence that Firefox does today.

    91. Re:Sigh by Draek · · Score: 1

      "Somewhat" popular, yeah. I still remember web developers going to hell and back for IE4 back when it had less than half of Firefox's current marketshare. They still do for IE6 despite being barely a tenth of the web's population.

      Don't delude yourself, H.264 was already dead as a standard the moment MPEG-LA decided to license it under terms unacceptable to the Mozilla Foundation. The only question is whether Google and Apple will go to Theora or the video tag will die and we'll all go back to Flash, most likely the latter.

      --
      No problem is insoluble in all conceivable circumstances.
    92. Re:Sigh by Anonymous Coward · · Score: 0

      "Slashdot is in the United States so please don't whine about this on a U.S. site."

      I don't see why he shouldn't.

      I agree with the rest of your point, that the US matters enough that outside-US-only features are non-starters (particularly since the bulk of mozilla development takes place in the US), but slashdot's country-of-origin doesn't seem that important.

      And a huge chunk of the non-US market has treaties with the US that mean US patent laws apply there (and those country's patent laws apply in the US) to some extent, anyway.

    93. Re:Sigh by Billly+Gates · · Score: 1

      The commercial influence is why I am against h.264. Its in everyone's interest to keep html open as possible... well except the media companies.

    94. Re:Sigh by shutdown+-p+now · · Score: 1

      But the system is extensible, meaning that said users can go and download that codec, and have it supported in all applications, including Firefox (should it go down that route).

    95. Re:Sigh by shutdown+-p+now · · Score: 2, Insightful

      Don't worry. No matter how much astroturfing takes place the fact won't change that any video service who fails to support Firefox would lose a share too large to be underestimated.

      They will support FF in exact same way they will support IE (which doesn't have any implementation of VIDEO element, and is too big to be ignored) - via Flash.

    96. Re:Sigh by Billly+Gates · · Score: 1

      Has anyone looked at the firefox 3.x welcome screen that shows videos welcoming you to firefox?

      That was theora/vorbis and they looked fine to me and even better than youtube.

      Sure there might be a few HD purists (those that have gold plated plugs for their audio cables) that will tell you a difference exists. But can the eye really spot it? Oh Theora uses more cpu than mpeg4 ... mpeg 4 plays fine on old pentium IIs. A modern video card and cpu combo can play Theora fine.

      Also h.264 is downgraded in sites like youtube for bandwidth reasons so you do not get supperior quality anyway.

      We need firefox to exists and it will be a problem next year I fear. Html and the web is endanger from these silly patents. Standards exists so we do not have to rely on monopolies, patents, and secrets to do everyday work. Its not a standard if its owned. It simply belongs to a someone who now has a monopoly.

    97. Re:Sigh by Anonymous Coward · · Score: 0

      Nonsense. Firefox can use any codec that is already installed on the user's system.

      No it can't. It could, with considerable effort, be given that ability.

      It's only because they have decided that they should try to force Theora on people that they are rejecting that solution.

      No, there are perfectly sound technical reasons to prefer Theora. With a free/open-source codec, they can implement support simply by embedding Theora into the browser. One bit of work, done, and now it works the same on every platform Firefox works on.

      The problem with people who shout "just use system codecs" is that what they mean is "just use codecs on my system". If you're a Windows user, you wouldn't cheer Mozilla for adding support for OS X system codecs. If you're a Mac user, you wouldn't be overjoyed by news of Gnome support. There's no cross-platform standard, so Mozilla would have to add completely separate support for every single platform they run on, one by one, starting from scratch every time.

      Or they could, you know, try to persuade people to use the codec that can be embedded right into any browser (not just Firefox, it would be easier for everyone). Makes a lot of sense when you think about it.

    98. Re:Sigh by Billly+Gates · · Score: 1

      We are not forcing theora.

      We are simply not forcing patented technologies in HTML 5. It does not belong in it and the www consortium wants an alternative to flash. This is a reasonable requests.

      Mozilla is upset because they can't use html 5 purely. They simply just can't distribute it and a year from now you may have to wipe your precious linux box for Windows so you can participate on the web when the mpeg companies start being jerks and pusing drm and monopoly fees on everyone.

      Worse Hollywood has been known to throw teenagers in jail for linking code and websites. Firefox might have to crippled and force everyone to use IE.

    99. Re:Sigh by Anonymous Coward · · Score: 0

      arguably they are "method patents" realistically they are standards patents which is even stupider imo

    100. Re:Sigh by icebraining · · Score: 2

      But I could just download gst-plugins-ugly and I'd be OK.

        That's a selfish attitude. Everyone should be able to browse the Web with a free software stack without having to jump through arcane hoops to download and install software (whose use is legally questionable).

    101. Re:Sigh by kriston · · Score: 1

      You do realize that Theora is derived directly from On2's VP3 codec, and that On2 owns and has the rights to use important IP and has the means by which to license it?

      --

      Kriston

    102. Re:Sigh by shutdown+-p+now · · Score: 1

      That's a selfish attitude. Everyone should be able to browse the Web with a free software stack without having to jump through arcane hoops to download and install software (whose use is legally questionable).

      You're absolutely free to do so. Hence why HTML5 doesn't mandate H.264. So you can have conformant browsers, and compliant web sites, that do not in any way deal with this patented format.

      But there's also the freedom of providers to use whatever format they deem best for the content they put up online. You don't have any right to force the providers to use the format that's convenient for you; you do have the freedom to ignore their content, though.

      It's only a big deal because Google sided up with the H.264 camp in this case, and even most geeks are hooked on the services that Google offers.

    103. Re:Sigh by Anonymous Coward · · Score: 0

      Put in 264 support
      Host firefox in a country without software patents
      ??????
      PROFIT

    104. Re:Sigh by Anonymous Coward · · Score: 0

      This poster gets it. Mozilla will be unable to reverse the current trend away from h.264 towards Theora. The main reason? Because there is a lack of professional level authoring tools for Ogg Theora (unlike h.264, where there are all kinds on PC and Mac). Backing a free open video standard does no good if there is no content available on that standard. And where will the content come from with a lack of professional authoring tools?

    105. Re:Sigh by Anonymous Coward · · Score: 0

      h264 and Ogg Theora are just fine in terms of quality. The problem that Mozilla is up against isn't any failures in the codecs, it's in the lack of authoring tools for Ogg Theora, hence a lack of content that is solely available in Theora.

    106. Re:Sigh by Pentium100 · · Score: 1

      "Hello and welcome to Youtube! To be able to watch our videos in higher quality, please download and install CCCP."

      In any case, a lot of users have h.264 codec installed. At least those who watch HD movies on their PCs.

    107. Re:Sigh by Anonymous Coward · · Score: 0

      You mean that the browser can "call" an internal H.264 engine and be done with it? Or is it done by an auxiliary program like WMPlayer or QuickTime or VLC? If so, why are we discussing this anyway?? Any browser should be able to "bundle" VLC and be done with it.

    108. Re:Sigh by Anonymous Coward · · Score: 0

      what part of "it is in violation of the law for us to distribute H.264 out-of-the-box in most western countries" do you not understand?

    109. Re:Sigh by jez9999 · · Score: 1

      Mark Shuttleworth's vision of Ubuntu is that "it just works".

      Hahahahahahahahahaha!

    110. Re:Sigh by Xest · · Score: 1

      I agree but I think his point was that it's time some companies start taking a stand on the problem.

      Perhaps if companies started doing this more prominently- releasing full feature versions outside the US, and crippled versions in the US, it'd make the US government reconsider software patents.

      This is already happening to an extent, but not prominently enough. Some Android phones have multi-touch outisde of the US, but have it disabled in the US because Apple holds a patent on it such that the US ends up with crippled versions.

      Of course, a lot of companies wont do this because they are themselves American and don't want to give themselves a crippled version and so work around the problem even if that means ending up with a solution that is not as good as it could be. The problem with that idea is that it just means they are supporting the US' stupid software patent regime and strengthening it's existence.

      The government wont do anything unless enough voices complain, but no voices will complain if they're just given half-assed workarounds that mask the fact the solution that they're getting is inferior to what it could be. People need to be given a reason to complain, and the likes of Mozilla are at least in a position to do so.

    111. Re:Sigh by icebraining · · Score: 1

      It's not "me", notice the quotation marks. It's Robert O'Callahan, in the blog post linked in the summary. So his opinion is Mozilla's, probably.

    112. Re:Sigh by badkarmadayaccount · · Score: 1

      Nokia.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    113. Re:Sigh by atilla+filiz · · Score: 1

      It is patented, and in exactly the same way as h264 will form a troll both on the internet

      Fixed that for you.

    114. Re:Sigh by hazydave · · Score: 1

      Google buying On2 could mean a few things.

      For one, there's this whole H.264 vs. Theora debacle in HTML5. Google and many other big companies are in support of H.264 largely because of the patent pool -- it's safe. While it's a fact that Ogg Vorbia and Theora live in the open source community, there's plenty of concern that they're not clear, patent-wise. Theora was adapted from On2's VP3 CODEC, which they donated to the FOSS community. But that doesn't make it immune to infringement of others' patents.

      On2 VP6 was the basis for the old standard definition Flash Video. But modern flash is done in H.264, and Google's not paying for flash encoding anyway. But VP7 or VP8 is the standard video CODEC for JavaFX, so there's going to be life here yet.

      One good bet: Google might want to offer an update to the Theora, too. On2's current video CODEC is VP8, which is far more competitive to H.264. If the H.264 fees were high, Google might have considered improving Theora with VP8 as a way to save costs on YouTube. As it standards, going to Theora today on YouTube would be bad news... they'd either lower quality or raise the one really expensive part of it... bandwidth demands. But H.264 licensing is $10,000 per web site per year... I think Google spends more in replacement foosballs for a year. On the other hand, On2 has been claiming that, at least for lower bitrates ("HD" video on YouTube is only 2Mb/s, which may quality), VP8 outperforms H.264, and is less compute intensive on playback. While many are skeptical, it would be very worthwhile to Google's bottom line from YouTube is they could actually maintain quality and lower bitrate for all that video. That would normally be a problem -- who wants another plug-in? But if they also influence the HMTL standard... no problem. Google has shown before they have no problem buying software and open sourcing it if it's going to save them money and/or protect a market (AndroidOS for example).

      Another one: Google is now the parent of two operating systems: Android and ChromeOS. Most OS companies (Microsoft and Apple in particular) have their own video CODECs as well as supporting the industry standards. Owning your own may offer some advantages... not sure about $100 million of them.

      Another bet is China. They have standardized in a very big way on the On2 VP6 CODECs for web video. There's a flurry of activity around VP7 for mobile video now, too. This might also mesh with On2's not-so-long-ago purchase (for $58 million) of Hantro, a mobile video company. Google is in the mobile device market now in a big way. VP7 is supposedly lower complexity, thus, longer battery life on playback... assuming the video hardware on your typical Android device offers as much boost for VP7 as it does for H264. That was a big issue (in theory, at least) over the whole Theora thing: today's video acceleration hardware is tuned for H.264, MPEG, and occasionally VC-1.

      About VP8: http://www.dspdesignline.com/showArticle.jhtml?articleID=214303691

      --
      -Dave Haynie
    115. Re:Sigh by Improv · · Score: 1

      I don't think it's a good solution if it leaves Linux users out.

      --
      For every problem, there is at least one solution that is simple, neat, and wrong.
    116. Re:Sigh by hazydave · · Score: 1

      Perhaps both.

      For one, you WANT to use the OS-available CODEC if it exists. This is the best way to ensure you're tapping into the available hardware resources.

      Mozilla CAN support these things. They can go ahead and build-in a Theora decoder, defaulting to an OS-level replacement if one exists (which might use your GPU, either via OpenCL or an OS-specific video acceleration API, or an add-in like the SPURS Engine).
      Or only support the external CODECs, but supply the latest Theora for the system at hand. Also support H.264, but not as a built-in, only via an external CODEC. Then offer a closed-source, pay-for CODEC of their own, if they're really that concerned that users won't have them.

      But I think it's important to note that a built-in decoder is only just better than none at all. It should be the last resort... OS level decoders should be used if available. Yeah, it's a little more work for the developers.

      It's stupid that this became a format war by the browser people. The real way to support innovation is to recommend that hooks into an OS multimedia system, if available. And that fully compliant browsers will supports some set of CODECs... such as H.264 and Theora, others optional. This allows content providers more freedom, and lets the whole industry get their act together on the formats everyone wants to support.

      This has happened before... with DVD and then Blu-Ray.

      --
      -Dave Haynie
    117. Re:Sigh by Guspaz · · Score: 1

      And all users with Windows 7 have already paid for the h.264 license, and have h.264 decoding built-in. It won't be long before the majority of Firefox's userbase will have a valid h.264 license.

      So, what's the problem with Firefox supporting h.264 if a local option is available? Supporting h.264 for (eventually) the majority of clients is better than not supporting it at all.

    118. Re:Sigh by icebraining · · Score: 1

      That's a selfish attitude. Everyone should be able to browse the Web with a free software stack without having to jump through arcane hoops to download and install software (whose use is legally questionable).

      Notice the quote marks. This was written by the author of the blog linked in the summary.

    119. Re:Sigh by icebraining · · Score: 1

      "Hello and welcome to Youtube! To be able to watch our videos in higher quality, please download and install CCCP."

      CCCP seems to be hosted in the US, so they are probably illegal unless they pay the fee to MPEG-LA.

      In any case, a lot of users have h.264 codec installed. At least those who watch HD movies on their PCs.

      Reply:

      That's a selfish attitude. Everyone should be able to browse the Web with a free software stack without having to jump through arcane hoops to download and install software (whose use is legally questionable).

      Notice the quote marks. This was written by the author of the blog linked in the summary (and I agree with him).

    120. Re:Sigh by Pentium100 · · Score: 1

      That's a selfish attitude. Everyone should be able to browse the Web with a free software stack without having to jump through arcane hoops to download and install software (whose use is legally questionable).

      And the current situation is even better. I cannot make firefox show h264 videos no matter how many hoops I jump.

      I don't like chrome (each tab = process) and safari, so I am forced to use flash or to just download the video and watch it in a separate media player program. Well, that is surely less hoop jumping than downloading a codec, right?

      Oh wait, I had to download and install flash too. So yea, let's compare:

      1.Firefox uses system codecs.
      Pros:
      It is possible to watch h264 videos.
      It is possible to do so without flash.
      Cons:
      Some users will have to download and install a small program (the codec).

      2.Sites continue to use flash to support Firefox.
      Pros:
      It is possible to watch h264 videos.
      Cons:
      Flash players are usually buggy and slow.
      All users will have to download and install a small program (the plugin).

      3.No flash and no h264 support in Firefox.
      Pros:
      You don't need to download and install a small program.
      Cons:
      You cannot watch h264 videos.
      If you want to watch them, you will have to download and install a small program (the same as in option 1), also you will have to download and install another program (the player), also you will have to manually download the videos and then play them, no more streaming (some players actually support playing files that the downloading is still in progress).

      4.Use another browser
      Pros:
      You can watch h264 videos without using flash.
      Cons:
      Maybe the browser is inferior to Firefox in other areas, so you will have to use two browsers - one to watch videos, another for everything else.

      Clearly option #2, #3 or #4 is less hoop jumping for the users than option #1.

      This looks to me like the IE thing all over again.

      IE6 did not support a lot of standards (for example some CSS properties), so web developers used workarounds to make the web sites work with IE. Since IE6 was the most used browser, some of them did not make a version of the site that is standards compliant. The result - some sites did not work without IE. Another result - the development of web standards was delayed a lot. But that was Microsoft, they wanted an MS only internet.

      Now Firefox has a lot of market share and Mozilla has ideological issues with h264 codec. So they refuse to implement the codec, even though it is possible for them to do so (use system codecs). Of course others hate Theora and refuse to implement it, but h264 has already become a de-facto standard, a lot of mobile devices support it. So, the HTML5 standard will be delayed, video tag, will be delayed and we will use flash players for a long time. Unless everybody starts using Chrome or Safari.

      Oh, and Microsoft does not like the video tag, great combination. Mozilla + MS should make a very good standards delaying team. MS has a lot of experience in that area, which will surely help Mozilla too.

      So, thank you, Mozilla (and MS), for fighting the fight for our freedom to continue to use flash players for watching videos on Youtube and other sites.

    121. Re:Sigh by icebraining · · Score: 1

      They are taking a stance; The others are trying to force people to use proprietary software (There are NO free* and Legal codecs for H.264).

      Mozilla's Mission is to give a free* browser to everyone. Not a "partially" free, or a "free to those who buy a non-free OS", or "free to those who break the law by using GPL codecs".

      What you are saying is that you are cool with other having to lose their freedom (and possibly go illegal), just so that you can watch H.264 comfortably. Sorry, but yes, that's a selfish attitude.

      *not as in beer.

    122. Re:Sigh by Pentium100 · · Score: 1

      And they are taking the exact opposite stance - they are cool with almost everyone not being able to watch most of the videos on the 'net just so few could watch videos comfortably (and only from specific sites - are there any sites that actually use HTML5 and Theora?).

      How about we turn this around - instead of nobody being able to watch the videos, how about those who cannot download the codec (for whatever reasons) continue to use flash, while those who can, watch the video without flash.

      If I could program... I could make a version of FF that uses system codecs, or would just somehow splice ffmpeg into it and distribute this version from a server outside the US (I don't live in the US either). I wonder how many downloads I would get. But I can't program and this is why there is no difference to me between an open source and a closed source program, as long as they cost the same.

      Oh, maybe someone has already done this, time to go to google.

    123. Re:Sigh by Guspaz · · Score: 1

      The author could not be more wrong. Looking up some blog posts from Asa Dotzler, 2-5% of Firefox users are on Linux, 7% are on OS X, and the rest are Windows. Right off the bat, that means that 95-98% of Firefox users are on platforms that either do or will eventually support h.264 out of the box.

      The "eventually" part is important because at some point, the percentage of people using a version before Windows 7 will be small enough that either Firefox will drop support or they will be statistically insignificant. For example, Firefox 3 and above do not run on Win98.

      Of the Linux users, some will already have some sort of h.264 support installed. I'll emphasize the already installed part because it circumvents the "jump through arcane hoops to download and install software (whose use is legally questionable)" bit, as in those users would have had it installed anyhow, for whatever reason.

      So if we make up a number and assume that half of Linux users have done so, we could come to a figure of 1.75% of Firefox users eventually supporting h.264 without any effort on the users' part.

      Now we turn it around; 98.25% of users can play h.264, it is the 1.75% of users who are selfish for refusing to let the VAST majority enjoy higher quality video. The selfish tiny free software minority are holding back technological progress for the rest of us!

  5. Just open up the video architecture by DrXym · · Score: 5, Insightful

    Mozilla doesn't have to implement anything, just make the video plugin architecture extensible. Otherwise sites will just push other browsers which do implement H264, or will use plugins like Silverlight / Flash to render the content anyway in Firefox.

    1. Re:Just open up the video architecture by hitmark · · Score: 1

      and that would be different from the media player plugin hell that we have seen for ages?

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    2. Re:Just open up the video architecture by jones_supa · · Score: 1

      Exactly. Couldn't this problem be avoided by just using something like GStreamer for the playback and let it and the OS take care of the codecs? Then you don't have to include anything.

    3. Re:Just open up the video architecture by sopssa · · Score: 3, Insightful

      At least other browsers would have a standard and didn't need to rely on flash. Firefox already kind of is addon hell, where you have to try to find all the plugins you would want from a browser and some of them aren't really that up to par with quality.

    4. Re:Just open up the video architecture by DrXym · · Score: 1

      It's quite straightforward to define a mechanism to install / remove plugins, interrogate them for the content types they support, and to allow a user to choose their default choice. Firefox already does this for regular plugins, so why do you think it would be hard for video specific ones? In fact, the existing plugin architecture would make a reasonable starting point for implementing video plugins - they could just be NPAPIs that happen to implement a certain interface for Firefox to control their playback functionality, register listeners and so on.

    5. Re:Just open up the video architecture by GreatBunzinni · · Score: 1

      I don't understand how that solves the problem of being forced to rely on patented code (and therefore being forced to pay license fees) to be able to perform a basic, mundane task. That is nothing more than playing hot potato with the problem and quickly passing it on to the users, expecting that somehow they solve the problem that they failed to tackle to begin with. In fact, that is a pretty big incentive for video sites such as youtube to simply stick with flash video. How is that a step forward?

      That is not how you solve the problem. You solve it by not relying on patent-encumbered standards from the start, which is exactly where we are right now and which is exactly what Mozilla is doing. And unless organizations such as Mozilla make a stance on this issue then we, the public, are screwed once again.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    6. Re:Just open up the video architecture by Anonymous Coward · · Score: 0

      Wouldn't that just push the problem else where? Debian aren't going to be touching this with a barge pole.

    7. Re:Just open up the video architecture by BenoitRen · · Score: 5, Informative
    8. Re:Just open up the video architecture by Anonymous Coward · · Score: 0

      Different interface. With plugins, every web developer has to handle the proprietary plugin object interface. With HTML5, the web browser presents a clean interface and handles the integration of third party codecs to actually supply the functionality.

      I'm sorry, but if Mozilla goes against H.264, they're vastly overestimating their importance. H.264 is the video compression standard for the next couple of years, because it's better and because there are hardware accelerated decoders on all kinds of devices from cellphones to computers and set top boxes. If Mozilla's browsers don't play it, people will use other browsers (or web developers will have to work around Mozilla-browsers' deficiencies with plugins, and hate Mozilla for that).

      By all means, keep working on a Free H.264 replacement, but until you can at least match H.264, don't leave your users hanging, or they'll leave you hanging.

    9. Re:Just open up the video architecture by DrXym · · Score: 1
      I don't understand how that solves the problem of being forced to rely on patented code (and therefore being forced to pay license fees) to be able to perform a basic, mundane task. That is nothing more than playing hot potato with the problem and quickly passing it on to the users, expecting that somehow they solve the problem that they failed to tackle to begin with. In fact, that is a pretty big incentive for video sites such as youtube to simply stick with flash video. How is that a step forward?

      Mozilla isn't forced to rely on any patented code. They expose a bunch of APIs and let someone else worry about it. Forcing people to choose between Silverlight / Flash and an video tag that only supports Ogg is completely counterproductive. Sites will simply use the former while advising people to use another browser.

      Besides, Mozilla already allows itself to host patented code in other ways such as plugins, and extensions so what exactly is the problem here?

    10. Re:Just open up the video architecture by Draek · · Score: 1

      That forcing website devs to choose between Silverlight/Flash and inconveniencing the user to install some illegal plugin on their browsers is similarly unproductive.

      --
      No problem is insoluble in all conceivable circumstances.
    11. Re:Just open up the video architecture by Goaway · · Score: 3, Insightful

      Soon enough, most users will be on an OS that supplies h.264 decoding by default, and won't need to rely on any plugins. That is, if Mozilla would actually use the OS-supplied h.264 decoders, which they say they won't.

    12. Re:Just open up the video architecture by cortana · · Score: 1

      You'll only have to experience the media plugin hell if you insist on using Firefox. Everyone else will have h.264 video that just works.

    13. Re:Just open up the video architecture by Antiocheian · · Score: 1

      Had you read the article, you'd find your point: "Everyone should be able to browse the Web with a free software stack without having to jump through arcane hoops to download and install software"

      Just don't think the Web should rely on h.264

    14. Re:Just open up the video architecture by arose · · Score: 3, Insightful

      At least other browsers would have a standard and didn't need to rely on flash.

      Did you just reply without even trying to understand the point? Flash became the de-facto web video standard *because* you couldn't rely on having RealPlayer, Windows Media or Quicktime being installed and have the codec in question. Just using whatever codecs are on any given machine leads down exactly the same path.

      Firefox already kind of is addon hell, where you have to try to find all the plugins you would want from a browser and some of them aren't really that up to par with quality.

      Browser extensions and content plugins are completely unrelated, web sites don't rely on extensions, so whatever problems you personally have with those is irrelevant to the discussion.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    15. Re:Just open up the video architecture by arose · · Score: 1

      Chrome and Safare is only "everyone else" in the sense that they are a small minority. IE and Firefox have most of the desktop market and Opera is still the mobile leader outside of the iPhone.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    16. Re:Just open up the video architecture by TheRaven64 · · Score: 1

      What hell? Seriously. It was a problem in the late '90s, when MPEG-1 worked everywhere, MPEG-2 was better, but probably didn't, MPEG-4 did if you had the right codec installed, RealVideo didn't provide CODECs, so you'd end up using their plugin, Sorensen and a few other proprietary CODECs had better video quality, but weren't widely supported. Now, there are two flavours of MPEG-4 (Part 2 and AVC) that work everywhere and a few smaller players (Dirac, Theora) that have some advantages but aren't widely supported.

      The problem with using plugins and embed / object tags was that there was no way of integrating them with the rest of your site. The video tag can, and should, be implemented via plugins. The difference between using video and using object is that you get a set of properties and methods that you can set and use that are independent of the plugin used for playback.

      Xiph.org provides DirectShow and QuickTime CODECs, so there's no reason why FireFox on Windows and Mac couldn't bundle these by default.

      --
      I am TheRaven on Soylent News
    17. Re:Just open up the video architecture by sopssa · · Score: 1

      Just using whatever codecs are on any given machine leads down exactly the same path.

      I didn't object to the parent's comment. In fact I agreed to it and there should be a single codec that would be used. That is the whole point of this story too.

      Frankly, H.264 is the best one there is and companies have already licensed it and are willing to do so. In fact, Windows 7 has H.264 and any program can use it.

      What was my point is that this is only a problem for Firefox (and somewhat Opera, but not as much). Since Firefox users already have to install lots of addons to use their browser, how bad would be to have one extra one?

    18. Re:Just open up the video architecture by arose · · Score: 2, Insightful

      Since Firefox users already have to install lots of addons to use their browser, how bad would be to have one extra one?

      No one has to install anything to just view websites, you need to install the Flash plugin (which is not a Firefox add-on as such) to play certain games and watch videos. Mozilla wants to bring the videos back into "no additional installation" land, not into "install Flash and a, possibly shady H.264 codec, unless on Win7" land.

      Not to mention giving people like me the ability to actually take advantage of the video tag without paying for the rights to encode H.264 and god knows what else after MPEG LA modifies the terms.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    19. Re:Just open up the video architecture by DrXym · · Score: 1
      Besides, even on operating systems with no default H264 encoders, there are still options. There are plenty commercial and non-commercial plugins for Windows, Mac and Linux. For example I'm sure DIVX would be delighted to supply a free video plugin for users on pre Windows 7 systems. And of course much of the world doesn't recognize software patents so VideoLan would be perfectly legal to use too.

      All of which is moot because of the nonsensical stance Mozilla is taking. By insisting on ogg and ogg only, they're just forcing web sites to ignore an important feature of HTML 5 and use proprietary plugins instead.

    20. Re:Just open up the video architecture by nabsltd · · Score: 1

      Mozilla doesn't have to implement anything, just make the video plugin architecture extensible.

      They could even include an H.264 player plugin as part of default install, but only make it a hook to already installed codecs.

      Then, add some code so that if you try to play HTML5 H.264 video without the right codec, it displays a page that tells the user how to download one for the current OS. If your OS has support out of the box, then you'd never know that Firefox couldn't play H.264 without some third-party code.

    21. Re:Just open up the video architecture by slim · · Score: 1

      Otherwise sites will just push other browsers which do implement H264, or will use plugins like Silverlight / Flash to render the content anyway in Firefox.

      Two mutually exclusive scenarios here:
      Scenario 1: HTML5 does not provide a better user experience than Flash. (yeah, right)
      In which case, why are we worrying. Sites will continue to use Flash. Everyone is happy.

      Scenario 2: HTML5 provides a better user experience than Flash
      So, sites will find that their users are demanding HTML5 video instead of Flash.
      Now, what's the easiest and least alienating to customers:
      (a) Tell customers "OK, here's your HTML5 video. But if you're using Firefox, go and get another browser."
      (b) Dual encoding to both Theora and H.264. Delta cost: just the storage.

      If it was my commercial site, I'd do (b). I'd also be crossing my fingers that one day the browser landscape would let me just use Theora, so I could stop paying these pesky license fees for encoding and transmitting H.264.

    22. Re:Just open up the video architecture by klapaucjusz · · Score: 1

      roc has explained why using DirectShow in Mozilla's Gecko won't happen in the foreseeable future.

      It sounds like he's making excuses.

    23. Re:Just open up the video architecture by jpmorgan · · Score: 1

      Probably most important: we want to focus our energy on promoting open unencumbered codecs at this time.

    24. Re:Just open up the video architecture by BronsCon · · Score: 1

      Besides, Mozilla already allows itself to host patented code in other ways such as plugins, and extensions so what exactly is the problem here?

      Uhmm... Plugins containing patent-protected code aren't distributed with Firefox? I'm not sure (it's not like it's obvious or anything), but I'd have to guess that's the fundamental difference between allowing patented plugins and including patented codecs.

      Allowing and including are two different things, I don't get how people miss that.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    25. Re:Just open up the video architecture by maztuhblastah · · Score: 2, Insightful

      Did you just reply without even trying to understand the point? Flash became the de-facto web video standard *because* you couldn't rely on having RealPlayer, Windows Media or Quicktime being installed and have the codec in question. Just using whatever codecs are on any given machine leads down exactly the same path.

      That's not really as relevant here as you might think.

      There's a difference between being unable to rely on a particular piece of software being installed when webmasters are given carte blanche in terms of format (as was the case in the early days with object embedding) and simply relying on a platform-specific implementation to support a clearly-understood de-facto standard.

      A better analogy would be the 'img' tag. There are three or four common image formats that quickly became the de-facto standard (despite the fact that the spec never mentioned file formats, IIRC.) Browsers rely on platform-specific implementations to handle decoding, etc.

      Honestly, there's no reason not to do this for Firefox. The *only* reason to treat the video tag differently is ideology. As far as ideology goes, I agree with Mozilla -- an 'open' web is better than a patent-encumbered one, by far.

      That said, at some point you have to be realistic. Mozilla simply doesn't have the clout necessary to force companies like Google to start using a technically-inferior solution (Theora -- yes, it *is* inferior.) While it's nice to imagine that Google will re-encode all their content into both formats so as to support Firefox, it just ain't gonna happen. Therefore, we're left with the coming situation: Safari, Chrome, and Internet Explorer -- the publishers of all of whom have no problem leveraging platform-specific decoding libraries -- will support YouTube's videos, but Firefox users will get a page saying "We're sorry, but your browser isn't supported. Click here to upgrade." with a link to one of the aforementioned. And what, pray tell, do you think the average user (the one whose geek friend installed Firefox for him) will do? Is he going to say "Ah, but Mozilla's pragmatic stance is better for the future of the web, thus I shall stick with Firefox"? Nope. He's gonna want to watch that video of a cat falling down stairs, or whatever, and he's gonna "upgrade" to Chrome or Safari or IE.

    26. Re:Just open up the video architecture by shutdown+-p+now · · Score: 2, Interesting

      Did you just reply without even trying to understand the point? Flash became the de-facto web video standard *because* you couldn't rely on having RealPlayer, Windows Media or Quicktime being installed and have the codec in question. Just using whatever codecs are on any given machine leads down exactly the same path.

      It all depends on the time frame.

      See, OS X already has H.264 support out of the box. Windows 7 has it out of the box. The biggest problem is that neither XP nor Vista do (and Linux issues will be ignored in any case).

      Now, any HTML5-based streaming service is going to be "experimental" until there's IE support for this. Even if IE drops down below 50%, it's still too big. And that support will most likely come, eventually, but if past history is anything to go by, it'll take a few more years. Again, looking at the trends, it would seem that Win7 would be the dominant Windows OS by then...

      So, effectively, by the time you can get VIDEO element working in most major browsers, most OSes will have H.264 out of the box. For the remaining few - well, they'll just go and download the codec - most likely from Google, provided for free - and that's it. Not really any different from Flash (which still requires a one-time download).

    27. Re:Just open up the video architecture by shutdown+-p+now · · Score: 1

      The only argument that has any meaning is the first one:

      "Probably most important: we want to focus our energy on promoting open unencumbered codecs at this time."

      All the rest of them don't make any sense from technical standpoint. That only Win7 has H.264 support of all Windows versions is irrelevant, because by the time VIDEO element is actually in widespread non-beta use, Win7 will take the majority. The claim about "highly variable quality of codecs" is irrelevant, since we're talking specifically about H.264 here, which is likely to come in a single "official" implementation. And so on.

      In fact, all these points equally apply to e.g. GStreamer on Linux, so I take it to mean that Firefox won't use GStreamer there either. Well, good luck with that, given that recent Opera for Linux alphas already spot GStreamer support.

    28. Re:Just open up the video architecture by Billly+Gates · · Score: 1

      They can't use h.264. Its owned by someone else.

      Thats what people do not get. If you want h.264 use IE or pay for a license. Linking is just as liable as coding a patent. Just research DVD Jon? Mozilla may even have to cripple their own browser. The MPAA lawyers are crazy enough to do this if you look at their past.

    29. Re:Just open up the video architecture by BenoitRen · · Score: 1

      That only Win7 has H.264 support of all Windows versions is irrelevant, because by the time VIDEO element is actually in widespread non-beta use, Win7 will take the majority.

      Given that web browsers are already implementing the video element, and sites are starting to use it, I don't think this would take that long. Furthermore, you don't know if Windows 7 will have the majority by then. Windows Vista, anyone?

      Yeah, Vista had a lot of bad publicity. But you can't really make predictions in this field, especially now. There's a huge installed base of Windows XP computers currently, and for most people Windows XP is good enough. Combine that with the recession possibly affecting the purchase of new computers, the rising availability of GNU/Linux in stores, and I don't think it's too far-fetched to say that Windows 7 will not necessarily take the absolute majority.

      In fact, all these points equally apply to e.g. GStreamer on Linux, so I take it to mean that Firefox won't use GStreamer there either.

      Actually, they're working on that. Search Bugzilla.

    30. Re:Just open up the video architecture by shutdown+-p+now · · Score: 1

      Actually, they're working on that. Search Bugzilla.

      It looks like they want to deliberately omit this feature from desktop builds, so as to not "tempt" the users into installing "bad" codecs.

    31. Re:Just open up the video architecture by bill_mcgonigle · · Score: 1

      Thats what people do not get. If you want h.264 use IE or pay for a license.

      If you have Windows 7 or OSX you've already paid the license fee.

      Linking is just as liable as coding a patent.

      Where do you get from from? Mozilla has been enabling the Quicktime Plug-In, since... let's see... forever. This isn't an accepted license like GPL.

      Just research DVD Jon?

      Huh? That's a matter of paying license fees.

      Mozilla may even have to cripple their own browser. The MPAA lawyers are crazy enough to do this if you look at their past.

      What does the MPAA have to do with this, I thought the MPEG LA was the governing authority?

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    32. Re:Just open up the video architecture by hazydave · · Score: 1

      It would be for two reasons. For one, the big problem with the Flash Player hasn't been that it's a plug-in, but that it was a proprietary, closed source, even closed spec thing. A big mystery, and something very difficult to replace with a similar plug-in from another company, much less open source. Defaulting to OS video CODECs is nowhere near as complex. Even if H.264 has to be licensed, it's an international standard -- nothing's hidden, you just have to pay the patent people. That IS a big difference already.

      Also, with Flash, you define the whole player architecture based on this one plug-in. For HTML5, using a system video CODEC changes nothing about interactions between user and browser, just the kind of video that can be played from within the browser.

      Video users are used to different video plug-ins. It's a standard OS piece, like a device driver, not something bound to just one guy's web browser, either. Far less objectionable, IMHO, than something like Flash. Supporting these frameworks, Video for Widows, DirectShow, Quicktime, gstreamer, etc. was a big step forward for video integration is operating systems. "Built-in" on the browser is a big step backward... it makes the browser big and stupid again, unable to move with video technology advances.

      Second one is that Theora could very definitely be included, free (at least until someone turns up a patent it offends that hasn't expired yet), ideally also as an OS-level CODEC. That's actually somewhat superior to "hidden within the web browser", as it allows that piece to also be something replaced, improved, accelerated... and used for other purposes. If it's installed by default, I could immediately crank out a Theora video, upload it to my web site, and be serving up video. This very much would help popularize its use.

      This also opens the way for the industry and web community to ultimately decide which forms should be popular, rather than saying, use for these formats (Theora, H.264), but hey, any other format (MPEG, Dirac, etc) and you're still forced, forevermore, to use a browser plug-in.

      --
      -Dave Haynie
  6. Re:HTML5 Video by porneL · · Score: 4, Informative

    Remember that Opera proposed video element in the first place and they've chosen Theora from the start. They're not fond of patents, and may not want to choose H.264, especially if Mozilla doesn't.

  7. Re:HTML5 Video by Pinky's+Brain · · Score: 3, Insightful

    Ugh, quicktime ... I'd even rather have flash.

  8. Oh please. by Anonymous Coward · · Score: 0, Interesting

    Just throw a DirectShow interface at the video player and quit shipping codecs.

    Let the user decide what codecs they want to install and allow the sites to choose what encoding mechanisms they wish to use.

    Not everyone requires free software. Some are prepared to pay a reasonable price for a product they select.

    1. Re:Oh please. by sopssa · · Score: 1

      I was going to comment on this if you really want to bring the codec hell to web too, but you are actually after something if they use XviD or other widely available codecs.

      But nevertheless, linux zealots coming in 3.. 2.. 1..

    2. Re:Oh please. by BZ · · Score: 1

      I assume you did read the articles? They do discuss this, you know.

    3. Re:Oh please. by jedidiah · · Score: 0, Flamebait

      Codec hell? What Codec hell? If I try to play something new, my OS will go and
      automagically fetch what I need and install it for me. Perhaps you run a Lame
      OS like Windows and view this situation as a problem.

      Perhaps you should use a less lame OS.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:Oh please. by mister_playboy · · Score: 0, Troll

      But nevertheless, linux zealots coming in 3.. 2.. 1...

      I'd start the countdown for MS zealots incoming, but it seems you've already arrived.

      --
      Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
    5. Re:Oh please. by Goaway · · Score: 1

      No, they just make weak excuses for why not to do this. None of their arguments hold water. In short:

      They say there is not support on every machine. But how is that worse than the current situation where they have no support on any machine?

      They say it codecs are badly written, and will cause problems. But they already load badly written code in several different ways, and that never was an argument against extensions or plugins, so why is it an argument now?

      They say codecs can have security issues. But once again, they already happily load plugins and extensions which also have security issues, so this argument is hypocritical too.

    6. Re:Oh please. by Anonymous Coward · · Score: 0

      > 4 digits Slashdot ID
      > Retarded argument
      > Complete disregard for reality.

      What does it feel like, being a hikikomori for roughly a decade?

    7. Re:Oh please. by BZ · · Score: 1

      > But how is that worse than the current situation where they have no support on any machine?

      Because right now you don't have a situation where someone writes a web page, it works fine on their computers, and then breaks on 60% of computers out there. That's really not a good situation to be in.

      > But they already load badly written code in several different ways, and that never was an
      > argument against extensions or plugins

      Oh, it's an argument against both. If they weren't quite as established as they are right now, in today's security climate they would be done _very_ differently.

      Note that there's ongoing work to sandbox extensions to some extent and to move plugins to a diffferent, sandboxed if possible, process. Also note that there is code in place to blacklist extensions and plugins if they're being exploited and not being fixed. One could do the same for codecs, of course, but it's really just making the best of a bad situation.

    8. Re:Oh please. by Goaway · · Score: 1

      but it's really just making the best of a bad situation.

      A bad situation is exactly what we have. Making the best of it is what should be done, no?

    9. Re:Oh please. by BZ · · Score: 1

      Yes, if by "bad situation" you mean "lack of a sane unencumbered format for web video". The question is whether having all browsers support an encumbered format Right Now is the best way to make the best of that bad situation.

    10. Re:Oh please. by jedidiah · · Score: 1

      Lie to yourself all you like.

      It doesn't hurt me in the end.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    11. Re:Oh please. by shutdown+-p+now · · Score: 1

      But nevertheless, linux zealots coming in 3.. 2.. 1..

      What "linux zealots"? Linux users are just as interested in this, only for them it would be GStreamer instead of DirectShow. Ditto for OS X users, who'd want QuickTime support.

      Any multimedia application should use the standard OS/DE services to discover and use media codecs, on any platform, period. Any excuses are either because of technical ineptitude, or political POV-pushing. In case of Firefox, they have already explicitly acknowledged it to be the latter, putting them squarely in the same moralistic camp as RMS "you're evil if you use non-free stuff, and I'll do everything I can to force you to be good" camp (as opposed to OSI etc).

  9. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Troll? Everything he commented on was covered in the linked article.

  10. So are Google and all the bunch just dumb? by bogaboga · · Score: 1, Insightful

    Indeed, even distributing H.264 content over the internet or broadcasting it over the airwaves requires the consent of the MPEG-LA, and the current fee exemption for free-to-the-viewer internet delivery is only in effect until the end of 2010. These license fees affect not only browser developers and distributors, but also represent a toll booth on anyone who wishes to produce video content."

    So Google, Apple and all the rest who are implementing the video tag are just dumb? Someone enlighten me please.

    1. Re:So are Google and all the bunch just dumb? by furball · · Score: 2, Insightful

      No, they just have money.

    2. Re:So are Google and all the bunch just dumb? by Anonymous Coward · · Score: 0

      "So are Google" should be "So is Google" because "Google" is singular, not plural. You have been enlightened.

    3. Re:So are Google and all the bunch just dumb? by BZ · · Score: 4, Interesting

      Google is not dumb. One major effect of a broadcast licensing fee for all web video is to make it harder to set up a Youtube competitor. Sure, Google has to pay the fee too. But it might well be worth it to them given the stifling of potential competition.

    4. Re:So are Google and all the bunch just dumb? by Rockoon · · Score: 1, Troll

      Mozilla has money too. A lot of money.

      They've had no problem using patented technology in the past (such as GIF) so clearly the arguement is not against patented technology, but instead against licensing fee's.

      Well fuck you, Mr PleaseSendUsMoneySoThatWeCanMakeFirefoxBetterWhileIGiveMyselfABigFatBonus. H.264 support would, by definition, make FireFox better.

      --
      "His name was James Damore."
    5. Re:So are Google and all the bunch just dumb? by Draek · · Score: 1

      They've had no problem using patented technology in the past (such as GIF)

      As far as I can remember, any and all patents covering *viewing* GIFs were long expired, and the only ones that remained were a bunch covering *creating* GIFs and, therefore, Mozilla was in the clear. Not so here, where even decoding h.264 is illegal without the appropiate, oh-so-bloody-expensive license.

      --
      No problem is insoluble in all conceivable circumstances.
    6. Re:So are Google and all the bunch just dumb? by mister_playboy · · Score: 1

      They would be more meaningful if they actually made money on Youtube. They certainly have lots of mind share, but it's been a nothing but red ink on their balance sheets.

      --
      Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
    7. Re:So are Google and all the bunch just dumb? by Rockoon · · Score: 1

      As far as I can remember, any and all patents covering *viewing* GIFs were long expired, and the only ones that remained were a bunch covering *creating* GIFs and, therefore, Mozilla was in the clear.

      Wrong. You remember clearly that there were no licensing issues with reading and displaying GIF's, and that was true.. but that wasn't because it did not require patented technology.

      Unisys, the owners of the LZW patent, simply did not require licensing on that end of it. Thats it. It was still patented and proprietary, and Unisys could have changed the terms at any time (and in fact on several occasions they did change their terms.)

      This is another reason that Theora isnt any better. Xiph.org can change the terms on the patents they own at any time. Its just as proprietary as H.264 in that regard, but unlike H.264 (finalized in 2003) its still a work-in-progress, and represents a moving target that may end up using even more patents (or even more patent holders!/i>) that extend out for a much longer timeframe than the H.264 patents.

      --
      "His name was James Damore."
    8. Re:So are Google and all the bunch just dumb? by Al+Dimond · · Score: 1

      Usually when a software company licenses a patent they pay some amount and have the right to distribute binaries implementing the patented methods. Mozilla distributes its source code under the LGPL. It's unlikely that Mozilla could arrange a deal under which they're allowed to distribute source code to users and provide users the right to redistribute it freely for any amount of money.

      This is the general problem with Free Software and patents.

    9. Re:So are Google and all the bunch just dumb? by Anonymous Coward · · Score: 0

      Xiph.org do not own any patents as far as I know.

      It just doesn't matter anyway. GPL and LGPL take care of those issues.

    10. Re:So are Google and all the bunch just dumb? by cortana · · Score: 1

      Did Unisys ever persue Mozilla (or a downstream recipient) for patent infringement?

    11. Re:So are Google and all the bunch just dumb? by FrostedWheat · · Score: 2, Informative

      Wrong. On2's (soon to be Google's) patents on VP3 / Theora are totally harmless:

      On2 also made an irrevocable, royalty-free license grant for any patent claims it might have over the software and any derivatives

    12. Re:So are Google and all the bunch just dumb? by arose · · Score: 1

      So Google, Apple and all the rest who are implementing the video tag are just dumb? Someone enlighten me please.

      As far as I'm aware Google and Apple are the only ones implementing the video tag with H.264. Mozilla and Opera along with Google are implementing it with Theora. Who are "all the rest"? Enlighten me please.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    13. Re:So are Google and all the bunch just dumb? by horza · · Score: 1

      Google happened to inherit a large archive of H.264 in the form of YouTube, and so for them it is a short-term convenience. Apple hold plenty of patents on H.264 and expect to get rich from it. None of this is to do with what is good for the consumer.

      Phillip.

    14. Re:So are Google and all the bunch just dumb? by Anonymous Coward · · Score: 0

      Another way to look at it: Any potential competitor could implement a video site based on Theora instead of H.264 and save itself the licensing fees, putting itself at an economic advantage ahead of Youtube.

    15. Re:So are Google and all the bunch just dumb? by Cyberllama · · Score: 1

      Firefox has implemented the video tag. It just only works with ogg.

    16. Re:So are Google and all the bunch just dumb? by Zero__Kelvin · · Score: 1

      "So Google, Apple and all the rest who are implementing the video tag are just dumb? Someone enlighten me please."

      No problem. Just sit and breath. Repeat the first sentence you wrote over and over in your mind until the question mark turns into a lightbulb above your head, and poof you will be enlightened about H.264 and its suitability as an open standard.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    17. Re:So are Google and all the bunch just dumb? by Anonymous Coward · · Score: 0

      So Google, Apple and all the rest who are implementing the video tag are just dumb? Someone enlighten me please.

      Quite the opposite actually. Here's the plan:

      1) Use your YouTube base to push for H.264 knowing Mozilla can't follow
      2) Marginalize Firefox so that Chrome can become the default web browser
      3) ???
      4) Profit!

      They're basically using the open source community to create their ultimate spy-ware browser, and at the same time giving a patents/features crippled code back.

      ffmpeg is how Chrome displays H.264, yet their license does not extend to Chromium or any derivative of that browser.

      "Oh, that's a shiny browser you have there Chromie-a-lot, wait, what? doesn't play YouTube videos? so long! Back to Chrome for me". In some sense it's AB MySQL all over again.

      I hate to say this, but maybe RMS had a good reason for GPLv3.

    18. Re:So are Google and all the bunch just dumb? by wvmarle · · Score: 1

      Not if that competitor is somewhere in Asia, for example. Or in almost any country in Europe. Or where-ever those patents are not valid, Canada may be an option as well. Then they do not have to pay said fee, and can still use h.264 as encoding format.

      Now I know the vast majority of large international Internet companies are founded in the USA but that doesn't mean outside of the US there is no chance for those. Maybe some US investors would even like to invest abroad to set up such a competitor.

    19. Re:So are Google and all the bunch just dumb? by BZ · · Score: 1

      > Not if that competitor is somewhere in Asia, for example.

      H.264 is covered by patents granted in Japan, China, South Korea, Hong Kong, Singapore, Taiwan, India. I didn't look for others; there might be more.

      > Or in almost any country in Europe.

      Covered by patents granted in Germany, France, UK, Finland, Italy, Sweden, Belgium, Bulgaria, Liechtenstein, Austria, Czech Republic, Denmark, Spain, Hungary, Ireland, The Netherlands, Poland, Romania, Portugal, Slovenia.

      > Canada may be an option as well

      It's not. Plenty of patents on H.264 granted in Canada.

      Oh, not on the above lists, but also places where H.264 is patent-encumbered: Australia, Mexico.

      Oh, and I stopped on page 6 of the 45-page list of patents. There might be a few other countries hiding in there.

      Source: http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx

      I think it would be pretty difficult to be a major Youtube competitor without having any operations in any of the countries above, in the near term. Heck, just finding some place not on the list that have the right bandwidth to places with the rich viewers who are worth targeting with ads (generally the US and Europe at the moment) might be hard enough.

  11. lame :P by Anonymous Coward · · Score: 0

    lame :P

  12. Good point here... by rinoid · · Score: 1

    I have to admit though, H.264 kind of rocks in quality, but; we need open streams and open formats.

  13. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Rrrriiiiggghhtt ... QuickTime is worse than Flash. It takes more resources, crashes constantly, and is slow as hell. Yep. Sounds like reality to me.

  14. Vorbis and MKV by Anonymous Coward · · Score: 2, Insightful

    I must be stupid.

    Ogg/Vorbis/Theora are unencumbered and free. No "deals" need to be worked out.
    Ogg/Vorbis/Theora has reasonable quality and compression.
    It can be placed into a MKV container http://matroska.org/, also unencumbered and free.

    Why would any end user select anything other than Theora/Vorbis codecs when given the choice? Google and Youtube have an opportunity to "don't be evil" and put an end to proprietary codecs being the default media format. It won't alter anything in the proprietary world, since they will always insist on DRM.

    When was the last time you heard an end user happy about DRM? Well, when? NEVER.

    Come on google, step up. Use Theora/Vorbis and MKV containers to significantly reduce the hold that proprietary formats have on your FLOSS OS using customers. Heck, if you do, I'll even stop using Scroogle .... maybe. Further, Apple and Microsoft can use the same codecs under the same terms that you or I can. For FREE. Talk about fair.

    1. Re:Vorbis and MKV by Chaos+Incarnate · · Score: 4, Insightful

      You're missing one important point: Google already has all these videos in H.264, so serving them up is relatively painless. They'd have to go back and reencode the entire YouTube library if they wanted to offer it in Theora.

      --
      Benford's Corollary to Clarke's Law: "Any technology distinguishable from magic is insufficiently advanced."
    2. Re:Vorbis and MKV by sopssa · · Score: 4, Informative

      Ogg/Vorbis/Theora are unencumbered and free. No "deals" need to be worked out.
      Ogg/Vorbis/Theora has reasonable quality and compression.
      It can be placed into a MKV container http://matroska.org/, also unencumbered and free.

      You are kind of comparing wrong things here. Both MKV and Ogg are merely containers (and H.264 can be placed inside MKV container too, and is usually done so).

      Also, Theora and H.264 aren't technically equivalent. Theora is kinda there, but it misses many features, is more heavy on hardware and requires a larger bitrate to get the same results. It also completely misses support for B-frames, variable frame rates, interlacing, and larger than 8-bits bit-depths. It also loses out because the creators have chosen to maintain backwards compatibility in cost of being technically superior.

      Another thing that manages to create more support for H.264 is that blu-ray, PS3, DVB (digital television in europe, including cable) and several other services and devices already support it.

    3. Re:Vorbis and MKV by Anonymous Coward · · Score: 0

      Why would any end user select anything other than Theora/Vorbis codecs when given the choice?

      Umm, because the quality of H.264 beats the crap out of Theora? Go do your homework and learn something about this before asking utterly stupid questions like that. Thanks.

    4. Re:Vorbis and MKV by Anonymous Coward · · Score: 3, Informative

      It's the patent minefield that is preventing theora from becoming the vorbis of video codecs. The developers can't implement some features, like those you've listed, for risk of patent litigation. It's not about backward compatibility.

    5. Re:Vorbis and MKV by Antiocheian · · Score: 1

      Someone else will then. Serving video to Firefox users is not an opportunity to be missed if YouTube can't.

    6. Re:Vorbis and MKV by slim · · Score: 1

      They'd have to go back and reencode the entire YouTube library if they wanted to offer it in Theora.

      It honestly wouldn't surprise me if they were quietly doing this as a background task, just in case.

      It would cost them storage, and processing time - they may have offpeak cycles free. It would put them in a position where they could switch to Theora more easily, should they decide to.

      Or they could throw it all away. Depends how the ecosystem develops.

      Another solution would be one where they serve you Theora if they have it, and fall back on something else if they don't. Not ideal, but possible to deliver sooner.

    7. Re:Vorbis and MKV by Zencyde · · Score: 1

      If anyone has the processing cycles for such an endeavor, it's Google.

      --
      What day is it? Could you please tell me?
    8. Re:Vorbis and MKV by tepples · · Score: 1

      They'd have to go back and reencode the entire YouTube library if they wanted to offer it in Theora.

      They had to do so anyway when they upgraded to support devices that can play H.264 but not the earlier version of FLV, such as iPod Touch.

    9. Re:Vorbis and MKV by jensend · · Score: 1

      Theora is definitely not heavier on hardware than H.264- unless you have dedicated hardware support for H.264 (GPU or Broadcom chip/other specialized DSP). It's a simpler codec and so its (fairly narrow) quality/bitrate disadvantage comes with a decoding speed advantage. There's nothing keeping people from doing hardware-accelerated Theora (should be possible to do on DX9 or higher gpus, simple to do with CUDA or OpenCL, and would be possible on a lot of DSPs if they opened up some documentation) . However, since Theora's decode requirements are significantly lower than H.264's, the only market where hardware-accelerated decoding would AFAIK make much of an impact is smartphones.

    10. Re:Vorbis and MKV by arose · · Score: 2, Informative

      Theora is kinda there, but it misses many features, is more heavy on hardware and requires a larger bitrate to get the same results.

      Any benchmarks out there comparing Theora and H.264 CPU only encoding and decoding? Visual quality for web video only need to be "good enough".

      It also completely misses support for B-frames, variable frame rates, interlacing, and larger than 8-bits bit-depths.

      True, completely false and the last two are irrelevant for web video.

      Another thing that manages to create more support for H.264 is that blu-ray, PS3, DVB (digital television in europe, including cable) and several other services and devices already support it.

      Again, mostly irrelevant for web video. If you are going to talk about hardware support you talk mobile phones, many of which have hardware H.264 decoders. That is the biggest advantage H.264 has over Theora for web video, but if MPEG LA decides to charge content providers and actively enforce it, then even that can't make enough difference for smaller players.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    11. Re:Vorbis and MKV by sopssa · · Score: 1

      Visual quality for web video only need to be "good enough".

      I disagree, I think that's something to say only because the technology is so new. It wasn't many years ago that YouTube came out but it used to be really shitty quality. It was remarkable when they introduced 720p videos.

      Why should web video only be "good enough"? Why not same as on desktop? Even more so because streaming from web is becoming commonplace now. The bandwidth is already there (even in US, and you can easy scale this to support all kinds of bandwidth)

      Since we are introducing major standards here that will show the route for years, why not do it the best way we can now?

      Just see what IE's "good enough" standard handling has done to web standards. Let's not take that route again, please.

    12. Re:Vorbis and MKV by Tellarin · · Score: 1

      The new "unified" ISDB-T standard (Japanese/Brazilian digital tv) also uses H.264.

    13. Re:Vorbis and MKV by Anonymous Coward · · Score: 0

      I have the same preference as you: theory and vorbis all the way, but the dark side is strong! Download handbrake and encode a DVD into a fixed size of your choosing, first using vorbis & theora, and then (to the same size) using aac & h.264. The difference isn't subtle h.264 looks considerably better.

      I personally would much prefer to have the freedom that goes with theora & vorbis. It opens up so many more opportunities for unencumbered technological progress.

      I hope Firefox sticks to it's free software principles. There's plenty of revved-up proprietary browsers running patented-tech for those who don't care for software & information freedom.

    14. Re:Vorbis and MKV by ObsessiveMathsFreak · · Score: 1

      It's not about the reencode time. Google has more than enough resources to reencode every youtube video in existance twice over if they choose that route. It's about the bandwidth.

      The fact is, Google offers video on a colossal scale. Remember all those statistics about Youtube being 10% or so of web traffic. Perhaps an exaggeration, but there is no doubt that Google is shovelling a lot of bits around every day. 5%-15% of that saved on H264s better compression ratio means Google is quite prepared to sink open video formats if it can save some money on its bandwidth costs.

      Google is a web service company. Their browser business with Chrome is a sideline. The same goes for Apple, hardware and Safari. Unfortunately, the presence of these two browsers has given both companies a seat at the W3C video tag table, where they have proceeded to sink the sanest solution for web video in order to benefit their other commercial interests. This is what happens when big business decides industry standards. We lose.

      --
      May the Maths Be with you!
    15. Re:Vorbis and MKV by arose · · Score: 1

      When I say "good enough", I don't mean good enough for postmark size. Thusnelda is good enough for anything you could realistically stream (bandwidth for full HD is not there yet by a long shot, no matter what the numbers in the ads say). There is a reason why JPEG 2000 hasn't gone anywhere even with digital cameras commonly being over 10 megapixels, JPEG is good enough and not a patent minefield.

      Theora is the best we can do right now if licensing issues are not ignored. In a few years the average computer might be able to handle Dirac, but we aren't there yet.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    16. Re:Vorbis and MKV by Anonymous Coward · · Score: 0

      Also, Theora and H.264 aren't technically equivalent. Theora is kinda there, but it misses many features, is more heavy on hardware and requires a larger bitrate to get the same results.

      That's a good argument. Too bad it's completely wrong. Theora is lighter on the hardware than h.264 with the notable exception of encoding and it provides better video quality than h.264 with the exact same file size. There are countless comparisons floating around and not a single one backs what you just stated.

    17. Re:Vorbis and MKV by fredma123 · · Score: 1

      Yeah, the problem is, Theora had to get around patents so they had to use less efficient algorithms. So the question is whether you want the best solution, or the open-source solution. I mean, I love open-source software, but unfortunately, H.264 just does beat it in several ways.

    18. Re:Vorbis and MKV by slim · · Score: 1

      Xiph, at least, would question the assertion that H264 has a better compression ratio.

      It's an assertion that's repeated so often, I think it's worth reminding ourselves that maybe it's not true.

    19. Re:Vorbis and MKV by Anonymous Coward · · Score: 0

      Someone else will then. Serving video to Firefox users is not an opportunity to be missed if YouTube can't.

      Enter dailymotion.com.

    20. Re:Vorbis and MKV by bit01 · · Score: 1

      you want the best solution, or the open-source solution.

      The two are not mutually exclusive.

      H.264 just does beat it in several ways.

      Not by much and not when you include the license. The license is an important technical characteristic of any piece of software, particularly when you want to make billions of copies of it.

      ---

      WGA. Guilty until proven innocent. For millions. Again and again.

  15. Why not both? by FrostedWheat · · Score: 1

    None of this would matter if the sites provided both formats. Chrome and Safari could have their H.264, everyone else could have the Theora version. Everyone wins.

    1. Re:Why not both? by TechnoFrood · · Score: 3, Insightful

      Everyone wins.

      Well apart from anyone who wants to host video on the web, who will have to either transcode on the fly (is that even possible?), or store 2 copies of the video, taking up around twice the space (assuming both formats produce the same filesize for the same quality , which as I understand they don't). And then what happens when Microsoft brings out IE X.X (Now with HTML5 video tag support!) which will only play back wmvs, thus requiring a third copy of the file.

    2. Re:Why not both? by FrostedWheat · · Score: 1

      Which is exactly why Theora and Vorbis where in the original HTML5 spec. You can thank Nokia and Apple for that mess.

    3. Re:Why not both? by Akral · · Score: 1

      None of this would matter if the sites provided both formats. Chrome and Safari could have their H.264, everyone else could have the Theora version. Everyone wins.

      And Google has to double it's storage space. :)

      --
      Don't worry, be happy!
  16. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Quicktime Alternative is a bit better and lets you save thhe files too.

  17. FFmpeg by argent · · Score: 1

    Since the LGPLed FFmpeg library supports H.264 among other codecs, all they need to do is support it as a plugin. They can ship Firefox with a version compiled without "--enable-gpl" and without "--enable-nonfree".

    1. Re:FFmpeg by Jahava · · Score: 4, Informative
      Just because there's an LGPL project supporting something doesn't mean that patents and licenses don't apply. For more information about this, read the FFMPEG FAQ.

      Mozlla's concerns don't seem related at all to the implementation of the video. Rather, they're concerned about the licensing issues related to their usage of it. According to the article (and the summary, at that), the only reason H264 is even legally embeddable in current software is due to a free-to-viewer clause, and even that may permanently expire in 2010.

      Currently, most of the web (Flash excluded) is free to generate. I can make an HTML document, or a tool to generate HTML documents, and render those HTML documents without paying or owing anybody anything. To legally generate H264 files, you must pay for a license. To build software that generates H264 files, the software company must pay for a license. And (possibly) after 2010, a viewer or viewer software may have to pay for a license to watch the content. These are some pretty huge issues to overcome.

    2. Re:FFmpeg by GreatBunzinni · · Score: 2, Informative

      That may be correct in a technical point of view and a very simple solution to this problem. Unfortunately, the world is a bit more complex than that, thanks for the mess of convoluted rules which each jurisdiction imposes on it's citizens. In this case, if you take a look at ffmpeg's patents min-FAQ" you will notice the following disclaimers:


      Q: Does FFmpeg use patented algorithms?
      A: We do not know, we are not lawyers so we are not qualified to answer this. Also we have never read patents to implement any part of FFmpeg, so even if we were qualified we could not answer it as we do not know what is patented. Furthermore the sheer number of software patents makes it impossible to read them all so no one (lawyer or not) could answer such a question with a definite no, those who do lie. What we do know is that various standards FFmpeg supports contain vague hints that any conforming implementation might be subject to some patent rights in some jurisdictions, examples for such statements are:
      For H.264:

              ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.

      Q: Is it safe to use such patented algorithms?
      A: Patent laws vary wildly between jurisdictions, and in many countries patents on algorithms are not recognized. Plus the use of patents to prevent the usage of a format or codec on a specific operating system or together with specific other software might violate antitrust laws. So whether you are safe or not depends on where you live and how judges interpret the law in your jurisdiction.

      So, although ffmpeg supports H.264 and other patent-encumbered formats, it does so in spite of the patents that affect the implementations. As a consequence, they make it clear that if you rely on ffmpeg then you are at your own risk. And needlessly putting yourself at risk is never a good thing.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    3. Re:FFmpeg by argent · · Score: 1

      Yes, I read the patent page too. If you compile ffmpeg with the options I listed, you're not going to be using any such algorithms. If you provide a general plugin mechanism and ship a non-encumbered version of FFmpeg then people are free to license other codecs on their own.

    4. Re:FFmpeg by argent · · Score: 1

      Currently, most of the web (Flash excluded) is free to generate. I can make an HTML document, or a tool to generate HTML documents, and render those HTML documents without paying or owing anybody anything. To legally generate H264 files, you must pay for a license. To build software that generates H264 files, the software company must pay for a license. And (possibly) after 2010, a viewer or viewer software may have to pay for a license to watch the content. These are some pretty huge issues to overcome.

      Why would you use H.264 instead of Ogg Theora to create your videos? What we're talking about here is how you would play videos created by someone like Youtube. The standard doesn't mandate H.264. It just fails to mandate Ogg.

    5. Re:FFmpeg by GreatBunzinni · · Score: 2, Interesting

      The need to "license other codecs" is exactly the problem. You shouldn't be forced to pay a toll to be able to perform basic, every day tasks such as watching web videos, particularly when you are supposed to be following an international standard. You aren't forced to deal with any of that crap if you happen to rely on a format which is patent-free. And that's why Mozilla is pushing for Theora, which is clearly the best solution to this absurd problem.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    6. Re:FFmpeg by argent · · Score: 2, Insightful

      I entirely agree with you, however it's irrelevant to the fact that if Mozilla doesn't provide a way for people to license other codecs if they want they're going to watch their market share go back to where it was ten years ago.

      Right now there's two bad choices if you want to watch Yotube videos. You can use a proprietary plug-in that's already had a devastating effect on web usability (to the point where one of the most popular browser plugins is Flashblock), or you can use an open API that incidentally requires you to have a license for the video codec that Youtube chose to use. Almost all end-users already have licensed versions of this codec in their video cards and media players, AND hooks that let you use these implementations from the browser. Using those hooks, including FFMpeg, will let people use HTML5 video on Youtube without anyone being subject to patent lawsuits.

    7. Re:FFmpeg by slim · · Score: 4, Insightful

      Why would you use H.264 instead of Ogg Theora to create your videos? What we're talking about here is how you would play videos created by someone like Youtube. The standard doesn't mandate H.264. It just fails to mandate Ogg.

      If you only put Theora videos on your site, they won't be viewable in Safari (using default Quicktime components), iPhone or Android.

      Professor Markup says:

      There is no single combination of containers and codecs that works in all HTML5 browsers.

      To make your video watchable across all of these devices and platforms, you’re going to have to encode your video more than once.

      As long as there are mainstream platforms that don't support Theora, either you have to encode to H.264 yourself (and pay) or have someone else (e.g. YouTube) encode and host it for you.

    8. Re:FFmpeg by chilvence · · Score: 1

      I disagree, if no one is prepared to put themselves at risk to see just what happens in the real world, then we end up in the situation we are in now, where the software patents are 100% effective at stifling the motivation of the competition. If people are afraid to even freely take code that is available and use it, then something is very wrong with the picture...

      Let's say Mozilla did use ffmpeg to sidestep the whole licence issue - at the very least, it would force the mpeg group to get off their perch and get their hands bloody, then we'd see the true colours eh?

    9. Re:FFmpeg by argent · · Score: 1

      If you only put Theora videos on your site, they won't be viewable in Safari (using default Quicktime components), iPhone or Android.

      If you install the Xiph Quicktime components you will be able to view them in Safari. Supporting locked platforms like the iPhone, Android, or WebOS is a matter of your personal ethics. I personally file it in the same bin as supporting software patents myself.

    10. Re:FFmpeg by mad.frog · · Score: 1

      Currently, most of the web (Flash excluded) is free to generate.

      Err, SWF *is* completely free to generate, aside from the patent-encumbered video codec parts (H.264 and Sorenson) and maybe the MP3/AAC audio codecs. Here's the spec, go to it:

      http://www.adobe.com/devnet/swf/pdf/swf_file_format_spec_v10.pdf

      Here's a website full of open-source tools for it:

      http://osflash.org/

      (And about the "yeah-but-audio-video-patents" exceptions -- hey, don't blame Adobe for that. They don't even hold those patents, they have to pay big bucks for 'em too!)

    11. Re:FFmpeg by ObsessiveMathsFreak · · Score: 1

      If you only put Theora videos on your site, they won't be viewable in Safari (using default Quicktime components), iPhone or Android.

      How tragic.

      --
      May the Maths Be with you!
    12. Re:FFmpeg by Anonymous Coward · · Score: 0

      If you only put h264 videos on your site, they won't be viewable in Firefox.

      As long as there are mainstream platforms that don't support h264, either you have to encode to theora yourself (and do not pay) or have someone else encode and host it for you.

    13. Re:FFmpeg by ducomputergeek · · Score: 1

      There aren't any hardware encoders/decorder chips that support Ogg is the main reason. And smart phones like the iPhone and Android use dedicated h.264 processors to decode and play video. In the case of the cell phones, the hardware manufacture is the one paying for the license, so it is included in the cost of the chip. And I believe the cap for licensing is $2.5M per year. Granted it was 2007 when I last looked at the MPEG-LA licensing terms.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    14. Re:FFmpeg by Anonymous Coward · · Score: 0

      You can use a proprietary plug-in that's already had a devastating effect on web usability (to the point where one of the most popular browser plugins is Flashblock)

      You're saying abnoxious advertising is a web usability problem? Or are you saying you really think people selectively block Flash for UI reasons?

      Bit of a reach to accept the latter, as sites that use Flash for UI almost never provide a no-flash backup. The former is an issue with the site's content.

    15. Re:FFmpeg by Rich0 · · Score: 1

      Just because there's an LGPL project supporting something doesn't mean that patents and licenses don't apply.

      Yes, but they wouldn't be violating anybody's patents if all they did was enabled firefox to utilize ffmpeg if a user has it on their system. Users shouldn't have that installed if they aren't legally allowed to use it anyway. If you must, have firefox prompt the user and ask them "I see that you have software installed that allows h264 videos to be played, hit OK to confirm that you are allowed to play these videos, or hit the disable button to disable this feature." Since anybody can legally purchase a license to play h264 videos in just about any jurisdiction, how is Mozilla to know if that isn't the case?

    16. Re:FFmpeg by Billly+Gates · · Score: 1

      "As long as there are mainstream platforms that don't support Theora, either you have to encode to H.264 yourself (and pay) or have someone else (e.g. YouTube) encode and host it for you.

      Well Firefox now is sizable enough that the reverse is true. If Firefox wont support H.264 then developers will be reluctant to use it. Java has supported H.264 for years so you can write a JavaFX, applet, or flash to display it. That is a whole can of worms altogether.

      Developers want standards but unfortunately its not in their best interest long term to standardize on a patented technology. You will be stuck with proprietary tools, drm, and high barriers of entry for those wanting to have their own sites.

      If its patented it does not belong in a standards body PERIOD. Whats the point of using standards then?

    17. Re:FFmpeg by wvmarle · · Score: 1

      Tragic, yes, as your site is going to lose out to competitors (e.g. Youtube) that DO play on those other devices that you may not care about, and that thus get more mind share and market share with it.

      The true tragic of the Internet is that for many services there is place for only one of each. The biggest. There is no place for a second eBay because they are smaller, offering both less choice for buyers and less customers for sellers. There is only place for one video sharing site (being taken by YouTube), honestly I don't know of any others like it. It's become the default place to share your videos, and the place where you can find the largest audience as publisher and largest choice as consumer.

      In effect there is only place for one standard for video - and that one appears to become h.264. Do not support it and become irrelevant. Publish using something else, and no-one can watch (the time where a link like "please install plugin x here" is still followed and acted upon is long gone), and your site will have no visitors. People do not try again.

    18. Re:FFmpeg by hazydave · · Score: 1

      If you're running Safari, you're already far more locked than any Android user.

      --
      -Dave Haynie
  18. Ideology meet reality by diamondsw · · Score: 3, Insightful

    All of the bitching about the patent/royalty situation ignores the following facts:

    • H.264 is hardware accelerated on nearly every platform, desktop and mobile - Ogg is not.
    • Ogg produces inferior video at the same bitrate as H.264, or larger video for the same quality.
    • YouTube, DailyMotion, and Vimeo have spoken in favor of H.264. Watch the dominoes topple.

    There are two alternatives here - Flash-based video and H.264. Don't kid yourself that Ogg is a third, because it's not going to happen. Time for Mozilla to face reality and pay up the license as Apple and Google have done. Otherwise, watch Chrome really destroy Firefox.

    --
    I don't know what kind of crack I was on, but I suspect it was decaf.
    1. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      you really don't understand open source, do you?

    2. Re:Ideology meet reality by Pinky's+Brain · · Score: 2, Informative

      Flash is H.264.

    3. Re:Ideology meet reality by BZ · · Score: 5, Insightful

      I don't think anyone's ignoring those facts. In particular, no one is under the illusion that ogg is a suitable replacement for h.264 in all cases. The hope is that a better codec than either will appear with more suitable licensing terms; in the meantime a premature standardization on h.264 would hurt the chances of that codec being adopted when it appears, no?

      On the other hand, you seem to be ignoring the fact that Wikipedia, say, has no plans to put its video in H.264 (so Safari, say, can't very well view it).

      > Time for Mozilla to face reality and pay up the license as Apple and Google have done.

      As a side note, Apple and Google did not have to pay for a license separately here. They already had the licenses.

      > Otherwise, watch Chrome really destroy Firefox

      If that were to start happening (and it's nowhere close yet), the calculation might have to change, of course.

    4. Re:Ideology meet reality by ubersoldat2k7 · · Score: 1, Insightful

      I think his point is that Ogg can always be improved to work things out better. It's still a young format and much improvements can be made. So, what happens when H264 includes some bug and they won't fix it? I think you can agree on pretty much everyone hates Flash, and H264 is Flash all over again:

      Your codec doesn't support H.264 v2.6.4.3.2.3.6 please upgrade

    5. Re:Ideology meet reality by Ant+P. · · Score: 4, Insightful

      Time for Mozilla to face reality and pay up the license

      Yeah, that'll happen right after you start paying $5.99 to install the browser.

    6. Re:Ideology meet reality by FooBarWidget · · Score: 1

      And push the license fees down to the users? Is that what you really want?

    7. Re:Ideology meet reality by Anonymous Coward · · Score: 1, Insightful

      Apparently, he doesn't.

      In addition, he seems to believe that Ogg is a video codec instead of a container format. What he probably means is Theora.

    8. Re:Ideology meet reality by Draek · · Score: 1

      Time for Mozilla to face reality and pay up the license as Apple and Google have done.

      Or simply throw a decoder in, and block the Mozilla website to any IP originating from the US. We get shiny new codec, Mozilla doesn't violate the GPL by throwing in additional demands upon their users, and the US goes further down the drain for being the legislative hell-hole that it is, win for all.

      --
      No problem is insoluble in all conceivable circumstances.
    9. Re:Ideology meet reality by GreatBunzinni · · Score: 3, Interesting

      All of the bitching about the patent/royalty situation ignores the following facts:

      • H.264 is hardware accelerated on nearly every platform, desktop and mobile - Ogg is not.

      This is a "chicken Vs egg" problem. There are hardware decoders for Theora out there and the only thing that stops you from getting hardware support for a format is the OEM's decision to add it. Nothing more, nothing less.

      Ogg produces inferior video at the same bitrate as H.264, or larger video for the same quality.

      Sorry, back here in reality Theora's quality is at least on par with H.264 with the same size. But thanks for your attempt at FUD, though.

      YouTube, DailyMotion, and Vimeo have spoken in favor of H.264. Watch the dominoes topple.

      How exactly do "dominoes topple" if not only they can easily support Theora but also it is a very easy way to avoid licensing costs? Support for H.264 is not free, you know? Didn't you even read the part in the summary that reads "the current fee exemption for free-to-the-viewer internet delivery is only in effect until the end of 2010."?

      There are two alternatives here - Flash-based video and H.264. Don't kid yourself that Ogg is a third, because it's not going to happen. Time for Mozilla to face reality and pay up the license as Apple and Google have done. Otherwise, watch Chrome really destroy Firefox.

      Just because you try to repeat "Theora isn't an option" as a mantra of sorts it doesn't mean that it's anything remotely close to true. There is a whole world out there that happens to enjoy watching videos online and no one in their right mind wishes to start paying money to keep doing that, neither the video providers nor the audience. So please pick up your poorly conceived FUD and go waste it elsewhere.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    10. Re:Ideology meet reality by BZ · · Score: 1

      > Or simply throw a decoder in, and block the Mozilla website to any IP originating from
      > the US.

      Given that Mozilla is headquartered in the US, this is not an option.

      Or are you suggesting that they fire most of the employees and relocate elsewhere?

    11. Re:Ideology meet reality by cynyr · · Score: 2, Insightful

      Time for Mozilla to face reality and pay up the license as Apple and Google have done.

      Except the problem is how do you keep the users from redistrubting the code that has how to decode a h264 file? and the users they give it to, and so on? Good luck getting a license from MPEG-LA that grants everyone a license to use it. Also, is Chrome(not chromium) available for linux distros other than debian/ubuntu/redhat/SUSE? slackware? gentoo? LFS? and host of others, see distro watch, because Chromium does not have support for the html5/h264 youtube.

      --
      All of the above was encrypted with a Quad ROT-13 method. Unauthorized decryption is in violation of the DMCA.
    12. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      Thats not going to happen, H264 is an agreed upon standard for video encoding, with all of its features ironed out and standardized years ago, its not a work in progress like flash...

    13. Re:Ideology meet reality by Draek · · Score: 1

      That's still more realistic than paying MPEG-LA, given that pushing additional burdens onto their users goes against the GPL. Still, the final choice is likely gonna be "ship Theora and to hell with MPEG-4". Which, in turn, will make the situation a "Theora or continue with Flash" for everybody else, as Firefox's marketshare is one that website owners cannot afford to ignore, so it's up to Google and Apple to see if they can swallow up their ego and implement a Free standard or not.

      --
      No problem is insoluble in all conceivable circumstances.
    14. Re:Ideology meet reality by selven · · Score: 4, Interesting

      Time for Mozilla to face reality and pay up the license as Apple and Google have done. Otherwise, watch Chrome really destroy Firefox.

      Time for Linux users to face reality and just give up and use Windows, as most other people have done.

      Oh, we didn't do that in 2000 and we have a strong, functioning, free as in freedom operating system now? I wonder how that could have happened.

    15. Re:Ideology meet reality by Tim+C · · Score: 1

      Ogg can always be improved to work things out better. It's still a young format and much improvements can be made... Your codec doesn't support H.264 v2.6.4.3.2.3.6 please upgrade

      So.. Ogg can be improved, which implies the need for the user to upgrade every once in a while, which is fine. Meanwhile, H.264 can require the user to upgrade which is bad?

    16. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      You mean like YouTube did?

    17. Re:Ideology meet reality by TheTurtlesMoves · · Score: 1

      They can't pay the license. MPEG-LA will not provide a license that is GPL compatible at any price.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    18. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      debunk time
      - H264 is hardware accelerated on many platforms; not nearly every. Oh dear, far from it
      - theora is arguably better than h264 in some conditions, and slightly worse in other conditions. all considered, they're quite similar. and theora doesnt have a lot of folks optimizing it like h264.
      - dailymotion supports theora in html5 and firefox plays the videos just fine

      h264 winning means destroying part of our freedom, how do you see it as a good thing? its good for the corporate world (lock in, very high fee requirement to enter the marke), bad for the consumers

    19. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      Yes, because we all go to wikipedia to watch funny video clips or tv shows...

    20. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      The idea would be somebody 'forks' firefox and makes 'Eurofox' or 'nonUSfox' adds the codecs and hosts outside of the US where the h.264 patents do not apply to software. Personally though I'm with mozilla on this, html5 is young enough that the biggest browser implementing it gets a significant say over how it's used, if Mozilla hold their ground google/vimeo/etc will fold because for all the chrome circlejerking, firefox has ~50% market share and chrome+opera+etc have ~5% (IEs share doesn't matter as it isn't going to implement any time soon).

    21. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      Um, mozilla *CAN'T* pay for the license. It's not a legal possibility.

    22. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      Well, as long as the two biggest browsers - Firefox and IE - don't support H.264 based HTML5 video, everybody will stay with Flash video anyway.

    23. Re:Ideology meet reality by arose · · Score: 1

      YouTube, DailyMotion, and Vimeo have spoken in favor of H.264. Watch the dominoes topple.

      Are the two sites named DailyMotion? http://openvideo.dailymotion.com/us

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    24. Re:Ideology meet reality by arose · · Score: 1

      Flash can be H.264, but that's only true for Flash 9. If you want to support Flash 6 and 7 you need Sorenson Spark. If you are content to just support Flash 8 you still need On2 VP6. In short, Flash is Flash, but might play some video formats, Flash 9 and up will play H.264, older versions will not.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    25. Re:Ideology meet reality by TheRaven64 · · Score: 3, Insightful

      Sorry, back here in reality Theora's quality is at least on par with H.264 with the same size [xiph.org]. But thanks for your attempt at FUD, though.

      Someone from Xiph.org isn't exactly an unbiased source - maybe you could cite someone who doesn't have a vested interest in one or the other. If you actually look at the videos on the site, you'll see that Theora performs a fair bit better than H.263 (not surprising; most things do these days), but watching the 17MB files next to each other it's immediately apparent which is which. The colours in the Theora version are washed out and details are fuzzy.

      Now, if Flash would add support for Theora, then GooTube could easily ditch the H.263 versions and serve both Theora and H.264, rather than H.263 and H.264...

      --
      I am TheRaven on Soylent News
    26. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      How exactly do "dominoes topple" if not only they can easily support Theora but also it is a very easy way to avoid licensing costs? Support for H.264 is not free, you know? Didn't you even read the part in the summary that reads "the current fee exemption for free-to-the-viewer internet delivery is only in effect until the end of 2010."?

      H.264 licensing fees are capped at a few million a year for unlimited usage. The big video-sharing sites are already paying the full fees, so using less H.264 doesn't actually lower their costs. Five million dollars a year is nothing to a company like Google anyway. If MPEG-LA goes insane and decides it can try to get users to pay for video players at the end of this year, then great, Theora wins, but I doubt it will happen.

    27. Re:Ideology meet reality by ObsessiveMathsFreak · · Score: 1

      All of the bitching about the patent/royalty situation ignores the following facts:

      It ignores them because they are not relevant. We know H264 is a better codec, has hardware support and is currently in use. That's not the issue.

      The issue is that H264 cannot be used without paying protection money to MPEG-LA. No amount of technical or commercial metrics are going to make this legal issue go away. A long as MPEG-LAs patents on the mathematics of video compression in H264 are upheld, it cannot be used for mass video on the web. Unless you want the only video on the web to be that provided by big vendors like Google/Youtube, and the only way to watch it being on the browser of big vendors like Google, Apple and Microsoft?

      Is that what you want? A pay to play web? Because right now, that's what what you're telling me you want.

      --
      May the Maths Be with you!
    28. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      Video sites will do what's in their interests; However, they cannot ignore Opera and Mozilla's plight. Mozilla have given valid reasons why they can't implement it. They aren't being idealistic, they're being realistic.

      Even if h.264 became the de facto standard, ignoring 30% of browsers is not an option. Should Dailymotion or any other video site support ogv, and YouTube/Video support only 10% of browsers, then what Microsoft does will be decisive. Don't say the battle's over before it's started.

    29. Re:Ideology meet reality by Cyberllama · · Score: 1

      If flash is an alternative, then certainly Ogg is as well. Ogg clearly beats out flash . . . Now you can make an argument about which is the greater evil or greater cost when it comes to Ogg vs H.264 of license costs vs bandwidth costs -- but ultimately its a moot point. This isn't really a case of Ogg vs H.264 -- it's h.264 vs any other free and open alternative.

      Ultimately, there will be something better. If that means a delay in adopting the video tag in html5, then so be it. It's better for everyone in the long run.

    30. Re:Ideology meet reality by GreatBunzinni · · Score: 0, Troll

      Someone from Xiph.org isn't exactly an unbiased source

      That accusation is absolutely irrelevant. The great thing about the scientific process is that no one is forced to blindly swallow any claim. claims such as those made in the xiph.org article can be peer reviewed by anyone who is remotely interested in doing so. That is why everyone who happens to watch the samples provided in that article can easily conclude by themselves that Theora is in fact on par with what h.264 offers, both in file size and image quality.

      But if people like you have any gripe with that then there's also absolutely no problem at all. Instead of throwing vague and baseless accusations which amount to nothing more than personal attacks you can simply inspect how the comparison between Theora and h.264 was made and, from there, find any flaw in it. Any flaw at all will do. If you cannot do that then you still have alternatives available. You can simply perform your own comparison and see for yourself how Theora fairs against h.264. Heck, if you find the results on par with your beliefs you can even release it to the public on some blog which you can easily put up in 2 minutes.

      So, to sum things up, if the comparison presented in that site is remotely as bogus as you claim to be then you should have absolutely no problem whatsoever debunking it by presenting any semblance of objective, measurable proof, either by pointing flaws in Xiph.org's comparison (which, oddly enough, you failed to provide) or even by providing your own comparison to back up your allegations. But oddly enough you failed to do any of that.

      Yet, the odd thing was that instead, the best thing you could come up to try to disprove the article's validity was a regrettable ad hominem attack to try to smear Xiph.org's reputation while avoiding any technical aspect whatsoever. Is that the best you can do to FUD Theora's performance?

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    31. Re:Ideology meet reality by BZ · · Score: 1

      Chrome supports Theora.

      The only major players in the browser market who don't, and who have said they won't are Apple (which is shipping H.264 by default and can have quicktime plug-ins to support theora) and Microsoft (which isn't shipping anything in this space yet).

      That said, Firefox isn't GPL. It's MPL/LGPL/GPL tri-licensed, so it may well be able to legally license H.264 if it really really wanted to. Whether that would be worse than having a very large percentage of the current core contributors unable to work on the browser is a tough call.

    32. Re:Ideology meet reality by TheRaven64 · · Score: 1
      Wow, so you replied to the first line of my post and completely ignored the bit where I addressed every single one of the points in your reply. Good job.

      That is why everyone who happens to watch the samples provided in that article can easily conclude by themselves that Theora is in fact on par with what h.264 offers, both in file size and image quality.

      I did watch them. I also watched the source video. The Theora one has much paler colours than the H.264 and the source video and is blurry. Pause it anywhere and you can see details in the H.264 version more clearly. I said that in my original post, instead of replying to that, you decided to embark on a long personal attack while accusing my of an ad hominem. Again, good job.

      Every comparison between H.264 and Theora by someone who doesn't have a vested interest in Theora says that H.264 is better. Even the videos posted by the blog you linked to demonstrated a clear difference in quality, and then claimed that there wasn't one. Then it proceeded to show pictures comparing H.263 to Theora, where you can clearly see the difference, so people who just glance at the page will see 'YouTube' and 'Theora' on the low quality pages and think that he's comparing H.264 and Theora in those screen shots.

      --
      I am TheRaven on Soylent News
    33. Re:Ideology meet reality by bonch · · Score: 1

      Time for Linux users to face reality and just give up and use Windows, as most other people have done.

      Oh, we didn't do that in 2000 and we have a strong, functioning, free as in freedom operating system now? I wonder how that could have happened.

      They bought Macs.

    34. Re:Ideology meet reality by slim · · Score: 1

      Aha, you seem to be suggesting that Firefox introduces in-browser ads.

    35. Re:Ideology meet reality by javabsp · · Score: 1

      Nah, time for everyone to just switch to IE.

    36. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      h.264 is only one of the many codecs the Flash runtime can play. See also h.263 and on2 vp6

    37. Re:Ideology meet reality by icknay · · Score: 3, Informative

      I did my best attempt at an unbiased comparison which shows Theora to have about a 30% disadvantage, although it uses a slightly older version of Theora: http://www-cs-faculty.stanford.edu/~nick/theora-soccer/

    38. Re:Ideology meet reality by klapaucjusz · · Score: 1

      Flash is H.264.

      To be entirely exact, Flash is either H.264, On2 or Sorenson Spark.

    39. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      I've had this discussion with him and he went straight for the ad hominem with me too.

      The trailer for "The Island" I linked in that post encoded with Theora 1.1 and an x264 revision from around the time it came out clearly shows heavy blocking in the Theora encode. The clips are 1280x528 encoded at 2 Mbit/s. Even in the first seconds which only contain the green "The following preview has been approved..." screen the current Theora version has noticeable problems in the form of different colour blocks. I assume this is a problem with the current implementation and not with the standard itself, but it's clearly visible that Theora exhibits blocking throughout the trailer, especially during high motion scenes.

      People just need to accept that H.264 is a newer spec that offers more advanced compression features and therefore a good H.264 encoder is going to reach transparency at significantly lower bitrates than a good Theora encoder.
      Comparing Theora 1.1 with current revisions of x264 the former needs somewhere around twice the bitrate for the same quality. I'm sure Theora will improve in the future to narrow that gap, but H.264 will retain a significant advantage regardless.

    40. Re:Ideology meet reality by Baloo+Uriza · · Score: 1

      Never mind that licensing is the overriding concern since that's the one that actually costs freedom and money.

      --
      Furries make the internet go.
    41. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      This would be great if it were true. In fact there's a single FPGA implementation of theora decodind in hardware, and nothing in the world of ASICs. There's a whole pile of verification pain after the design work in any hardware decoder, and implementation costs die area, which costs $$ for every unit sold.

      It would really better serve open source codec advocacy if you were better informed and more honest about the situation.

    42. Re:Ideology meet reality by maztuhblastah · · Score: 2, Insightful

      Sorry, back here in reality Theora's quality is at least on par with H.264 with the same size. But thanks for your attempt at FUD, though.

      So... you linked to the Theora developer's site to support a Theora developer's claims that Theora was superior to competitors. And then you accuse him of FUD?

      Nice.

      The test you linked to, BTW, is crap. No triangle tests, no A/B testing, etc. Just one guy who uploaded and downloaded a sample from YouTube (the encoder and encoding parameters of which he did not know) and compared it to a Theora encode that he did using some rather... "interesting" settings, most notably this: "A keyframe interval of 250 frames was used for the Theora encoding."

      A 250 frame keyframe rate? Are you kidding me?! I don't know what YouTube's using for its keyframe interval, but I guarangoddamntee you it's lower than that. That's a keyframe every 10 seconds. Let's try an encode with H.264 with that interval and see how it measures up to Theora, hm?

      Look, I'm all for using open formats rather than closed ones, but citing a wildly flawed, extremely limited casual test as proof of your contender's superiority just reeks of desperation. Theora's pretty good for what it is: an open source continuation of an old codec that was donated because its commercial competitors had surpassed it. The OSS community's done a good job of improving it and evolving it, and it's great to even have an open-source video codec -- but claiming that it's superior is just flat-out false.

    43. Re:Ideology meet reality by shutdown+-p+now · · Score: 1

      I don't think anyone's ignoring those facts. In particular, no one is under the illusion that ogg is a suitable replacement for h.264 in all cases.

      GP's point was not about technological merits of codecs, so much as it was about reality. As it is, the best you can hope for now is HTML5+H.264 for those user agents that can handle it, and HTML4+Flash for everyone else. The latter category will definitely include IE for the time being, but it now looks like it'll also include Firefox as well.

      The hope is that a better codec than either will appear with more suitable licensing terms; in the meantime a premature standardization on h.264 would hurt the chances of that codec being adopted when it appears, no?

      Companies that are pushing for HTML5 in general (and VIDEO element in particular) - Google, Apple and friends - want to solve a particular problem, and they want to solve it now. As far as they're concerned, H.264 does have licensing terms which are very much suitable for them.

      On the other hand, you seem to be ignoring the fact that Wikipedia, say, has no plans to put its video in H.264 (so Safari, say, can't very well view it).

      Wikipedia is not a big player here, because the amount of video content on it is miniscule. In part this is precisely because they stick to Theora, which few people can be bothered to produce, especially knowing that even fewer actually have the means (or can be bothered to acquire them) to view it.

    44. Re:Ideology meet reality by shutdown+-p+now · · Score: 1

      There is a whole world out there that happens to enjoy watching videos online and no one in their right mind wishes to start paying money to keep doing that, neither the video providers nor the audience.

      The biggest video provider today, by far, is that website called "YouTube". It happens to be run by Google which supports H.264. Then we also have Apple as another big player... surprise, they're in for H.264, too.

      And audience? They don't want to pay for the players, but they won't have to. They'll just use free browsers that come with H.264 support out of the box - Safari on Windows, and Chrome on Linux. In a few years, possibly, also some future version of IE on Win7.

      And Linux? So long as we're speaking about wide audience, it's not even on the radar, sorry.

    45. Re:Ideology meet reality by icknay · · Score: 1

      Oops -- wishful typo, as the linked article above says, the penalty is about 60%, not 30%. That was as of theora1.1a, and now 1.1.1 is out, so I should re-test with that.

    46. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      Yeah, that makes sense, after all the big push for freedom on Linux lead to things like the dropping of CSS on DVDs and Ogg Vorbis taking over from MP3s as the dominant music file standard. Oh, wait...

      Unfortunately, Firefox hasn't got enough market share to influence the dominant standard, so the pragmatic solution is to implement some form of optional h.264 support. Going back to Linux, how many Linux users run with 100% free software, I know I don't, I always install the extra mplayer codecs, libdvdcss and I'm currently using the proprietary ATI graphics driver for my desktop because the open source one just didn't work properly (when I last did an install) and I used the closed NVidia driver when I had NVidia graphics.

      I'd love to be able to run 100% Free Software, but I also want my computer to work properly and do what I want, so I have to compromise.

    47. Re:Ideology meet reality by Anonymous Coward · · Score: 0

      Wikipedia is using Ogg/Theora, using the video tag; however, Safari and IE can view it as well using a Java applet.

    48. Re:Ideology meet reality by horza · · Score: 1

      You should also test at 500kbps and 250kbps. Trying to get something usable out of the latter seems especially difficult from what I've seen. Especially a football match.

      Phillip.

    49. Re:Ideology meet reality by bill_mcgonigle · · Score: 1

      The hope is that a better codec than either will appear with more suitable licensing terms

      Hope is an excuse for inaction.

      Doesn't MoFo have a fair amount of Google revenue to invest? If this is really such a critical issue, why not drop a team of image processing PhD's on this for a couple years (and some engineers, of course)? There's nothing saying Mozilla efforts can't have broad applicability outside of Firefox.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    50. Re:Ideology meet reality by bill_mcgonigle · · Score: 1

      The issue is that H264 cannot be used without paying protection money to MPEG-LA. No amount of technical or commercial metrics are going to make this legal issue go away.

      So, you're completely right, but Mozilla is playing tactics, not strategy.

      If Mozilla doesn't support h.264 then people will switch to Chrome (or IE8, gah). When the -2010 license expires, the only option will be to pay up to MPEG-LA.

      On the other hand, if Mozilla allows free competition in codecs, and does everything possible to make the Free version better, then when 2011 rolls around, they can heavily market to users that there's a Free/free solution already installed. And, perhaps, just because the option exists, the license will keep getting extended, at least until in Re: Bilski is settled.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    51. Re:Ideology meet reality by BZ · · Score: 1

      > If this is really such a critical issue, why not drop a team of image processing PhD's on
      > this for a couple years

      I suspect you're underestimating the resources need to develop an H.264-quality codec without infringing on any of the H.264 patents by several orders of magnitude. For reference, On2 (which was basically in the business of video codec development, and had pretty lengthy experience with it) had 100-some employees (about 50% of the total manpower employed by Mozilla) as of 2008.

      On the other hand, they also happened to have developed some H.264-quality video codecs that Google, having bought them, now owns. The question is whether Google will choose to license them, and if so under what terms.

    52. Re:Ideology meet reality by hazydave · · Score: 1

      Flash actually does On2 VP6 or H.264, these days. The older SD video online is VP6 in a Flash container.

      --
      -Dave Haynie
  19. Handbr by Anonymous Coward · · Score: 0

    So, given that H264 is a really bad idea license-wise, why did Handbrake completely switch over to it? The "xvid is hard" or "divx is old" doesn't seem to hold much water.

    1. Re:Handbr by Svartalf · · Score: 1

      This is because it's technically superior to xvid/divx, both of which are merely implementations of MPEG4. AVC (h.264) is better. What you don't know is that there were license problems with the MPEG4 implementations on FOSS platforms as well- and largely the same set of them. This is a matter of the problem is still there so why keep a inferior solution when there's no difference picking up the "good" one.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  20. It's not a funding problem ... by Pinky's+Brain · · Score: 2, Interesting

    Very few companies could afford a license compatible with the LGPL ... hell, I'm pretty sure the MPEG-LA isn't even authorized to issue such a license, so you'd have to make private deals with everyone. Going to take 100's of millions of dollars easy, maybe more.

  21. Obligatory by ilovegeorgebush · · Score: 3, Interesting

    It really frustrates me that a technology created and owned by someone (MPEG) and otherwise unrelated to the software created and distributed by another (Firefox) is by proxy restricting success and future adoption.

    It is so utterly archaic and unfair that this is allowed to continue; MPEG-LA have the industry by its consumers by their collective balls.

    1. Re:Obligatory by Pinky's+Brain · · Score: 1

      MPEG? You mean ITU don't you?

    2. Re:Obligatory by CowboyBob500 · · Score: 1

      It is so utterly archaic and unfair that this is allowed to continue; MPEG-LA have the US industry by its consumers by their collective balls

      FTFY

    3. Re:Obligatory by Draek · · Score: 1

      Welcome to the wonderful, wonderful world of Software Patents. Or well, patents in general, they're all about taking control of the work somebody else did with his own two hands merely because it's in some way similar to what you thought of a decade ago.

      --
      No problem is insoluble in all conceivable circumstances.
    4. Re:Obligatory by onefriedrice · · Score: 3, Informative

      It is so utterly archaic and unfair that this is allowed to continue; MPEG-LA have the industry by its consumers by their collective balls.

      Err, not really. Nobody forced anyone to adopt h.264; it just happens that it did get adopted because it actually is a good codec. There are alternatives of varying quality and success, and even if there weren't, nothing is stopping someone from designing one and marketing it.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    5. Re:Obligatory by Billly+Gates · · Score: 1

      Its used because its free (for now) and is using an illegal bait and switch technique to build a false standard and then own the world.

      I bet the mpeg consortium probably paid flash and Apple to use its technology to make it standard then bribed the w3c, and now are going to charge everyone through the roof. Cable companies are doing this and now are $200 a month and go up 15% a year. It will be a few thousand a month a decade from now. These same executives want to own the web and h.264 is their way to do it.

      Having it part of html5 is pushing the effort to standardize on it as well.

  22. Good idea, wrong implementation. by argent · · Score: 1

    Just throw a DirectShow interface at the video player and quit shipping codecs.

    How do you propose they do that on OS X or Linux?

    The general idea is a good one, but FFmpeg is probably a more generaly useful approach.

    1. Re:Good idea, wrong implementation. by paskie · · Score: 2, Insightful

      Isn't it better to use the native video player infrastructure on each platform? Quicktime on OS X, gstreamer/whatever on Linux?

      --
      It's not the fall that kills you. It's the sudden stop at the end. -Douglas Adams
    2. Re:Good idea, wrong implementation. by jedidiah · · Score: 1

      Ironically enough: ALL of those will be using ffmpeg. They will just dress it
      up differently can call it by a different name. But yeah, using the mime and
      plug-in interface that has existed in mozilla since the beginning of time does
      seem an obvious way to approach this "problem".

      --
      A Pirate and a Puritan look the same on a balance sheet.
    3. Re:Good idea, wrong implementation. by paskie · · Score: 1

      Will ffmpeg really be used on Windows and OSX? Anyway, if you use the standard platform interface, (i) you won't have to care about having all the obscure codecs (ii) you will not have to ship the codecs with firefox, which is very important for the patent stuff - you are offloading the responsibility to the vendor, and linux distributions already came up with plenty of solutions for this kind of problem (be it special licences or repositories in patent-safe countries).

      I don't know a whole lot about HTML5 video tag, but I don't think you can use the existing plugins too easily, since in case of <video> you have to give the surrounding javascript the abilities to fully control the playback, draw the controls, etc. But I don't understand why don't they do some plugins API extension for this either, my suspicion is that the developers might still largely live within the mindset of trying to standardize on a single fixed format which was what they originally strived for.

      --
      It's not the fall that kills you. It's the sudden stop at the end. -Douglas Adams
    4. Re:Good idea, wrong implementation. by arose · · Score: 1

      Do you volunteer to maintain this mess?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    5. Re:Good idea, wrong implementation. by jedidiah · · Score: 1

      > Will ffmpeg really be used on Windows and OSX?

      You're right. Now that I think about it, it is EVERYTHING ELSE besides h264 that Perian/ffmpeg will be used for on OSX.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    6. Re:Good idea, wrong implementation. by Anonymous Coward · · Score: 0

      while i would like to inflict quicktime on those unfortunate enough to be stuck with os x, i think it would be technically better to use gstreamer everywhere

  23. The route of mp3? by LikwidCirkel · · Score: 1

    Doesn't somebody own the rights to mp3, and technically, all users and content providers should pay royalties? Does that stop anyone from freely including decoders and distributing mp3 content? Here's hoping that H.264 goes that route, and unofficial, but well-recognized plugins for Firefox support emerge.

    1. Re:The route of mp3? by Anonymous Coward · · Score: 0

      AFAIK there was never licensing regulations on distributing content in mp3 format, like MPEG-LA reserves for h.264. Also, MP3 is so old one can argue it should be public domain any day now. h.264 is brand new in comparison, so MPEG-LA will fight for royalties for many, many years to come and hinder the development of the Web in the process.

    2. Re:The route of mp3? by reub2000 · · Score: 1

      Many of the major linux distros don't include an mp3 decoder by default because of the patents.

    3. Re:The route of mp3? by jrincayc · · Score: 1

      MP3 should be going patent free somewhere between Dec 2012 or 2017. I have written more at:

      http://scratchpad.wikia.com/wiki/MPEG_patent_status/Kuro5hin_MPEG_patent_status_paper

  24. Reasons by Anonymous Coward · · Score: 0

    H.264 looks better that Ogg and makes smaller files. Nobody is going to say, oh I'd like my video to look worse and cost people more to download please! High quality video providers will use H.264 anyway for this reason. If Ogg was the standard everyone will end up installing H,264 anyway and the standard will be ignored. Everyone already has H.264 software. Nobody has Ogg software. I bet if you checked outside of this thread you'd find 0.1% of people have it an about 90% can alreay play H264 Thirdly ogg just sounds stupid. I wouldn't implement it for the name alone. I might as well write "NOW SUPPORTS FARTY FARTY PLOP PLOP" on the outside of the box. The name shouldn't matter. But it does. A lot!

    1. Re:Reasons by slim · · Score: 1

      Everyone already has H.264 software. Nobody has Ogg software. I bet if you checked outside of this thread you'd find 0.1% of people have it an about 90% can alreay play H264.

      Everyone with (current) Firefox or Chrome already has an Ogg Theora viewer. I'll wager that's more than 0.1%.

      Everyone with Safari, Chrome or Flash has an H.264 viewer. I'll wager that's more than 90%.

      Thirdly ogg just sounds stupid. I wouldn't implement it for the name alone.

      Perhaps they should rename I.375 for your benefit?

  25. Think again by Zero__Kelvin · · Score: 1

    "It's mostly just problem for Mozilla"

    There is a reason why this story wasn't posted in the "Mozilla's Rights Online" section of Slashdot.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  26. Re:HTML5 Video by Zero__Kelvin · · Score: 1

    "Only if people insist on using it."

    Great point. H.264 is a lot like an IED.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  27. Free software from Google my *** by suffix+tree+monkey · · Score: 2

    Yeah, "free software from Google" indeed - too bad us Joe Sixpacks can't distribute it, only companies with the proper patent license portfolio can. If this debate tells us (free software fans) something, it's that it's time to move to GPL 3 before things get way worse.

    And to all you people who don't care about this and just want their videos to work:

    This video^H^H^H^H^H opinion is no longer available in your country.

  28. Selecting compatibility for ideological goals by Anonymous Coward · · Score: 0

    What he basically states is that "we are ideologically opposed to H264, therefore we won't support it".

    Which is a devastating indictment of the entire Open Source community and something Microsoft should pick up in arguments with the EU about why Firefox should be prevented from taking a dominant position.

  29. More patent abuse by russotto · · Score: 3, Insightful

    Indeed, even distributing H.264 content over the internet or broadcasting it over the airwaves requires the consent of the MPEG-LA

    Now that's ridiculous. Unlike many other technology subject to patents, it's pretty clear that H.264 is useful, novel, and non-obvious. But allowing claims that cover not just the encoder and decoder, but the actual bitstreams they produce, is completely abusive of the patent system. A fancy new saw to cut complex curves in wood might be patentable, but allowing that patent to cover the product would be silly on the face of it. This is no different.

    1. Re:More patent abuse by Dachannien · · Score: 4, Informative

      Actually, the patents can't cover the bitstreams. Case law such as In re Warmerdam indicates that nonfunctional descriptive material (such as a picture or a song) isn't a process, machine, article of manufacture, or composition of matter, so it doesn't meet the requirements of 35 USC 101.

      However, the patents can potentially cover (modulo any prior art issues) the process of transmitting the bitstreams. It may sound like some really thin slices of salami to you, but that's how the law works.

      By the way, your example about the "fancy new saw" and the resulting cut wood is wrong. As long as the cut wood resulting from using the fancy new saw has a specific, substantial, and credible use (for example, it's not merely ornamental, although there's something called a design patent that covers ornamental designs), it is patent eligible under 35 USC 101, because it's an article of manufacture.

    2. Re:More patent abuse by russotto · · Score: 1

      Actually, the patents can't cover the bitstreams. Case law such as In re Warmerdam indicates that nonfunctional descriptive material (such as a picture or a song) isn't a process, machine, article of manufacture, or composition of matter, so it doesn't meet the requirements of 35 USC 101.

      Which doesn't stop patent claims covering "A machine readable medium containing X", where X is some thing not patentable on its own.

      However, the patents can potentially cover (modulo any prior art issues) the process of transmitting the bitstreams. It may sound like some really thin slices of salami to you, but that's how the law works.

      To get a patent out of that you have to slice the salami so thin there's no salami at all. The claim would have to read something like "A process for transmitting a bit stream wherein the bitstream to be transmitted was produced by the method of claim X", possibly with a detailed description of the perfectly standard method of transmission. In other words, the only thing distinguishing the claimed invention from the prior art would be the actual content of the bitstream.

      By the way, your example about the "fancy new saw" and the resulting cut wood is wrong. As long as the cut wood resulting from using the fancy new saw has a specific, substantial, and credible use (for example, it's not merely ornamental, although there's something called a design patent that covers ornamental designs), it is patent eligible under 35 USC 101, because it's an article of manufacture.

      Yes, the cut wood might be patent eligible. It is not, however, covered by the patent on the saw used to cut it; it would be just as patentable if produced by some other method.

    3. Re:More patent abuse by Anonymous Coward · · Score: 0

      ahh yes it may well be "useful, novel, and non-obvious" but it is very likely to be
      manipulation of symbols - aka mathematics. You know that stuff you are not supposed
      to be able to patent. Yes yes - a implementation of hardware/software can be patented but not
      using a general purpose computing machine.

    4. Re:More patent abuse by Dachannien · · Score: 1

      Which doesn't stop patent claims covering "A machine readable medium containing X", where X is some thing not patentable on its own.

      Actually, current policy at the USPTO is to reject such claims by not lending any patentable weight to X in cases where X is nonfunctional descriptive material. So, if a claim recites "A compact disc embodied with Rick Astley's 'Never Gonna Give You Up'", the examiner only needs to find prior art describing a CD, because the music doesn't change the functionality of the medium.

      I agree (more or less) with your other statements, though.

    5. Re:More patent abuse by Jafafa+Hots · · Score: 1

      OK so they haven't patented the wooden doohickey I just made with their new patented saw...

      They just patented putting the output of that saw (my wooden creations) on a truck and driving them to market.

      --
      This space available.
  30. Re:HTML5 Video by Nevynxxx · · Score: 1

    Except the fact that the article is asking for *more open* standards, , which completely invalidates the first sentence fo the last paragraph, if nothing else. Troll is a bit extream though...

  31. HTML5 allows multiple codecs to be specified by jrincayc · · Score: 1

    HTML5 allows multiple video or audio codecs to be provided. Therefore, Youtube and Vimeo can provide both H.264 and Ogg Theora/Vorbis support. If their concern is bandwidth, then they can just provide a slightly lower quality Ogg version with the same bandwidth usage.

    http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#the-source-element

    1. Re:HTML5 allows multiple codecs to be specified by slim · · Score: 1

      The concerns would more likely be:
        - storage
        - conversion costs (processor time)

      However, these get cheaper all the time. Hosting both formats is the only option right now, if you want to take the HTML5 high road.

    2. Re:HTML5 allows multiple codecs to be specified by Midnight+Thunder · · Score: 1

      Having to deal with multiple video formats means either increased storage requirements or processor requirements. I believe the reason for trying to standardise the supported video formats to a limited selection, is the same one for limiting the number of image formats officially supported by web pages: ensuring the content is viewable everywhere. If the specification said do what you want, we would see half a dozen different formats, browser supporting some of them and the users being caught in the cross-fire.

      The day an Ogg endcoder/decoder is made available for things like Adobe Premiere, Final Cut, Quicktime and Windows Media Player, using a BSD style license and also focus on quality for a given bit rate, then we aren't going to see widespread adoption.

      While Ogg might be fine, it is not packaged as a solution suitable for commercial products. At the same time the MP4/H264 licensing means it is not suitable for open source. We have clash of cultures and each is wanting to stand in their ivory tower, and not come down to Earth.

      --
      Jumpstart the tartan drive.
    3. Re:HTML5 allows multiple codecs to be specified by shutdown+-p+now · · Score: 1

      They can, but why would they bother to?

  32. Crippling PPC Incompatibilities, too. by Anonymous Coward · · Score: 0

    Starting perhaps a month ago, certain video players completely hang Safari on PPC machines. It's incredibly annoying, because often websites and even some advertising content feature embedded video which automatically plays (read: hangs) upon opening the page. This 'feature' has rendered many sites a crapshoot as to whether or not they'll bring a browsing session to a halt, and made some altogether unvisitable.

  33. Soo... by Anonymous Coward · · Score: 0

    Forgive me for probably being completely retarded in the matter here, but can't applications like VLC and Handbrake decode H.264? How do they handle the these copyright things, and couldn't Mozilla do something similar with Firefox?

  34. Re:HTML5 Video by Draek · · Score: 0, Troll

    - Opera is a commercial product and they do a lot of business in embedded devices, mobile phones, wii and tv's and so on. They probably want to get a tech to play video for devices without new Flash versions (especially since it's 100% Adobe's responsibility to update Flash on those devices and Opera can't do much about it)

    They do, but an open one. I'd say Opera has been even more vocal about their distaste for MPEG4's patents than Firefox has, likely because, being the little guy in most of the world, they're painfully aware as to how such mandatory licenses increase the barrier to entry and exclude anybody who's not already a large corporation from entering the market.

    Since Firefox already has it's Gecko engine and wide range of plugins, why don't they make themself more reasons to forget about Flash and start using open standards?

    Sure, as soon as MPEG-4 is an open standard and all patents covering it are released into the Public Domain.

    --
    No problem is insoluble in all conceivable circumstances.
  35. Re:HTML5 Video by pmontra · · Score: 3, Informative

    Why troll? AC is correct. The article gives a nice answer to the OP. It's the OP that totally missed the point.

  36. Nonsense by coryking · · Score: 2, Insightful

    Don't people have to cough up a license fee to implement USB? PCI? AGP? Those are all standards.

    People license stuff all the time, even standards. Mozilla needs to get over themselves and provide a way to play standard H.264 videos.

    lots of people just won't be interested

    I'm assuming you are projecting the fact that most people are purely interested in open source.

    You are wrong. Most people want things to just work. Firefox got where they are today because what they produced *worked*. The fact Firefox is open source, free source, or RMS Free as in Freedom(tm) is secondary.

    The day Firefox stops *just working* is the day its lunch will be taken by competitors like Chrome, Opera or Safari. If IE9 plays H.264, Chrome plays H2.64, Opera plays H.264, and Safari plays H.264 but Firefox does not play H.264, guess which one doesn't "just work"?

    By the way, has any of the Mozilla folk sat down at the table and talked with the folks that own whatever IP needs licensing? Have they, you know, said "dudes, we have 33% of the browser market and our business model isn't structured for this sort of thing". My hunch is they could probably get some kind of deal hammered out. The Mozilla foundation does have some political capital you know--this is a good use of it.

    1. Re:Nonsense by Anonymous Coward · · Score: 1

      The day Firefox stops *just working* is the day its lunch will be taken by competitors like Chrome, Opera or Safari.

      Which is exactly what will happen if a proprietary format becomes the standard.

      Have they, you know, said "dudes, we have 33% of the browser market and our business model isn't structured for this sort of thing". My hunch is they could probably get some kind of deal hammered out

      Probably the MPEG-LA will rub their hands together and think how much they could make by forcing licensing payments for every browser shipped.

    2. Re:Nonsense by Sponge+Bath · · Score: 5, Informative

      Don't people have to cough up a license fee to implement USB? PCI? AGP?

      For USB the only fees are for using official logos to show a product passed certification testing. For PCI you pay 3K/year for a membership to get a PCI ID assigned, but there is no licensing fee I am aware of. I don't know about AGP.

    3. Re:Nonsense by Anonymous Coward · · Score: 4, Informative

      Little problem: Even if Mozilla caves in and pays the license fee, that does not cover anyone else distributing Firefox. Canonical would also have to pay the $5 million for Ubuntu's browser. Firefox would effectively no longer be open source as it would be illegal to compile it (with H.264 support) and distribute the resulting binary.

    4. Re:Nonsense by Anonymous Coward · · Score: 0

      Don't people have to cough up a license fee to implement USB? PCI? AGP? Those are all standards.

      Not in software, and hardware can't be free anyway, since even if every employee wishes to work for free the cost of manufacturing will always be quite large, as opposed to the relatively small cost of web hosting.

      People license stuff all the time, even standards. Mozilla needs to get over themselves and provide a way to play standard H.264 videos.

      There are two ways, they can start charging money or bankrupt themselves, can you see why this would be a bad idea?

      The day Firefox stops *just working* is the day its lunch will be taken by competitors like Chrome, Opera or Safari. If IE9 plays H.264, Chrome plays H2.64, Opera plays H.264, and Safari plays H.264 but Firefox does not play H.264, guess which one doesn't "just work"?

      By the way, has any of the Mozilla folk sat down at the table and talked with the folks that own whatever IP needs licensing? Have they, you know, said "dudes, we have 33% of the browser market and our business model isn't structured for this sort of thing". My hunch is they could probably get some kind of deal hammered out. The Mozilla foundation does have some political capital you know--this is a good use of it.

      Yes, if they can't implement H.264 it will no longer "just work", we are aware of that and so are they, it's a problem that needs to be fixed, but that doesn'tmean there's a magical solution for it which has no downsides, some things (such as software patents) don't work that way.
      I'm unaware if they've gone to the license-holders, the only comment I've seen from a Firefox developer (or at least it seems to be from one) says that they will not be allowed to implement this codec if Firefox is to remain free software, they probably could get a deal if they were willing to make it a proprietary program, but that's not something they're willing to do.
      He also hints at getting around this by using the OS libraries to play videos/audio, which would probably be the best solution IMO, since even on Linux a "sudo apt-get install kubuntu-restricted-extras" or the equivalent would provide pretty much all codecs you need, but I haven't seen any solid plans for this and it may not be that easy looking at how crap most media plugins are.

    5. Re:Nonsense by BZ · · Score: 3, Informative

      You apparently didn't read the article. The issue is not that Mozilla can't get a license; it can. The issue is that it sees doing so as actively harmful to the web and to users.

    6. Re:Nonsense by Kjella · · Score: 4, Informative

      By the way, has any of the Mozilla folk sat down at the table and talked with the folks that own whatever IP needs licensing? Have they, you know, said "dudes, we have 33% of the browser market and our business model isn't structured for this sort of thing". My hunch is they could probably get some kind of deal hammered out. The Mozilla foundation does have some political capital you know--this is a good use of it.

      The GPL and patents intentionally mix like oil and water. Directly from paragraph 7 of the GPLv2: "For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program." You can get around this by covenant not to sue *cough*Novell*cough*, but that's abusing a loophole really.

      That works out great in certain circumstances, for example I can't patent something, add that to a GPL project and control distribution by selling patent licenses. But neither can Mozilla, they can't license it from MPEG LA just for themselves, the GPL basically requires them to license it for everyone. That is why you can download the Chromium source, but you will not get a patent license from that either. Only binary builds of Chrome gets the patent license, since a right to sublicense would destroy MPEG LA's revenue model.

      --
      Live today, because you never know what tomorrow brings
    7. Re:Nonsense by Antiocheian · · Score: 1

      Don't people have to cough up a license fee to implement USB? PCI? AGP? Those are all standards.

      People might cought the fees but Mozilla doesn't include implementations of USB, PCI and AGP. If people were to cough a standard fee for H264 on their OS, then Mozilla would also support it. But, as the article states: "Most users with Windows Vista and earlier do not have an H.264 codec installed. So for the majority of our users, this doesn't solve any problem.". Hey, did you read the article ?

      I'm assuming you are projecting the fact that most people are purely interested in open source. You are wrong. Most people want things to just work.

      But idealism is the "reason for Mozilla to exist." as the article states which really begs the question: did you read the article ?

      The day Firefox stops *just working* [competitors will win]

      Oh, h264 video is the definition of a workable web browser? I don't think so, but also how about "Currently providing H.264 content on the Internet is zero-cost, but after 2010 that will almost certainly change [...] If you just want to put a few videos on your Web site, or add a help video to your Web application, or put a video cut-scene in your Web game, that is probably not something you want to do." ?

      By the way, has any of the Mozilla folk sat down at the table and talked with the folks that own whatever IP needs licensing?

      Look, just read the article, ok ? (Sorry no video option available)

    8. Re:Nonsense by TheTurtlesMoves · · Score: 5, Insightful

      People license stuff all the time, even standards. Mozilla needs to get over themselves and provide a way to play standard H.264 videos.

      Licensing something like h264 is very different. Its not just the fee (about 5Million pa for FF popularity) its the restrictions that the contract has. Like promising to enforce DRM or not permitting redistribution. These licenses are simply not compatible with GPL 2 or 3. Since I am not free to redistribute FireFox without getting a license from MPEG-LA.

      And proving a H.264 *content* will require licenses after 2010. Have fun with that

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    9. Re:Nonsense by Anonymous Coward · · Score: 0

      I think this would be a good eventuality. Maybe then Ubuntu would step up to the plate and make it easier for third parties to compiler software on their system if they could only distribute official binaries from Mozilla

    10. Re:Nonsense by Anonymous Coward · · Score: 0

      Here's my problem with the idea that Firefox doesn't "Just work".

      No other browser supports No Script.

      The more I work with the internet on a daily basis, the more convinced I become that managing which hosts and sites are allowed to execute ANY code on my machine is something I was very fine granular control over.

      I like Chrome (I'm posting this from Chrome at the moment, actually, as I'm currently booted into Win7 instead of my normal Ubuntu install). However, I would never think to use it as my daily browser, because Noscript on Firefox is simply too powerful.

      At the end of the day, if Firefox refuses to support H264, and the other browsers refuse to enable support for add-ons like Noscript in any meaningful way, I'll use Firefox for everything except video, and write my own add-on to launch links to all the major video sites in Chrome or Chromium.

      I don't care how well it "just works" if it compromises my machine, and there are a helluva lot of geeks just like me in the same boat.

    11. Re:Nonsense by aristotle-dude · · Score: 1

      Little problem: Even if Mozilla caves in and pays the license fee, that does not cover anyone else distributing Firefox. Canonical would also have to pay the $5 million for Ubuntu's browser. Firefox would effectively no longer be open source as it would be illegal to compile it (with H.264 support) and distribute the resulting binary.

      Open source is not necessarily free. The majority of development contributions, like with most successful "open source" products comes from inside of the mozilla foundation staff. This was true with MySQL as well. They could easily have the main "open source tree" and then have a source branch which referenced the main tree and H264 code. The binaries with H264 support would only be available from the Mozzila foundation directly. Firefox could also be dual licensed for inclusion in commercial products to cover the cost of h264 licensing. Another alternative would be to offer H264 as an optional add-on for Firefox for a small fee to cover H264 licensing and support Firefox development. Problem solved.

      Where I work, we have some common code shared between source trees of different product groups that show up as "external" in an SVN update so I know that open source source control products like SVN can do what I'm describing.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    12. Re:Nonsense by Anonymous Coward · · Score: 5, Insightful

      More importantly, you generally BUY SOMETHING with USB, PCI, or AGP, therefore you give the company money to pay the fees with. Mozilla is given away freely, recouping some money with advertising links. They can't promise to pay lots of money and MPEG-LA has already cut the "loss leader" deals with big companies.... gotta get the money from the little guy. Worse yet, the MPEG-LA is notoriously fickle and as soon as fees kick in we'll have another situation like MP3 where everybody THOUGHT they paid up, but companies in the patent pool use loopholes to revoke MPEG-LA's consolidation of license fees.... then go after everybody "again" just like happened with MP3.

    13. Re:Nonsense by Drantin · · Score: 1

      Chrom(e/ium) will have No Script features eventually.

      --
      Actio personalis moritur cum persona. (Dead men don't sue)
    14. Re:Nonsense by TheRaven64 · · Score: 1

      No, that's only part of the problem. The other part is that Mozilla incorporates code from third parties (i.e. all of the community developers) which is released under the GPL/MPL/LGPL. All of these clauses contain patent clauses when prohibit redistribution if the code contains patents that you can't grant redistribution rights for. That makes it impossible for Mozilla to include any patented code unless they get a license which allows unlimited sublicensing. The MPEG-LA isn't going to allow this, because anyone who got a copy of FireFox would then not have to pay them royalties.

      The only way around this is for them to provide hooks for connecting DirectShow / QuickTime / FFMPEG for playback (which is what they should be doing anyway - you can already use them via object or embed tags, the only difference with video is that you have a uniform way of accessing them via scripting, rather than lots of different ad-hoc ways).

      --
      I am TheRaven on Soylent News
    15. Re:Nonsense by 0100010001010011 · · Score: 4, Interesting

      Debian used to have the "Non-US" repositories. I can't see why they couldn't go back to it.

      As much as everyone hates it, Ogg isn't going to win this. As far as I know there isn't a single hardware decoder for it yet. Almost any newer Nvidia card will do it. VDPAU under Linux works AWESOME. It will even upscale SD content (feature set C). Broadcom has their MiniPCI card that a ton of NetBooks run. I bought one for my AppleTV so that I can do 1080p. XBMC supports it. OS X should support it soon.

    16. Re:Nonsense by zzyzyx · · Score: 3, Informative

      There is a $2000 fee to buy a unique USB Vendor ID, and the right to use the USB logo for two years, which is pretty much mandatory if you want to make a commercial product.

    17. Re:Nonsense by Runaway1956 · · Score: 1

      Just how easy should it be to compile something?

      configure
      make
      make install

      Someone who fears the command line to much to use those three commands shouldn't even be ATTEMPTING to compile something.

      As for Canonical, or anyone else, who might fear liability for distributing a binary, they can run a simple script to do the compiling on the end user's machine.

      Your objection is utter failure.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    18. Re:Nonsense by ottothecow · · Score: 4, Insightful
      Probably the MPEG-LA will rub their hands together and think how much they could make by forcing licensing payments for every browser shipped.

      Nah, I would imagine they would be open to it for a very favorable rate. If the license for free streaming content expires, anyone who wants to use h.264 online will need to pay for an encoding license. The only reason you would want to pay for a license to encode (when there are alternatives that are free on both ends) is if the tech is good and your viewers can all decode the content

      If the MPEG-LA wants to sell to content distributers (who are more willing to pay since they actually depend on the content), they will want firefox's 33% of the market. They might not do it for free since mozilla also has some amount of willingness to pay but I doubt they are in a position to gouge them (and a "donation" to the nonprofit mozilla foundation might be a nice annual tax writeoff).

      --
      Bottles.
    19. Re:Nonsense by Anonymous Coward · · Score: 0

      "It will even upscale SD content (feature set C)."

      Each and every video card since the 90s has hardware scaling for video.

    20. Re:Nonsense by Bert64 · · Score: 1

      USB, PCI, AGP etc are hardware standards, you may have to license them to create hardware which supports them but you certainly don't need to pay anything if you just want to create software that drives such devices.

      Hardware cannot be made for free anyway, therefore the licensing cost merely goes in with all the other manufacturing and raw materials costs...
      Software on the other hand can be made for free unless you start introducing artificial restrictions like having to license a media format.

      Something like this is great for MS because it basically makes it impossible to have a free web browser.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    21. Re:Nonsense by sopssa · · Score: 1

      As for Canonical, or anyone else, who might fear liability for distributing a binary, they can run a simple script to do the compiling on the end user's machine.

      No. No they cannot. Legally that would be viewed exactly the same way.

      Also isn't Linux trying to gain marketshare on desktop? Saying things like compiling things is easy and one shouldn't fear command line just doesn't do that. With comments and assumptions like this I doubt we will ever see larger marketshare of Linux on Desktop.

    22. Re:Nonsense by HouseOfMisterE · · Score: 1

      He/She meant that the newest nVidia chips have hardware support for decoding "MPEG-1, MPEG-2, MPEG-4 Part 2 (a.k.a MPEG-4 ASP), VC-1/WMV9 and H.264" via VDPAU in linux (see http://en.wikipedia.org/wiki/VDPAU ). The biggest benefit of VDPAU is hardware decode of HD content like H.264, but it's also nice that SD DivX/XviD/MPEG-1/MPEG-2/etc. is accelerated, too.

    23. Re:Nonsense by Runaway1956 · · Score: 1

      FFS, dude. Linux is gaining market share PARTLY because people WANT TO control what their machines are doing. People - some people - people like me - WANT to get inside, and see who, when, what, where, how, and why.

      I don't WANT MS or anyone else to hold their code so close that I'm unable to even LOOK AT IT. To me, this is one of the major selling points of Linux, and any other open source project.

      Fear the command line? Sorry - I can't respect it.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    24. Re:Nonsense by Hal_Porter · · Score: 2, Funny

      He/She/It meant

      Fixed that for you. Speciesist bastard.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    25. Re:Nonsense by sznupi · · Score: 1

      FYI, Opera is also behind Theora (heck, they proposed video tag back then). Though people portraying this as only Mozilla doing the "right thing" is only...typical.

      http://my.opera.com/core/blog/2009/12/31/re-introducing-video

      BTW, Debian folks would really argue about the extent to which Firefox or Seamonkey are free...

      --
      One that hath name thou can not otter
    26. Re:Nonsense by sopssa · · Score: 1

      No, I do not fear the command line, and I use Linux daily. And I DO agree with that, but lets face it, we're minority. 99% of users don't want to dick around with all the technical sides of computers, they just want something that works and does what they want to do.

    27. Re:Nonsense by Hal_Porter · · Score: 1

      Opera lets you block content. So I could block *.js on a site if I wanted. Or more likely I'd block the irritating ad providers by URL on all sites.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    28. Re:Nonsense by sznupi · · Score: 2, Informative

      No other browser supports NoScript-like functionality except for, usually ignored in such "only FF supports that" rants, Opera. For a long, long time...

      BTW, Opera also stands behind Theora (and generally a web accessible to everybody), they proposed the tag.

      --
      One that hath name thou can not otter
    29. Re:Nonsense by Cyberllama · · Score: 1

      They have enough market share to push us all towards Ogg instead for HTML5 video -- and I'm pretty sure that's where Google would rather go too. At this point, everything is in flash video and nobody complains about having to install a plugin to support it. Are they going to suddenly cry foul if they need a plugin to support h264? My guess is if one format is easier, thanks to Firefox's stubborness, then many websites may simply adopt ogg as the standard in the first place.

        Apple, on the other hand, may not agree, but Safari is mostly irrelevant. It sneaks in with iTunes (another terrible piece of software) but it's not actually used much. It's currently 4th place in a 3-way competition.

    30. Re:Nonsense by Anonymous Coward · · Score: 0

      Except that Firefox is not licensed under the GPL, and the MPL need not apply to the entire work, leaving them free to supply potentially patented code under any license they wish.

    31. Re:Nonsense by sopssa · · Score: 1

      Firefox is licensed under many licenses, main one being Mozilla Public License, not GPL. They can leave the proprietary parts out of redistribution, if they want to.

      Unlike strong copyleft licenses, the code under the MPL may be combined with proprietary files in one program ("Larger Work"). For example, Netscape 6 and later releases were proprietary versions of the Mozilla Application Suite, by adding the proprietary AIM and other parts. The MPL treats the source code file as the boundary between MPL code and proprietary parts, meaning that a certain source file (e.g., C++, JavaScript or XUL file) is either fully MPL or fully proprietary. The GPL, in contrast, uses the process boundary of the executable as the license boundary (for details, see GPL).

    32. Re:Nonsense by CheshireFerk-o · · Score: 0

      In fact I still use the following...

      deb ftp://debian.lcs.mit.edu/debian/ testing non-free

      I've been using debian for over 9 years now, and running unstable/testing, I've only installed the OS twice. Once at birth and once on the switch to raid. Not once have I had a problem doing pretty much whatever I want it to do.

    33. Re:Nonsense by djradon · · Score: 3, Insightful

      Not to mention USB/PCI and AGP implementations are all hardware devices, presumably to be sold. Your comparison is horrible.

      The day Firefox is "taken" by commercial software will be a sad day indeed. The Mozilla Foundation could probably get a reduced price on a license easily enough, but that's not the point.

    34. Re:Nonsense by slashqwerty · · Score: 2, Informative

      Except that Firefox is not licensed under the GPL

      Sorry, but yes it is.

      Core Mozilla project source code is licensed under a disjunctive tri-license giving you the choice of one of the three following sets of free software/open source licensing terms:

      This allows the use of our code in as wide a variety of software projects as possible, while still maintaining copyleft on code we wrote.

    35. Re:Nonsense by DJRumpy · · Score: 2, Insightful

      "Which is exactly what will happen if a proprietary format becomes the standard."

      That argument doesn't work even through beer (as in free) goggles. Pretty much every media standard on your typical electronics device like a PC, your Television, and your iPod all contain proprietary licenses. MPEG-2 for DVD's, MP3, AC3, H.264. All huge successes, and all standards in their time. Companies wouldn't be interested in investing in new technologies if they can't profit off of it. Even patents have their place.

      It would be almost impossible to find any successful gadget today that isn't laden with proprietary technology, yet technology marches on. FOSS is great, but I wouldn't say it's necessary in the grand scheme of things. If/When these big sites stop using Flash (I pray for that day), and switch to H.264 only, Mozilla had better pray they have a solution because the typical end user could care less about their 'ideals':

      I found this part of TFA curious:

      "Mozilla should pick up and use H.264 codecs that are already installed on the user's system. I've previously written about a variety of reasons this would be a bad idea, especially on Windows. Really there are two main issues:

      * Most users with Windows Vista and earlier do not have an H.264 codec installed. So for the majority of our users, this doesn't solve any problem.
      * It pushes the software freedom issues from the browser (where we have leverage to possibly change the codec situation) to the platform (where there is no such leverage). You still can't have a completely free software Web client stack. "

      Their first mistake is ignoring Windows 7. Love it or hate it, it will inherit XP, and by such, it will support H.264. This would solve a huge slice of their problem which would only get smaller as Windows 7 adoption increases. OS X already has this support built in which takes care of another big (albeit far smaller than Windows) player and that would also be a no-brainer. That leaves Linux, which will managed just fine on it's own as it always does. Why would you NOT take a step that would allow functionality for millions? Granted, right now Mozilla has market share, but that will quickly dwindle if they can't compete with the others.

      Their second mistake is putting their ideals in front of their users and assuming the users will stick with them. Users are fickle. Ask most users what Mozilla's 'ideals' are they will just give you a blank stare. Users just want a browser that works. It seems to me that Mozilla is assuming too much trying to force this issue to remain in the browser or by demanding that they specify Ogg as the official HTML5 video standard. They simply don't want to admit that they never had control of the codec situation in the first place. An easy solution for the typical end user is just a quick browser download away.

      Their third mistake is assuming that they have even the smallest chance of success with Ogg against the juggernaut that H.264 has become. It's almost as if they believe it will somehow surpass h.264 in the market place. H.264 is already supported by millions of Blu-Ray players, music players, web sites, and software vendors. When you get that much market acceptance, you're going to lose unless you offer something substantially a step above, and Ogg simply doesn't do that. It is based on old MPEG-4 Part 2 technology and arguably doesn't offer much better compression than the old MPEG-2 standard. The final nail in the coffin is due to the fact that there is also no market support for hardware acceleration for Ogg. It is no trivial task for PC manufacturers, and smart phone manufacturer's to replace internals if some chip ever came along to add hardware acceleration for Ogg. Why should they bother? H.264 is unquestionably here to stay for many years to come. Mozilla's only hope is if sites like YouTube cave and offer up their content in Ogg. Get a major player like that to do it and you at least grease the wheels. B

    36. Re:Nonsense by slim · · Score: 1

      As for Canonical, or anyone else, who might fear liability for distributing a binary, they can run a simple script to do the compiling on the end user's machine.

      ... which would not work around the licensing issues in any way.

      You have to pay MPEG LA for licensing the patents, whether the code is shipped as source or binary. It makes not a jot of difference.

    37. Re:Nonsense by Anonymous Coward · · Score: 0

      The thing holding back linux on the desktop is inertia, games, drivers for some stuff.
      Even granny would prefer to apt-get a source than the mess of keeping windows and all the installed stuff cleanly updated.

    38. Re:Nonsense by Runaway1956 · · Score: 1

      Who, exactly, has to pay? Canonical? Hmmmm - I have a good bit of software installed in Ubuntu that Canonical doesn't support. DVDCSS for example. Actually, that breaks the law, here in the US - so, who is liable? I would assume that I am liable for all the software I use for circumventing software restrictions - not Canonical, not Debian, not Asus, or anyone else.

      Pay MPEG LA? Nope, I won't. As long as I can find the source and/or a binary somewhere, I'll use their stuff, but I'm not paying them. Simple as that. There will always be a way around paying them, and I'll take advantage of it.

      Now, if a mere 20 million more people took that position, and told MPEG LA and all the other patents holders that we aren't paying, we might make Congress and the courts take notice.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    39. Re:Nonsense by aristotle-dude · · Score: 2, Interesting

      You apparently didn't read the article. The issue is not that Mozilla can't get a license; it can. The issue is that it sees doing so as actively harmful to the web and to users.

      Removing Firefox as a viable option by implementing Theora only would do harm to the web and its users. It would remove the ability for users to use Firefox to browse the majority of video websites in the future all in the name of some "holy" crusade for FOSS principles.

      Firefox is not developed by the community. It is developed by a small cadre of Mozilla foundation employees. Open source is just a marketing angle for the majority of high profile projects.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    40. Re:Nonsense by Anonymous Coward · · Score: 0

      PCI documentation you can't get hold of legaly/easily without been a member of the pci group with the ossociated 3k fee etc.

    41. Re:Nonsense by slim · · Score: 1

      They probably won't come after you, since you're small fry.

      If, however, you were serving an appreciable amount of H.264 video on the web, they'd come after you asking for thousands, or tens of thousands, or millions.

      You could try your civil disobedience trick. You'd have your day in court, lose, and owe them even more.

    42. Re:Nonsense by Anonymous Coward · · Score: 0

      Except they are the largest browser that supports HTML5's Video tag, they use Theora encoded video. Their market share is more than double the combined share of browsers that do support HTML5 Video with h.264, so maybe, just maybe that should have some sway here. Of course, if they allowed for the OS to register browser codecs, similar to how plugins are registered, then they could rely on OS functionality. And have the installer just re-use/register whatever codecs are available on install.

    43. Re:Nonsense by BZ · · Score: 1

      > Removing Firefox as a viable option by implementing Theora only would do harm to the web
      > and its users

      You're assuming that this would remove Firefox as a viable option. In the short term, that's very unlikely (e.g. Youtube continues to work in Firefox). In the longer term, if nothing changes, maybe Mozilla would in fact end up feeling forced to implement H.264 support.

      > all in the name of some "holy" crusade for FOSS principles

      Did you read the article? The "holy principle" in question here is that anyone should be able to put up video on the web and anyone should be able to view it. That seems to be a pretty key part of how the web is supposed to work.

      > Firefox is not developed by the community.

      It's developed by whoever cares to develop it, actually. In the last three months, I've seen at least 4 different people show up, dive in, fix things that were bothering them.

      In general, the direction of any large project is set by its core contributors. In the case of Mozilla, they happen to have been able to hire a large fraction of the core contributors, so they're actually paid for their contributions. The direction is still set by said individual contributors.

    44. Re:Nonsense by BikeHelmet · · Score: 1

      If it was only $2000, they'd already have licensed it. But people are throwing around quotes of $5,000,000 per year, which is a HUGE amount of Mozilla and Opera's revenue.

    45. Re:Nonsense by slim · · Score: 3, Insightful

      Love it or hate it, it will inherit XP, and by such, it will support H.264. This would solve a huge slice of their problem which would only get smaller as Windows 7 adoption increases.

      You misunderstand what their "problem" is, even though you quote it in your post. It's not that they would have difficulty supporting H264. It's that their raison d'etre is to promote a free and open Web.

      They don't want or need to kill off H264, since HTML5 makes it easy for a site to support both at once. With this you end up with the equitable solution where you can say "If you want to use a browser with a proprietary codec, you can. Maybe it'll even look better. But if your browser only uses free codecs, you're OK too.

      They just want to promote a Web where a user without access to H264 can take part in a meaningful way. So, a child in India/Brazil/Namibia/etc. who can't afford an H264 license (nor a Windows license) can still view mainstream video sites. So the same kid can create videos and share them on the Web.

      If they didn't pursue those ideals, they might as well pack it in today and let everyone use IE.

    46. Re:Nonsense by DJRumpy · · Score: 1

      But they do so at the risk of their users. If a browser doesn't display a page, users will simply use another browser. I never said their ideals aren't lofty. They simply aren't realistic.

      Where is the harm in them providing the ability to use codecs that are available to the underlying OS?

    47. Re:Nonsense by Firehed · · Score: 1

      Heh, if only.

      If a browser doesn't display a page, people will wonder what the hell is wrong, and then hit the back button. That's somewhat less true for Firefox users than those of most other browsers (IE and Safari, at least), but with something as widespread as video embeds, chances are that it's mostly irrelevant. Webmasters will either a) provided h.264, ogg, and flash fallback*, b) provide h.264 and flash fallback, or c) just use flash. Only sites that basically equate to tech demos aren't going to provide any sort of graceful degradation when it comes to html5 video support.

      That being said, Mozilla needs to suck it up and find a way to implement h.264, even if that means coughing up for licensing. It's not some lofty ideal, but h.264 has already become the de-facto standard and has been for quite a while - this is just changing the playback medium. I've had enough trouble trying to get one video converted to ogg for html5/firefox playback (to the point where I eventually just gave up... something with broken poster frames I think, and the color getting screwed up). YouTube et al are already serving h.264 via flash - transcoding millions of hours of video simply isn't going to happen, especially not to support a format that's never seen any real widespread use.

      Nothing against ogg/vorbis/theora, that's just the reality of things. H.264 won, and it did so about three years ago.

      *Flash fallback is so easy to implement that I don't know why all video sharing sites haven't switched to html5 natively anyways. You just wrap the flash embed inside the video tag - if the browser can play the video natively it will, otherwise it uses the flash.

      --
      How are sites slashdotted when nobody reads TFAs?
    48. Re:Nonsense by Firehed · · Score: 1

      Just how easy should it be to compile something?

      configure
      make
      make install

      Someone who fears the command line to much to use those three commands shouldn't even be ATTEMPTING to compile something.

      Well, yeah. But I'll be damned if I have to sit around for an hour while my browser is compiling before I can browse the web after a fresh OS install.

      Just because it's easy doesn't mean it makes sense. And that approach certainly won't do much for the "year of the Linux desktop" that we've been celebrating for the past decade.

      --
      How are sites slashdotted when nobody reads TFAs?
    49. Re:Nonsense by Gerv · · Score: 1

      Yes it's licensed under the GPL, but not _exclusively_ under the GPL. You can choose your terms from the quoted list of three. So a company - Mozilla or any other - could choose "MPL", and then combine the Mozilla code with proprietary code, whether it implemented video codecs or did something else. The MPL patent language only applies to the code in the final product which is MPLed, and the GPL patent language wouldn't apply at all, because the company's original choice of terms from the three was MPL, not GPL. Netscape is an example of a company which did this, but there are many others who do it today.

      Gerv

    50. Re:Nonsense by FlyingBishop · · Score: 1

      I own a Motorola Droid, which comes with a hardware H.264 encoder/decoder. I'm pretty pissed that I don't have a corresponding license to view that H.264 on the computer I'm typing this on.

      That's why I'm behind Mozilla 100% on this.

    51. Re:Nonsense by Anonymous Coward · · Score: 0

      price is irrelevant. There's some legalities involved :-P

    52. Re:Nonsense by Anonymous Coward · · Score: 0

      Where did you get the idea the Mozilla has some amount of willingness to pay? Maybe they do, but the licence itself is the real sticking point. Mozilla does not want to produce software that others can't freely distribute, to get Mozilla to include h.264 MPEG-LA would have to effectively give a free license for all h.264 decoders because Firefox is distributed under the GPL (and the LGPL and MPL) and the GPL requires royalty-free re-distribution.

    53. Re:Nonsense by Anonymous Coward · · Score: 0

      Almost, but google already use h264 extensively as it's what they serve to flash applets on youtube, converting all existing content to theora would be problematic for them, they also want to increase chrome marketshare, and killing mozilla by supporting a patented technology would certainly help there. Google have a certain capacity for evil and a loyalty to their brands.

    54. Re:Nonsense by badkarmadayaccount · · Score: 1

      That's friggin' cheap! Do you realize how much the codecs cost?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    55. Re:Nonsense by hazydave · · Score: 1

      Yeah, actually, most of these "Intel-pushed" standards, like USB, PCI, AGP, PCI Express, etc. are patented, but you're granted free license to all patents if you follow the specs. This is because Intel just wants to sell the chips, and adding new interfaces sells more chips. It's a good thing.

      In fact, USB was born largely because Apple was asking $1.00 per port for Firewire, and Intel though that was nuts, given the margins in the PC industry. At the same time, Compaq and some others were trying to figure out some kind of "desktop bus" standard, like DEC's Access.Bus or Apple's ADB. The two forces got together, and the result was very good for us. Even for Apple, eventually. And Firewire was mitigated to special purpose applications.

      --
      -Dave Haynie
  37. So does the Mozilla Foundation by coryking · · Score: 1

    They also have at least a 1/3 of the desktop browser market. That gives them significant leverage in negotiating some kind of deal to license the codec in their browser.

    Business is business, time for Mozilla to step up and act like one.

    1. Re:So does the Mozilla Foundation by Anonymous Coward · · Score: 0

      Unlike Apple and Google with their browsers, Firefox is also designed to be compileable by third parties and linux distributions without becoming an inferior product.

      By licensing and including H.264, the downstream users of the software that do not get it directly from Mozilla will hot have the same experience as those that do, since the licence will not be transferrable down the chain.

    2. Re:So does the Mozilla Foundation by Rockoon · · Score: 1

      By licensing and including H.264, the downstream users of the software that do not get it directly from Mozilla will hot have the same experience as those that do, since the licence will not be transferrable down the chain.

      Mozilla has not negotiated a license for H.264 so you cannot make a claim about what rights would or would not be transferable under it.

      (suggestion: please use a browser that has a spell checker)

      --
      "His name was James Damore."
    3. Re:So does the Mozilla Foundation by Antiocheian · · Score: 1

      That also gives them significant leverage in forcing video services to support Theora on HTML5. And that's far easier than negotiating with patent royalties lawyers.

    4. Re:So does the Mozilla Foundation by slim · · Score: 1

      Suggestion: consider that spelling conventions vary among English speaking countries. "Transferrable" is unconventional, but appears in dictionaries. "Licence" is the standard British spelling.

  38. How to silently kill firefox by ammorais · · Score: 3, Interesting

    How to silently kill Firefox:

    * Support Firefox trough funding (so that nobody can call you evil)

    * Buy one of the most successful video sites.

    * Implement a technology on this site that you know for sure Firefox can't use.

    * Reduce competition on this site by using a video format not everyone can use on their site(increasing linking and video embedding to your own site)

    * Support this video format on your own browser.

    *Profit.

    1. Re:How to silently kill firefox by Antiocheian · · Score: 1

      * Support Firefox trough funding (so that nobody can call you evil)
      * Buy one of the most successful video sites.
      * Implement a technology on this site that you know for sure Firefox can't use.
      * Reduce competition on this site by using a video format not everyone can use on their site(increasing linking and video embedding to your own site)

      * Watch your share degrade as Firefox-supporting competition rises
      * Lose Profit

    2. Re:How to silently kill firefox by rgo · · Score: 1

      Interesting? What the hell!? Why would Google want to kill Firefox and spend BILLIONS trying to do it??

    3. Re:How to silently kill firefox by Anonymous Coward · · Score: 0

      But what in what order do we do these? What order!?!

    4. Re:How to silently kill firefox by Midnight+Thunder · · Score: 1

      I don't think Firefox was even a target and is rather it was collateral damage. Rather I think is probably along these line:
        - H264 was support by Apple
        - Google was on good terms with Apple
        - MP4/H264 provide high quality images for bandwidth. Think HD video
        - Ogg Theora is nice and all, but is not available in any commercial product

      IMHO, Ogg Theora people are so wound up in their ideology that they aren't addressing what they need to to give MP4/H264 a run for its money. Believe me sometimes you have to step out of the tower and walk into the market. The MPEG group needs to do the same, for different reasons.

      --
      Jumpstart the tartan drive.
    5. Re:How to silently kill firefox by ammorais · · Score: 1

      I don't think Firefox was even a target ...

      Perhaps not. But Google did know for sure what problems Firefox could have with the exclusive adoption of H264 on Youtube.

      That has do make me think.

    6. Re:How to silently kill firefox by Anonymous Coward · · Score: 2, Funny

      Adblock

    7. Re:How to silently kill firefox by bonch · · Score: 1

      Except that the Flash player already supports H.264 videos, and Firefox happily plays those. As with Flash, this will be solved by a plugin, and in a few years, nobody will even remember this exaggerated controversy.

    8. Re:How to silently kill firefox by BikeHelmet · · Score: 1

      Uhh... interesting? That's a bit nutty if you ask me.

      Firefox has helped Google chop away at Microsoft's stranglehold on the web. It's helped Google more than any other browser.

      Now Google owns Youtube and has big red numbers in their balance books. When examining bandwidth costs, H.264 just makes sense.

      Profit is the goal, but there's no malice involved, and no conspiracy to kill Firefox. Plus, according to a thread from a few days ago, Firefox is working on the same solution as Opera (GStreamer based plugin) - they just don't want to implement it.

    9. Re:How to silently kill firefox by joelpt · · Score: 1
    10. Re:How to silently kill firefox by Anubis+IV · · Score: 1

      Yes! You've uncovered Google's secret plans to spend billions of dollars on YouTube, enter a new field by producing a high-quality browser, and support the better technology in a format war, all so that they could get traffic to their search engine? Which they were already getting from Firefox anyway...because...umm...yeah. I got nuthin'.

    11. Re:How to silently kill firefox by Acaeris · · Score: 1

      YouTube was stuck in the H.264 situation before Google took control of it. Google are aiming to support both Ogg and H.264 in Chrome as far as I know but concentrated on H.264 because of all the content already in that format on YouTube. In essence, the decision for Chrome and YouTube to support H.264 was made by Adobe.

  39. Why is this Mozilla's problem? by Anonymous Coward · · Score: 0

    Why is this Mozilla's problem? You're putting video on the internet for a reason. You want to sell something or advertise something to sell. So why would you want to put it out in a compressed format that not everyone can see? Especially if you have to pay a royalty to do so.

    In fact, why do you need patents on compression: without it, we'd have analogue or Laser Disk. DVD consortium would pay to get a compression ratio better than they get from analogue just so they can sell DVDs which are cheaper than laser disks. So the market doesn't need patents to monetise this: the demand of the industry itself would do the work.

    Just like the Dirac code: it would cost the BBC more to license another codec than it would to write their own.

    So they did.

    1. Re:Why is this Mozilla's problem? by Goaway · · Score: 1

      h.264 is the closest thing to a format that "everyone can see" that we have at the moment. It's used everywhere. Most importantly, Flash already uses it. You're most likely watching h.264 video every day.

    2. Re:Why is this Mozilla's problem? by arose · · Score: 1

      It's used everywhere. Most importantly, Flash already uses it. You're most likely watching h.264 video every day.

      Not even close. MPEG-2 is more widely used in general and on the web flash is more often paired up with Sorenson Spark. Only Chrome and Safari support H.264 for HTML5 video tags.

      Only cell phones are dominated by H.264 and the lifetime of the average cell phone is short enough to upgrade in a few years if MPEG LA really starts going after content providers.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    3. Re:Why is this Mozilla's problem? by Goaway · · Score: 1

      MPEG-2 is widely used because of legacy devices. It's not used in new systems. And Flash is probably more often paired up with h.264 than h.263 these days. And if it isn't yet, it will very soon be.

    4. Re:Why is this Mozilla's problem? by arose · · Score: 1

      MPEG-2 is widely used because of legacy devices. It's not used in new systems.

      Theoretically that is the case for MP3 as well, nonetheless no one in their right mind will claim that AAC is "used everywhere" which was the point. MPEG-2 rules, because the DVD isn't going away quite yet. None of this directly relevant to web video.

      And Flash is probably more often paired up with h.264 than h.263 these days.

      For people who are content to ignore anything but Flash 9 maybe.

      And if it isn't yet, it will very soon be.

      And Firefox will be paired with Theora if it isn't yet. Or maybe people who are content with Sorenson Spark will see no reason to shell out for H.264, unless you have a crystal ball you can't know what MPEG LA will do at the end of the year.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    5. Re:Why is this Mozilla's problem? by Goaway · · Score: 1

      MPEG-2 rules, because the DVD isn't going away quite yet.

      However, the format of DVDs do not really affect the web in any meaningful way.

      For people who are content to ignore anything but Flash 9 maybe.

      Which is most people, with the fairly aggressive update cycles for Flash.

      Or maybe people who are content with Sorenson Spark will see no reason to shell out for H.264,

      I doubt anybody is content with h.263.

    6. Re:Why is this Mozilla's problem? by arose · · Score: 1

      However, the format of DVDs do not really affect the web in any meaningful way.

      Well, thanks for restating what I've been saying all along. What non web-enabled devices use is not relevant. I remind that you argued H.264 should be used because "it's used everywhere", without specifying the everywhere.

      I doubt anybody is content with h.263.

      So we should all adopt H.264 and pay the MPEG LA through the nose because what you personally believe other people are content or not content with?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  40. Re:HTML5 Video by TheLink · · Score: 4, Interesting

    Why's that modded troll? Quicktime has annoyed me enough to uninstall it. I still have flash installed.

    Installing quicktime puts some stupid icon in the systray that annoys you every now and then. If you're not careful while installing quicktime, you might get itunes bundled along.

    Adobe hasn't got around to making flash as annoying as quicktime yet (but they have made Acrobat Reader annoying thus I no longer have it installed).

    --
  41. Re:HTML5 Video by Hatta · · Score: 5, Insightful

    Why can't Mozilla just implement a plugin framework, and leave it up to the user to decide whether he wants to install the h264 plugin, which may or may not be illegal in his area. Some Linux distros ship without MP3 support because it requires licensing, and it's usually just one command to enable MP3 support. It seems like the same thing should work with h264.

    --
    Give me Classic Slashdot or give me death!
  42. sopssa by Anonymous Coward · · Score: 0

    sopssa is a well-known M$ asskisser, and he will be modded up by other M$ fans.

    They modded AC troll.

    1. Re:sopssa by Anonymous Coward · · Score: 1, Funny

      Everyone's a shill. Get cancer and die.

  43. Re:HTML5 Video by mrsteveman1 · · Score: 1

    h.264 is an open standard, the spec is available online, for free, right here: http://www.itu.int/rec/T-REC-H.264-200305-S

    Of course you need to pay to implement it, but lets not pretend it's a black box or 'closed' just because it isn't literally free to pass around like friendship bread.

  44. documenting it on http://en.swpat.org by H4x0r+Jim+Duggan · · Score: 1, Troll

        Regarding software patents, I've gathered some info already about H.264 and the standards problem:

    It's a public wiki, help welcome.

  45. A fab costs a lot, if you can afford one by Anonymous Coward · · Score: 0

    A fab costs a lot, if you can afford one you can afford a license.

    And it's an invention: a real thing that has to get around those pesky real life things, unlike the maths that is a compression algorithm.

  46. Re:HTML5 Video by Anonymous Coward · · Score: 0

    - Opera is a commercial product and they do a lot of business in embedded devices, mobile phones, wii and tv's and so on. They probably want to get a tech to play video for devices without new Flash versions (especially since it's 100% Adobe's responsibility to update Flash on those devices and Opera can't do much about it)

    Distributing Flash is still 5 million dollars cheaper per year than to pay current licensing rates from MPEG-LA, so it's quite obvious why Opera is supporting Ogg Theora instead of h.264. One could argue that Flash with Ogg support would be a better solution for the Web than HTML5 with h.264.

  47. DON'T PANIC! by Mad+Fish+The+One · · Score: 3, Informative

    Mozilla is going to implement gstreamer backend for html5 video element. See Bug 422540.

    Also, Opera developers are going the same way. See this blog post.

    Using gstreamer as a backend will eliminate ALL the problems with codecs. Forever. It will be able to play just the same as a usual desktop players, and that means, it will be able to play Ogg Theora, H.264, DivX, whatever you like - it's only a matter of plugins installed.

    1. Re:DON'T PANIC! by TerranFury · · Score: 1

      If they're using gstreamer on Linux, then I guess they'll implement a DirectShow backend on Windows?

    2. Re:DON'T PANIC! by Mad+Fish+The+One · · Score: 1

      gstreamer is quite mature and can be used on Windows and Mac OS X as well. So there are no reasons to make different backends for each OS.

  48. Re:HTML5 Video by Draek · · Score: 0, Troll

    H.264 is as open as Microsoft Shared Source or OOXML. Forgive me, then, if I don't really consider it "open".

    --
    No problem is insoluble in all conceivable circumstances.
  49. Theora lock-in? by harlows_monkeys · · Score: 1, Redundant

    Under Mozilla's approach, what happens when someone develops a new, free, codec that is better than Theora? If they aren't going to support using the codecs that are on the host system, just how do the early adopters start using the new codec?

    Are we supposed to hold off on using the new codec until Mozilla determines it to be Firefox-worthy and builds it into the browser?

    1. Re:Theora lock-in? by Improv · · Score: 1

      It's not like the industry is going to suddenly shift formats in five minutes and Firefox can only make a new release every five years.

      --
      For every problem, there is at least one solution that is simple, neat, and wrong.
  50. Re:Just give up your principles and compromize by Johnny+Loves+Linux · · Score: 1

    Mozilla doesn't have to implement anything, just make the video plugin architecture extensible.

    They can't do that as they explain in the blog entry a) that most windows users don't have an H264 codec and b) It's pissing on their principles (my words, not theirs). And I see their point. The Mozilla people want to be able to browse the internet with a completely free stack. That is their point: a completely free stack.

    What your suggestion is offering is a technical solution to the problem which unfortunately conflicts with their principle and thus they can't go down the road. I see Mozilla people's point and I agree with them. It's reasonable, logical and consistent. But I also understand there are a lot of people who read slashdot who just don't seem to understand what the point of freedom is.

    So, I'm going to propose the following thought experiment for people who just don't get why it's important not to throw away your principles for a quick and easy solution that violates your principles. So suppose you're in the following scenario: you get to recieve a pile of money in exchange for a corporation to cut off your right leg (why? Who knows what their motivation is.)

    1. Do you reject the proposal out of hand without even determining how much money is involved?
    2. Do you bargain for how much money you'll take for the loss of your right leg?

    What if it was only a few toes say of one of your siblings, or a living parent, or one of your children if you have any? Would you be willing to bargain away someone else's toes?

    Now, some of you might be willing to bargain but rationalize to yourself "Hey, I didn't sell out cheap, I got $XYZ dollars for my right leg! Or. hey my brother didn't need his little toe to live, I'll cut him in for 30% of the money". I'm sorry to say that if you're someone who would do a thing like that, I don't understand you and I doubt that I ever will. From my perspective, you have no principles except possibly the pursuit of money which as a goal I just don't see much point. Pursuit of money as a goal is not a socially constructive purpose. If this is you then it's obvious why you don't grok Stallman and the Free Software Foundation. If you happen to be an American, you probably also don't grok the value of the Bill of Rights either right up until a cop splits your head open for resisting arrest while doing nothing. Then all of a sudden you might appreciate your freedoms with a little more enthusiasm.

    As the blg points out that yes, H264 patents will run out on 2017, but that is not the end of patented video codecs, there will be an H265 that follows it and so on. If you value freedom then you can't piss away your freedom or others' freedom by compromising on freedom in the name of expediency.

  51. Re:HTML5 Video by El_Muerte_TDS · · Score: 2, Interesting

    It's mostly just problem for Mozilla

    And every site that wants to host their own video content. H.264 also requires a license for hosting content. All those sites will probably stick to Flash if other browsers don't support Theora.

  52. HTML5, SVG, etc = BS by El+Cabri · · Score: 0, Flamebait

    I really don't understand why Silicon Valley type geeks get so excited about the alleged advent of "free" and "standard" web technologies such as HTML5 and SVG. First, as this story illustrates, these are not "free". More importantly, these are not "standard". SVG for example has existed as a finalized, commitee underwritted standard for more than eleven years now, yet not a single browser supports more than a subset of it, and each a different subset. Even if it had been supported by IE from the beginning (Adobe doesn't even bother to support their plug-in btw), web developpers would have faced the pain of making their app working across browser, which is bad enough currently with the JS situtation.

    Instead of having these commitee designed pseudo "standard" existing in abstract document and leaving it up to multiple browser and platforms to implement their own interpretation of it, I much prefer the model in which a few vendors develop mature plug-ins such as Flash or Silverlight that are guaranteeded to work the same whatever they're plugged into. Yes these are "proprietary" but so are your OS and drivers if you run Windows or MacOSX, so is the design of your CPU and GPU, etc.

    Better having working platforms which empower a multitude of developpers to get working stuff out to the public than abstract, broken chimeras that burden developers with absurd compatibility and licensing issues.

    Ponder over the original story and the paradox that the FOSSest browser out there might be actually better off loading a proprietary Flash or SL plug in than implement a "Free" HTML5 "standard"

    1. Re:HTML5, SVG, etc = BS by slim · · Score: 1

      I guess you weren't around during the Netscape years, when MS and Netscape were busy inventing their own ad-hoc and non-interoperable HTML tags with abandon.

      It was *horrible*.

  53. Mozilla doesn't need to pay a dime to support h264 by SideshowBob · · Score: 1

    Just use the platform's native video architecture. Then instead of some poorly optimized software-only codec (on most platforms; it would of course be optimized for Windows), the video would actually look good and perform well.

    I don't know what to do about Linux. But I'm not sure why the prevailing attitude is that Mozilla should be completely self contained and try to do everything themselves. Some other project besides Mozilla should be worrying about h.264 for Linux.

  54. I don't know what to say. by fibrewire · · Score: 1

    Considering all that is happened, i was trying to figure out how to get an IPTV box for free internet television out for the last 4 years, but i kept running into this same discussion. I guess the situation has finally come to a head.

  55. Re:HTML5 Video by aristotle-dude · · Score: 2, Insightful

    It's mostly just problem for Mozilla Only if people insist on using it. I can't see that it would be in YouTube's interest to use H.264 exclusively.

    YouTube already encodes everything in H.264 for embedding in Flash and for portable devices like the iPhone which consume the video directly since it does not support Flash. Why should everyone be forced to download or include in their portable device an Theora plug-in just to support yet another format when H264 is already available on all commercial desktop and mobile platforms?

    But in any case, it sounds like a misnomer to call it "HTML5 Video", which sort of implies a standard. If the "standard" involves coughing up a whacking great licence fee to use it, lots of people just won't be interested, and H.264 will be consigned to the same back shelves as some of the ogg codecs.

    Perhaps you should buy an old fashioned dictionary to look up the word "standard". I'm all for open standards but not when they are obscure or inferior to the industry standards and those standards are available for anyone to implement for a small fee.

    I hate to break it to you but almost everyone is already using H.264 to distribute video whether it be directly or embedded within a flash video file. It has wide industry support in both software and hardware (HD Video cameras). To use Theora, you would have to re-encode all of your video in order to use it.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  56. Re:HTML5 Video by iVtec · · Score: 1

    Actually it's a software patent problem that excludes small commercial vendors and open source vendors of any size. The HTML5 video spec does not define a standard codec, so using the operating system's back end is a reasonable choice for mozilla. The problem is that mozilla can not have native support for h.264 in any reasonable way that would let its users, or firefox variants for that case (like iceweasel/icecat, swiftweasel, etc), redistribute a modified version of their browser.

    This whole problem could be avoided if Google decided to push for VP8 on youtube and license it in a way it could be used in open source software without patent restrictions.

    Of course, the whole problem could be avoided altogether if software patents weren't allowed in the first place. This is a fine example of legal Bullshit getting in the way of technology.

  57. We shouldn't wish to be forced to... by pmontra · · Score: 2, Interesting

    ... pay to create and distribute video content or having to upload it on the few big sites that have enough money to pay the royalties to MPEG-LA.

    We might decide to use h.264 anyway because it's technically better but what I expect is that customers and content creators should be happier to see a totally free codec succeed over one that will cost them money.

    Youtube, Vimeo & Co are trying to use h.264 to become the new majors. I understand why those companies don't want a free codec to succeed: that would lead to more competition and less ways to profit from their position. I'm afraid that in this case their best interests are our worst interests.

    Think if it happened to images. You could only legally upload graphics to Flickr, Facebook and a few dozens of other big sites with the money to pay royalties. All vacation pictures and UI buttons would have to go there. Figuring out what the web would look like is left as an exercise to the reader.

    1. Re:We shouldn't wish to be forced to... by Anonymous Coward · · Score: 0

      Youtube, Vimeo & Co are trying to use h.264 to become the new majors.

      That's not going to work; no Browser of any consequence supports that standard.

    2. Re:We shouldn't wish to be forced to... by Anonymous Coward · · Score: 0

      I understand why those companies don't want a free codec to succeed: that would lead to more competition and less ways to profit from their position.

      I doubt that has anything to do with it. They want users to have the best user experience on their site that they can, and currently there is little competition there. Ogg theora and h264 are just not on the same playing field.

      I can decode 1080p h264 with only 10% cpu usage on a core2duo (with VDPAU). Can theora do that? Will theora ever be able to do that? I doubt it.

        Last I checked h264 offered better picture quality for the same bitrate too, which certainly is a factor. Having to up the bitrate means higher system requirements for your users and more bandwidth costs, which is the bottom line on video sites.

    3. Re:We shouldn't wish to be forced to... by Anonymous Coward · · Score: 0

      Or, maybe, YouTube and Vimeo use h264 because it's a superior codec that gives higher quality at lower bitrates - which is very important for streaming video? Not everything is a big financial conspiracy.

    4. Re:We shouldn't wish to be forced to... by BikeHelmet · · Score: 2, Insightful

      Youtube, Vimeo & Co are trying to use h.264 to become the new majors. I understand why those companies don't want a free codec to succeed: that would lead to more competition and less ways to profit from their position. I'm afraid that in this case their best interests are our worst interests.

      They're using H.264 because of the bandwidth costs. When you're looking at saving hundreds of thousands of gigabytes, the savings add up to very real amounts. It's not about stifling competition - that's a side effect. It's about cutting costs.

      Think if it happened to images.

      I thought it did happen to images? Aren't JPEG/GIF - the most widely used formats online - patent encumbered? I don't recall anything apocalyptic happening with them, but I have a feeling MPEG-LA will be more pushy. After all, they want money so they can work on H.265.

    5. Re:We shouldn't wish to be forced to... by shutdown+-p+now · · Score: 1

      You aren't forced to do anything. HTML5 does not mandate H.264 support for VIDEO element. If some browsers chose not to support it, and some websites chose not to offer it, they're still conformant.

    6. Re:We shouldn't wish to be forced to... by pmontra · · Score: 1

      I thought it did happen to images? Aren't JPEG/GIF - the most widely used formats online - patent encumbered? I don't recall anything apocalyptic happening with them,

      Apparently it didn't happen to JPEG and all the GIF patents expired between 2003 and 2004. PNG was born a free alternative to GIF in 1996 because of those patents.

      but I have a feeling MPEG-LA will be more pushy. After all, they want money so they can work on H.265.

      I smell sarcasm here and I agree. I sincerely doubt that they're going to invest all the money they get into new technologies. I think they'll want some profit, which is OK, but why should I be happy to give them the money and to others the control of Internet video?

  58. Re:HTML5 Video by Goaway · · Score: 3, Insightful

    Because their opposition to h.264 is ideological, not technical, so a technical solution is not enough for them.

    They are definitely muddying the waters by coming up with weak technical excuses for not doing it too, though. Those excuses are mostly easily refuted, and just makes the whole thing even more confusing. They should be more honest about it.

  59. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Any chance 3rd party developers can make a h.264 enabling extension for Firefox? I'd pay a few dollars for that.

  60. Re:Ideology meet reality that's why FSF will win by Johnny+Loves+Linux · · Score: 3, Insightful

    Here's a relevant quote from Geore Bernard Shaw. Quote:

    "The reasonable man adapts himself to the conditions that surround him... The unreasonable man adapts surrounding conditions to himself... All progress depends on the unreasonable man."

    So you're asking the Free Software People to give up their principles in favor of expediency and thus promote no progress. I think not. I prefer to live in a world of Freedom than one ruled by expediency. Expediency might win a battle but in the end principles win the war. Considering the progress of GPL software for the past 26 years I would say they are doing a damn fine job of promoting positive progress. Better for the reasonable man to use free and open standards codecs than the Free Software People piss away their principles.

  61. Re:HTML5 Video by sopssa · · Score: 1

    It is open. Just because theres licensing costs it doesn't mean the underlying technology isn't open. Free != Open, even if open usually goes along with free. But it's not necessary.

  62. Re:HTML5 Video by icebraining · · Score: 1

    - Apple definitely needs to support it in MAC OSX and maybe iPhone too, so WebKit and Safari will most likely support it.

    Webkit is GPL and BSD, you can't distribute a paid patented implementation of a codec with it.

    Safari can support it as a "module", but Webkit can't. It's the same reason why Mono doesn't distribute the MS codecs, even though they cost 0.

    Being GPL or BSD implies that you can redistribute it, but you can't do that to the H264 codec, so it would conflict.

  63. Re:HTML5 Video by sopssa · · Score: 1

    This is a fine example of legal Bullshit getting in the way of technology.

    In a way, but not completely. You can blame software patents about it, but the fact is that if those weren't available, MPEG-LA would just use a different method to generate revenue back on their technology. Now they could open up their technology, because they can still ask for licensing costs because they hold the patent. If they couldn't, they wouldn't have opened it up and would use some other way.

    That is a fine example of how capitalism works and why changing one thing doesn't always work out as you would expect.

  64. Re:HTML5 Video by Anonymous Coward · · Score: 0, Insightful

    and H.264 will be consigned to the same back shelves as some of the ogg codecs.

    H.264 is the de-facto standard for online video now. Just about every device has decoding for it in hardware these days, phones, PMPs, TVs et al. Being supported by large companies and market leaders means it's here for a very long time.

    OGG has never been popular and is now getting dropped from various projects due to lack of use. It's a near dead format, despite it's benefits over MP3, it simply never achieve support in almost all devices, or obtain any interest by consumer device manufacturers.

  65. Re:HTML5 Video by larry+bagina · · Score: 1
    Almost everything he said is wrong on some level.
    • Chrome supports H.264 today.
    • Safari and Mobile Safari support H.264 today. On day 1, the iPhone youtube app played youtube videos via H.264.
    • If you look at actual usage statistics, the iPhone dominates in terms of actual usage.
    • Opera does not support H.264 and my understanding is that they don't want to
    • Microsoft recently announced they would support HTML5 but who knows when or how well. Ask yourself: will they license H.264 or push WMV?
    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  66. It's also plain old maths. by Anonymous Coward · · Score: 0

    It's also plain old maths. And, as such, is not patentable. So it's ALREADY a borked patent.

    And you STILL have to rely on A.N.Other to provide your video. You now have to say "supported on Browser X,Y,Z... on OS A,B,C.." instead of "supported under HTML 5".

    Which do you think is going to cause least customer confusion?

    And if your customer is confused, will they buy or leave?

  67. Re:Just give up your principles and compromize by Goaway · · Score: 2, Insightful

    They can't do that as they explain in the blog entry a) that most windows users don't have an H264 codec and b) It's pissing on their principles (my words, not theirs)

    The first is a silly argument: Is it somehow better to play on NO computers, than to play on only SOME?

    The real reason is the second, that they are ideologically opposed to it. And that stance is only going to hurt them, and they should just get over it. It is not a fight they can possibly win.

  68. Re:HTML5 Video by flooey · · Score: 1

    Only if people insist on using it. I can't see that it would be in YouTube's interest to use H.264 exclusively.

    The YouTube guys have said that they don't want to spend the hard drive space to hold three different formats on disk (and considering 20 hours of video of video are uploaded to YouTube every minute, I can't blame them), and that the bandwidth requirements for the same level of quality are significantly higher for Theora than for H.264. So basically, YouTube uses H.264 because it's cheaper than any alternative, presumably even after factoring in licensing costs (which I think are capped at like a few million dollars for each licensee, and thus are probably noise to YouTube).

  69. Re:HTML5 Video by arose · · Score: 1

    Since Firefox already has it's Gecko engine and wide range of plugins, why don't they make themself more reasons to forget about Flash and start using open standards?

    They are. H.264 is not open enough to be shipped with a FLOSS product that is playing strictly by the rules. The question is why Apple and Microsoft are not supporting open standards, because Theora support is in Chrome and pre-release versions of Opera.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  70. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Installing quicktime puts some stupid icon in the systray that annoys you every now and then. If you're not careful while installing quicktime, you might get itunes bundled along.

    It seems that you are on a Windows system; you need to install QT Lite.

  71. The Theora bitstream format is frozen by tepples · · Score: 2, Informative

    You know that Theora is a work-in-progress, right? That right there says GO AWAY

    The Theora bitstream format is frozen since the beta. All the work in progress is directed at 1. performance of the decoder, and 2. quality of the encoder while producing bitstreams that still play correctly on all conforming decoders.

  72. Re:HTML5 Video by TheRaven64 · · Score: 3, Informative

    It's modded troll because it's from someone who can't tell the difference between a media API and a media player. The ClickToFlash plugin for Safari will let you use QuickTime for YouTube and it uses about 10-20% of the CPU that Flash uses, while presenting a UI that is more consistent with the rest of the system and the same features (although better buffering). Anyone who'd rather use Flash is an idiot or a troll.

    --
    I am TheRaven on Soylent News
  73. No, I won't pardon you for being retarded. by Anonymous Coward · · Score: 0

    No, I won't pardon you for being retarded. It's even mentioned in the links, not to mention several times here on the thread.

    Distributing the output of a patented algorithm IS being threatened with a license fee. Their claim is like the output of a program (to the screen) is copyrightable/protected (one click shopping, for example. Or Look n feel).

    The decompression without license doesn't make sense because it's using the patented algorithm just as much. And they've only stated this is fee-free until this year.

    And you will STILL have the problem of "I've put a video on line, but many customers cannot see it". Instead of being unable because the browser cannot do it, it's unable to be seen because the computer OS cannot do it.

  74. Re:HTML5 Video by sjames · · Score: 1

    You missed a lot of the point there. Part of the point is that once Mozilla coughs up that 5 MILLION bucks, the browser is in the clear, but now people wanting to actually produce something in H.264 format, they have to cough up again and if (god forbid) they actually want to 'bvroadcast' that video, they get to cough up some more.

    The argument is that it's better to support something that regular people can afford and don't need a law degree to understand the licensing terms for.

  75. Re:HTML5 Video by LO0G · · Score: 1

    Not only does Microsoft license H.264 in Windows 7, but any application written for Windows 7 can play back H.264 content.

  76. Do no Evil ????? by DrLov3 · · Score: 1, Troll

    Step #1 : Buy youtube.

    Step #2 : Switch the video format on youtube to H.264, a proprietary format that free browsers can't afford the licenses it needs to distribute a reader for it.

    Step #3 : Push H.264 part of the open standard HTML 5, even though it's not open at all, thus further shoving free browsers downward the spiral.

    Step #4 : Win the browser War, pwn the internet, make profit with ur browser built in search engine.


    ..... F***ers, .... (Shakes Fist)
    We were paying attention....

    1. Re:Do no Evil ????? by shutdown+-p+now · · Score: 1

      Step #3 : Push H.264 part of the open standard HTML 5

      H.264 is not part of the HTML5 standard (no codec is).

      The issue at hand is that H.264 will become a de facto standard, in the same way as GIF and JPEG became de facto standards for images on the Web (similarly, HTML spec for IMG element never mandated support for any specific formats).

  77. You're not lying, so what does this tell us? by xigxag · · Score: 1

    But I can play flash from within FF.
    And if flash is H.264, then I can play H.264 from within FF.
    But this is impossible.
    Therefore you are lying.

    --
    There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
    1. Re:You're not lying, so what does this tell us? by furball · · Score: 1

      Flash is provided by a plugin to play within FF. The playback is enabled by external software to what Mozilla produces.

    2. Re:You're not lying, so what does this tell us? by xigxag · · Score: 1

      Exactly. My. Point.

      This whole issue of Firefox dying because of a lack of H.264 doesn't exist. A freeware plugin could be just as ubiquitous as flash. It wouldn't even need to license anything. Windows and Mac both come out the box with H.264 codecs baked in, the plug-in would just have to link to those codecs.

      --
      There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
  78. software patents are immoral by circletimessquare · · Score: 3, Insightful

    and contrary to the concepts of a free market

    we should actively rip off h.264, not because we want to use the codec for free, but simply to undermine the status quo that some people, for whatever reason, respect this bullshit called software patents

    those who created the codec need to depend upon ancillary streams of revenue, such as hardware prodcuts that depend upon the software ideas. meanwhile, patenting a simple arrangement of bits is contrary to the free exchange of ideas

    you should only be able to patent physical objects

    everything else is abstract representation: this should never be protected. do we respect the idea that the church of scientology has a copyright on its sacred texts? of course this is bullshit, just as much as it is bullshit that the RIAA attempts to control the flow of bits, or that the chinese autocracy attempts to control the flow of information: the entirety of the phylosophical concept of putting roadblocks on the flow of ideas is a form weakness, failure. it leads to a less rich society

    ip law must be actively fought

    luckily, this is all too easy, because the internet is the disruptive techology that destroys ip law, whether some people like it or not

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:software patents are immoral by reub2000 · · Score: 1

      This would punish anyone who wants to follow the law. A better approach is to simply not implement it. Firefox is currently used by a third of web users, and not supporting it would mean that there is no way for H.264 to become universal.

    2. Re:software patents are immoral by Eil · · Score: 1

      do we respect the idea that the church of scientology has a copyright on its sacred texts?

      I can't speak for you or anyone else, but my answer is yes: I do respect the idea that the CoS has a copyright on whatever publishes. Because no matter how batshit insane/corrupt/immoral the organization is, Free Software would not exist without copyright and Free Software is pretty important to me. The CoS needs to be fought for the things that they are truly guilty of.

      of course this is bullshit, just as much as it is bullshit that the RIAA attempts to control the flow of bits,

      Not sure exactly what you mean by "control the flow of bits," but if you're talking about DRM then I'd have to say that you're always free to vote with your money and not buy content or devices which are encumbered by DRM.

      or that the chinese autocracy attempts to control the flow of information: the entirety of the phylosophical concept of putting roadblocks on the flow of ideas is a form weakness, failure. it leads to a less rich society

      I'm not supportive of the Chinese government's policies and actions, but good luck with that "less rich society" line when China's economy has boomed over the last few decades and a significant percentage of their citizens are just now getting a taste of what we Americans have considered a middle-class lifestyle for almost a century. If their economic growth continues as is, (and our continues to stagnate) then China could easily overtake the U.S. as the world's leading superpower within my lifetime.

      ip law must be actively fought

      No, the bad parts of IP law must be actively fought. How would you feel if some big shot in Hollywood took your low-budget horror flick, softened the dialogue a bit, refilmed it with CGI special effects, gave the starring role to Brenden Fraser, made hundreds of millions in merchandise agreements alone, and didn't even bother to say thanks? I guess you'd be okay with that. I sure wouldn't.

    3. Re:software patents are immoral by crimperman · · Score: 1

      You know, whatever argument you are trying to make will be a lot easier to read if you fix the shift keys on your keyboard.

    4. Re:software patents are immoral by badkarmadayaccount · · Score: 1

      Leaving us with Flash, using... H.264! Only for FF of course. I say, Mozilla scream anti-trust, and fucking rape the MPEG-LA in court. I doubt Google is going to chime in, but we can at least hope. And we've still got Nokia, who wouldn't mind to stop paying fees, and don't really love Apple.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    5. Re:software patents are immoral by Improv · · Score: 1

      We can do it on an individual level, but we can't do it on other levels - IP police might not manage to catch every individual, but if the Mozilla foundation were to itself violate patent/copyright protections, it would lose. I agree with you on what should happen in the long run, but we shouldn't expect Mozilla to die for our beliefs. They have to fight this on another level, by simply steering away frm proprietary codecs when possible.

      --
      For every problem, there is at least one solution that is simple, neat, and wrong.
  79. Fork? by zokier · · Score: 1

    What we need is clean fork of Firefox which would have some kind of h264 support. It should follow otherwise upstream as closely as possible and be 100% compatible with extensions and themes. Of course MozCos trademarks should be avoided. So, a catchy domain, few devs and some marketing, and MozCos stubbornness wouldn't matter anymore. I'd guess even Google could help to sponsor this kind of project, as it's in their interest to get the format war over.

    1. Re:Fork? by shutdown+-p+now · · Score: 1

      What we need is clean fork of Firefox which would have some kind of h264 support.

      All we need is a clean fork of Firefox that supports native OS APIs for media codecs - DirectShow, GStreamer, QuickTime. This takes care of H.264, as well as any future codecs that may become popular.

  80. Re:HTML5 Video by arose · · Score: 1

    I hate to break it to you but almost everyone is already using H.264 to distribute video whether it be directly or embedded within a flash video file.

    Only "everyone" who is already distributing video on the web, that is to say, a small minority of web sites. Nd even then, not all flash video is H.264 a huge chunk (if not most) is Sorenson Spark as it is has been supported longer in Flash. People who do not yet stream videos are more likely to be affected by what MPEG LA decides to do about distributors. Support in HD video cameras is irrelevant, unless you plan to post full resolution, un-edited videos from them.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  81. Can we please just start promoting Dirac ? by /.Rooster · · Score: 1

    I don't want to sound like a repeating record but the Dirac codec produced by BBC R&D is royalty free and extremely good.

    I am sure if you look you will find more but start with these links.

    http://en.wikipedia.org/wiki/Dirac_(codec)

    http://diracvideo.org/

    http://sourceforge.net/projects/dirac/files/

    and if you can watch the promo too.

    http://dirac.kw.bbc.co.uk/download/video/maybefinal/

    why are we still debating this?

    --
    Rooster - A friend. "Anyone's friend in particular or just generally well disposed to people?"
    1. Re:Can we please just start promoting Dirac ? by atilla+filiz · · Score: 1

      Because major players don't want to use royalty-free codecs? Maybe?

  82. Re:HTML5 Video by arose · · Score: 2, Informative

    MPEG-LA didn't "open" anything, they are a post-factum licensing agency, the actual standard was created by the ISO/IEC Moving Picture Experts Group.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  83. Re:HTML5 Video by iVtec · · Score: 1

    Your definition of opening up their technology excludes small competitors and open source altogether though. And they are a large part of the competition out there today. Even inside a patent regime like the one in the US, there are ways to license your technology such that it does not exclude competition, while at the same time making a handsome profit. Software patents are squarely the one to blame and RAND licenses in particular. Such licensing schemes often lead to oligopolies, which are quite ant-capitalistic.

  84. Re:HTML5 Video by slim · · Score: 1

    But in any case, it sounds like a misnomer to call it "HTML5 Video", which sort of implies a standard.

    As far as I understand, the HTML5 standard does not specify ANY standards. They tried, but there were people with vested interests on the committee, and it proved impossible to come to an agreement.

    So, HTML5 says you can use any codecs and any container format within a <VIDEO> tag. It's up to the developer to know what browsers support.

    Sucky, but there it is.

  85. What we REALLY need is... by JustNiz · · Score: 1

    YouTube et al to switch to Ogg instead.

  86. Codecs by edxwelch · · Score: 1

    Is it appropiate to put the video decode code in the browser in the first place? Media player's use the codecs that are installed on the OS. Presumably if they went this route they get the hardware acceleration that's built into the video card

  87. So a proprietary format became part of an HTML by Perp+Atuitie · · Score: 1

    standard? Can somebody explain how the hell that could happen? What does H.264 have to do with HTML5, exactly?

    1. Re:So a proprietary format became part of an HTML by shutdown+-p+now · · Score: 2, Informative

      It didn't. HTML5 doesn't mandate any codec for VIDEO element (just like HTML4 doesn't mandate any format for IMG element). The server specifies the codecs it can provide in HTML markup, and the browser picks the best one it can handle.

      It just so happens that the only two major contenders are H.264 and Theora, of which H.264 is technologically superior but patent-encumbered. So Google and Apple are pushing for H.264 (they have already licensed it, so they'd rather go for better quality), while Mozilla and Opera want Theora (it's open and free to implement).

      Whoever wins in practice, it will be a de facto standard, not a part of the spec.

  88. Dirac and Snow by Anonymous Coward · · Score: 0

    What's the state of Dirac and Snow codecs. They're never brought up in these discussions.

  89. Use a different h264 by Anonymous Coward · · Score: 0

    It's not like the MPEG-LA has the only working implementation in the world. If you don't want their product then use one of the lgpl versions and dont pay them. Stop fussing over nothing.

  90. Flash by Anonymous Coward · · Score: 0

    Don't forget flash supports h.264 in addition to On2's VP#.

  91. How is this "Offtopic" assholes? by gbutler69 · · Score: 1

    This is precisely on-topic. No, I guess not. Why? Because you're in the 80 - 90%. Fucking Douche-Bag!

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  92. Re:Most vs. All by coryking · · Score: 1

    Right, because that makes a ton of sense. My mobile phone can play H.264... whats your excuse?

  93. Uhhh? by gbutler69 · · Score: 1

    You're aware that there is a Patent on the "Method", not on the specific software implementation right? Right?

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    1. Re:Uhhh? by Anonymous Coward · · Score: 0

      > You're aware that there is a Patent on the "Method", not on the specific software implementation right? Right?

      It is not a "method" patent. It's a patent on the algorithm, i.e. a software patent because the only possible infringing technologies are programs (whether run on general-purpose or on custom hardware).

  94. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Why can't Mozilla just implement a plugin framework, and leave it up to the user to decide whether he wants to install the h264 plugin, which may or may not be illegal in his area.

    WTF do you think we have now?

    We already have Flash, Windows Media Player, QuickTime, RealPlayer, Silverlight..... how many more video plugins do you want?

    Though, it's moot now, but we would have been far better served if HTML5 also dictated a codec.

  95. Offload to Video Card by Anonymous Coward · · Score: 0

    If the license fee for h.264 has already been paid by the video card company for on-card decoding, could Firefox offload the decoding, forgoing the need for a redundant license?

  96. Mozilla H.264 Fees = $5,000,000+ per year by CritterNYC · · Score: 4, Insightful

    If Mozilla were bundling H.264 support right now, it would be closed source (so forget about seeing it in Ubuntu by default) and it would cost them $5,000,000 this year. Next year, the fee will be even higher. So, Mozilla would have to allot 6% of their revenue (revenue, not profit) to supporting this one proprietary video codec.

    H.264 is only supported by Chrome and Safari (less than 10% of those online). Let's keep it that way and keep the barrier for entrance into the browser market from reaching insane proportions. Otherwise we'll be left with fewer choices in the browser wars since lots of people can't pay $0.20 per unit for a product they give away for free. Mozilla and Opera certainly can't. But for Google and Aple, supporting H.264 in their browsers is free since they already hit the $5,000,000 cap this year (Google due to all the encoding and streaming of it, Apple due to licensing it for iPods/iTunes).

    So, it's EASY for Apple and Google to support it since it's free and they already ship closed source products (Safari is closed source even though the underling webkit is open, Chrome is closed source even though the underlying Chromium bits are open). Mozilla would have to pay a ton of cash (and increasing) and add closed source bits to Firefox.

    1. Re:Mozilla H.264 Fees = $5,000,000+ per year by WiseWeasel · · Score: 1

      How about if I, as a Firefox user, could pay $0.20 for a license to play back h.264, maybe gaining access to some h.264 playback add-on from Mozilla.org? $0.20 to get rid of Flash playback is certainly worth it for me. It would sure beat the current option of "Tough shit, use Safari or Chrome for decent non-crashy web video playback!" I want a web browser with Firefox's extensibility, and the ability to play h.264 tags. Of those two features, playing the h.264 content without crashing is the more important one. I have rough equivalents to the FF add-ons I use on other browsers. Mozilla's current position, while ideologically respectable, is not practically acceptable. Unless someone somehow enables HTML5 h.264 playback in FireFox, it will be sad to have to give up such a nice browser over this issue, but that's exactly what I'll be doing.

      --
      "I like systems, their application excepted", George Sand (French)
    2. Re:Mozilla H.264 Fees = $5,000,000+ per year by Skapare · · Score: 1

      This sounds like an excellent reason to avoid H.264. But what if a system were set up whereby all the H.264 decoding was done purely in the video card? The application (such as the Firefox browser) would identify an area of its display for video location. That area would be passed on via the video display layer (X and it's video chipset driver) as translated to the full display, to the video card/chipset. Associated with that identified display location would be a data stream, with flow control, as well as an additional substream for metadata such as decryption keys where needed. Then the browser merely feeds a raw bit stream that X passes on to the video card.

      Is MPEG-LA going to want to claim licensing of the browser and/or display system (X) just because they are passing along a bit stream (that may even be encoded in something else besides an MPEG/H.264 format, so the software might never even know what it is) ?

      Even if they don't claim a right to license the raw bitstream transmissions just because the data might contain something encoded in a format they hold rights to, there is still an issue around licensing "per encoding". They are wanting to charges licensing at that stage based on how many viewers are actually going to decode and view it, or even potential viewers (e.g. licensing of broadcasts by market size). None of the articles gave any info on how the market size fits in per video hosted on a web site, since the potential "market" for a web page is the entire world.

      I emailed that organization about 3 years ago and specifically asked for licensing information. I got no answer. Perhaps they just don't want to address licensing issues for millions of individual web sites? But they clearly aren't coming out and saying those will be free, either.

      I did contact Unisys about licensing LZW, for inside GIF, many years back when that was an issue. At least to their credit they did answer, and were willing to discuss it. The problem was, the terms just didn't want to recognize a small operation that was generating GIFs on the fly (so there would have been LZW encoding going on, or else uncompressed GIFs). They wanted to license based on factors that I could not provide, such as number of subscribers (since there were no subscribers ... they didn't understand the web very well back then). The only alternative was a flat rate that was around ten times my whole first years startup costs. The lady I spoke with at Unisys did personally understand the issues, and acknowledged to me that she could clearly see that the licensing structure didn't work for me, and that her management clearly "did not get it" with respect to web usage. She also acknowledged that they were unlikely to ever make any effort to straighten it out with respect to "small users" that, in total, represented less than one percent of their licensing revenue.

      BTW, I would have switched to PNG for that project, but the PNG group made a serious error in not including basic animation within the standard. So don't get any idea that the open standards community does things well, either. PNG is a clear case of failing to completely address a need (they tried to replace GIF without addressing all of what GIF could do).

      MPEG-LA licensing seems to be as equally messed up as Unisys was. Maybe the same clueless management is there? Or maybe it's all the owners of all the patent components they are bundling that have turned it into a camel?

      Anyway, unless and until this is fixed (which I doubt will ever happen), then MPEG/H.264 is something for the open source, open standards, open access, open information, communities to stay away from. PNG, despite its omissions, did succeed to supplant a large portion of GIFs and managed to stay on as a viable image format. MNG, the motion successor to PNG, I'm not so sure of. JPEG did the rest and GIF pretty much was clobbered until the LZW patent ran out in most of the world.

      PNG didn't do as well as GIF and/or JPEG in most cases. Yet it

      --
      now we need to go OSS in diesel cars
    3. Re:Mozilla H.264 Fees = $5,000,000+ per year by bonch · · Score: 1

      Mozilla doesn't need to bundle H.264 support. Use a plugin. It's as if everybody has forgotten that Flash FLV files already support H.264, which means that Firefox already plays H.264 videos. A mini-campaign to fight a common codec will go nowhere, especially when the proposed alternative (Theora) is inferior.

    4. Re:Mozilla H.264 Fees = $5,000,000+ per year by jrcamp · · Score: 1

      By some estimates Firefox has over 270 million users. That is less than 2 cents a user. Can somebody tell me where to send my 2 cents (literally) so I can get on with watching adorable cats struggle to stay awake.

    5. Re:Mozilla H.264 Fees = $5,000,000+ per year by aristotle-dude · · Score: 1
      So then Mozilla could charge 99 cents as a one time fee to download the official binary per year (updates from within Firefox would be free for the year). They could also enforce that anyone releasing unofficial builds would not be allowed to call it "Firefox" or include H264 support. Most people are willing to pay 99 cents especially if you frame it as paying to support H264 support and to support future development.

      Cheapskates would be told that they have to download the source and build it themselves.

      The GPL offers free access to the source. It does not demand that binaries must be gratis.

      Another alternative would be to simply bind Firefox to Core Video (OS X) and Direct Show (windows). Firefox could offer linux users H264 support for a small fee as an optional download.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    6. Re:Mozilla H.264 Fees = $5,000,000+ per year by Anubis+IV · · Score: 1

      [citation needed]

    7. Re:Mozilla H.264 Fees = $5,000,000+ per year by Anonymous Coward · · Score: 0

      Safari is closed source even though the underling webkit is open, Chrome is closed source even though the underlying webkit bits are open

      FTFY

    8. Re:Mozilla H.264 Fees = $5,000,000+ per year by horza · · Score: 1

      It' an average $0.20 per user. Those that were paying would have to subsidise all those that were not. If nobody else wanted to then your plugin would cost you $5M.

      Phillip.

  97. Re:Just give up your principles and compromize by arose · · Score: 1

    The first is a silly argument: Is it somehow better to play on NO computers, than to play on only SOME?

    Yes, consistency is better then (from the users point of view) random breakage. If you are dealing with a large number of technically unsophisticated users then having youtube work on one computer and not another without being able to transparently fix it (as opposed to "Click here to install Flash") is worse then it consistently not working with and explanation.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  98. Um, hello? by coryking · · Score: 2, Informative

    Firefox users will just get routed to the old flash interface on YouTube. YouTube isn't gonna transcode the whole damn library into some silly format when they can just treat Firefox like a legacy browser and feed it H.264 wrapped up in a .flv. If anything, they wouldn't bother with the whole Video tag at all when Flash worked fine before.

  99. What? by gbutler69 · · Score: 0, Troll

    Nothing you said contradicts a single word of what I said. In fact, you just made my point.

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    1. Re:What? by coryking · · Score: 1

      So basically you feel left out because you want something for free? Again, my *mobile phone* plays H.264. It is the standard. Deal with it.

  100. Pay For It by CritterNYC · · Score: 1

    And someone will have to pay for it since shipping H.264 support costs $0.20 per unit. Either that or you have to avoid all countries that support software patents. That means you may to host downloads yourself, too, since all the big players in open source project hosting (SourceForge, Google Code, Ohloh, etc) are US entities.

  101. Ummm by CritterNYC · · Score: 1

    And what exact advantage does it offer over Ogg? It has the exact same chicken and egg issues (namely that TONS of stuff supports H.264 and *almost nothing* supports Ogg or Dirac.

    It's the exact same argument, but with a different codec.

    1. Re:Ummm by Skapare · · Score: 1

      This is the same old silly argument that leads to so many bad standards and ideas that get entrenched just because they are first. Firstness does NOT mean best in all ways. Often things that are first are terrible is quite many, usually because so many things were not learned at the time it came out. The point here is to specifically NOT use the argument "because it is already in use" as a counter to the argument "let's change it". Instead, such argument should justify why the change would cost more now, than leaving it the way it is forever. With your argument, we wouldn't even have digital TV. And in the case of OTA TV, the "TONS of stuff" was "ALL the stuff" and digital still won. In the case of H.264 "TONS of stuff" is still just a fraction. It's not like video has expanded to everywhere it will be on the web and internet ... not even close. Video is just getting started and what runs H.264 right now is a tiny fraction of all that will be running video in the coming years.

      The question is which to use for the growth that video will bring. The dilemma is both H.264 and Theora each do not solve all the issues. And the issues exist both in the decoding as well as encoding realms. So just having both formats available in web pages, or having both formats in the browsers, is not a viable solution. Making hardware chips that do handle Theora for phones is only a partial solution due to the bandwidth issue that phones have (which isn't a big issue for broadband, once the net neutrality rules get established that create strong competition). The answer may well be that the web will use Theora and/or Dirac (which I consider to be a better option than Theora, but it doesn't seem to be getting the press coverage it should), and the phone provides set gateways that convert to H.264.

      --
      now we need to go OSS in diesel cars
  102. You're a fool! by gbutler69 · · Score: 0, Troll

    You're a fool and a slave. Why don't you just get on about sucking the cocks of your corporate overlords while they pound you in your ass. You're so stupid, you don't even realize you are not "Free". It has nothing to do with "Free" as in price. Everything to do with "Free" as in Freedom. You don't even own your phone or the data on it you douche-bag. Your masters do. But, you won't believe it, because you are too goddamn stupid. All you know is it tastes sweet, looks shiny, and smells like flowers. If they coat their cock in sugar, scent it with jasmine, and polish it with chrome, you will drink their spooge like a good little slave. Jack-Ass!

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    1. Re:You're a fool! by coryking · · Score: 1

      "Free as in Freedom" is a talking point given to you by a different kind of overlord.

      Besides, I know what "Free as in Freedom" means but I happen to think it is rather impractical. I also disagree with a large part of platform the political party who publishes that talking point promotes.

  103. Re:HTML5 Video by mad.frog · · Score: 1

    Wow, that's a great idea. Maybe they could even get some other large company to write a plugin for H.264 for them! And get it installed on 97% of computers worldwide! Maybe they could call it "Flash"... </sarcasm>

  104. technical by zogger · · Score: 1

    No, it's technical, and this is what I think is going on here. It is economically technical, and I would bet/guess that higher level Moz folks are thinking about this right now. The planet is soon to be encumbered with some draconian restrictions on bits and bytes if you don't come up with the scratch that some folks demand for some of those bits and bytes. As soon as ACTA is made law all over, this "just download the naughty bits" that go to make your fav browser/OS/player "just work" for your listening and viewing pleasure will be tracked and people will start getting notices that this might result in getting their connection turned off, or worse, if they are distributing or facilitating the "naughty bits", perhaps charged with "enabling" or some other lawspeak.

        Sure, there will still be ways to "get the codecs" and install them, just the real world cost of doing so inside nations that have more effective policing will go up. Right now, not much enforcement, after ACTA, this will change rather severely. When you have all these major economies switching from durable goods for creating wealth to "IP" licensing, the moneysuits who 100% control your "elected representatives" will determine what gets ignored or not, what gets enforced or not. They will want their money, or no vid soup for you, unless you want to go from being a "casual criminal", as it is now with not much enforcement, with not much worries for most people, like "ya, sure, just go to the unrestricted repositories and download.." wink wink nudge nudge, to "man, this sucks, a fifty grand fine! I ain't touching that stuff. I'll have to use the officially approved browser/OS/Player" level, which is (a big part of) what ACTA is all about.

    This is coming soon to a computer reality near you. It's going to be a game changer. It's designed to be a game changer, they wouldn't be dorking around with it if it wasn't, and because they are, they will start enforcing their fees and restrictions a LOT more than what we have grown accustomed to.

    Ya, some will say they can stay pure and just use "hooks" for this or that in the software to allow these naughty bits to work..those moneysuits see billions that they ain't got and billions that they do want, the politicians see their cut coming, and this duality will soon be dictating to the cops and prosecutors, and they won't give a rat's ass about minor software technical things like that, they will look at the end result "whole" and go "you are guilty, pay up or else".

    This going to be for both content, and also how you get to experience this content.

    1. Re:technical by SanityInAnarchy · · Score: 1

      As soon as ACTA [wikipedia.org] is made law all over, this "just download the naughty bits" that go to make your fav browser/OS/player "just work" for your listening and viewing pleasure will be tracked and people will start getting notices that this might result in getting their connection turned off, or worse, if they are distributing or facilitating the "naughty bits", perhaps charged with "enabling" or some other lawspeak.

      It's been over a decade since DeCSS was released. If they haven't already, I very much doubt anyone will track down individual Linux users who downloaded x264.

      Short of that, Windows and OS X both have h.264 built-in, and there are legal ways of getting the codecs for Linux -- nothing "naughty" about it. The only problem is that for ideological reasons, Mozilla refuses to support these, even though the most users already have licensed codecs for just this purpose.

      "man, this sucks, a fifty grand fine! I ain't touching that stuff. I'll have to use the officially approved browser/OS/Player"

      I would think that would also rapidly transition to many websites supporting Theora instead, if it came to it. But again, this hasn't happened, and you're applying an absurd amount of slippery-slope fallacy here.

      Ya, some will say they can stay pure and just use "hooks" for this or that in the software to allow these naughty bits to work..those moneysuits see billions that they ain't got and billions that they do want, the politicians see their cut coming, and this duality will soon be dictating to the cops and prosecutors...

      ...at which point, it won't matter who won this battle right here. They'll just declare Theora to be evil and un-american, or they'll come up with some bullshit submarine patent (Apple's excuse for not supporting it) and the judges will allow it.

      You have to have some faith in the system, otherwise you may as well give up now and just ignore the law. And if you're going to do that, I don't see why you give a rat's ass about free codecs -- x264 works pretty well.

      --
      Don't thank God, thank a doctor!
    2. Re:technical by FlyingBishop · · Score: 1

      The system has already failed. The only reason we can backup DVDs is that the technology wasn't there yet. In a few years, they will have hardware DRM integrated into our displays, and the only way to backup our media will be with a network of mics and a video camera.

    3. Re:technical by SanityInAnarchy · · Score: 1

      The only reason we can backup DVDs is that the technology wasn't there yet.

      No, the reason we can backup DVDs is that DRM is inherently flawed, and cannot survive, especially as long as there's a remotely free Internet.

      In a few years, they will have hardware DRM integrated into our displays,

      And exactly how is this different than having hardware DRM integrated into our optical drives, which DVD already has? For that matter, how's it different than HDCP, which Blu-Ray is already using -- that's right, Blu-Ray can already encrypt the signal straight through to your TV -- but Blu-Ray has also been thoroughly cracked?

      --
      Don't thank God, thank a doctor!
    4. Re:technical by FlyingBishop · · Score: 1

      But you were appealing to faith in the system. Faith in the unprovable assertion that true DRM is impossible is simply naive.

      Blu-Ray is crackable because it still has to allow for a mess of hardware issues on the computer side. Straight from player to display with no intervention from other machines, and DRM is quite feasible, at least to the point that ripping will be prohibitively expensive next to simply exploiting the final analog gap.

    5. Re:technical by SanityInAnarchy · · Score: 1

      Faith in the unprovable assertion that true DRM is impossible is simply naive.

      Then I'll prove it.

      DRM relies on giving the user, physically (built-in to the player) or digitally, both a key and an encrypted copy of some media. Viewing the media (playing the movie) at all requires the possibility that this key can be used to decrypt this media. The "security" of DRM relies on a savvy user not being able to figure out how to put the key and the media together.

      It is security through obscurity at its finest.

      It is inherently flawed because all the ingredients are there. Your only solution would be to make the player somehow tamper-proof, physically -- any good ideas for how to make something cheap, mass-produced, and somehow tamper-proof? About all I can think of is packing the components in thermite, but that'd be kind of hazardous to try to sell that to consumers, and you'd have to replace a lot of units whether or not people actually try to break them.

      It's also inherently flawed because it relies on the security of individual keys. Remember 09 F9? All it takes is for one of those keys -- which you are, again, physically distributing to people who actively want to get at them -- to be leaked, and suddenly half your movies are broken.

      at least to the point that ripping will be prohibitively expensive

      Define "prohibitively expensive." The other flaw in DRM is assuming that if you make it "hard enough", the "average user" won't be able to crack it. The problem is, your opponent here isn't John Q. Public, it's a few very talented and very motivated pirate groups, of the sort who can afford to have their own dedicated FTP servers with gigabit (and more) bandwidth.

      And they only have to crack it once.

      After that, it goes from there to the newsgroups, and then to BitTorrent, and in less than 24 hours -- hell, probably less than 3 hours -- it's all over the net, and John Q. Public will fire up uTorrent and grab it from his favorite tracker.

      Worst case? It's not going to cost anywhere near as much per-viewer to support a group to crack your disc as it cost you to make the movie. Short of that, I think my principle holds -- it only takes one person (or a small group) with the motivation, skills, and resources, and your movie is all over the place.

      So is DRM impossible? No, but effective DRM is, unless you change your definition of "effective". Most in the game industry admit that DRM is considered "successful" if it's not cracked within the first few weeks to a month or so -- but implicit in this is the acknowledgement that any DRM they use will eventually be cracked, and that goes for console games as well.

      I am not entirely opposed to people protecting their copyright, but DRM is entirely the wrong way to go about it.

      --
      Don't thank God, thank a doctor!
  105. Re:HTML5 Video by mad.frog · · Score: 1

    You don't have to. Just use Flash -- Adobe has already paid the H.264 bucks for you. (You *do* know that Flash supports H.264 directly, right?)

  106. Oh, hi, it's you ? by Antiocheian · · Score: 1

    Firefox users will just get routed to the old flash interface on YouTube.

    Then what is the issue, you think ?

    1. Re:Oh, hi, it's you ? by coryking · · Score: 1

      There is no issue. I just think anybody who thinks that the day HTML5 hits YouTube will suddenly stop working on Firefox is kidding themselves. Firefox supports H.264 already--as a Flash plug-in. Why bother transcoding to a new codec for Firefox when the existing one works on Firefox just fine?

    2. Re:Oh, hi, it's you ? by Antiocheian · · Score: 1

      I agree but tell that to the astroturfers who think that h.264 on HTML5 would threaten Mozilla's market share. Look here:

      http://slashdot.org/comments.pl?sid=1522496&cid=30880802

  107. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Yes. And?

  108. Re:HTML5 Video by Hal_Porter · · Score: 4, Funny

    If only there was a company who had licensed H264 and distributed a plug in for free that worked with all major browsers - their business model would be to make money from the authoring tools.

    In fact, since this is going to be used for video, wouldn't it be even better if that plugin supported a Javascript like language, perhaps compiled to byte code and JITted to native code to get decent performance. Perhaps a custom graphics library that allowed people to make players with custom controls show a list of related clips once the video ended.

    Then open source browsers could use the plugin to show H264 videos.

    --
    echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  109. Yep, and... by gbutler69 · · Score: 0, Troll

    "I've go mine, get yours" is your only talking point.

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  110. TPB? by sourcerror · · Score: 1

    The most important thing is to persuade the Pirate Bay to support Theora but not H264.

  111. Re:Most vs. All by Goaway · · Score: 1

    It sure is nice that you have no real problems, so you have the time to get this worked up about such trifling matters.

  112. Re:Just give up your principles and compromize by Goaway · · Score: 1

    Said explanation being "We made this not work for you even though we could because we wanted to be fair to everyone"?

  113. Re:Just give up your principles and compromize by horza · · Score: 2, Informative

    The real reason is the second, that they are ideologically opposed to it. And that stance is only going to hurt them, and they should just get over it. It is not a fight they can possibly win.

    Deja vu. That's what people used to say about Linux and Open Source. They still appear to be around. Anyway, define 'win'.

    Phillip.

  114. Re:HTML5 Video by TheLink · · Score: 1

    Yeah, and instead of installing annoying Adobe Acrobat reader I can install some other PDF reader (and I do).

    But that's not really the point since when I said Quicktime I meant Apple's version of it. And I assume the OP meant that too. Similarly I believe "flash" meant Adobe's stuff.

    FWIW, I have tried Quicktime Alternative - and it was flaky too (crashes, hangs, doesn't fail gracefully, etc) - given that other codecs and video playing stuff I've installed don't give as much trouble I think quicktime is the problem[1]. So I uninstalled that too. I'm not going to bother trying QT Lite because frankly I don't feel like wasting more time on "quicktime".

    I don't care if in theory the technology is great, because in practice it isn't. For example when there video downloads with multiple format choices I have not noticed "MOV" videos being significantly smaller in typical cases. In fact they often seem to be bigger. Just google for mov wmv download trailer and look for examples with the same video at same res (e.g. 720p ) available.

    Why should I install some flaky software when the downloads aren't significantly smaller in practice?

    Maybe one day it will be less crap.

    [1] I don't blame the crashes on Media Player Classic (included with quicktime alternative) since in my experience it's less crash prone than VLC (which is subpar - I noticed when playing short videos VLC often doesn't render some frames at the end, VLC has lots of other annoyances too, but I'm digressing enough ;) ).

    --
  115. Re:Just give up your principles and compromize by arose · · Score: 1

    Said explanation will probably not be necessary on big sites that would be out of their mind to drop flash support. However trying and failing to load an appropriate system codec might lead to breakage and reflect badly on Firefox even if it wasn't their bug.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  116. Re:HTML5 Video by Anonymous Coward · · Score: 0

    - Microsoft can probably work out a pretty good deal with MPEG-LA, and licensing technology is no problem for MS.

    Microsoft is an MPEG-LA member. They'd probably pay little or nothing. And whatever it costs, they're already paying the maximum, because they're distributing H.264 in Windows 7.

    - Google aswell and they have to support it on YouTube anyway.

    Yeah, they're also surely already at the maximum premiums, so it probably costs them nothing extra to ship it in Chrome. (Which they already do.)

    - Opera is a commercial product and they do a lot of business in embedded devices, mobile phones, wii and tv's and so on. They probably want to get a tech to play video for devices without new Flash versions (especially since it's 100% Adobe's responsibility to update Flash on those devices and Opera can't do much about it)

    Here you're wrong. Opera is aggressively pro-standards, sometimes even more so than Mozilla. They likely won't support H.264 out of the box anytime soon. I believe current alphas support it only on Linux, where they use system GStreamer and so will use system codecs. On other platforms they bundle GStreamer with a fixed list of codecs.

    - Apple definitely needs to support it in MAC OSX and maybe iPhone too, so WebKit and Safari will most likely support it.

    They already do support it.

    The real question is not whether all browsers will support H.264, it's whether they'll all support Theora. If MS supports Theora, everyone will hate Safari for being the only one not to support it, so Apple will likely support it too, and it will be the only format that works on all browsers. But if MS comes out with <video> support for H.264 only, which seems likely, then Mozilla will have to seriously consider compromising, because it will have real trouble winning as a lone standout.

    Until then, Mozilla's refusal to compromise is buying Theora a lot of attention, and might help make it a better competitor to H.264. If they compromise now, Theora loses, but if they hold out, they can always compromise later if necessary at no great loss to web standards. Everyone will have to fall back to Flash for several years anyway, so the format war isn't making <video> that much less attractive; one extra browser will have to fall back to Flash, at worst.

    If H.264 does win: oh well. We tried. GIF didn't kill the open web, and nor will H.264. What we have to be really vigilant about is not letting another proprietary format get a foothold in the future. Then we'll be in the clear by 2017, if not earlier.

  117. No. by gbutler69 · · Score: 0

    There is no such thing as a patent on an algorithm. It is a patent on a method. You and I may know better, but that has nothing to do with the law. You make the mistake of trying to logical rather than legal. Everyone makes this mistake all along. They actually believe in the law because they think it matches up with what is logical. It does not! Most laws exist to give some individuals or exclusive groups power over you and everyone else. Why won't you just swallow it like all the other lemmings? Oh, my bad, you are an intelligent thinking individual who can tell the difference between what should be fair and logical and what is legal. Now, if only most people could understand this we'd be somewhere. But, instead, we have butt-wads like "coryking" and their, "My smart-phone does h.264, what's your problem?"

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    1. Re:No. by Anonymous Coward · · Score: 0

      > There is no such thing as a patent on an algorithm. It is a patent on a method.

      Call it whatever you want, it is still DE FACTO a software patent - do your homework, I'm not here to educate you.

  118. Re:Mozilla doesn't need to pay a dime to support h by BenoitRen · · Score: 1

    Congratulations, you're /. user #1001 to suggest this. Read why Gecko won't use DirectShow in the foreseeable future.

  119. Wow! by gbutler69 · · Score: 0, Troll

    How do you know what problems I have or don't have? How do you know I get worked up about this because I actually give a shit about other people's right to communicate? You assume much and offer little. You like to dismiss people who "get worked up" because you never bother to "get worked up" for anything you don't think immediately affects you. So, I'm going to invoke Godwin: First, they came for the right to produce video communication, and I said nothing; Then, they came for the right to consume video communication, and I said nothing; Then, they came for the right to produce written communications, and I said nothing; Then, they came for the right to read written communications and I said nothing; Then, they came for the right to speak communication, and I said nothing (because they had cut out my tongue).

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
    1. Re:Wow! by Anonymous Coward · · Score: 0

      EU states have been granting software patents willy-nilly for years now.
      There is no confusion as to whether the h.264 are software patents from a legal perspective.
      The confusion is with respect to the enforceability of the patents.
      Current EU law does not enable enforcement of those h.264 patents.
      But that still doesn't prevent the patent owners from threatening people.

    2. Re:Wow! by Anonymous Coward · · Score: 0

      > Did you even read what I said? What the fuck do you think you are educating me on? I just said it doesn't matter what it is in reality, but, what it is legally.

      Of course I read what you wrote. I'm not trying to educate you, educate YOURSELF. This is NOT a "method" patent, because the only "method" involved is an algorithm, and the only way to implement it is through SOFTWARE or FIRMWARE. "Method" patents are usually granted for business methods, not inventions like computer programs (of which these codecs are an example).

      Nobody is questioning your manhood. Geez, get a grip!

    3. Re:Wow! by gbutler69 · · Score: 0, Troll

      What exactly did I play into? What am I saying that indicates I'm a child? Who is trying to have fun and who is making a serious argument? Come on and come see this faggot-pussy: 2807 Summit Road, Copley, Ohio 44321. Come visit me and we'll see who is the faggot pussy! Bring it on you little wimpy ass bitch! Come fuck me if you think you're such a badass. I'll rip you apart you fucking leech!

      --
      Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  120. Re:HTML5 Video by TheLink · · Score: 1

    Maybe I'm lucky but I don't notice flash playback using very much CPU. Just tried it on youtube, full screen. 5% cpu usage. 10-20% of %5 is 0.5 to 1% CPU usage.

    I guess 5% to 1% is great for you, but to me such gains aren't worth putting up with quicktime. Especially since Apple keeps trying to sneak in itunes along with it. Anyone remember itunes causing BSODs? http://blogs.zdnet.com/Bott/?p=543

    I don't recall Adobe ever bugging me and suggesting I get "Flash Player Pro" when I try to play flash movies.

    Adobe is bad, but Apple has a worse track record.

    I sure hope someone comes up with a decent alternative when flash player gets as crap as adobe acrobat reader, but quicktime isn't a decent alternative to me.

    I don't think I'm trolling, so I guess you can call me an idiot, which is fine with me as long as I don't have to use quicktime.

    --
  121. Re:HTML5 Video by dryeo · · Score: 1

    See https://bugzilla.mozilla.org/show_bug.cgi?id=422540 you might have to copy and paste the URL as mozilla doesn't like being linked from slashdot.

    --
    https://en.wikipedia.org/wiki/Inverted_totalitarianism
  122. Re:HTML5 Video by slim · · Score: 1

    I can actually hear the 'woosh' sounds from here, as your point flies over the head of a million /. readers.

  123. Re:Just give up your principles and compromize by Anonymous Coward · · Score: 0

    The first is a silly argument: Is it somehow better to play on NO computers, than to play on only SOME?

    It is a question of resources. doing a lot of work for a solution that helps small amount of people on a single platform isn't that interesting to them. This will probably change when most Windows installs have these codecs (but this will take several years, if history is any indication).

    The real reason is the second, that they are ideologically opposed to it. And that stance is only going to hurt them, and they should just get over it. It is not a fight they can possibly win.

    This sounds eerily familiar... I remember how Mozilla developers and users were laughed at just a few years ago: many viewed the battle lost and saw IE-emulation and an activeX-implementation the only solutions that could make free software relevant in the browser space again.

  124. "RMS Free" by oldhack · · Score: 2, Insightful

    You know, "RMS Free" is a lot clearer than "Free", "Libre", blah blah. You say "RMS Free", and we all know what that means, and those that don't know won't falsely assume they know.

    --
    Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
  125. Re:HTML5 Video by Cyberllama · · Score: 1

    It is slow, it does crash alot, and it does take a lot of resources. It crashes more often than flash, in my experience, but flash is the bigger resource hog (both in cpu and memory). It's very unstable as a browser plugin and when using Firefox I avoid anything that might try to use quicktime as a browser plugin. It's pretty awful.

    If it weren't for my iPhone, I'd just uninstall quicktime. Unfortunately, Apple married the iPhone to iTunes and iTunes to quicktime -- so there's simply no way to avoid it. By the way, iTunes is also terrible. It might well be the worst software experience known to me. I cannot express enough how much I hate iTunes. It's the anti-iphone: slow as shit, super confusing to use, highly unstable, and weak on features. I could write you a 12 page essay on iTunes and why I hate it, and still probably have forgotten several points a long the way. It's TERRIBLE.

    Sorry, I just can't miss any opportunity to rant about iTunes.

  126. Wow! by gbutler69 · · Score: 2, Insightful

    Did you even read what I said? What the fuck do you think you are educating me on? I just said it doesn't matter what it is in reality, but, what it is legally. The law doesn't give two shits about what logical people like you and I think about it. We can trumpet from the highest towers, "It's a software patent", and they will say, "Shut the fuck up!"

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  127. Lies meet fud by Anonymous Coward · · Score: 0

    DailyMotion uses Theora. Wikipedia uses Theora.

    Flash based Video *is* H.264 these days, you're comparing unlike things. Flash can be used as an alternative for the tag. Codecs are an independent issue.

    The "hardware accelerated" point is mostly spurious. No one bothered adding special hardware for older codecs than H.264 because older codecs didn't have the utterly insane cpu requirements. The Theora decoder is several times faster than H.264 decoders. Yes, Theora doesn't get the same quality per bitrate that H.264 gets but thats not due to any flaws in Theora: Theora is optimized for lower cpu usage instead. There is no free lunch: Every codec must balance bitrate, quality, cpu usage, licensing/patents, and other factors. Theora strikes a very different balance than H.264. You might try to argue that CPUs are fast enough that H.264's addition usage is irrelevant, but you (and everyone elses) cries for hardware acceleration put the lie to that claim.

    Moreover, if you're defining "hardware accelerated" broadly enough that you can say "nearly every platform, desktop and mobile" or even just "most desktops" then you must only be talking about hardware colorspace conversion, which works equally well for Theora. On many platforms, "hardware acceleration" means little more than using the specialized media instructions most of which apply equally to Theora and H.264. On some smartphone platforms (like palm-pre, android devices, nokia table) it means using a dedicated DSP, and there is already a port there. My stupid little jailbroken Iphone decodes full screen theora at about 100fps using the arm optimized port.

  128. This is a losing strategy by reub2000 · · Score: 1

    If the MPEG-LA looked at history, they would know that pretty much every format universal on the Internet today, got that way because the player/viewer was offered free of charge. The MPEG-LA is basically shooting them selves in the foot by requiring a royalty to decode.

    1. Re:This is a losing strategy by Skapare · · Score: 1

      ... and also by requiring a royalty based on number of real or potential viewers for each encoding being done ... and also by requiring per-encode operation royalties when using already paid for and licensed encoders.

      Still, MPEG/H.264 could still succeed because there is a lot of specific demand for it. And it makes economic sense in some situations, such as mobile phones where an H.264 hardware decoder is already present, and in others where the licensee is "too big to fail" and has a royalty cap. So, much effort needs to be done to ensure that an open standard is at least a strong viable option.

      --
      now we need to go OSS in diesel cars
    2. Re:This is a losing strategy by Wesley+Felter · · Score: 2, Informative

      pretty much every format universal on the Internet today, got that way because the player/viewer was offered free of charge.

      Not really; MPEG-4 (aka "DivX") is patented and requires royalties; you just didn't notice because either someone paid the royalties for you or you're infringing the patents.

  129. Re:HTML5 Video by TheRaven64 · · Score: 1

    Sounds like you're using Windows. Try using Flash on any other platform. On my 1.5GHz G4 Mac, Flash uses 100% of the CPU playing YouTube content. QuickTime uses 30-40% (VLC uses around 20%, but doesn't look quite as nice).

    --
    I am TheRaven on Soylent News
  130. Re:Just give up your principles and compromize by Goaway · · Score: 1

    "Win" would mean Theora becoming the standard for video on the web. And no, that is not happening, no matter how much you idolize Linux.

  131. Re:Just give up your principles and compromize by Goaway · · Score: 1

    It is a question of resources. doing a lot of work for a solution that helps small amount of people on a single platform isn't that interesting to them.

    It is neither a small amount of people, nor a single platform.

    This sounds eerily familiar...

    Yet it isn't.

  132. yes, it would punish those who follow the law by circletimessquare · · Score: 1

    follow a broken, outdated, immoral law, and you will do worse off than those who disobey the broken scheme called ip law, yes, that is exactly true

    ip law punishes those who abide by so-called (easily circumvented) restrictions

    it rewards all of us, including creators, who ignore ip law

    ip law is simply unenforceable in the age of the internet, so stop trying to follow it anyways. you only get punished when you obey ip law

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:yes, it would punish those who follow the law by reub2000 · · Score: 1

      Every user that installs an H.264 decoder only increases the installed base of the codec. A larger installed base allows the codec to reach a universal status, which will mean more people buying this. If you really want to hit them where it hurts, then you won't install the decoder whether or not you payed for a license.

  133. Selfish format selection is immoral by Anonymous Coward · · Score: 0

    "we should actively rip off h.264, not because we want to use the codec for free, but simply to undermine the status quo that some people, for whatever reason, respect this bullshit called software patents"

    Let me guess, you're a ffmpeg developer, no? Well you sure sound like them: "Look at me! I'm sticking it to THE MAN by using his LICENSED FORMATS! TAKE THAT!"

    Listen up, idiot. The reason people use formats is for compatibility. Every other factor is secondary. Even if you're not a judgement-proof teen in the Ukraine you're going to be forced by market pressure to use the same formats he uses, because no one wants to be incompatible.

    THE MAN doesn't have to collect cash from each person in order to make a boatload of money, he'll happily go after the most likely to pay: MPEG LA has collected over $66 per every man, woman, and child on earth in codec licensing so far. They won't go after you, they go after your technology suppliers and the cost gets passed along. If thats ever not enough they'll simply have your government tax it out of you like the music industry has done with blank media in many places.

    You think you're screwing the man? You're a fucking idiot. By writing and using these excellent open source tools for encumbered formats you're assuring the man's success. Why do you think that MPEG LA does not enforce against flagrant violators like ffmpeg, VLC, etc? They are required to use the same terms for everyone, but they risk a hard smackdown by the FTC for antitrust abuse specifically because allowing those tools to go unmolested is good for business.

    The only way to screw the man here is to not adopt his formats. End of story.

  134. Greed will fix it by BlueParrot · · Score: 2, Interesting

    It was greed and corruption that brought about this situation and it is greed and corruption that will fix it. In particular:

    Google wants Microsoft's desktop monopoly to break, and at the same time they compete directly with Apple's iTunes. As a consequence their only realistic shot at this is to help Linux flourish.

    Microsoft sees Google as a threat to their monopoly and hence they can't let Google kill Firefox as Firefox users would likely prefer chrome to IE, thereby strengthening google further.

    RIAA, MPAA etc... don't want google to grow to strong since they don't want google dictating terms to them, something they could do if they become the de-facto only site to serve video.

    MPEG-LA will try to squeeze every penny from the patent licenses while the party lasts, something google and vimeo very much dislikes.

    Essentially the usual short-sighted greed over quarterly profits amongst companies will cause them to push the situation until it breaks. It may take a few years but eventually the very greed that made a patent encumbered format the de-facto standard is the same greed that will kill it.

    1. Re:Greed will fix it by Skapare · · Score: 1

      Greed didn't fix the LZW (for GIF) licensing mess. Why do you think suits will figure it out this time? Remember, the reason people like that have no clue is because they specifically reject clues.

      --
      now we need to go OSS in diesel cars
    2. Re:Greed will fix it by MathiasRav · · Score: 1

      Google wants Microsoft's desktop monopoly to break, and at the same time they compete directly with Apple's iTunes. As a consequence their only realistic shot at this is to help Linux flourish.

      Microsoft sees Google as a threat to their monopoly and hence they can't let Google kill Firefox as Firefox users would likely prefer chrome to IE, thereby strengthening google further.

      Or, you know, Google and Microsoft could be enemies and still both want Mozilla and Apple to die.

    3. Re:Greed will fix it by evilviper · · Score: 1

      Essentially the usual short-sighted greed over quarterly profits amongst companies will cause them to push the situation until it breaks.

      The MPEG-LA has been around for over a decade. How many years are you planning on?

      It may take a few years but eventually the very greed that made a patent encumbered format the de-facto standard is the same greed that will kill it.

      It's NOT greed that drives adoption of the technically superior format. Self-interest, OTOH, is a desirable trail, which resulted in many good technical standard.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  135. Re:HTML5 Video by sopssa · · Score: 1

    mozilla doesn't like being linked from slashdot.

    thats quite interesting. why not?

  136. Re:HTML5 Video by OmniVector · · Score: 0, Troll

    ... Installing quicktime puts some stupid icon in the systray that annoys you every now and then. ...

    Found your problem there. You're obviously using windows.

    --
    - tristan
  137. OK, but, that doesn't change anything... by gbutler69 · · Score: 0

    The original point was that Mozilla can't just go ahead and use h.264 because of Patents. Call them software patents, call them patents on algorithms, call them patents on methods. It doesn't matter. As long as it isn't a "Patent on a Specific Implementation" then Mozilla can't use it without infringing it. You can't publish video using it (after December 2010) without infringing it. You can't consume/view said video without infringing it. You will need to license to produce and consume. This CANNOT work for Mozilla and open web standards, It is a DEAD END!

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  138. GPL, 20 yrs old and still needed by SmallFurryCreature · · Score: 1

    Richard Stallman, must maligned by the "I just want my bread and circuses" crowd, is still one of the few who will say this consistently. Either you have free software or you are owned by the companies, and there is no half way.

    In 2010, the free license for h264 runs out, and then what? Must everyone suddenly pay for every use of the codec? It is all to easy to sacrifice freedom for a little bit of convenience, but every time you do it, you must spend far more if you ever want to get it back.

    Look at the origins of Firefox. We surrendered our freedom to IE, and it took a LOT of hard work to get it back. Now we want to do the same again? And for what? Replace Flash with another 3rd party program that is under the control of a company only seeking to maximize its profit?

    It will be interesting to see what is going to happen, I think it will be yet another setback, forever increasing the gap between open and closed software. Just as browsers are becoming more standardized so that everyone can use the web with whatever software they wish, another closed source element sneaks its way back in. Google might have reasons to do this, but it might well end up biting them in the ass. All MS has to do is create their own youtube, that supports HTML5, with only THEIR codec pre-installed on the OS. Google and Apple would have NO grounds to complain, since they did the same.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  139. you have to use some format by circletimessquare · · Score: 1

    and all i'm saying is use whatever the hell format you like: the creator can benefit in ancillary ways

    i could care less about "the man"

    i care about a set of laws that in the internet age has no more integrity or enforceability

    you'r hyperventilating and getting caught up in derivative conflicts

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  140. Variable frame rates by Anonymous Coward · · Score: 1, Interesting

    VFR is purely a container issue, not a codec issue.

    Ogg also supports VFR, with fairly modest overhead. It just does it somewhat differently than some other formats, more like how windows media does it: Rather than explicitly switching frame rates, you use a high stated frame rate (like 1000 fps) then skip the frames you don't need.

    Some of the 'features' Theora skips are responsible for Theora's much more reasonable CPU usage. Other ones (like interlaced coding) are locked up behind a wall of patents (but fortunately no one should give a shit about interlace support anymore). Part of the problem with comparing to H.264 is that its not just one format, there are a dozen different profiles and most devices (especially hardware decoders) can't play many of them, even most software players won't play deep video or 4:2:2/4:4:4. There is just one Theora, and it even has 4:2:2 and 4:4:4.

  141. Re:HTML5 Video by Graymalkin · · Score: 1

    QuickTime no longer enables the system tray icon by default and has not for a long time. I also don't see how you can get confused and end up with iTunes installed. The QuickTime installer only contains QuickTime, the iTunes installer contains both iTunes and QuickTime. I guess see how you can get confused on a second look, one is named QuickTimeInstaller.exe and the other is named iTunesInstaller.ex;, they both have "installer" in their name. How confusing, be careful out there!

    --
    I'm a loner Dottie, a Rebel.
  142. Re:HTML5 Video by Cronq · · Score: 1

    Beta versions of opera use gstreamer for video, so if you install H.264 gstreamer plugin (and such exists) then you will have opera playing H.264 streams.

  143. Video decoders in OpenCL or CUDA by tepples · · Score: 2, Insightful

    Nothing stopping them installing one...

    Except price.

    Also, most video cards these days support h.264 in hardware

    True, some mobile and set-top-box video cards implement the entire MPEG-2 or MPEG-4 stack on an ASIC. But Firefox is targeted at desktop and laptop PCs, and as I understand it, PC video cards support signal transforms that are useful for video decoding in general, such as cosine transform (IDCT), deblocking filter, and motion reconstruction. A Theora decoder written partly in OpenCL or CUDA would run on a video card just as well as an H.264 decoder written partly in OpenCL or CUDA.

  144. Re:HTML5 Video by slim · · Score: 1

    The thing is, both iTunes and Quicktime are stable and usable on Macs (no surprises there). Most Apple fanboys won't have experienced it on Windows.

    They'd doubtless assume the problems are somehow Windows' fault...

    The reality is that I think both are based on Mac-targeted source code, and work via a compatibility layer written by Apple. This adds some inefficiencies to what the code has to do. It also means they have Mac UI traits, that Windows users don't know what to do with.

  145. Re:HTML5 Video by TheLink · · Score: 1

    > Sounds like you're using Windows. Try using Flash on any other platform.

    No thanks. At home I use Windows, FreeBSD and Linux. I do the "desktop stuff" (videos, games etc) on Windows.

    So flash is crap on the Mac, and quicktime is crap on Windows. Not surprised actually.

    FWIW, Quicktime using 30%-40% CPU to play Youtube videos doesn't sound that great, but maybe that's due to the 1.5GHz G4.

    I thought the powerpc G4 had fancy instructions? Does quicktime use them to speed stuff up?

    How much CPU does quicktime on the newer Intel Macs use to playback youtube videos?

    --
  146. Re:HTML5 Video by slim · · Score: 1

    Windows works a lot better without Apple applications on it.

    Deliberate sabotage? Or just incompetence?

  147. Re:HTML5 Video by TheRaven64 · · Score: 1

    On my Core 2 Duo Mac, QuickTime uses around 5-10% of my CPU, flash uses 40-50%. It's less important on that machine, but on the older machine QuickTime can play 720p quite happily, while Flash can only handle normal quality YouTube stuff without dropping frames if nothing else is using the CPU. On my 1.2GHz Celeron laptop, Flash can't handle YouTube videos without dropping frames, but VLC can play them back using under 50% of my CPU.

    --
    I am TheRaven on Soylent News
  148. Re:HTML5 Video by Toonol · · Score: 1

    Yes, QT is far more unpleasant than Flash. Maybe it works acceptably when it's ran natively on a mac; but on other OS's, I'd lump QT in with Real Video. Immediate scrub off my machine if it shows up.

  149. Another video war? by ElusiveJoe · · Score: 1

    So it's like a major web browser creator versus major web video providers. I think the porn industry will say the final word again.

  150. Denial will not fix things. by Hurricane78 · · Score: 1

    Especially refusal to live in reality.

    As I previously said:
    Firefox does not need to do anything!
    Just bind to ffmpeg/ffdshow/CoreVideo. They all support H.264, and your responsibility is zero.
    You can still fall back to Theora, even if nobody will actually ever use it in the real world.

    There is no either/or here. There is not even a compromise. You can have all your wishes and dreamy ideals, and we can have H.264.
    The whole problem is made-up. And only kept alive trough continued denial and ignorance of what I just said.

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
    1. Re:Denial will not fix things. by gringer · · Score: 1

      Just bind to ffmpeg/ffdshow/CoreVideo. They all support H.264, and your responsibility is zero.

      And lose all the extra optimisation and swish features that are only possible for a decoder they have full control over.

      --
      Ask me about repetitive DNA
    2. Re:Denial will not fix things. by aristotle-dude · · Score: 1

      Just bind to ffmpeg/ffdshow/CoreVideo. They all support H.264, and your responsibility is zero.

      And lose all the extra optimisation and swish features that are only possible for a decoder they have full control over.

      Care factor zero. It is not supposed to be the responsibility of web browser developers to worry about sort of stuff for plugins so why would HTML 5 video be any different?

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    3. Re:Denial will not fix things. by bill_mcgonigle · · Score: 1

      Just bind to ffmpeg/ffdshow/CoreVideo. They all support H.264, and your responsibility is zero.

      Their legitimate complaint is fear of compromise through buggy plug-ins.

      But the solution is to sandbox the plug-ins, not restrict the plug-ins artificially. Oh, wait, that's hard with the 1990's application architecture Firefox is built on.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    4. Re:Denial will not fix things. by bill_mcgonigle · · Score: 1

      And lose all the extra optimisation and swish features [lca2010.org.nz] that are only possible for a decoder they have full control over.

      Somebody's going to open a Can of Knuth on this this thread.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  151. Re:Just give up your principles and compromize by slim · · Score: 1

    That's rather defeatist. It could happen. It would need to happen in stages. Each stage is a win in itself.

    1. It becomes common practice for sites to host both H.264 and Theora. (HTML5 lets you specify multiple video URLS. The browser will pick the one it prefers. You can do fallback-to-Flash in Javascript)

    2. Some sites start using Theora only. Either for ideological reasons, or because it's simply all they can afford. Their fallback is a message saying "sorry, please use Firefox, Opera, Chrome, etc."

    3. People start complaining to their vendors about this content they can't view -- "how come Firefox can do this and my browser can't?". Under commercial pressure, these vendors start to support Theora.

    If Firefox folds on this issue, then even step 1 won't happen. God bless 'em for having principles.

  152. Flash is free to generate. by goingToSay · · Score: 1

    Why do you exclude flash? The sdk is free and the player is free. Adobe makes some IDEs that are for sale but they are not required.

  153. Licensing doesn't prevent open sourcing by Anonymous Coward · · Score: 0

    You can buy a licence from MPEGLA for a using an opensource implementation of H264 such as ffmpeg or x264, entreprises do that already.

    The patents are public so there's no need to hide source code of implementations.

    1. Re:Licensing doesn't prevent open sourcing by aristotle-dude · · Score: 1

      You can buy a licence from MPEGLA for a using an opensource implementation of H264 such as ffmpeg or x264, entreprises do that already.

      The patents are public so there's no need to hide source code of implementations.

      Exactly. Also, binaries do not have to be gratis. There is no requirement for the developers to offer the binaries for free even under the GPL. If you don't want to pay, download the source and figure out how to build it yourself or pay a small amount of money (less than the price of a meal most likely) and contribute towards the support of your favourite software project while getting the convenience of a binary build.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    2. Re:Licensing doesn't prevent open sourcing by Skapare · · Score: 1

      At what price (for both decoding and encoding)?

      --
      now we need to go OSS in diesel cars
  154. Re:Mozilla doesn't need to pay a dime to support h by amRadioHed · · Score: 1

    Linux media players already have support for h.264.

    --
    We hope your rules and wisdom choke you / Now we are one in everlasting peace
  155. Power when given, not taken, is still power by jonaskoelker · · Score: 1

    Nobody forced anyone to adopt Microsoft Windows; it just happens that it did get adopted because it actually is a good operating system. There are alternatives of varying quality and success, and even if there weren't, nothing is stopping someone from designing one and marketing it.

    While not completely analogous, Microsoft isn't forcing anyone at gunpoint to buy or sell Windows. They're just using their market position to compel people to do so ("an offer you can't refuse").

    A lot of people have voluntarily chosen to get locked in, and have in this way granted a lot of power to an organization that might not have their interest as its top priority.

    MPEG-LA didn't take power, people just (stupidly?) gave them power. That doesn't change the fact that it now has a lot of power. And it wields it counter to our interests.

    I think that's what your parent was getting at.

  156. Re:Just give up your principles and compromize by DrXym · · Score: 1
    They can't do that as they explain in the blog entry a) that most windows users don't have an H264 codec and b) It's pissing on their principles (my words, not theirs). And I see their point. The Mozilla people want to be able to browse the internet with a completely free stack. That is their point: a completely free stack.

    A browser that supports a completely free stack has no need for plugins. Or add-ons that handle content that the browser doesn't. So let Mozilla put their principals where their mouth is and start by banning those things.

    What your suggestion is offering is a technical solution to the problem which unfortunately conflicts with their principle and thus they can't go down the road. I see Mozilla people's point and I agree with them. It's reasonable, logical and consistent. But I also understand there are a lot of people who read slashdot who just don't seem to understand what the point of freedom is.

    Their principle is already conflicted by things their browser supports. Many sites contain an embedded swf and Mozilla dutifully instantiates a proprietary component to play it. Hell, their browser will even HELP the user get Adobe Flash Player if it encounters sites that contain SWFs. It's hard to imagine how their principles could be compromised any more if they're taking some kind of stance on this particular point.

    Of course I realise why their principles take a backseat here. IMO it's simply pragmatic to support the proprietary stuff while pushing HTML standards which do away with them. But a video tag that only supports ogg really isn't much use at all. Sites aren't going to code against that tag when it doesn't support the INDUSTRY STANDARD codec. Some sites might use it but the majority will carry on using proprietary plugins by Adobe and Microsoft to play their content or advise users to use Google who do supply a browser which plays videos. Either way open standards and Mozilla lose.

    It simply makes no sense for Mozilla to take this stance. By all means ship with the ogg player. After all, the power of the default can be never be underestimated. But not allowing other codecs is flat out stupid and ultimately self defeating. Most modern operating systems either contain an h264 player, or can obtain them. In many parts of the world, it's even free and legal to use h264. Denying a popular industry standard video format and denying providing an API so that others can support it is cutting off the nose to spite the face.

  157. Re:HTML5 Video by master5o1 · · Score: 1

    So does this settle it for firefox on windows 7?

    --
    signature is pants
  158. Re:HTML5 Video by master5o1 · · Score: 1

    This is how it should be, at least for an OS that uses gstreamer.

    --
    signature is pants
  159. Re:HTML5 Video by SanityInAnarchy · · Score: 1

    It looks as though they're finally accepting this. Is that true?

    Yay for technical merit beating political bullshit, then! Next up: DirectShow on Windows and QuickTime on OS X? Please?

    --
    Don't thank God, thank a doctor!
  160. Re:HTML5 Video by master5o1 · · Score: 1

    I would have modded you funny, but I already posted abobe :|

    --
    signature is pants
  161. Re:HTML5 Video by master5o1 · · Score: 1

    *above.

    --
    signature is pants
  162. Re:HTML5 Video by aristotle-dude · · Score: 1

    Support in HD video cameras is irrelevant, unless you plan to post full resolution, un-edited videos from them.

    Name some mainstream consumer video editing packages that support Theora encoding. A large proportion of video content on the web is produced on the mac and Apple is one of the major supporters of the H.264 standard.

    Most people don't even know what software is out there that allows you to play back Theora let alone encode in that format.

    I think the open source community is wasting its time with this battle when they could be concentrating on developing their server service standards like Open Directory to compete with Active directory and develop a robust replacement for Exchange server. I'm all for open source "server" services and open standards for networks but I'm not a fanatic about open source being used everywhere and for everything.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  163. Out of the mirage and into the other mirage by SuperKendall · · Score: 1

    no one is under the illusion that ogg is a suitable replacement for h.264 in all cases. The hope is that a better codec than either will appear with more suitable licensing terms

    And the second thing you mention is not equally delusional as the first why exactly?

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Out of the mirage and into the other mirage by BZ · · Score: 1

      > And the second thing you mention is not equally delusional as the first why exactly?

      http://www.techcrunch.com/2009/08/05/google-acquires-video-compression-technology-company-on2-for-106-million/

  164. Why would you pay anything? Mozilla can. by SuperKendall · · Score: 1

    Lost in all this noise here is the reality that while Mozilla would have to pay on the order of $5million/year, they already make tens of millions per year being paid to have Google as the default search engine.

      So why not take some of that large amount of profit and roll it back into the browser being distributed? I'm sure they do already in terms of development R&D. The stance against h.264 is somewhat admirable from the standpoint of idealism, but not very practical for someone wanting to distribute a modern browser. If you never compromise you'll always end up stuck.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  165. What Flashblock's for... by argent · · Score: 1

    You're saying abnoxious advertising is a web usability problem?

    Yes, actually. Though that's by no means all of it. I mostly use Flashblock because nothing says "screw you" like a background window suddenly using 100% of my CPU.

    sites that use Flash for UI almost never provide a no-flash backup.

    That's why Flashblock shines. Instead of having 20 little applets busywaiting in the background, I get 20 little (>) icons that I can selectively enable, and leave the 3d flash navigation menu that's tracking my mouse pointer with a clippy-quality avatar blocked until such time as I need it.

    And, yes, even with the extra clicks, this gives me a far better user experience than without it.

  166. Two problems: by SanityInAnarchy · · Score: 1

    Problem #1: I don't know about everyone else, but I am in favor of Mozilla promoting an open, free, and sane video standard. I just wish they would do that while also giving their users choice by supporting proprietary codecs through mechanisms which have been set up specifically for this purpose.

    That is: I have no problem with Mozilla supporting Theora. I have no problem with them promoting it, or even providing a little notice on pages that use other codecs. I have a very big problem with them refusing to support anything else, even through plugins.

    Fortunately, that particular bit of insanity seems to have passed -- it looks as though Firefox will support GStreamer on Linux, so we'll get h.264 support if we want.

    Problem #2: I might Mozilla doing this if Theora was a stupidly-obvious choice. An example of a stupidly-obvious choice is PNG -- there is no rational reason to choose GIF instead of PNG for any still image. Another example is FLAC -- if you've got the space, and you're looking for a lossless format, FLAC is the obvious choice, and it's not going to be terribly painful for anyone to convert from, say, Apple Lossless to FLAC.

    But it's not. Theora is catching up, but is still measurably and visibly behind h.264 in every comparison I've seen, including comparisons done by Theora proponents and Theora developers. So far, it appears it would cost Google more than 5 million in extra storage space and bandwidth to store Theora files instead of h.264 files -- and that's ignoring the additional cost of transcoding all these videos again, adding a generational loss to the ones people managed to upload in a format YouTube didn't feel the need to transcode at all.

    And the only thing standing in the way of h.264 being an open standard is legal issues. That means this is all going to be moot in, what, 10 years? 15 at the most. Technologically, we understand it, we have many free software implementations of it, and it's already an open standard anywhere software patents aren't enforced.

    These problems aren't addressed by your simple explanation -- perhaps I should call it a simplistic explanation. If you can make Theora (or Dirac) better than h.264 in every way, then I will support it, I'll participate in letter-writing campaigns to YouTube, and so on. But as it stands, you're letting the lawyers force you into adopting worse technology, and you're taking one of the icons of user freedom, Firefox, and severely limiting users' freedom in that way. That's where we have a problem.

    --
    Don't thank God, thank a doctor!
  167. Re:HTML5 Video by aristotle-dude · · Score: 2, Interesting

    It's mostly just problem for Mozilla

    And every site that wants to host their own video content. H.264 also requires a license for hosting content. All those sites will probably stick to Flash if other browsers don't support Theora.

    Do you work for a living or do you just live of student grants? In the real world, things cost money and companies need to find a way to recoup their investment in developing things in H264. Not every company can live off donations and selling t-shirts or donations from other companies which are "for profit".

    If if was not for there being some of those "evil" closed source companies, most open source projects would have never seen the light of day because they would not have had enough resources. Servers and bandwidth are not free.

    Open source software should not be "free" to download for people who have not contributed considerable code to the project. I think there should be the option to pay for a license to use the binary, the option to contribute sweat equity to the project in exchange for a binary download and just give the non-paying public a link to the source and let them build the binary themselves.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  168. Re:HTML5 Video by spire3661 · · Score: 1

    Not only that Apple has the fucking gall to want you to buy their product if you want to get fullscreen. Not to mention it likes to take over ALL video. I finally gave up after years of installing and uninstalling it and now i just do without quicklime. Its jsut not worth it to see a trailer or something. I hate fucking quicktime and their bullshit decisions instead of just being a decent media player.

    --
    Good-bye
  169. Re:HTML5 Video by spire3661 · · Score: 1

    Never attribute to malice that which is adequately explained by stupidity

    --
    Good-bye
  170. You don't get it by jonaskoelker · · Score: 1

    Why can't Mozilla just implement a plugin framework, and leave it up to the user to decide whether he wants to install the h264 plugin

    No, no, you don't get it: that would be smart, and convenient, and uhh...

    Oh wait. Well, I recall a link to a blog post by some firefox dude a few days ago (sorry I'm being so specific ^_^) who said that this has been suggested, and that it would be problematic: if there's a security issue (or some other issue) in the third party code, then firefox can't fix it.

    It doesn't make any sense to me: sooner or later, firefox is going to make a system call. If the Windows API is broken, will firefox (the mozilla foundation) fix Windows? Will they fix libgtk? Or the OS X TCP/IP stack? Why is the video codec different? And by not shipping a video codec, they force us to use flash on (e.g.) youtube. Where are all the Mozilla foundation fixes to flash?

    But there's the argument: The Mozilla foundation can't fix third party code, so it (selectively) won't rely on it.

  171. Freeing slaves punished those who followed the law by Anonymous Coward · · Score: 0

    Freeing slaves punished those who followed the law: the law that allowed you to keep slaves.

  172. just wait and see... by AlgorithMan · · Score: 1

    Do you really think google will just ignore it when youtube's webhits nosedive by 36% and their advertising partners leave en masse?
    If 36% of all internet users and especially the pros can't see your html 5 videos, then html 5 is done for.
    just wait for html 5's demise and ogg/theora in html 6...
    Mozilla is to powerful in the browsermarket for any website to not support them!

    --
    The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
    1. Re:just wait and see... by shutdown+-p+now · · Score: 1

      Do you really think google will just ignore it when youtube's webhits nosedive by 36% and their advertising partners leave en masse?
      If 36% of all internet users and especially the pros can't see your html 5 videos, then html 5 is done for.

      Do you really think Google will just ignore it when YouTube's hits nosedive by 65%?

      Yeah, I think they won't, too. Which is why they will keep offering Flash version (likely with browser detection) for several more years, at least. And if Firefox won't support H.264, then it'll just be redirected to that version, same as IE.

      Which, for vast majority of users out there, is good enough. It'll still play with the same quality (after all, Flash itself will play the very same H.264 stream).

  173. Like flash? by Anonymous Coward · · Score: 0

    You mean like flash lets people use any installed codec? Oh wait. No flash forces you to use its internal H.264, H.263, or VP6. Or like IE lets you use any system codec? Oh wait, no it doesn't. You must mean like silverlight? No, even silverlight forces to use the built in codecs. Of course there is Chrome... BUT EVEN CHROME ONLY USES ITS OWN INTERNAL CODECS. Safari on mac actually does use system codecs, though apple severely constrains the functionality (for example, MOV with embedded hyperlinks don't play).

    Ever think there might be a reason for this? System codecs are notoriously insecure. This is acceptable when they aren't going to be exposed to a highly hostile environment, but being embedded in a widely used browser or plugin is a very hostile environment, so no one does it. Except for apple, and thats mostly because they can get away with being security stupid because no one bothers attacking their platform.

    Moreover, it's been possible to embed videos using the object tag since the mid 90s on any system dumb enough to expose the system codecs, and yet no one does video this way: The reason is because you can't expect it to work. You can't trust that the user will have any particular codec, or even one codec out of a small finite set (e.g. Theora or H.264). Virtually all video hosting sites create a couple renditions for different player CPU levels, screen sizes, and bandwidths so supporting two formats is bad but not a killer, but having to support two dozen formats just to get something to play is a total non-starter.

    TLDR: System codecs = insecure; unpredictable; inconsistently available; shifts the openness problem onto someone else They are a problem, not a solution.

     

  174. Re:HTML5 Video by Wildfire+Darkstar · · Score: 1

    mozilla doesn't like being linked from slashdot.

    thats quite interesting. why not?

    Slashdot effect.

    --
    Sean Daugherty "I have walked in Eternity -- and Eternity weeps."
  175. Nope, continue panicing by Wesley+Felter · · Score: 1

    Mozilla is going to implement gstreamer backend for html5 video element.

    That's only for Fennec; roc is dead set against enabling GStreamer for desktop Firefox.

    1. Re:Nope, continue panicing by shutdown+-p+now · · Score: 1

      That's only for Fennec; roc is dead set against enabling GStreamer for desktop Firefox.

      Is that for the same ideological reasons? I.e. "we want to push for open standards"?

    2. Re:Nope, continue panicing by Wesley+Felter · · Score: 1

      Yep. They won't implement proprietary codecs and they won't let you sneak in proprietary codecs through GStreamer either.

    3. Re:Nope, continue panicing by shutdown+-p+now · · Score: 1

      Too bad. Choosing pure idealism over a healthy dose of pragmatism, in the long term, will land up Firefox in about the same position that Linux on the desktop enjoys today.

      If they keep going that way, I guess that Firefox will become the "GNU/Browser" eventually - the kind of thing used by free software purists, recommended by Stallman etc, the gNewSense of Linux distros - while the likes of (still open-sourced) Chrome will come to dominate the market, and ship as a default browser in Ubuntu.

  176. Hack some JS to replace the video by paxcoder · · Score: 1

    Someone should make a greasemonkey script that replaces the H.blah thing with mpeg or flv - whichever Firefox supports. The tricky thing would be to fake browser title (Safari or Chrome) only on youtube sites - since Youtube doesn't really give you the video tag on other things as far as I can see. Faking is possible to change in about:, so maybe someone already wrote an extension to do that on the fly (would need to be modified to do it automatically on *youtube.com* sites), so some sort of mix should be made - I don't really know the limitations of either - perhaps you can do it both in just greasemonkey.
    Alternatively (and until then), you can use this script: http://userscripts.org/scripts/show/50771 (it's free software)

    1. Re:Hack some JS to replace the video by shutdown+-p+now · · Score: 1

      Someone should make a greasemonkey script that replaces the H.blah thing with mpeg or flv - whichever Firefox supports.

      Er... are you actually suggesting to write a realtime H.264 decoder, and a realtime Theora encoder, in JavaScript?

      Or did I misunderstand your suggestion?

    2. Re:Hack some JS to replace the video by paxcoder · · Score: 1

      You misunderstood it. Take a look at the link. The script replaces the flash player with the traditional pre-HTML5 embedded video (you need a totem or a vlc plug-in). It plays flv, has several "quality" options to chose from. I'm guessing not all of those files are encoded with H.blah (although tbh, i'm not sure), so if you get a video tag with H.blah (if you lie you're Safari), you could use greasemonkey (javascript) to replace the video tag src property with another (non-H.blah) URI.

    3. Re:Hack some JS to replace the video by horza · · Score: 1

      There are already firefox plugins that rip the video stream from YouTube etc, shouldn't be too hard to transcode to Theora via cli and serve it up. You could also run a proxy server to do the same think. However this would be counter-productive and it reduces the incentive for producers to support Theora. Much like Wine doesn't encourage producers to write games native for Linux.

      Phillip.

  177. Do you have any idea at all of how much money? by Anonymous Coward · · Score: 1, Informative

    Do you even realize how steep the licensing fees are for MPEG?

    Chris Blizzard was on record a while ago saying that if Mozilla wanted to ship mp3 support in FF, the licensing fees would be somewhere over $500,000 *a day*. h.264 is considerably more expensive. Millions a day. Mozilla would be broke in under a week.

    The MPEG-LA had a little slideshow not long ago talking about how successful it's been. One of the slides said proudly, I kid you not, that in 2008, MPEG-LA took in $66.46 of royalty fees for every man, woman and child ON THE PLANET for MPEG-2 ALONE.

    Oh yeah huurr hurr its all about greasy hippies and freedom. No, its about COLD HARD CASH.

  178. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Quicktime and Acrobat are the evil twins of PC software, developed from the outdated perspective that software licensors have a more valid claim on your hardware than you do. My OS no longer ignores desktop input while completing unrequested mandates from Apple or Adobe. Search 'remove acrobat plugins' for an indicator of the general feel out there. Like you I dropped them both.

  179. Re:Most vs. All by The+End+Of+Days · · Score: 1

    Holy shit dude that was fucking hilarious.

  180. Re:HTML5 Video by shutdown+-p+now · · Score: 1

    Opera has been releasing 10.50 "pre-alpha" versions for the last few weeks, with one major feature being <video>. It supports Theora, but not H.264. Actually, it uses GStreamer, so third-party H.264 support is quite feasible on platforms where the latter is first-class (Linux, BSDs etc) - it will just support anything your distro offers.

    On Windows they use their own minimal port of GStreamer which only supports Theora for video; that said, GStreamer is still open source, and so is this thing, so it can be theoretically hacked to add H.264 as well. Nonetheless, this isn't exactly "out of the box".

    As it stands, only Safari and Chrome stand by H.264.

  181. Re:HTML5 Video by shutdown+-p+now · · Score: 1

    They don't even need to implement a plugin framework. They just need to use the one that OS provides already - DirectShow on Windows, GStreamer on Linux, QuickTime (the framework, not the codec) on OS X, and so on.

  182. Challenge: Build a better codec fast by Anonymous Coward · · Score: 0

    The challenge is to build a better codec fast. A better codec that is covered under the GNU GPL would stop H.264 in its tracks. Until then, we have H.264. I know Apple has turned into the new Microsoft, so they want to push lock in and proprietary formats and the HTML5 tag doesn't specify a codec, so Ogg Theorea or H.264 could both be used, but Apple whined they like H.264 (they created it). It screws everyone else though, and makes Firefox users disgruntled. I think its time to kill proprietary video and audio codecs on the internet. If you want to poison your own users, then fine. The internet is a public forum. Proprietary has no place here.

  183. Its not about ideology by Billly+Gates · · Score: 1

    I think many slashdotters have a knee jerk reaction to those promoting freedom due to RMS being a little extreme.

    I just want to get something to work hassle free. To me supporting H.264 is about using $$$$ tools like adobe flash to create sites and use internet applications. Html is supposed to be as open as you can get. I do not care if people are greedy and yes supporting this will be the death of firefox and ultimately the internet. Lawyers from other companies will then demand payments for things like displaying the letter A with a font and using a network, and a whole bunch of endless redicious fees.

    Then firefox will receede and IE will take over and html 5 development will mean expensive proprietary tools that only work on windows, etc.

    Yes I willl use proprietary products if it gets the job done. However the internet is the only free thing left and I do not want a return to AOL, MSN, in the1990's where creativity was discouraged and $$$ ruled the day on who gets to develop software.

    With html5 and free software codecs we can use our own tools and encourage innovation.
    The net is free now but that is endangered. The lack of IPv4 addresses by domain squatters, h.264, and flash are creating problems.

     

  184. Obligatory ... by Anonymous Coward · · Score: 0

    What about DIRAC????

  185. Re:HTML5 Video by arose · · Score: 1

    Name some mainstream consumer video editing packages that support Theora encoding. A large proportion of video content on the web is produced on the mac and Apple is one of the major supporters of the H.264 standard.

    You are changing the subject (cameras vs editors). But anyway.

    1. You found a chicken and egg problem with a proposed standard, congrats.
    2. Editors are software, easily patch-able if there is demand.
    3. Editors can output uncompressed and/or MJPEG which can be used by a dedicated encoder. It's possible to do Theora now, no question about it.

    Most people don't even know what software is out there that allows you to play back Theora let alone encode in that format.

    Most people don't know about any of it for H.264 either, or for JPEGs or PNGs for that matter. They just go to a site with Firefox or Chrome and Theora video "just works". As far as encoding is concerned, anyone who knows enough to write HTML5 should be able to google for it. It's not obscure enough that there is no info out there, just that many people haven't heard about it.

    In short, the tools will come, and rather quickly if anyone wants them, the groundwork has been laid, the user friendly front ends are not that big of a deal.

    I think the open source community is wasting its time with this battle when they could be concentrating on developing their server service standards like Open Directory to compete with Active directory and develop a robust replacement for Exchange server.

    I think that, unless you expect Firefox developrs to just randomly drop developing a browser and start on random server side projects, you are off topic there.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  186. Re:HTML5 Video by LO0G · · Score: 1

    I don't know - I suspect that the firefox team wants to support all platforms equally which would be a problem.

  187. Re:HTML5 Video by Amorya · · Score: 1

    They dropped the pay-for-fullscreen thing a few years back.

  188. whoa by zogger · · Score: 1

    Yo man, don't shoot the messenger here. I am just reminding about this new ACTA. I am not disputing the present or the past, they are what they are, just talking about the near future. They are going to be serious about it once that passes. that's the whole idea, and they got the juice to do it. You may not recognize it as a big deal yet, shoot, hardly anyone does, but it is there and eventually will be put into force. DeCss and so on, is exactly what I have been saying, they *haven't* been serious about enforcement, nor much for downloading copyrighted content. It's been joke level enforcement so far. This previous **AA "enforcement", for example, is just them getting warmed up and developing their tech to pull this off better. They will keep changing it around until they get something that works on a mass scale. so far, when they have started sending out the threatening letters for getting people to be bounced from the net connection, that has been working better than threats of cash lawsuits. After that will come blacklists, and no more net connections for people anyplace. All of this is set to change fast once they have even more legal precedent that will be in the form of this international treaty/agreement. A lot of these repositories and so on with "infringing" warez to make your box functional with various media will find it hard to find anyplace that will host them outside of the control of the RBN. The wild wild west days of the net are rapidly closing, the suits are going to want their money and way more control of the net, or else.

    1. Re:whoa by SanityInAnarchy · · Score: 1

      DeCss and so on, is exactly what I have been saying, they *haven't* been serious about enforcement,

      And I'm saying the reasons for that have more to do with the target they're after. Consider -- if they actually manage to make me remove DeCSS from my computer, that's all the more reason for me to use BitTorrent. And torrents are something they've tried to crack down on -- key word, tried.

      This previous **AA "enforcement", for example, is just them getting warmed up and developing their tech to pull this off better.

      And how do you know this? Never ascribe to malice...

      They will keep changing it around until they get something that works on a mass scale.

      Which they won't, because it isn't possible.

      After that will come blacklists, and no more net connections for people anyplace.

      Given the popularity of open wireless, this seems incredibly unlikely.

      A lot of these repositories and so on with "infringing" warez to make your box functional with various media will find it hard to find anyplace that will host them outside of the control of the RBN.

      Not terribly. Freenet exists, and so does Sealand, among others.

      The wild wild west days of the net are rapidly closing,

      People keep saying this, and I keep not seeing it.

      the suits are going to want their money and way more control of the net, or else.

      Or else what? I mean, I want a pony, but...

      --
      Don't thank God, thank a doctor!
    2. Re:whoa by zogger · · Score: 1

      Well. we will have to see, this is speculation after all. Freenet and sealand and tor and so forth type efforts..they could shut them down if they felt like it, at the major nodes. As it is now, I bet they leave them up just to monitor traffic. Heck, half of those entry and exit points are probably cops anyway...

      Open wireless, make it a serious crime if someone does naughty things on your open wireless, people will start restricting them more and require verified logins. For example, my local library has wireless, but you must have a library card to access it, and you must show ID to get such a card. Businesses that currently run those things, like coffee shops and so on, will have their lawyers tell them to lock it down more. and most of them have security cams now, even if they don't require any ID to access, could be if later on they wanted to narrow it down, they could just correlate interesting traffic with the cam feed/storage, work from there.

      In other words, it isn't as technically difficult as it seems, it is just in the past and even now they haven't really done it. That is what I think will change after ACTA is passed. They know or have a good idea what is what, look at that slashdot story now about shutting down people who got zombiefied (good idea there actually, at least slow them down and give them notice to get their computer dipped in disinfectant). Just about as much effort as it would take to notice who is doing what else they might want to look at or restrict. Deep packet and so on. Private VPNs..court order, one end or the other, or they could run a cutout and offer that service themselves, just for fishing expeditions. They already do that with drugs sales stings and prositution sales stings and official secrets stings., sop plenty of legal precedent there. "terrorism" "security" "economic protection against the evil haxorz" whatever, they will have some excuse or excuse.

      All of that type stuff. You could easily see canonical and a lot of other linux distros not linking at all to things like DeCSS, or half the stuff that goes with mplayer, and mplayer itself have to go basically underground/dark net under a "making available" statute. Stuff like that.

      I think for real world examples, in the face of opposition, perhaps look at how china keeps evolving their net access and content access restrictions, working hand in glove with the top networking manufacturers. Sure it can be circumvented, but it gets harder all the time for the people there to do so, and it will cross a point where joe or wong sixpack simply will not have any skills to defeat that, which joe or wong sixpack being 99.999% of the traffic.

      The bottom line is *their* bottom line as regards how much tech and effort they will throw at this, and we don't know yet, because they are still working on that ACTA at the higherest international level. They have made no bones about enforcing "IP" in the strictest sense because that is what they want to use to replace manufacturing type jobs/serious income with in the west. This is potentially hugemongous gobs of money and interest now, so we have to extrpolate based on past similar interests how much effort and tech they will throw at this then. My guess is, "a lot". Not very scientific, but they will certainly be throwing a lot more than what they are doing now, else, what is the point of ACTA in the first place? They wouldn't even be fooling around with it.

      So, we can agree to disagree, you think it won't be much different from today, I think it will shoot up and get a lot harder to be "casual" with IP issues, with a lot more busts, and a lot more media coverage and people getting scared when they start getting nasty gram warnings from their ISP. That isn't happening right now very much, but if and when, etc..

    3. Re:whoa by SanityInAnarchy · · Score: 1

      Freenet and sealand and tor and so forth type efforts..they could shut them down if they felt like it, at the major nodes.

      All except Freenet. I don't need a major Freenet node to connect, I just need any Freenet node. The only way they could shut Freenet down is by blocking all but approved traffic, thus simultaneously shutting out innovation on the Internet, and still not blocking Freenet, which would then move to steganography.

      Open wireless, make it a serious crime if someone does naughty things on your open wireless, people will start restricting them more and require verified logins.

      Public pushback would be fairly high on this. I mean, I've suggested this before for other reasons, but unfortunately, trying to hold people responsible for what their machines do is not reasonable to attempt in a democracy, because you'd have the vast majority of the population vote you out of office immediately.

      And I do wish that were otherwise, because it'd eliminate most of the spam, etc.

      For example, my local library has wireless, but you must have a library card to access it, and you must show ID to get such a card.

      Do they actually install software on your machine? If so, you could probably petition for that to be changed, as they are likely requiring specific OSes. If not, it can likely be trivially circumvented with MAC spoofing -- perhaps you'll need a card at first (and perhaps not), but you'll be able to easily impersonate another patron.

      most of them have security cams now, even if they don't require any ID to access, could be if later on they wanted to narrow it down, they could just correlate interesting traffic with the cam feed/storage...

      Leave an iPod Touch or something similar hidden in the vicinity. It can act as a repeater to you somewhere out of range, or it can be a relay point to somewhere else.

      Just about as much effort as it would take to notice who is doing what else they might want to look at or restrict. Deep packet and so on.

      About as effective as it currently is at blocking BitTorrent. It takes much less effort to deal with zombies, which are by definition doing something obvious to someone else -- making SMTP connections, or DOS-ing a particular address, or connecting to a given command-and-control center -- than it does to deal with peers who only need to connect to each other, with both ends of the connection deliberately trying to hide themselves.

      You could easily see canonical and a lot of other linux distros not linking at all to things like DeCSS, or half the stuff that goes with mplayer,

      I don't know if Ubuntu does now. I do know there's a third-party project called Medibuntu which provides them from outside the US.

      I think for real world examples, in the face of opposition, perhaps look at how china keeps evolving their net access and content access restrictions, working hand in glove with the top networking manufacturers.

      Even there, they haven't been entirely successful. You're right in that I wouldn't want to live in China, the way it is now, but I don't think it can be entirely successful, and I do agree with the collateral damage. What I'm hoping is that the harder they push, the more obvious that damage becomes.

      Sure it can be circumvented, but it gets harder all the time for the people there to do so,

      Not particularly. From what I understand, it hasn't actually changed very much qualitatively. All that changes is that China blacklists more and more pages, meaning it continues to be difficult to find a proxy.

      So, we can agree to disagree, you think it won't be much different from today, I think it will shoot up and get a lot harder to be "casual" with IP issues, with a lot more busts, and a lot more media coverage and people gettin

      --
      Don't thank God, thank a doctor!
  189. MPEG-LA's balls are in a vice by Anonymous Coward · · Score: 1, Interesting

    So US law is very slanted against patent pools, they are viewed as anti-trust law violations by default and can pretty much only exist with the permission of the FTC. MPEG-LA has come under fire several times regarding anti-trust law.

    Part of the criteria required for a patent pool to be lawful is that it must be offered under RAND terms-- the licenses must be available to absolutely everyone at exactly the same price. No special deals, no incentive freebies, etc. Break that and the principles of mpeg-la are looking at time in federal prisons, the law here is pretty serious.

    They are currently playing somewhat fast and loose with the intention of the law, if not the expressed language of it: They are wilfully blind to most beneficial infringement, x264 is breaking the law like WOAH, but since they make the best encoder by far MPEG-LA looks the other way. It's not at all clear that the failure to enforce in these cases is at all lawful in the context of anti-trust law, so no one is going to formalize that kind of deal, and Mozilla can't afford to depend on the hope that MPEG-LA won't enforce like VLC, ffmpeg, and x264 can. They also violate the intent of the law in that the patent holders themselves cross-license with each other without paying into the pool, and the annual rate cap is highly discriminatory-- though discriminates via proxy rather than by name.

    Government regulators respond slowly, but I expect there will be some amazing fireworks once the FTC does wake up.

  190. Re:Just give up your principles and compromize by Billly+Gates · · Score: 1

    Its not ideology at all in my opinion. Mozilla lawyers simply stated, do not include H.264 because its legally owned by someone else.

    I do not like this situation either and think its ridiculous. The mozilla foundation has a legal responsibility to protect its assets against frivolous lawsuits.

     

  191. The myth of US software development. by upuv · · Score: 1

    Speaking as someone that has lived all over the world and done extensive amounts of work in the US in Software.

    First off. Every Country/Region needs to understand that if they make the conditions unfavorable for mid-long term business operations for software development the software shop will move. ( The whole concept of outsourcing ).

    For quite a long time now we have seen the migration of LARGE data centers to cost effective, dependable locations. Data centers have different criteria than a software shop but they show us an interesting parallel to software development. Chicago used to be one of the data centers capitals of the world. It's not exactly known for that now. Why? Unfriendly local taxation, cost of power, reliability of power, migrating network backbones away from region. What I'm saying is data centers moved away from Chicago because the conditions became unfavorable.

    Software development is even more vulnerable. In the last 24 months I have had contract development done in Vietnam, Brazil, Sri Lanka, India, France and NONE in the United states. All because of factors like. Cost, Time to Market availability of resource etc.

    Other factors do have impact. In the example above kernels. The issue here is the concentration of specialized developer staff. Is a major factor. For several years San Fran was the "only" place to set up a software shop of any kind. Not so any more. Why? Partly the specialized skill spread out.

    Several of the driving factors for migration away from the US are. Cost of staff, Cost of facilities, Cost of power, legal over head, governmental regulatory encumbrance. ( Basically all of them are money )

    Do not for one second believe that what you see on the ground now for jobs and company shops in the US will remain so in 2-5-10 years time. Taxation in the United states will most likely climb. Taxes go up expensive jobs will flee. I have seen dramatic shifts in the IT world over the decades, boom bust, migration and dispersal. A lot of local changes had to do with government and taxation.

    A common joke around my office circle is. "How do you make a project over run and never deliver? Get an IBM project manager from the States on the job." It may or may not be true. But it does reflect the sentiment that is out there. Basically the rest of the world does not look to the United States first for development.

    So you the future leaders of the US software industry. You need to really pull your finger out of that dark hole it's in and start doing something to improve the reputation, the viability, the cost of software development in the United States. Cause if you don't wave good buy to another white collar high paying industry. As someone else said. The US made this mess and now the US needs to dig them selves out of it. This statement is also true for other locations on the planet as well. India for example is facing a very nasty fall in the software industry if conditions don't improve for companies.

  192. It's motherfucking Google. by DrYak · · Score: 2, Insightful

    They'd have to go back and reencode the entire YouTube library if they wanted to offer it in Theora.

    We're speaking about Google.
    MOTHER. FUCKING. GOOGLE.
    If anyone on the web has the processing power and storage space to reencode the whole Youtube library on a whim, it's them.

    And if they are really that short on storage space, they could kick out some of the older format stored in the library.
    Each video isn't just stored as H-264, but as a whole set of different formats - for backward compatibility (I seem to have read somewhere that there are even Flash 7 compatible encodes).
    Google could drop one of the older format (say, Sorenson, for example) and use the freed space and processing power to do Ogg/Theora encodes instead.

    As Theora is less complex, it wouldn't probably require as much processing resources as H.264 anyway. (In fact it's somewhat the same generation of technologies as the Sorenson codec, for example).
    As Youtube and the like mostly contain crappy quality clips taken with camera-phone, the fact that Theora is less complex won't impact that much the quality (well at the beginning Youtube used much poorer quality codecs and still did well - the move to h.264 is an overkill quality-wise).

    (The h.264 vs Theora quality will only start to matter for websites streaming HD TV and HD commercial movies)

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:It's motherfucking Google. by hazydave · · Score: 1

      It has very little to do with storage or CPU. Yeah, Google could re-encode the whole YouTube library, probably in a short time, and pretty cheap. It would drop in quality, transcoding from the H.264. And don't discount H.264 on YouTube... phone-cam stuff isn't encoded at high bitrates. You only get HD options on YouTube from HD sources.... I have several of these up ("hazydave" channel), from full HD sources. They wouldn't look good on my 71" DLP, but for Web Video... doesn't suck. YouTube serves up "HD" at 2Mb/s, always cut to 720p if you don't downrez yourself (they actually accept 1080i/p uploads, but don't save them). Then again, the phone-cam on my phone produces better quality video that what you get from many consumer camcorders (Motorola DROID... it's just ok, but there are plenty of consumer SD camcorders with tiny 1/8" sensors and not even full DV quality resolution).

      It's quality and bandwidth that makes Ogg Theora a problem right now. You need more bits for the same quality from an original source, plain and simple -- Theora is not as good as H.264. Google may be mighty, but they do pay for bandwidth. Lots. That's why YouTube is still losing money. Going to Theora would cost more in bandwidth than they would save not paying the H.264 licenses. Also not a good thing for the internet in general, considering how much volume of global traffic is video these days.

      Google may well be going in yet-another-direction. They did just buy On2, the guys who did the work behind VP3, which begat Theora. And VP6, which was the original video CODEC in Flash video. And VP7 and VP8. The On2 people claim VP8 is 40% more efficient (eg, bits at the same perceived quality) than H.264 for low bitrate video. If that's true, Google could save themselves hundreds of millions a year by re-encoding to VP8.

      That would be interesting. Even more interesting would be if Google open sourced VP8, assuming it's clear of any MPEG-LA or Microsoft or other video compression patents. Eliminating H.264 advantages of quality and bitrate means real money to any of these buy guys, and you don't have to beat H.264 on HDTV to beat it streaming at a megabit or two.

      I would have liked a "must carry" CODEC or two as part of the VIDEO standard, that's no big deal. What is a big deal is Mozilla saying, no, we're not going to support H.264, but we're also not going to support any of your system CODECs already. Which means you won't get any video CODEC they don't decide to compile in themselves (well, you could build your own). That's kind of evil... I have been playing around with Dirac, which would be a reasonable web format as well, and, well... there are plenty of other browsers. It's a shame that, having built back at least a reasonable chunk of the former Netscape glory, Mozilla would fall on their sword this way.

      Of course, Microsoft is so asleep at the wheel, they haven't even committed to HTML5 or the tag. And they're still around 50%. I guess they think they can get SOMEONE to run Silverlight...

      --
      -Dave Haynie
  193. Re:HTML5 Video by rdnetto · · Score: 1

    So in other words, it can be done, but Mozilla refuses to do so. Given how big of a deal HTML5 is getting to be, I wouldn't be surprised if someone forks Firefox over this.

    --
    Most human behaviour can be explained in terms of identity.
  194. you're logically contradicting yourself by circletimessquare · · Score: 1

    how do free installs somehow compel other people to buy?

    free installs compel more free installs

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  195. The default install by tepples · · Score: 1

    But does the default install of Ubuntu have any "don't install this software if you're not sure it's legal to do so" software?

  196. Non-standard by tepples · · Score: 1

    Ian Hickson, as it happens, is violently against anything even slightly non-standard, and you can bet he would love to see H.264 die.

    H.264 is a standard published by an international standards body (ISO/IEC 14496-10 - MPEG-4 Part 10, Advanced Video Coding). Theora is not.

  197. Theora outperforms Dirac at 500 kbps by tepples · · Score: 1

    Why does everyone seem to forget about Dirac?

    The article states that Theora outperforms Dirac "at typical Web bit rates" such as 500 kbps.

  198. hmmmmm... by Anonymous Coward · · Score: 0

    The main point as i understand, is that MPEG-LA can start after 2010 to force users to pay for the content they view. Until now, the viewer are free of payments, but this can change. At least on US territories and any territory where software patents apply (i can think JP/US/Some countries @Europe). I don't think is a thing of "we buy the software" anymore, but the thing can become a "Pay per View", so you want to see some video encoded with H.264, then you (as user) pay MPEG-LA or their licensors let's say, US 0.99 per video... It will be be not the end of youtube or similars, but the end of free videos using H.264. Of course there's a chance that MPEG-LA just say the viewer are excempt of payment, but... why allow this??

    That's why an open standard should be supported... is not that it will replacing a commercial standard anyway... If you want to support a commercial standard, then pay for it.. a plugin??... well why not... if the os has included facilities, then you pay for this when you buy the OS (windows/osx). If you use linux, then you are out of luck or be illegal and live with it... (not much of a difference with a informatic pirate anyway, but laws changes from country to country anyway).

  199. Citation Provided by CritterNYC · · Score: 1

    Here's a quote about it from Mike Shaver, VP of Engineering at Mozilla:
    http://www.osnews.com/story/22787/Mozilla_Explains_Why_it_Doesn_t_License_h264

    The licensing fees for H.264 are well-known and widely published. The current cap is $5,000,000 per year (which Mozilla easily hits considering their userbase). The cap is going up again next year. Previous raises were an additional $750,000 per year, but you never know what it's going to be. There's no contractual limit on how much they raise the cap, only a promise of how much they raise the per-unit fees which doesn't affect Mozilla (they have so many units, they'll always hit the cap).

  200. Re:Ideology meet reality that's why FSF will win by Anonymous Coward · · Score: 0

    Considering the progress of GPL software for the past 26 years I would say they are doing a damn fine job of promoting positive progress.

    Do you think the Googlers didn't expect this response from the Mozilla foundation? If Mozilla stick to their guns, Chrome will swallow Firefox whole... end of story.

  201. Re:HTML5 Video by Lars+T. · · Score: 1

    They are. H.264 is not open enough to be shipped with a FLOSS product that is playing strictly by the rules. The question is why Apple and Microsoft are not supporting open standards, because Theora support is in Chrome and pre-release versions of Opera.

    Because better the devil you know. They know there's not going to be any more people asking for extra fees for H.264 - Theora simply isn't deep enough in the water for the subs to prepare their torpedos.

    --

    Lars T.

    To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

  202. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  203. Video tag was botched by LostMyBeaver · · Score: 1

    Fact is, if the web site has the ability to choose the CODEC, then they should have a means of providing the CODEC. An architecture via DOM, EcmaScript, WebGL and an audio object should have been designed so that CODECs could be distributed to the web browser as byte code that can be compiled optimized for the platform.

    Sure, initially it would be slow, but now that pretty much all EcmaScript implementations compile to native, it would make sense to push the limits and force the ability to produce vectorized code as well. There's simply no reason that EcmaScript couldn't be used for implementing CODECs. WebGL provides video textures which can be used for pushing the media to. Additionally, GLSL might be able to be used for GPU accelerated Video CODECs.

    As far as I can see, the only thing missing is a method of outputting audio data from EcmaScript as a stream.

  204. Re:Just give up your principles and compromize by Pentium100 · · Score: 1

    a) that most windows users don't have an H264 codec

    Great, because some people do not have the codec I will have to continue to use flash on Youtube. Maybe I could download some plugin that allowed me to watch h264 videos because I have the codec. Maybe I should tell everybody how easy it is to download HD TV shows using torrents. Then more people will have the codec.

    b) It's pissing on their principles (my words, not theirs)

    Too bad.

    But I also understand there are a lot of people who read slashdot who just don't seem to understand what the point of freedom is.

    Well, I admit I don't. I always though that freedom meant that I could do whatever I wanted (within reason of course). That should include being able to watch h264 videos on Firefox.

    So suppose you're in the following scenario: you get to recieve a pile of money in exchange for a corporation to cut off your right leg

    Depends n the amount of money. If the amount of money is enough to build a fully functional artificial leg and then there would still be enough for me to never have to work again I'd probably do it.

    What if it was only a few toes say of one of your siblings, or a living parent, or one of your children if you have any?

    I'd ask the person h(im|er)self.

    From my perspective, you have no principles except possibly the pursuit of money which as a goal I just don't see much point

    So, you would refuse to sell your leg for any amount of money. You continue to live and work as usual and can be proud and tell everybody "Well, you see, I was offered $XYZ, but I refused, I still have my leg and can continue to enjoy living in fear of losing my job", well, until you get in an accident in which you lose that leg anyway (or maybe you don't).

    From where I see it, this decision by Mozilla actually is infringing on my freedom. I want to be able to watch videos in sites that use h.264 codec. Almost everything else uses that codec (anime, HD TV shows, youtube) and a lot of devices support it (PCs, bluray players, my cell phone). So why use the codec that is only supported on PCs and is inferior in quality? OK, you like the codec because of legal reasons, I understand that Mozilla cannot distribute h.264 codec for free etc. OK. So make it possible to write a plugin with that codec.

    Or even better, use the codecs that are in the PC already. Ir that particular user does not have h264 codec, the site can guide him to download it or if he can't it certainly won't be worse than it is now, where I can't play the videos even if my PC has the codec.

    Going back to your analogy about cutting off a leg. If you respect freedom, than you have to respect my choice to sell my leg (or my kidney, or some of my blood), otherwise your idea of freedom becomes something like "Do whatever you want as long as I approve it". And this is why I can't understand the laws that prohibit the sale of non vital organs. If I can't sell it, you aren't getting it for free either.

  205. MOD PARENT UP by cyclomedia · · Score: 1

    It is not firefox's job to decide what video content i can and cannot watch. If the site serves the video and i have installed (legally, illegally or outside of juristiction) the required codec to render it then the video should play. 'nuff said.

    --
    If you don't risk failure you don't risk success.
  206. Re:HTML5 Video by TheLink · · Score: 1

    > QuickTime no longer enables the system tray icon by default and has not for a long time.

    Good to see some progress. But they're not going to get in my good books so easily. After all:

    > The QuickTime installer only contains QuickTime, the iTunes installer contains both iTunes and QuickTime.

    Sure maybe TODAY it does. But every now and then Apple "thinks different" see:

    1) http://www.digitalhomethoughts.com/news/show/92938/want-quicktime-apple-forces-you-to-install-itunes-to-get-it.html

    2) http://digg.com/software/Download_Quicktime_7_Without_Being_Forced_to_Install_iTunes

    3) http://jeremy.zawodny.com/blog/archives/005533.html

    So, no thanks.

    Maybe I'll switch if Adobe started forcing people to install Acrobat Reader even though they only want Flash Player...

    --
  207. Re:HTML5 Video by badkarmadayaccount · · Score: 1

    RefControl: Default:Block HTTP referer. ;)

    --
    I know tobacco is bad for you, so I smoke weed with crack.
  208. Re:HTML5 Video by aristotle-dude · · Score: 1

    You are changing the subject (cameras vs editors). But anyway.

    1. You found a chicken and egg problem with a proposed standard, congrats.
    2. Editors are software, easily patch-able if there is demand.
    3. Editors can output uncompressed and/or MJPEG which can be used by a dedicated encoder. It's possible to do Theora now, no question about it.

    Easy? So I take it that you have never written any software I take it? I've been working as a software developer for over a decade. It all appears deceptively easy to the uninitiated.

    A lot of people use tools like Quicktime, iLife or Movie Maker to quickly edit and upload their videos to places like Youtube. Where are people expected to get encoding software? Will it work seamlessly? Will they even care enough to choose Theora when the default might be H264? Where will these videos be hosted? How easy will it be to upload the videos?

    Most people don't even know what software is out there that allows you to play back Theora let alone encode in that format.

    Most people don't know about any of it for H.264 either, or for JPEGs or PNGs for that matter. They just go to a site with Firefox or Chrome and Theora video "just works". As far as encoding is concerned, anyone who knows enough to write HTML5 should be able to google for it.

    Thank you for proving my point. People expect their software to "just work". Without content in Theora format, they will have nothing to watch. As for creating and publishing in H264 format, there is Quicktime and iMovie which now support uploading in H264 to Youtube from within the application.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  209. H.264 won.... deal with it. by hazydave · · Score: 1

    H.264 had already won. It wins because it does the job the best. Yeah, it's a commercial thing, and that IS bad for the web in ways that's not really much of a big deal for other things. Similarly, delivering the best compression per bit is critical for video delivery over most other media, but particularly ... well, the places it's already used. Every major still or video camera maker uses H.264. Every Blu-Ray member, satellite companies like Echostar and DirecTV. Every major PMP maker.

    The simple fact is that H.264 is to the early 21rst century was MPEG-2 was to the 1990s... THE video standard format.

    The correct way to manage this the way the video players (DVD, Blu-Ray) have done, but that still sucks a little if you're Mozilla. Basically, every video format has both mandatory and optional formats it must decode. This makes this a bit harder on the player producers, but much easier on the content delivery folks.... the only have to chose one of the above. So if I make a Blu-Ray (I do, this isn't just hypothetical), I have the choice of H.264/AVC, VC-1 (WMV9), or MPEG-2 as the video format, and half a dozen audio formats, including a few flavors of AC-3 and plain old uncompressed.

    So the right consumer solution here would have been to demand that support H.264 and Ogg Theora as mandatory formats. Toss in a few optional formats if you like... they might not be popular, but you never know (MPEG Layer 2 audio was an optional format for Region 1 DVD, yet nearly every players supports it).

    To support open source, make the H.264 piece into a closed source, pay-for plug-in. This is how a number of companies (Nero, Archos, etc) have dealt with the extra cost of supporting AVC, at least at some time in the past. It might have a bad taste without those Fundamentalists among us who want to refuse even the possibility of closed source or proprietary formats getting into their faces, but for those who just want a practical engineering solution, this works. None of the Theora backers were EVER going to get the H.264 proponents to back down and embrace Theora as the only HTML5 video format. Look at the list... they're all the guys with the money, and most of them have vast investments already in H.264 content. Taking them on the way this was done, it was a guaranteed fail.

    But of course, this is the computer industry, where everyone has to fight over their one preferred solution, rather than take the "what's best for the most people" approach, which is really what the CE type solution comes down to. And of course, the CE industry NEVER has such format wars [ducking....]

    --
    -Dave Haynie
  210. Re:HTML5 Video by arose · · Score: 1

    Easy? So I take it that you have never written any software I take it? I've been working as a software developer for over a decade. It all appears deceptively easy to the uninitiated.

    We are talking about yet another encoder module, not an architecture overhaul. You have been a software developer, would you use modules for import/export functionality if you were developing an application that needs to deal with multiple file format? I'm not a professional developers, but I'm not completely clueless to the process either.

    A lot of people use tools like Quicktime, iLife or Movie Maker to quickly edit and upload their videos to places like Youtube.

    Will they even care enough to choose Theora when the default might be H264?

    If they don't care, they will not encode H.264 with just the right settings for youtube to pass it through without trans-coding. So the answer is, it doesn't matter if their high-bitrate H.264 export gets trans-coded to a lower bitrate H.264 or Theora video.

    Thank you for proving my point. People expect their software to "just work". Without content in Theora format, they will have nothing to watch.

    Except that that wasn't the point you were making (I cannot vouch for what you attempted to make). You said that people wouldn't know how to playback Theora and encode it, basically they wouldn't know what to make of these odd .ogg files. I don't see a way of reading "Most people don't even know what software is out there that allows you to play back Theora [..]" as "Firefox might play back Theora transparently, but since no one publishes Theora videos it doesn't actually 'just work' even if in reality it does as seen by the few people who actually do publish Theora vidoes". I might also add that the latter doesn't make much sense, so I might be completely misreading and would prefer clarification if I am.

    As for creating and publishing in H264 format, there is Quicktime and iMovie which now support uploading in H264 to Youtube from within the application.

    There is also Windows Movie Maker for XP, digital cameras that can capture videos in MJPEG and all sorts of other sources outside of the (still relatively small) Mac ecosystem. Youtube still accepts and trans-codes videos from these people, if they switched to Theora today the effect would be minimal.

    In case Quicktime and iMovie has a special mode that allows the video to avoid trans-coding there might be a slight quality loss as they would be trans-coded due to the format change. At least until someone gets around to implement it (or they'd insist in continuing to push a format they have for which they have patent in the pool and point fingers at Google).

    In the end however, web video is bigger then youtube and what I personally care about is the ability to put my videos on my site without paying a format tax in one way or another. If I have to point to a third party with a flash player for fall back for browsers other then Firefox, Chrome and Opera, then that's still better then having to rely on a third party exclusively. For Firefox to try to support me, more then they try to support Apples video editors is no surprise given their history.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  211. Re:HTML5 Video by arose · · Score: 1

    They know there's not going to be any more people asking for extra fees for H.264 - Theora simply isn't deep enough in the water for the subs to prepare their torpedos.

    Suspect or hope, they can't know this. And Google is a pretty big target and was On2 back in the day (VP3 has been around). If someone in the business had wanted to flex their patents, why wouldn't they have gone after a big codec developer?

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
  212. Re:Ideology meet reality that's why FSF will win by bill_mcgonigle · · Score: 1

    I prefer to live in a world of Freedom than one ruled by expediency.

    The freedom for there not to be choice and competition in VIDEO tag codecs?

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  213. Re:HTML5 Video by bill_mcgonigle · · Score: 1

    Ugh, quicktime ... I'd even rather have flash.

    You'd rather have the MPEG-4 file format than the Quicktime file format?

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  214. Re:Just give up your principles and compromize by hazydave · · Score: 1

    Well, sometimes there are folks who stick to religious convictions, regardless of the impact. Some religions reject the use of modern medicine, others, apparently, reject the use of some specific operating system interfaces (video), but curiously, not others (images, files, etc).

    And then there's occasionally someone who just wants to get the frickin' job done, and perhaps in a way that people will use it. Which is why everyone says "Linux" today, not "GNUix" or whatever..... Linus just got it done. I'm sure he's got plenty of principles, but they didn't get in the way of building something people would actually use.

    Mozilla looks like they are trying very hard to make themselves a moot point. I rather expect they'll just keep playing videos via a Flash plug-in, years after HTML5 takes off, with increasingly fewer users. Or we'll be getting the popular version of Firefox from somewhere else, the one that adds the external video CODEC option to Mozilla's base.

    They seem to be missing the point entirely here... popularizing Theora would lead to people using it. Force-feeding will not. And until Theora doesn't suck, and does get general support in video applications that are actually creating video (eg, via those same OS-level video CODECs that Mozilla abhors) it's not going to get much use. And I say this as a guy who does both engineering and video.

    --
    -Dave Haynie
  215. Re:HTML5 Video by Anonymous Coward · · Score: 0

    Open source software should not be "free" to download for people who have not contributed considerable code to the project.

    Ah, somebody fixated on creating artificial scarcity and who can't cope with the idea of non-rivalrous goods.

    The world is a richer place when things can be freely copied billions of times.

    Artificial scarcity, copyright and patents, are a primitive hack to encourage creation that possibly was going to happen anyway, nothing more, and often cost society much more than they give.

  216. HD Quality for camera-phone lolcats ? by DrYak · · Score: 1

    It's quality and bandwidth that makes Ogg Theora a problem right now. You need more bits for the same quality from an original source, plain and simple

    But once again : Do we *really* need that quality for crappy clips taken with sub-quality camera ?

    Yes, a 512kbit/s Theora will be more blurry as a 512kbit/s h.264. It would probably need a 768kbit/s to achieve the same visual quality as 512kbit/s h.264
    BUT what I'm arguing is that these extra 128kbit will only be spent trying to be more faithful to the artifact of the original video.

    I understand the debate "to achieve the same quality, Theora needs more bits". What I want people to take notice is, as long we're speaking about video-clip-upload websites (as opposed to website stream commercial HD shows & movies), these extra bits are useless : the difference in quality doesn't matter.
    That difference is only about which CODEC will be better at conveying the noise of the original clip MJPEG at 60%-quality.

    Google doesn't need to give the additional bits to Theora. Let it run at the same bandwidth as h264 - thus it won't cost Google any extra. The quality would be lower but : Nobody is really going to pay attention that much AND by doing so, they are enabling a patent un-encumbered format.

    Theora-users would be only losing some quality but still be part of the game.
    Whereas in the current situation, users of browsers who can't afford paying the h264 patents are left completely out.

    Google may well be going in yet-another-direction. They did just buy On2 {...} The On2 people claim VP8 is 40% more efficient (eg, bits at the same perceived quality) than H.264 for low bitrate video. {...} Even more interesting would be if Google open sourced VP8, assuming it's clear of any MPEG-LA or Microsoft or other video compression patents.

    That would REALLY be interesting. I was kind of expecting something on the long term, although I was more expecting it to come from the Dirac/Schroedinger projects. Which would probably one day too perform much better as h264 (given that it's a newer generation of technology) but are currently still very young and immature and still require lots of development.

    But I'm afraid that actually a Google Free/Libre VP8 would actually lead to even more fragmentation :
    - Google would be interested because of the bandwidth saving and the free/libre.
    BUT
    - Apple would still cling to h264, simply because it's hardware accelerated already in current chips on their iPhones. And probably because VP8 is more complex than h264 and more resource-hungry (thus CPU software decoding is a less desirable option).

    I think this whole debate will only close when embed hardware's GPU are advanced enough to OpenCL-based power-efficient implementation of codecs.

    What is a big deal is Mozilla saying, no, we're not going to support H.264, but we're also not going to support any of your system CODECs already.

    Well the whole idea behind "VIDEO" tag was to get rid of 3rd party plugins.
    If you insist on using 3rd party codecs you're back into the situation you were trying to run away from.
    Only worse, because you're not using plugin designed from the ground up for a browser, but instead feeding data directly from the virus-laden web straight into a video codec which might never been meant for anything else than a simple offline player.

    I you only solve the problem for platform having system codecs. You don't solve it for platform lacking support for h264 (like Windows XP among others). You don't solve the problem for all the interesting new and creative way to use the web (the mythical internet-enabled fridge :-P ).

    As pointed out by others : If you had to pay several million in patent fee to the CERN each time you implemented HTML or CSS, do you think that all the crazy disruptive development of the web would have happened since Tim Berners-Lee proposed it in 1980 ?

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  217. Re:Just give up your principles and compromize by Goaway · · Score: 1

    The fact is that they have options that do not require them to include h.264 code themselves. They are rejecting those outright too.

    It is ideological, and they would be the first to tell you so.

  218. Re:HTML5 Video by aristotle-dude · · Score: 1

    Open source software should not be "free" to download for people who have not contributed considerable code to the project.

    Ah, somebody fixated on creating artificial scarcity and who can't cope with the idea of non-rivalrous goods.

    The world is a richer place when things can be freely copied billions of times.

    Artificial scarcity, copyright and patents, are a primitive hack to encourage creation that possibly was going to happen anyway, nothing more, and often cost society much more than they give.

    This has nothing to do with artificial scarcity. It has to do with people valuing the work of others. When you pay for something, you are much more likely to value it but if it is free, it becomes something that has no value to you and is easily disposable.

    You seem to think that you are entitled to the work of others. Just because something is free, it does not mean that is does not have value. Unfortunately, many people like you do not see value in things that are free so it become necessary for you to work or pay for it in order to appreciate what something is worth. The problem is with your mindset.

    Open source software is written by people and it takes considerable effort. It's just so sad that most people are not capable of appreciating the value of a gift given by someone to the community at large. It should inspire you to contribute donations or learn how to program and contribute something yourself instead of being selfish and sponging off the good nature of others.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  219. its worse: 2028, not 2017 by jrincayc · · Score: 1

    Its worse. You would have to wait until 2028 for the US MPEG-LA H.264 patents to expire.

    http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-July/020737.html

  220. Waiting till 2028 is a long time by jrincayc · · Score: 1

    In the US the last MPEG-LA patents listed for H.264 expire in 2028, not 2017.

    http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-July/020737.html

  221. Relatively cheap and provides goodwill by jrincayc · · Score: 1

    Depends on whether they want a showdown with maybe Mozilla and definitely the Free Software community. Right now Google can probably claim that it is beta that they are only supporting H.264. However, if they persist in only supporting H.264 for youtube, they are basically saying that they do not want open source programs to be able to view youtube anywhere that H.264 is patented (which is more than just the US). Using a rate of $0.66/GB per year (Amazon S3 rate) the $5 million dollar MPEG-LA fee would buy about 7.2 petabytes of online storage ( 5e6/(0.055*12)/1024/1024 ) . So they can probably transcode and make it available online for something on the same order magnitude as the cost of the MPEG-LA licensing fee. I think it is fairly likely that Google will start supporting Ogg Theora/Vorbis as well.

    http://aws.amazon.com/s3/
    http://beerpla.net/2008/08/14/how-to-find-out-the-number-of-videos-on-youtube/

    1. Re:Relatively cheap and provides goodwill by shutdown+-p+now · · Score: 1

      However, if they persist in only supporting H.264 for youtube, they are basically saying that they do not want open source programs to be able to view youtube anywhere that H.264 is patented (which is more than just the US).

      Or, they can just point at Chrome, which is open source, and supports H.264...

    2. Re:Relatively cheap and provides goodwill by jrincayc · · Score: 1

      Chrome is not open source. Chromium is open source and does not support H.264. As I understand it, anywhere that H.264 is patented cannot have a legal and cost less open source implementation of H.264.