This article may have too many, and could require to meet Wikipedia's. Per the, please remove duplicate links, and any links that are not relevant to the context. (May 2018) H.264 / MPEG-4 AVC Developed by, Type of format Extended from, Extended to ISO/IEC 14496–10, ITU-T H.264? No Website H.264 or MPEG-4 Part 10, Advanced Video Coding ( MPEG-4 AVC) is a block-oriented -based.

As of 2014, it is one of the most commonly used formats for the recording, compression, and distribution of video content. It supports resolutions up to 8192×4320, including. 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, or ), 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, storage, / packet networks, and multimedia 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, although it is also possible to create truly regions within lossy-coded pictures or to support rare use cases for which the entire encoding is lossless. H.264 was developed by the (VCEG) together with the (MPEG).

The project partnership effort is known as the Joint Video Team (JVT). The ITU-T H.264 standard and the ISO/IEC 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. (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; 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, and the, Web software such as the and, and also various broadcasts over terrestrial (, or ), cable , and satellite ( and ). H.264 is protected by owned by various parties.

A license covering most (but not all) patents essential to H.264 is administered. 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 pays royalties to MPEG LA on behalf of the users of binaries for its H.264 encoder. Contents. Naming The H.264 name follows the naming convention, where the standard is a member of the H.26x line of video coding standards; the MPEG-4 AVC name relates to the naming convention in /, 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 and the, where MPEG-2 video is known to the ITU-T community as H.262.

) Some software programs (such as ) internally identify this standard as AVC1. History In early 1998, the (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. Was chaired by (, formerly, U.S.).

The first draft design for that new standard was adopted in August 1999. In 2000, (, Germany) became VCEG co-chair. In December 2001, VCEG and the Moving Picture Experts Group ( – /WG 11) formed a Joint Video Team (JVT), with the charter to finalize the video coding standard. Formal approval of the specification came in March 2003. The JVT was (is) chaired by, and (, U.S.: later, 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 (SVC).

The JVT management team was extended by Jens-Rainer Ohm (, Germany). From July 2006 to November 2009, the JVT worked on (MVC), an extension of H.264/AVC towards. 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 (=) 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 (the High 4:4:4 profile) that industry feedback indicated should have been designed differently. The next major feature added to the standard was (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 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 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 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 extensions were completed in November 2007. The next major feature added to the standard was (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 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 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 (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 (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 identifiers (including support of for ) 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, (HLG), and additional color-related VUI code points and SEI messages. Applications. Further information: 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 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. Sony claims that 9 Mbit/s AVC recording mode is equivalent to the image quality of the format, which uses approximately 18–25 Mbit/s. 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 format and the now-discontinued format include the H.264/AVC High Profile as one of three mandatory video compression formats. The Digital Video Broadcast project approved the use of H.264/AVC for broadcast television in late 2004.

The (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. It has also been approved for use with the more recent (Mobile/Handheld) standard, using the AVC and SVC portions of H.264. The (Closed Circuit TV) and markets have included the technology in many products. Many common use H.264 video wrapped in QuickTime MOV containers as the native recording format. Derived formats is a high-definition recording format designed by and that uses H.264 (conforming to H.264 while adding additional application-specific features and constraints). Is an -only compression format, developed.

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. XAVC can support (4096 × 2160 and 3840 × 2160) at up to 60 (fps). Sony has announced that cameras that support XAVC include two cameras—the Sony PMW-F55 and Sony PMW-F5. The Sony PMW-F55 can record XAVC with 4K resolution at 30 fps at 300 and 2K resolution at 30 fps at 100 Mbit/s. XAVC can record 4K resolution at 60 fps with 4:2:2 chroma subsampling at 600 Mbit/s. 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 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-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 (VBSMC) with block sizes as large as 16×16 and as small as 4×4, enabling precise segmentation of moving regions.

The supported 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 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, including I-macroblocks, resulting in much more efficient encoding when using B-frames.

This feature was notably left out from. Six-tap filtering for derivation of half-pel sample predictions, for sharper subpixel motion-compensation. Quarter-pixel motion is derived by linear interpolation of the halfpel values, to save processing power. precision for motion compensation, enabling precise description of the displacements of moving areas. For the resolution is typically halved both vertically and horizontally (see ) 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, 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 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 prediction block sizes of 16×16, 8×8, and 4×4 (of which only one type can be used within each ). macroblock coding features including:. 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 -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 signals with little of the ' 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, T.Natarajan and K.R.Rao, which is Citation 1 in. 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 performed on 'DC' coefficients of the primary spatial transform applied to chroma DC coefficients (and also in one special case) to obtain even more compression in smooth regions. 4,096.2,304@3008,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 samples is 16x16=256 times the number of macroblocks (and the number of 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 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 In 2009, the was split between supporters of Ogg, 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 Ogg Theora (now Google, Mozilla and Opera all support Theora and with ). 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?' By saying 'If you want to do something that is universal, there is no question the world is going HTML5.' In January 2011, Google announced that they were pulling support for H.264 from their Chrome browser and supporting both Theora and / to use only open formats. On March 18, 2012, 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.

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. Firefox 35.0, released on January 13, 2015 supports H.264 on OS X 10.6 and higher.

On October 30, 2013, from announced that Cisco would release both binaries and source code of an H.264 video codec called under the, and pay all royalties for its use to MPEG LA for any software projects that use Cisco's precompiled binaries, thus making Cisco's OpenH264 binaries free to use. However, any software projects that use Cisco's source code instead of its binaries would be legally responsible for paying all royalties to MPEG LA. 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. Also on October 30, 2013, from 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. Cisco published the source to OpenH264 on December 9, 2013. Software encoders AVC software implementations Feature 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 C b and C r 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 Hardware. See also: and 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 , 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 ' processors introduced at the January 2011 CES offer an on-chip hardware full HD H.264 encoder, known as.

A hardware H.264 encoder can be an or an. 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, Allegro DVT, (formerly Hantro, acquired by Google), NGCodec. Some companies have both FPGA and ASIC product offerings. Texas Instruments manufactures a line of ARM + DSP cores that perform DSP H.264 BP encoding 1080p at 30fps.

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. See also: and In countries where 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.

This applies to the Baseline Profile as well. A private organization known as, 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 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. On August 26, 2010, MPEG LA announced that H.264 encoded Internet video that is free to end users will never be charged royalties.

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. The license terms are updated in 5-year blocks. An actual Status of Patents in law and expired at end of 2018 is available at 123 pages.

In 2005, Qualcomm, which was the assignee of and, 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. 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. 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. See also. References. Ozer, Jan.

Retrieved 10 October 2016. Retrieved 2017-08-23. Retrieved 2016-09-15. Retrieved 2007-04-15. Retrieved 2013-04-18. Retrieved 2013-04-18.

Retrieved 2013-04-18. Retrieved 2013-04-18. Retrieved 2013-04-18. Retrieved 2013-04-18. Retrieved 2013-04-18. Retrieved 2013-04-18. Retrieved 2013-04-18.

Mpeg 2 Video Linear Pcm Timecode Codec For Mac Download

Retrieved 2013-04-18. Retrieved 2013-04-18. Retrieved 2013-04-18. Retrieved 2013-06-16. Retrieved 2016-02-28.

Retrieved 2017-06-14. Retrieved 2017-06-14. Retrieved 2017-06-14. Wenger; et al.: 2. Sony eSupport. Archived from on November 9, 2017.

Retrieved December 8, 2018. Archived from (PDF) on August 7, 2011. Retrieved July 30, 2011.

Archived from (PDF) on August 7, 2011. Retrieved July 30, 2011. Archived from (PDF) on July 26, 2011. Retrieved July 30, 2011. Retrieved 2012-11-01.

Retrieved 2012-11-01. Steve Dent (2012-10-30). Retrieved 2012-11-05. October 30, 2012. Archived from (PDF) on November 19, 2012. Retrieved November 1, 2012. Archived from on March 8, 2013.

Retrieved November 5, 2012. Archived from (PDF) on April 2, 2015. Retrieved November 5, 2012. Retrieved 2011-07-30. ^, p.3. Apple Inc. Archived from on March 7, 2010.

Retrieved 2010-05-17. Karsten Suehring. Retrieved 2010-05-17. Retrieved 2010-05-17. ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU. Recommendation ITU-T H.264.

Ars Technica. Retrieved 2011-01-12. November 2010. Retrieved 2011-01-12.

Retrieved 2011-01-12. Retrieved 2012-03-20. Retrieved 2013-03-15. Retrieved 2013-11-01. Retrieved 2013-11-01. Retrieved 2013-11-21.

Mpeg 2 Video Linear Pcm Timecode Codec For Mac Mac

Retrieved 2013-11-01., Retrieved 2011-09-22., Retrieved 2011-06-22., Retrieved 2011-06-22., Retrieved 2011-06-22. Intel® Software Network. Retrieved 2011-01-19. Retrieved 2011-01-19. Retrieved 2010-05-17.

Retrieved 2011-07-30. Archived from on May 11, 2010. Retrieved August 26, 2008.

Mpeg 2 Video Linear Pcm Timecode Codec For Mac Free

has a MPEG LA patent US 7826532 that was filed in September 5, 2003 and has a 1546 day term extension. Retrieved 2010-08-26. Hachman, Mark (2010-08-26). Retrieved 2010-08-26. Retrieved 2010-05-17. ^ See, No. 2007-1545, 2008-1162 (Fed.

December 1, 2008). For articles in the popular press, see signonsandiego.com, and; and bloomberg.com Further reading.

Attention, Internet Explorer User Announcement: Jive has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, Jive no longer supports Internet Explorer 7. Jive will not function with this version of Internet Explorer. Please consider upgrading to a more recent version of Internet Explorer, or trying another browser such as Firefox, Safari, or Google Chrome. (Please remember to honor your company's IT policies before installing new software!).