<?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"
	>
<channel>
	<title>Comments on: Empowering Content Creators, Not Platforms With H.264</title>
	<atom:link href="http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/</link>
	<description>This is the blog of Brooks Andrus. Here, at irregular intervals, you may find digital noise centered around the activities of an early 21st century technologist. I work for TechSmith Corporation, but this web space and the views found on it are entirely my own.</description>
	<pubDate>Thu, 20 Nov 2008 18:49:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Convergence: Silverlight 3 To Support h.264 Video</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-48554</link>
		<dc:creator>Convergence: Silverlight 3 To Support h.264 Video</dc:creator>
		<pubDate>Wed, 10 Sep 2008 05:02:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-48554</guid>
		<description>[...] creators and the industry as a whole out. It&#8217;s a move away from vendor lock-in and toward customer empowerment. Microsoft has big plans for Silverlight. They want it to be embedded on a lot of platforms (mobile [...]</description>
		<content:encoded><![CDATA[<p>[...] creators and the industry as a whole out. It&#8217;s a move away from vendor lock-in and toward customer empowerment. Microsoft has big plans for Silverlight. They want it to be embedded on a lot of platforms (mobile [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brooks</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45938</link>
		<dc:creator>Brooks</dc:creator>
		<pubDate>Thu, 22 May 2008 14:52:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45938</guid>
		<description>@Bill - Yep, that's me, but thanks for making fun. ;-)</description>
		<content:encoded><![CDATA[<p>@Bill - Yep, that&#8217;s me, but thanks for making fun. ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Scanlon</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45936</link>
		<dc:creator>Bill Scanlon</dc:creator>
		<pubDate>Thu, 22 May 2008 14:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45936</guid>
		<description>Is that you're voice on the video?  Doesn't sound like you.

Sounds like you doing a video narrator voice...which I guess it is.</description>
		<content:encoded><![CDATA[<p>Is that you&#8217;re voice on the video?  Doesn&#8217;t sound like you.</p>
<p>Sounds like you doing a video narrator voice&#8230;which I guess it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brooks</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45762</link>
		<dc:creator>Brooks</dc:creator>
		<pubDate>Mon, 19 May 2008 20:59:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45762</guid>
		<description>@Tony - Do I expect Microsoft to drop VC-1? No. 

Do they risk continuing to be irrelevant in the video space as long as the go it alone? Yes.

Should we expect big business to cooperate for the greater good? Yes. In fact, in the video broadcast industry they've been doing this for a very long time. I think you've seen the video industry as a whole recognize that no one is going to own the entire stack (MS is about the only one refusing to recognize this at  this point) and that competing formats hurt vendors and consumers. While format competition still flairs up from time to time (BluRay vs HD-DVD) there's tremendous pressure for consolidation to occur -- the paralysis of multiple distribution formats is just too high.

I would argue we're well past the tipping point on the web video front (Adobe bringing h.264 to Flash was the nail in the coffin). Everybody, except for MS has conceded and is backing / supporting h.264 and MS isn't even a legit player in the web video playback market (Flash Player has 95% market share). This is why I see the burden being on MS rather than on everyone else (if they were talking from a position strength -- 95% market share -- it would alter the discussion a bit). It's up to MS to make themselves relevant.</description>
		<content:encoded><![CDATA[<p>@Tony - Do I expect Microsoft to drop VC-1? No. </p>
<p>Do they risk continuing to be irrelevant in the video space as long as the go it alone? Yes.</p>
<p>Should we expect big business to cooperate for the greater good? Yes. In fact, in the video broadcast industry they&#8217;ve been doing this for a very long time. I think you&#8217;ve seen the video industry as a whole recognize that no one is going to own the entire stack (MS is about the only one refusing to recognize this at  this point) and that competing formats hurt vendors and consumers. While format competition still flairs up from time to time (BluRay vs HD-DVD) there&#8217;s tremendous pressure for consolidation to occur &#8212; the paralysis of multiple distribution formats is just too high.</p>
<p>I would argue we&#8217;re well past the tipping point on the web video front (Adobe bringing h.264 to Flash was the nail in the coffin). Everybody, except for MS has conceded and is backing / supporting h.264 and MS isn&#8217;t even a legit player in the web video playback market (Flash Player has 95% market share). This is why I see the burden being on MS rather than on everyone else (if they were talking from a position strength &#8212; 95% market share &#8212; it would alter the discussion a bit). It&#8217;s up to MS to make themselves relevant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Dunckel</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45709</link>
		<dc:creator>Tony Dunckel</dc:creator>
		<pubDate>Sun, 18 May 2008 20:35:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45709</guid>
		<description>Brooks - you're singing to the choir here, but MS has a lot of influence across the various parts of the puzzle.  Is it realistic to that the big 3 (Microsoft, Adobe and Apple) will all concede and centralize around the same format?  Perhaps a better way to phrase the question is can we really expect big business to make a play for the greater good of the consumer and that seamless experience we all think is nirvana at this point?</description>
		<content:encoded><![CDATA[<p>Brooks - you&#8217;re singing to the choir here, but MS has a lot of influence across the various parts of the puzzle.  Is it realistic to that the big 3 (Microsoft, Adobe and Apple) will all concede and centralize around the same format?  Perhaps a better way to phrase the question is can we really expect big business to make a play for the greater good of the consumer and that seamless experience we all think is nirvana at this point?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: And He Blogs &#187; links for 2008-05-17</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45650</link>
		<dc:creator>And He Blogs &#187; links for 2008-05-17</dc:creator>
		<pubDate>Sat, 17 May 2008 18:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45650</guid>
		<description>[...] Empowering Content Creators, Not Platforms With H.264 (tags: andrus flv h.264 video webcast flash) [...]</description>
		<content:encoded><![CDATA[<p>[...] Empowering Content Creators, Not Platforms With H.264 (tags: andrus flv h.264 video webcast flash) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brooks</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45584</link>
		<dc:creator>Brooks</dc:creator>
		<pubDate>Fri, 16 May 2008 20:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45584</guid>
		<description>@Trav - Great link bro. Hardware is definitely more of an issue now that there's increasing emphasis on battery life in laptops and smaller form factor mobile devices. On the desktop front it was completely reasonable to rely on pure software decoding since CPU speed increases were a given and power was an unquestioned constant. 

I'm definitely looking forward to more chip driven decoding and looking to vendors to have the hooks / APIs that allow 3rd party software to directly pipe the decoding / encoding to the dedicated hardware. Content creation apps are going to be getting significantly richer which is great news.</description>
		<content:encoded><![CDATA[<p>@Trav - Great link bro. Hardware is definitely more of an issue now that there&#8217;s increasing emphasis on battery life in laptops and smaller form factor mobile devices. On the desktop front it was completely reasonable to rely on pure software decoding since CPU speed increases were a given and power was an unquestioned constant. </p>
<p>I&#8217;m definitely looking forward to more chip driven decoding and looking to vendors to have the hooks / APIs that allow 3rd party software to directly pipe the decoding / encoding to the dedicated hardware. Content creation apps are going to be getting significantly richer which is great news.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brooks</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45582</link>
		<dc:creator>Brooks</dc:creator>
		<pubDate>Fri, 16 May 2008 20:02:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45582</guid>
		<description>@Ryan - Thanks for the props. I'm using the Kimili plugin for WordPress to do the embedding, but I don't believe that has anything to do with the enclosure showing up in the feed. Because of the popularity of podcasting / blogging hybrids, WordPress is pretty good about sniffing out podcast formats and writing the enclosure tags into the feed. Anytime you reference an  .mp4, mp3, .m4a, .m4b, or .m4v file in a post WP will do the work for you. 

This is one of the reasons why I was a bit bummed to see Adobe moving forward with the f4v naming convention. I believe I understand some of the reasoning, but it means you won't leverage the existing interoperability there is right out of the gate. I definitely want to hear more color from you guys about this decision.</description>
		<content:encoded><![CDATA[<p>@Ryan - Thanks for the props. I&#8217;m using the Kimili plugin for WordPress to do the embedding, but I don&#8217;t believe that has anything to do with the enclosure showing up in the feed. Because of the popularity of podcasting / blogging hybrids, WordPress is pretty good about sniffing out podcast formats and writing the enclosure tags into the feed. Anytime you reference an  .mp4, mp3, .m4a, .m4b, or .m4v file in a post WP will do the work for you. </p>
<p>This is one of the reasons why I was a bit bummed to see Adobe moving forward with the f4v naming convention. I believe I understand some of the reasoning, but it means you won&#8217;t leverage the existing interoperability there is right out of the gate. I definitely want to hear more color from you guys about this decision.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis Stoliker</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45580</link>
		<dc:creator>Travis Stoliker</dc:creator>
		<pubDate>Fri, 16 May 2008 19:05:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45580</guid>
		<description>Great post, Brooks. I agree H.264 is a game changer. I can't wait until the H.264 chips start showing up in laptops and other components for hardware decoding/encoding. 

http://www.pbs.org/cringely/pulpit/2007/pulpit_20070308_001806.html</description>
		<content:encoded><![CDATA[<p>Great post, Brooks. I agree H.264 is a game changer. I can&#8217;t wait until the H.264 chips start showing up in laptops and other components for hardware decoding/encoding. </p>
<p><a href="http://www.pbs.org/cringely/pulpit/2007/pulpit_20070308_001806.html" rel="nofollow">http://www.pbs.org/cringely/pulpit/2007/pulpit_20070308_001806.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Stewart</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45579</link>
		<dc:creator>Ryan Stewart</dc:creator>
		<pubDate>Fri, 16 May 2008 18:32:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45579</guid>
		<description>Excellent post, and I agree.

How did you embed the video? It showed up in my feed reader as just a regular MP4 embed that you could download. I thought it was a nice touch to have the visible Flash movie and the H.264 download so I wondered if you had to do anything special.

Love the blog, it's becoming one of my favorites.
=Ryan
rstewart@adobe.com</description>
		<content:encoded><![CDATA[<p>Excellent post, and I agree.</p>
<p>How did you embed the video? It showed up in my feed reader as just a regular MP4 embed that you could download. I thought it was a nice touch to have the visible Flash movie and the H.264 download so I wondered if you had to do anything special.</p>
<p>Love the blog, it&#8217;s becoming one of my favorites.<br />
=Ryan<br />
<a href="mailto:rstewart@adobe.com">rstewart@adobe.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mateusz</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45558</link>
		<dc:creator>Mateusz</dc:creator>
		<pubDate>Fri, 16 May 2008 09:20:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45558</guid>
		<description>Naturally there are many codecs which are free , look at OGG theora, or dirac.</description>
		<content:encoded><![CDATA[<p>Naturally there are many codecs which are free , look at OGG theora, or dirac.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brooks</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45554</link>
		<dc:creator>Brooks</dc:creator>
		<pubDate>Fri, 16 May 2008 08:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45554</guid>
		<description>@Thijs - the last time I checked On2 held patents for the vp6 codec that flv uses. FFMPEG has an implementation of the h.263 codec, but that doesn't mean its unencumbered (Macromedia licensed h.263 aka "Spark" from Sorenson). So, I'm not certain you can assert flv is free. 

Maybe someday, there will be a killer, patent free, open source codec for video, but I'm not holding my breath (Sun announced their intent to work on just such a thing recently, but their media track record stinks...remember JMF).</description>
		<content:encoded><![CDATA[<p>@Thijs - the last time I checked On2 held patents for the vp6 codec that flv uses. FFMPEG has an implementation of the h.263 codec, but that doesn&#8217;t mean its unencumbered (Macromedia licensed h.263 aka &#8220;Spark&#8221; from Sorenson). So, I&#8217;m not certain you can assert flv is free. </p>
<p>Maybe someday, there will be a killer, patent free, open source codec for video, but I&#8217;m not holding my breath (Sun announced their intent to work on just such a thing recently, but their media track record stinks&#8230;remember JMF).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thijs</title>
		<link>http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45552</link>
		<dc:creator>Thijs</dc:creator>
		<pubDate>Fri, 16 May 2008 08:12:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.brooksandrus.com/blog/2008/05/16/empowering-content-creators-not-platforms-with-h264/#comment-45552</guid>
		<description>In your video you ask why use anything else then h264, and one answer could be: FLV is free and doesn't contain any patent or licensing restrictions, while H264 requires you to pay royalties for every video. From &lt;a href='http://en.wikipedia.org/wiki/H.264#Patent_licensing' rel="nofollow"&gt;Wikipedia&lt;/a&gt;: "In countries where software patent regulations are upheld, the vendors of products which make use of H.264/AVC are expected to pay patent licensing royalties for the patented technology that their products use"</description>
		<content:encoded><![CDATA[<p>In your video you ask why use anything else then h264, and one answer could be: FLV is free and doesn&#8217;t contain any patent or licensing restrictions, while H264 requires you to pay royalties for every video. From <a href='http://en.wikipedia.org/wiki/H.264#Patent_licensing' rel="nofollow">Wikipedia</a>: &#8220;In countries where software patent regulations are upheld, the vendors of products which make use of H.264/AVC are expected to pay patent licensing royalties for the patented technology that their products use&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
