Slashdot Mirror


Cisco Releases Open Source "Binary Module" For H.264 In WebRTC

SD-Arcadia writes "Mozilla Blog: 'Cisco has announced today that they are going to release a gratis, high quality, open source H.264 implementation — along with gratis binary modules compiled from that source and hosted by Cisco for download. This move enables any open source project to incorporate Cisco's H.264 module without paying MEPG LA license fees. Of course, this is not a not a complete solution. In a perfect world, codecs, like other basic Internet technologies such as TCP/IP, HTTP, and HTML, would be fully open and free for anyone to modify, recompile, and redistribute without license agreements or fees. Mozilla is fully committed to working towards that better future. To that end, we are developing Daala, a fully open next generation codec. Daala is still under development, but our goal is to leapfrog H.265 and VP9, building a codec that will be both higher-quality and free of encumbrances.'"

22 of 95 comments (clear)

  1. Good luck with that... by Thinine · · Score: 4, Insightful

    A modern video codec that exceeds the performance of H.265 and VP9 without violating any of the patents held by contributors to either? And one that gains the support of hardware vendors to build it into systems? Good luck.

    1. Re:Good luck with that... by SimonTheSoundMan · · Score: 2

      Why not sell full h.264 converters in countries other than USA, Australia, New Zealand and the other handful of countries that have such software patents?

      Bring the datacentres to the UK or other EU countries.

      At the same time Mozilla set up bank accounts and trading addresses in Europe and release a browser with h.264 support. Companies get away with it for tax, so why not for patents?

    2. Re:Good luck with that... by CastrTroy · · Score: 3, Insightful

      I often wonder how you can guarantee something doesn't violate any patents. Since there's no requirement for how long a new product can exist before the patent holder "all-of-a-sudden" discovers that the new product is in violation of the an existing patent, and since there are so many patents out there, it would be quite hard for there to be a guarantee that something didn't violate a patent. "Submarine patents" as they are called happen all the time. You don't bring up a case as soon as some product makes it to market. You wait a few years, and after the product is a success, then you go and ask for a bunch of money. I would say that in many, if not the in the vast majority of patent infringement cases, that the people violating the existing patent unintentionally, and without knowledge of the patent existing at all, or even if they were aware of it, they read it, and interpreted it differently and figured they weren't infringing.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    3. Re:Good luck with that... by Lennie · · Score: 2

      You are forgetting Daala is developed at the IETF and Mozilla by some of the same people that made the patent free Opus audio codec.

      Which really is 'best of breed':

      http://www.opus-codec.org/comparison/

      So have I have at least some fait.

      --
      New things are always on the horizon
    4. Re:Good luck with that... by jmv · · Score: 3, Informative

      Legally, there's a reasonable limit on how long you can wait (6 years under some theories). That being said, indeed can can never prove non-infringement, and it's equally valid for free codecs than it is for encumbered codecs. Paying the MPEG LA tax does not shield you from trolls, or even from companies that participated in the standard and aren't part of the patent pool (usually, not all declared IPR holders are represented in a pool).

    5. Re:Good luck with that... by jmv · · Score: 4, Informative

      I recommend reading Monty's Daala demos 1, 2, 3 and 4. We're not just building a similar codec, but making radical changes to many fundamental components of a video codec.

  2. Why not just build on VP9? by AlphaWolf_HK · · Score: 3, Insightful

    Isn't VP9 supposed to be unencumbered by patents anyways?

    --
    Careful with names containing L slashdot.org/~AiphaWolf_HK slashdot.org/~AlphaWoif_HK slashdot.org/~AiphaWoif_HK
    1. Re:Why not just build on VP9? by horza · · Score: 3, Informative

      Why isn't this comment already rated -5 Troll? Pathetic even for a troll, 1 second Google search shows it is BSD licensed.

      Phillip.

    2. Re:Why not just build on VP9? by RivenAleem · · Score: 2

      And you trust a Google search to be impartial in this!?

  3. Misconceptions by Imagix · · Score: 4, Interesting

    Hmm.. that blog post reads of marketing-speak. It talks about "plan to open-source" and release as a binary module. If it's "open-source", what about the source code? And it talks about "plan to" open-source. Not that they are going to, or already have, but they "plan to" in some nebulous future timeframe, which by then, the plans may have changed. Another statement I find interesting is that the "(IETF) will decide next week" about which codec to use. I'm guessing that he's referring to the IETF 88 meeting happening in Vancouver next week. Too bad nothing actually gets decided at the meeting. Decisions go back to the working group mailing lists for decisions.

    1. Re:Misconceptions by Tapewolf · · Score: 4, Interesting

      As I understand it from reading the article and the comments, Cisco will subsidize the patent licenses if you use the binary. If you prefer, you can use the source code, but then you will have to deal with the patent licensing yourself.

      "Nathan – We will select licensing terms that allow for this code to be used in commercial products as well as open source projects. In order for Cisco to be responsible for the MPEG LA licensing royalties for the module, Cisco must provide the packaging and distribution of this code in a binary module format (think of it like a plug-in, but not using the same APIs as existing plugins), in addition to several other constraints. This gives the community the best of all worlds – a team can choose to use the source code, in which case the team is responsible for paying all applicable license fees, or the team can use the binary module distributed by Cisco, in which case Cisco will cover the MPEG LA licensing fees. Hope that answers the first part of your question – Nadee, Cisco PR "

    2. Re:Misconceptions by jmv · · Score: 2

      Right now, the site has neither binaries nor source, but I'm pretty sure both will be available at the same time. The only point of the binaries there is that since they are served by Cisco, then Cisco can handle the patent licensing. The license is non-transferable (this is not something Cisco controls), so you can't download once and put it into your product, each product has to downloading it on its own for the license to apply. Since it's open source, anyone can also just build it themselves, then then obviously they're also not covered by the license.

  4. Monty's comments by jmv · · Score: 4, Informative

    Beyond the official announcements, I strongly recommend reading Monty's comments on the issue.

  5. Open source still requires license fees by dFaust · · Score: 4, Informative

    As pointed out in the comments on the Cisco blog post by a Cisco PR rep, if you use the source code (as opposed to the binary) you are responsible for any resulting licensing fees. Cisco is only covering the fees for those who use the binary.

  6. Daala development is just like "good math"... by Anonymous Coward · · Score: 4, Insightful

    The Daala development is covering new grounds (yes, that's correct), and doing so in a public way. Just like the proof for the Fermat theorem was extremely useful because it created a LOT of new, *good* math (that has applications on stuff as seriously important as the entire field of cryptography) and not because it proved the Fermat theorem, Daala is already important even if the end result ends up not being the best codec under the sun. However, if you go by the result in Opus, it WILL be of extremely good quality.

  7. Re:Open Source Binary Module by undeadbill · · Score: 4, Informative

    FTA: "Cisco is going to release, under the BSD license, an H.264 stack, and build it into binary modules compiled for all popular or feasibly supportable platforms, which can be loaded into any application (including Firefox)."

    From your comment: ..."since it lacks copyleft provisions to actually make the source open."

    Looks like the source will be open, since they are releasing the stack under the BSD license. Looks like people will be able to do anything they want with it, including making baby mulchers, angel summoning portals, and *gasp* video player implementations. Oh, HORRORS, people might not submit their code back to Cisco after attributing their source to them (as simply doing so will allow people to find, oh, I don't know, the source that Cisco is offering for free under a BSD license?).

    The only issue is with the fact that Cisco is having to provide a shield using the BSD license between MPEG LA and the rest of the world, while paying a hefty licensing fee for the privilege. However, using a BSD license means they cannot have any unreasonable hold over the source once it is out in the open. If anything, Cisco is a good guy in this (god, did I just say that?).

  8. Re:Why free? by thue · · Score: 4, Insightful

    Because the H.264 video format is only worth money because of the network and incumbency effects, not because it is better. A video format is a natural monopoly. VP8 is just as good as H.264, and free, but that is not enough to displace H.264 because H.264 has a monopoly via the network effect.

    If we were talking about a program such as Photoshop, where the barriers to entry is most determined by your ability to make a better photo editor, it would not be the same thing. There is good reason that the other examples in the summary are "TCP/IP, HTTP, and HTML", all of which are not terribly hard to replace, but which have powerful positions because of the network and incumbency effects.

  9. Re:Why free? by Goaway · · Score: 2

    VP8 is just as good as H.264,

    This is not actually true.

  10. Laches by tepples · · Score: 2

    It's called "laches". If someone waits years between becoming aware of an infringement and bringing suit, the assumption in a court of equity is that he sat on his rights to let the damages pile up.

  11. Oh, goody, I can "consume" silent movies now... by Dr.Dubious+DDQ · · Score: 3, Interesting

    If this license and "modules" covers encoding as well as decoding, AND The Motion Picture Experts Group Licensing Association doesn't decide to rescind their moratorium on charging license fees for the amazing innovative "actually sending the video over the internet" parts of the patent pool, at least this will allow some basic participation in online using the lower-quality "baseline" profile (only, as far as I know) without paying a poll tax to use their Intellectual Precious.

    However, I would also assume this doesn't include AAC or MP3 patents either, so unless "consumers" start using Opus (preferable - Opus is awesome) for their audio codec [and it's packageable with h.264 video in some legally-usable manner], you'll still be limited to providing "silent movies".

    If the MPEG License Ass. was serious about killing VP[0-9]+, they'd explicitly waive license fees for any implementation of the h.264 encoding and decoding algorithms that are implemented in "software" intended to be executed on a general-purpose CPU (i.e. no dedicated "hardware decoding/encoding") and which is released under an OSI-approved license (if they really wanted to troll, they could mandate that it be a share-alike license like the GPL, just to make a subset of people throw a tantrum). This wouldn't cost them anything (people with money who are "selling" software and/or making dedicated hardware for encoding and decoding h.264 would still be paying them anyway), but there'd still be a legally-free path for everyone else to participate using h.264 (i.e. Mozilla et al could implement software encoders and decoders to distribute). This would eliminate the need for any of the current-generation "alternative"/free codecs entirely, leaving them only daala to have to compete with later, and completely undermining what little momentum Google has bothered to get going on the VP* codecs.

    Given how much sense this would seem to make, though, I wouldn't expect the MPEG License Ass. to even consider it.

    1. Re:Oh, goody, I can "consume" silent movies now... by chefmonkey · · Score: 2

      Well, keep in mind that an MTI video codec is mostly intended to serve the purpose of preventing complete failures to negotiate. Also, the MTI that 's being proposed in the IETF is H.264 baseline, which is a far sight worse than VP8 by pretty much every metric imaginable. If H.264 baseline is selected as MTI, then I would imagine that the existing implementations will continue to offer VP8 in preference to H.264 baseline, and fall back to H.264 baseline only as an emergency backup "codec of last resort".

      As far as Opus is concerned, both Firefox and Chrome currently use Opus as their preferred audio codec for WebRTC, and have since day one. Opus was a relatively uncontroversial choice as the MTI codec, so I suspect any other interested parties will be happy to do the same.

      In terms of Opus support for the audio element... well, try it out for yourself. Put this in an arbitrary HTML file, load it up in Firefox, and see what you get: <audio src="http://radioserver1.delfa.net:80/256.opus" controls/>

  12. Free binaries + free Backdoors! by Jmc23 · · Score: 3, Interesting

    Get 'em while they're hot!

    --
    Don't complain about syntax, grammar, or spelling. There is no.hell like input on android.