When it comes to vendor specific SDK for hardware assisted video encoding, Intel Media SDK is perhaps the oldest one among current vendors: Intel, NVIDIA, AMD. And also surprisingly the worst one. All three vendors are offering their SDKs for really close capabilities, however the kits are designed and structured differently. If NVIDIA and AMD are close in terms of convenience to developer, Intel Media SDK is apparently an outsider here.<\/p>\n
Debug output to facilitate debugging and troubleshooting? No. Working with this and having memories of AMF SDK Trying to initialize a session against non-Intel GPU, which is apparently not going to work? No failure until you hit something weird later in an unrelated call. What the hell is\u00c2\u00a0 Forgot to attach an allocator? You get a meaningless failure code trying to initialize encoding context.<\/p>\n Trying to identify maximal supported resolution for encoder? Oopsy.<\/p>\n How do I identify if runtime\/driver is capable to implicitly handle ARGB32 (RGB4) to NV12 conversion? No way without actual attempt to initialize context. In which runtime version the capability was introduced? Not documented.<\/p>\n Asynchronous The hardware encoders are out there for years, and decent ones. It is surprising that the SDK is not equally well and friendly.<\/p>\n","protected":false},"excerpt":{"rendered":" When it comes to vendor specific SDK for hardware assisted video encoding, Intel Media SDK is perhaps the oldest one among current vendors: Intel, NVIDIA, AMD. And also surprisingly the worst one. All three vendors are offering their SDKs for really close capabilities, however the kits are designed and structured differently. If NVIDIA and AMD… <\/p>\nAMFDebug<\/code> and AMFTrace<\/code> evetnually makes you cry.<\/p>\nMFX_IMPL_HARDWARE2<\/code> in first place? In which exactly enumeration this device is second or otherwise how do I understand what device this is exactly when I select it by Intel’s ordinal number? MFX_IMPL_HARDWAREn<\/code> flags are not defined to be sequential. Documentation typo references non-exiting MFX_IMPL_HARDWARE1<\/code> flag. NVIDIA and AMD are clearly offering this in a more convenient way.<\/p>\nmfxExtVPPDoNotUse<\/code><\/a> and mfxExtVPPDoUse<\/code><\/a>\u00e2\u20ac\u00a6 Seriously? Not documented well. An attempt to initialize structures \u00e2\u20ac\u0153differently\u00e2\u20ac\u009d still making sense results in meaningless error code.<\/p>\nMFXVideoENCODE_EncodeFrameAsync<\/code> requires that lifetime of mfxFrameSurface1<\/code> argument is extended to the completion of asynchronous call… Things like these just have to be documented! One would hate to find this out while troubleshooting unstable operation of the API.<\/p>\n