Slashdot Mirror


The Looming Video Codec Fight

itwbennett writes "With both Apple and Microsoft promoting HTML5 standards, you'd think that there would be joy in software freedom land. But instead there's another fight brewing. 'While it is true that HTML5 video is a step in the right direction, we also have to take into consideration the underlying codecs used to deliver the video content,' says blogger Brian Proffitt. The problem, says Proffitt, is that Microsoft and Apple's browsers will be supporting only the proprietary H.264 video codec by default. But Google supports only the WebM (VP8) and Ogg Theora codecs. 'So, basically, if Ogg Theora content starts making a dent in Apple and Microsoft's bottom line, or that of the MPEG LA's, then expect to see a lawsuit or two headed Google's way after 2015,' concludes Proffitt."

235 comments

  1. Or we could just fix patents and be done with it. by hedwards · · Score: 4, Informative

    Seriously, MPEG LA is going to create a new pool to try and kill WebM, I'm sure they're already working on it. The question is whether or not we're going to let a bunch of patent trolls control future development of the web. Standardizing around a standard that requires licensing fees is the wrong way to go.

  2. Firefox by Anonymous Coward · · Score: 0

    Why is there no mention of Firefox? Are they assuming that Mozilla is being stupid enough to kill itself before Firefox hits version 87 (approximately 1 year from now)

    1. Re:Firefox by jonbryce · · Score: 1

      TFA does mention Firefox

      "But Google (even though it's still listed as a licensee of H.264, right alongside Apple and Microsoft) has opted to avoid the 2016 problem altogether and support only the WebM (VP8) and Ogg Theora codecs, dropping support for H.264. Mozilla has opted for the same codecs for its Firefox browser."

    2. Re:Firefox by Baseclass · · Score: 1
      I'm OK with this, let the best browsers win.
      Also, there will be plugins/hacks available in no time, officially supported or otherwise.

      So what about Konqueror?

      --
      ^^vv<><>BA
    3. Re:Firefox by Lanteran · · Score: 1

      Konqueror can handle ogg and webM at the moment.

      --
      "People don't want to learn linux" hasn't been a valid excuse since '03.
    4. Re:Firefox by Grishnakh · · Score: 2

      Are they assuming that Mozilla is being stupid enough to kill itself before Firefox hits version 87 (approximately 1 year from now)

      I look forward to that. Then when I'm using Firefox 87, and I see someone using IE9 or IE10 (if it's out then), I can tell them they should use Firefox 87 instead. When they ask what's better about it, I can tell them "IE only goes up to 10. Firefox goes up to 87!".

    5. Re:Firefox by shutdown+-p+now · · Score: 1

      I can tell them they should use Firefox 87 instead.

      And then they'll ask, "what, like, from 1987?".

      Bad idea. ~

    6. Re:Firefox by Anonymous Coward · · Score: 0

      Who cares?

    7. Re:Firefox by Lanteran · · Score: 1

      The guy who asked maybe? Idiot.

      --
      "People don't want to learn linux" hasn't been a valid excuse since '03.
  3. FFMPEG To The Rescue by Anonymous Coward · · Score: 2, Insightful

    Seriously, who gives a shit? Patents are for lawyers. FFMPEG will play just about anything.

    1. Re:FFMPEG To The Rescue by Anonymous Coward · · Score: 0

      Absolutely! Browsers should just use libavcodec.

    2. Re:FFMPEG To The Rescue by hedwards · · Score: 2

      FFMPEG, which works until folks get sued for infringing the patent. It doesn't really matter who is doing the infringing ultimately, if you're having to either infringe or pay a fee to use a standard. For years the main headache I had from running FreeBSD as my primary desktop was no Flash, which meant no Youtube and same for dozens of other poorly designed sites.

      Which is the way that this is likely to end up.

    3. Re:FFMPEG To The Rescue by Gaygirlie · · Score: 1

      Seriously, who gives a shit? Patents are for lawyers. FFMPEG will play just about anything.

      That is not a rescue. If you are using FFMPEG you can be sued for patent violations.

    4. Re:FFMPEG To The Rescue by nzac · · Score: 1

      Only if the patient are valid in your country, which i'm fairly sure is not here.
      Don't know about exporting the finished product back to US though but no ones going to extradite over that.

    5. Re:FFMPEG To The Rescue by Teancum · · Score: 1, Informative

      Only if the patient are valid in your country, which i'm fairly sure is not here.
      Don't know about exporting the finished product back to US though but no ones going to extradite over that.

      Which implies that any engineering, design work, or for that matter manufacturing can't happen in America without paying off this protection racket. Yeah, that really helps promote a competitive "free market". And people wonder why manufacturing companies are leaving America?

    6. Re:FFMPEG To The Rescue by Lunix+Nutcase · · Score: 1

      That is not a rescue. If you are using FFMPEG you can be sued for patent violations.

      Bullshit. You can't get sued for USING ffmpeg. That's not how the law works. You can get sued for DISTRIBUTING it in the without a proper license in areas in which the software patents are in effect, but that's a completely different thing.

    7. Re:FFMPEG To The Rescue by nzac · · Score: 1

      I wonder if a dedicated sever would get you around this?
      Can the patient make transferring a binary file illegal?

    8. Re:FFMPEG To The Rescue by Alex+Belits · · Score: 1

      Actually no. Copyrights are for distribution.

      --
      Contrary to the popular belief, there indeed is no God.
    9. Re:FFMPEG To The Rescue by Gaygirlie · · Score: 1

      Bullshit. You can't get sued for USING ffmpeg. That's not how the law works. You can get sued for DISTRIBUTING it in the without a proper license in areas in which the software patents are in effect, but that's a completely different thing.

      Incorrect. Copyright law handles distribution of software, patent laws apply even when you aren't distributing something. You are mixing the two things.

    10. Re:FFMPEG To The Rescue by terrox · · Score: 0

      patent. and no it isn't possible to just bypass the issue.

    11. Re:FFMPEG To The Rescue by Anonymous Coward · · Score: 0

      I have a license, my video card can play h264, so I must have one.

    12. Re:FFMPEG To The Rescue by Anonymous Coward · · Score: 0

      Just because you own hardware doesn't mean your legally allowed to use it.

      previous statement is both hilariously true and depressing.

    13. Re:FFMPEG To The Rescue by Anonymous Coward · · Score: 0

      As the law provides, patents "grant to the patentee ... right to exclude others from making, using, ... the invention throughout the United States"
      http://www.law.cornell.edu/uscode/35/154(a)(1).html

      If you are using FFMPEG in the US to encode or decode patent encumbered codecs, you are violating the law. Individuals could certainly be sued. However, if MPEG-LA were to sue an individual, it would make them very unpopular. For example Linus Torvalds has publicly stated that he uses the patent encumbered gstreamer plugins-ugly, and has yet to be sued:
      https://bugzilla.redhat.com/show_bug.cgi?id=439858#c19

  4. Since when? by Lunix+Nutcase · · Score: 3, Informative

    But Google supports only the WebM (VP8) and Ogg Theora codecs.

    Wrong. It still plays HTML5 video that is H.264.

    1. Re:Since when? by Anonymous Coward · · Score: 0

      Last I heard they removed that capability in January (and Microsoft swiftly released a Chrome plugin to put it back, on Chrome for Windows). Are you saying they backed off the position?

      I'm currently on Windows so I can't verify for sure since Chrome on Windows has H.264 in the same sense that IE9 has WebM.

    2. Re:Since when? by Lunix+Nutcase · · Score: 1

      No, last January they said they were planning to drop it. But, no, they haven't done so. I just tested it by playing an H.264 video in an HTML5 player.

    3. Re:Since when? by hedwards · · Score: 1

      They haven't finished converting the videos. Last I heard, they hadn't managed to ad advertising to their WebM selection. But, I can attest to the fact that there are plenty of WebM videos on Youtube, they just haven't gotten around to converting the whole site.

    4. Re:Since when? by Lunix+Nutcase · · Score: 1

      Even still they won't drop H.264 then unless they are planning to fuck over people using the youtube app that gets streamed H.264 video due to the hardware accelerated playback. And I wasn't talking about Youtube when I was playing the video, anyway. The whole H.264 thing with Google is mostly posturing anyway otherwise they would have dropped it in Chrome months ago.

    5. Re:Since when? by hedwards · · Score: 1

      I'm not so sure, Google has to pay a licensing fee for the codecs that handle the encoding and decoding process. Also, didn't they dump the codec only to have MS provide a workaround on Windows computers?

    6. Re:Since when? by 93+Escort+Wagon · · Score: 4, Informative

      But Google supports only the WebM (VP8) and Ogg Theora codecs.

      Wrong. It still plays HTML5 video that is H.264.

      Spot on - they only announced the intention to remove it; however H.264 HTML5 video still plays just fine in Chrome.

      Additionally, they're only removing it from the desktop Chrome browser - not Android. When asked about H.264 support in Android, they specifically drew a (rather artificial IMHO) distinction between the desktop and mobile platforms.

      --
      #DeleteChrome
    7. Re:Since when? by Lunix+Nutcase · · Score: 2

      I'm not so sure, Google has to pay a licensing fee for the codecs that handle the encoding and decoding process.

      Yeah, at max they will pay a "whopping" $6.5 million a year which is less than a fraction of 1% of their yearly revenue. Secondly, mobile devices do not have hardware acceleration for WebM and there are no future models that list that as something to be included so are they going to force people to use a software decoder and draing their battery many times faster? Doubtful.

      Also, didn't they dump the codec only to have MS provide a workaround on Windows computers?

      No, they didn't dump it as I already said. Microsoft was goign to release an extension or something for Chrome if they had dropped it to provide H.264 support but I have no such thing installed. Just go to the HTML5 test and you can see that Chrome still lists H.264 support. Also go: here which is an HTML5 video in H.264 which plays just fine even in the most up-to-date dev version of Chrome.

    8. Re:Since when? by Lunix+Nutcase · · Score: 1

      Oh and if you still don't believe me that Google isn't dropping H.264 here:

      A Google Spokesperson tells Webmonkey that the announcement is related to "Chrome only and does not affect Android or YouTube."

      H.264 is still going to live on.

    9. Re:Since when? by Lunix+Nutcase · · Score: 2

      Yep, they were just posturing which is why if they were really going to do it they would have already done it by now. Google was just trying to use the whole WebM vs H.264 thing to push Google TV and all that but when that fell through it's amazing how we heard no more news about H.264 support being dropped.

    10. Re:Since when? by Anonymous Coward · · Score: 0

      That distinction isn't artificial. Mobile chipsets don't decode vp8 or theora in hardware and that's that. It will take quite a while before any HW implementation of these codecs actually make any way inroads so dropping h264 becomes a viable option.

    11. Re:Since when? by bWareiWare.co.uk · · Score: 1

      The Rockchip RK29xx already has full hardware decoding of VP8. It also happens to be by far the most commonly used chip in upcoming media players and TVs.
      Google have also provided the same VHDL or Verilog to the 20 other manufactures so it is likely all future media SoCs will support it.

    12. Re:Since when? by Compaqt · · Score: 1

      Well, for one thing, they're the head of the coalition of handset manufs that have a leading market share now (Open Handset Alliance).

      And for another, they just bought a phone manufacture (Motorola), so I think you can expect to see WebM support coming soon to a phone near you.

      For a trifecta, they own YouTube. So if they decide they want to drop h.264 support, they can certainly play the game.

      --
      I'm not a lawyer, but I play one on the Internet. Blog
    13. Re:Since when? by Lunix+Nutcase · · Score: 1

      Well, for one thing, they're the head of the coalition of handset manufs that have a leading market share now (Open Handset Alliance).

      Great. But what video chipsets or SoCs does Google make? Oh right, none. So even if they wanted to push something with WebM it would be years out from now before it'd make it into a mobile device.

    14. Re:Since when? by SiChemist · · Score: 1

      Geez! Did you even read any of this thread before you commented?

      by bWareiWare.co.uk (660144) Alter Relationship on 05:58 AM September 24th, 2011 (#37500676)

      The Rockchip RK29xx already has full hardware decoding of VP8. It also happens to be by far the most commonly used chip in upcoming media players and TVs.
      Google have also provided the same VHDL or Verilog to the 20 other manufactures so it is likely all future media SoCs will support it.

  5. Bring it on by Anonymous Coward · · Score: 0

    Personally, I say bring it. If indeed WebM and/or Ogg Theora are in violation then they need to fix the violation or get out of the video business. The whole premise that this is wrong is based on the notion that patents on software is wrong which is idiotic IMHO.

    1. Re:Bring it on by ScrewMaster · · Score: 3, Insightful

      Personally, I say bring it. If indeed WebM and/or Ogg Theora are in violation then they need to fix the violation or get out of the video business. The whole premise that this is wrong is based on the notion that patents on software is wrong which is idiotic IMHO.

      You'll need to explain that in more detail. Most people that I know who are in the software industry (myself included) take a diametrically-opposed view of software patents.

      Furthermore, even if (and it's a big 'if') software patents have any real benefit to anyone but anti-competitive corporate sociopaths such as Apple Computer, the way the law and the United States Patent Office are handling them is an abomination. Inventions are an expression of an idea: patenting the expression is one thing ... patenting the mere idea is another, and that is very wrong.

      --
      The higher the technology, the sharper that two-edged sword.
    2. Re:Bring it on by hedwards · · Score: 1

      Patents on software is one thing, patents on standards is quite another thing. It's completely unacceptable for a standard to require a party to license the patent to use the standard. You can sort of get away with it, when it's a standard solely for interacting with a particular software package, but otherwise it's obnoxious and has no place in a standard.

      Just look at the headaches with GIF and JPEG, if you don't believe me.

    3. Re:Bring it on by Dahamma · · Score: 1

      Actually, GIF wasn't an official "standard", just an image format created by Compuserve and adopted in a bunch of other places.

      And JPEG was specifically designed/created to be patent royalty free:

      "The JPEG committee has as one of its explicit goals that their standards (in particular their baseline methods) be implementable without payment of license fees, and they have secured appropriate license rights for their upcoming JPEG 2000 standard from over 20 large organizations."

      There have been a few lawsuits over patents claimed to be infringed by JPEG, but they were from patent trolls who were ultimately unsuccessful.

      But I agree that the way some standards like MPEG, JEDEC, etc. handle patent licensing is ridiculous (though I guess the JEDEC fiasco was mostly due to Rambus' douchy behavior...)

    4. Re:Bring it on by ceoyoyo · · Score: 1

      A video codec is about as close to the expression of an idea as you get get without limiting patents to actual machines (and I just have to switch around a gear or something to make my expression different than yours).

      Stupid software patents like CSS tricks and one click are bad, but they're bad because they're obvious or trivial, things that are already not supposed to be patentable. Clever, nontrivial or obvious algorithms themselves should be patentable just like a clever chemical process or mechanical process should be patentable. Video codecs fall into the latter category.

    5. Re:Bring it on by GNUALMAFUERTE · · Score: 1

      Absolutely. I own a software and hardware dev company. We are firmly opossed to software patents. I find the idea laughable. I know competition will try to implement the features I include, and I'll do the same. That drives innovation, and helps create both formal and ad-hoc standards. Whenever I include a feature that noone has included before, I try to make as complete as possible, and we start working on an update right on release date, knowing I still have to compete We don't own a single patent, and we develop both proprietary and GPL products. We have earned a nice marketshare playing fair, we give our customers free updates for life, and we free most of our code. If you want to play fair, you don't need no stinking patents.

      --
      WTF am I doing replying to an AC at 5 A.M on a Friday night?
    6. Re:Bring it on by Teancum · · Score: 1

      Perhaps you might be correct here.... so far as the ideas expressed in a patentable video codec would need to be rather narrow in definition where the patent really only covers the specific approach used with a particular codec.

      Sadly, particularly with software patents, they are typically interpreted very broadly where you are being held liable for infringement merely because you wrote a single line of code.... in whatever language you are writing that software.

      If you could write some software completely from scratch without having seen the work of somebody else, I don't think you should even be capable of infringing somebody's patent. Sadly, I think most programmers at the moment unintentionally violate several patents, often on a daily basis, merely because they can't constantly search the USPTO website to make sure they aren't infringing on somebody's patent. Where is the justice in that?

    7. Re:Bring it on by Teancum · · Score: 4, Interesting

      The issue with GIF wasn't even Compuserve, but rather some patent trolls at Unisys who discovered that they held a patent on the LZW compression algorithm. Unisys went to Compuserve with a legal threat, but also a licensing scheme where they and their customers could be absolved of past and future infringement if they would submit to the license.... and they capitulated.

      In fairness to Compuserve, the developers who created the GIF standard intended it to be patent and royalty free. Their mistake was picking up an ACM Journal and discovering the LZW algorithm when they were trying to establish the format, thus adopting that algorithm into the standard. Typically at the time, algorithms published in such a manner were considered "in the public domain"... or at least assumed so if you were formally publishing how they were working in an internationally recognized journal of that nature. Certainly in the article where this algorithm appeared there was no mention of intellectual property other than a copyright on the article itself. Software patents were presumed to be something you would do to something that you also protected via trade secrets and deliberately tried to keep from your competitors except for a begrudging filing with the USPTO that was usually obfuscated enough that you couldn't really figure the algorithm out from the patent application anyway.

      It should be noted that IBM also seemed to have a patent on LZW algorithm, so the claim by Unisys could have been challenged from multiple fronts. The problem was that nobody wanted to take them on so it was either ignored or people capitulated to Unisys.

      The largest problem with the GIF format was the issue that web browsers had adopted the GIF standard as a de facto image standard and the only universal image format across multiple operating systems and browsers that displayed images. JPEG images were starting to come into use, but there are limitations on JPEG images and it wasn't nearly so universal. Furthermore, most image editing software at the time Unisys started to demand royalty payments supported the GIF standard.... in part because it was thought to be patent and royalty free.

      This stands out because it was one of the first software patents that really impacted a broad swath of software developers and pretty much hit nearly every internet user at about the same time. Few companies are willing to let such "submarine patents" languish without enforcement any more because too much money can be made through enforcement before the concept becomes essentially an international standard. Unisys got lucky after a fashion too, as they certainly didn't contribute to the development of the GIF standard.

      In terms of "official standard", I guess that is in the eye of the beholder. I do believe that the W3C did archive the GIF standard and provided links to Compuseve's documents on the format as a recommended image format for web browsers before the patent issue hit the fan. It certainly was hard to avoid the use of GIFs even if you tried, and was a pretty universal image format even before web browsers were created.

    8. Re:Bring it on by Dahamma · · Score: 1

      In terms of "official standard", I guess that is in the eye of the beholder. I do believe that the W3C did archive the GIF standard and provided links to Compuseve's documents on the format as a recommended image format for web browsers before the patent issue hit the fan. It certainly was hard to avoid the use of GIFs even if you tried, and was a pretty universal image format even before web browsers were created.

      Yep, everything you say is true, of course - I was just pointing out that neither GIF nor JPEG was really an example of a standards body intentionally expecting implementors to pay licensing fees. JPEG in fact tried to avoid it and was hit by trolls, and GIF was just one of those de facto standards in the early days of the Internet that was also hit by a troll.

      IMO it would be interesting to see if there could be some sort of government registration of "standards" that requires a review and formal submission process/timeline for any potential infringing patents, after which it is officially declared patent-free and open for implementation by anyone. Seems like that would go a long way towards preventing patent trolls like this...

    9. Re:Bring it on by Teancum · · Score: 1

      At the very least, if courts recognized standards bodies and invalidated patents not disclosed for standards widely published after a certain period of time, I think that would go a long way in terms of stopping trolls. Part of the problem with a patent is that you don't have to enforce it like you do with trademarks and copyright. With copyright, if you ignore enforcement.... the infringement is held to be legal. With patent law, you can file a lawsuit decades after infringement and even seek compensation for infringement in the past.

      In the case of the GIF format, had Unisys been up front about the fact they held the patent, most people would have either dealt with the licensing or not used the format but would have done so with knowledge of what they were doing. It might have even pushed the development of the PNG format to a much earlier time frame. Disclosure is the key, and the problem was that disclosure didn't happen.

      Unisys did contemplate the idea of going after previous infringement, as technically the law permitted them to essentially "own the internet" and demand billions of dollars from nearly every internet user. They risked the potential, however, of somebody willing to stand up to such a tactic and invalidating the patent altogether.... so they chose instead the path of least resistance. Their licensing terms were screwy at best, and I did try to negotiate a license with them at one point in my professional career explicitly for a product that used GIF images. I ended up telling Unisys to get lost after they came back with a counter-offer.

    10. Re:Bring it on by DNS-and-BIND · · Score: 1

      Decoding a compressed JPEG image took a non-trivial amount of CPU power back then, too. Put 20 of them on a web page and watch your computer grind to a halt decompressing them.

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    11. Re:Bring it on by ceoyoyo · · Score: 1

      It's not trivial to write a working, modern video codec without using techniques other people have invented, and the patents on those techniques are fairly specific. The parts that aren't fall under "obvious." Again, "software patents" is too broad a category - there are good patents on algorithms and poor, overly broad patents on non-software. I do agree that a better patent search mechanism would be a good idea though. On the other hand, the algorithms that are protected by good patents tend to come with a clear warning in books.

      I remember when I was doing some graphics work, VTK came with a marching cubes filter with a warnings stamped all over the documentation that it was patented.

    12. Re:Bring it on by Pinky's+Brain · · Score: 1

      All the MPEG-LA members are too chickenshit to commit their patents. There is nothing for WebM to fix, since no patent number has ever been mentioned.

      The MPEG-LA members know better than most that patent litigation is a complete fucking crapshoot, everything is far too interconnected for any real judgement to be made ... it all comes down to whether the scribbles on a piece of paper from a random bunch of inbreds in Texas looks more like guilty or not guilty. They are riding the gravy train with the patent pool and they aren't going to jeopardize that in litigation against Google.

    13. Re:Bring it on by ScrewMaster · · Score: 1

      They are riding the gravy train with the patent pool and they aren't going to jeopardize that in litigation against Google.

      Yes. It would be a damned shame if Google got some of those oh-so-valuable patents invalidated. I'd really like them to go after IBM: the Nazgûl would take them down a notch or two.

      --
      The higher the technology, the sharper that two-edged sword.
    14. Re:Bring it on by Aighearach · · Score: 1

      The SCOTUS already provided the details, we can only react to those realities in one way or another.

      You don't have to understand the weather to look outside the door and choose good boots.

    15. Re:Bring it on by KingMotley · · Score: 1

      Are any of the people you know in the software industry over the age of 25? Most entry level programmers don't like software patents, but that is only because they themselves aren't trying to make, sell, and distribute something they have written themselves. When the shoe changes feet and they develop something new and innovative, and then when a multi-billion dollar company steals the idea, hires a team of programmers and re-creates it, and then starts putting improvements on it 10 times quicker than you can ever hope to, they will quickly scream bloody murder and how the government needs to do something to prevent this.

    16. Re:Bring it on by ScrewMaster · · Score: 1

      Are any of the people you know in the software industry over the age of 25?

      All of them. I'm over fifty myself. And why is it the government's job to provide such protection?

      The reason that we look at software patents as a bad thing is that we do care about our work, and what we don't want is some big team of lawyers telling us that we can't use or improve algorithms in order to make our products better. The software industry moves at warp speed compared to just about any other: assigning patent protection to algorithms (or at best, the expression of same in code) serves no valid purpose. In any event, how you look at this depends entirely upon what you believe the purpose of software patent protection to be: the advancement of the useful arts and sciences, or the suppression of progress in order to maintain the revenue streams of a comparatively few large patent holders. You decide.

      This particular issue, that of codecs, is a perfect example. There's tons of money to be made in this business by every legitimate entity involved regardless of patent protection. The only real beneficiaries here are companies that simply don't want to be bothered by someone outside their little cabalistic group coming up with something better, even though in the long run they too would benefit from such progress.

      Granted, much of the debate here centers as much upon the unbelievably poor handling of software patents (indeed, patents in general) by Congress and the United States Patent Office as it does upon the mere existence of this class of patents. Nevertheless, anyone who is concerned about the long-term health of the profession of developer, and the advancement of the state of this particular art, should be very concerned about software patents. You can say what you like about how software needs the dubious "protection" of patents, but the reality is that this industry has not only survived but thrived for decades with nothing but the substantial defenses afforded by copyright. Copyright your work, sue if your rights are infringed by illegal distribution, obfuscate your executables if necessary to maintain your trade secrets. There are plenty of effective ways to protect your intellectual assets, especially in the age of Web applications where your oh-so-valuable code need not reside on the customer's equipment, making reverse engineering impossible. On the other hand, telling me that I can't use a particular mathematical expression in my code is, well ... patently ridiculous. Arguably even more batshit insane than universities and corporations that are patenting genes. Genes.

      It's pretty clear at this point that software patents are little more than a blunt instrument used by the big boys to suppress potential competition, and trolls to extort money from the organizations they parasitize. They simply don't have much benefit to the little guy, in practical terms: unless you happen to have accumulated a substantial number of relevant patents for defensive purposes and have a correspondingly hefty legal budget, the big boys will do what they want with your world-changing patented "idea". Sure, you can take them to court and try for some degree of redress, but that's a massively expensive undertaking. In the meantime, if your algorithm is truly valuable, they'll be making millions from it. If you're a small developer or startup, depending upon the law to protect your assets is a mistake as it simply does not work in your favor. The odds of winning a patent lawsuit generally work like this (no. of relevant patents x size of legal department) + (relative innumeracy of the judge and jury.)

      The Founders perspective (very clearly expressed in the Constitution) was that the ultimate beneficiary of what we now know as "intellectual property" was to be We the People, and that both patents and copyright were, ultimately, to benefit the public domain. So yes, I understand your point: nobod

      --
      The higher the technology, the sharper that two-edged sword.
    17. Re:Bring it on by ScrewMaster · · Score: 1

      The SCOTUS already provided the details, we can only react to those realities in one way or another.

      You don't have to understand the weather to look outside the door and choose good boots.

      Congress still has the power to change matters. They have no particular incentive to do so, but they could. Theoretically.

      --
      The higher the technology, the sharper that two-edged sword.
    18. Re:Bring it on by KingMotley · · Score: 1

      And your point of view is on how terrible it may be that you can't implement something that someone has already done into your own applications. I'm on the other end of the balance. My projects are typically innovative. They aren't copies of something that someone else has done before, so I'm more afraid of a large company stealing my ideas and profiting from them than I am of whether I can or can't steal the ideas someone else had.

      That doesn't mean I'm in total agreement with how software patents have been granted in the past. They are typically too broad (See i4i vs Microsoft), too general, and for things that are rarely innovative (See "click once"), or a simple repacking of one idea+some new medium=new patent.

      As for the software patents being a blunt instrument used by the big boys.. I guess I'm in a special situation. I'm not big, but if a large company did decide to try and steal one of my ideas, I could quickly raise the capital to fend them off if necessary, but then again, I'm easily bought off if they present a large enough check. I'm not out to rule the world, just earn enough to keep food on the table, a roof over my head, and a slew of sports cars parked in my garage.

  6. H.264 isn't closed by vijayiyer · · Score: 2, Informative

    I don't know what it will take to get people straight on this. H.264 is open and is a standard, but patented. WebM isn't a standard, but isn't patented.

    1. Re:H.264 isn't closed by wagnerrp · · Score: 1

      I don't know what it will take to get people straight on this. WebM is a standard, it just isn't standard. It is a static, published set of audio and video codecs, and a container to package them in. It is just not standard as it has limited browser support, and no hardware support.

    2. Re:H.264 isn't closed by kvvbassboy · · Score: 1

      It has the same effect in that Mozilla will not be able to license the patents to implement H.264.

    3. Re:H.264 isn't closed by Salvo · · Score: 2

      WebM is not a documented standard; The standard is the implementation. Google can change the implementation at any time and the standard follows.
      H.264 is a documented standard; anyone can write their implementation and as long as it adheres to the standard, it can be called a H.264 codec.

      The problem with documented standards is their lack of flexibility. It is also their greatest advantage. That is why there are always new versions of standards: HMTL, HTML2, HTML3, xhtml, HTML4, HTML5; MPEG, MPEG2, MPEG4, etc.
      WebM is too dynamic, or has the potential to be dynamic. This is a huge disadvantage in a standard.

    4. Re:H.264 isn't closed by Gaygirlie · · Score: 4, Insightful

      I don't know what it will take to get people straight on this. H.264 is open and is a standard, but patented.

      In practice it's the same thing as you still cannot implement H.264 encoding or decoding without a license.

    5. Re:H.264 isn't closed by hedwards · · Score: 2

      H.264 requires people to pay a licensing fee to use. They have magnanimously agreed to allow people to stream H.264 for free, knowing that they've been paid for the software to encode the stream and for the software to decode the stream. That's enough to prevent the software from being freely available and shouldn't be the case with an open standard.

    6. Re:H.264 isn't closed by vijayiyer · · Score: 1

      If it's not a formal standard issued by a standards body, and it's not a de facto standard, what really makes it a standard? If simply publishing defined a standard, almost anybody could create a standard, and there would be nothing standard about it.

    7. Re:H.264 isn't closed by Lunix+Nutcase · · Score: 1

      WebM is a standard, it just isn't standard.

      In what way is it a standard? Is it an ISO standard? Is it an ECMA standard? Is it a W3C standard? Right, it's not a standard of any standards body. Just because something is open source does not make it a "standard".

    8. Re:H.264 isn't closed by Lunix+Nutcase · · Score: 1

      H.264 requires people to pay a licensing fee to use.

      Not true. For non-commercial streaming use it's royalty-free and if you ship an encoder and/or decoder you only pay royalties for any units over 100,000 that you ship. Outside of a Google it is pretty much free for anyone. And even for someone like Google the royalties cap out at like $6 million dollars a year which is a pittance to someone pulling in 10s of billions of dollars in revenue.

    9. Re:H.264 isn't closed by Anonymous Coward · · Score: 1

      you only pay royalties for any units over 100,000 that you ship

      Its a darn good thing then that all these free software projects like GStreamer or VLC have thousands of dollars to spend on royalties when users download their software and distributions package it up for users.

      Oh wait.

    10. Re:H.264 isn't closed by Anonymous Coward · · Score: 1

      In the same way that RFCs are standards. They put out documentation and code, people adopted it.

    11. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      WebM may or may not be patented.

      There is no way to really tell until patent holders come out of the wood work, which would certainly happen if WebM becomes the winner.

      H.264, on the other hand, seems to have brought the patent holders out already. And there is a coherent licensing scheme in place to make those patent availables.

      So:
      H.264 = patents, but manageable.
      WebM = no clue, might get lucky, might get sued shitless.

    12. Re:H.264 isn't closed by Anonymous Coward · · Score: 2, Informative

      I don't know what you're talking about. The VP8 bitstream is frozen. WebM and VP8 are well-documented formats. An alternative codec, libvpx, was written based on the spec alone and released over a year ago. It's actually better than Google's implementation. libvpx is a VP8 codec just as much as x264 (also by DarkShikari) is an H.264 codec.

    13. Re:H.264 isn't closed by Meneth · · Score: 1, Informative

      Tell that to x264 and FFmpeg.

    14. Re:H.264 isn't closed by Anonymous Coward · · Score: 1

      (replying to self) Oops, mixed the names up. libvpx is the Google codec. ffvpx is the alternative VP8 decoder, and I think it's still more performant than the libvpx decoder. A new encoder based on the x264 framework is in the works. Other hardware and software implementations are also being developed. You can't pretend it's just one opaque codec owned by Google. WebM might not formally be a standard yet, but it's an open and well specified format.

    15. Re:H.264 isn't closed by MrHanky · · Score: 1

      It doesn't need a standards organisation behind it to be a standard. For instance, ed, the standard editor, is standard because it's ed!

    16. Re:H.264 isn't closed by YesIAmAScript · · Score: 1

      Decoding h.264 streams is free as long as the content in the stream is free. So you can stream and decide content without paying.

      There still is a significant license fee for encoding.

      --
      http://lkml.org/lkml/2005/8/20/95
    17. Re:H.264 isn't closed by tepples · · Score: 5, Insightful

      To lawfully use x264 and FFmpeg without a license from MPEG-LA, I'd have to 1. move out of the United States and other countries where software patents are enforced, and 2. move all my customers out of the United States and other countries where software patents are enforced.

    18. Re:H.264 isn't closed by Anonymous Coward · · Score: 1

      Tell that to x264 and FFmpeg.

      I did. They said something about being based in France...

    19. Re:H.264 isn't closed by BitZtream · · Score: 1

      And its included by default in everything UNIX install this side of the moon basically. Defacto standard.

      WebM is used in ... (crickets)

      See the difference?

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    20. Re:H.264 isn't closed by reasterling · · Score: 1

      That is why there are always new versions of standards: HMTL, HTML2, HTML3, xhtml, HTML4, HTML5

      What a great example of how a standard that has 0 royalty fees and is not patented can truly benefit the whole human race. It would be hard to imagine what the web would be like today if you had to pay a fee to create HTML code. It would basically block the poor from making a web site. Should the barrier of entry to just view the web have to include the cost of a windows licence or worse a mac?

      I know you are not the one to mention this, but there have been several who have commented along these lines of thought. This only affects the Linux users who do not want to pay for their software. I thought that companies like Microsoft and such complain about piracy. Linux and other free OSs are the ONLY alternative that the poor have to remain legal on their pieced together computers. I speak from personal experience after building my first computer from parts given to me I wouldn't have been able to use it legally with out the copy of turbo linux to put on it.

      Software patents are nothing more than a tool used by large corporations to stifle competition. Building a standard like HTML5 around patented software only serves those who own the patents.

      On a side note, I sometimes miss the days when Linux didn't just work. I enjoyed spending time learning about my computer by having to add device nodes and such. I also miss the days when xfce actually resembled cde.

      --
      "For I desired mercy, and not sacrifice" -- God
    21. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      Firefox, Chrome, Opera and fucking YouTube?

    22. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      In what way is it a standard? Is it an ISO standard? Is it an ECMA standard? Is it a W3C standard? Right, it's not a standard of any standards body. Just because something is open source does not make it a "standard".

      WebM is an Internet-Draft (I-D) standard of Internet Engineering Task Force (IETF).

      The IETF standards process is documented here:

      http://www.ietf.org/about/standards-process.html

      The IETF produce Internet standards via "RFCs". This process is the way Internet standards such as email were arrived at.

    23. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      The only holds true until 2015. At that stage the terms will change. At this stage we don't know what the new license terms will be, but I'm sure that if H.264 is completely dominating the web then the terms won't be a good, they won't need to be. The current licensing terms are designed with one thing in mind, getting H.264 into a dominant position that can the be taken advantage of at a later date.

    24. Re:H.264 isn't closed by Patch86 · · Score: 1

      If you use H.264, you (potentially, at least) will need to pay its owners a licensing fee.

      In my mind, it's somewhat irrelevant as to whether that's regulated by copyright law, patent law, trademark law, contract law, or the laws of thermodynamics; the upshot is the same. If you are reliant on the owner's permission in order to use a piece of software, then that isn't "open".

    25. Re:H.264 isn't closed by Gaygirlie · · Score: 1

      Tell that to x264 and FFmpeg.

      They aren't located in a place where software patents are valid.

    26. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      You just described the modus operandi of RFCs

    27. Re:H.264 isn't closed by E+IS+mC(Square) · · Score: 1

      Yeah. Two out of three leading browsers + few other non-trivial ones is crickets.

    28. Re:H.264 isn't closed by smash · · Score: 1

      Thats it. However the other thing is that everybody already owns media, and media generating devices like cameras that produce h.264. So, even if you get your shiny new vp8 player, how are you going to transcode all the h.264 you own into vp8, without paying for a h.264 decoder license? Never mind that quality wise, h.264 has proven to be superior.... and its... y'know.... already in that format...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    29. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      Bullshit. Mozilla most certainly can afford to license H.264 with its ~$80 million/year in revenue.

      But then again, they don't actually have to license H.264. They can simply use whatever codecs are installed on the system.

      So what we have is a situation where they have 3 choices. (A) License H.264. (B) Use H.264 if the codec is installed on the system. (C) Refuse to support H.264

      They hove chosen (C) .. so spare us the crap about Mozilla not being able to license the technology, and spare us the crap about not being able to support the technology.. they refuse to do either of those simply as a matter of stubborn choice.

    30. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      Perfect solution: ignore the USA (and everyone who wants to join them) and we'll see how innovation proceeds in this world.
      My guess is that the "software patent" countries will be the "developing countries" within 50 years.

    31. Re:H.264 isn't closed by nine-times · · Score: 1

      Well honestly the bigger issue is that you can't distribute H.264 content without a license.

      But no, the fact that it's an open standard *does* matter. Maybe not in the short term of "What can I as a consumer do today?" but in a lot of non-obvious ways. Things like, "What are the practical concerns for using this as an archival format?" and "If I were developing a new platform that MPEG-LA didn't want to support, could I theoretically write an implementation myself?"

    32. Re:H.264 isn't closed by Gaygirlie · · Score: 1

      "If I were developing a new platform that MPEG-LA didn't want to support, could I theoretically write an implementation myself?"

      Only if you live in a country that doesn't support software patents, otherwise you could get sued; in other words, no, you couldn't write such an implementation yourself in that case.

    33. Re:H.264 isn't closed by ScrewMaster · · Score: 1

      (replying to self) Oops, mixed the names up. libvpx is the Google codec. ffvpx is the alternative VP8 decoder, and I think it's still more performant than the libvpx decoder. A new encoder based on the x264 framework is in the works. Other hardware and software implementations are also being developed. You can't pretend it's just one opaque codec owned by Google. WebM might not formally be a standard yet, but it's an open and well specified format.

      So I understand. That's pretty much in character for Google anyway: they're incredibly opaque in terms of their internal operations, but remarkably open when it comes to their choice of Internet standards and public APIs. I doubt they'd have bothered with VP8 or anything like it if there'd been an existing standard that was adequate for their needs (both technically and legally.)

      --
      The higher the technology, the sharper that two-edged sword.
    34. Re:H.264 isn't closed by nine-times · · Score: 1

      You *can* write your own implementation. You'll just have to pay a licensing fee.

    35. Re:H.264 isn't closed by ScrewMaster · · Score: 1

      H.264 requires people to pay a licensing fee to use.

      Not true. For non-commercial streaming use it's royalty-free and if you ship an encoder and/or decoder you only pay royalties for any units over 100,000 that you ship. Outside of a Google it is pretty much free for anyone. And even for someone like Google the royalties cap out at like $6 million dollars a year which is a pittance to someone pulling in 10s of billions of dollars in revenue.

      You do realize that that is not cast in stone? That they can change those terms at any time? That the only reason they're so "reasonable" (and I use the term loosely) is to encourage adoption and keep any potential competition at bay? Remember, the first hit is free.

      These people aren't stupid (sleazy and highly unethical, yes, but not stupid) and as soon as they believe that their's been a sufficient uptake of their codec they'll start hitting manufacturers and developers up for more money. That's how the game is played, and they'll try to find that sweet spot where they maximize profit at the expense of some number of users. Heinlein said it best, "Never depend upon another man's better nature ... he might not have one." Well, here's a case where we already know they don't, so becoming willingly dependent upon MPEG-LA's good will is a foot-in-self-shoot situation.

      Most of those users will be people that are unable to legally run that codec unless they buy into expensive licensed software and operating systems. I run a Linux household. Linux does what we need and want, and I'm perfectly legal without giving Microsoft or Apple Computer a penny. I don't like the fact that a good chunk of video content on the Internet might eventually become unavailable to me because of this. That cannot be construed to be good for anyone (except, of course, the MPEG-LA.)

      --
      The higher the technology, the sharper that two-edged sword.
    36. Re:H.264 isn't closed by ScrewMaster · · Score: 1

      The only holds true until 2015. At that stage the terms will change. At this stage we don't know what the new license terms will be, but I'm sure that if H.264 is completely dominating the web then the terms won't be a good, they won't need to be. The current licensing terms are designed with one thing in mind, getting H.264 into a dominant position that can the be taken advantage of at a later date.

      Yes. If there was ever a Slashdot story that needs to be marked "it's a trap!" this is it.

      --
      The higher the technology, the sharper that two-edged sword.
    37. Re:H.264 isn't closed by ScrewMaster · · Score: 1

      If you use H.264, you (potentially, at least) will need to pay its owners a licensing fee.

      In my mind, it's somewhat irrelevant as to whether that's regulated by copyright law, patent law, trademark law, contract law, or the laws of thermodynamics; the upshot is the same. If you are reliant on the owner's permission in order to use a piece of software, then that isn't "open".

      Well, yes and no. In the U.S., you really can't go after users very easily, especially if they bought the product in good faith, having every reason to believe any patented software content was properly licensed. What's would be the point? You won't get much money, and all you'll succeed in doing is make people believe that you're a bunch of complete assholes and that any product containing your patented algorithms is too dangerous to use. You can, however, go after the manufacturer of the product if you believe they're infringing on your patent.

      If MPEG-LA starts going after people who bought H.264-based products who had no idea the product vendor didn't license the codec, they'll be shooting themselves in the foot. Assuming, that is, they're capable of taking the longer view.

      --
      The higher the technology, the sharper that two-edged sword.
    38. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      So I guess these aren't the fixed specification documents: http://www.webmproject.org/code/specs/

      The only thing that sets it apart from any other standard is they haven't gone and asked a standards body like iso to sign off on it, and that means very little really.

    39. Re:H.264 isn't closed by Anonymous Coward · · Score: 0

      I think what you are trying to say is that H.264 is Open but not Free (or free) and that WebM is proprietary but some hope it will be Free (and free) and open source.

      I think that there is every likelihood that WebM will be infringing on some patents the question will be be whether Google can negotiate for them to be free for users (e.g. if they are held by Android dependent companies or if Google just pay for a WW license for everyone).

    40. Re:H.264 isn't closed by LordVader717 · · Score: 1

      And just because something isn't published by a standardization organisation doesn't make it not a standard. WebM is a format for multimedia files. The fact that a variety of independent projects and companies support it makes it a standard format.

  7. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 1

    They certainly make a lot of noise of how they are forming it and how patent holders have been identified. About a press release every three months, and no concrete facts. The pool has been textbook FUD so far.

  8. It's a very real problem by obarthelemy · · Score: 3, Interesting

    The $25-PC Raspberry Pi project is struggling about which codecs to include right. Even at a few bucks or less a codec, that's a huge cost when you try to hit $25 for a functional PC.

    --
    The Cloud - because you don't care if your apps and data are up in the air.
    1. Re:It's a very real problem by guruevi · · Score: 1

      Back in the day, some Linux distro's included them in the non-free repositories maintained outside the US. Why don't we find a legal loophole like that and just let the customer (who usually doesn't have to pay for the license) decide?

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    2. Re:It's a very real problem by slew · · Score: 1

      At less than 100,000 units/year, the H.264 royalty rate is zero.
      From 100,000 to 5,000,000 units/year the rate is $0.20/unit (twenty cents)
      and above 5,000,000 units/year, the rate is $0.10 (ten cents), until the maximum cap amount of $6.5 million/year is paid.

      Source: http://www.mpegla.com/main/programs/avc/Documents/AVC_TermsSummary.pdf

    3. Re:It's a very real problem by obarthelemy · · Score: 1

      I have no clue which other codecs are required and not free. Probably MPEG-2, MPEG-3... I'm guessing the total quickly reaches $1-$3, which is 5-15% of $25 and is, comparatively, a lot.

      --
      The Cloud - because you don't care if your apps and data are up in the air.
    4. Re:It's a very real problem by Anonymous Coward · · Score: 0

      and what about all the other codecs they wish to include?

    5. Re:It's a very real problem by Anonymous Coward · · Score: 0

      I work at a biggish car manufacturer. You would be surprised how much of the total manufacturing cost of the car is due to various licensing fees. The same applies to the consumer electronics market.

      Truth is, everyday consumers end up paying for MPEG-LA licensing fees whether they want it or not. It, and other fees, account for a hefty percentage of the retail price of a consumer electronics gadget.

      So, sure you can pirate the actual software codecs, but MPEG-LAs pocket gets fat anyway through the retail price of the hardware.

    6. Re:It's a very real problem by Anonymous Coward · · Score: 0

      People often do not understand the implication of a few cents multiplied by a few million units.

      It is quite naive to say that 20 cents is irrelevant.
      Sure a big manufacturer would not be bothered with a cost increase of 20 cents per year in TOTAL.

      But a major mobile phone manufacturer probably sells in the order of 10 million phones a year. Even at 10 cents a pop, this means $ 1 million down the drain. Money that otherwise would be either profit or lets say salaries for 15 employees.

      So who is the sucker now? You and 10 of your friends just lost their jobs, all because MPEG-LA charges 10 cents a phone.

    7. Re:It's a very real problem by Anonymous Coward · · Score: 0

      That is only an issue in the US. It'd be very unfair to cripple features only to please 4% of the market.

      IMHO better solutions would be to either make a special US edition (with minimum codec support), or a special price for the US (with the licenses baked in). And let US customers know why their devices is crippled/premium priced.

    8. Re:It's a very real problem by smash · · Score: 1

      Or they could spend the 1 million on codec development to come up with something that isn't half-assed like VP8

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    9. Re:It's a very real problem by ScrewMaster · · Score: 1

      At less than 100,000 units/year, the H.264 royalty rate is zero. From 100,000 to 5,000,000 units/year the rate is $0.20/unit (twenty cents) and above 5,000,000 units/year, the rate is $0.10 (ten cents), until the maximum cap amount of $6.5 million/year is paid.

      Source: http://www.mpegla.com/main/programs/avc/Documents/AVC_TermsSummary.pdf

      For now. As has been said elsewhere, in a few years those terms are going to change, and nobody knows what they're going to be yet. If I were planning on being in business then, I'd seriously consider not using H.264. It's a minefield just waiting to be touched off.

      --
      The higher the technology, the sharper that two-edged sword.
    10. Re:It's a very real problem by ScrewMaster · · Score: 1

      There's no obligation on the authors of MPEG4 algorithms to provide those for free just so that someone can sell a computer with the price capped at $N.

      There was no obligation on the part of our elected officials to make software patentable either. But they did, and they've screwed over a number of industries in the process. Groups like the MPEG-LA are largely parasitic in that the only service they provide is to collect royalties on algorithms whose creators, for the most part, disagree with the entire premise of software patents. And why is that? Well, I'll tell you: it's because those of us in the business recognize that software patents are intrinsically antithetical to our ability to improve upon what is, to advance the state of the art.

      Actually, that applies to patents in general, however the presumption was that without such protection, nobody would invest the capital required to turn an otherwise-worthless idea into a shipping product. Now, maybe that's true in the world of physical invention, where millions (or billions) of dollars may be required to build the necessary physical plant. That's just not true in comparatively fast-paced world of software, where patents are a hindrance, and serve no purpose but to slow the pace of progress. Look around you: the software business has been booming for decades without any patent protection whatsoever: what possible need for them do we have now, if not for the desire of certain parties to control the dissemination of competitive technologies? Furthermore, when did competition become a dirty word?

      I don't know about Europe and other places. I'm an American, and what I do know is that our Constitution is very clear on one point: patents and copyrights are required to promote the useful arts and sciences. That is their purpose. Period. Nothing in there about milking the world for billions of dollars in royalties by providing legal monopolies on mere ideas. Nothing about squelching innovation. And every time I hear about a promising new technology squeezed out of existence by some patent troll (or existing organization who just can't stand the thought of competition) or millions spent on needless, lawyer-enriching, court-clogging litigation I want to throw up. So would the Founders, if they were still with us.

      Keep this in mind: the kinds of people that want software patents are the same kinds of people who have been doing their level best to suppress any form of innovation or technological advancement that they feel threatens their established businesses. Not the kind of people you want in control of progress, at any level.

      --
      The higher the technology, the sharper that two-edged sword.
    11. Re:It's a very real problem by mgiuca · · Score: 1

      Tell that to Mozilla, who ships several million units a year. At the moment it costs absolutely nothing (besides bandwidth) -- you're asking them to pay a few hundred thousand dollars a year just to support basic web standards. And that doesn't consider the free software distros who distribute Firefox / Chromium either. It isn't economically feasible for open source browsers to support this technology.

    12. Re:It's a very real problem by slew · · Score: 1

      At less than 100,000 units/year, the H.264 royalty rate is zero.
      From 100,000 to 5,000,000 units/year the rate is $0.20/unit (twenty cents)
      and above 5,000,000 units/year, the rate is $0.10 (ten cents), until the maximum cap amount of $6.5 million/year is paid.

      Source: http://www.mpegla.com/main/programs/avc/Documents/AVC_TermsSummary.pdf

      For now. As has been said elsewhere, in a few years those terms are going to change, and nobody knows what they're going to be yet. If I were planning on being in business then, I'd seriously consider not using H.264. It's a minefield just waiting to be touched off.

      yes for "now", but if you actually read the link...

      The first term of the License runs through 2010, but the License will be renewable for successive five-year periods for the life of any Portfolio patent on reasonable terms and conditions which may take into account prevailing market conditions, changes in technological environment and available commercial products at the time, but for the protection of licensees, royalty rates applicable to specific license grants or specific licensed products will not increase by more than ten percent (10%) at each renewal.

      So the royalty rate can't go up more than 10% every 5 years until the patents expire (which is 2 more times)... However, if it follows the MPEG2 license, it will probably go down to less than 1/2 the price per unit at each 5 year point, but keep the maximum cap.

  9. What a second... by inject_hotmail.com · · Score: 1

    There have been a bunch of posts so far, and none of them were 1, 2, 3, ???, 4 Profitt?!

    For shame Slashdot, for shaaaaaaame.

    1. Re:What a second... by Anonymous Coward · · Score: 0

      So you're going to meta-post about it instead of creating your own? And I'm going to meta-meta-post about it.

    2. Re:What a second... by Anonymous Coward · · Score: 0

      You can't outmeta my post!

    3. Re:What a second... by ScrewMaster · · Score: 1

      There have been a bunch of posts so far, and none of them were 1, 2, 3, ???, 4 Profitt?! For shame Slashdot, for shaaaaaaame.

      1. Develop efficient video codec.

      2. Patent the Hell out it.

      3. Release to the world under "reasonable" license.

      4. Sue anyone who doesn't comply.

      5. Wait a few years.

      6. Change license agreement.

      7. Sue anyone who doesn't comply.

      8. Profit!!!!

      --
      The higher the technology, the sharper that two-edged sword.
    4. Re:What a second... by inject_hotmail.com · · Score: 1

      There have been a bunch of posts so far, and none of them were 1, 2, 3, ???, 4 Profitt?! For shame Slashdot, for shaaaaaaame.

      1. Develop efficient video codec.
      2. Patent the Hell out it.
      3. Release to the world under "reasonable" license.
      4. Sue anyone who doesn't comply.
      5. Wait a few years.
      6. Change license agreement.
      7. Sue anyone who doesn't comply.
      8. Profit!!!!

      Most excellent! With one exception. I was poking fun at the name quoted (Profitt)...two Ts...I don't think anyone caught that...

  10. WAIT a second... by inject_hotmail.com · · Score: 1

    Alright...and now for the grammar Nazis.

  11. Pretty Much The Standard.. by RevSpaminator · · Score: 1

    Who's implementation of this new standard will define what is considered the standard when people try to conform to the standard? That is to say...who's standard will become the most standard standard?!

    1. Re:Pretty Much The Standard.. by JackAxe · · Score: 1

      LOL!

    2. Re:Pretty Much The Standard.. by ScrewMaster · · Score: 1

      Who's implementation of this new standard will define what is considered the standard when people try to conform to the standard? That is to say...who's standard will become the most standard standard?!

      Usually, most people just settle on the standard one.

      --
      The higher the technology, the sharper that two-edged sword.
  12. Re:Or we could just fix patents and be done with i by Salvo · · Score: 0

    The Patent Pool isn't to kill WebM, it is to protect those who choose to use WebM from litigation.

    Maybe if Apple, Microsoft and Google provided a similar Patent Pool to their mobile developers, for a nominal fee, we wouldn't see all these Patent Trolls. A licence to a patent pool is better than paying Protection Money to a dozen different extortionists.

  13. Re:Or we could just fix patents and be done with i by hedwards · · Score: 2

    And, hopefully FUD is what it will remain. But, as long as they're unwilling to sign over royalty free use for the h.264 pool, then we need to be using something else. It's not acceptable, IMHO, for standards like this to be pay for play.

  14. Atack early, atack often by Graftweed · · Score: 2, Insightful

    The patentability of software is basically flawed and has no place in any knowledge driven economy, but unfortunately this is the reality we're saddled with for the time being.

    Nevertheless, I'm getting pretty tired of companies using software patents as a tactical weapon against competition. If I could introduce a single new law, is that any given company's patent claims would have not be valid unless they were exercised at the earliest possible opportunity. No waiting for years until your competition starts threatening your bottom line before you unleash your army of lawyers. Either they would deplete their resources against every single target out there that may or may not be a threat later on, or they would forfeit any claims they might have.

    Sure, there would be loopholes, and I can think of a few right now, but it would still be fun to watch.

    1. Re:Atack early, atack often by RyuuzakiTetsuya · · Score: 1

      Actually patents and IP law are the basis in which a knowledge driven economy can even work.

      If work you've done could be decompiled and reverse engineered and your competitors can put a product on the shelf that undercuts your price because they didn't have to pay for R&D, then why bother even going to market? That's the end of innovation.

      Yes, what patent trolls like Intellectual Ventures is blatantly wrong, but that's a flaw in the system, not with the patent concept as a whole.

      --
      Non impediti ratione cogitationus.
    2. Re:Atack early, atack often by Anonymous Coward · · Score: 0

      If work you've done could be decompiled and reverse engineered and your competitors can put a product on the shelf that undercuts your price because they didn't have to pay for R&D, then why bother even going to market? That's the end of innovation.

      You suffer from a severe lack of imagination.

      That may be the end of big brand R&D and commercial exploitation but there are plenty of people, hobbyists, open source and academics, who would continue to innovate even if everyone else vacated the marketplace. Not everyone is motivated purely by profit, whether innovation would be slower due to lack of investment or faster due to lack of barriers (see fashion industry) isn't a foregone conclusion.

      Actually patents and IP law are the basis in which a knowledge driven economy can even work.

      In any case, thank you for deliberately conflating copyright, patents and trademarks as though they are somehow the same thing in order to build a strawman. GP talked exclusively about patents, his/her opinion on copyright and trademarks wasn't given.

    3. Re:Atack early, atack often by BitZtream · · Score: 1

      The patentability of software is basically flawed and has no place in any knowledge driven economy

      Without patents, there is no knowledge driven economy. Knowledge is only power if no one else has access to it. As soon as you release software (or hardware for that matter) into the while, its no longer a secret and without patents, you have no power.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    4. Re:Atack early, atack often by wvmarle · · Score: 2

      Software is already well protected by copyright.

      Patents are for hardware stuff. Machines and the like. And they specifically allow for reverse engineering (figuring out how things work), as that advances the general knowledge. Then people inspired by one patented machine may design their own improved machine. With or without other patented bits. Also a patent is designed to be a full disclosure of how a particular machine works: you get your 20 or so years of protection, under condition that you fully disclose how it works. One of the requirements of a patent is that using only the patent a person skilled in the art can build the invention.

      Patents, copyright, trademark rights: all great things, and when developed the "founding fathers" got it right. After that copyright terms were extended to unreasonable lengths, and patents got expanded in areas where they do not belong.

    5. Re:Atack early, atack often by bk2204 · · Score: 1

      There's already a legal term for this. It's called the doctrine of laches. Basically, if you sit on your rights, you lose the right to enforce them. This is designed explicitly to avoid harming others that relied on your inaction.

    6. Re:Atack early, atack often by paulsnx2 · · Score: 1

      Written by someone who obviously has never done any reverse engineering. It just isn't that easy.

    7. Re:Atack early, atack often by Arlet · · Score: 1

      Most software is distributed in binary form, which is hard enough to reverse engineer that patent protection doesn't really add that much benefit.

  15. Re:Or we could just fix patents and be done with i by hedwards · · Score: 1

    Kill WebM, extort money for using WebM, it goes the same way ultimately. As long as people are required to pay for the use of the codec, it can't be in Firefox or any other free browser without somebody infringing on the patent. Which is the problem.

    I was referring to the patent pool that MPEG LA was trying to put together, although in retrospect that was probably not at all clear.

  16. Re:Or we could just fix patents and be done with i by EdZ · · Score: 4, Insightful

    a standard that requires licensing fees

    Only in the US. In places where software patents are a load of hogwash (e.g. europe) h.264 and VP8 are equally open.

  17. Shameless Ad by phizi0n · · Score: 2

    The battle between h.264 and Theora has existed for over a year and this article doesn't add any new insight to the table. The OP is full of name dropping and was submitted by someone at IT World but doesn't even throw in a "full disclosure" statement. We get it, Brian Proffitt wrote a stale article for you and your buddy Soulskill hooked you up again...

    1. Re:Shameless Ad by icebraining · · Score: 1

      Frankly, I agree. What is here to talk about? It's just a rehash of the same old and tired discussion.

    2. Re:Shameless Ad by phizi0n · · Score: 1

      I should have said the battle between h.264 and open standards for the video tag spec. On one hand you've got some companies wanting h.264 because of hardware support for it and because they have patents in the spec, on the other hand you've got companies that believe an open standard (html5) should promote other open standards. In the end, they seem to have compromised on leaving codecs out of the video tag spec but that means that websites will probably continue to encode in h.264 and use Flash to play it except on Apple's devices where they'll have to use the video tag.

      Btw, thanks for completely ignoring the point of my original post.

    3. Re:Shameless Ad by Anonymous Coward · · Score: 0

      I probably don;t really know what I'm talking about, but to this monkey it seems well time for video codecs to move to graphics chipset, where we can forget about them. Unless I'm mistaken this is one of the reasons Jobs was adamant about not allowing flash, because video decoding should be handled in hardware not some inefficient software plugin.

    4. Re:Shameless Ad by phizi0n · · Score: 1

      Flash does make use of hardware decoding. Steve Jobs is just a control freak.

    5. Re:Shameless Ad by ScrewMaster · · Score: 1

      Flash does make use of hardware decoding. Steve Jobs is just a control freak.

      Yes. On one of our Ubuntu machines is regularly used for viewing Youtube videos. I discovered the "hardware acceleration" option because there's a bug in it where the display goes monochrome when in full-screen. Go back to windowed, and it works fine. If I turn off hardware support, full screen shows color. Weird.

      --
      The higher the technology, the sharper that two-edged sword.
  18. Re:Or we could just fix patents and be done with i by Riceballsan · · Score: 1

    Which works great, as long as you have no intention of ever releasing your website or program on a international level.

  19. You forgot - MS wants to eliminate plugins.. by Anonymous Coward · · Score: 0

    You forgot - MS wants to eliminate plugins in Windows 8.

    No plugins, then no plugin for open codecs.

    1. Re:You forgot - MS wants to eliminate plugins.. by Anonymous Coward · · Score: 0

      I don't suspect that the lack of plugins will bode well for IE's market share.

    2. Re:You forgot - MS wants to eliminate plugins.. by Anonymous Coward · · Score: 0

      Surely MS can find the money to license H.264, so no need for any plugins there.

    3. Re:You forgot - MS wants to eliminate plugins.. by aaron552 · · Score: 1

      Even in that case, given that IE uses DirectShow for HTML5 video, you'd just need to install a WebM or Theora DirectShow filter (like ffmpeg) and it would work in IE.

      --
      I had a sig once. It was lost in the great storm of '09.
  20. Theora? by Anonymous Coward · · Score: 0

    Why would anyone still use Theora? VP8 is twice as good in terms of compression : quality. The development of Ptalarbvorm also seems a bit stalled, I guess they themselves don't see much sense in it anymore.

  21. Re:Or we could just fix patents and be done with i by Lunix+Nutcase · · Score: 1

    Except for the fact that there are already websites and programs that are international that use patented software but don't pay royalties?

  22. Jpg and gif by Anonymous Coward · · Score: 0

    It's like the old days where gif died cause cmpuserve owned it

    1. Re:Jpg and gif by mat+catastrophe · · Score: 1

      Yea, gifs are totally dead.

      senorgif.com

      --
      sig not found
    2. Re:Jpg and gif by ScrewMaster · · Score: 1

      It's like the old days where gif died cause cmpuserve owned it

      It wasn't Compuserve that caused all the hate and discontent. It was Unisys that was making threats and trying to get royalties. Compuserve didn't sue anybody, didn't demand anything from anyone. In fact, I believe they were Unisys' first target.

      --
      The higher the technology, the sharper that two-edged sword.
  23. Re:Or we could just fix patents and be done with i by Grishnakh · · Score: 0

    What are you talking about? Software patents are fully legal in Europe:
    http://www.eweekeurope.co.uk/news/german-court-declares-software-patents-legal-7211

  24. I'm really pissed about this whole mess. by Anonymous Coward · · Score: 0

    3 years ago I bought a car radio which plays ogg. Life was beautiful because the sound is better for the same file size vis-à-vis the mp3 alternative.

    By that time I learned about insinuations about radio makers not advertising ogg support due to fears of being sued for patent violation -- which the ogg people firmly denied, citing that since the ogg codec existed for more than 10 years, obviously it didn't violate any patents -- or else someone would have already complained.

    Now history repeats with video. A lot of smearing free solutions and veiled threats about (hidden) patents and companies prefering to settle rather than litigate.

    Meanwhile we consumers cannot get the better sounding solution, but must use what pays someone bills. That sucks.

    1. Re:I'm really pissed about this whole mess. by Anonymous Coward · · Score: 0

      Better sound from Ogg Vorbis for the same file size as MP3? *snort* you need to come clean the coffee off my monitor, I haven't laughed that hard in quite a while. I tried, I really tried, to get behind Ogg, but in side-by-side comparisons the sound quality was terrible. Warbly and artificial. Deity help you if you listened to solo acoustic or classical. Sorry, but I am a consumer, I want the better technology, and if it works in my devices, and well, that's what I will support (and purchase).

    2. Re:I'm really pissed about this whole mess. by Teancum · · Score: 1

      If you don't want to worry about patents, stick with MPEG-1 video. It does a pretty good job, both software and hardware implementations are ubiquitous, and you have test data of almost anything you would like.

      Ogg Theora is nearly as old as Ogg Vorbis, although its adoption has been much slower in part because MPEG-1 has been available to fill in any niche application that might have used it.

      Yes, compression on MPEG-1 stinks compared to some of the newer codecs. That is what you pay for with the new fangled formats. Also.... don't buy into the BS that you can't have 1080p video with MPEG1, as you most certainly can. The difference is strictly the compression levels... and possibly an implementation which can handle that much data.

    3. Re:I'm really pissed about this whole mess. by Anonymous Coward · · Score: 0

      Have a link, son, and educate yourself.

    4. Re:I'm really pissed about this whole mess. by mat+catastrophe · · Score: 1

      Yea, that last line about "outdated results" really beefs up your point, there.

      --
      sig not found
  25. No more than 100,000 people by tepples · · Score: 1

    Good luck making sure that no more than 100,000 people receive a copy of your program. That's even fewer people than, say, Jehovah's Witnesses think will go to heaven.

    1. Re:No more than 100,000 people by BitZtream · · Score: 1, Interesting

      As a software developer, I'm generally happy when my 'problem' is that I have to start paying royalties because my software has hit 100k users.

      I don't know about what sort of ultra-awesome-kickass programmer you are, but by the time most of us start selling 100k units/year we've got enough accountants involved that dealing with MPEG-LA licensing is a drop in the bucket.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    2. Re:No more than 100,000 people by syockit · · Score: 1

      Let's say I want to develop software, which uses AVC, for free distribution. Do I still have to pay?

      --
      Democracy is for the people; you only vote once per season and we'll do the rest of the work for you don't have to.
    3. Re:No more than 100,000 people by Anonymous Coward · · Score: 0

      It depends.

      If your software simply streams pre-recorded AVC, you don't have to pay as there are no royalties for streaming AVC over the internet (this was made free until the patents expired by the MPEG-LA group).

      If your software actually encodes or decodes AVC, life is a bit more complicated.

      From a strictly legal point of view, you don't infringe on patents by writing the code, only by using the code, so it is your users that would be infringing (if the patent holders cared at all), but technically you may be contributing to their infringement depending on how they use your product but since they got it for free from you that point is debatable.

      Of course from a technical point of view, you should get the license offered by MPEG-LA which allows your users to legally use AVC codecs to encode for personal or internal non-distribution purposes w/o having to pay. If you distribute less and 100,000 copies/year of your free software, then it's still free (meaning you don't pay).

      On the other hand from a practical point of view, if you don't actually sell your software (e.g, it is distributed freely like say libx264), you are likely under the radar regardless of how many copies you don't sell (e.g., give away for free) especially if you don't actually keep track of how many copies over 100,000 copies per year you are distributing.

    4. Re:No more than 100,000 people by E+IS+mC(Square) · · Score: 1

      Wtf is modding this asshole insightful?

    5. Re:No more than 100,000 people by ScrewMaster · · Score: 1

      Wtf is modding this asshole insightful?

      I don't think he's an asshole, I just think he hasn't thought this all the way through.

      --
      The higher the technology, the sharper that two-edged sword.
  26. Re:Or we could just fix patents and be done with i by Meneth · · Score: 2

    That's only Germany, and the final legality of that declaration is still unclear.

    The European Patent Convention clearly excludes computer programs from patentability, as seen in Article 52 (2) c.

    However, the European Patent Office has flatly ignored this paragraph, and granted many software patents.

    The debate continues.

  27. Computational complexity by tepples · · Score: 1

    Why would anyone still use Theora? VP8 is twice as good in terms of compression : quality.

    What's the relative computational complexity of decoders for the two formats? I've been told Theora is comparable to MPEG-4 Part 2 (e.g. DivX) and VP8 is comparable to H.264. When trying to play back video on existing hardware, such as a video game console, it helps to know that you can hit the 24 fps target without overheating.

    1. Re:Computational complexity by ScrewMaster · · Score: 1

      it helps to know that you can hit the 24 fps target without overheating.

      True, and for even lower-powered devices (those with ARM processors like cell phones and tablets) heating and battery life become an issue. As the mobile market continues to grow, the computational efficiency of codecs will be an issue, even if you have hardware support.

      --
      The higher the technology, the sharper that two-edged sword.
  28. Re:Or we could just fix patents and be done with i by Caesar+Tjalbo · · Score: 1

    a standard that requires licensing fees

    Only in the US. In places where software patents are a load of hogwash (e.g. europe) h.264 and VP8 are equally open.

    You're still paying for it when you purchase a gadget with the codec.

    --
    "I'm not much interested in interoperability. I want substitutability. I want to be able to throw your software out."
  29. Re:Or we could just fix patents and be done with i by Grishnakh · · Score: 1

    Hmm... that sounds like the US: having a law on the books but blatantly ignoring it.

  30. Re:Or we could just fix patents and be done with i by warrigal · · Score: 1

    Is anybody behind these "free" codecs willing to indemnify the implementers against submarine patents that surface once the codecs gain enough market-share to be worth litigation? There's no way anyone can know if Ogg, Theora, WebM etc are not infringing (or can be alledged to infringing) somebody's IP until it's tested in court. And even then... I note that Apple has been to bat for its developers against patent trolls. Anyone else?

  31. Re:Or we could just fix patents and be done with i by sg_oneill · · Score: 4, Informative

    Have you any idea how these pirates work? MPEG-LA is not a charity, its a business with an extremely predatory model. Collect patents together and then try and collect rent from developers.

    If WebM needs protection, google will protect it. Nobody is asking MPEG-:LA to pool patents to sieze licencing rights to something they didnt invent (They didn't invent ANYTHING they licence out by the way, MPEG-LA is not MPEG. They just exploit the fact you cant trademark acronyms).

    Patent pools are incompatible with free/open source. If someone forces mozilla to licence a patent, guess what only mozilla can use that code and its not free software no more. If parents cover webkit, its not free software no more.

    We might well end up with a scenario that the only browsers distributable with linux are those without video.

    A world without firefox, VLC , and so on is a world without free access to user created content, and that ultimately is a spike in the heart of free speech.

    --
    Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
  32. Re:Or we could just fix patents and be done with i by node+3 · · Score: 0

    As long as people are required to pay for the use of the codec, it can't be in Firefox or any other free browser without somebody infringing on the patent.

    Firefox can use patented codecs (like H.264 and WebM) just fine. You mentioned FUD before, but what exactly do you call your false claims?

  33. Old news is *SO EXCITING* by bersl2 · · Score: 1

    derp

  34. Taking the long (long) view? by Dutch+Gun · · Score: 1

    Sigh... I'm not very optimistic about the software patent situation. The only bright spot is the very long view. Companies are patenting absolutely anything they can get away with right now. While this poses a problem for short term software development, I wonder if this will have ramifications for long term development. That is... once all the "core technology" patents have expired, they'll be free to use henceforth.

    There are likely natural limitations to how much audio or video data can be compressed. Once these patents expire, it will probably occur at a point in time when any incremental advancements in the next codec don't render enough of an advantage given the likely increases in network speeds. I think we've already hit that point with audio encoding - for nearly everyone, mp3 is now good enough and small enough that more sophisticated codecs don't really matter anymore, even if they marginally improve compression/quality ratios.

    Scant comfort, I know, as 17 years is a hell of a long time to wait for things to be freed up. Still, it's nice to know these companies won't have an eternal lock on these methods.

    --
    Irony: Agile development has too much intertia to be abandoned now.
    1. Re:Taking the long (long) view? by russotto · · Score: 1

      While this poses a problem for short term software development, I wonder if this will have ramifications for long term development. That is... once all the "core technology" patents have expired, they'll be free to use henceforth.

      Wrong; they'll just patent them again with slightly different wording or "...on the latest shiny toy". Sure such patents are crap, but no one has the resources to fight them all.

    2. Re:Taking the long (long) view? by Dutch+Gun · · Score: 1

      Maybe, but as patents get more specific, they also become less relevant. Sounds like you're even more jaded than I am. I hold out some hope, because we've already seen patents such as LZW expire, and (at least to my knowledge), no one has been able to patent it again with "slightly different wording". The system is bad right now, but I don't believe it's that completely corrupt yet.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    3. Re:Taking the long (long) view? by russotto · · Score: 1

      Maybe, but as patents get more specific, they also become less relevant.

      At best, that just means that everything old becomes new again when a new underlying technology comes along. Consider patents "... on an IPV6 network", or "on a display with a dot pitch of less than 0.08mm". At worst, they get the narrow patent but enforce it broadly, depending on courts and juries to wave away the fine distinctions without realizing those were the only things making the inventions "novel" in the first place.

      Maybe, but as patents get more specific, they also become less relevant. Sounds like you're even more jaded than I am. I hold out some hope, because we've already seen patents such as LZW expire, and (at least to my knowledge), no one has been able to patent it again with "slightly different wording". The system is bad right now, but I don't believe it's that completely corrupt yet.

      LZW was patented at least twice; the Unisys patent was the later of the two. It won't be patented again for two reasons: it's too well known and it's so specific that one could actually use publicly-available code from before any subsequent patent to implement it.

      Other stuff, though... Apple patented a menu system "on a portable media player", and Microsoft had the cheek to patent something "on a limited resource computer device" which had been done on computers when computers had fewer resources than the PDAs they were referring to.

  35. Re:Or we could just fix patents and be done with i by visualight · · Score: 3, Insightful

    If you want to 'take the moral high ground' to the extreme, then you just have to recognize that there are going to be plenty of times when you don't get your way because no one else cares about your irrational response to what you perceive as a problem in the natural order of things.

    This will not be one of those times. Also, you're wrong about everything else, particularly your attempts to redefine open and paint anyone who disagrees with you as a cult member. You're delusional if you think you're litany changes the fact that software patents are the opposite of open.

    --
    Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
  36. Re:Or we could just fix patents and be done with i by a_n_d_e_r_s · · Score: 4, Informative

    || Patent pools are incompatible with free/open source.

    |I'm sorry, thats flat out false is most ways.

    Actually its very true.

    You, mine friend, need to learn how patent pools work and how it stops anyone from freely distribute the code using GPL.

    http://www.gnu.org/philosophy/stallman-mec-india.html

    Given that GPL is the most used license for open source software - patent pools are very bad.

    --
    Just saying it like it are.
  37. Re:Or we could just fix patents and be done with i by Teancum · · Score: 2

    It has nothing at all to do with 'open', well if it does, its only in that the MPEG-LA license is pretty much the definition of open license. It also has nothing at all to do with 'Free as in speech', it does however have something to do with 'free as in beer'. The open part may not be what you define open as, but it fits pretty accurately for everyone not part of the RMS cult.

    I don't know where you get this impression, as the MPEG-LA isn't really even "free as in beer".... or at least you need to check their licenses out a little better before you make such statements.

    The problem is that the royalties are sent downstream, and represent barriers to entry in the form that developers of products have a minimum price they must sell software or devices simply due to how the licensing scheme is set up. It is also a protection racket where content authors or even patent holders (in the case of MPEG-LA royalties) almost never get anything from the money collected. Most of it goes into the overhead of simply operating the MPEG-LA.

    If you are selling a high-end audio editing software suite or a commercial MP3 player, the royalty payments for the MPEG-LA really are inconsequential.... but they aren't free.

    Most significantly, their licensing terms are completely incompatible with something like an "open source" software project, particularly with the GPL. It isn't so much that the GPL or "open source" licenses are explicitly prohibited, but that the royalty collection system simply isn't in place for that kind of software or product. Even building an MP3 player or a hand-held computer with video playback with an Arduino home-brew kit where you publish the source code and schematics is incompatible with anything under the terms of the MPEG-LA.

    Simply put, you can't call that an "open license" other than it doesn't discriminate against multi-national companies wishing to produce commercial products using formats claimed under licenses offered by the MPEG-LA. They are no different than ASCAP, but then again I'm not a big fan of that organization either.

  38. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 1

    Is anybody behind those standard codecs willing to indemnify the implementers against submarine patents that surface once the codecs gain enough market-share to be worth litigation?

  39. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 0, Informative

    And I can smash newborns' heads with my bare fists just fine, that doesn't mean it's legal.

    You want to play video with patented encoding, you need to have licensed codec somewhere in the line from browser and plugins to OS shared codecs, and someone needs to pay for that license.

  40. i don't get the whole h264 fiasco by sixsixtysix · · Score: 1

    i understand it is mpeg la's ip. some hardware/software is licensed to decode it. other hardware/software is licensed to encode it. how is it different than every other codec?

    --
    ...
    1. Re:i don't get the whole h264 fiasco by Red_Chaos1 · · Score: 1

      Well, theoretically, if hard/software folks didn't have to pay licenses and royalties for the tech, then they could sell the soft/hardware cheaper, for one.

    2. Re:i don't get the whole h264 fiasco by KingMotley · · Score: 1

      Yes, everyone would pay $.001 per copy cheaper. I'll give mozilla a penny if they include it, think they have change?

  41. Re:Or we could just fix patents and be done with i by Curunir_wolf · · Score: 1

    Oh, the situation with MPEG-LA is worse than that. If you capture video on any kind of MPEG camera, even high-end "professional" models, you've now got a video that is encumbered and you can't use it for ANY commercial purpose without a license from MPEG-LA.

    --
    "Somebody has to do something. It's just incredibly pathetic it has to be us."
    --- Jerry Garcia
  42. Re:Or we could just fix patents and be done with i by sjames · · Score: 5, Insightful

    The Patent Pool isn't to kill WebM, it is to protect those who choose to use WebM from litigation.

    Spit that cool aid out fast! They cannot possibly protect from litigation, only accept payments to not litigate themselves. Anyone who chooses not to toss their patent into the pool can still crawl out from the woodwork at any time (for mpeg, vp8, or anything else).

    MPEG-LA's pool has one purpose and one purpose only. It is a desperate search for anything they can use to screw people who choose to avoid their fees on mpeg and h.264.

    There are two codecs out there (theora and vp8) that are freely licensed and that pisses them off. Keep in mind that when MPEG-LA claims all codecs are covered by patents, it's a combination of propaganda and wishful thinking on their part. They have so far failed to produce one that covers theora or VP8 (and they have certainly been looking). Their stated mission is to find a way to poison the well so they can sell bottled water.

  43. Just make both available! by micronicos · · Score: 1

    Videopress, the video hosting arm of Wordpress, offers main video encoding in h.264 & also an Ogg Theora view or download option, both are available.

    If you have a free Wordpress.com blog, you can buy Videopress & once you've uploaded your video to the Wordpress Blog, play the stream in any other web site with a Flash player. Gets around the Youtube 15 minute limitation as well.

    --
    Nico M, London, GB.
  44. Re:Or we could just fix patents and be done with i by rsborg · · Score: 1

    The Patent Pool isn't to kill WebM, it is to protect those who choose to use WebM from litigation.

    Sure, but protection from whom? From themselves perhaps?

    'The president of the FFII has brought to people’s attention this good report from The Prior Art blog, saying that “MPEG-LA’s CEO Larry Horn also heads MobileMedia, a patent troll holding no less than 122 patents bought to Nokia and Sony” '

    --
    Make sure everyone's vote counts: Verified Voting
  45. Re:Or we could just fix patents and be done with i by fusiongyro · · Score: 1, Interesting

    Normally this situation is pretty cut and dry. Unfortunately, the problem here is that H.264 is substantially better technology than WebM, it's not clear that WebM is not trampling on MPEG-LA patents, Google is not indemnifying WebM users against it, and Ogg Theora is noticeably worse than WebM.

    I am obviously in favor of eliminating software patents, and thereby eliminating the problem of patent trolls like MPEG-LA. I am also obviously in favor of open standards. But this is not like most software where we can just round up some of the gang and knock out a new better thing in a few weeks. There are not a lot of people who can design a modern, performant, high-quality video codec, open source or no (notably, both Google and Xiph have managed to do a shitty job). To do so within our legal constraints really might be asking too much.

    Since it looks like we don't get to live in the world we want to live in, we have to ask ourselves which of the worlds we can have we would like. I don't relish the idea of having inferior technology foisted on me any more than the idea of closed standards. But it's looking like we're going to have to pick one, and I don't think when it comes down to it I'd rather have the inferior technology.

  46. Re:Or we could just fix patents and be done with i by DrXym · · Score: 1

    As long as people are required to pay for the use of the codec, it can't be in Firefox or any other free browser without somebody infringing on the patent. Which is the problem.

    Video shouldn't have to be in the browser. Every modern OS has a perfectly usable media framework for apps to use and in the vast majority of cases it already contains an H264 codec or permits one to be obtained.

  47. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 0

    I love how the GP says:

    "but it fits pretty accurately for everyone not part of the RMS cult"

    And you retort by linking to a RMS rant.

  48. When MPEG-LA whips the llama's ass by tepples · · Score: 1

    On the other hand from a practical point of view, if you don't actually sell your software (e.g, it is distributed freely like say libx264), you are likely under the radar regardless of how many copies you don't sell

    Even for a product comparable to, say, Winamp?

  49. Apple "only" supporting h.264? by jo_ham · · Score: 1

    According to the HTML5 test page, Safari (on OS X) supports WebM as well as H.264.

    This may be different on iOS of course, due to decoding issues.

  50. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 0

    In places where software patents are a load of hogwash (e.g. europe)

    Sadly that is not 100% true. While software patents should not exist in europe you can still patent a system containing software designed to run on some broadly specified piece of hardware. So the software itself is not patented but you cant run it on a device with, for example, at least 3mb memory and a cpu without infringing on the patent (there was a court case about one of microsofts FAT filesystems a while back using this logic).

  51. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 0

    He is writing whatever master Steve Jobs wants. After all, he is Jobs' bitch.
    Anyway. The point is that do not expect rational discussion with somebody like him or other apple fanbois.

  52. right by smash · · Score: 1

    So given all my media is already in h.264 when it comes off the device, what's the rationale behind getting it in webM/vp8 without any proprietary license? Never mind that h.264 is technically superior and has hardware support in all my devices, and webM is open to being shafted due to patent infringement...

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  53. Re:Or we could just fix patents and be done with i by Tomato42 · · Score: 1

    Thankfully, out judges and politicians are still learning this Art.

  54. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 0

    In places where software patents are a load of hogwash (e.g. europe) h.264 and VP8 are equally open

    Guffaw. The problem with your logic is that codec patents aren't software patents. Maybe you should actually look at the list of patents.

  55. Re:Or we could just fix patents and be done with i by maxwell+demon · · Score: 1

    Why is it that its okay for Mozilla to have restrictions on their code and require conditions of a license to be met, but its not for MPEG-LA?

    If you don't want to use Mozilla, you are free to use another browser, without any averse effect. But if H.264 becomes the standard video on the Web, you cannot just choose another format. Providers can't because people likely will not have that other codec installed, and possibly cannot even install it. Users cannot, because if a video is H.264, there's no way to watch it except with a H.264 codec. You cannot even write your own H.264 codec without a license, because unlike copyright, patents also cover clean-room reimplementations.

    --
    The Tao of math: The numbers you can count are not the real numbers.
  56. Re:Or we could just fix patents and be done with i by Pinky's+Brain · · Score: 1

    Apart from Microsoft there is no one who offers indemnification, not Apple (they offered to pay legal fees in the Lodsys case, which is something entirely different) and certainly not MPEG-LA ... a WebM developer is as safe from litigation as a H.264 developer in the end, in both cases they are protected by the commercial interest of the parties behind the standards without any outright guarantees.

    As for whether it's clear that WebM is not trampling in MPEG-LA patents ... over a year without a single patent number being mentioned is clear enough for me.

  57. I'd first have to leave the USA by tepples · · Score: 1

    Perfect solution: ignore the USA

    In order to ignore the USA, I'd first have to leave the USA. Which country do you recommend, and how should I qualify for lawful resident status?

  58. Re:Or we could just fix patents and be done with i by makomk · · Score: 2

    It'd actually be very surprising if WebM did infringe any MPEG-LA patents; it was carefully designed to avoid doing so, and this shouldn't be that hard to do because a lot of the patents in question are very narrow. The reason they're so narrow is that because of the MPEG standards body's stance of patent-neutrality, the original patent holder can submit technologies to the standard that infringe on their patents and the MPEG Group won't modify them to work around the patents no matter how trivial it is to do so. Narrow patents are more easily defended against prior art, hence most of them are just broad enough to catch all standards-compliant implementations.

  59. Re:Or we could just fix patents and be done with i by OeLeWaPpErKe · · Score: 1

    3 things :

    1) linux doesn't (well, not a legal one anyway). It's not free.
    2) neither does windows xp
    3) even in the cases where such is provided, they're like all other "standard" implementations : incompatible

  60. Re:Or we could just fix patents and be done with i by OeLeWaPpErKe · · Score: 1

    In fairness ... you might list the full steps from the MPEG-LA's business plans. It goes like this :

    1) bring together experts, implementors (on their payroll), testers, ..., and negotiate for years with all sorts of different companies and government agencies until you have enough investment to get a quality video compression format
    2) publish all the products of step 1 openly, for everyone to read and use. Write books about it (yes, plural, we're talking dozens)
    3) profit

    Step 3, the "predatory" part, is kind of a necessity for this whole thing to work ... And you could just as well argue that people using this product without compensating MPEG-LA is just as predatory. H264 is something that you don't write in an afternoon (or with 100 developers in a year's time, for that matter).

  61. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 0

    Seriously, I'd LOVE to see Firefox linked against libx264 for HTML5 video, but that just isn't going to happen until this patent malarkey gets fixed. If this shit went away, everyone could go back to to H.264 support and we could consign WebM and Theora to the "open, but not useful" bin of history.

  62. The *did* develop h264, and (partly) WebM ... by OeLeWaPpErKe · · Score: 1

    MPEG-LA did invest kind of a huge amount of money to create h264 in the first place. WebM, is partly based on that work. Work which was shared, but not freely shared. See here for example, note what software is used for WebM decoding : http://en.wikipedia.org/wiki/VP8#Encoding.

    So what's the big deal here ? MPEG-LA advanced the state of the art in compression codecs, by a lot, and they invested money in that project. How is it unfair of them to expect compensation from people using that work, whether that is through using WebM or h264 ?

    Anyway, the point is moot, since anything that needs video codecs still needs h264. Only when that changes (which won't be until blue-ray is forgotten in the dustbin of history) will there be a problem : if you buy a license for your software to decode h264, you're perfectly welcome to use that same license for WebM as far as MPEG-LA is concerned.

    1. Re:The *did* develop h264, and (partly) WebM ... by sjames · · Score: 1

      Firstly, MPEG-LA has nothing to do with the development of ffmpeg. Second, you're confusing a framework for the actual codec.

      There's no mystery who developed vp8 (pro tip: it's in the link you referred to). MPEG-LA isn't it. There's no mystery who developed Theora either, also nobody in MPEG-LA. MPEG-LA are just trying to steal someone else's IP.

      Thus far, other than mumbling that there must be some patent in their portfolio that's relevant to theora and vp8, they have nothing. The code is out there and they've had plenty of time and motivation to examine it. They have yet to name a single patent in their vast portfolio that is at all relevant to either codec.

    2. Re:The *did* develop h264, and (partly) WebM ... by OeLeWaPpErKe · · Score: 1

      Are you really going down this road ? What you're saying is akin to "mathematics has nothing to do with building a computer", with the argument probably being that there are no mathematicians on the factory floor. Same with a codec. In the same way MPEG-LA has a LOT to do with ffmpeg development. You cannot just sit down and develop a better codec.

      First you develop a lot of principles you can use, and describe their properties purely theoretically. Then you pay a lot of developers to try to combine those in hundreds of ways until you find a few good ones. This requires actual decent developers with solid theoretical knowledge and years of experience. You know, the kind google complains regularly turn down $200k/year offers. Then you publish the result, various kinds of example code, encoders, good decoders, bad (but fast) decoders... subsequently patenting all this stuff.

      No offence, but h264, and the stuff based on it, is pretty close to how the patent system is supposed to work. You do a lot of theoretical work, then publish it for free and for anyone to learn from. But if they want to build stuff with it, that requires they pay you for your work, for a limited time. MPEG-LA seems to me a very good example of the patent system used to accomplish a very worthy goal.

      MPEG-LA is not a patent troll. Their patents are not obvious, they're not copies of academics' work, they're not even bought from other parties. They actually worked long and hard on finding all this stuff before they patented it. Why are they not entitled to payment for their work ? Nobody is stopping you from finding and using *other* principles and combinations to implement a codec (which is not what vp8 developers did, so yes MPEG-LA will require payment for users of VP8 as well, which seems perfectly fair to me).

      The simple truth is that without MPEG-LA and their investments we would not have video codecs half as good as h264. Nor would be have vp8 or theora codecs. In my book that entitles them to get their investment back and a tidy profit on top of that.

    3. Re:The *did* develop h264, and (partly) WebM ... by sjames · · Score: 1

      You DO realize that ffmpeg is a piece of software that implements a number of codecs, right? That it was not written by the people who developed the codecs? That the mere inclusion of another codec in a 3rd party framework doesn't somehow merge them conceptually?

      For example, Gnome is a framework. Not all Gnome programs are the same program, just because they have been wrapped in the same framework and may appear in the same menu.

      I'll repeat it for you, MPEG-LA holds not one single patent that is relevant to VP8 or to theora. They made no contribution to either codec. The codecs would exist with or without them. They would really like for us to believe otherwise, yet cannot point to any patent in their portfolio that would lend credence to the claim. If they were honest businessmen and had such a patent, they would name it.

      MPEG-LA has been slapped in court on more than one occasion for fraudulently slipping non-essential patents into the essential patent pool. They are now busy spouting FUD with no backing evidence. They demand royalties for streaming mpeg video even if no encoding or decoding is involved and they didn't develop any software or techniques involved in internet streaming.

      I never claimed they shouldn't profit from their own hard work, just that they shouldn't try to steal the profit from other people's hard work. Fact is, there exist codecs other than theirs, they're not the only smart people on the planet. It just ticks them off because they might face the reality that good enough and free might beat out better but costs and that as long as good enough and free exists, better can only be priced so high.

      How much are they paying you anyway?

    4. Re:The *did* develop h264, and (partly) WebM ... by OeLeWaPpErKe · · Score: 1

      Let me just say this :

      Finally, the problem of patents appears to be rearing its ugly head again. VP8 is simply way too similar to H.264: a pithy, if slightly inaccurate, description of VP8 would be “H.264 Baseline Profile with a better entropy coder”. Even VC-1 differed more from H.264 than VP8 does, and even VC-1 didn’t manage to escape the clutches of software patents. It’s quite possible that VP8 has no patent issues, but until we get some hard evidence that VP8 is safe, I would be cautious. Since Google is not indemnifying users of VP8 from patent lawsuits, this is even more of a potential problem. Most importantly, Google has not released any justifications for why the various parts of VP8 do not violate patents, as Sun did with their OMS standard: such information would certainly cut down on speculation and make it more clear what their position actually is.

      Read the article (there's about a page's worth of text in there about patents, including specific processes. It convincingly tears the notion that VP8 is independant from h264 to shreds), this guy's done a lot of research into this :

      http://x264dev.multimedia.cx/archives/377

    5. Re:The *did* develop h264, and (partly) WebM ... by sjames · · Score: 1

      In other words, a 3rd party has CONCERNS that MPEG-LA may be able to swipe the sweat right off of the developer's brows due to accidental similarities.

      Of course, that was written before MPEG-LA spent a year and a half trying and apparently failing to come up with a specific patent that is actionably infringed. I have an advantage of hindsight not available to the author of that article at the time.

    6. Re:The *did* develop h264, and (partly) WebM ... by SiChemist · · Score: 1

      Not to mention the fact that the developer in question works on a H264 implementation and has a vested interest in people choosing H264 over VP8/WebM

    7. Re:The *did* develop h264, and (partly) WebM ... by OeLeWaPpErKe · · Score: 1

      In other words, a 3rd party has CONCERNS that MPEG-LA may be able to swipe the sweat right off of the developer's brows due to accidental similarities.

      Have you looked at the math behind it ? Accidental similarities is not a very good defense if they're 90% identical, with including at least 3 operations that were, as far as I can tell, invented (from zero) for h264 (and thus effectively owned by MPEG-LA). There is *no* original step in VP8, as far as I can tell. The things they didn't copy from h264 they copied from apple, although the actual path would more likely be apple -> academic papers -> vp8.

      Oh and one of the steps VP8 added was actually suggested by MPEG-LA in the standard, in the "avenues for further research" section, with a link to a paper describing exactly what they did.

      Let's not pretend this is anywhere near a doubtful case : it's not. MPEG-LA did >90% of the development work that was needed to bring VP8 into the world. Which is probably why VP8 was developed by 6 people where the MPEG-LA needed hundreds.

  63. Shocked to my foundation by nightcats · · Score: 1

    God, how utterly shocking: the only winners from a new technology are lawyers. My world will go half deaf from being thus turned onto its ear.

    --
    Development is programmable; Discovery is not programmable. (Fuller)
  64. Have I been wrong all these years??????? by Anonymous Coward · · Score: 0

    I thought, in VERY general terms:
    x264 was to h.264 as
    Xvid was to divX.....
    open source >>> proprietary

  65. Re:Or we could just fix patents and be done with i by Vanders · · Score: 1

    Is the MPEG-LA willing to indemnify H.264 licensees against non-MPEG-LA submarine patents that surface? No. So why the double-standards?

  66. Re:Or we could just fix patents and be done with i by Aighearach · · Score: 1

    Given that GPL is the most used license for open source software

    Most OSS uses some sort of BSD-style license.

  67. Re:Or we could just fix patents and be done with i by DrXym · · Score: 1
    1. It's perfectly legal in most non US countries and not beyond the realms of possibility that commercial dists sell a codec pack for a few dollars.

    2. DiVX amongst others offers a H264 codec for nothing. Perhaps if demand for a Linux codec were so great they'd even supply one of those.

    3. There are very precise definitions of what H264 should do at various profiles and levels. If a particular codec didn't meet those requirements it could be blacklisted.

    I have no objection to VP8 being the "default" codec but to artificially deny other codecs even when they're sitting right there in the OS is absurd. Especially H264 which is the defacto format for hardware devices and will continue to be regardless of VP8 or not.

  68. Re:Or we could just fix patents and be done with i by Vanders · · Score: 1

    it's not clear that WebM is not trampling on MPEG-LA patents, Google is not indemnifying WebM users against it

    It's also not clear that H.264 is not trampling on Goole (On2) patents and MPEG-LA is not idemnifying MPEG-LA licensees against it (or anyone else) either. So what's your point?

  69. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 0

    So, reverse engineer H.264, open sorcerers.

  70. What's so hard about using multiple browsers? by WebManWalking · · Score: 1

    Many tools for the same job. Blocked here, circumvent there, get everywhere you want to go. Outta my way, only-one-way-to-do-things developers. On the web, I'm in charge.

  71. Re:Or we could just fix patents and be done with i by Lord_Jeremy · · Score: 1

    Indeed, the arguments against open source browsers using system frameworks or codecs for non-free formats just don't hold water. I feel the main reason Mozilla refuses to allow this is politically motivated. Same for Google, although they're pushing their own format. Neither of them want to see H.264 or any other commercial format become the de-facto standard because the folks at Mozilla don't believe people have the right to choose non-free software and the folks at Google want the world to use their shit. I love H.264 because it gives me awesome quality in small files and it "just works" across a myriad of my devices. My iPad cannot play VP8 or Theora and VLC on my Macs don't play OGG files very well. Hell I even tried using VLC on my jailbroken iPad. If VP8 or another "free" format had the hardware and software support of H.264 then I would have no problem using it.

  72. Re:Or we could just fix patents and be done with i by OeLeWaPpErKe · · Score: 1

    1) please look up how valid the FAT patent was in Europe : perfectly valid. For most non-Chinese Asian countries software patents are valid and China is just a matter of time (problem is enforcement, not so much the law)
    2) I believe DiVX has a proper license, and to get their implementation you have to agree to their EULA ... which requires you, amongst other things, to never use any other player than their own, if you think that's a better deal, go ahead
    You might have mentioned flash as well, since that's at least a workable solution for websites
    3) if that were true every implementation except the win7 and ffmpeg one should be blacklisted (specifically the divx one). Browser makers don't like to have bugs "this video works on win2k, but not on winxp" type bugs which are unavoidable when using the OS's codecs. It also adds complexity to the user's experience because they will need to track down the correct codec for their own system. Google is pretty adamant about avoiding that (and their browser is much better for it)

  73. why fight? by Anonymous Coward · · Score: 0

    H.264 isn't proprietary. It's an open standard, it's just not free. You have to license it, but there is nothing proprietary about it. It was designed and built by many contributors and it's a ratified standard. WebM (VP8) and Ogg Theora are great, but they're not going to win a codec fight. And who says HTML5 has to have a built-in codec? All HTML5 needs to do is define a video type/tag and whatever OS the browser is running on will handle the video playback. Also, who says only one video format should be supported? True, most sites are only going to put up H.264, but that doesn't mean other formats can't or shouldn't be available. Why are there always these fights with people thinking there should be only one way to skin a cat?

  74. Re:Or we could just fix patents and be done with i by DrXym · · Score: 1
    1) And my point applies to any country where software patents are enforced. Sell a codec pack. Though I expect most Linux users have the nous to obtain a codec for free and virtually every other OS would ship with one in it, or one would be obtainable for nothing.

    2) From the DivX website - "The DivX Plus® Codec Pack includes everything you need to play DivX® or MKV files in third-party applications, like Windows Media Player.". Or in a web browser assuming the browser bothered to use what was available to it.

    3) The fact is that a browser could maintain a whitelist / blacklist of codecs and if any particular codec vendor wished to extricate themselves from a blacklist, or get onto the whitelist the browser vendor could provide a mechanism to do it. Heck, the browser could one step further and treat a video tag as a specialized NPAPI plugin that declares what containers & codecs it supported and implementing a particular scripting API and callback. Supply the VP8 plugin with the browser and then let the vendors implement additional video plugins in any way they saw fit.

    The fact is that browser have chosen to artificially limit the usefulness of video tag and it sucks.

  75. Re:Or we could just fix patents and be done with i by LordVader717 · · Score: 1

    Bzzz. Wrong. MPEG-LA demands license fees from anyone in Europe too.

  76. Windows 8... by Anonymous Coward · · Score: 0

    The big issue with a codec "war" isn't really that some browsers might not support a certain video format out of the box.
    The big issue is Microsofts intention of not allowing plugins to the IE-version that will ship with Windows 8.
    This means that any site that offers online video will be forced to use H264 as a lowest common denominator if they want any substantial market.
    Other browsers will be possible to extend to support formats that they don't support as standard.
    IE will not.

    In other words, the "war" has probably already been won and H264 is the winner.
    One wonders if this is one of the reasons behind Microsofts "no-plugins allowed" design of IE 10 Metro.

  77. So find a BSD version for me by Anonymous Coward · · Score: 0

    that I can use freely. Oh, it doesn't give me anything other than the right to look at the code because it's patented?

    So I guess patent pools are likewise hostile to BSD.

  78. Only to the same extent as patents are political by Anonymous Coward · · Score: 0

    Because there's no reason to require a patent on a video codec or require that people sign off for it. But they do, so I guess the main reason is political. Apple refuse to free the patent for political reasons. Same for Windows. Neither of them want to see Open Source become a viable competitor. Apple, for example, want people to use their shit.

    You love H264 because you don't have to sign a license for it. Mozilla and Google would. "It just works" fails on Windows XP and similar problems with Ogg encoding on Apple iPods: they don't want to use a free codec. Why? At least they don't have to pay for it.

    VP8 does have hardware support like H264 does. Apple, however, refuse to allow such free codecs access.

  79. Re:Or we could just fix patents and be done with i by Anonymous Coward · · Score: 0

    The key word is try.

  80. Re:Or we could just fix patents and be done with i by Wesley+Felter · · Score: 1

    Mozilla can pay for the license out of their $100M annual revenue; they just don't want to. Free software martyrdom is a choice; it's not some law of nature.

  81. True, but longer than 17 years by jrincayc · · Score: 1

    I agree that it is good that patents will expire. That said, they last longer than 17 years in the US (and in plenty of other countries they last 20 years). But it will be awhile before they are finished. For example MP3 (and MPEG-1 that MP3 is a part of) will not be done till at least 2015 (and the draft standard came out in 1991), MPEG-2 is at least 2018 and H.264 is 2027. By that time, there will probably be some 3D video codec that everyone wants, so we still will have to deal with software patents.
    http://www.osnews.com/story/24954/US_Patent_Expiration_for_MP3_MPEG-2_H_264

  82. Re:Or we could just fix patents and be done with i by neonsignal · · Score: 1

    Ah, but that is why software patents are even more insidious than copyright restrictions; you can infringe a software patent without even being aware of doing it. A clean-room implementation does nothing to solve this.