Media (Intel® Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools like Intel® oneAPI Video Processing Library and Intel® Media SDK
Announcements
The Intel Media SDK project is no longer active. For continued support and access to new features, Intel Media SDK users are encouraged to read the transition guide on upgrading from Intel® Media SDK to Intel® Video Processing Library (VPL), and to move to VPL as soon as possible.
For more information, see the VPL website.
3083 Discussions

Understanding MFXVideoDECODE_DecodeHeader

sjboone
Beginner
‎03-15-2012 11:52 AM
968 Views
Hi

I am callingMFXVideoDECODE_DecodeHeader in an attempt to initialize the mfxVideoParam structure. The source of the H.264 encoded data is in the following file (http://software.intel.com/file/m/42421) which was generated using the Intel Media SDK (version 1.3). The sequence and picture parameter sets are contained in the first 46 bytes of the file.

If I provide the first 50 or 75 bytes fromthis file to the MFXVideoDECODE_DecodeHeader function (via the mfxBitStream parameter), the function returns MFX_ERR_NONE and the mfxVideoParam structure is filled out correctly. If I provide a different number of bytes (e.g. 46, 47, 48, 49, 70, 71, 72, 73, 74), the function returns MFX_ERR_MORE_DATA.

I expected to be able to provide only the first 46 bytes. Can anyone explain to me why this does not work?

Thanks, Steve
0 Kudos

Link Copied

1 Reply
Petter_L_Intel
Employee
‎03-15-2012 02:24 PM
968 Views
Hi Steve,

I was able to reproduce the issue you reported. Looking at the implementation of DecodeHeader it seems we likely have a bug here.

Thanks for sharing your finding and helping us improve Intel Media SDK. We hope to provide a solution for this in both SW and HW implementation as soon as possible.

In the meantime you should be able to workaround the issue padding the data provided to DecodeHeader.

Regards,
Petter
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

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