'Free' H.264 a Precursor To WebM Patent War?
webmink writes "The MPEG LA seem unwilling to explain why they have extended their 'free' H.264 streaming video policy now. This article unpacks the history of MPEG LA and then suggests the obvious — it's all because of WebM — and the worrying — maybe it's preparing the ground for opening a third front in the patent war against Google."
It seems an obvious requirement now to me that any 'international standards', as H.264 is described in TFA, should not be written by a consortium that have a collection of patents on the only possible implementation of the standard!
I'm not sure how this would be ensured - maybe the same consortium that pool the defensive patent pool for Linux could start a standards body based around this simple idea.
If a man empties his purse into his head no man can take it from him. An investment in knowledge pays the best interest.
I'm still rooting for Google's format. I don't care about free as in money so much as free as in open source. I don't see how it could possibly be sustainable for every single company that makes a browser from here on out to have to pay a fee to use this codec. If they put H.264 into the HTML 5 spec, that is only going to make it a pain in the ass for browser developers and open source users. It's stupid. This isn't helpful...it's just slight of hand. "Look it's free!" Um no...it actually isn't free at all. I wish people writing all the other articles would acknowledge that a little better. This changes nothing.
"Those who would sacrifice essential liberties for a little temporary safety deserve neither liberty nor safety." - BenF
The third link has a good explanation of why h264 isn't really free.
First thing to be noted is that any deal they offer today can be withdrawn in five years anyway.
The free bit is only that they will not bill the end user.
the encoding is not free
the streaming is not free
and the decoding is absolutely not free.
The last one means any browser wishing to offer this functionality has to pay for it and unfortunatly it can't pass on the patent protection granted by paying for this so there is no way for firefox to offer this.
So really we should say no to h264 and hope google doesn't get creamed in its patent battles.
Blarney Quality Restaurant, Plants
The natural party to sue would be Mozilla or Opera here, not Google I think. Google already pay the appropriate license fees for YouTube, so there seems to be very little of a legal case there.
(Patent) war! What is it good for!? Absolutely nothing.
H.264. What is it good for!? Absolutely nothing.
Sing it with me everybody!
These posts express my own personal views, not those of my employer
First, kill all the lawyers. Yeah, sure, we'll have some confusion, initially, but... Come on, really. You know it's definitely, at least, worth a try.
Cases like this are ones where the US government (assuming these are US patents) should step up and use their powers of eminent domain to acquire these patents, declare H.264 a government standard (like AES and DES before it) and release the patents (or a perpetual license thereto) into the public domain.
The developers of H.264 and other codecs have certainly put in a lot of research and hard thinking. I believe their algorithms should be patentable (as opposed to "software" patents that are really on UI patterns and business methods), and I believe the inventors should be justly compensated. However, for maximal furtherance of the creative arts, information interchange formats need to be standardized and unencumbered. The visual entertainment industry contributes far, far more to the US economy than the codec-designing industry, and always will. An indirect subsidy like this would be an excellent stimulus.
If they had any sense, the MPAA would by lobbying the government to make this happen, rather than trying to shore up their old distribution models with copyright crackdowns. Getting free (gratis), standard, H.264 decoders into the hands of billions of people worldwide would give them a huge boost to their audience. Unfortunately, since they represent motion picture distributors, they're probably in favour of steep licensing fees to keep the barrier to entry high for content producers wishing to distribute independently.
Be careful. People in masks cannot be trusted.
When he says "free", he means "free of patents threats". Of course you can do it "for free", but they will eventually come after you.
Ah, and when you "pass it to the OS", you need to have paid for and OS from a vendor that has paid the licensing...
exp(i*pi)+1=0
First thing to be noted is that any deal they offer today can be withdrawn in five years anyway.
Nope. What part of "royalty free forever" did you not understand? If you read that third link again you'll find it USED TO BE five year periods but now lasts until the patents expire, which essentially means forever since it's all moot after the expiration.
That argument is dead now.
so there is no way for firefox to offer this.
They have more than enough money to pay for this and also could distribute a standalone player module for Linux - because after all, on other platforms they could simply use the native h.264 playback facilities that both Apple and Microsoft offer.
I understand philosophically where Firefox is coming from but it's not a practical fight and not one Firefox can do anything but be hurt by as more and more users switch to other browsers like Chrome that can play back h.264.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Erm, no. You can't rely on companies and individuals implementing a standard. They'll implement anything they like regardless, and then you'll have interoperability issues, pretty much as we have now anyway.
If you want a standard to be reliably implemented in a wide range of systems, you have to take out the "implementation" part of the equation. That means, distribute a public domain or BSD library which does all the hard work, and let everyone piggyback on that for nothing.
You can pirate everything and never be able to do proper commercial stuff with your computer. Or you can do it the right legal way and be able to make some money off of it. The problem is of a legal nature. It's not about what you can do at your home when nobody looks. It's more about what you can do in a firm or organization which is subject to some oversight. MPEG LA have said that they do not see a possibility that there is such a thing as a codec that does not violate their patents. And there are problems with getting for instance Full-HD recording equipment which is not subject to h264 patents.
First thing to be noted is that any deal they offer today can be withdrawn in five years anyway.
Yes, I can remember that only last year people saying that everybody using H.264 would pay when the MPEG LA jacks up their fees in 2011. That didn't happen of course, which isn't a surprise since the MPEG LA historically always offered the same or better terms when a new licensing period began. Turns out they have something to lose by alienating their customers, especially since they also want to sell future products to them which isn't that easy if people mistrust you.
the encoding is not free
Encoding is free, encoders aren't if you distribute more than 100.000 a year.
the streaming is not free
It isn't free if the streams are pay per view or part of a payed subscription provided that there are more than 100.000 sales or subscribers per year. If you have to pay it's either 2 cent or 2% of the price per sale (whichever is lower) and at worst 10 cent per year per subscriber.
and the decoding is absolutely not free.
Again, decoding is free, distributing more than a certain number of decoders isn't.
The last one means any browser wishing to offer this functionality has to pay for it and unfortunatly it can't pass on the patent protection granted by paying for this so there is no way for firefox to offer this.
Any browser can offer H.264 decoding for free by using the system provided codec framework. While Mozilla has been decrying that approach for their desktop browser it's exactly what they do in their mobile version (Fennec). Every modern operating system comes with a H.264 decoder anyway. For older Windows and MacOS systems there are free licensed downloads (Divx, Quicktime) and for Linux systems there is at least a cheap gstreamer plugin (ignoring the fact that almost anyone who uses Linux as a desktop operating system probably has some version of FFMpeg installed anyway).
Of course this is a problem, but it's a far cry from there being no way to offer such functionality.
Yes, I can remember that only last year people saying that everybody using H.264 would pay when the MPEG LA jacks up their fees in 2011. That didn't happen of course, which isn't a surprise since it's not 2011 yet you muppet.
it can't pass on the patent protection granted by paying for this so there is no way for firefox to offer this.
Here I have the feeling I'm still missing something. Why can FF not offer H.264 video? I understand it can not be built in (though they could make two versions of it, with native H.264 for jurisdictions outside software patent land). It's something that comes up all the time.
Not so long ago I have been playing YouTube videos in H.264 right in FF using mplayer-plugin. There is some greasemonkey script for that, youtube without flash. Maybe not as technically charming as native but for the end user what counts is: it works.
And before anyone starts riling about plugins: why are plugins bad while add-ons are good? From a user pov they're the same. Just a different name. Both add functionality to a browser that it doesn't do natively.
Also what I do not understand, is why FF is singled out for this. Chrome is also given away for free, just like Opera and IE. There is also an OS version of Chrome. I never hear about problems of paying for license fees for those browsers. Or any other browsers - which may be because the rest is too small to count.
The government can take patents away for more or less any reason it likes, that congress has passed a law allowing it to. Reason is because patents are a power specifically granted to the government. Physical property ownership is considered more of a natural right. The government doesn't grant you ownership because they can't deny it either. Eminent Domain exists because they can take private property for public use, in certain circumstances, however there has to be compensation.
With patents that's not the case. The government doesn't have to grant patents at all. They have the power to do so, but it isn't required. What that means is the government owns all patents ultimately and can do as they want.
As such there are some peculiarities with patent law many don't know about. The NSA can fine secret patents. If a civilian files the same patent, the NSA patent is then revealed and granted at the time it is revealed. The government is allowed to make a law like that, since patents are one of their explicit powers.
Likewise they can take them for various reasons. Congress hasn't granted unlimited power in that regard, but there are a list of reasons for which they can say "That's ours now," and you get nothing. That was actually threatened in the NTP-RIM case and is probably part of the reason NTP took a settlement that didn't include future fees. NTP was requesting an injunction to shut down Blackberry service. The federal government wrote a brief to the court saying they believed that would have an impact on national security (the US government loves them some Blackberries, they are the biggest customer) and they'd prefer the court didn't grant it. They also noted that if it was, they might simply have to void the patent, which can be done on national security grounds. The judge then strongly suggested the two sides work their shit out now.
Google isn't stupid. They got to investigate the format and patents before they bought On2, and of course after once they owned everything. Also, this is precisely the kind of thing Google would be good at: Looking through large amounts of information and figuring out what is relevant. So My guess is that one of both of the following are true:
1) VP8 (WebM) does not infringe on any MPEG-LA patents, or at least not any real ones. They probably have some overly broad BS ones, but Google probably has examples of prior art. Google did an extensive review and found that there was no infringement, VP8 had been engineered to avoid MPEG-LA patents so that it could be sold without additional license.
2) On2, and therefor now Google, holds patents on critical technologies used in H.264. In the event of any infringement suit, they can pull those out and file countersuit. Having WebM stopped would not be a real big deal to Google. They aren't using it for anything important yet. Having H.264 stopped would be devastating for MPEG-LA. Google could thus force them to license all relevant patents, at not charge, in return for the licenses to the Google patents.
Those are my bets. One or both of those is the case and so Google is confident they can win a game of chicken. This also might explain the move by MPEG-LA to put a permanent licensing moratorium on free H.264 stuff, as well as the fact that there is no suit. They may have looked at things and said "Shit, we can't touch VP8. We could try but we'd almost certainly fail and just wind up with a bunch of legal bills, plug give Google an ironclad thing to point to showing WebM is ok." They may have decided it is better to make H.264 look more attractive and perhaps keep up some nebulous threats to make people think twice about implementing WebM.
Always remember that patent warfare is a dangerous game. The trolls can play it because they don't own anything or make anything losing patents means nothing. In MPEG-LA's case, there could be a lot to lose if things went wrong.
Also what I do not understand, is why FF is singled out for this. Chrome is also given away for free, just like Opera and IE. There is also an OS version of Chrome. I never hear about problems of paying for license fees for those browsers.
"Chrome" is a closed source browser distributed by Google that contains a binary H.264 codec with a license valid for that binary only. "Chromium" is open source but comes with no H.264 codeo, though it's been patched to use the system codecs if available.
Firefox can not use the same solution as Chrome. It could use the same solution as Chromium, but it means it would only work for some people so they won't do it. That is why FF is singling themselves out, they are the only ones where it simply will not work.
Live today, because you never know what tomorrow brings
``I don't care as much about the codecs being open source or closed source - I'm mainly interested in which format offers the higher quality at the same (or lower) bitrate.''
I, too, care about which format offers the higher quality at the same (or lower) bitrate. But I'm pragmatic enough to not want to have to jump through hoops if I want to install the software on my computer (on whatever OS I happen to be running), fix any bugs that I encounter while using it, or maybe even audit the software. And I don't want to get in trouble with the law over watching or encoding a video.
If MPEG-LA or any other organization wants to offer a video format that I cannot legally use, or for which a codec that allows me to do all the things I want cannot legally be implemented and distributed, that's fine with me. However, I then won't be using the format. Getting slightly better video quality isn't worth the hassle, annoyance, and security risks of typical "we care more about our anti-piracy measures than about our customers" software. If anyone else does want to use such software, fine by me.
The only point where this becomes a problem is when we are talking about standardizing on a format. Standardizing on a format that is not free to implement and use is a very bad idea. Not because it cannot be made to work, but because of pragmatic reasons: there will be barriers, and those barriers will hinder implementation and adoption. All the major players including MPEG-LA recognize this. That's why MPEG-LA is offering this "free for the most common uses" licensing: without that, H.264 would be a huge hassle. Similarly, Flash only became as widespread as it is because the player is freely available for the most popular platforms, TrueType won out over Type1 because of better licensing conditions, and free software is all over the software development world because you can use it without having to jump through hoops.
Ask yourself this: being pragmatic, how much are you willing to pay and how much work are you prepared to do to get to (legally) use H.265, the new and wonderful (and at this point, hypothetic) video format that is even better than H.264? At what point would you, for pragmatic reasons, decide to go with VP12, the (also hypothetic) video format that is almost as good, and free for all to use for any purpose, with free software codecs that you can install with a single click or command?
Please correct me if I got my facts wrong.
the encoding is not free
Unless you use x.264.
In which case, you still need a patent license from the MPEG-LA if you live in a country where any of their patents are valid.
So all those open source projects like VLC, MPlayer, etc are paying through the nose to the MPEG-LA?
Nope, they all use FFMPEG, which is based in France. France does not recognise software patents, so they are not required to pay anything. Using them in the USA without a patent license, however, is illegal.
I am TheRaven on Soylent News
The main problem caused by MPEG-LA is that people can't distribute video software. GNU/Linux distros have to worry about distributing software that supports H.264, and developers have to worry about adding support to their apps. Documenting this situation is my hobby horse but this "free" licence" is so limited, I can't find much to write about it. It won't make H.264 safe for standards like HTML5 either.
They promise not to sue non-commercial distributors of video (no ads allowed on the webpage). That means I'm safe to publish videos of me singing karaoke, but no one was going to sue me for that anyway. The only real case I can think of is public service television, which could put their shows online now without worry, but they'd have to be very careful about not having anything that could be called an ad on their webpage. Is that really the extent of this "free" licence that such a fuss is being made about?
Expert in software patents or patent law? Contribute to the ESP wiki!
Why can FF not offer H.264 video?
They can. It's only their philosophy that prevents them from doing so. Neither the MPEG-LA, nor their own license, prevents them from supporting H.264. They could even distribute an H.264 plugin for Firefox on all supported platforms completely legally.
ARM and W-CDMA work in similar ways. ARM happens to own the patents and licenses them to whomever for a reasonable fee. W-CDMA works in much the same way as H.264. You have a bunch of companies that decide to share patents into one resource. It makes it easy for other companies to pay 1 fee and then use the technology. And H.264's licensing terms are reasonable. There is a cost of doing business. I know that is not popular around here, but it's the truth.
But for comparison here, if I own an ARM computer and make a video or some kind of word processing document on it, there's absolutely nothing stopping you from opening that video or that document on your computer with an x86 chip (at least nothing related to the origin of the file being an ARM-powered device).
If you create a video or audio file and encode it with codec XYZ, you can bet your sweet pile of software patents that when you send that file to me I'm going to have to use information about that codec to turn that file back into something my eyes and ears can understand. I have no choice.
Similarly, my phone doesn't have to support W-CDMA for me to be able to call you. I can just use a POTS line. Or use a GSM phone. Sure, I am more limited than I would be were there no software or hardware patents, but at least I have choices.
Unfortunately it's going to be harder for Free software going forward. Try writing an opensource point-of-sale or e-commerce program that can directly process credit cards. You can't without spending around $20,000 for PA-DSS auditing.
For those curious folk, here's the wikipaedia link for PA-DSS. It appears that people have discussed the PA-DSS + FOSS question before and it really sounds like it's just and issue of someone stepping up and taking control of the process.
Sure, you'll have to pay some money to have the software audited. Sure, you'll have to provide information about how the team audits and creates new releases of the software. Sure, you'll have to jump through certain hoops. But that's what it took when OpenSSL got FIPS 140-2 validation.
coding is life
Ah, and when you "pass it to the OS", you need to have paid for and OS from a vendor that has paid the licensing...
So you can support it only on OSes which have already done so. I've got Windows 7, which has done so. OS X has also done so. If you've got a recent nVidia card, chances are you've got a fully legal and paid-for hardware decoder which can be used just fine under Linux.
In fact, passing it to the OS, or to whatever local codec subsystem you've got, is a great way to ensure you can take advantage of hardware decoders. Insisting on implementing all this in the browser as a childish political move is a great way to ensure that Firefox will be the last to take advantage of hardware-accelerated WebM, if that ever surfaces.
Passing it to the OS pretty much ends the legal bullshit, and is the right choice technologically, also. It seems pretty clear that the only reason Firefox refuses to do so is because they don't want h.264 to win, even if it doesn't affect Firefox itself directly.
Don't thank God, thank a doctor!
No, I don't. I live in a country where software patents are not valid.
You miss the point. You (or some other AC) said "If you can show that the US patent is not being used in x-264 then I will concede your point." Pharmboy's point is that the burden of proof is always on the person saying something is being done. It's nearly impossible to prove the negative.
I'll give you an example: if you prove that you didn't rape and murder a little girl in 1997, I'll concede that you didn't rape and murder a little girl in 1997. You see? The burden should actually be on me to prove that you did. To pose the statement the other way is not logical.
On to another of your points. I do not know of any "personal use" exception to patent infringement. You might be thinking of copyrights, which do have a fair use defense. There are several research groups that are trying to get Congress to pass a patent fair use exception, though.
The point is that Firefox doesn't need to implement any codec whatsoever. Just pass video decoding to the OS, and worry about whether the OS supports the codec in question, be it in hardware or software.
Check out my world simulator thingy.
Have you ever read the license terms of an HD camera
No, and neither have you, you have just read what somebody on the internet claims it means.
That license agreement is there to cover the manufacturer's ass. They have paid their license to produce a device that encodes and decodes h.264. However, they have not paid for a license for you to distribute that content. They couldn't, because the cost of that license depends on how much you distribute. Non-commercial distribution is free, which is why they put that in the license agreement.
You do not need a license to encode on a licensed encoder, commercial or not. You do need one to distribute. If you are a filmmaker, you likely pay this license when you have discs pressed. This is nothing new, it's been this way for a long time. MPEG-2 on DVDs is the exact same.