H.264 / MPEG-4 Part 10 White Paper-翻译
1. Introduction
Broadcast(广播) television and home entertainment(娱乐) have been revolutionised(彻底改变) by the advent(出现) of digital TV andDVD-video.(--广播电视和家庭娱乐方式被彻底改变了在数字电视和DVD-Video出现之后--) These applications and many more were made possible by the standardisation of video compression technology.(--这些应用和其他的许多东西慢慢变得可能实现在这个视频压缩技术标准之后--) The next standard in the MPEG series(--MPEG系列的下一个标准--), MPEG4 is enabling(启用) a new generation of (代名)internet-based video applications(--MPEG4为新一代的给予因特网的视频应用提供了可能--) whilst(同时 ) the ITU-T H.263 standard for video compression is now widely used in video conferencing(会议) systems.(--ITU-T H.263视频压缩标准在现在被广泛的用于视频会议系统--)
MPEG4 (Visua(视频)l) and H.263 are standards that are based on video compression (“video coding”) technology from circa. 1995.(--MPEG4和H.263是视频压缩(视频编码)技术的标准大约从1995年开始。--) The groups responsible for these standards(--一下组织负责这些东西的标准--), the Motion Picture Experts Group and the Video Coding Experts Group (MPEG and VCEG) (--运动图像专家组,和视频编码专家组--)are in the final stages of developing a new standard that promises to significantly outperform MPEG4 and H.263(--致力于开发一个比MPEG4更加--,), providing better compression of video images together with a range of features supporting high-quality, low-bitrate streaming video.(--高性能,高品质,低比特流--) The history of the new standard, “Advanced Video Coding” (AVC), goes back at least 7 years.
After finalising(敲定) the original(原始) H.263 standard for video telephony(电话) in 1995(--在1995年为了视频电话敲定H.263原始标准--), the ITU-T Video Coding Experts Group (VCEG) started work on two further development areas(ITU-T视频编码专家组开始在两个深入的领域发展:): a “short-term” effort to add extra features(特点,特性) to H.263 (resulting in Version 2 of the standard) (--一个是通过短期的努力去增加H.263更多的特性(制定出来版本2的标准)--)and a “long-term” effort to develop a new standard for low bit rate visual communications.(--另一个是通过长期的努力致力于发展一个新的版本为了适应低比特流的视频压缩--) The long-term effort led to the draft “H.26L” standard,(--长期项目组努力的领导起草了H.26L标准--) offering significantly(显著) better video compression efficiency(效率) than previous ITU-T standards(--提供了明显优于ITU-U标准的压缩效率--). In 2001, the ISO Motion Picture Experts Group (MPEG) recognised the potential benefits(潜在的好处) of H.26L(--2001年MPEG小组发现了H.264潜在的有点--) and the Joint Video Team (JVT) was formed,(JVM团队就被提出来了。) including experts from MPEG and VCEG(包含了来自这两个小组的专家). JVT’s main task is to develop the draft H.26L “model” into a full International Standard. (JVM小组的主要任务就是将“H.26L标准发展为国际标准”)In fact, the outcome will be two identical standards(事实上他们推出了两个标准): ISO MPEG4 Part 10 of MPEG4 and ITU-T H.264.(。。。就这两个) The “official” title of the new standard is Advanced Video Coding (AVC)(官方声称这个才是真正的新版本); however, it is widely known by its old working title, H.26L and by its ITU document number, H.264 [1].(然而更加广为人知的是采用旧的命名方式的。。。。。)
2. H.264 CODEC
In common with earlier standards (such as MPEG1, MPEG2 and MPEG4)(--和之前版本差不多的是--), the H.264 draft standard does not explicitly(明确的) define a CODEC (enCOder / DECoder pair). (--H.264并没有显式的定义一个编解码机器--)Rather, the standard defines the syntax of an encoded video bitstream together with the method of decoding this bitstream.(--而,这个标准只定义了将视频编码为比特流和从比特流解码的方法。--) In practice, however, a compliant encoder and decoder are likely to include the functional elements shown in Figure 2-1 and Figure 2-2. (--然而,一个合格的编解码机器需要包含图中2-1和2-2的功能元素--)Whilst the functions shown in these Figures are likely to be necessary for compliance(同时对于一个合格的编解码机器来说能过表现出这些功能是十分重要的。), there is scope for considerable variation in the structure of the CODEC(编解码机器还是有相当大的变异空间的). The basic functional elements(这些基本功能元素) (prediction, transform, quantization, entropy encoding)(预测,传输,量化,熵编码) are little different from previous standards (和之前的标准差不多)(MPEG1, MPEG2, MPEG4, H.261, H.263); the important changes in H.264 occur in the details of each functional element.(H.264最主要的变化实在这些模块的实现细节上面。)
The Encoder (Figure 2-1) includes two dataflow paths(编码包括两条数据流路径), a “forward” path (left to right, shown in blue)(一条向前的,(从左到右))and a “reconstruction” path (right to left, shown in magenta).(还有一条重构路径 从右到左,品红色的路径)The dataflow path in the Decoder (Figure 2-2) is shown from right to left to illustrate the similarities between Encoder and Decoder.(解码器的数据流以从右到左的方式表示,一次来说明,编解码机器的共同点‘。)

2.1 Encoder (forward path)
2.1编码器(向前路径)
An input frame F n is presented for encoding.(当一个输入帧提交编码的时候) The frame is processed in units of a macroblock (corresponding to 16x16 pixels in the original image).(该帧以宏模块为单位进行处理,(对应原图16*16的像素为一个模块)) Each macroblock is encoded in intra or inter mode.(每个宏块,被编码成帧内模式,或帧间模式) In either case, a prediction macroblock P is formed based on a reconstructed frame. In Intra mode, P is formed from samples in the current frame n that have previously encoded, decoded and reconstructed (uF’ n in the Figures; note that the unfiltered samples are used to form P). In Inter mode, P is formed by motion-compensated prediction from one or more reference frame(s). In the Figures, the reference frame is shown as the previous encoded frame F’ n-1 ; however, the predicton for each macroblock may be formed from one or two past or future frames (in time order) that have already been encoded and reconstructed.
The prediction P is subtracted from the current macroblock to produce a residual or difference macroblock D n . This is transformed (using a block transform) and quantized to give X, a set of quantized transform coefficients. These coefficients are re-ordered and entropy encoded. The entropy-encoded coefficients, together with side information required to decode the macroblock (such as the macroblock prediction mode, quantizer step size, motion vector information describing how the macroblock was motion-compensated, etc) form the compressed bitstream. This is passed to a Network Abstraction Layer (NAL) for transmission or storage.
H.264 / MPEG-4 Part 10 White Paper-翻译的更多相关文章
- 【二】H.264/MPEG-4 Part 10 White Paper 翻译之 Prediction of Intra Macroblocks
翻译版权所有,转载请注明出处~ xzrch@2018.09.14 ------------------------------------------------------------------- ...
- 【一】H.264/MPEG-4 Part 10 White Paper 翻译之 Overview of H.264
翻译版权所有,转载请注明出处~ xzrch@2018.09.14 ------------------------------------------------------------------- ...
- 每天进步一点点------H.264学习 (一)
分三个阶段学习1.第一个阶段: 学习H.264,首先要把最基本最必要的资料拿在手里.这些资料包括:标准文档+测试模型+经典文章,在本FTP中能找到.首先看 <H.264_MPEG-4 Part ...
- 【转】实现RTP协议的H.264视频传输系统
1. 引言 随着信息产业的发展,人们对信息资源的要求已经逐渐由文字和图片过渡到音频和视频,并越来越强调获取资源的实时性和互动性.但人们又面临着另外一种不可避免的尴尬,就是在网络上看到生动 ...
- 基于RTP协议的H.264传输
1. 引言 随 着信息产业的发展,人们对信息资源的要求已经逐渐由文字和图片过渡到音频和视频,并越来越强调获取资源的实时性和互动性.但人们又面临着另外一种不可避免 的尴尬,就是在网络上看 ...
- H.265 & H.264
H.265 & H.264 HEVC (H.265) vs. AVC (H.264) https://en.wikipedia.org/wiki/High_Efficiency_Video_C ...
- H.264 White Paper学习笔记(一)总览
H.264 White Paper对于264编码器的原理讲的比较透彻,在阅读学习的时候收获很大,这份文献网上有很多了,也有不少人翻译,不过想要理解更清楚我觉得还是得看英文原版的. 首先看一下白皮书里给 ...
- H.264 White Paper学习笔记(二)帧内预测
为什么要有帧内预测?因为一般来说,对于一幅图像,相邻的两个像素的亮度和色度值之间经常是比较接近的,也就是颜色是逐渐变化的,不会一下子突变成完全不一样的颜色.而进行视频编码,目的就是利用这个相关性,来进 ...
- H.264开源解码器评测
转自:http://wmnmtm.blog.163.com/blog/static/38245714201142883032575/ 要播放HDTV,就首先要正确地解开封装,然后进行视频音频解码.所以 ...
随机推荐
- 【转】 MySQL与PostgreSQL:该选择哪个开源数据库?哪一个更好?
转载地址:http://www.infoq.com/cn/news/2013/12/mysql-vs-postgresql 如果打算为项目选择一款免费.开源的数据库,那么你可能会在MySQL与Post ...
- 【leetcode❤python】 28. Implement strStr()
#-*- coding: UTF-8 -*- #题意:大海捞刀,在长字符串中找出短字符串#AC源码:滑动窗口双指针的方法class Solution(object): def strStr(se ...
- Cheatsheet: 2015 12.01 ~ 12.31
Mobile Setting Up the Development Environment iOS From Scratch With Swift: How to Test an iOS Applic ...
- 用流从一个指定的网址抓取html代码
package cn.bdqn.collect.test; import java.io.BufferedReader; import java.io.InputStream; import java ...
- PHP-----函数和二进制
递归-----函数本身调用本身.每一个栈中的变量都是独立的,不受外部变量的影响,除非传参.这一点和Js不一样. 在一个php页面中要引用其他的php文件可以使用require,require_once ...
- Java vs. C#
Java Program Structure C# package hello; public class HelloWorld { public static void main(String ...
- js中的fadeIn()
一.fadeIn()淡入,fadeOut()淡出 fadeIn()和fadeOut()括号里边跟执行的时间
- hdu2296Ring(ac自动机+dp)
链接 dp[i][j]表示长度为i在节点J的时候的权值最大值,根据trie树转移一下就行,需要每次都取最小的,所以需要另开一数组保存字典序最小的状态. #include <iostream> ...
- 【java基础】方法2
让形参可变的方法 jdk1.5之后,java允许定义形参长度可变的参数,允许为方法指定数量不确定的形参. package object; public class VariableParam { // ...
- Android各组件/控件间通信利器之EventBus
实际项目开发过程中,经常遇到如下场景:不同的应用程序组件的控件间具有一定的相互关联性,其中用户对后者进行的某种操作会引起前者的相应改变.举一个具体的场景:以糗事百科为例,在糗事列表页和详情页页,对于每 ...