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

H264 decoder: access violation

etep2010
Beginner
‎06-19-2014 02:44 AM
510 Views

Hello,

 

I use in loop the sample_decode project with Visual Studio C++ 2010 PRO and Windows 7 PRO .

I've fixed to open alternatively 2 files (only progressive video): one with HD 1080P30 H264 video and the second one with 720P60 H264  video.

I did'nt create output file. I want only test he H264 decoder for simple H264 frame ( no GOP ).

 

If I decode only file with same video type IN LOOP, there no problem.

If I decode alternatively with 2 different video type , errors occur. 0xC0000005 ACCESS VIOLATION @  0x000000000 . After this error, when I change the video file MFX_ERR_UNKNOWN appears, and no more decoding is possible.

Perhaps I need to reset something before changing video file ?

Have you a solution ?

 

Delphine

 

0 Kudos

Link Copied

1 Reply
Surbhi_M_Intel
Employee
‎07-28-2014 04:51 PM
510 Views

Hi Delphine,

In general, to use videos of different resolution or properties this sample code requires you to reset the buffers.
Having said that, can you please give more details about how you are trying to pass 2 different type of video alternatively ?
I have tried reproducing this issue using 1 stream which has a resolution change (made by concatenating 2 different types of videos) and wasn't able to get the error you have mentioned above.

 

 

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.