Intel® Media SDK

How can AVStream drivers capture video directly to the graphics adapter's VRAM?

  Hello everyone,Now I need the AVStream driver to capture video directly to the graphics adapter's VRAM.According to the Microsoft's WDK,one of the steps is to get the display adapter’s GUID.
  The WDK documents mention that "Obtain the adapter GUID from the vendor-supplied graphics miniport driver. The DXGK_INTERFACESPECIFICDATA structure contains the adapter GUID to return in the property request. This structure is generated by the DirectX graphics kernel (DXGK) subsystem and is passed to the miniport driver when the adapter is initialized."

System freeze (linux)


I'm writing an server application that records and merges from several IP cams, and renders the result using the Intel media sdk. For this I use a modified version of the sample encoder. However the application sporadically freezes the entire system completely, in such a way that nothing echoes to console, nothing is printed to any system log. More importantly the server becomes unresponsive and has to be rebooted physically turning it on and off.  We have two such servers each controlling 11 cameras, our resulting frames are 1920x480, fps 50.

Problem meeting Profile/Level constraints on vbv_size

For MPEG2 encode, the streams generated by MSDK do not appear to obey main profile/main level constraints on vbvsize.

Table 8-14 in ISO_IEC_13818-2 limits vbv buffer size to 112*16384 = 1835008 bits for main profile/main level.

In the attached code, I setup the encoder for main profile/main level and parse the coded output to determine what value the encoder specifies.  I see the results below.  The software version specifies a size of 134*16384 bits and the hardware version specifies136*16384.

Using a Xeon E3-1285 v3 with a Supermicro X10SLH-F

Hi, I am having a bit of trouble getting MediaSDK 2013 R3 for Linux to run on a Xeon E3-1285 v3 (on an Intel recommended Supermicro X10SLH-F motherboard) with Ubuntu 12.04.3 LTS.  I am running the recommended kernel, completed MeediaSDK installation, have verified the i915 module is loaded correctly, but am strugging to get the /dev/dri/card* entry to be listed for the integrated HD Graphics P4700 device.

The X10SLH-F board has an ASPEED interface on board, enabled by default.  This is listed in addition to the Xeon graphics in the output of lspci as follows:

Error codes

Hi, we sold some NUC DC3217IYE to our customer & they got error code -10 when running Intel Video Decoding Sample from Intel Media SDK Samples to play the file created by Intel Video Transcoding Sample under Windows Embedded Strandard 7. We've tested it but got different error code -3 & 1 (as attached picture). What do those error code (-10, -3, & 1) mean? Does anybody have the checklist of Intel Media SDK error code? Thanks!


How to make efficient use of async decoding?

I'm trying to understand if there's a more efficient of doing things than what I'm doing now. Basing myself on the decode samples, I have a single-threaded model like this:

  • Add data to the bitstream as needed
  • Call DecodeFrameAsync until it returns MFX_ERR_NONE
  • Call SyncOperation on the syncPoint returned by DecodeFrameAsync
  • Enqueue the frame for later use (same thread can used to take the frame and render)

It seems counter-productive to start an asynchronous operation only to wait for its completion immediately after.

dynamic change bitrate in CBR mode

    I'm using the SDK(API 1.8 for linux) to change the target bitrate dynamically. When I use VBR mode, it seems to be OK, but when I use CBR mode, the Reset() function seems success(return MFX_WRN_INCOMPATIBLE_VIDEO_PARAM), and after call GetVideoParam(), the value of bitrate is what I set , but the streem contain the old bitrate, maybe I am missing something?

Stream incompatibility w/ API v1.7

As a result of experimentation with AVISynth and the assistance of some very talented people on the Doom9 forums, I've uncovered an incompatibility with the Intel Media API v1.7.  It would seem that part of the movie "Pacific Rim" simply doesn't work with this version, but only if you're using the 3D disc as the source (the 2D disc appears to work just fine).  There are at least two sections where attempting to use the Intel Media API results in frames being corrupted and lost, each and every time you attempt to decode them.

Subscribe to Intel® Media SDK