比较重要的链接都在这里：
How HEVC/H.265 works, technical details & diagrams Part I
（HEVC或者H.265如何工作：技术细节以及相关流图）
首先想附上两个相关链接： 1，CSDN yangxiao_xiang 2， 原出处： here , 3, 这里还有一个关于HEVC的技术overview的报告： here
Now that the HEVC standard is finalized, I'd like take this opportunity to explain how HEVC coding works in plain-ish English. About me: I am a hardware codec engineer who has been working with HEVC for over a year now and I have participated in the JCT-VC meetings where HEVC has taken shape. The spec itself, located at http://phenix.int-evry.fr/jct/doc_en...nt.php?id=7243, is rather hard to follow. This post will assume you are reasonably familiar with the coding techniques in H.264/AVC, hereafter referred to as AVC. This overview will gloss over a few details, but feel free to ask for any elaboration.
现如今HEVC标准已经定稿，我借此机会用平实的语言向大家介绍一下HEVC如何进行编码的。关于我本人，我是一个硬件编解码工程师，在HEVC领域已经有一年的工作经历，并且参加了研讨HEVC标准的JCT-VC会议。对于这个标准本身，具体内容可见于 here ，但写的晦涩难懂，
因为它是写给那些熟悉了H.264/AVC的同志们滴；在本文中我们会忽略一部分技术细节，但是如有不明指出尽请提出。 （nice boy）
To start with: HEVC is actually a bit simpler conceptually than AVC, and lots of things in the spec are done to make life easier for the hardware codec designer (like me).
行文伊始：不得不说HEVC在概念上要比AVC简洁，而且在整个规范中对于硬件编解码工程师而言很多体贴入微的设计（亚克西）。
Picture partitioning
Instead of macroblocks, HEVC pictures are divided into so-called coding
tree blocks, or CTBs for short, which appear in the picture in raster
order. Depending on the stream parameters, they are either 64x64, 32x32
or 16x16. Each CTB can be split recursively in a quad-tree structure,
all the way down to 8x8. So for example a 32x32 CTB can consist of three
16x16 and four 8x8 regions. These regions are called coding units, or
CUs. CUs are the basic unit of prediction in HEVC. If you have been
paying attention you have already inferred that CUs can be 64x64, 32x32,
16x16 or 8x8. The CUs in a CTB are traversed and coded in Z-order.
Example ordering in a 64x64 CTB:
图的分割：（我自己对于这块内容也不懂，所以强迫自己翻译一遍，以期能明白一二）