Quantcast
Channel: Intel® Software - Media
Viewing all 697 articles
Browse latest View live

VPP corrupts NV12 to YUY2 conversion when using SW mode

$
0
0

Hi,

Sample_vpp is not converting nv12 to yuy2 when using software acceleration. I tried sw dll (libmfxsw64.dll) from Intel(R) Media SDK 2018 R1 and Intel(R) Media SDK 2019 R1, and both produced same issue. You can reproduce it by simple command line:

sample_vpp -i test_1920x1080.nv12 -o out.yuv -sw 1920 -sh 1080 -scc nv12 -dw 1920 -dh 1080 -dcc yuy2 -lib sw

If I use hardware acceleration (-lib hw option) then this conversion is fine, so I think issue is in libmfxsw64.dll only.

TCE Level: 

TCE Open Date: 

Monday, January 20, 2020 - 21:38

example of sample_hevc_fei_abr

$
0
0

Hi, 

is it possible to have a working commandline example of sample_hevc_fei_abr.

 

Thanks.

 

BR

Francesco

Can't initialize encoder on Atom E3950

$
0
0

I'm trying to get access to hardware accelerated video compression on an Atom processor.  I did some preliminary work on an i7-4910MQ without issues, but I can't successfully call MFXVideoENCODE_Init on the E3950.  Is there some setting or other change I need?

When I compile the "simple_encode" tutorial project for x86, MFXVideoENCODE_Init will return MFX_ERR_MEMORY_ALLOC.  simple_encode.exe will print the following:

>simple_encode.exe -g 640x480 -b 74000 -f 30/1
 Could not allocate memory. c:\source\mediasdk-tutorials-0.0.3\simple_3_encode\src\simple_encode.cpp 167

When I compile the "simple_encode" tutorial project for x64, MFXVideoENCODE_Init causes an access violation and simple_encode.exe will exit without printing anything.

simple_session.exe works OK for both x86 and x64.

>simple_session.exe
Implementation: HARDWARE                 API Version: 1.27

I'm running Windows 10 Enterprise LTSC.  Compiling with Intel(R) Media SDK 2019 R1 on MS Visual Studio 2017.

 

Hardware acceleration in VM

$
0
0

Is hardware acceleration for Quick Sync supported in virtual machines now? Without passthrough. On Xeon. KVM or Hyper-V.

Thanks!

Intel open source computing library for deep neural network (clDNN) for Intel processor graphics (R)

$
0
0

(Photo provided by Yorg 3)

kubernetes are becoming the de facto standard with a greater amount of software technology and applications moving into containers. kubernetes has captured the cloud market by storm through the implementation of strong infrastructure development. It makes application deployment and management easier and improves the reliability and reduces the time you need for Devops.
In today's economic platform, most software businesses are looking to provide a high-performance application with a seamless customer experience.
Kubernetes is one of the emerging platforms that allow companies to run and manage packaged applications globally.
"According to Gartner 's report, by 2022 more than 75% of organizations worldwide will run packaged applications, especially loT applications.
Here are 5 key business capabilities promoted by Kubernetes and its benefits for large businesses

  • Application development / deployment faster
  • Reduce resource costs
  • Scalable workload
  • Multi-cloud flexibility
  • Effective cloud move

---------------------------------------

coppywrite by Gamesbx 2

#sketch full iso türkçe

#bombom host 

#battle royale io

TCE Open Date: 

Friday, February 21, 2020 - 17:55

Trouble reverting back to an old version of Media SDK

$
0
0

I have a Visual Studio 2017 C++ application using the Intel Media SDK 2016 to do H.264 encoding. I recently upgraded to the 2019 SDK in an attempt to get H.265 encoding working. Yesterday I reverted back to the 2016 SDK but my application is not working the same as before. It no longer detects Quick Sync Hardware encoding on the target machine. I have uninstalled the 2019 SDK, reinstalled the 2016 one, revert all code changes and rebuilt the project but that didn't work. I also had a friend build my source code against the 2016 SDK and the resulting .exe that he build worked as expected. When comparing the file he built to mine, the file sizes differ by a few KB suggesting they are somehow different.

How do you properly uninstall the 2019 SDK? Has anyone had experience with left-over files or registry values after an uninstall?

TCE Level: 

TCE Open Date: 

Thursday, March 12, 2020 - 05:13

AVC fei encode example with bitrate control or single field mode

$
0
0

Do you provide examples with sample_fei and bitrate control?  Or else, can i encode interlace avc with single field mode without fei api?

 

For example, we need  encode like this:

./sample_fei -tff -single_field_processing -g 50 -encpak -i MediaSDK/tests/content/test_stream_176x96.yuv -o output.h264 -w 176 -h 96

 

with single_field_processing but also with bitrate control,

TCE Level: 

TCE Open Date: 

Tuesday, March 17, 2020 - 03:24

Intel® Media RAW Accelerator Help

$
0
0

Hi ,

i have a project from collage regarding image processing, we decided to learn how to use intel's dedicated framework for that purpose.

i am struggling finding any basic guide to see examples regarding of how to use Intel® Media RAW Accelerator.

any help would be great ,thank you.

TCE Level: 

TCE Open Date: 

Tuesday, March 17, 2020 - 05:59

Init returns MFX_ERR_MFX_ERR_INVALID_VIDEO_PARAM after upgrading from Media SDK 2016 to 2019

$
0
0

Windows 10 Enterprise 2016 LTSB

Intel Core i7-6700

Intel HD Graphics 530 version 25.20.100.6323

I have an application used to encode video using hardware acceleration and H.264. After upgrading my Intel Media SDK from 2016 to the 2019 one, the pEncoder->Init function returns MFX_ERR_MFX_ERR_INVALID_VIDEO_PARAM(-15).  Code below:

Constructor:

m_BitStream.Data = NULL;
m_HeaderBuf.SPSBuffer = NULL;
m_HeaderBuf.PPSBuffer = NULL;
m_VideoParam.ExtParam = NULL;

mfxVersion min_version;
mfxVersion actual_version;
min_version.Major = 1;
min_version.Minor = 0;

mfxStatus sts = m_EncoderSession.Init( MFX_IMPL_HARDWARE, &min_version );
m_EncoderSession.QueryVersion( &actual_version ); // returns 1.27
m_EncoderSession.QueryIMPL( &m_usedImpl ); // returns 514

prepareEncoder function:

bool CompEngine::PrepareCompress()
{
	mfxStatus sts;

	int width = 1024;
	int height = 544;
	int bufferSizeBytes = 12582912;

	m_VideoParam.IOPattern = MFX_IOPATTERN_IN_SYSTEM_MEMORY;
	m_VideoParam.AsyncDepth = 1;
	m_VideoParam.mfx.CodecId = MFX_CODEC_AVC;

	m_VideoParam.mfx.TargetUsage = MFX_TARGETUSAGE_4;
	m_VideoParam.mfx.RateControlMethod = MFX_RATECONTROL_QVBR;

	m_VideoParam.mfx.TargetKbps = 5000;
	m_VideoParam.mfx.InitialDelayInKB = 0;
	m_VideoParam.mfx.MaxKbps = 10000;

	m_VideoParam.NumExtParam = 1;
	m_VideoParam.ExtParam = new mfxExtBuffer *[1]; 		
	m_VideoParam.ExtParam[0] = (mfxExtBuffer*)&m_CodingOptions3Buf;
	memset(&m_CodingOptions3Buf, 0, sizeof(mfxExtCodingOption3));
	m_CodingOptions3Buf.Header.BufferSz = sizeof(mfxExtCodingOption3);
	m_CodingOptions3Buf.Header.BufferId = MFX_EXTBUFF_CODING_OPTION3;
	m_CodingOptions3Buf.QVBRQuality = 18;

	m_VideoParam.mfx.EncodedOrder = 0;
	m_VideoParam.mfx.NumRefFrame = 9;
    	m_VideoParam.mfx.FrameInfo.FourCC = MFX_FOURCC_NV12;
	m_VideoParam.mfx.FrameInfo.Width = width;
    	m_VideoParam.mfx.FrameInfo.Height = height;

	m_VideoParam.mfx.FrameInfo.CropX = 0;
	m_VideoParam.mfx.FrameInfo.CropY = 0;
	m_VideoParam.mfx.FrameInfo.CropW = width;
	m_VideoParam.mfx.FrameInfo.CropH = height;

	m_VideoParam.mfx.FrameInfo.FrameRateExtN = 30;
	m_VideoParam.mfx.FrameInfo.FrameRateExtD = 1; 
	m_VideoParam.mfx.FrameInfo.PicStruct = MFX_PICSTRUCT_PROGRESSIVE;
	m_VideoParam.mfx.FrameInfo.ChromaFormat = MFX_CHROMAFORMAT_YUV420;

	m_VideoParam.mfx.BufferSizeInKB = bufferSizeBytes/1024;
	m_VideoParam.mfx.GopPicSize = 1;
	m_VideoParam.mfx.GopRefDist = 1;
	m_VideoParam.mfx.GopOptFlag = MFX_GOP_STRICT;
	m_VideoParam.mfx.IdrInterval = 1;
	
	// Allocate Bitstream to receive the data	
	memset( &m_BitStream, 0, sizeof(mfxBitstream) );
	m_BitStream.MaxLength = bufferSizeBytes;
	m_BitStream.Data = new unsigned char[bufferSizeBytes];

	// create the encoder
	m_Encoder = new MFXVideoENCODE( m_EncoderSession );
	
	mfxFrameAllocRequest request;
	sts = m_Encoder->QueryIOSurf( &m_VideoParam, &request ); // returns MFX_ERR_NONE
	AllocateSurfacePool( request );

	sts = m_Encoder->Init( &m_VideoParam ); // returns MFX_ERR_INVALID_VIDEO_PARAM

	return true;
}

Can someone please tell me why m_VideoParam is invalid?

TCE Level: 

TCE Open Date: 

Tuesday, March 17, 2020 - 10:12

What's the maximum compression ratio for h264 and h265 encoding now?

$
0
0

Well, in my situation, my encoding configuration is:

resolution=3840x2160

target bitrate=500kbps

fps=30

codec=h264

RC mode=CBR

And the real encoded bitrate is 4000kbps. And I found some sentences in this forum that said the limit of the compression ratio is 500x.

I can understand the real bitrate is mismatched now. But I want to make sure that the limit of the compression ratio is still 500x? Is h265 encoding the same?

BTW, there is a parameter named BitrateLimit in CodingOptionValue. I tried to set it to false, and nothing changed.

 

TCE Level: 

TCE Open Date: 

Tuesday, March 17, 2020 - 21:26

Main10 monochrome H.265 Encoding with Kaby Lake: MFX_ERR_UNDEFINED_BEHAVIOR (-16)

$
0
0

The monochrome 10bit images from openCV should be compressed in a H.265 file with Kaby Lake HW accelerator.

Because the supported formats are not b/w I changed to an RGB (CV_16UC3) image which is converted to YUV using cvtBGRtoTwoPlaneYUV.

	int fourcc = cv::VideoWriter::fourcc('H', '2', '6', '5');
	...
	params.mfx.CodecId = codecId;
	params.mfx.TargetUsage = MFX_TARGETUSAGE_BALANCED;
	params.mfx.TargetKbps = (mfxU16)cvRound(frameSize.area() * fps / 500); // TODO: set in options
	params.mfx.RateControlMethod = MFX_RATECONTROL_VBR;
	params.mfx.FrameInfo.FrameRateExtN = cvRound(fps * 1000);
	params.mfx.FrameInfo.FrameRateExtD = 1000;
	params.mfx.FrameInfo.BitDepthLuma = 10; // added by customer
	params.mfx.FrameInfo.BitDepthChroma = 10; // added by customer
	params.mfx.FrameInfo.FourCC = MFX_FOURCC_P010; // modified by customer
	params.mfx.FrameInfo.Shift = 1; // added by customer
	params.mfx.FrameInfo.ChromaFormat = MFX_CHROMAFORMAT_YUV420;
	params.mfx.FrameInfo.PicStruct = MFX_PICSTRUCT_PROGRESSIVE;
	params.mfx.FrameInfo.CropX = 0;
	params.mfx.FrameInfo.CropY = 0;
	params.mfx.FrameInfo.CropW = (mfxU16)frameSize.width;
	params.mfx.FrameInfo.CropH = (mfxU16)frameSize.height;
	params.mfx.FrameInfo.Width = (mfxU16)alignSize(frameSize.width, 32);
	params.mfx.FrameInfo.Height = (mfxU16)alignSize(frameSize.height, 32);
	params.IOPattern = MFX_IOPATTERN_IN_SYSTEM_MEMORY;

The changes from the openCV videoio code are highlighted. This results in the output:

FrameInfo: 
| FourCC: P010 (0x30313050)
| Size: 288x288
| ROI: (0;0) 288x288
| BitDepth(L/C): 10 / 10
| Shift: 1
| TemporalID: 0
| FrameRate: 10000/1000
| AspectRatio: 0x0
| PicStruct: 1
| ChromaFormat: 1

By calling write_one I get the output:

MFX GetVideoParam: MFX_ERR_NONE (0)
requested 414 kB
BS Open /home/appVideo/data/o.mp4 -> 1
BS Allocate 847872 bytes (0.808594 Mb)
Calling with surface: 0x7fffec042450
ERR_MORE_DATA
Calling with surface: 0x7fffec042508
ERR_MORE_DATA
Calling with surface: 0x7fffec0425c0
ERR_MORE_DATA
Calling with surface: 0x7fffec042678
ERR_MORE_DATA
Calling with surface: 0x7fffec042730
MFX: Sync error: MFX_ERR_UNDEFINED_BEHAVIOR (-16)
Calling with surface: 0x7fffec0427e8
MFX: Sync error: MFX_ERR_UNDEFINED_BEHAVIOR (-16)
Calling with surface: 0x7fffec0428a0
MFX: Sync error: MFX_ERR_UNDEFINED_BEHAVIOR (-16)
Calling with surface: 0x7fffec042958
MFX: Sync error: MFX_ERR_UNDEFINED_BEHAVIOR (-16)
Calling with surface: 0x7fffec042a10

The ERR_MORE_DATA is normal according to the documentation. Because I did not find any documentation about the message MFX_ERR_UNDEFINED_BEHAVIOR I would like to ask the experts for support. Please let me know if I should take other formats to handle 10bit mono frames, etc. - Thank you, Christoph

AttachmentSize
Downloadapplication/zipimageProcessor.zip11.49 KB

TCE Level: 

TCE Open Date: 

Wednesday, March 18, 2020 - 00:54

Intel MediaSDK Decode 8k

$
0
0

hello, does Intel MediaSDK 2018R2 support decode 8k h264 (in hardware mode)? I did not find any information about this even in the release note

any response will be highly appreciated, thanks alot

TCE Level: 

TCE Open Date: 

Tuesday, March 24, 2020 - 02:43

Encoder init return error when using d3d11 memory and extbrc

$
0
0

Hello,

  I'm running encoder sample with "extbrc:on" and "d3d11" options, and MFXVideoENCODE_Init return MFX_ERR_UNKNOWN. But when i'm using system memory with extbrc, and it works fine.

  Could somebody tell me why and how to fix it?

Thanks!

H264 Decoding performance on Linux.

$
0
0

I'm porting a windows transcoder to Linux, and running into an issue on the speed of decoding a 1080p H.264 video frame - the encoding works as expected.  Comparing the same feed from a low end Pentium Linux (N4200 - 1.1 GHz) to my Windows developer machine (i5-6500 - 3.2 GHz), the encode takes about 2x longer (as expected), but the decode takes 20x longer. (1+ milliseconds compared to over 26 milliseconds).  I'm wondering if there is something obvious I am doing wrong, or if this CPU isn't fully supported, or what ?

I'm running Ubuntu 19.10 server.

CPU: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz

Installed the mfx packages: sudo apt-get -y install libmfx1 libmfx-tools libva-drm2 vainfo intel-media-va-driver-non-free
export LIBVA_DRIVER_NAME=iHD
Running: I see

libva info: VA-API version 1.5.0
libva info: va_getDriverName() returns 0
libva info: User requested driver 'iHD'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_5
libva info: va_openDriver() returns 0
awk: fatal: cannot open file `/etc/network/interfaces' for reading (No such file or directory)
 

As to my code: I'm opening up the VA display (_vaDisplay is shared between my encode/decode sessions)

    int _card = open("/dev/dri/card0", O_RDWR); /* primary card */
    VADisplay _vaDisplay = vaGetDisplayDRM(_card);
    VAStatus vaStatus = vaInitialize(_vaDisplay, &majorVersion, &minorVersion);
 

Opening up my session:

    mfxVersion min_version = { 3, 1 };  // min version 1.3 to support Low Latency.
    mfxStatus initStatus = MFXInit(MFX_IMPL_HARDWARE_ANY, &min_version, &session);
    initStatus = MFXVideoCORE_SetHandle(session, MFX_HANDLE_VA_DISPLAY, (mfxHDL)_vaDisplay);  // added for Linux

And the basic decode which I timed (obviously I do the DecodeHeader before, and necessary surface creation)

        sts = MFXVideoDECODE_DecodeFrameAsync(_session, &bitstream, inputFrame, &surface, &syncPoint);
        sts = MFXVideoCORE_SyncOperation(_session, syncPoint, MSDK_DEC_WAIT_INTERVAL);

vainfo error with VPL

$
0
0

Hi, 

I have setup the VPL and the required environmental setting on my Ubuntu Host. I ma trying to execute the "vainfo" utility but ending 

up with the below error :

bosepriy@bosepriy:/opt/intel/inteloneapi/vpl/2021.1-beta03/lib$ ./vainfo
libva info: VA-API version 1.4.1
libva info: va_getDriverName() returns -1
libva info: User requested driver 'iHD'
libva info: Trying to open /opt/intel/inteloneapi/vpl/2021.1-beta03/lib/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva error: /opt/intel/inteloneapi/vpl/2021.1-beta03/lib/iHD_drv_video.so init failed
libva info: va_openDriver() returns 18
vaInitialize failed with error code 18 (invalid parameter),exit

bosepriy@bosepriy:/opt/intel/inteloneapi/vpl/2021.1-beta03/lib$ ls -lrt /opt/intel/inteloneapi/vpl/2021.1-beta03/lib/iHD_drv_video.so
-rwxrwxrwx 1 root root 105642088 Feb 26 23:35 /opt/intel/inteloneapi/vpl/2021.1-beta03/lib/iHD_drv_video.so

Any idea why this error code 18 is observed ?

Best Regards

Priyanka
 

 

 


Fresh installation of Intel Media SDK reports MFX_ERR_NULL_PTR(-2)

$
0
0

I am using Ubuntu 20.04 beta:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu Focal Fossa (development branch)
Release:	20.04
Codename:	focal

Running the example code from https://github.com/Intel-Media-SDK/MediaSDK/wiki/Intel-media-stack-on-Ub... gives me this error:

$ /usr/share/mfx/samples/sample_encode h264   -w 176 -h 144 -f 30 -cqp -qpi 30 -qpp 30 -qpb 30 -qsv-ff    -i AUD_MW_E.yuv -o encoded_AUD_MW_E.264

[ERROR], sts=MFX_ERR_NULL_PTR(-2), Init, f pointer is NULL at /build/intel-mediasdk-UBsAHl/intel-mediasdk-20.1.0/samples/sample_common/src/sample_utils.cpp:142

[ERROR], sts=MFX_ERR_NULL_PTR(-2), Init, m_FileReader.Init failed at /build/intel-mediasdk-UBsAHl/intel-mediasdk-20.1.0/samples/sample_encode/src/pipeline_encode.cpp:1654

[ERROR], sts=MFX_ERR_NULL_PTR(-2), main, pPipeline->Init failed at /build/intel-mediasdk-UBsAHl/intel-mediasdk-20.1.0/samples/sample_encode/src/sample_encode.cpp:1627

 

VPL decode works, but encode fails : not sure about system requirements

$
0
0

Hello,

I just gave a try to oneAPI VPL (2021.1-beta05)

During installation, it complained about unsupported OS. It required at least Win7* 64 Intel, which is precisely the one I run, so that was a first issue. Was it a bug of the installer, or a wrong system requirements description ?

Then I built a sample code to decode H264 with the vplWorkstream : it worked flawlessly (in TARGET_DEFAULT mode, TARGET_GPU won't run on my machine)

Finally, I built a sample code to encode H264 from raw YUV, and this time it failed. No error is raised by all the configuration, but EncodeFrame() returns 0 bytes and immediately sets the encoder's state to VPL_STATE_ERROR. Since it could be a misuse of my code, I switched to the sample code from https://github.com/intel/BaseKit-code-samples/tree/master/VideoProcessin..., and the behaviour is exactly the same : no visible error, until EncodeFrame() is called and returns 0 bytes with a VPL_STATE_ERROR state.

So I suspect that encoding is not supported on my system, but why, since decoding works ?

I also tried to use VPL_PROP_STATUS_CALLBACK, but no prototype is given in the header files, so I tried to guess it as

void myStatusCallback(vpl::Workstream* encoder, vplWorkstreamState status, void* data)

but it is never called anyway.

Is there a way to trace deep errors ?

 

 

10 bits output is not actually P010

$
0
0

According to https://docs.microsoft.com/en-us/windows/desktop/medfound/10-bit-and-16-... P010 stores values left shifted 6 bits, as if the values were originally 16 bits, but Intel Media SDK doesn't shift the values.  Bot HW and SW decoding in kaby lake behave the same.  https://software.intel.com/en-us/forums/intel-media-sdk/topic/731469 mentions that HW decoding used to be correct. Repro:

1
curl http://jell.yfish.us/media/jellyfish-3-mbps-hd-hevc-10bit.mkv --output jelly.mkv
2
ffmpeg -i jelly.mkv -vcodec copy -an -bsf hevc_mp4toannexb -vframes 1 jelly.265
3
simple_decode_hevc10.exe jelly.265 mfx.yuv
4
ffmpeg -i jelly.265 -pix_fmt p010le p010le.yuv
5
ffmpeg -i jelly.265 -pix_fmt yuv420p10le yuv420p10le.yuv
6
ffmpeg -i jelly.265 -pix_fmt yuv420p16le yuv420p16le.yuv
mfx.yuv should equal p010le.yuv but actually equals yuv420p10le.yuv (the Y plane is identical but mfx.yuv interleaves U/V like NV12 and yuv420p10le.yuv stores all Us before all Vs).  As expected the Y plane of yuv420p16le.yuv equals the Y plane of p010le.yuv, while the later interleaves U/V.

Bruno

tutorial screen capture ERROR

$
0
0

hello

   when i using the pluging(mfxplugin64_screen_capture.dll) to capture the desktop

mfxVideoParam par;

.......

 par.mfx.FrameInfo.FourCC = params.fourcc;
    par.mfx.FrameInfo.ChromaFormat = params.chroma_format;
    par.mfx.CodecId = MFX_CODEC_CAPTURE;

//par.NumExtParam = 1;
   // par.ExtParam = &mfxextbuf;

..........

everything works well!

when:

mfxVideoParam par;

.......

 par.mfx.FrameInfo.FourCC = params.fourcc;
    par.mfx.FrameInfo.ChromaFormat = params.chroma_format;
    par.mfx.CodecId = MFX_CODEC_CAPTURE;

par.NumExtParam = 1;
par.ExtParam = &mfxextbuf;

..........

mfxSts = MFXVideoDECODE_Query(mfxSes, &par, &par);

always return MFX_ERR_UNSUPPORTED.

what's the problem with this??how can i to do

Interlaced HEVC encoding problem

$
0
0

Hi, i'm need to encode interlaced yuv source to interlaced hevc CQP, but it gives erros, doesnt matter what type software or hardware here the command line options

D:\Intel Media SDK Plugins>sample_encode h265 -i C:\ffmpeg\Teste.yuv -o D:\WTRS1E1.hevc -tff -w 704 -h 528 -bref -idr_interval 1 -f 50 -cqp -qpi 20 -qpp 22 -qpb 24 -u balanced -r 4 -x 6 -g 50 -hw -p e5400a06c74d41f5b12d430bbaa23d0b -gpb:off -num_slice 1 -pp
Preset-controlled parameters (Default):
AdaptiveMaxFrameSize: 0
AsyncDepth: 4
BRefType: 2 (original preset value: 0)
GopPicSize: 50 (original preset value: 100)
GopRefDist: 4 (original preset value: 0)
IntRefCycleDist: 0
IntRefCycleSize: 0
IntRefQPDelta: 0
IntRefType: 0
LookAheadDepth: 0
LowDelayBRC: 0
MaxFrameSize: 0
RateControlMethod: 3 (original preset value: 2)
TargetUsage: 4 (original preset value: 4)
WeightedBiPred: 0
WeightedPred: 0

plugin_loader.h :173 [INFO] Plugin was loaded from GUID: { 0xe5, 0x40, 0x0a, 0x06, 0xc7, 0x4d, 0x41, 0xf5, 0xb1, 0x2d, 0x43, 0x0b, 0xba, 0xa2, 0x3d, 0x0b } (Intel (R) Media SDK GPU-Accelerated plugin for HEVC ENCODE)
Encoding Sample Version 8.3.26.0

Input file format       YUV420
Output video            HEVC
Source picture:
        Resolution      704x544
        Crop X,Y,W,H    0,0,704,528
Destination picture:
        Resolution      704x272
        Crop X,Y,W,H    0,0,704,264
Frame rate      50.00
QPI     20
QPP     22
QPB     24
Gop size        50
Ref dist        4
Ref number      6
Idr Interval    1
Target usage    balanced
Memory type     system
Media SDK impl          hw
Media SDK version       1.26

Processing started

[ERROR], sts=MFX_ERR_MORE_SURFACE(-11), CEncodingPipeline::Run, m_pmfxENC->EncodeFrameAsync failed at c:\users\thx4ever\documents\intel« media sdk 2018 r1 - media samples 8.3.26.352\sample_encode\src\pipeline_encode.cpp:1892

[ERROR], sts=MFX_ERR_MORE_SURFACE(-11), wmain, pPipeline->Run failed at c:\users\thx4ever\documents\intel« media sdk 2018 r1 - media samples 8.3.26.352\sample_encode\src\sample_encode.cpp:1308
Frame number: 0
Encoding fps: -0
plugin_loader.h :199 [INFO] MFXBaseUSER_UnLoad(session=0x0000023BB23B1380), sts=0

Viewing all 697 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>