<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>H265.net &#187; Transform</title>
	<atom:link href="http://www.h265.net/tag/transform/feed" rel="self" type="application/rss+xml" />
	<link>http://www.h265.net</link>
	<description>Witness the development of H.265</description>
	<lastBuildDate>Wed, 11 Aug 2010 07:08:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Mode-Dependent Directional Transform (MDDT) in JM/KTA</title>
		<link>http://www.h265.net/2009/09/mode-dependent-directional-transform-mddt-in-jmkta.html</link>
		<comments>http://www.h265.net/2009/09/mode-dependent-directional-transform-mddt-in-jmkta.html#comments</comments>
		<pubDate>Tue, 22 Sep 2009 14:51:20 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[KTA]]></category>
		<category><![CDATA[Transform]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=255</guid>
		<description><![CDATA[<p style="text-align: justify;">The intra prediction in H.264/AVC is a type of spatial domain directional prediction, which means different intra prediction modes represent different prediction directions, such as horizontal, vertical, and diagonal. An intra-coded MB can be partitioned into 4&#215;4, 8&#215;8, or 16&#215;16 intra prediction blocks. The 4&#215;4 and 8&#215;8 intra prediction blocks have nine prediction directions, respectively, and the 16&#215;16 block has four. Hence, totally 22 (9+9+4) intra prediction modes are used in H.264/AVC. The residue usually has high energy along the direction of prediction, as edges are more difficult to be predicted than smooth areas.</p>
<p style="text-align: justify;">Mode-dependent directional transform (MDDT) was proposed to compact the residue produced by intra prediction. It consists of a series of pre-defined separable transforms; each transform is efficient in compacting energy along one of the prediction directions, thus favoring one of the intra modes. The type of MDDT is coupled with the selected[......]</p><p class='read-more'><a href='http://www.h265.net/2009/09/mode-dependent-directional-transform-mddt-in-jmkta.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2009/09/mode-dependent-directional-transform-mddt-in-jmkta.html/feed</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Transform Error Introduced by Non-orthogonality</title>
		<link>http://www.h265.net/2009/04/transform-error-introduced-by-non-orthogonality.html</link>
		<comments>http://www.h265.net/2009/04/transform-error-introduced-by-non-orthogonality.html#comments</comments>
		<pubDate>Mon, 27 Apr 2009 04:11:25 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[KTA]]></category>
		<category><![CDATA[Transform]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=29</guid>
		<description><![CDATA[<p style="text-align: justify;">In the Geneva meeting held in Feb. 2009, a proposal with the title &#8220;Video Coding Using Extended Block Sizes&#8221; was adopted by KTA, where the MB size is extended up to 64&#215;64 and the motion partitions are scaled accordingly. At the same time, a 2D order-16 transform was also proposed for transforming the residual blocks with the size larger than or equal to 16&#215;16. The transformation matrix of the proposed 2D order-16 transform is given as below, which is obtained by scaling the transformation matrix of 2D order-16 DCT by the factor 128 and rounding, and is non-orthogonal.</p>
<p style="text-align: center;"><img style="vertical-align: middle;" src="http://www.h265.net/wp-content/uploads/2009/04/T16.jpg" alt="The transformation matrix of the proposed 2D order-16 transform" width="623" height="205" /></p>
<p style="text-align: justify;">  Non-orthogonality will inevitably introduce transform error. Before analyzing the transform error quantitatively, let&#8217;s recall two properties of orthogonal transforms. Firstly, signals can be reconstructed perfectly if no quantization is performed in the transform domain. Secondly, if quantization is performed in the transform domain, the average variance (or energy) of the reconstruction er[......]</p><p class='read-more'><a href='http://www.h265.net/2009/04/transform-error-introduced-by-non-orthogonality.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2009/04/transform-error-introduced-by-non-orthogonality.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
