Dmitry Ermilov
Dmitry Ermilov
@dvrogozh , can you please review?
@XinfengZhang , it seems no concerns anymore. Can you please merge?
Please try to add -hw: sample_decode.exe h264 -i 1.h264 -o 1.yuv -hw
It's Ivybridge. Pretty old driver and HW. It's very hard to say what's wrong. I'd suggest you to experiment. Try -d3d9 vs d3d11. Try to collect msdk api traces (tracer...
What is the difference between normal and non-normal machine?
Ahh. Okay. Most likely old mediasdk run-time library doesn't support something which is needed by https://github.com/Intel-Media-SDK/MediaSDK/blob/510d19dcace1d8c57567fdd40b557155ab11ab8e/api/mfx_dispatch/windows/src/mfx_dispatcher.cpp#L542
I guess ffmpeg simply doesn't use MFXQueryAdapters. MFXQueryAdapters is an optional function.
You can rely on this commit which shows example of decode->two VPPs: https://github.com/dmitryermilov/MediaSDK/commit/d5430f799e28ad1862fb4ff15acb605d5596d952 You need to add encoder after 2nd VPP: * add QueryIOSurf to get right num of surfaces...
Hi @MonkeySon , what Linux kernel do you use?
Since GPU hang is seen using both MediaSDK and ffmpeg, it's user mode driver issue. Can you please submit an issue against https://github.com/intel/media-driver/ ?