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
[FFmpeg-vaapi][ICL][VP9][VDENC] vaMapBuffer returns two bufs in the buf_list including a zero-sized buf #624
Comments
|
Currently, i see only VDENC is allowed for VP9 encode (VAEntrypointEncSliceLP), With cmdline: Error message: And regular P frame is used for encoding currently, is there low delay B needed, too? |
|
@Xiaogangli-intel Error message: In vaapi_encode_output, It seems the returned buf_list has 2 member: But the next returned buf has size 0 and no data is available. And this zero buffer covers the previous correct encoded data. Here are the questions:
|
|
Cope with potential multiple buf situation in ffmpeg level: |
|
@fulinjie Media driver will return 2 buffers in fact. The first buffer is VACodedBufferSegment buffer which includes encoded output. And the second buffer is extra VACodedBufferVP9Status. If ffmpeg needn't it, it could be ignored. Please refer to the following URL: |
|
a2ca915 should fix it. |
Any constraints or BKMs for enabling vp9 VDENC?
Like hevc VDENC does in #618
The text was updated successfully, but these errors were encountered: