Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
Mozilla Open Source Patents

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

Posted by Unknown Lamer from the bait-and-switch dept.
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.'"
This discussion has been archived. No new comments can be posted.

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

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

Comments Filter:

  • Good luck with that... (Score:5, Insightful)

    by Thinine ( 869482 ) on Wednesday October 30, 2013 @11:09AM (#45281361)
    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.

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

      • Re: (Score:2)

        by AK Marc ( 707885 )

        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?

        I didn't think New Zealand had software patents.

    • Re:Good luck with that... (Score:4, Insightful)

      by CastrTroy ( 595695 ) on Wednesday October 30, 2013 @11:17AM (#45281457)
      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.

      • Re:Good luck with that... (Score:4, Informative)

        by jmv ( 93421 ) on Wednesday October 30, 2013 @11:39AM (#45281797) Homepage

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

        • Re: (Score:2)

          by TheSync ( 5291 )

          Legally, there's a reasonable limit on how long you can wait (6 years under some theories).

          There have been codec legal fights much longer than 6 years after a patent was granted.

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

      • I often wonder how you can guarantee something doesn't violate any prior art. Since there's no requirement for how long an existing "invention" can wait before the patent applicant "all-of-a-sudden" independently discovers that an existing idea has never been pushed through to be patent process, and since there are so many ideas out there, it would be quite hard for there to be a guarantee that something didn't think of something first. "Undisclosed source code" as it's called happens all the time. You don

        • I think it's even more complicated than that. With seven billion people on the planet, it's completely possible that something is both non-obvious and that many people could arrive at the same method of solving a problem in a very short period of time. Non-obvious is a very loose term anyway. Many things that seem obvious to one person, are not at all obvious to another person. How exactly does one test for "obviousness"?

    • Re: (Score:3)

      by Lennie ( 16154 )

      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/ [opus-codec.org]

      So have I have at least some fait.

      • So to prove this Opus codec is the best, you link to... the website opus-codec.org? I could employ that same methodology to prove that Surface is the best tablet ever, the NSA only does what it needs to keep us safe, and that cigarettes are beneficial in many ways.

        • Re: (Score:1)

          by narcc ( 412956 )

          So to prove this Opus codec is the best, you link to... the website opus-codec.org?

          "Prove"? He's clearly just directing readers to more information about the codec. (He mistakenly thought Slashdot users could read, research, and make their own judgments.) What better place to start than the official website?

          Would you rather he linked to Wikipedia or some blog entry? Would that make you feel better? Probably not ...

          "So to prove this Opus codec is the best, you link to... the website wikipedia.org? I could employ that same methodology to prove that Surface is the best tablet ever,"

          Did I

        • There are several reputable third-party listening tests linked at the bottom of the page, below their own, admittedly unjustified, graphs.

    • Re:Good luck with that... (Score:5, Informative)

      by jmv ( 93421 ) on Wednesday October 30, 2013 @11:43AM (#45281861) Homepage

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

      • Daala development is just like "good math"... (Score:4, Insightful)

        by Anonymous Coward on Wednesday October 30, 2013 @11:54AM (#45282039)

        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.

    • Thanks for the warm show of support at the end. You're right that it's a huge task and that we'll need all the luck we can get.

    • Re: (Score:2)

      by suutar ( 1860506 )
      It's not that it doesn't involve patents, it's that Cisco is paying the patent license fee and not charging anyone else for it.

    • A modern video codec that exceeds the performance of H.265...? And one that gains the support of hardware vendors to build it into systems? Good luck

      There are about thirty licensors of H.264 and HEVC technologies.

      Most of them global industrial giants like Mitsubishi, Philips, Samsung, Toshiba, LG. Their principal licensees are on the same scale and for all practical purposes control together they control 100% of a vertically integrated video hardware market.

      The geek may have a codec in development. Panasonic and Samsung will have 4K UHD video gear in production.

  • Why not just build on VP9? (Score:4, Insightful)

    by AlphaWolf_HK ( 692722 ) on Wednesday October 30, 2013 @11:10AM (#45281363)

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

  • Go Monty (Score:1)

    by Anonymous Coward

    Huge respect for Chris Montgomery. Instead of using his talents to make a huge pile of money he works so we can have open codecs! I also have watched his video destroying myths about digital audio [xiph.org] about ten times, it's great.

  • Misconceptions (Score:5, Interesting)

    by Imagix ( 695350 ) on Wednesday October 30, 2013 @11:13AM (#45281409)
    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.

    • agree with your perspective

    • Re:Misconceptions (Score:5, Interesting)

      by Tapewolf ( 1639955 ) on Wednesday October 30, 2013 @11:29AM (#45281641)

      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 "

    • Re: (Score:2)

      by Goaway ( 82658 )

      The binary module is by far the more interesting part. There are already entirely capable open-source h.264 decoders. Another one would not be interesting on its own. Getting a fully licensed binary is much more useful.

    • Re: (Score:2)

      by Guspaz ( 556486 )

      They're releasing both the source and the binary... I get the feeling the binary release and the way that Cisco hosts it and Firefox downloads it on-demand has something to do with how the licensing works, that you wouldn't be covered by Cisco's patent payments if you compiled the source yourself.

    • Re: (Score:3)

      by jmv ( 93421 )

      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

  • Looks interesting [xiph.org] and all, but it'll take a lot to convince me it's a serious competitor to H.264.

    • Re: (Score:2)

      by Goaway ( 82658 )

      It's not a competitor to h.264, it's aiming to be a competitor to h.265.

      • You're right. I misread

        our goal is to leapfrog H.265 and VP9, building a codec that will be both higher-quality and free of encumbrances.

        to mean it intends merely to be a generation ahead of the current-generation truly-open video codecs, which would be a much weaker claim.

        My opinion towards it remains the same, though: truly-open codecs don't have a great track record, but I really hope they succeed.

        • though: truly-open codecs don't have a great track record

          Like opus which beats pretty uch everything else?

          • Re: (Score:2)

            by Goaway ( 82658 )

            They've been doing well for audio, both Vorbis and Opus are good codecs. But audio is a lot simpler. It's a very different story for video.

      • VP9 (Score:2)

        by tepples ( 727027 )
        VP9, developed by the On2 division of Google, is the competitor to H.265. Daala is the competitor to H.266, and from what I've seen, it'll be as big of an improvement over currently popular codecs as JPEG was over heavily-dithered GIF for photographic images.

  • Monty's comments (Score:5, Informative)

    by jmv ( 93421 ) on Wednesday October 30, 2013 @11:27AM (#45281613) Homepage

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

  • Open source still requires license fees (Score:5, Informative)

    by dFaust ( 546790 ) on Wednesday October 30, 2013 @11:38AM (#45281791)

    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.

    • That's actually missing a key piece of information. Patent licenses can be very narrow in scope, which allows an owner to charge different parties for different aspects how a device uses a patented technology.

      Does anybody know why I wouldn't need a separate licensing deal with MPEG LA if I built a web application using WebRTC? Their typical licensing agreement (as used in Windows and Flash, for instance) does not extend to third-party applications that use the codecs through APIs.

  • I especially like how they're not charging for the NSA code either.

  • It should be Cisco Releases "Open Source" Binary Module For H.264 In WebRTC :)

  • Oh, goody, I can "consume" silent movies now... (Score:4, Interesting)

    by Dr.Dubious DDQ ( 11968 ) on Wednesday October 30, 2013 @02:16PM (#45284005) Homepage

    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.

    • You understand what "WebRTC" is, right?

      • "You understand what "WebRTC" is, right?"

        Yes...but you've got a point. I hadn't immediately recognized that this was really just for "Internet Video-Telephone" use rather than "Internet Television" (i.e. Youtube). There are a lot of people that seem to also be commenting on the assumption that this has something to do with watching TV on youtube (e.g. the <video> tag)...which it hypothetically could, though it seems obvious that's not what Cisco cares about.

        The point about not having proprietary-soun

        • 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

          • "In terms of Opus support for the audio element... well, try it out for yourself.[...]load it up in Firefox[...]"

            Firefox has supported .opus files in <audio> for more than a year now and it works quite well. (I'm a raving Opus fanboy since over a year ago - I started running what would become Firefox 15 during its "Aurora" stage just because I knew it had .opus support. I've had .opus up on my "HTML5 <audio> Test Page [dogphilosophy.net] for quite some time. (I still need to add an .alac sample on there - if it tu

  • Free binaries + free Backdoors! (Score:4, Interesting)

    by Jmc23 ( 2353706 ) on Wednesday October 30, 2013 @02:24PM (#45284123) Journal
    Get 'em while they're hot!

    • Re: (Score:2)

      by caspy7 ( 117545 )

      Eich often does a good job of intelligently addressing questions in the comments. I strongly encourage looking through them to learn more.
      In reply to one question about the binaries he replied:

      ...because the BSD-licensed source code is available at http://www.openh264.org/ [openh264.org], you and others can verify the compiled bits come from that source, no malware or spyware added. We will organize community auditing of this sanity check, and the binary modules will be cryptographically signed so Firefox can verify their integrity.

      And another,

      great question, and it applies to Firefox, Chrome, and other browsers. But in the case of Firefox for Linux at least, and for Cisco’s OpenH264 binary modules, we can audit: get matching revision of the open source, compile with the same (bootstrapped from open source) clang or gcc toolchain, and compare bits.

      It appears we can have a good amount of confidence that what's in the code is what's in the binary.

  • Consider http://thewikiman.allsup.co/MegaMetaPatent, and how what is described there could represent any patent.  Then consider ways of scrambling the language and perhaps making things just specific enough to get a patent granted, then rinse-lather-repeat until you've mined out your desired area of the market.
  • Anybody can create their own implementation of TCP, as far as I know? You simply need to follow some standard to ensure that your stack will work with other stacks, but that's about it as far as I know!

Slashdot Top Deals

As you will see, I told them, in no uncertain terms, to see Figure one. -- Dave "First Strike" Pare

Close