<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Let&#8217;s get this staight &#8211; MPEG-LA&#8217;s and an x264 developer&#8217;s sabre rattling is pure FUD</title>
	<atom:link href="http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/</link>
	<description>Where the urethane hits the pavement</description>
	<lastBuildDate>Mon, 10 Oct 2011 13:34:18 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: xxx</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21426</link>
		<dc:creator>xxx</dc:creator>
		<pubDate>Sat, 22 May 2010 06:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21426</guid>
		<description>The x264 post you refer to was actually a very good technical analysis of VP8. That you read it as negative is your perception problem, it was sticking to the facts. I prefer that to hysterical rants like yours any time.

As for his patent remarks: he simply remarked that VP8&#039;s algorithms are very similar to H.264 and that he would be afraid of that. Well, that&#039;s because he&#039;s no lawyer and misses the fact that it&#039;s enough to make a small change to side-step a patent.

You&#039;ll notice that he remarks on these small differences and can&#039;t make technical sense of them. That&#039;s because they serve LEGAL purpose, not technical one.

See another (much more sensible than yours) take: http://blog.flameeyes.eu/2010/05/22/some-personal-comments-about-google-s-webm

Finally, I wouldn&#039;t worry about MPEG-LA. They were claiming the same thing about Theora for years, but could never find a single patent worth a lawsuit.</description>
		<content:encoded><![CDATA[<p>The x264 post you refer to was actually a very good technical analysis of VP8. That you read it as negative is your perception problem, it was sticking to the facts. I prefer that to hysterical rants like yours any time.</p>
<p>As for his patent remarks: he simply remarked that VP8&#8217;s algorithms are very similar to H.264 and that he would be afraid of that. Well, that&#8217;s because he&#8217;s no lawyer and misses the fact that it&#8217;s enough to make a small change to side-step a patent.</p>
<p>You&#8217;ll notice that he remarks on these small differences and can&#8217;t make technical sense of them. That&#8217;s because they serve LEGAL purpose, not technical one.</p>
<p>See another (much more sensible than yours) take: <a href="http://blog.flameeyes.eu/2010/05/22/some-personal-comments-about-google-s-webm" rel="nofollow">http://blog.flameeyes.eu/2010/05/22/some-personal-comments-about-google-s-webm</a></p>
<p>Finally, I wouldn&#8217;t worry about MPEG-LA. They were claiming the same thing about Theora for years, but could never find a single patent worth a lawsuit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Zollner</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21425</link>
		<dc:creator>Karl Zollner</dc:creator>
		<pubDate>Sat, 22 May 2010 00:52:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21425</guid>
		<description>@dobey - of course Florain did not post this here, I shared this on this blog because concerns that J5 raised about FUD regarding patent protection in regards to Webm is being raised by none other that Florian Mueller, perhaps one of the most significant persons involved in the fight against software patents in europe. 

The horrible irony is that even those fighting against software patents can hardly escape re-producing the exact same FUD from which the patent-trolls and proponents of software patents thrive and profit. I am not surprised that so many people have come out voicing FUD- after all the FUD campaign has been quite sucessfull. 

So many people have a vested (personal/financial:x264 non-olet) interest in maintaining this FUD that it gets damned near impossible to figure out what is really going on. But it is a different issue when those who are seeking to rid ourselves of software patents, themselves, get sucked into the vortex of FUD. 

Perhaps it was out of place quoting Florain on this blog site. Perhaps I violated a certain netiquette. If so simply say so and I apologize in advance. I merely did this to illustrate what I perceive is exactly what J5 is talking about. Since posting this Florian has responded to my post, and I to his follow up- we do not see eye to eye, but I still respect his work against software patents in europe.</description>
		<content:encoded><![CDATA[<p>@dobey &#8211; of course Florain did not post this here, I shared this on this blog because concerns that J5 raised about FUD regarding patent protection in regards to Webm is being raised by none other that Florian Mueller, perhaps one of the most significant persons involved in the fight against software patents in europe. </p>
<p>The horrible irony is that even those fighting against software patents can hardly escape re-producing the exact same FUD from which the patent-trolls and proponents of software patents thrive and profit. I am not surprised that so many people have come out voicing FUD- after all the FUD campaign has been quite sucessfull. </p>
<p>So many people have a vested (personal/financial:x264 non-olet) interest in maintaining this FUD that it gets damned near impossible to figure out what is really going on. But it is a different issue when those who are seeking to rid ourselves of software patents, themselves, get sucked into the vortex of FUD. </p>
<p>Perhaps it was out of place quoting Florain on this blog site. Perhaps I violated a certain netiquette. If so simply say so and I apologize in advance. I merely did this to illustrate what I perceive is exactly what J5 is talking about. Since posting this Florian has responded to my post, and I to his follow up- we do not see eye to eye, but I still respect his work against software patents in europe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J5</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21422</link>
		<dc:creator>J5</dc:creator>
		<pubDate>Fri, 21 May 2010 21:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21422</guid>
		<description>@dobey - people (those who dislike being forced to use h.264) aren&#039;t afraid that the license is viral.  They are afraid of the actual content of the license which is pretty hostile (and more to the point they are afraid of the patents.  The license just hint to cases where they may utilize their patent portfolio). GPL&#039;s viral nature only pertains to copying code, not methods.  Someone is free to clone any GPL code as long as they don&#039;t plagiarize the original work.  They can utilizes the binary in any way they wish as long as they provide access to the source if they distribute it.  Software copyright is pretty well defined and narrow where software patents aren&#039;t.  Please don&#039;t compare apples to oranges.</description>
		<content:encoded><![CDATA[<p>@dobey &#8211; people (those who dislike being forced to use h.264) aren&#8217;t afraid that the license is viral.  They are afraid of the actual content of the license which is pretty hostile (and more to the point they are afraid of the patents.  The license just hint to cases where they may utilize their patent portfolio). GPL&#8217;s viral nature only pertains to copying code, not methods.  Someone is free to clone any GPL code as long as they don&#8217;t plagiarize the original work.  They can utilizes the binary in any way they wish as long as they provide access to the source if they distribute it.  Software copyright is pretty well defined and narrow where software patents aren&#8217;t.  Please don&#8217;t compare apples to oranges.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dobey</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21421</link>
		<dc:creator>dobey</dc:creator>
		<pubDate>Fri, 21 May 2010 20:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21421</guid>
		<description>@Karl, I think you posted that reply in the wrong place? Florian hasn&#039;t commented on this post at all. Perhaps you want to complain to him on slashdot instead? :)</description>
		<content:encoded><![CDATA[<p>@Karl, I think you posted that reply in the wrong place? Florian hasn&#8217;t commented on this post at all. Perhaps you want to complain to him on slashdot instead? <img src='http://www.j5live.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dash</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21420</link>
		<dc:creator>Dash</dc:creator>
		<pubDate>Fri, 21 May 2010 20:23:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21420</guid>
		<description>I don&#039;t want to sound too conspiratorial, but are all you guys defending the open source x264 project aware that they&#039;re contacting all the copyright holders so that they can sell exceptions to the GPL? I don&#039;t think that&#039;s a terrible thing on its own, but it leads to a bad taste when he goes on to spread patent FUD and make bizarre claims about other folk&#039;s open source code that he sees as competition. For example:

&quot;The assembly code is much worse, with staggering levels of copy-paste coding, some completely useless instructions that do nothing at all, unaligned loads/stores to what-should-be aligned data structures, and a few functions that are simply written in unfathomably roundabout (and slower) ways.  While the C code isn’t half bad, the assembly is clearly written by retarded monkeys.&quot;

So the assembly is slow, slow, stupid and slow. Got that? I wonder how much faster it&#039;ll get when rewritten by someone with a clue?

&quot;the current one seems to be reasonably well-optimized and has SIMD assembly code for almost all major DSP functions, so I doubt it will get that much faster.&quot;

Oh, I see, written by &quot;retarded monkeys&quot; yet they&#039;ve left absolutely no room for optimization as they&#039;ve squeezed ever last bit of performance out of the processor. Seems like VP8 can&#039;t really win in this review. And yet if you cut through the hyperbole, he actually seems to think VP8 has a solid foundation. Should be interesting to see how this develops.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t want to sound too conspiratorial, but are all you guys defending the open source x264 project aware that they&#8217;re contacting all the copyright holders so that they can sell exceptions to the GPL? I don&#8217;t think that&#8217;s a terrible thing on its own, but it leads to a bad taste when he goes on to spread patent FUD and make bizarre claims about other folk&#8217;s open source code that he sees as competition. For example:</p>
<p>&#8220;The assembly code is much worse, with staggering levels of copy-paste coding, some completely useless instructions that do nothing at all, unaligned loads/stores to what-should-be aligned data structures, and a few functions that are simply written in unfathomably roundabout (and slower) ways.  While the C code isn’t half bad, the assembly is clearly written by retarded monkeys.&#8221;</p>
<p>So the assembly is slow, slow, stupid and slow. Got that? I wonder how much faster it&#8217;ll get when rewritten by someone with a clue?</p>
<p>&#8220;the current one seems to be reasonably well-optimized and has SIMD assembly code for almost all major DSP functions, so I doubt it will get that much faster.&#8221;</p>
<p>Oh, I see, written by &#8220;retarded monkeys&#8221; yet they&#8217;ve left absolutely no room for optimization as they&#8217;ve squeezed ever last bit of performance out of the processor. Seems like VP8 can&#8217;t really win in this review. And yet if you cut through the hyperbole, he actually seems to think VP8 has a solid foundation. Should be interesting to see how this develops.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Zollner</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21419</link>
		<dc:creator>Karl Zollner</dc:creator>
		<pubDate>Fri, 21 May 2010 19:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21419</guid>
		<description>In response to a post by Florian Mueller of European software patent fame who said :

&quot;I try to avoid &quot;See I Told Ya So&quot; types of posts, but in this case SCNR: WebM/VP8 patent risk for software developers&quot; [slashdot.org] (and I previously made that suggestion on my blog in this post on video codecs [blogspot.com])

I&#039;m all for open-sourcing useful program code but the question here is whether it&#039;s fair for Google to expose an entire community, including the commercial adopters of open source, to this kind of risk. The situation surrounding Android serves as a warning. Google is unfortunately in favor of software patents and doesn&#039;t do anything against the problem. They&#039;re entitled to their patent strategy. But it&#039;s important that third parties don&#039;t run into patent problems in reliance upon Google&#039;s vague promises.

If Google really believed that WebM/VP8 was safe from a patent perspective, then why in the world don&#039;t its WebM license terms contain a hold-harmless clause or at least some basic indemnification (less value than holding harmless but better than nothing) in favor of developers adopting it?

People should think twice (at least!) before relying on any vague promises and they should also consider that Google isn&#039;t the patent powerhouse that could start a &quot;pissing contest&quot; with the major contributors to the MPEG LA pool. I explained Google&#039;s limits in that regard in this recent slashdot comment, The idea of Google countersuing isn&#039;t realistic [slashdot.org].&quot;

This is my response: 

Listen you can&#039;t speak out of both sides of your mouth at once. You cannot claim to be against software patents and vilify some group for failing to provide patent indemnification in the same breath. Providing patent indemnification is nothing other than racketeering, those purporting to do so are rackets(ie. MPEG-LA). I applaud the work of those who fight against software patents. But when you argue that Google should be providing patent indemnification you are actively undermining any strategy to rid the world of software patents. Shy of getting the laws regarding software patents changed(ie prohibiting them in the first place), the kind of patent provisions provided in Googles new license for webm *is* the most effective way of fighting software patents. Because of the shitty patent system in place whole industries have arisen which produce nothing other than Fear Uncertainty and Doubt.

In fact, it is hard to speak about patents *at all* without engaging in the same FUD-because FUD is the medium of the existence of patent speculator industry(of which Larry Horn, CEO of MPEG-LA, is a known patent-troll par-excellence). One aspect of the fight against software patents is the desire to protect the *users* from being sued into oblivion by patent holding entities(either patent-trolls or companies engaging in patent-trolling). Yet claiming that *users* should be indemnified *is* the raison-d&#039;etre of patent racketeering industry. So if you argue that Google is failing to protect *users* you are, in stating such, proving, providing, and furthering the self-justification that such patent rackets(MPEG-LA) use themselves. And in so doing your words of caution and concern are nothing more than additional weapons in the arsenals of thepatent rackets ideological propaganda. The laws concerning patents(what is patentable, the terms of patents etc.) will only change once the patent situation in general has been sufficiently defused so as to limit the actual perceived value of patents. By insisting that *uers* should be indemnified one is ratcheting up the perceived patent threat, artificially inflating the value of said patents, which directly works against the goal of eliminating software patents. As long as everyone is terrified of potential patent suits those who support software patents already have their case(ie. why we supposedly need software patents) made for them by the very perceived fear. We must break this cycle. Googles new license goes an awful long way towards defusing the actual FUD atmosphere.

Stating that Google is exposing the community to patent litigation is literally the exact opposite of what is really happening. By getting extremely broad industry support for webm within hours of launching webm and coupling this support with patent provisions in the license which state that any filing of patent litigation against webm(vp8) will result in termination of the usage rights envisioned by license, they have dramatically reduced the likelihood of any kind of patent litigation. The effect of this is unequivocally, a *defusing* of the already existing FUD-bases patent insanity. As of this writing those who promote software patents will have more difficulty justifying why we need such patents and the patent rackets are struggling to find some kind of rhetorical self-justification with which they can continue to sell their poisonous FUD.

Flo I really do respect your work. But you are wrong on this one. And not only are you wrong, but you are dangerously close to speaking out of both sides of your mouth. Choose which side you are on. If you raise FUD be aware of what master you are serving.</description>
		<content:encoded><![CDATA[<p>In response to a post by Florian Mueller of European software patent fame who said :</p>
<p>&#8220;I try to avoid &#8220;See I Told Ya So&#8221; types of posts, but in this case SCNR: WebM/VP8 patent risk for software developers&#8221; [slashdot.org] (and I previously made that suggestion on my blog in this post on video codecs [blogspot.com])</p>
<p>I&#8217;m all for open-sourcing useful program code but the question here is whether it&#8217;s fair for Google to expose an entire community, including the commercial adopters of open source, to this kind of risk. The situation surrounding Android serves as a warning. Google is unfortunately in favor of software patents and doesn&#8217;t do anything against the problem. They&#8217;re entitled to their patent strategy. But it&#8217;s important that third parties don&#8217;t run into patent problems in reliance upon Google&#8217;s vague promises.</p>
<p>If Google really believed that WebM/VP8 was safe from a patent perspective, then why in the world don&#8217;t its WebM license terms contain a hold-harmless clause or at least some basic indemnification (less value than holding harmless but better than nothing) in favor of developers adopting it?</p>
<p>People should think twice (at least!) before relying on any vague promises and they should also consider that Google isn&#8217;t the patent powerhouse that could start a &#8220;pissing contest&#8221; with the major contributors to the MPEG LA pool. I explained Google&#8217;s limits in that regard in this recent slashdot comment, The idea of Google countersuing isn&#8217;t realistic [slashdot.org].&#8221;</p>
<p>This is my response: </p>
<p>Listen you can&#8217;t speak out of both sides of your mouth at once. You cannot claim to be against software patents and vilify some group for failing to provide patent indemnification in the same breath. Providing patent indemnification is nothing other than racketeering, those purporting to do so are rackets(ie. MPEG-LA). I applaud the work of those who fight against software patents. But when you argue that Google should be providing patent indemnification you are actively undermining any strategy to rid the world of software patents. Shy of getting the laws regarding software patents changed(ie prohibiting them in the first place), the kind of patent provisions provided in Googles new license for webm *is* the most effective way of fighting software patents. Because of the shitty patent system in place whole industries have arisen which produce nothing other than Fear Uncertainty and Doubt.</p>
<p>In fact, it is hard to speak about patents *at all* without engaging in the same FUD-because FUD is the medium of the existence of patent speculator industry(of which Larry Horn, CEO of MPEG-LA, is a known patent-troll par-excellence). One aspect of the fight against software patents is the desire to protect the *users* from being sued into oblivion by patent holding entities(either patent-trolls or companies engaging in patent-trolling). Yet claiming that *users* should be indemnified *is* the raison-d&#8217;etre of patent racketeering industry. So if you argue that Google is failing to protect *users* you are, in stating such, proving, providing, and furthering the self-justification that such patent rackets(MPEG-LA) use themselves. And in so doing your words of caution and concern are nothing more than additional weapons in the arsenals of thepatent rackets ideological propaganda. The laws concerning patents(what is patentable, the terms of patents etc.) will only change once the patent situation in general has been sufficiently defused so as to limit the actual perceived value of patents. By insisting that *uers* should be indemnified one is ratcheting up the perceived patent threat, artificially inflating the value of said patents, which directly works against the goal of eliminating software patents. As long as everyone is terrified of potential patent suits those who support software patents already have their case(ie. why we supposedly need software patents) made for them by the very perceived fear. We must break this cycle. Googles new license goes an awful long way towards defusing the actual FUD atmosphere.</p>
<p>Stating that Google is exposing the community to patent litigation is literally the exact opposite of what is really happening. By getting extremely broad industry support for webm within hours of launching webm and coupling this support with patent provisions in the license which state that any filing of patent litigation against webm(vp8) will result in termination of the usage rights envisioned by license, they have dramatically reduced the likelihood of any kind of patent litigation. The effect of this is unequivocally, a *defusing* of the already existing FUD-bases patent insanity. As of this writing those who promote software patents will have more difficulty justifying why we need such patents and the patent rackets are struggling to find some kind of rhetorical self-justification with which they can continue to sell their poisonous FUD.</p>
<p>Flo I really do respect your work. But you are wrong on this one. And not only are you wrong, but you are dangerously close to speaking out of both sides of your mouth. Choose which side you are on. If you raise FUD be aware of what master you are serving.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dobey</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21418</link>
		<dc:creator>dobey</dc:creator>
		<pubDate>Fri, 21 May 2010 19:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21418</guid>
		<description>@J5 Well, based on personal experience, I probably wouldn&#039;t trust the lawyers on such issues, either. Dealing with Novell&#039;s legal department, even just trying to get clarification on licensing for Tango Icon Theme, was a horrible pain in the ass that never should have been.

I wasn&#039;t saying we should ignore the issues. I was saying we *ARE* ignoring the issues. The MPEG-LA licensing is not all that different from the GPL. The fact that it&#039;s a patented proprietary codec we&#039;re talking about is what has everyone up in arms. If the license was exactly the same as it is now, but the codec was in fact more liberal itself (but still required the viral distribution), we wouldn&#039;t be seeing all these complaints. People would in general just ignore the problem until they started being sued (if they ever actually did get sued).

In fact, most if not all of the content on YouTube is violating the MPEG-LA license for h.264 content, since they&#039;re not distributing it in h.264 in the majority of cases. And fighting the viral license piece is going to present a much larger problem for the FSF, if anyone does in fact do so, and succeed. Because, if the viral licensing is challenged in court, and found to be invalid, it means that the viral licensing scheme of the GPL will also likely be invalidated. That would be a very interesting court case, though. :)</description>
		<content:encoded><![CDATA[<p>@J5 Well, based on personal experience, I probably wouldn&#8217;t trust the lawyers on such issues, either. Dealing with Novell&#8217;s legal department, even just trying to get clarification on licensing for Tango Icon Theme, was a horrible pain in the ass that never should have been.</p>
<p>I wasn&#8217;t saying we should ignore the issues. I was saying we *ARE* ignoring the issues. The MPEG-LA licensing is not all that different from the GPL. The fact that it&#8217;s a patented proprietary codec we&#8217;re talking about is what has everyone up in arms. If the license was exactly the same as it is now, but the codec was in fact more liberal itself (but still required the viral distribution), we wouldn&#8217;t be seeing all these complaints. People would in general just ignore the problem until they started being sued (if they ever actually did get sued).</p>
<p>In fact, most if not all of the content on YouTube is violating the MPEG-LA license for h.264 content, since they&#8217;re not distributing it in h.264 in the majority of cases. And fighting the viral license piece is going to present a much larger problem for the FSF, if anyone does in fact do so, and succeed. Because, if the viral licensing is challenged in court, and found to be invalid, it means that the viral licensing scheme of the GPL will also likely be invalidated. That would be a very interesting court case, though. <img src='http://www.j5live.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Williamson</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21417</link>
		<dc:creator>Adam Williamson</dc:creator>
		<pubDate>Fri, 21 May 2010 18:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21417</guid>
		<description>You say Google is confident it&#039;s okay to ship VP8. I rather doubt that assertion.

Take a look at it from a cynical Google lawyer&#039;s perspective. Right now, Google already pays MPEG-LA to license h.264, they have that cost on their books, and the arrangement exists.

Things can go one of two ways. Either way, Google benefits.

1: MPEG-LA somehow doesn&#039;t manage to sue someone for using VP8. Result? Google lauded as saviour of free world, Google-owned VP8 codec goes global, Google saves a bit of pocket change (the h.264 license fee).

2: MPEG-LA does successfully demonstrate that VP8 infringes its patents. Result? Google gets some good press (&quot;plucky Google tries to save world from patent trolls, but is brought down by evil MPEG&quot;), and gets a license from MPEG-LA to go right on using VP8 wherever it wants. Probably they&#039;d barely have to pay an extra penny, I doubt MPEG-LA would be able to screw much more money out of them when they&#039;re already licensing all the same patents for h.264 use.

So, sure, Google is talking a good fight about VP8 being patent-free. But if it turns out it hasn&#039;t, what&#039;s Google lost? Just about nothing. I doubt anyone at Google would lose much sleep if it turns out their public position on VP8&#039;s patentedness turns out to be incorrect.</description>
		<content:encoded><![CDATA[<p>You say Google is confident it&#8217;s okay to ship VP8. I rather doubt that assertion.</p>
<p>Take a look at it from a cynical Google lawyer&#8217;s perspective. Right now, Google already pays MPEG-LA to license h.264, they have that cost on their books, and the arrangement exists.</p>
<p>Things can go one of two ways. Either way, Google benefits.</p>
<p>1: MPEG-LA somehow doesn&#8217;t manage to sue someone for using VP8. Result? Google lauded as saviour of free world, Google-owned VP8 codec goes global, Google saves a bit of pocket change (the h.264 license fee).</p>
<p>2: MPEG-LA does successfully demonstrate that VP8 infringes its patents. Result? Google gets some good press (&#8221;plucky Google tries to save world from patent trolls, but is brought down by evil MPEG&#8221;), and gets a license from MPEG-LA to go right on using VP8 wherever it wants. Probably they&#8217;d barely have to pay an extra penny, I doubt MPEG-LA would be able to screw much more money out of them when they&#8217;re already licensing all the same patents for h.264 use.</p>
<p>So, sure, Google is talking a good fight about VP8 being patent-free. But if it turns out it hasn&#8217;t, what&#8217;s Google lost? Just about nothing. I doubt anyone at Google would lose much sleep if it turns out their public position on VP8&#8217;s patentedness turns out to be incorrect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: twilightomni</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21415</link>
		<dc:creator>twilightomni</dc:creator>
		<pubDate>Fri, 21 May 2010 18:05:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21415</guid>
		<description>FUD has different contexts.  The world of digital video is separate from, ex, Linux &quot;kernel patent infringement&quot; FUD.  In video, the major players are research organizations and universities, not open source players, and major foundations of the science may already have been patented. [I&#039;m not a lawyer in the field, so I only qualify here.  But I do so with more realism than your article above.]

*Any* video compression technique may be covered by a previous invention or patent.  It&#039;s not nebulous - it&#039;s likely.  There are only so many known video compression techniques.  Pretending that the threat of infringement is nonexistent isn&#039;t a solution.  I don&#039;t like the MPEG license agreements, but they were created as a *solution* for businesses to minimize their patent risk with video technologies.

And some major businesses do want to buy in the patent pool protection model.  Is the MPEG Group selling snake oil?  Considering the American intellectual landscape, maybe not.  The fears are not unfounded.

It&#039;s not about the codecs, it&#039;s about the intellectual status of video compression itself.  MPEG isn&#039;t the enemy.  MPEG is shades of grey.  The real adversary is video patents, and a brand new codec that still uses old video compression techniques might not be the answer.</description>
		<content:encoded><![CDATA[<p>FUD has different contexts.  The world of digital video is separate from, ex, Linux &#8220;kernel patent infringement&#8221; FUD.  In video, the major players are research organizations and universities, not open source players, and major foundations of the science may already have been patented. [I'm not a lawyer in the field, so I only qualify here.  But I do so with more realism than your article above.]</p>
<p>*Any* video compression technique may be covered by a previous invention or patent.  It&#8217;s not nebulous &#8211; it&#8217;s likely.  There are only so many known video compression techniques.  Pretending that the threat of infringement is nonexistent isn&#8217;t a solution.  I don&#8217;t like the MPEG license agreements, but they were created as a *solution* for businesses to minimize their patent risk with video technologies.</p>
<p>And some major businesses do want to buy in the patent pool protection model.  Is the MPEG Group selling snake oil?  Considering the American intellectual landscape, maybe not.  The fears are not unfounded.</p>
<p>It&#8217;s not about the codecs, it&#8217;s about the intellectual status of video compression itself.  MPEG isn&#8217;t the enemy.  MPEG is shades of grey.  The real adversary is video patents, and a brand new codec that still uses old video compression techniques might not be the answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J5</title>
		<link>http://www.j5live.com/2010/05/21/lets-get-this-staight-mpeg-las-and-x264-developers/comment-page-1/#comment-21414</link>
		<dc:creator>J5</dc:creator>
		<pubDate>Fri, 21 May 2010 18:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.j5live.com/?p=791#comment-21414</guid>
		<description>woops sorry for the double posting, my internet was going haywire.  I think the router had a bad DNS entry. 

Had to remove the other post which had a comment on it from Scott Dowdle:

&lt;em&gt;Just a clarification.  I think in many instances above, you refer to &quot;x264&quot; when you really mean &quot;H.264&quot;.  &lt;a href=&quot;http://en.wikipedia.org/wiki/X264&quot; rel=&quot;nofollow&quot;&gt;x264&lt;/a&gt; *IS* free software licensed under the GPL.&lt;/em&gt;

While the license may be GPL it does not make it free to use due to known patent concerns.  This makes it explicitly non-free. e.g. it is not in the spirit of the GPL and as such is not shipped by Debian or Fedora by default.</description>
		<content:encoded><![CDATA[<p>woops sorry for the double posting, my internet was going haywire.  I think the router had a bad DNS entry. </p>
<p>Had to remove the other post which had a comment on it from Scott Dowdle:</p>
<p><em>Just a clarification.  I think in many instances above, you refer to &#8220;x264&#8243; when you really mean &#8220;H.264&#8243;.  <a href="http://en.wikipedia.org/wiki/X264" rel="nofollow">x264</a> *IS* free software licensed under the GPL.</em></p>
<p>While the license may be GPL it does not make it free to use due to known patent concerns.  This makes it explicitly non-free. e.g. it is not in the spirit of the GPL and as such is not shipped by Debian or Fedora by default.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

