Feature request: Expose VP9 encode support on Kabylake+ with the iHD driver

[Brainiarc7]

Perhaps related to #630 and #205 : Will this ever be implemented?
A while back, FFmpeg received an implementation for the VP9 QSV encoder, with two constraints:

(a). Only low-power encoding is supported, and
(b). Icelake IGPs+ are supported. Older generations, even these capable of VP9 encoding with VAAPI are left out.

[XinfengZhang]

@Brainiarc7 sorry for late response, we will not enable VP9 encode on Gen9 platforms , if someone still want it, he could try PR #717 , it add VP9 encode support. but Gen9 VME design is not optimized for VP9. so we have concerns on it.

[Brainiarc7]

I see.
Perhaps a branch for the same could be created for legacy support.

[XinfengZhang]

you mean to create a gen9_vp9_poc branch? and sync the code regularly ?

[Brainiarc7]

Yes.

…

On Fri, 6 Dec 2019 at 06:25, XinfengZhang ***@***.***> wrote: you mean to create a gen9_vp9_poc branch? and sync the code regularly ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#771?email_source=notifications&email_token=AAR7NB4FCB3JFD5IUOLDFQDQXHA4JA5CNFSM4JKPDS42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGC4ZPA#issuecomment-562416828>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR7NBY636PFSGQ4RHQ2PVDQXHA4JANCNFSM4JKPDS4Q> .

[Brainiarc7]

@XinfengZhang can that be done?
The patchwork is quite good and it works, as tested on CFL.

[rosetta-jpn]

+1 to this feature.
Processors at a lot of existing devices are gen9.
i965 driver needs to be used on them due to a lack of iHD driver's VP9 encoding support.
i965 driver is no longer be maintained actively.
So it is nice to enable us to use iHD driver on gen9 devices.

[sreerenjb]

@Brainiarc7 Thank you for testing this on CFL :)

[Gaurav-Original-ClassicShellTester]

+1. VP9 should be exposed on Gen9 GPUs even with their limitations. On Windows also as there are many devices vs Ice Lake which is far too new.

[fubsan]

Is there an update on this wrt roadmapping and 10th gen KBL derivative comet lake support? Particularly considering this used to work with the intel vaapi driver on related cpu generations and also replies like this: intel/intel-vaapi-driver#499

[grzegorz-kurzejamski]

definitely +1
At the project I'm working in we had to switch to 10th gen for multiple of processing nodes and it was quite a suprise that there is a 9/10th gen VP9 encoder support black hole with intel-vaapi-driver support up to 8th gen and iHD driver from 10th+ onwards. We were using VP9 Enc extensively up till now with 7th and 8th gen so this new generation is like a big downgrade, given better CPU specs and the very same iGPU. If there was a chance to build even minimal support for VP9 Encoder for 10th gen it would be much appreciated.

[thetooth]

Also in the same situation with a 11th gen processor. Why advertise VP9 encoding support if nothing can access it?

[XinfengZhang]

I could not commit that we could support VP9 VME(dual path) path on Gen9. there are several reasons, 1. VP9 VME path need the media-kernel (shader), and it was deprecated in future platforms , and it is not the direction , you could treat it as a temporal solution, TBH, I have no much confidence on it, so we have no plan to maintain it. 2. intel-vaapi-driver support all platforms of gen10- , so , if someone want to try VP9, we suggest they still keep older intel-vaapi-driver.

#717 is a patch which support VP9 dual pipe path, it should be workable , maybe we could create a branch basing one release branch, but suppose we will not rebase it any more. from this perspective, seems it is similar with using intel-vaapi-driver.

[XinfengZhang]

@thetooth , not sure whether I could answer your question, you mean you could not access ICL? , ICL 11th gen GPU certainly support VP9 encoding , it is fix function. hw support ..