mfxExtPictureTimingSEI

Definition

 

 

typedef struct {

  mfxExtBuffer    Header;

  mfxU32          reserved[14];

 

  struct {

      mfxU16    ClockTimestampFlag;

      mfxU16    CtType;

      mfxU16    NuitFieldBasedFlag;

      mfxU16    CountingType;

      mfxU16    FullTimestampFlag;

      mfxU16    DiscontinuityFlag;

      mfxU16    CntDroppedFlag;

      mfxU16    NFrames;

      mfxU16    SecondsFlag;

      mfxU16    MinutesFlag;

      mfxU16    HoursFlag;

      mfxU16    SecondsValue;

      mfxU16    MinutesValue;

      mfxU16    HoursValue;

      mfxU32    TimeOffset;

  } TimeStamp[3];

} mfxExtPictureTimingSEI;

 

Description

 

 

The mfxExtPictureTimingSEI structure configures the H.264 picture timing SEI message. The encoder ignores it if HRD information in stream is absent and PicTimingSEI option in mfxExtCodingOption structure is turned off. See mfxExtCodingOption for details.

If the application attaches this structure to the mfxVideoParam structure during initialization, the encoder inserts the picture timing SEI message based on provided template in every access unit of coded bitstream.

If application attaches this structure to the mfxEncodeCtrl structure at runtime, the encoder inserts the picture timing SEI message based on provided template in access unit that represents current frame.

 

Members

 

 

Header.BufferId

Must be MFX_EXTBUFF_PICTURE_TIMING_SEI

 

 

ClockTimestampFlag

CtType

NuitFieldBasedFlag

CountingType

FullTimestampFlag

DiscontinuityFlag

CntDroppedFlag

NFrames

SecondsFlag

MinutesFlag

HoursFlag

SecondsValue

MinutesValue

HoursValue

TimeOffset

These parameters define the picture timing information. An invalid value of 0xFFFF indicates that application does not set the value and encoder must calculate it.

See Annex D of the ISO*/IEC* 14496-10 specification for the definition of these parameters.

 

 

Change History

 

This structure is available since SDK API 1.3.

 

 

 

 

 

For more complete information about compiler optimizations, see our Optimization Notice.