See more H.264/MPEG 4 AVC articles on AOD.

Powered by
TTSReader
Share this page on
Article provided by Wikipedia


( => ( => ( => H.264/MPEG-4 AVC [pageid] => 237036 ) =>

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.[1] It supports resolutions up to 4096×2304, including "4K UHD.[2]

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 "MPEG-2, "H.263, or "MPEG-4 Part 2), without increasing the complexity of design so much that it would be impractical or excessively expensive to implement. An additional goal was to provide enough flexibility to allow the standard to be applied to a wide variety of applications on a wide variety of networks and systems, including low and high bit rates, low and high resolution video, "broadcast, "DVD storage, "RTP/"IP packet networks, and "ITU-T multimedia "telephony systems. The H.264 standard can be viewed as a "family of standards" composed of a number of different profiles. A specific decoder decodes at least one, but not necessarily all profiles. The decoder specification describes which profiles can be decoded. H.264 is typically used for "lossy compression, although it is also possible to create truly "lossless-coded regions within lossy-coded pictures or to support rare use cases for which the entire encoding is lossless.

H.264 was developed by the "ITU-T "Video Coding Experts Group (VCEG) together with the "ISO/IEC JTC1 "Moving Picture Experts Group (MPEG). The project partnership effort is known as the Joint Video Team (JVT). The ITU-T H.264 standard and the ISO/IEC "MPEG-4 AVC standard (formally, ISO/IEC 14496-10 – "MPEG-4 Part 10, Advanced Video Coding) are jointly maintained so that they have identical technical content. The final drafting work on the first version of the standard was completed in May 2003, and various extensions of its capabilities have been added in subsequent editions. "High Efficiency Video Coding (HEVC), a.k.a. H.265 and MPEG-H Part 2 is a successor to H.264/MPEG-4 AVC developed by the same organizations, while earlier standards are still in common use.

H.264 is perhaps best known as being one of the video encoding standards for "Blu-ray Discs; all Blu-ray Disc players must be able to decode H.264. It is also widely used by streaming internet sources, such as videos from "Vimeo, "YouTube, and the "iTunes Store, web software such as the "Adobe Flash Player and "Microsoft Silverlight, and also various "HDTV broadcasts over terrestrial ("Advanced Television Systems Committee standards, "ISDB-T, "DVB-T or "DVB-T2), cable ("DVB-C), and satellite ("DVB-S and "DVB-S2).

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.[3] 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.

Contents

Naming[edit]

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; the 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 partnership of 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 "MPEG-2 also arose from the partnership between "MPEG and the "ITU-T, where MPEG-2 video is known to the ITU-T community as H.262.[4]) Some software programs (such as "VLC media player) internally identify this standard as AVC1.

History[edit]

In early 1998, the "Video Coding Experts Group (VCEG – ITU-T SG16 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 applications. "VCEG was chaired by "Gary Sullivan ("Microsoft, formerly "PictureTel, U.S.). The first draft design for that new standard was adopted in August 1999. In 2000, "Thomas Wiegand ("Heinrich Hertz Institute, Germany) became VCEG co-chair.

In December 2001, VCEG and the Moving Picture Experts Group ("MPEG – "ISO/IEC JTC 1/SC 29/WG 11) formed a Joint Video Team (JVT), with the charter to finalize the video coding standard.[5] Formal approval of the specification came in March 2003. The JVT was (is) chaired by "Gary Sullivan, "Thomas Wiegand, and Ajay Luthra ("Motorola, U.S.: later "Arris, U.S.). In June 2004, the Fidelity range extensions (FRExt) project was finalized. From January 2005 to November 2007, the JVT was working on an extension of H.264/AVC towards scalability by an Annex (G) called "Scalable Video Coding (SVC). The JVT management team was extended by Jens-Rainer Ohm ("Aachen University, Germany). From July 2006 to November 2009, the JVT worked on "Multiview Video Coding (MVC), an extension of H.264/AVC towards "free viewpoint television and "3D television. That work included the development of two new profiles of the standard: the Multiview High Profile and the Stereo High Profile.

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["which?] 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["which?] that industry feedback["by whom?] 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[edit]

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.

Applications[edit]

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 "MPEG-2 Part 2 are reported. For example, H.264 has been reported to give the same Digital Satellite TV quality as current MPEG-2 implementations with less than half the bitrate, with current MPEG-2 implementations working at around 3.5 Mbit/s and H.264 at only 1.5 Mbit/s.[23] Sony claims that 9 Mbit/s AVC recording mode is equivalent to the image quality of the "HDV format, which uses approximately 18–25 Mbit/s.[24]

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 the "Blu-ray Disc format and the now-discontinued "HD DVD format include the H.264/AVC High Profile as one of 3 mandatory video compression formats. The Digital Video Broadcast project ("DVB) approved the use of H.264/AVC for broadcast television in late 2004.

The "Advanced Television Systems Committee (ATSC) standards body in the United States approved the use of H.264/AVC for broadcast television in July 2008, although the standard is not yet used for fixed ATSC broadcasts within the United States.[25][26] It has also been approved for use with the more recent "ATSC-M/H (Mobile/Handheld) standard, using the AVC and SVC portions of H.264.[27]

The "CCTV (Closed Circuit TV) and "Video Surveillance markets have included the technology in many products.

Many common "DSLRs use H.264 video wrapped in QuickTime MOV containers as the native recording format.

Derived formats[edit]

"AVCHD is a high-definition recording format designed by "Sony and "Panasonic that uses H.264 (conforming to H.264 while adding additional application-specific features and constraints).

"AVC-Intra is an "intraframe-only compression format, developed by "Panasonic.

"XAVC is a recording format designed by Sony that uses level 5.2 of H.264/MPEG-4 AVC, which is the highest level supported by that video standard.[28][29] XAVC can support "4K resolution (4096 × 2160 and 3840 × 2160) at up to 60 "frames per second (fps).[28][29] Sony has announced that cameras that support XAVC include two "CineAlta cameras—the Sony PMW-F55 and Sony PMW-F5.[30][31] The Sony PMW-F55 can record XAVC with 4K resolution at 30 fps at 300 "Mbit/s and 2K resolution at 30 fps at 100 Mbit/s.[32] XAVC can record 4K resolution at 60 fps with 4:2:2 chroma subsampling at 600 Mbit/s.[33][34]

Design[edit]

Features[edit]

""
""
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:

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 MPEG-2 video—typically obtaining the same quality at half of the bit rate or less, especially on high bit rate and high resolution situations.[37]

Like other ISO/IEC MPEG video standards, H.264/AVC has a reference software implementation that can be freely downloaded.[38] Its main purpose is to give examples of H.264/AVC features, rather than being a useful application per se. Some reference hardware design work is also under way in the "Moving Picture Experts Group. The above-mentioned are complete features of H.264/AVC covering all profiles of H.264. A profile for a codec is a set of features of that codec identified to meet a certain set of specifications of intended applications. This means that many of the features listed are not supported in some profiles. Various profiles of H.264/AVC are discussed in next section.

Profiles[edit]

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.[39] 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 "Blu-ray Disc storage format and the "DVB HDTV broadcast service).
Progressive High Profile (PHiP, 100 with constraint set 4)
Similar to the High profile, but without support of field coding features.
Constrained High Profile (100 with constraint set 4 and 5)
Similar to the Progressive High profile, but without support of B (bi-predictive) slices.
High 10 Profile (Hi10P, 110)
Going beyond typical mainstream consumer product capabilities, this profile builds on top of the High Profile, adding support for up to 10 bits per sample of decoded picture precision.
High 4:2:2 Profile (Hi422P, 122)
Primarily targeting professional applications that use interlaced video, this profile builds on top of the High 10 Profile, adding support for the 4:2:2 "chroma subsampling format while using up to 10 bits per sample of decoded picture precision.
High 4:4:4 Predictive Profile (Hi444PP, 244)
This profile builds on top of the High 4:2:2 Profile, supporting up to 4:4:4 chroma sampling, up to 14 bits per sample, and additionally supporting efficient lossless region coding and the coding of each picture as three separate color planes.

For camcorders, editing, and professional applications, the standard contains four additional "Intra-frame-only profiles, which are defined as simple subsets of other corresponding profiles. These are mostly for professional (e.g., camera and editing system) applications:

High 10 Intra Profile (110 with constraint set 3)
The High 10 Profile constrained to all-Intra use.
High 4:2:2 Intra Profile (122 with constraint set 3)
The High 4:2:2 Profile constrained to all-Intra use.
High 4:4:4 Intra Profile (244 with constraint set 3)
The High 4:4:4 Profile constrained to all-Intra use.
CAVLC 4:4:4 Intra Profile (44)
The High 4:4:4 Profile constrained to all-Intra use and to CAVLC entropy coding (i.e., not supporting CABAC).

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[edit]

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:0

 
4:2:0

 
4:2:0

 
4:2:0

 
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

Levels[edit]

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[40]
Level
Max decoding speed Max frame size Max video bit rate for video coding layer (VCL) kbit/s (Baseline, Extended and Main Profiles) Examples for high resolution
@ highest frame rate
Toggle additional details

Luma samples/s Macroblocks/s Luma samples Macroblocks
1 380,160 1,485 25,344 99 64
128×96@30
176×144@15
1b 380,160 1,485 25,344 99 128
128×96@30
176×144@15
1.1 768,000 3,000 101,376 396 192
128x96@60
176×144@30
352×288@7.5
1.2 1,536,000 6,000 101,376 396 384
128x96@120
176×144@60
352×288@15
1.3 3,041,280 11,880 101,376 396 768
128x96@172
176×144@120
352×288@30
2 3,041,280 11,880 101,376 396 2,000
128x96@172
176x144@120
352×288@30
2.1 5,068,800 19,800 202,752 792 4,000
176x144@172
352×240@60
352×288@50
352×480@30
352×576@25
2.2 5,184,000 20,250 414,720 1,620 4,000
176×144@172
352×480@30
352×576@25
720×480@15
720×576@12.5
3 10,368,000 40,500 414,720 1,620 10,000
176×144@172
352×240@120
352×480@60
720×480@30
720×576@25
3.1 27,648,000 108,000 921,600 3,600 14,000
352x288@172
352x576@130
640x480@90
720×576@60
1,280×720@30
3.2 55,296,000 216,000 1,310,720 5,120 20,000
640x480@172
720x480@160
720x576@130
1,280×720@60
4 62,914,560 245,760 2,097,152 8,192 20,000
720x480@172
720x576@150
1,280×720@60
2,048×1,024@30
4.1 62,914,560 245,760 2,097,152 8,192 50,000
720x480@172
720x576@150
1,280×720@60
2,048×1,024@30
4.2 133,693,440 522,240 2,228,224 8,704 50,000
720x576@172
1,280×720@140
2,048×1,080@60
5 150,994,944 589,824 5,652,480 22,080 135,000
1,024×768@172
1,280×720@160
2,048×1,080@60
2,560×1,920@30
3,680×1,536@25
5.1 251,658,240 983,040 9,437,184 36,864 240,000
1,280×720@172
1,920×1,080@120
2,048×1,536@80
4,096×2,048@30
5.2 530,841,600 2,073,600 9,437,184 36,864 240,000
1,920×1,080@172
2,048×1,536@160
4,096×2,160@60
6 1,069,547,520 4,177,920 35,651,584 139,264 240,000
2,048×1,536@300
4,096×2,160@120
8,192×4,320@30
6.1 2,139,095,040 8,355,840 35,651,584 139,264 480,000
2,048×1,536@300
4,096×2,160@240
8,192×4,320@60
6.2 4,278,190,080 16,711,680 36,651,584 139,264 800,000
4,096*2,304@300
8,192×4,320@120

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[edit]

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
6
6.1
6.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
696,320
696,320
696,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.

Implementations[edit]

In 2009, the "HTML5 working group was split between supporters of Ogg "Theora, a free video format which is thought["by whom?] 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 Ogg Theora (now Google, Mozilla and Opera all support Theora and "WebM with "VP8).[41] Microsoft, with the release of Internet Explorer 9, has added support for HTML 5 video encoded using H.264. At the Gartner Symposium/ITXpo in November 2010, Microsoft CEO Steve Ballmer answered the question "HTML 5 or "Silverlight?" by saying "If you want to do something that is universal, there is no question the world is going HTML5."[42] In January 2011, Google announced that they were pulling support for H.264 from their Chrome browser and supporting both Theora and "WebM/"VP8 to use only open formats.[43]

On March 18, 2012, "Mozilla announced support for H.264 in Firefox on mobile devices, due to prevalence of H.264-encoded video and the increased power-efficiency of using dedicated H.264 decoder hardware common on such devices.[44] On February 20, 2013, Mozilla implemented support in Firefox for decoding H.264 on Windows 7 and above. This feature relies on Windows' built in decoding libraries.[45] Firefox 35.0, released on January 13, 2015 supports H.264 on OS X 10.6 and higher.[46]

On October 30, 2013, "Rowan Trollope from "Cisco Systems announced that Cisco would release both binaries and source code of an H.264 video codec called "OpenH264 under the "Simplified BSD license, and pay all royalties for its use to MPEG LA themselves for any software projects that use Cisco's precompiled binaries (thus making Cisco's OpenH264 binaries free to use); any software projects that use Cisco's source code instead of its binaries would be legally responsible for paying all royalties to MPEG LA themselves, however. Current target CPU architectures are x86 and ARM, and current target operating systems are Linux, Windows XP and later, Mac OS X, and Android; iOS is notably absent from this list because it doesn't allow applications to fetch and install binary modules from the Internet.[47][48][49] Also on October 30, 2013, "Brendan Eich from "Mozilla wrote that it would use Cisco's binaries in future versions of Firefox to add support for H.264 to Firefox where platform codecs are not available.[50]

Cisco published the source to OpenH264 on December 9, 2013.[51]

Software encoders[edit]

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[52]
4:4:4[53]
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[54] 10 8 8 8 8 10 12
Predictive lossless coding No No No Yes[55] No No No No No No No

Hardware[edit]

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 "Intel ""Sandy Bridge" "Core i3/i5/i7 processors introduced at the January 2011 CES ("Consumer Electronics Show) offer an on-chip hardware full HD H.264 encoder, known as "Intel Quick Sync Video.[56][57]

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&Media, Allegro DVT, "On2 (formerly Hantro, acquired by Google), "Imagination Technologies, NGCodec. Some companies have both FPGA and ASIC product offerings.[58]

Texas Instruments manufactures a line of ARM + DSP cores that perform DSP H.264 BP encoding 1080p at 30fps.[59] This permits flexibility with respect to codecs (which are implemented as highly optimized DSP code) while being more efficient than software on a generic CPU.

Licensing[edit]

In countries where "patents on software algorithms are upheld, vendors and commercial users of products that use H.264/AVC are expected to pay patent licensing royalties for the patented technology that their products use.[60] This applies to the Baseline Profile as well.[61]

A private organization known as "MPEG LA, which is not affiliated in any way with the MPEG standardization organization, administers the licenses for patents applying to this standard, as well as the "patent pools for MPEG-2 Part 1 Systems, MPEG-2 Part 2 Video, MPEG-4 Part 2 Video, HEVC, MPEG-DASH, and other technologies. The MPEG LA H.264 patents in the US last at least until 2027.[62]

On August 26, 2010, MPEG LA announced that H.264 encoded internet video that is free to end users will never be charged royalties.[63] All other royalties remain in place, such as royalties for products that decode and encode H.264 video as well as to operators of free television and subscription channels.[64] The license terms are updated in 5-year blocks.[65]

In 2005, Qualcomm, which was the assignee of U.S. Patent 5,452,104 and U.S. Patent 5,576,767, sued Broadcom in US District Court, alleging that Broadcom infringed the two patents by making products that were compliant with the H.264 video compression standard.[66] In 2007, the District Court found that the patents were unenforceable because Qualcomm had failed to disclose them to the JVT prior to the release of the H.264 standard in May 2003.[66] In December 2008, the US Court of Appeals for the Federal Circuit affirmed the District Court's order that the patents be unenforceable but remanded to the District Court with instructions to limit the scope of unenforceability to H.264 compliant products.[66]

See also[edit]

References[edit]

  1. ^ Ozer, Jan. "Encoding for Multiple Screen Delivery, Section 3, Lecture 7: Introduction to H.264". Udemy. Retrieved 10 October 2016. 
  2. ^ "Delivering 8K using AVC/H.264". Mystery Box. Retrieved 2017-08-23. 
  3. ^ "AVC/H.264 FAQ". www.mpegla.com. Retrieved 2016-09-15. 
  4. ^ "H.262 : Information technology — Generic coding of moving pictures and associated audio information: Video". Retrieved 2007-04-15. 
  5. ^ Joint Video Team, "ITU-T web site.
  6. ^ "ITU-T Recommendation H.264 (05/2003)". ITU. 2003-05-30. Retrieved 2013-04-18. 
  7. ^ "ITU-T Recommendation H.264 (05/2003) Cor. 1 (05/2004)". ITU. 2004-05-07. Retrieved 2013-04-18. 
  8. ^ "ITU-T Recommendation H.264 (03/2005)". ITU. 2005-03-01. Retrieved 2013-04-18. 
  9. ^ "ITU-T Recommendation H.264 (2005) Cor. 1 (09/2005)". ITU. 2005-09-13. Retrieved 2013-04-18. 
  10. ^ a b "ITU-T Recommendation H.264 (2005) Amd. 1 (06/2006)". ITU. 2006-06-13. Retrieved 2013-04-18. 
  11. ^ "ITU-T Recommendation H.264 (2005) Amd. 2 (04/2007)". ITU. 2007-04-06. Retrieved 2013-04-18. 
  12. ^ "ITU-T Recommendation H.264 (11/2007)". ITU. 2007-11-22. Retrieved 2013-04-18. 
  13. ^ "ITU-T Recommendation H.264 (2007) Cor. 1 (01/2009)". ITU. 2009-01-13. Retrieved 2013-04-18. 
  14. ^ a b "ITU-T Recommendation H.264 (03/2009)". ITU. 2009-03-16. Retrieved 2013-04-18. 
  15. ^ a b "ITU-T Recommendation H.264 (03/2010)". ITU. 2010-03-09. Retrieved 2013-04-18. 
  16. ^ a b "ITU-T Recommendation H.264 (06/2011)". ITU. 2011-06-29. Retrieved 2013-04-18. 
  17. ^ "ITU-T Recommendation H.264 (01/2012)". ITU. 2012-01-13. Retrieved 2013-04-18. 
  18. ^ a b c d "ITU-T Recommendation H.264 (04/2013)". ITU. 2013-06-12. Retrieved 2013-06-16. 
  19. ^ a b "ITU-T Recommendation H.264 (02/2014)". ITU. 2014-11-28. Retrieved 2016-02-28. 
  20. ^ "ITU-T Recommendation H.264 (02/2016)". ITU. 2016-02-13. Retrieved 2017-06-14. 
  21. ^ "ITU-T Recommendation H.264 (10/2016)". ITU. 2016-10-14. Retrieved 2017-06-14. 
  22. ^ "ITU-T Recommendation H.264 (04/2017)". ITU. 2017-04-13. Retrieved 2017-06-14. 
  23. ^ Wenger; et al. "RFC 3984 : RTP Payload Format for H.264 Video": 2. 
  24. ^ "Which recording mode is equivalent to the image quality of the High Definition Video (HDV) format?". Sony eSupport. 
  25. ^ "ATSC Standard A/72 Part 1: Video System Characteristics of AVC in the ATSC Digital Television System" (PDF). Retrieved 2011-07-30. 
  26. ^ "ATSC Standard A/72 Part 2: AVC Video Transport Subsystem Characteristics" (PDF). Retrieved 2011-07-30. 
  27. ^ "ATSC Standard A/153 Part 7: AVC and SVC Video System Characteristics" (PDF). Retrieved 2011-07-30. 
  28. ^ a b "Sony introduces new XAVC recording format to accelerate 4K development in the professional and consumer markets". Sony. 2012-10-30. Retrieved 2012-11-01. 
  29. ^ a b "Sony introduces new XAVC recording format to accelerate 4K development in the professional and consumer markets" (PDF). Sony. 2012-10-30. Retrieved 2012-11-01. 
  30. ^ "Sony supports "Beyond HD" strategy with new full sensor cameras". broadcastengineering.com. 2012-10-30. Retrieved 2012-11-01. 
  31. ^ Steve Dent (2012-10-30). "Sony goes Red-hunting with PMW-F55 and PMW-F5 pro CineAlta 4K Super 35mm sensor camcorders". Engadget. Retrieved 2012-11-05. 
  32. ^ "F55 CineAlta 4K the future, ahead of schedule" (PDF). Sony. 2012-10-30. Retrieved 2012-11-01. 
  33. ^ "Ultra-fast "SxS PRO+" memory cards transform 4K video capture". Sony. Retrieved 2012-11-05. 
  34. ^ "Ultra-fast "SxS PRO+" memory cards transform 4K video capture" (PDF). Sony. Retrieved 2012-11-05. 
  35. ^ "The H.264/AVC Advanced Video Coding Standard: Overview and Introduction to the Fidelity Range Extensions" (PDF). Retrieved 2011-07-30. 
  36. ^ a b c RFC 3984, p.3
  37. ^ Apple Inc. (1999-03-26). "H.264 FAQ". Apple. Archived from the original on March 7, 2010. Retrieved 2010-05-17. 
  38. ^ Karsten Suehring. "H.264/AVC JM Reference Software Download". Iphome.hhi.de. Retrieved 2010-05-17. 
  39. ^ "TS 101 154 – V1.9.1 – Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG-2 Transport Stream" (PDF). Retrieved 2010-05-17. 
  40. ^ Advanced video coding for generic audiovisual services. ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU. p. 324. Recommendation ITU-T H.264 
  41. ^ "Decoding the HTML 5 video codec debate". Ars Technica. 2009-07-06. Retrieved 2011-01-12. 
  42. ^ "Steve Ballmer, CEO Microsoft, interviewed at Gartner Symposium/ITxpo Orlando 2010". Gartnervideo. November 2010. Retrieved 2011-01-12. 
  43. ^ "HTML Video Codec Support in Chrome". 2011-01-11. Retrieved 2011-01-12. 
  44. ^ "Video, Mobile, and the Open Web". 2012-03-18. Retrieved 2012-03-20. 
  45. ^ "WebRTC enabled, H.264/MP3 support in Win 7 on by default, Metro UI for Windows 8 + more – Firefox Development Highlights". hacks.mozilla.org. mozilla. 2013-02-20. Retrieved 2013-03-15. 
  46. ^ Firefox Notes Version 35.0
  47. ^ "Open-Sourced H.264 Removes Barriers to WebRTC". 2013-10-30. Retrieved 2013-11-01. 
  48. ^ "Cisco OpenH264 project FAQ". 2013-10-30. Retrieved 2013-11-01. 
  49. ^ "OpenH264 Simplified BSD License". 2013-10-27. Retrieved 2013-11-21. 
  50. ^ "Video Interoperability on the Web Gets a Boost From Cisco's H.264 Codec". 2013-10-30. Retrieved 2013-11-01. 
  51. ^ https://github.com/cisco/openh264/commit/59dae50b1069dbd532226ea024a3ba3982ab4386
  52. ^ "x264 4:2:2 encoding support", Retrieved 2011-09-22.
  53. ^ "x264 4:4:4 encoding support", Retrieved 2011-06-22.
  54. ^ "x264 support for 9 and 10-bit encoding", Retrieved 2011-06-22.
  55. ^ "x264 replace High 4:4:4 profile lossless with High 4:4:4 Predictive", Retrieved 2011-06-22.
  56. ^ "Quick Reference Guide to generation Intel® Core™ Processor Built-in Visuals". Intel® Software Network. 2010-10-01. Retrieved 2011-01-19. 
  57. ^ "Intel® Quick Sync Video". www.intel.com. 2010-10-01. Retrieved 2011-01-19. 
  58. ^ "Design-reuse.com". Design-reuse.com. 1990-01-01. Retrieved 2010-05-17. 
  59. ^ "Category:DM6467 - Texas Instruments Embedded Processors Wiki". Processors.wiki.ti.com. 2011-07-12. Retrieved 2011-07-30. 
  60. ^ http://www.mpegla.com/main/programs/AVC/Documents/avcweb.pdf
  61. ^ "OMS Video, A Project of Sun's Open Media Commons Initiative". Retrieved 2008-08-26. 
  62. ^ http://www.osnews.com/story/24954/US_Patent_Expiration_for_MP3_MPEG-2_H_264 has a MPEG LA patent US 7826532 that was filed in September 5, 2003 and has a 1546 day term extension. http://patft1.uspto.gov/netacgi/nph-Parser?patentnumber=7826532 http://www.google.com/patents/about?id=2onYAAAAEBAJ
  63. ^ "MPEG LA’s AVC License Will Not Charge Royalties for Internet Video that is Free to End Users through Life of License" (PDF). MPEG LA. 2010-08-26. Retrieved 2010-08-26. 
  64. ^ Hachman, Mark (2010-08-26). "MPEG LA Cuts Royalties from Free Web Video, Forever". pcmag.com. Retrieved 2010-08-26. 
  65. ^ "AVC FAQ". MPEG LA. 2002-08-01. Retrieved 2010-05-17. 
  66. ^ a b c See Qualcomm Inc. v. Broadcom Corp., No. 2007-1545, 2008-1162 (Fed. Cir. December 1, 2008). For articles in the popular press, see signonsandiego.com, "Qualcomm loses its patent-rights case" and "Qualcomm's patent case goes to jury"; and bloomberg.com "Broadcom Wins First Trial in Qualcomm Patent Dispute"

Further reading[edit]

External links[edit]

) )