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.
3066 Discussions

Mapping the functions listed in SDK Developer Reference to Sample Code

ming-cong_w_
Beginner
‎01-09-2017 07:34 AM
270 Views

Hi,

 I am tracing the sample code under Tutorial, like simple_session and sample_multi_transcode. And also trying to mapping the behavior and functions which are listed in SDK Developer Reference.

 But I found, it's hard to directly map them together. For example,  

 Creating Sessions list on manuals are always using MFXInit. But, refer to the source code, it aways implemented by 

// Initialize Intel Media SDK Session, device/display and memory manager
mfxStatus Initialize(mfxIMPL impl, mfxVersion ver, MFXVideoSession* pSession, mfxFrameAllocator* pmfxAllocator, bool bCreateSharedHandles = false);

 Why MFXInit no longer used in the sample code? Or I miss understand something? Thanks.

 

 

 

0 Kudos

Link Copied

0 Replies
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). 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.