Jon Recker

Yes, oneVPL dispatcher searches for runtime libs in the directories listed in the spec - latest version is [here](https://spec.oneapi.io/onevpl/latest/index.html). To add locations to the search process, they can be added...

PR was out of sync with the HEAD so changes were pulled into the following commit: https://github.com/oneapi-src/oneVPL/commit/6182082a12a4fc90b3db89568b3924f2c88f2704

Should be resolved by the commit: https://github.com/oneapi-src/oneVPL/commit/6182082a12a4fc90b3db89568b3924f2c88f2704

Thank you, and apologies for merging changes into one commit. We had issues getting suitable build fixes staged properly in the staging repo which this repository mirrors. The workaround [here](https://github.com/oneapi-src/oneVPL/commit/6182082a12a4fc90b3db89568b3924f2c88f2704#diff-1e7de1ae2d059d21e1dd75d5812d5a34b0222cef273b7c3a2af62eb747f9d20aR47)...

Agreed, updating the headers is the best long-term solution. Thank you for creating a PR into the spec repository. Please note that these headers are usually updated ~ a few...

Thank you for the input. These enums are also defined separately for the test tools in [sample_utils.h](https://github.com/intel/libvpl/blob/master/tools/legacy/sample_common/include/sample_utils.h#L82) but I agree that these should be defined in a single place in...

After initializing the encoder, the application can retrieve the SPS by calling [MFXVideoEncode_GetVideoParam()](https://intel.github.io/libvpl/latest/API_ref/VPL_func_vid_encode.html#mfxvideoencode-getvideoparam) and attaching the buffer [mfxExtCodingOptionSPSPPS](https://intel.github.io/libvpl/latest/API_ref/VPL_structs_encode.html#mfxextcodingoptionspspps) to the mfxVideoParam structure which is passed to GetVideoParam(). Here is an...

Thank you for your input. OpenCL surface sharing for Linux is currently under consideration, but there is not yet a timeline for this feature. Knowing that this would be useful...

Adding @mgonchar - would you expect vaQuerySurfaceStatus() to succeed here? hello-sharing-vaapi-export runs correctly, so Export() looks to be returning valid frames. The failure in clCreateFromVA_APIMediaSurfaceINTEL() is probably due to some...

MFX_FOURCC_BGR4 [maps to](https://github.com/intel/vpl-gpu-rt/blob/main/_studio/shared/src/libmfx_allocator_vaapi.cpp#L76) VA_FOURCC_ABGR, so you could file a feature request to ``compute-runtime`` to add support for VA_FOURCC_ABGR. Or you could convert the frame using VPP (video post processing) in...