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

intel media sdk20170701 sample decode with screen capture plu-in

QIYUAN__FENG
Beginner
896 Views

hey ,nice to meet to:

when i am testing the sample sample decode with screen capture plu-in :error belows:

sample_decode.exe h264-hw -p 22d62c07e672408fbb4cc20ed7a053e4 -scr:w 1500 -scr:h 700 -d3d11  -o output.yuv

sts=MFX_ERR_OINVALID_VIDEO_PARAM(-15),CDecodingPipeline::init,m_pmfxDEX->Init failed at pipeline_decode.cpp:447

sts=MFX_ERR_OINVALID_VIDEO_PARAM(-15),wmain,Pipeline.Init failed at sample_decode.cppL681

plugin_loader.h:199[INFO]MFXBaseUSER_Unload(session=0x000001c9c34A20),sts=0

how can i resolve this issue?

 

0 Kudos
4 Replies
Ramashankar
New Contributor III
896 Views

Hi Qiyuan,

Replace ‘h264’ with ‘capture’ in command line argument. 

sample_decode.exe capture -hw -p 22d62c07e672408fbb4cc20ed7a053e4 -scr:w 1500 -scr:h 700 -d3d11  -o output.yuv

0 Kudos
keiyuen__feng
Beginner
896 Views

First of all,i am glad to recive to reply,I have tried two Intel media SDK (Intel(R) _media_sdk_2016.0.2 and Intel(R) _media_sdk_2017.0.1)

First:

INTELMEDIASDK_WINSDK_PATH     C:\Program Files (x86)\Windows Kits\10

INTELMEDIASDKROOT                      C:\Program Files (x86)\IntelSWTools\Intel(R)_Media_SDK_2016.0.2

file: ..x64/Debug/

                          22d62c07e672408fbb4cc20ed7a053e4/mfxplugin64_screen_capture.dll

                          22d62c07e672408fbb4cc20ed7a053e4/plugin.cfg

                          54542616243341e693ae899942ce7355/mfxplugin_camera_pipe64.dll

                          54542616243341e693ae899942ce7355/plugin.cfg

                          lib/igfx_s3dcontrol.lib

                          lib/libmfx.lib

                          lib/libmfx_d.lib

                          lib/sample_common.lib

                          libmfxaudiosw64.dll

                          libmfxsw64.dll

                          sample_decode.exe

                          sample_decode.ilk

                          sample_decode.pdb

commondline :

sample_decode.exe capture -d3d11  -hw -f 25 -p 22d62c07e672408fbb4cc20ed7a053e4 -w 1920 -h 1080 -fourcc nv12  -o output.yuv

 

yes,work well:

decoding Sample Version 6.0

Decoding Started

Frame number:550 ,fps 4.920 ,fread_fps:0.000,fwrite_fps:5.388

  • MY QUESTION IS:one:Why the use of CPU is very high,how can i cut down the cpu?,two:  ,how can i get the 25 fps??

 

second:

INTELMEDIASDK_WINSDK_PATH            C:\Program Files (x86)\Windows Kits\10

INTELMEDIASDKROOT                               C:\Program Files (x86)\IntelSWTools\Intel(R)_Media_SDK_2017.0.1

x64/Debug/        22d62c07e672408fbb4cc20ed7a053e4/mfxplugin64_screen_capture.dll

                          22d62c07e672408fbb4cc20ed7a053e4/plugin.cfg

                          lib/igfx_s3dcontrol.lib

                          lib/libmfx.lib

                          lib/libmfx_d.lib

                         lib/sample_common.lib

                         libmfxaudiosw64.dll

                         libmfxsw64.dll

                         sample_decode.exe

commondline:sample_decode.exe capture -d3d11 -p 22d62c07e672408fbb4cc20ed7a053e4 -scr:w 1920 -scr:h 1080 -fourcc nv12

or:::sample_decode.exe capture -d3d11  -f 25 -p 22d62c07e672408fbb4cc20ed7a053e4 -w 1920 -h 1080 -fourcc nv12

Decoding Sample Version  8.0

Features:Press 1 to toggle fullscreen rending on/off

 

Why is this version going wrong?

 

 

0 Kudos
Ramashankar
New Contributor III
896 Views

Hi Qiyuan,

sample_decode.exe capture -d3d11  -hw -f 25 -p 22d62c07e672408fbb4cc20ed7a053e4 -w 1920 -h 1080 -fourcc nv12  -o output.yuv

  • MY QUESTION IS:one:Why the use of CPU is very high,how can i cut down the cpu?,two:  ,how can i get the 25 fps??

You are writing raw output frames in file (by using -o option) which causes high cpu usage as well as low frame rate too. Exclude -o option from your command line and you will observe better performance. 

Secondly, screen capture part doesn't consider fps parameter provided in command line, its you who need to make call to DecodeFrameAsync() at interval as per required fps. But if you opt to render the capture frames then renderer will try to achieve the fps rate as provided in command line (use -r option for this).

Also, please refer the 'readme-decode.pdf' file for further information of all these parameters.

0 Kudos
keiyuen__feng
Beginner
896 Views

I am very glad to receive your reply, I want to know how to use (https://software.intel.com/zh-cn/articles/intel-media-sdk-screen-capture//simple_screen_capture.zip), how to obtain the original data of desktop?

my commonline:(tutorial_screen_capture.exe -n 500 -w 1920 -h 1080 -enc -enc_codec 'avc' -enc_file test1.avc),always mfxsts==MFX_ERR_NONE,tutorial_screen_capture.cpp,line 692,why error??

Ramashankar wrote:

Hi Qiyuan,

sample_decode.exe capture -d3d11  -hw -f 25 -p 22d62c07e672408fbb4cc20ed7a053e4 -w 1920 -h 1080 -fourcc nv12  -o output.yuv

  • MY QUESTION IS:one:Why the use of CPU is very high,how can i cut down the cpu?,two:  ,how can i get the 25 fps??

You are writing raw output frames in file (by using -o option) which causes high cpu usage as well as low frame rate too. Exclude -o option from your command line and you will observe better performance. 

Secondly, screen capture part doesn't consider fps parameter provided in command line, its you who need to make call to DecodeFrameAsync() at interval as per required fps. But if you opt to render the capture frames then renderer will try to achieve the fps rate as provided in command line (use -r option for this).

Also, please refer the 'readme-decode.pdf' file for further information of all these parameters.

0 Kudos
Reply