[Libva] Deinterlacing: vaapi-ext vs staging

[Mario Schulz]

(Repost, sent as reply instead of new thread previously.)

All,

The staging branch contains a very nice documentation how to use the
interlacers in va_vpp.h.
Although I have coded my way through it and the system correctly answers
the available deinterlacers: Just Bob and Weave can be applied to the
video pipeline (*).

All of this will not work with the vaapi-ext branch: This in term has a
superb picture by default, but I have no idea how to code any changes.
I do find the magic words "motion adaptive" or "motion compensated" in va.h.

So conceptually you will be moving forward to the presented programming
paradigm of the staging branch, but nothing is really available. On the
other hand you guys seem to have the nice stuff but no API to them.

- Am I supposed to test that with the vaapi-ext branch, and how?
- Is it possible to switch deinterlacing by just flipping a bit in the
kernel, driver or libva?
- How and when will that be resolved to see the staging paradigm with
the ext features?


(*) A Sandy Bridge based system, intel-driver & libva in its staging
branch with kernel drm-intel at 3.3.0-rc2+. Calls to

vaQueryVideoProcFilterCaps(..., VAProcFilterNoiseReduction, ..,
&num_denoise_caps);
vaQueryVideoProcFilterCaps(..., VAProcFilterDeinterlacing, ...,
&num_deinterlacing_caps);

reveal 1 denoiser and 2 deinterlacers, these decoding as weave and bob.