-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Expose VP9 encode support on Kabylake+ with the iHD driver #771
Comments
@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. |
I see. |
you mean to create a gen9_vp9_poc branch? and sync the code regularly ? |
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>
.
|
@XinfengZhang can that be done? |
+1 to this feature. |
@Brainiarc7 Thank you for testing this on CFL :) |
+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. |
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 |
definitely +1 |
Also in the same situation with a 11th gen processor. Why advertise VP9 encoding support if nothing can access it? |
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. |
@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 .. |
Hi, |
@XinfengZhang It looks that on Intel gen 11, Ubuntu 21.04, iHD driver 21.1.1, VP9 encoder is still unsupported. |
The iHD driver should have the vp9 encode support on ICL. Make sure you have Gu&HuC firmware in place to play with vp9 hardware encode (in case if it is missing). |
To sum up: encoding "works" but output video is broken. Details:
Results:
So formerly encoder "works", but drivers are still not ready for VP9 video encoding |
Hello there @karoldob , You'll need to add the the Try the command below and report back: ffmpeg -loglevel info -hide_banner -y -hwaccel vaapi -hwaccel_output_format vaapi -hwaccel_device /dev/dri/renderD128 -i Big_Buck_Bunny_1080_10s_2MB.mp4 -bsf:v "vp9_raw_reorder,vp9_superframe" -c:v vp9_vaapi out.webm |
Hi @Brainiarc7 , |
This should be the issue when set rc_mode as ICQ, if specific rc_mode as CQP/CBR/VBR not this issue. |
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.
The text was updated successfully, but these errors were encountered: