On 19/06/17 08:07, Víctor M. Jáquez L. wrote:
Hi,
On 06/18/17 at 04:13pm, Xiang, Haihao wrote:
>
> Hi all,
>
> We are planning to bump the VA-API major version from 0.40.0 to 1.0.0. In
> the new version, we will
>
> * fix errors in API/data structure definition,
> e.g.
https://github.com/01org/libva/issues/32
> * add new features, e.g. #https://github.com/01org/libva/pull/69
> * deprecate some useless API/data structures, e.g. libva-tpi, libva-egl.
> * provide other improvements, e.g. use portable type to define data structure.
>
>
https://github.com/01org/libva/issues/72 was created to track this task, you
> are welcome to provide any comment / suggestion at
>
https://github.com/01org/libva/issues/72 . if you have a patch to improve
> the api, please submit your pull request against
>
https://github.com/01org/libva/tree/v2.0-branch
Recently we patched gstreamer-vaapi (and gst-build) to require libva < 0.99.0
because there where users linking msdk with gstreamer-vaapi [1].
With this change we have to revert that patch (and gst-build) but we'll not
have a way to avoid msdk users to link gstremaer-vaapi. Is this correct?
I think we should just assume that the media SDK fork will continue to use version 0.99.0
for the forseeable future - they haven't changed the version at all in years despite
many releases updating the headers. So, might as well just check for 0.99.0 exactly.
That said, it's not difficult to support both for everything except encoding - we do
in libav*, which allows some nice use-cases like being able to use the faster libmfx
encoder while doing all other stuff with common VAAPI code.
- Mark