Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Aleksandr_S_
Beginner
124 Views

Intel SDK and FFmpeg

Hello all,

What libraries should I use for FFmpeg that worked intel sdk. Only openCL?

0 Kudos
11 Replies
124 Views

Can you please elaborate the question Aleksandr with more details? For example, what is it the pipeline you are trying to develop, and how does ffmpeg fit into it. And how you plan to use Media SDK?

Aleksandr_S_
Beginner
124 Views

Hello,

 Need to transcode MPEG-2 to MPEGTS H.264 for live stream.
 

Lee_g_
Beginner
124 Views

You can download qsv codes from https://github.com/shenhailuanma/qsv-ffmpeg-codec

I'm currently using it with some customization in FFmpeg 2.6.3, as i recall, also qsv decoder is available in FFmpeg 2.6.1

Surbhi_M_Intel
Employee
124 Views

Hi Aleksandr,

You can check one of our existing samples which has a same pipeline set up. Check Full Transcoding Sample in this package - https://software.intel.com/en-us/intel-media-server-studio-support/code-samples. You can transcode a MPEG2 input to H264. You need prebuilt FFmpeg version 2.0.2(you can find the details in the Media Samples Guide which comes in the package).

Thanks,
Surbhi

Aleksandr_S_
Beginner
124 Views

Hello,

We are trying to run ffmpeg which implements Intel's hardware encoding. The ffmpeg stucks at ff_qsv_enc_frame() function and permanently prints out to the console 

[h264_qsv @ 0x1b47800] Timeout, device is so busy. cnt:5005
[h264_qsv @ 0x1b47800] Timeout, device is so busy
[h264_qsv @ 0x1b47800] Timeout, device is so busy. cnt:5005
...
So, it means that the hardware is permanently busy. How to work around this issue ?
Here is an actual implementation of the ff_qsv_enc_frame()
https://github.com/shenhailuanma/qsv-ffmpeg-codec/blob/master/ffmpeg2.2/libavcodec/qsvenc.c#L843

Aleksandr_S_
Beginner
124 Views

Hello,

We are trying to run ffmpeg which implements Intel's hardware encoding. The ffmpeg stucks at ff_qsv_enc_frame() function and permanently prints out to the console 

[h264_qsv @ 0x1b47800] Timeout, device is so busy. cnt:5005
[h264_qsv @ 0x1b47800] Timeout, device is so busy
[h264_qsv @ 0x1b47800] Timeout, device is so busy. cnt:5005
...
So, it means that the hardware is permanently busy. How to work around this issue ?
Here is an actual implementation of the ff_qsv_enc_frame()
https://github.com/shenhailuanma/qsv-ffmpeg-codec/blob/master/ffmpeg2.2/libavcodec/qsvenc.c#L843

Aleksandr_S_
Beginner
124 Views

Hello all,

intel xeon e-1245v3 and intel xeon e-1276v3   support intel sdk?

Lee_g_
Beginner
124 Views

Hi Aleksandr,

Did you install custom kernel on your system?

 

It happens constantly when running qsv without custom kernel, which must be build to use quick sync and can be found in Media SDK.

The_T_
Beginner
124 Views

Hi,

I am stuggling for weeks with the exact same issue..

Lee, what do you mean by custom kernel ? Can you please elaborate a bit ?

Thx

The_T_
Beginner
124 Views

Hi,

I found the 172 patches :), it works now!

ffmpeg has some problems when calling MFXClose though.. it crashes or hangs the app.

 

Sergey_G_1
Beginner
124 Views

The T. wrote:

ffmpeg has some problems when calling MFXClose though.. it crashes or hangs the app.

Hi! The same problem. Who can help ?  my skype: svgramatchikov