Media (Intel® oneAPI 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 sign-in experience has changed to support enhanced security controls. If you sign in, click here for more information.

Error unsupported while session init with 4 monitors.

Jakub_K_1
Beginner
219 Views

Hi,

I've problem with MFXVideoSession initialization. Currently I have 4 monitors connected to external GPU and Intel display connected as "Try to connect anyway on: VGA" (when there are 3 monitors, quick sync HW works).

Example code looks like this:

 mfxVersion version = { 1, 0 }; // doesn't matter which version

 MFXVideoSession session;

 mfxStatus sts = session.Init( MFX_IMPL_AUTO_ANY, &version );
 session.Close();

sts is MFX_ERR_UNSUPPORTED.

My HW spec is HD4600 and Media SDK 2013 R2. 

Is there sth wrong in code, or media sdk version is too old? I'm using rather latest vga drivers.

Regards, j_kulaga.

0 Kudos
2 Replies
Harshdeep_B_Intel
219 Views

Hi,

Please update to latest version of MediaSDK 2015 with INDE from https://software.intel.com/en-us/intel-inde.

Also verify and update to latest graphics drivers from https://downloadcenter.intel.com/. After updating MediaSDK, refer to the msdk manual on Page 187 where, it is briefly explained how to initialize 4th graphic hardware for multiple monitors by implementation type MFX_IMPL_HARDWARE4. Let me know if that helps.

Thanks, 

Harshdeep_B_Intel
219 Views

Hi,

First, please update to latest version of MediaSDK 2015 with INDE from https://software.intel.com/en-us/intel-inde and update to latest graphics drivers from https://downloadcenter.intel.com/. From logs I see you are using old version 2013 of MSDK and 3496 driver version. 

Also, We have a open memory leak issue with sample_decode when initialized for multi-decode. The main reason is originally sample_decode was not designed for multi-decoding in loop. I will update with a fix/workaround soon. 

Thanks,

 

Reply