Quantization parameter, and similar information). Spatial address of the first macroblock in the slice, the initial Macroblocks and the information of the slice header (containing the String that contains the macroblock data of an integer number of Inter picture prediction with motion compensation and transformĬoding of the residual signal. Most of today's video codecs, a macroblock-based coder that uses Mechanisms such as transform, quantization, and motion-compensated The VCL contains the signal processing functionality of the codec The codec specification itself conceptually distinguishes betweenĪ Video Coding Layer (VCL) and a Network Abstraction Layer (NAL). Quality, for example, was reported to be achievable at 1.5 Mbit/s,Ĭompared to the current operation point of MPEG 2 video at around 3.5 State of technology, the overall performance of H.264 is such thatīitrate savings of 50% or more are reported. Streaming applications to HDTV broadcast and Digital CinemaĪpplications with nearly lossless coding. The H.264 video codec has a very broad application range that coversĪll forms of digital compressed video, from low bitrate Internet ISO/IEC counterpart of the coding standard. In this memo, the name H.264 is used for theĬodec and the standard, but this memo is equally applicable to the International Standard 14496-10 (both also known as Advanced Standard known as ITU-T Recommendation H.264 and ISO/IEC This memo specifies an RTP payload specification for the video coding RFC 6184 RTP Payload Format for H.264 Video May 2011 1. Robust Transmission Scheduling of Redundant Coded Example of Multi-Picture Slice Interleaving. Informative Appendix: Rationale for Decoding Order Number. Robust Packet Scheduling in Video Streaming. Video Telephony or Streaming with FUs and ForwardĮrror Correction. Video Telephony, Interleaved Packetization Using Video Telephony, No Slice Data Partitioning, No Video Telephony According to Annex A of ITU-T Informative Appendix: Application Examples. Gradual Recovery Procedure to Respond toĪ Request for a Decoder Refresh Point. IDR Procedure to Respond to a Request forĪ Decoder Refresh Point. Transport of Parameter Sets (Informative). Decoder Refresh Point Procedure Using In-Band Usage in Declarative Session Descriptions. Mapping of Payload Type Parameters to SDP. RFC 6184 RTP Payload Format for H.264 Video May 2011 8. Single NAL Unit and Non-Interleaved Mode. The Trust Legal Provisions and are provided without warranty asġ. Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal RFC 6184 RTP Payload Format for H.264 Video May 2011Ĭopyright (c) 2011 IETF Trust and the persons identified as the Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. Issues on backward compatibility to RFC 3984 are Transmission, to high bitrate video-on-demand. The payload format has wideĪpplicability, as it supports applications from simple low bitrateĬonversational usage, to Internet video streaming with interleaved Network Abstraction Layer Units (NALUs), produced by an H.264 videoĮncoder, in each RTP payload. The RTP payload format allows for packetization of one or more Scalable Video Coding (SVC) extension and the Multiview Video CodingĮxtension, for which the RTP payload formats are defined elsewhere. ISO/IEC International Standard 14496-10 video codec, excluding the Recommendation H.264 video codec and the technically identical This memo describes an RTP Payload format for the ITU-T Internet Engineering Task Force (IETF) Y.-K.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |