VP8 and MPEG LA (WebM blog)
The arrangement with MPEG LA and 11 patent owners grants a license to Google and allows Google to sublicense any techniques that may be essential to VP8 and are owned by the patent owners; we may sublicense those techniques to any VP8 user on a royalty-free basis. The techniques may be used in any VP8 product, whether developed by Google or a third party or based on Google's libvpx implementation or a third-party implementation of the VP8 data format specification. It further provides for sublicensing those VP8 techniques in one successor generation to the VP8 video codec."
Posted Mar 7, 2013 19:58 UTC (Thu)
by drag (guest, #31333)
[Link] (25 responses)
So much we will probably never know. At least not anytime in the next couple decades.
> It further provides for sublicensing those VP8 techniques in one successor generation to the VP8 video codec."
They started working on "VP9" yet?
Posted Mar 7, 2013 19:59 UTC (Thu)
by drag (guest, #31333)
[Link] (24 responses)
http://news.cnet.com/8301-1023_3-57561111-93/googles-new-...
Posted Mar 7, 2013 22:05 UTC (Thu)
by dowdle (subscriber, #659)
[Link]
Posted Mar 8, 2013 0:25 UTC (Fri)
by Wol (subscriber, #4433)
[Link] (22 responses)
What's the betting that it's MPEG-LA that have had to bend over ... ?
I wouldn't put it past Google to have gone to MPEG-LA and said "look at this pile of evidence. Do you want us to give it to the USPTO and ask them to re-examine your patents? Just sign here and there'll be no unpleasantness :-)".
Cheers,
Posted Mar 8, 2013 2:34 UTC (Fri)
by drag (guest, #31333)
[Link] (21 responses)
The most likely way Google would be able to get this would be through cross-licensing patents. They paid a LOT for Motorola's patents and maybe some of the MPEG-LA members wanted a cheap way to avoid violating some of those. But since I don't see any mention of cross-licensing then I don't know how likely this is.
> but does menttion that no licence is being offered by MPEG-LA...
Yes.
I am curious how Google accomplished this. They know that VP8 would be worthless if people had to license it from MPEG-LA. It would make it effectively the same as H.264 from a end user's legal perspective. So they did something very important and impressive to have a blanket license granted to not only their VP8 implementation, but ALL VP8 implementations whether they are derivative or not. Without this it would pretty much eliminate any point in using it over the already well established H.264 stuff; both from business and open source perspective.
> I wouldn't put it past Google to have gone to MPEG-LA and said "look at this pile of evidence. Do you want us to give it to the USPTO and ask them to re-examine your patents? Just sign here and there'll be no unpleasantness :-)".
Given the history of USPTO and the massive unlikelihood that anybody would be able to defeat the patents by making them invalid in court I think this is extremely unlikely. Could be wrong, but I don't think so. It would be nice. By why play this game? Why not release the evidence and just leave it at that? They don't have to take MPEG-LA to court to convince other people that the patents have no teeth. Once people see the evidence then they would simply not feel compelled to pay MPEG-LA for the licenses over those particular patents. You don't need to court to destroy patents...
A alternative, and more somewhat more likely scenario (although I still think is unlikely), is that this is purely a marketing stunt. There is no way to prove a negative in this sort of case (MPEG-LA is not a risk). So Google figured out that the 'Fear and Doubt' game was working against VP8 adoption. The effective licensing costs for H.264 are so low that it made the legal issue mute when dealing with other large players. It was seen by large players that complying with H.264 was costing them virtually nothing and VP8 represented a unknown legal risk. So why risk it?
So Google simply threw a few million at MPEG-LA to get the blanket license for patents that seem like they could pose a risk, even if Google's lawyers think that they may be able to work around them. This way it removes the FUD and clears the way for the adoption of VP8 and VP9. This would be expensive, but they have a huge budget for promoting their products and maybe this was seen as a cheaper way to get users out of the shadow of doubt then to try to convince them through adverts and press releases.
Posted Mar 8, 2013 6:02 UTC (Fri)
by eru (subscriber, #2753)
[Link] (7 responses)
Posted Mar 8, 2013 8:19 UTC (Fri)
by daniel (guest, #3181)
[Link] (3 responses)
Posted Mar 8, 2013 12:12 UTC (Fri)
by man_ls (guest, #15091)
[Link] (2 responses)
Posted Mar 8, 2013 13:12 UTC (Fri)
by bawjaws (guest, #56952)
[Link] (1 responses)
More interestingly, the films and TV shows that Google rents are going to start being VP8 on ChromeOS due to that fake DRM they're trying to put into web standards to stop people using the fake DRM in Flash and Silverlight.
Kind of mixed feelings about that, but, it seems to be working.
Posted Mar 8, 2013 13:28 UTC (Fri)
by man_ls (guest, #15091)
[Link]
It is a bit thermonuclear: as a threat it looks great, in real life it sucks.
Posted Mar 8, 2013 13:24 UTC (Fri)
by bawjaws (guest, #56952)
[Link] (1 responses)
That's a big deal, and particularly the ability to jump quickly to VP9 due to the lesser format lock-in for effectively disposable video makes this a good place for open codecs to start.
They've already chosen Opus on the audio side, it could well be a very big deal.
Google's announcement email to the WebRTC list:
They're supposed to be making the codec decision at an IETF meeting in a week or so. Google delayed addressing the topic at the last meeting saying they had something lined up that would silence the critics. I guess the other shoe just dropped.
Posted Mar 8, 2013 14:10 UTC (Fri)
by bawjaws (guest, #56952)
[Link]
MPEG (not MPEG-LA) have been kicking around the idea of an royalty-free codec for a while, basing it on old MPEG tech that has fallen out of patent or on getting H.264 folk to agree to freeing up some baseline patents.
With this latest announcement about patents, Google has proposed VP8 to become the official MPEG royalty free codec.
http://www.robglidden.com/2013/03/google-mpegla-vp8-mpeg-...
Posted Mar 8, 2013 18:30 UTC (Fri)
by Lennie (subscriber, #49641)
[Link]
H.265 might still have a slight head-start though.
Posted Mar 8, 2013 6:22 UTC (Fri)
by iabervon (subscriber, #722)
[Link] (5 responses)
Posted Mar 8, 2013 13:06 UTC (Fri)
by pboddie (guest, #50784)
[Link] (4 responses)
Posted Mar 8, 2013 18:41 UTC (Fri)
by iabervon (subscriber, #722)
[Link] (3 responses)
Posted Mar 8, 2013 22:25 UTC (Fri)
by pboddie (guest, #50784)
[Link] (2 responses)
Posted Mar 8, 2013 23:21 UTC (Fri)
by iabervon (subscriber, #722)
[Link] (1 responses)
Posted Mar 9, 2013 3:04 UTC (Sat)
by tialaramex (subscriber, #21167)
[Link]
Injunctions are a means of _preventing harm_. The court must be persuaded that without the injunction some type of harm will occur to the plaintiff (e.g. their priceless 10th century wall painting will be destroyed, or their stranglehold on the desktop PC market will be broken) which is unlawful, and which cannot be made right through any of the court's normal remedies (e.g. monetary damages). If this is so it can decide based on very limited evidence (often timely action is essential) that the plaintiff is on balance likely to succeed in their claim and that it's not excessive to prevent the defendant from doing something (e.g. demolishing the wall, or shipping a new OS) meanwhile.
But even without an injunction all the ordinary remedies are still available. You just have to actually go through the entire lawsuit process to reach a judgement and get the remedy you want, rather than cutting straight to the injunction and hoping it strangles the defendant so badly that they've no choice but to forfeit their day in court altogether.
A world where Apple can ship infringing iPhones despite a lawsuit, but then has the bailiffs at One Infinite Loop repossessing the office furniture is not one where there "aren't any meaningful consequences" to not paying.
Posted Mar 8, 2013 7:53 UTC (Fri)
by epa (subscriber, #39769)
[Link] (5 responses)
Posted Mar 8, 2013 9:03 UTC (Fri)
by Wol (subscriber, #4433)
[Link] (4 responses)
Patent APPLICATIONS are pretty much rubber-stamped by the USPTO.
Patent RE-EXAMS are much stricter - a significant number of patents are invalidated by a re-exam.
And it wouldn't cost Google much to swamp the USPTO with re-exam requests that are on-point, pertinent, and capable of doing much much much damage to the patents.
It is NOT normal practice to invalidate patents in court. Even in a court case it is far more effective, and cheaper, to refer the patents back to the USPTO for re-exam. Only if that route fails do you really want to get into a court battle over validity.
Cheers,
Posted Mar 8, 2013 9:26 UTC (Fri)
by epa (subscriber, #39769)
[Link]
Posted Mar 8, 2013 13:16 UTC (Fri)
by bawjaws (guest, #56952)
[Link] (2 responses)
Where it gets muddy is when they claim that their stack of patents apply to other codecs. That seems to involve courthouses and juries learning about the ins-and-outs of video compression, therefore high cost and risk.
Posted Mar 8, 2013 16:05 UTC (Fri)
by Wol (subscriber, #4433)
[Link] (1 responses)
One only has to look at the gif patent (I think I've got the right one) where the USPTO granted two different patents on THE SAME algorithm. All Google has to do (and the tighter the patent is, the easier this is to do) is find a prior implementation of the same technique, and BOOM, the patent is gone.
I can't see it being hard for Google to find prior art. After all, they are the masters of search ... :-)
Cheers,
Posted Mar 8, 2013 21:08 UTC (Fri)
by dlang (guest, #313)
[Link]
fight with google over something involving searching....
Posted Mar 9, 2013 21:38 UTC (Sat)
by tterribe (guest, #66972)
[Link]
Google is a licensee of the H.264 pool at least (#384 on the list at <http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx>). That means they and their affiliates have to offer a reciprocal license to all other licensees.
This is one of the major controversies of the Motorola v. Microsoft case: since Motorola was acquired after Google agreed to the license and not included in the explicit list of "affiliates" Google provided, and since the lawsuit began before Google acquired them, Motorola claims the reciprocal license does not apply. Microsoft claims it does.
Posted Mar 7, 2013 23:09 UTC (Thu)
by boog (subscriber, #30882)
[Link] (11 responses)
Posted Mar 7, 2013 23:59 UTC (Thu)
by Zizzle (guest, #67739)
[Link] (10 responses)
Posted Mar 8, 2013 2:36 UTC (Fri)
by drag (guest, #31333)
[Link] (9 responses)
Posted Mar 8, 2013 7:36 UTC (Fri)
by auc (subscriber, #45914)
[Link] (8 responses)
Posted Mar 8, 2013 12:10 UTC (Fri)
by robert_s (subscriber, #42402)
[Link] (7 responses)
How long has WebM been around? What percentage of youtube videos are still not offered in WebM?
Posted Mar 8, 2013 14:18 UTC (Fri)
by drag (guest, #31333)
[Link] (6 responses)
I have yet to run:
'clive -f best http://www.youtube.com/watch?v=foo' and not get a WebM version of the video.
I think that one of the major reasons why you don't see more WebM by default is by the technical limitations of HTML5 versus Flash for the purposes of overlays and such things for adverts, although I could easily be mistaken.
Posted Mar 8, 2013 19:13 UTC (Fri)
by tialaramex (subscriber, #21167)
[Link]
Now try the same exact video, same browser, but found on Youtube directly, most likely you will get a message saying that you need Adobe Flash to play the video. We've seen that Youtube has a WebM version of the video, so why the message? Because Flash is used to display and control advertisements and Youtube is fuelled by advertising revenue.
Posted Mar 8, 2013 19:30 UTC (Fri)
by robert_s (subscriber, #42402)
[Link] (4 responses)
Posted Mar 11, 2013 8:06 UTC (Mon)
by jezuch (subscriber, #52988)
[Link] (3 responses)
In youtube-dl it's -f 43 or -f 45 :) By default the H.264 version is considered "best quality" and going after best quality is the default. I change that whenever I can (not all videos are transcoded to WebM).
Posted Mar 11, 2013 23:14 UTC (Mon)
by lsl (subscriber, #86508)
[Link] (2 responses)
Posted Mar 18, 2013 16:49 UTC (Mon)
by wookey (guest, #5501)
[Link] (1 responses)
All this is very tiresome. I'd love to be able to tell youtube 'show me which need flash' or even 'don't show me any that need flash as I can't play them without a load of faff.' Some reliable way to get things to either 'work for everything' or 'only show stuff that will actually work' would be a huge boon. But my understanding of how all this fits together is too weak to do much more than take what I'm given.
I'd even be happy to spend some time developing this to fix things if I had any idea how to. Does removing gnash/lightspark help because now your browser stops claiming to be able to do flash?
Posted Mar 18, 2013 17:35 UTC (Mon)
by njwhite (guest, #51848)
[Link]
Nope. Instead you just get a "you need flash to play this video" message when you try to load the video page, so no improvement on your current setup. It is enormously annoying.
Though the experience is still not as bad as when using the official flash player, which inserts adverts all over the place - I don't know how people viewing things that way tolerate it.
Posted Mar 8, 2013 8:33 UTC (Fri)
by Seegras (guest, #20463)
[Link]
The USPTO issued patents on mathematics illegally to MPEG-LA, and now somebody even takes these officially invalid patents into consideration?
Really, the only thing to do would be to take the USPTO to justice for its illegal doings.
Posted Mar 8, 2013 12:04 UTC (Fri)
by Company (guest, #57006)
[Link] (8 responses)
Or did I get that wrong? Help, I don't speak lawyer, someone explain the legal implications to me please.
Posted Mar 8, 2013 13:26 UTC (Fri)
by dowdle (subscriber, #659)
[Link]
Posted Mar 8, 2013 15:23 UTC (Fri)
by lambda (subscriber, #40735)
[Link] (6 responses)
Also, what makes you say that the license is GPL incompatible? As far as I know, the only requirement of the GPL is that if you have a patent license, you must grant the same rights to people downstream, and it sounds like this license does that. Do you have details of the agreement that indicates that it's not GPL compatible?
Posted Mar 8, 2013 21:30 UTC (Fri)
by Company (guest, #57006)
[Link] (4 responses)
Posted Mar 9, 2013 0:36 UTC (Sat)
by xnox (guest, #63320)
[Link] (1 responses)
Posted Mar 16, 2013 7:53 UTC (Sat)
by drag (guest, #31333)
[Link]
Saying that you can take VP8 code and combine it with x264 to make a patent-free H.264 implementation (or whatever your approach is) is like saying: I paid my taxes this year so I can speed on the highway without fear of getting a ticket.
Posted Mar 9, 2013 2:00 UTC (Sat)
by ARealLWN (guest, #88901)
[Link]
Posted Mar 9, 2013 3:00 UTC (Sat)
by dlang (guest, #313)
[Link]
This includes all the software that Redhat owns the patents on (or purchased a license that covers all GPL uses as well)
Posted Mar 9, 2013 21:56 UTC (Sat)
by tterribe (guest, #66972)
[Link]
There's actually an argument to be made that it confirms they're _not_ covered by these patents: http://xiphmont.livejournal.com/59893.html
Posted Mar 10, 2013 1:56 UTC (Sun)
by gdt (subscriber, #6284)
[Link]
In attempting to establish a patent pool for VP8 MPEG LA could be moving beyond the terms of that Letter. I am sure Google would argue to DOJ that MPEG LA was already operating beyond the limits of that Letter, thus by definition had breached the anti-trust laws in the view of DOJ, and thus should be prosecuted, and if the prosecution is successful, MPEG LA disbanded.
Of course should MPEG LA not seek a patent pool for VP8 and successors, then Google would not find it worthwhile to hand this "brief we have prepared" to DOJ or to pursue a private antitrust suit using the insider materials about MPEG LA which came to Google via the Motorola acquisition.
This scenario would explain the lack of a patent cross-licensing, because the issue under negotiation here isn't MPEG LA's patents, but the continuing existence of MPEG LA itself. Indirectly this would also turn MPEG LA from a revenue source for Apple, etc into a loss, since MPEG LA's legal fees would need to come from somewhere. Thus the pressure on MPEG LA to reach an agreement rather than to continue with FUD.
All of the above is, of course, speculation.
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
Wol
VP8 and MPEG LA (WebM blog)
Because I didn't see any mention of Google licensing patents back to MPEG-LA. I think that is usually mentioned if there is any cross-licensing. (Unless Google is now a member of MPEG-LA ?)
Feeling pessimistic, I wonder it MPEG-LA co-operated just to get good PR for little cost. At this point it is fairly clear that VP8 is not a serious competitor to H.264 any more, if it ever was. Simply because software and cameras spitting out H.264 natively are now ubiquitous.
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
Google license H.264 right now for Chrome and YouTube, so I guess they pay MPEG-LA a lot of money. That must give them some leverage too: "Please do us a favor and license this V8 thing of ours, or the next version of the most widely used browser and the most widely used video site will not use your codec". I am guessing there is a big shiny button at YouTube HQ with the label "convert all videos to V8".
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
You are right about the big shiny button. So perhaps there is another big shiny button right besides it that says: "Delete all H.264 videos right now" so only the VP8 copy is left. Think about it: Chrome can read it, Firefox can read it, Android can read it. Perhaps iOS or IE<=8 cannot access YouTube anymore? Tough luck.
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
http://www.ietf.org/mail-archive/web/rtcweb/current/msg06...
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
Injunctions are not a replacement for damages
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
Wol
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
Why would it be hard?
Wol
Why would it be hard?
VP8 and MPEG LA (WebM blog)
> MPEG-LA. I think that is usually mentioned if there is any cross-
> licensing. (Unless Google is now a member of MPEG-LA ?)
Thank you, Google!
Thank you, Google!
Thank you, Google!
Thank you, Google!
Thank you, Google!
Thank you, Google!
Adverts
Thank you, Google!
Thank you, Google!
Thank you, Google!
Thank you, Google!
Thank you, Google!
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
No, I don't think that there is any admission that VP8 is covered by these patents, just that if so, there is a license to use it regardless.
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
GPL and Patents
VP8 and MPEG LA (WebM blog)
VP8 and MPEG LA (WebM blog)
> patents, just that if so, there is a license to use it regardless.
VP8 and MPEG LA (WebM blog)