<?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: H.265 Gets Approved &#8211; Focuses on High-Quality at Low Bandwidth</title>
	<atom:link href="http://techgage.com/news/h-265-gets-approved-focuses-on-high-quality-at-low-bandwidth/feed/" rel="self" type="application/rss+xml" />
	<link>http://techgage.com/news/h-265-gets-approved-focuses-on-high-quality-at-low-bandwidth/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=h-265-gets-approved-focuses-on-high-quality-at-low-bandwidth</link>
	<description>PC enthusiasts one-stop resource for high-quality reviews, articles and current technology news.</description>
	<lastBuildDate>Tue, 21 May 2013 22:56:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: RainMotorsports</title>
		<link>http://techgage.com/news/h-265-gets-approved-focuses-on-high-quality-at-low-bandwidth/#comment-727</link>
		<dc:creator>RainMotorsports</dc:creator>
		<pubDate>Mon, 28 Jan 2013 17:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://techgage.com/?post_type=news&#038;p=18360#comment-727</guid>
		<description><![CDATA[Well of course H.265 is aimed at mobile so processor demand is not necessarily a luxury when you consider you want to record on the device to it.  But I am with you.  I would love to sacrifice time encoding for better bitrates at visually identical quality. Even with hardware encoders and time I don&#039;t think I would target such a trade off to H.265, need a second standard just to have options. But I can&#039;t wait for this to saturate the market.  ]]></description>
		<content:encoded><![CDATA[<p>Well of course H.265 is aimed at mobile so processor demand is not necessarily a luxury when you consider you want to record on the device to it.  But I am with you.  I would love to sacrifice time encoding for better bitrates at visually identical quality. Even with hardware encoders and time I don&#8217;t think I would target such a trade off to H.265, need a second standard just to have options. But I can&#8217;t wait for this to saturate the market.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Fletcher</title>
		<link>http://techgage.com/news/h-265-gets-approved-focuses-on-high-quality-at-low-bandwidth/#comment-726</link>
		<dc:creator>Jamie Fletcher</dc:creator>
		<pubDate>Mon, 28 Jan 2013 14:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://techgage.com/?post_type=news&#038;p=18360#comment-726</guid>
		<description><![CDATA[I wouldn&#039;t mind if the processing demand was higher if we could get lower bit-rates for comparable quality. Broadband speeds are barely budging, and bandwidth caps run rife; however, processing power is increasing exponentially. If a codec is too demanding now, it doesn&#039;t mean it won&#039;t be later. Maybe this is the approach taken with h.265.


One comment I do need to make though... royalties. Will it be the same system as h.264, a bait and switch later, or an up-front cost? Guess we&#039;ll find out later.]]></description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t mind if the processing demand was higher if we could get lower bit-rates for comparable quality. Broadband speeds are barely budging, and bandwidth caps run rife; however, processing power is increasing exponentially. If a codec is too demanding now, it doesn&#8217;t mean it won&#8217;t be later. Maybe this is the approach taken with h.265.</p>
<p>One comment I do need to make though&#8230; royalties. Will it be the same system as h.264, a bait and switch later, or an up-front cost? Guess we&#8217;ll find out later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Focus Elf</title>
		<link>http://techgage.com/news/h-265-gets-approved-focuses-on-high-quality-at-low-bandwidth/#comment-725</link>
		<dc:creator>The Focus Elf</dc:creator>
		<pubDate>Mon, 28 Jan 2013 14:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://techgage.com/?post_type=news&#038;p=18360#comment-725</guid>
		<description><![CDATA[I was all excited when I heard the words &quot;Google Fibre&quot; and then realized it was only STILL in Kansas and Missouri.  H.265 does appear great, sure as I&#039;ve been converting content to H.264 it did seem a little  bloated.  What is the &quot;minor&quot; way you are expecting to see the H.265 codec appear?]]></description>
		<content:encoded><![CDATA[<p>I was all excited when I heard the words &#8220;Google Fibre&#8221; and then realized it was only STILL in Kansas and Missouri.  H.265 does appear great, sure as I&#8217;ve been converting content to H.264 it did seem a little  bloated.  What is the &#8220;minor&#8221; way you are expecting to see the H.265 codec appear?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 1/4 queries in 0.003 seconds using memcached
Object Caching 181/183 objects using memcached

 Served from: techgage.com @ 2013-05-22 00:00:51 by W3 Total Cache -->