<?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: Current Status of H.265 (as at July 2008)</title>
	<atom:link href="http://www.h265.net/2008/07/current-status-of-h265.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.h265.net/2008/07/current-status-of-h265.html</link>
	<description>Witness the development of H.265</description>
	<lastBuildDate>Mon, 26 Jul 2010 04:00:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: forrestlem</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2386</link>
		<dc:creator>forrestlem</dc:creator>
		<pubDate>Thu, 17 Sep 2009 09:02:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2386</guid>
		<description>H.264 makes many parts predictive while KTA makes many parts adaptive. There truly seems no fundamental change comparing KTA with the previous standards. No wonder VCEG is still waiting for proposals.</description>
		<content:encoded><![CDATA[<p>H.264 makes many parts predictive while KTA makes many parts adaptive. There truly seems no fundamental change comparing KTA with the previous standards. No wonder VCEG is still waiting for proposals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jie Dong</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2382</link>
		<dc:creator>Jie Dong</dc:creator>
		<pubDate>Wed, 16 Sep 2009 02:24:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2382</guid>
		<description>Agree. It&#039;s difficult.</description>
		<content:encoded><![CDATA[<p>Agree. It&#8217;s difficult.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hui Yuan</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2381</link>
		<dc:creator>Hui Yuan</dc:creator>
		<pubDate>Mon, 14 Sep 2009 14:09:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2381</guid>
		<description>Do you really think before year 2010,  H265 can achieve its performance?

Now, the coding efficiency can be further improved up to  32% than H264/AVC High profile when all the accepted tools  were used simutaneously.  However , for nearly one year,  there are no novel coding technologies accepted by VCEG. 

Can H.265 really come ture before 2010 under traditional coding frame work?

I don&#039;t think so, and what&#039;s your opinion?

I think the H264+ can be realized.</description>
		<content:encoded><![CDATA[<p>Do you really think before year 2010,  H265 can achieve its performance?</p>
<p>Now, the coding efficiency can be further improved up to  32% than H264/AVC High profile when all the accepted tools  were used simutaneously.  However , for nearly one year,  there are no novel coding technologies accepted by VCEG. </p>
<p>Can H.265 really come ture before 2010 under traditional coding frame work?</p>
<p>I don&#8217;t think so, and what&#8217;s your opinion?</p>
<p>I think the H264+ can be realized.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mack</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2334</link>
		<dc:creator>Mack</dc:creator>
		<pubDate>Mon, 10 Aug 2009 13:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2334</guid>
		<description>I dunno, I don&#039;t work for MPEG. I think Danny is right when he speculated that the lower computational complexity is encoder-wise. It could be both for encoding and playback. It would be cool if it would take less to decode, because my machine can play 720p but not 1080p. Then again, my machine sucks and decoding is trivial on modern systems. Encoding is NOT.</description>
		<content:encoded><![CDATA[<p>I dunno, I don&#8217;t work for MPEG. I think Danny is right when he speculated that the lower computational complexity is encoder-wise. It could be both for encoding and playback. It would be cool if it would take less to decode, because my machine can play 720p but not 1080p. Then again, my machine sucks and decoding is trivial on modern systems. Encoding is NOT.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2333</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 09 Aug 2009 20:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2333</guid>
		<description>Mack, according to your reply, if the new brand codec H.265 will require half than H.264 to run fine, then basically, any encoding progress would be faster 2 times than H.264 encoding? Also, if it requires less CPU by 50%, then any machine that run 720p very high quality video that can&#039;t run 1080p H.264 video smoothly will be able to do so with H.265?</description>
		<content:encoded><![CDATA[<p>Mack, according to your reply, if the new brand codec H.265 will require half than H.264 to run fine, then basically, any encoding progress would be faster 2 times than H.264 encoding? Also, if it requires less CPU by 50%, then any machine that run 720p very high quality video that can&#8217;t run 1080p H.264 video smoothly will be able to do so with H.265?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nader</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2329</link>
		<dc:creator>nader</dc:creator>
		<pubDate>Fri, 07 Aug 2009 11:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2329</guid>
		<description>I would like to know how can I do to show the maximum gain provided by the latest version of the KTA software? in other word what&#039;s the best configuration that  I must use?
Thanks.</description>
		<content:encoded><![CDATA[<p>I would like to know how can I do to show the maximum gain provided by the latest version of the KTA software? in other word what&#8217;s the best configuration that  I must use?<br />
Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2309</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Wed, 22 Jul 2009 14:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2309</guid>
		<description>I think the 50% to 3 times range is specified for encoding.  For decoding, I can&#039;t see how it can be 50% complexity compared to H.264...</description>
		<content:encoded><![CDATA[<p>I think the 50% to 3 times range is specified for encoding.  For decoding, I can&#8217;t see how it can be 50% complexity compared to H.264&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mack</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2301</link>
		<dc:creator>Mack</dc:creator>
		<pubDate>Sat, 11 Jul 2009 09:24:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2301</guid>
		<description>No, it&#039;s planned to even be more efficient at half the CPU than H.264.
http://www.h265.net/2009/04/the-preliminary-requirements-for-ngvc.html</description>
		<content:encoded><![CDATA[<p>No, it&#8217;s planned to even be more efficient at half the CPU than H.264.<br />
<a href="http://www.h265.net/2009/04/the-preliminary-requirements-for-ngvc.html" rel="nofollow">http://www.h265.net/2009/04/the-preliminary-requirements-for-ngvc.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hoboX10</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html/comment-page-1#comment-2300</link>
		<dc:creator>hoboX10</dc:creator>
		<pubDate>Fri, 10 Jul 2009 09:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.h265.net/?p=23#comment-2300</guid>
		<description>Will h.265 be harder for a CPU to decode than h.264?</description>
		<content:encoded><![CDATA[<p>Will h.265 be harder for a CPU to decode than h.264?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
