H.264 or MPEG-4 PART 10, ADVANCED VIDEO CODING ( MPEG-4 AVC) is a block-oriented motion-compensation -based video compression standard . As of 2014 it is one of the most commonly used formats for the recording, compression, and distribution of video content.
The intent of the H.264/AVC project was to create a standard capable
of providing good video quality at substantially lower bit rates than
previous standards (i.e., half or less the bit rate of
H.264 was developed by the
Video Coding Experts Group (VCEG)
together with the
Moving Picture Experts Group
H.264 is perhaps best known as being one of the video encoding
H.264 is protected by patents owned by various parties. A license covering most (but not all) patents essential to H.264 is administered by patent pool MPEG LA . Commercial use of patented H.264 technologies requires the payment of royalties to MPEG LA and other patent owners. MPEG LA has allowed the free use of H.264 technologies for streaming internet video that is free to end users, and Cisco Systems pays royalties to MPEG LA on behalf of the users of binaries for its open source H.264 encoder.
* 1 Naming
* 2 History
* 2.1 Versions
* 3 Applications
* 3.1 Derived formats
* 4 Design
* 4.1 Features
* 4.2 Profiles
* 4.2.1 Feature support in particular profiles
* 4.3 Levels * 4.4 Decoded picture buffering
* 5 Implementations
* 5.1 Software encoders * 5.2 Hardware
* 6 Licensing * 7 See also * 8 References * 9 Further reading * 10 External links
The H.264 name follows the
ITU-T naming convention, where the
standard is a member of the H.26x line of
VCEG video coding standards;
MPEG-4 AVC name relates to the naming convention in ISO /IEC MPEG
, where the standard is part 10 of ISO/IEC 14496, which is the suite
of standards known as MPEG-4. The standard was developed jointly in a
VCEG and MPEG, after earlier development work in the
ITU-T as a
VCEG project called H.26L. It is thus common to refer to
the standard with names such as H.264/AVC, AVC/H.264, H.264/MPEG-4
AVC, or MPEG-4/H.264 AVC, to emphasize the common heritage.
Occasionally, it is also referred to as "the JVT codec", in reference
to the Joint Video Team (JVT) organization that developed it. (Such
partnership and multiple naming is not uncommon. For example, the
video compression standard known as
In early 1998, the
Video Coding Experts Group (
Q.6) issued a call for proposals on a project called H.26L, with the
target to double the coding efficiency (which means halving the bit
rate necessary for a given level of fidelity) in comparison to any
other existing video coding standards for a broad variety of
VCEG was chaired by Gary Sullivan (
In December 2001,
VCEG and the
Moving Picture Experts Group
The standardization of the first version of H.264/AVC was completed in May 2003. In the first project to extend the original standard, the JVT then developed what was called the Fidelity Range Extensions (FRExt). These extensions enabled higher quality video coding by supporting increased sample bit depth precision and higher-resolution color information, including sampling structures known as Y'CbCr 4:2:2 (=YUV 4:2:2 ) and Y'CbCr 4:4:4. Several other features were also included in the Fidelity Range Extensions project, such as adaptive switching between 4×4 and 8×8 integer transforms, encoder-specified perceptual-based quantization weighting matrices, efficient inter-picture lossless coding, and support of additional color spaces. The design work on the Fidelity Range Extensions was completed in July 2004, and the drafting work on them was completed in September 2004.
Further recent extensions of the standard then included adding five other new profiles intended primarily for professional applications, adding extended-gamut color space support, defining additional aspect ratio indicators, defining two additional types of "supplemental enhancement information" (post-filter hint and tone mapping), and deprecating one of the prior FRExt profiles that industry feedback indicated should have been designed differently.
The next major feature added to the standard was Scalable Video Coding (SVC). Specified in Annex G of H.264/AVC, SVC allows the construction of bitstreams that contain sub-bitstreams that also conform to the standard, including one such bitstream known as the "base layer" that can be decoded by a H.264/AVC codec that does not support SVC. For temporal bitstream scalability (i.e., the presence of a sub-bitstream with a smaller temporal sampling rate than the main bitstream), complete access units are removed from the bitstream when deriving the sub-bitstream. In this case, high-level syntax and inter-prediction reference pictures in the bitstream are constructed accordingly. On the other hand, for spatial and quality bitstream scalability (i.e. the presence of a sub-bitstream with lower spatial resolution/quality than the main bitstream), the NAL (Network Abstraction Layer ) is removed from the bitstream when deriving the sub-bitstream. In this case, inter-layer prediction (i.e., the prediction of the higher spatial resolution/quality signal from the data of the lower spatial resolution/quality signal) is typically used for efficient coding. The Scalable Video Coding extensions were completed in November 2007.
The next major feature added to the standard was Multiview Video Coding (MVC). Specified in Annex H of H.264/AVC, MVC enables the construction of bitstreams that represent more than one view of a video scene. An important example of this functionality is stereoscopic 3D video coding. Two profiles were developed in the MVC work: Multiview High Profile supports an arbitrary number of views, and Stereo High Profile is designed specifically for two-view stereoscopic video. The Multiview Video Coding extensions were completed in November 2009.
Versions of the H.264/AVC standard include the following completed revisions, corrigenda, and amendments (dates are final approval dates in ITU-T, while final "International Standard" approval dates in ISO/IEC are somewhat different and slightly later in most cases). Each version represents changes relative to the next lower version that is integrated into the text.
* Version 1 (Edition 1): (May 30, 2003) First approved version of H.264/AVC containing Baseline, Main, and Extended profiles. * Version 2 (Edition 1.1): (May 7, 2004) Corrigendum containing various minor corrections. * Version 3 (Edition 2): (March 1, 2005) Major addition to H.264/AVC containing the first amendment providing Fidelity Range Extensions (FRExt) containing High, High 10, High 4:2:2, and High 4:4:4 profiles.
* Version 4 (Edition 2.1): (September 13, 2005) Corrigendum containing various minor corrections and adding three aspect ratio indicators. * Version 5 (Edition 2.2): (June 13, 2006) Amendment consisting of removal of prior High 4:4:4 profile (processed as a corrigendum in ISO/IEC). * Version 6 (Edition 2.2): (June 13, 2006) Amendment consisting of minor extensions like extended-gamut color space support (bundled with above-mentioned aspect ratio indicators in ISO/IEC). * Version 7 (Edition 2.3): (April 6, 2007) Amendment containing the addition of High 4:4:4 Predictive and four Intra-only profiles (High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, and CAVLC 4:4:4 Intra). * Version 8 (Edition 3): (November 22, 2007) Major addition to H.264/AVC containing the amendment for Scalable Video Coding (SVC) containing Scalable Baseline, Scalable High, and Scalable High Intra profiles. * Version 9 (Edition 3.1): (January 13, 2009) Corrigendum containing minor corrections. * Version 10 (Edition 4): (March 16, 2009) Amendment containing definition of a new profile (the Constrained Baseline profile) with only the common subset of capabilities supported in various previously specified profiles. * Version 11 (Edition 4): (March 16, 2009) Major addition to H.264/AVC containing the amendment for Multiview Video Coding (MVC) extension, including the Multiview High profile. * Version 12 (Edition 5): (March 9, 2010) Amendment containing definition of a new MVC profile (the Stereo High profile) for two-view video coding with support of interlaced coding tools and specifying an additional SEI message (the frame packing arrangement SEI message). * Version 13 (Edition 5): (March 9, 2010) Corrigendum containing minor corrections. * Version 14 (Edition 6): (June 29, 2011) Amendment specifying a new level (Level 5.2) supporting higher processing rates in terms of maximum macroblocks per second, and a new profile (the Progressive High profile) supporting only the frame coding tools of the previously specified High profile. * Version 15 (Edition 6): (June 29, 2011) Corrigendum containing minor corrections. * Version 16 (Edition 7): (January 13, 2012) Amendment containing definition of three new profiles intended primarily for real-time communication applications: the Constrained High, Scalable Constrained Baseline, and Scalable Constrained High profiles. * Version 17 (Edition 8): (April 13, 2013) Amendment with additional SEI message indicators. * Version 18 (Edition 8): (April 13, 2013) Amendment to specify the coding of depth map data for 3D stereoscopic video, including a Multiview Depth High profile. * Version 19 (Edition 8): (April 13, 2013) Corrigendum to correct an error in the sub-bitstream extraction process for multiview video. * Version 20 (Edition 8): (April 13, 2013) Amendment to specify additional color space identifiers (including support of ITU-R Recommendation BT.2020 for U HDTV ) and an additional model type in the tone mapping information SEI message. * Version 21 (Edition 9): (February 13, 2014) Amendment to specify the Enhanced Multiview Depth High profile. * Version 22 (Edition 9): (February 13, 2014) Amendment to specify the multi-resolution frame compatible (MFC) enhancement for 3D stereoscopic video, the MFC High profile, and minor corrections. * Version 23 (Edition 10): (February 13, 2016) Amendment to specify MFC stereoscopic video with depth maps, the MFC Depth High profile, the mastering display color volume SEI message, and additional color-related video usability information codepoint identifiers. * Version 24 (Edition 11): (October 14, 2016) Amendment to specify additional levels of decoder capability supporting larger picture sizes (Levels 6, 6.1, and 6.2), the green metadata SEI message, the alternative depth information SEI message, and additional color-related video usability information codepoint identifiers. * Version 25 (Edition 12): (April 13, 2017) Amendment to specify the Progressive High 10 profile and additional color-related VUI code points and SEI messages
Further information: List of video services using H.264/ MPEG-4 AVC
The H.264 video format has a very broad application range that covers
all forms of digital compressed video from low bit-rate Internet
streaming applications to
HDTV broadcast and Digital Cinema
applications with nearly lossless coding. With the use of H.264, bit
rate savings of 50% or more compared to
To ensure compatibility and problem-free adoption of H.264/AVC, many
standards bodies have amended or added to their video-related
standards so that users of these standards can employ H.264/AVC. Both
Advanced Television Systems Committee
Many common DSLRs use H.264 video wrapped in
XAVC is a recording format designed by
This article IS IN A LIST FORMAT THAT MAY BE BETTER PRESENTED USING PROSE . You can help by converting this article to prose, if appropriate . Editing help is available. (April 2016)
Block diagram of H.264
H.264/AVC/ MPEG-4 Part 10 contains a number of new features that allow it to compress video much more efficiently than older standards and to provide more flexibility for application to a wide variety of network environments. In particular, some such key features include:
* Multi-picture inter-picture prediction including the following features:
* Using previously encoded pictures as references in a much more flexible way than in past standards, allowing up to 16 reference frames (or 32 reference fields, in the case of interlaced encoding) to be used in some cases. In profiles that support non-IDR frames, most levels specify that sufficient buffering should be available to allow for at least 4 or 5 reference frames at maximum resolution. This is in contrast to prior standards, where the limit was typically one; or, in the case of conventional "B pictures " (B-frames), two. This particular feature usually allows modest improvements in bit rate and quality in most scenes. But in certain types of scenes, such as those with repetitive motion or back-and-forth scene cuts or uncovered background areas, it allows a significant reduction in bit rate while maintaining clarity. * Variable block-size motion compensation (VBSMC) with block sizes as large as 16×16 and as small as 4×4, enabling precise segmentation of moving regions. The supported luma prediction block sizes include 16×16, 16×8, 8×16, 8×8, 8×4, 4×8, and 4×4, many of which can be used together in a single macroblock. Chroma prediction block sizes are correspondingly smaller according to the chroma subsampling in use. * The ability to use multiple motion vectors per macroblock (one or two per partition) with a maximum of 32 in the case of a B macroblock constructed of 16 4×4 partitions. The motion vectors for each 8×8 or larger partition region can point to different reference pictures. * The ability to use any macroblock type in B-frames , including I-macroblocks, resulting in much more efficient encoding when using B-frames. This feature was notably left out from MPEG-4 ASP . * Six-tap filtering for derivation of half-pel luma sample predictions, for sharper subpixel motion-compensation. Quarter-pixel motion is derived by linear interpolation of the halfpel values, to save processing power. * Quarter-pixel precision for motion compensation, enabling precise description of the displacements of moving areas. For chroma the resolution is typically halved both vertically and horizontally (see 4:2:0 ) therefore the motion compensation of chroma uses one-eighth chroma pixel grid units. * Weighted prediction, allowing an encoder to specify the use of a scaling and offset when performing motion compensation , and providing a significant benefit in performance in special cases—such as fade-to-black, fade-in, and cross-fade transitions. This includes implicit weighted prediction for B-frames, and explicit weighted prediction for P-frames.
* Spatial prediction from the edges of neighboring blocks for "intra" coding, rather than the "DC"-only prediction found in MPEG-2 Part 2 and the transform coefficient prediction found in H.263v2 and MPEG-4 Part 2. This includes luma prediction block sizes of 16×16, 8×8, and 4×4 (of which only one type can be used within each macroblock ).
* A lossless "PCM macroblock" representation mode in which video data samples are represented directly, allowing perfect representation of specific regions and allowing a strict limit to be placed on the quantity of coded data for each macroblock. * An enhanced lossless macroblock representation mode allowing perfect representation of specific regions while ordinarily using substantially fewer bits than the PCM mode.
* Flexible interlaced -scan video coding features, including:
* Macroblock-adaptive frame-field (MBAFF) coding, using a macroblock pair structure for pictures coded as frames, allowing 16×16 macroblocks in field mode (compared with MPEG-2, where field mode processing in a picture that is coded as a frame results in the processing of 16×8 half-macroblocks). * Picture-adaptive frame-field coding (PAFF or PicAFF) allowing a freely selected mixture of pictures coded either as complete frames where both fields are combined together for encoding or as individual single fields.
* New transform design features, including:
* An exact-match integer 4×4 spatial block transform, allowing precise placement of residual signals with little of the "ringing " often found with prior codec designs. This design is conceptually similar to that of the well-known discrete cosine transform (DCT), introduced in 1974 by N. Ahmed , T.Natarajan and K.R.Rao, which is Citation 1 in Discrete cosine transform . However, it is simplified and made to provide exactly specified decoding. * An exact-match integer 8×8 spatial block transform, allowing highly correlated regions to be compressed more efficiently than with the 4×4 transform. This design is conceptually similar to that of the well-known DCT, but simplified and made to provide exactly specified decoding. * Adaptive encoder selection between the 4×4 and 8×8 transform block sizes for the integer transform operation. * A secondary Hadamard transform performed on "DC" coefficients of the primary spatial transform applied to chroma DC coefficients (and also luma in one special case) to obtain even more compression in smooth regions.
* A quantization design including:
* Logarithmic step size control for easier bit rate management by encoders and simplified inverse-quantization scaling * Frequency-customized quantization scaling matrices selected by the encoder for perceptual-based quantization optimization
* An in-loop deblocking filter that helps prevent the blocking artifacts common to other DCT -based image compression techniques, resulting in better visual appearance and compression efficiency
* An entropy coding design including:
Context-adaptive binary arithmetic coding (CABAC), an algorithm to
losslessly compress syntax elements in the video stream knowing the
probabilities of syntax elements in a given context.
data more efficiently than
CAVLC but requires considerably more
processing to decode.
Context-adaptive variable-length coding
* Loss resilience features including:
* A Network Abstraction Layer (NAL) definition allowing the same video syntax to be used in many network environments. One very fundamental design concept of H.264 is to generate self-contained packets, to remove the header duplication as in MPEG-4's Header Extension Code (HEC). This was achieved by decoupling information relevant to more than one slice from the media stream. The combination of the higher-level parameters is called a parameter set. The H.264 specification includes two types of parameter sets: Sequence Parameter Set (SPS) and Picture Parameter Set (PPS). An active sequence parameter set remains unchanged throughout a coded video sequence, and an active picture parameter set remains unchanged within a coded picture. The sequence and picture parameter set structures contain information such as picture size, optional coding modes employed, and macroblock to slice group map. * Flexible macroblock ordering (FMO), also known as slice groups, and arbitrary slice ordering (ASO), which are techniques for restructuring the ordering of the representation of the fundamental regions (macroblocks) in pictures. Typically considered an error/loss robustness feature, FMO and ASO can also be used for other purposes. * Data partitioning (DP), a feature providing the ability to separate more important and less important syntax elements into different packets of data, enabling the application of unequal error protection (UEP) and other types of improvement of error/loss robustness. * Redundant slices (RS), an error/loss robustness feature that lets an encoder send an extra representation of a picture region (typically at lower fidelity) that can be used if the primary representation is corrupted or lost. * Frame numbering, a feature that allows the creation of "sub-sequences", enabling temporal scalability by optional inclusion of extra pictures between other pictures, and the detection and concealment of losses of entire pictures, which can occur due to network packet losses or channel errors.
* Switching slices, called SP and SI slices, allowing an encoder to direct a decoder to jump into an ongoing video stream for such purposes as video streaming bit rate switching and "trick mode" operation. When a decoder jumps into the middle of a video stream using the SP/SI feature, it can get an exact match to the decoded pictures at that location in the video stream despite using different pictures, or no pictures at all, as references prior to the switch. * A simple automatic process for preventing the accidental emulation of start codes , which are special sequences of bits in the coded data that allow random access into the bitstream and recovery of byte alignment in systems that can lose byte synchronization.
* Supplemental enhancement information (SEI) and video usability information (VUI), which are extra information that can be inserted into the bitstream to enhance the use of the video for a wide variety of purposes. SEI FPA (Frame Packing Arrangement) message that contains the 3D arrangement:
* 0: checkerboard: pixels are alternatively from L and R. * 1: column alternation: L and R are interlaced by column. * 2: row alternation: L and R are interlaced by row. * 3: side by side: L is on the left, R on the right. * 4: top bottom: L is on top, R on bottom. * 5: frame alternation: one view per frame.
* Auxiliary pictures, which can be used for such purposes as alpha compositing . * Support of monochrome (4:0:0), 4:2:0, 4:2:2, and 4:4:4 chroma subsampling (depending on the selected profile). * Support of sample bit depth precision ranging from 8 to 14 bits per sample (depending on the selected profile). * The ability to encode individual color planes as distinct pictures with their own slice structures, macroblock modes, motion vectors, etc., allowing encoders to be designed with a simple parallelization structure (supported only in the three 4:4:4-capable profiles). * Picture order count, a feature that serves to keep the ordering of the pictures and the values of samples in the decoded pictures isolated from timing information, allowing timing information to be carried and controlled/changed separately by a system without affecting decoded picture content.
These techniques, along with several others, help H.264 to perform
significantly better than any prior standard under a wide variety of
circumstances in a wide variety of application environments. H.264 can
often perform radically better than
Like other ISO/IEC
The standard defines a sets of capabilities, which are referred to as profiles, targeting specific classes of applications. These are declared as a profile code (profile_idc) and a set of constraints applied in the encoder. This allows a decoder to recognize the requirements to decode that specific stream.
Profiles for non-scalable 2D video applications include the
following: Constrained Baseline Profile (CBP, 66 with constraint set
1) Primarily for low-cost applications, this profile is most typically
used in videoconferencing and mobile applications. It corresponds to
the subset of features that are in common between the Baseline, Main,
and High Profiles. Baseline Profile (BP, 66) Primarily for low-cost
applications that require additional data loss robustness, this
profile is used in some videoconferencing and mobile applications.
This profile includes all features that are supported in the
Constrained Baseline Profile, plus three additional features that can
be used for loss robustness (or for other purposes such as low-delay
multi-point video stream compositing). The importance of this profile
has faded somewhat since the definition of the Constrained Baseline
Profile in 2009. All Constrained Baseline Profile bitstreams are also
considered to be Baseline Profile bitstreams, as these two profiles
share the same profile identifier code value. Extended Profile (XP,
88) Intended as the streaming video profile, this profile has
relatively high compression capability and some extra tricks for
robustness to data losses and server stream switching. Main Profile
(MP, 77) This profile is used for standard-definition digital TV
broadcasts that use the
MPEG-4 format as defined in the DVB standard.
It is not, however, used for high-definition television broadcasts, as
the importance of this profile faded when the High Profile was
developed in 2004 for that application. High Profile (HiP, 100) The
primary profile for broadcast and disc storage applications,
particularly for high-definition television applications (for example,
this is the profile adopted by the
For camcorders, editing, and professional applications, the standard
contains four additional
As a result of the Scalable Video Coding (SVC) extension, the standard contains five additional scalable profiles, which are defined as a combination of a H.264/AVC profile for the base layer (identified by the second word in the scalable profile name) and tools that achieve the scalable extension: Scalable Baseline Profile (83) Primarily targeting video conferencing, mobile, and surveillance applications, this profile builds on top of the Constrained Baseline profile to which the base layer (a subset of the bitstream) must conform. For the scalability tools, a subset of the available tools is enabled. Scalable Constrained Baseline Profile (83 with constraint set 5) A subset of the Scalable Baseline Profile intended primarily for real-time communication applications. Scalable High Profile (86) Primarily targeting broadcast and streaming applications, this profile builds on top of the H.264/AVC High Profile to which the base layer must conform. Scalable Constrained High Profile (86 with constraint set 5) A subset of the Scalable High Profile intended primarily for real-time communication applications. Scalable High Intra Profile (86 with constraint set 3) Primarily targeting production applications, this profile is the Scalable High Profile constrained to all-Intra use.
As a result of the Multiview Video Coding (MVC) extension, the standard contains two multiview profiles: Stereo High Profile (128) This profile targets two-view stereoscopic 3D video and combines the tools of the High profile with the inter-view prediction capabilities of the MVC extension. Multiview High Profile (118) This profile supports two or more views using both inter-picture (temporal) and MVC inter-view prediction, but does not support field pictures and macroblock-adaptive frame-field coding. Multiview Depth High Profile (138)
Feature Support In Particular Profiles
FEATURE CBP BP XP MP PROHIP HIP HI10P HI422P HI444PP
I AND P SLICES Yes Yes Yes Yes Yes Yes Yes Yes Yes
BIT DEPTH (PER SAMPLE) 8 8 8 8 8 8 8 to 10 8 to 10 8 to 14
CHROMA FORMATS 4:2:0
4:2:0/ 4:2:2 4:2:0/ 4:2:2/ 4:4:4
FLEXIBLE MACROBLOCK ORDERING (FMO) No Yes Yes No No No No No No
ARBITRARY SLICE ORDERING (ASO) No Yes Yes No No No No No No
REDUNDANT SLICES (RS) No Yes Yes No No No No No No
DATA PARTITIONING No No Yes No No No No No No
SI AND SP SLICES No No Yes No No No No No No
INTERLACED CODING (PICAFF, MBAFF) No No Yes Yes No Yes Yes Yes Yes
B SLICES No No Yes Yes Yes Yes Yes Yes Yes
MULTIPLE REFERENCE FRAMES Yes Yes Yes Yes Yes Yes Yes Yes Yes
IN-LOOP DEBLOCKING FILTER Yes Yes Yes Yes Yes Yes Yes Yes Yes
CAVLC ENTROPY CODING Yes Yes Yes Yes Yes Yes Yes Yes Yes
CABAC ENTROPY CODING No No No Yes Yes Yes Yes Yes Yes
4:0:0 (MONOCHROME ) No No No No Yes Yes Yes Yes Yes
8×8 VS. 4×4 TRANSFORM ADAPTIVITY No No No No Yes Yes Yes Yes Yes
QUANTIZATION SCALING MATRICES No No No No Yes Yes Yes Yes Yes
SEPARATE CB AND CR QP CONTROL No No No No Yes Yes Yes Yes Yes
SEPARATE COLOR PLANE CODING No No No No No No No No Yes
PREDICTIVE LOSSLESS CODING No No No No No No No No Yes
As the term is used in the standard, a "level" is a specified set of constraints that indicate a degree of required decoder performance for a profile. For example, a level of support within a profile specifies the maximum picture resolution, frame rate, and bit rate that a decoder may use. A decoder that conforms to a given level must be able to decode all bitstreams encoded for that level and all lower levels.
Levels with maximum property values Level MAX DECODING SPEED MAX FRAME SIZE MAX VIDEO BIT RATE FOR VIDEO CODING LAYER (VCL) KBIT/S Examples for high resolution @ highest frame rate (max stored frames) Toggle additional details
LUMA SAMPLES/S MACROBLOCKS/S LUMA SAMPLES MACROBLOCKS Baseline, Extended and Main Profiles HIGH PROFILE HIGH 10 PROFILE
1 380,160 1,485 25,344 99 64 80 192 128×email@example.com (8) 176×firstname.lastname@example.org (4)
1B 380,160 1,485 25,344 99 128 160 384 128×email@example.com (8) 176×firstname.lastname@example.org (4)
1.1 768,000 3,000 101,376 396 192 240 576 176×email@example.com (9) 320×firstname.lastname@example.org (3) 352×email@example.com (2)
1.2 1,536,000 6,000 101,376 396 384 480 1,152 320×firstname.lastname@example.org (7) 352×email@example.com (6)
1.3 3,041,280 11,880 101,376 396 768 960 2,304 320×firstname.lastname@example.org (7) 352×email@example.com (6)
2 3,041,280 11,880 101,376 396 2,000 2,500 6,000 320×firstname.lastname@example.org (7) 352×email@example.com (6)
2.1 5,068,800 19,800 202,752 792 4,000 5,000 12,000 352×firstname.lastname@example.org (7) 352×email@example.com (6)
2.2 5,184,000 20,250 414,720 1,620 4,000 5,000 12,000 352×firstname.lastname@example.org (12) 352×email@example.com (10) 720×firstname.lastname@example.org (6) 720×email@example.com (5)
3 10,368,000 40,500 414,720 1,620 10,000 12,500 30,000 352×firstname.lastname@example.org (12) 352×email@example.com (10) 720×firstname.lastname@example.org (6) 720×email@example.com (5)
3.1 27,648,000 108,000 921,600 3,600 14,000 17,500 42,000 720×firstname.lastname@example.org (13) 720×email@example.com (11) 1,280×firstname.lastname@example.org (5)
3.2 55,296,000 216,000 1,310,720 5,120 20,000 25,000 60,000 1,280×email@example.com (5) 1,280×1,firstname.lastname@example.org (4)
4 62,914,560 245,760 2,097,152 8,192 20,000 25,000 60,000 1,280×email@example.com (9) 1,920×1,firstname.lastname@example.org (4) 2,048×1,email@example.com (4)
4.1 62,914,560 245,760 2,097,152 8,192 50,000 62,500 150,000 1,280×firstname.lastname@example.org (9) 1,920×1,email@example.com (4) 2,048×1,firstname.lastname@example.org (4)
4.2 133,693,440 522,240 2,228,224 8,704 50,000 62,500 150,000 1,280×email@example.com (9) 1,920×1,firstname.lastname@example.org (4) 2,048×1,email@example.com (4)
5 150,994,944 589,824 5,652,480 22,080 135,000 168,750 405,000 1,920×1,firstname.lastname@example.org (13) 2,048×1,email@example.com (13) 2,048×1,firstname.lastname@example.org (12) 2,560×1,email@example.com (5) 3,672×1,firstname.lastname@example.org (5)
5.1 251,658,240 983,040 9,437,184 36,864 240,000 300,000 720,000 1,920×1,email@example.com (16) 2,560×1,firstname.lastname@example.org (9) 3,840×2,email@example.com (5) 4,096×2,firstname.lastname@example.org (5) 4,096×2,email@example.com (5) 4,096×2,firstname.lastname@example.org (5)
5.2 530,841,600 2,073,600 9,437,184 36,864 240,000 300,000 720,000 1,920×1,email@example.com (16) 2,560×1,firstname.lastname@example.org (9) 3,840×2,email@example.com (5) 4,096×2,firstname.lastname@example.org (5) 4,096×2,email@example.com (5) 4,096×2,firstname.lastname@example.org (5)
The maximum bit rate for High Profile is 1.25 times that of the Base/Extended/Main Profiles, 3 times for Hi10P, and 4 times for Hi422P/Hi444PP.
The number of luma samples is 16x16=256 times the number of macroblocks (and the number of luma samples per second is 256 times the number of macroblocks per second).
DECODED PICTURE BUFFERING
Previously encoded pictures are used by H.264/AVC encoders to provide predictions of the values of samples in other pictures. This allows the encoder to make efficient decisions on the best way to encode a given picture. At the decoder, such pictures are stored in a virtual decoded picture buffer (DPB). The maximum capacity of the DPB, in units of frames (or pairs of fields), as shown in parentheses in the right column of the table above, can be computed as follows: capacity = min(floor(MaxDpbMbs / (PicWidthInMbs * FrameHeightInMbs)), 16)
Where MaxDpbMbs is a constant value provided in the table below as a function of level number, and PicWidthInMbs and FrameHeightInMbs are the picture width and frame height for the coded video data, expressed in units of macroblocks (rounded up to integer values and accounting for cropping and macroblock pairing when applicable). This formula is specified in sections A.3.1.h and A.3.2.f of the 2009 edition of the standard.
LEVEL 1 1B 1.1 1.2 1.3 2 2.1 2.2 3 3.1 3.2 4 4.1 4.2 5 5.1 5.2
MAXDPBMBS 396 396 900 2,376 2,376 2,376 4,752 8,100 8,100 18,000 20,480 32,768 32,768 34,816 110,400 184,320 184,320
For example, for an HDTV picture that is 1920 samples wide (PicWidthInMbs = 120) and 1080 samples high (FrameHeightInMbs = 68), a Level 4 decoder has a maximum DPB storage capacity of Floor(32768/(120*68)) = 4 frames (or 8 fields) when encoded with minimal cropping parameter values. Thus, the value 4 is shown in parentheses in the table above in the right column of the row for Level 4 with the frame size 1920×1080.
It is important to note that the current picture being decoded is not included in the computation of DPB fullness (unless the encoder has indicated for it to be stored for use as a reference for decoding other pictures or for delayed output timing). Thus, a decoder needs to actually have sufficient memory to handle (at least) one frame more than the maximum capacity of the DPB as calculated above.
In 2009, the HTML5 working group was split between supporters of Ogg
Theora , a free video format which is thought to be unencumbered by
patents, and H.264, which contains patented technology. As late as
July 2009, Google and Apple were said to support H.264, while Mozilla
and Opera support
Theora (now Google,
On March 18, 2012,
On October 30, 2013,
Rowan Trollope from
Cisco published the source to OpenH264 on December 9, 2013.
AVC software implementations FEATURE QUICKTIME NERO LEAD X264 Main- Concept ELECARD TSE Pro- Coder AVIVO ELEMENTAL IPP
B SLICES Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes
MULTIPLE REFERENCE FRAMES Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes
INTERLACED CODING (PICAFF, MBAFF) No MBAFF MBAFF MBAFF Yes Yes No Yes MBAFF Yes No
CABAC ENTROPY CODING Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes
8×8 VS. 4×4 TRANSFORM ADAPTIVITY No Yes Yes Yes Yes Yes Yes Yes No Yes Yes
QUANTIZATION SCALING MATRICES No No No Yes Yes No No No No No No
SEPARATE CB AND CR QP CONTROL No No No Yes Yes Yes No No No No No
EXTENDED CHROMA FORMATS No No No 4:2:2 4:4:4 4:2:0 4:2:2 4:2:2 4:2:2 No No 4:2:0 4:2:2 No
LARGEST SAMPLE DEPTH (BIT) 8 8 8 10 10 8 8 8 8 10 12
PREDICTIVE LOSSLESS CODING No No No Yes No No No No No No No
See also: List of cameras with onboard video stream encoding and H.264/ MPEG-4 AVC products and implementations
Because H.264 encoding and decoding requires significant computing power in specific types of arithmetic operations, software implementations that run on general-purpose CPUs are typically less power efficient. However, the latest quad-core general-purpose x86 CPUs have sufficient computation power to perform real-time SD and HD encoding. Compression efficiency depends on video algorithmic implementations, not on whether hardware or software implementation is used. Therefore, the difference between hardware and software based implementation is more on power-efficiency, flexibility and cost. To improve the power efficiency and reduce hardware form-factor, special-purpose hardware may be employed, either for the complete encoding or decoding process, or for acceleration assistance within a CPU-controlled environment.
CPU based solutions are known to be much more flexible, particularly when encoding must be done concurrently in multiple formats, multiple bit rates and resolutions (multi-screen video ), and possibly with additional features on container format support, advanced integrated advertising features, etc. CPU based software solution generally makes it much easier to load balance multiple concurrent encoding sessions within the same CPU.
The 2nd generation
A hardware H.264 encoder can be an ASIC or an FPGA .
ASIC encoders with H.264 encoder functionality are available from many different semiconductor companies, but the core design used in the ASIC is typically licensed from one of a few companies such as Chips -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;">
* ^ Ozer, Jan. "Encoding for Multiple Screen Delivery, Section 3,
Lecture 7: Introduction to H.264". Udemy. Retrieved 10 October 2016.
* ^ "AVC/H.264 FAQ". www.mpegla.com. Retrieved 2016-09-15.
* ^ "H.262 : Information technology — Generic coding of moving
pictures and associated audio information: Video". Retrieved
* ^ Joint Video Team,
ITU-T web site.
* ^ "
ITU-T Recommendation H.264 (05/2003)". ITU. 2003-05-30.
* ^ "
ITU-T Recommendation H.264 (05/2003) Cor. 1 (05/2004)". ITU.
2004-05-07. Retrieved 2013-04-18.
* ^ "
ITU-T Recommendation H.264 (03/2005)". ITU. 2005-03-01.
* ^ "
ITU-T Recommendation H.264 (2005) Cor. 1 (09/2005)". ITU.
2005-09-13. Retrieved 2013-04-18.
* ^ A B "
ITU-T Recommendation H.264 (2005) Amd. 1 (06/2006)". ITU.
2006-06-13. Retrieved 2013-04-18.
* ^ "
ITU-T Recommendation H.264 (2005) Amd. 2 (04/2007)". ITU.
2007-04-06. Retrieved 2013-04-18.
* ^ "
ITU-T Recommendation H.264 (11/2007)". ITU. 2007-11-22.
* ^ "
ITU-T Recommendation H.264 (2007) Cor. 1 (01/2009)". ITU.
2009-01-13. Retrieved 2013-04-18.
* ^ A B "
ITU-T Recommendation H.264 (03/2009)". ITU. 2009-03-16.
* ^ A B "
ITU-T Recommendation H.264 (03/2010)". ITU. 2010-03-09.
* ^ A B "
ITU-T Recommendation H.264 (06/2011)". ITU. 2011-06-29.
* ^ "
ITU-T Recommendation H.264 (01/2012)". ITU. 2012-01-13.
* ^ A B C D "
ITU-T Recommendation H.264 (04/2013)". ITU.
2013-06-12. Retrieved 2013-06-16.
* ^ A B "
ITU-T Recommendation H.264 (02/2014)". ITU. 2014-11-28.
* ^ "
ITU-T Recommendation H.264 (02/2016)". ITU. 2016-02-13.
* ^ "
ITU-T Recommendation H.264 (10/2016)". ITU. 2016-10-14.
* ^ "
ITU-T Recommendation H.264 (04/2017)". ITU. 2017-04-13.
* ^ Wenger; et al. "RFC 3984 : RTP Payload Format for H.264 Video":
* ^ "Which recording mode is equivalent to the image quality of the
High Definition Video (HDV) format?".
* ^ "
OpenH264 Simplified BSD License". 2013-10-27. Retrieved
* ^ "Video Interoperability on the Web Gets a Boost From Cisco\'s
H.264 Codec". 2013-10-30. Retrieved 2013-11-01.
* ^ "x264 4:2:2 encoding support", Retrieved 2011-09-22.
* ^ "x264 4:4:4 encoding support", Retrieved 2011-06-22.
* ^ "x264 support for 9 and 10-bit encoding", Retrieved 2011-06-22.
* ^ "x264 replace High 4:4:4 profile lossless with High 4:4:4
Predictive", Retrieved 2011-06-22.
* ^ "Quick Reference Guide to generation Intel® Core™ Processor
Built-in Visuals". Intel® Software Network. 2010-10-01. Retrieved
* ^ "Intel® Quick Sync Video". www.intel.com. 2010-10-01.
* ^ "Design-reuse.com". Design-reuse.com. 1990-01-01. Retrieved
* ^ "Category:DM6467 - Texas Instruments Embedded Processors Wiki".
Processors.wiki.ti.com. 2011-07-12. Retrieved 2011-07-30.
* ^ http://www.mpegla.com/main/programs/AVC/Documents/avcweb.pdf
* ^ "OMS Video, A Project of Sun\'s Open Media Commons Initiative".
MPEG LA patent US 7826532 that was filed in September 5, 2003
and has a 1546 day term extension.
* ^ "
* Wiegand, Thomas; Sullivan, Gary J.; Bjøntegaard, Gisle; Luthra, Ajay (July 2003). "Overview of the H.264/AVC Video Coding Standard" (PDF). IEEE Transactions on Circuits and Systems for Video Technology. 13 (7). Retrieved January 31, 2011. * Topiwala, Pankaj; Sullivan, Gary J.; Luthra, Ajay (August 2004). "Overview and Introduction to the Fidelity Range Extensions" (PDF). SPIE Applications of Digital Image Processing XXVII. Retrieved January 31, 2011. * Ostermann, J.; Bormans, J.; List, P.; Marpe, D.; Narroschke, M.; Pereira, F.; Stockhammer, T.; Wedi, T. (2004). "Video coding with H.264/AVC: Tools, Performance, and Complexity" (PDF). IEEE Circuits and Systems Magazine. 4 (1). Retrieved January 31, 2011. * Sullivan, Gary J.; Wiegand, Thomas (January 2005). "Video Compression—From Concepts to the H.264/AVC Standard" (PDF). Proceedings of the IEEE. 93 (1). doi :10.1109/jproc.2004.839617 . Retrieved January 31, 2011. * Richardson, Iain E. G. (January 2011). "Learn about video compression and H.264". VCODEX. Vcodex Limited. Retrieved January 31, 2011.
* ITU-T publication page: H.264: Advanced video coding for generic audiovisual services *