H.264 Video Types

http://msdn.microsoft.com/en-us/library/windows/desktop/dd757808(v=vs.85).aspx

H.264 Video Types

The following media subtypes are defined for H.264 video.

Subtype	FOURCC	Description
MEDIASUBTYPE_AVC1	'AVC1'	H.264 bitstream without start codes.
MEDIASUBTYPE_H264	'H264'	H.264 bitstream with start codes.
MEDIASUBTYPE_h264	'h264'	Equivalent to MEDIASUBTYPE_H264, with a different FOURCC.
MEDIASUBTYPE_X264	'X264'	Equivalent to MEDIASUBTYPE_H264, with a different FOURCC.
MEDIASUBTYPE_x264	'x264'	Equivalent to MEDIASUBTYPE_H264, with a different FOURCC.

 

These subtype GUIDs are declared in wmcodecdsp.h.

The main difference between these media types is the presence of start codes in the bitstream. If the subtype isMEDIASUBTYPE_AVC1, the bitstream does not contain start codes.

H.264 Bitstream with Start Codes

H.264 bitstreams that are transmitted over the air, or contained in MPEG-2 program or transport streams, or recorded on HD-DVD, are formatted as described in Annex B of ITU-T Rec. H.264. According to this specification, the bitstream consists of a sequence of network abstraction layer units (NALUs), each of which is prefixed with a start code equal to 0x000001 or 0x00000001.

When start codes are present in the bitstream, the following media type is used:

Major type	MEDIATYPE_Video
Subtypes	MEDIASUBTYPE_H264, MEDIASUBTYPE_h264, MEDIASUBTYPE_X264, or MEDIASUBTYPE_x264
Format type	FORMAT_VideoInfo, FORMAT_VideoInfo2, FORMAT_MPEG2Video, or GUID_NULL

 

If the format type is GUID_NULL, no format structure is present.

When the bitstream contains start codes, any of the format types listed here is sufficient, because the decoder does not require any additional information to parse the stream. The bitstream already contains all of the information needed by the decoder, and the start codes enable the decoder to locate the start of each NALU.

The following subtypes are equivalent:

H.264 Bitstream Without Start Codes

The MP4 container format stores H.264 data without start codes. Instead, each NALU is prefixed by a length field, which gives the length of the NALU in bytes. The size of the length field can vary, but is typically 1, 2, or 4 bytes.

When start codes are not present in the bitstream, the following media type is used.

Major type	MEDIATYPE_Video
Subtype	MEDIASUBTYPE_AVC1
Format type	FORMAT_MPEG2Video

 

The format block is an MPEG2VIDEOINFO structure. This structure should be filled in as follows:

• hdr: A VIDEOINFOHEADER2 structure that describes the bitstream. No color table is present after theBITMAPINFOHEADER portion of the structure, and biClrUsed must be zero.
• dwStartTimeCode: Not used. Set to zero.
• cbSequenceHeader: The length of the dwSequenceHeader array in bytes.
• dwProfile: Specifies the H.264 profile.
• dwLevel: Specifies the H.264 level.
• dwFlags: The number of bytes used for the length field that appears before each NALU. The length field indicates the size of the following NALU in bytes. For example, if dwFlags is 4, each NALU is preceded by a 4-byte length field. The valid values are 1, 2, and 4.
• dwSequenceHeader: A byte array that may contain sequence parameter set (SPS) and picture parameter set (PPS) NALUs.

The MP4 container might contain sequence parameter sets (SPS) or picture parameter sets (PPS) as special NAL units in file headers or in a separate stream (distinct from the video stream). When the format is established, the media type can specify SPS and PPS NAL units in the dwSequenceHeader array. If cbSequenceHeader is greater than zero,dwSequenceHeader is the start of a byte array containing SPS and PPS NALUs, delimited by 2-byte length fields, all in network byte order (big-endian). It is possible to have both SPS and PPS, only one of these types, or none. The actual type of each NALU can be determined by examining the nal_unit_type field of the NALU itself.

When this media type is used, each media sample starts at the beginning of a NALU, and NAL units do not span samples. This enables the decoder to recover from data corruption or dropped samples.

 

 

Send comments about this topic to Microsoft

Build date: 9/2/2013