[Bug 780881] gstreamer-vaapi against intel-vaapi-driver 1.8.0: Multiple regressions

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=780881

--- Comment #1 from Víctor Manuel Jáquez Leal <vjaquez at igalia.com> ---
(In reply to sreerenj from comment #0)
> The new intel-vaapi-release-1.8.0 is bringing multiple regressions. This bug
> is to discuss what we can do from middleware perspective in order to not
> break the backward compatibility for gstreamer-vaapi customers.
> 
> Here is the release mail of intel-vaapi-release: 
> https://github.com/01org/intel-vaapi-driver/releases
> 
> As mentioned in the release mail this driver release is not supporting (not
> failing gracefully to):
> 
> The new AVC encoder doesn't support MVC/SVC encoding
> The new AVC encoder doesn't support ROI encoding
> The new AVC encoder doesn't support multiple slice encoding
> 
> The new driver come up with lot of quality improvements for AVC encode in
> SKL/BXT and KBL platfrom by introducing new media kernels. But unfortunately
> is not backward compatible since it is not supporting the MVC encode and
> multi-slice-encode which we support in gstreamer-vaapi.

Are these features broken in all the Intel platforms or only in SKL&KBL???

> 
> We should provide some work-around or blacklisting specifically for this
> driver release.

In the case of ROI, I guess it is simple: the driver should report
num_roi_regions as zero.

For the other features, it seems difficult.

I don't like the idea of identifying the intel-driver version and disable
options in run-time. It will make the code more complex and hard to follow.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.