<?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; Jie Dong</title>
	<atom:link href="http://www.h265.net/author/jdong/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>Two Loop Filters in KTA</title>
		<link>http://www.h265.net/2010/08/two-loop-filters-in-kta.html</link>
		<comments>http://www.h265.net/2010/08/two-loop-filters-in-kta.html#comments</comments>
		<pubDate>Sun, 01 Aug 2010 02:00:09 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[Adaptive Filtering]]></category>
		<category><![CDATA[KTA]]></category>
		<category><![CDATA[Loop Filter]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=753</guid>
		<description><![CDATA[<p style="text-align: justify;">KTA employs two concatenating loop filters: the deblocking loop filter and the adaptive loop filter.</p>
<p style="text-align: justify;">The deblocking loop filter, inherited from H.264/AVC, alleviates the blocking artifacts caused by the block-based DCT+MCP video coding framework. It uses a bank of low-pass filters, which are adaptively applied to block boundaries according to the boundary strength (BS), and provides better visual quality and improved capability to predict other pictures.</p>
<p style="text-align: justify;">Adaptive loop filter (ALF; click <a href="http://www.h265.net/2009/08/adaptive-post-loop-filters-in-jmkta-part-2.html">here</a> for introduction) is placed in the MCP loop after the deblocking process, and is used to restore the degraded picture (caused by compression) such that the MSE between the reconstructed and source frames is minimized. The coefficients of ALF are calculated and transmitted on a frame basis and the <a href="http://en.wikipedia.org/wiki/Minimum_mean-square_error">minimum mean squared error (MMSE) estimator</a> is used. For each degraded frame, ALF can be applied to the entire frame or to local areas. The former is known as frame-based ALF. In the latter case, additiona[......]</p><p class='read-more'><a href='http://www.h265.net/2010/08/two-loop-filters-in-kta.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2010/08/two-loop-filters-in-kta.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adaptive Interpolation Filter for Video Coding</title>
		<link>http://www.h265.net/2010/07/adaptive-interpolation-filter-for-video-coding.html</link>
		<comments>http://www.h265.net/2010/07/adaptive-interpolation-filter-for-video-coding.html#comments</comments>
		<pubDate>Wed, 21 Jul 2010 10:10:13 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[Adaptive Filtering]]></category>
		<category><![CDATA[KTA]]></category>
		<category><![CDATA[MCP]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=248</guid>
		<description><![CDATA[<p style="text-align: left"><strong>Why use interpolation in video coding?</strong>  </p>
<p style="text-align: justify">Motion-compensated prediction (MCP) is the key to the success of the modern video coding standards, as it removes the temporal redundancy in video signals and reduces the size of bitstreams significantly. With MCP, the pixels to be coded are predicted from the temporally neighboring ones, and only the prediction errors and the motion vectors (MV) are transmitted. However, due to the finite sampling rate, the actual position of the prediction in the neighboring frames may be out of the sampling grid, where the intensity is unknown, so the intensities of the positions in between the integer pixels, called sub-positions, must be interpolated and the resolution of MV is increased accordingly.  </p>
<p style="text-align: justify"><strong>Interpolation in H.264/AVC</strong>  </p>
<p style="text-align: justify">In H.264/AVC, for the resolution of MV is quarter-pixel, the reference frame is interpolated to be 16 times the size for MCP, 4 times both sides. As shown in Fig. 1(a), the interpolation defined in H.264 includes two stages, inter[......]</p><p class='read-more'><a href='http://www.h265.net/2010/07/adaptive-interpolation-filter-for-video-coding.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2010/07/adaptive-interpolation-filter-for-video-coding.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introduction to Test Model under Consideration (TMuC)</title>
		<link>http://www.h265.net/2010/06/introduction-to-tmuc.html</link>
		<comments>http://www.h265.net/2010/06/introduction-to-tmuc.html#comments</comments>
		<pubDate>Sun, 27 Jun 2010 04:37:19 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[HEVC]]></category>
		<category><![CDATA[JCT-VC]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[TMuC]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=552</guid>
		<description><![CDATA[<p style="text-align: justify;">TMuC is the initial test model of JCT-VC, but it is not formally adopted as a test model of the draft standard, as no thorough testing has been performed for such a possible combination of tools. The coding tools in TMuC will be further tested to confirm their effectiveness, before adopted in a formal test model.</p>
<p style="text-align: justify;">TMuC provides more flexibility than H.264/AVC. The  basic coding unit, called coding tree block (CTB), which has a similar role to the macroblocks in H.264/AVC, can have variable sizes (a power of 2). The sizes of the largest and smallest CTBs are specified in the sequence parameter set (SPS). A frame is divided into non-overlapped largest CTBs (LCTB), e.g., 128&#215;128, and then each LCTB can be further divided in a recursive tree representation.</p>
<p style="text-align: justify;">Each CTB has its own prediction type (intra/inter) and prediction partition. The partition can be symmetric, just as in H.264/AVC, or asymmetric, e.g., 64&#215;64 block can be partitioned into 64&#215;16/64&#215;48 or 16&#215;64/48&#038;[......]</p><p class='read-more'><a href='http://www.h265.net/2010/06/introduction-to-tmuc.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2010/06/introduction-to-tmuc.html/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>The First JCT-VC Meeting, Dresden, DE</title>
		<link>http://www.h265.net/2010/06/the-first-jct-vc-meeting-dresden-de.html</link>
		<comments>http://www.h265.net/2010/06/the-first-jct-vc-meeting-dresden-de.html#comments</comments>
		<pubDate>Sat, 19 Jun 2010 08:51:43 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[HEVC]]></category>
		<category><![CDATA[JCT-VC]]></category>
		<category><![CDATA[Status]]></category>
		<category><![CDATA[TMuC]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=523</guid>
		<description><![CDATA[<p style="text-align: justify;">During Apr. 15-23, 2010, the first meeting of JCT-VC was held in Dresden, DE. In the meeting, 27 responses to the <a href="http://ftp3.itu.ch/av-arch/video-site/1001_Kyo/VCEG-AM91.zip">Call for Proposal</a>, issued in Jan. 2010, were reviewed and the associated video material was evaluated in extensive subjective tests.</p>
<p><strong>Tentative Conclusions from CfP Responses Reviews</strong></p>
<p style="text-align: justify;">Coding tools used in respective proposals are listed in <a href="http://ftp3.itu.int/av-arch/jctvc-site/2010_04_A_Dresden/JCTVC-A203.zip">JCTVC-A203</a>. High-level noteworthy aspects from the review of the proposals and the outcome of the subjective tests are outlined:</p>
<ul>
<li>Substantial progress in coding efficiency has clearly been demonstrated, compared with H.264/AVC</li>
<li>There is no indication of a need to change the fundamental architecture of &#8220;conventional&#8221; hybrid video coding designs to achieve a substantial improvement</li>
<li>Inclusion of support of larger block sizes in a highly variable (typically tree-structured) block segmentation approach is a major common theme, although large block sizes were not found in all proposals that did well subjectively (and objectively)</li>
<li>Modif[......]</li></ul><p class='read-more'><a href='http://www.h265.net/2010/06/the-first-jct-vc-meeting-dresden-de.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2010/06/the-first-jct-vc-meeting-dresden-de.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>12</slash:comments>
		</item>
		<item>
		<title>R-D Performance of 1/8-pel MCP on HD Sequences</title>
		<link>http://www.h265.net/2009/06/r-d-performance-of-18-pel-mcp-on-hd-sequences.html</link>
		<comments>http://www.h265.net/2009/06/r-d-performance-of-18-pel-mcp-on-hd-sequences.html#comments</comments>
		<pubDate>Sun, 07 Jun 2009 15:47:34 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[Adaptive Filtering]]></category>
		<category><![CDATA[KTA]]></category>
		<category><![CDATA[MCP]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=30</guid>
		<description><![CDATA[<p style="text-align: justify;">The technique of 1/8-pel interpolation [<a href="http://ftp3.itu.ch/av-arch/video-site/0610_Han/VCEG-AD09.zip">AD09</a>] was proposed for motion-compensated prediction (MCP) and adopted in KTA software. Three types of interpolation filters are used for 1/2-, 1/4-, and 1/8-pel sub positions, respectively.</p>
<ul style="text-align: justify;">
<li>[-3, 12, -39, 158, 158, -39, 12, -3]/256 for 1/2-pel sub positions.</li>
<li>[-3, 12, -37, 229, 71, -21, 6, -1]/256 and [-1, 6, -21, 71, 229, -37, 12, -3]/256 for 1/4-pel sub positions.</li>
<li>Bilinear filter for 1/8-pel sub positions.</li>
</ul>
<p style="text-align: justify;">  The frequency response of the interpolation filter is shown in the following figure. As can be seen, it is almost an ideal low-pass filter with a gain of 8 and a cutoff frequency <span style="font-size: small; font-family: Calibri;">π/8.</span></p>
<p style="text-align: center;"><img style="vertical-align: middle;" src="http://www.h265.net/wp-content/uploads/2009/06/FR.gif" alt="Frequency response" width="560" height="420" /></p>
<p style="text-align: justify;">  According to the performance reported in the proposal, the gain on CIF/QCIF sequences is quite significant, i.e., up to 14% bit-rate reduction. I tested this technique based on a set of HD sequences. As shown in Table 1, the R-D performance is measured by BDPSNR [1], i.e., PSNR improvement at the same bit-rate or bit-rate reduction at the same PSNR.</p>
<p style="text-align: justify;"> </p>
<p style="text-align: center;"><img src="http://www.h265.net/wp-content/uploads/2009/06/results.jpg" alt="Performance of 1/8-pel MCP" width="592" height="381" /></p>
<p style="text-align: justify;"> </p>
<p style="text-align: justify;"> [......]</p><p class='read-more'><a href='http://www.h265.net/2009/06/r-d-performance-of-18-pel-mcp-on-hd-sequences.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2009/06/r-d-performance-of-18-pel-mcp-on-hd-sequences.html/feed</wfw:commentRss>
		<slash:comments>7</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>
		<item>
		<title>KTA Software JM11KTA2.3</title>
		<link>http://www.h265.net/2009/04/kta-software-jm11kta23.html</link>
		<comments>http://www.h265.net/2009/04/kta-software-jm11kta23.html#comments</comments>
		<pubDate>Thu, 16 Apr 2009 09:59:07 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[KTA]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=28</guid>
		<description><![CDATA[<p>The latest KTA software is <a href="http://iphome.hhi.de/suehring/tml/download/KTA/jm11.0kta2.3.zip">JM11KTA2.3</a>, which integrates the coding tools adopted in the Geneva meeting (Jan. 2009) and before.  </p>
<ol>
<li>Inter prediction
<ol>
<li>Adaptive interpolation filter (AIF)
<ul>
<li>2-D non-separable AIF (<a href="http://ftp3.itu.ch/av-arch/video-site/0610_Han/VCEG-AD08.zip">AD08</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0701_Mar/VCEG-AE16.zip">AE16</a>)</li>
<li>Separable AIF (<a href="http://ftp.h265.net/C219.zip">COM16-C219</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0710_She/VCEG-AG10.zip">AG10</a>)</li>
<li>Directional AIF (DAIF) (<a href="http://ftp3.itu.ch/av-arch/video-site/0710_She/VCEG-AG21.zip">AG21</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0710_She/VCEG-AG22.zip">AG22</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0801_Ant/VCEG-AH17.zip">AH17</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0801_Ant/VCEG-AH18.zip">AH18</a>)</li>
<li>Enhanced DAIF (E-DAIF) (<a href="http://ftp3.itu.ch/av-arch/video-site/0807_Ber/VCEG-AI12.zip">AI12</a>,  <a href="http://ftp.h265.net/C126.doc">COM16-C126</a>)</li>
<li>Enhanced DAIF 2 (E-DAIF2) (<a href="http://ftp.h265.net/C125.doc">COM16-C125</a>)</li>
<li>Enhanced AIF (EAIF) (<a href="http://ftp.h265.net/C464.zip">COM16-C464</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0807_Ber/VCEG-AI38.zip">AI38</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0810_San/VCEG-AJ30.zip">AJ30</a>)</li>
<li>Switch interpolation filters with offsets (SIFO) (<a href="http://ftp.h265.net/C463.zip">COM16-C463</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0807_Ber/VCEG-AI35.zip">AI35</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0810_San/VCEG-AJ29.zip">AJ29</a>, <a href="http://ftp.h265.net/C126.doc">COM16-C126</a>)</li>
<li>High precision filter (HPF) (<a href="http://ftp3.itu.ch/av-arch/video-site/0807_Ber/VCEG-AI33.zip">AI33</a>)</li>
<li>Single-Pass Encoding (<a href="http://ftp3.itu.ch/av-arch/video-site/0810_San/VCEG-AJ29.zip">AJ29</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0904_Yok/VCEG-AK26.zip">AK26</a>)</li>
</ul>
</li>
<li>1/8-pel MCP (<a href="http://ftp3.itu.ch/av-arch/video-site/0610_Han/VCEG-AD09.zip">AD09</a>)</li>
<li>Extended MCP block size (<a href="http://ftp.h265.net/C123.doc">COM16-C123</a>)</li>
<li>Competition-based MV prediction (<a href="http://wftp3.itu.int/av-arch/video-site/0607_Kla/VCEG-AC06r1.doc">AC06r1</a>)</li>
</ol>
</li>
<li>Transform and quantization
<ol>
<li>Mode-dependent directional transform (MDDT) (<a href="http://ftp3.itu.ch/av-arch/video-site/0704_San/VCEG-AF15.zip">AF15</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0710_She/VCEG-AG11.zip">AG11</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0801_Ant/VCEG-AH20.zip">AH20</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0810_San/VCEG-AJ24.zip">AJ24</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0807_Ber/VCEG-AI36.zip">AI36</a>)</li>
<li>Very large block transform (<a href="http://ftp.h265.net/C123.doc">COM16-C123</a>)</li>
<li>Adaptive prediction error coding (APEC) (<a href="http://ftp3.itu.ch/av-arch/video-site/0601_Ban/VCEG-AB06.doc">AB06</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0610_Han/VCEG-AD07.zip">AD07</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0701_Mar/VCEG-AE15.zip">AE15</a>)</li>
<li>Adaptive quantization matrix selection (AQMS) (<a href="http://ftp3.itu.ch/av-arch/video-site/0607_Kla/VCEG-AC07.doc">AC07</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0610_Han/VCEG-AD06.zip">AD06</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0704_San/VCEG-AF08.zip">AF08</a>, <a href="http://ftp3.itu.ch/av-arch/video-site/0807_Ber/VCEG-AI19.zip">AI19</a>)</li>
<li>Rate-distortion optimized quantization (RDO[......]</li></ol></li></ol><p class='read-more'><a href='http://www.h265.net/2009/04/kta-software-jm11kta23.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2009/04/kta-software-jm11kta23.html/feed</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Current Status of H.265 (as at July 2008)</title>
		<link>http://www.h265.net/2008/07/current-status-of-h265.html</link>
		<comments>http://www.h265.net/2008/07/current-status-of-h265.html#comments</comments>
		<pubDate>Tue, 01 Jul 2008 07:01:00 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[Research]]></category>
		<category><![CDATA[KTA]]></category>
		<category><![CDATA[Status]]></category>
		<category><![CDATA[VCEG]]></category>

		<guid isPermaLink="false">http://www.h265.net/?p=23</guid>
		<description><![CDATA[<p style="text-align: justify;">H.265 is a long-term video coding standard, launched by VCEG. As indicated in <a href="http://www.itu.int/ITU-T/studygroups/com16/sg16-q6.html" target="_blank">ITU-T SG16&#8242;s homepage</a>, VCEG plans to complete the requirement definition and begin the detailed algorithm design for H.265 in the study period 2005-2008, and if the progress in contribution technology is sufficient, H.265 is expected to be finalized in 2009-2010.</p>
<p style="text-align: justify;">Currently, H.265 hasn&#8217;t been formalized and VCEG keeps seeking proposals and information regarding the possibility of a major gain in performance to justify the step from H.264 to H.265. Though the necessary scope of H.265 is yet to be determined, it is agreed that among the goals will be [<a href="http://ftp3.itu.ch/av-arch/video-site/0510_Nic/VCEG-AA01.doc" target="_blank">AA01</a>]:</p>
<ul style="text-align: justify;">
<li>simplicity and &#8220;back to basics&#8221; approach</li>
<li>high coding efficiency, e.g., two times compared with H.264</li>
<li>computational efficiency, considering both encoder and decoder</li>
<li>loss/error robustness</li>
<li>network friendliness</li>
<li>other considerations as necessary </li>
</ul>
<p style="text-align: justify;">Backward/forward compatibility is not assumed to be required for H.265, as H.265 is a brand [......]</p><p class='read-more'><a href='http://www.h265.net/2008/07/current-status-of-h265.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2008/07/current-status-of-h265.html/feed</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Welcome to H265.net</title>
		<link>http://www.h265.net/2008/06/welcome-to-h265net.html</link>
		<comments>http://www.h265.net/2008/06/welcome-to-h265net.html#comments</comments>
		<pubDate>Mon, 02 Jun 2008 03:46:10 +0000</pubDate>
		<dc:creator>Jie Dong</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Help]]></category>

		<guid isPermaLink="false">http://www.h265.net/2008/06/welcome-to-h265net.html</guid>
		<description><![CDATA[<p style="text-align: justify;">Hello, everybody, welcome to H265.net!</p>
<p style="text-align: justify;">This blog is dedicated to the development of H.265 that is still in its infancy. Not only does this blog records the events of H.265, but it also discusses the (potential) techniques for H.265, i.e., the proposals in VCEG. Please feel free to post your comments and suggestions, no matter you are a beginner or an expert.</p>
<p style="text-align: justify;">Before posting the comments, you need to <a href="http://www.h265.net/wp-login.php?action=register" target="_blank">register</a> for the first time or  <a href="http://www.h265.net/wp-login.php" target="_blank">login</a> if you already have a user name. The privacy policy of this blog can be found <a href="http://www.h265.net/privacy">here</a>. Your comment will appear on the site after approved by the administrator.</p>
<p style="text-align: justify;">If you are interested in signing up the free e-mail service with the domain @h265.net, which provides 5 GB storage space and rich functionalities , just simply click the &#8220;sign up&#8221; button in the upper-right corner of the homepage. The mail server is hosted by Microsoft.</p>
<p style="text-align: justify;">Should you have suggestions for the construction of this blog, please send an e-mail to <a href="mailto:admin@h265.net">admin@h265.net</a>. Thank you very m[......]</p><p class='read-more'><a href='http://www.h265.net/2008/06/welcome-to-h265net.html'>Read More...</a></p>]]></description>
		<wfw:commentRss>http://www.h265.net/2008/06/welcome-to-h265net.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
