Skip to content
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

avc vdenc doesn't work as expected when using FFmpeg. #110

Closed
xhaihao opened this issue Mar 8, 2018 · 5 comments
Closed

avc vdenc doesn't work as expected when using FFmpeg. #110

xhaihao opened this issue Mar 8, 2018 · 5 comments
Labels
verifying PR: fix ready and verifying with build/test

Comments

@xhaihao
Copy link
Contributor

xhaihao commented Mar 8, 2018

The slice header in the encoded h264 stream is wrong, ffprobe reports the following errors:

[h264 @ 0x559068a82fa0] illegal modification_of_pic_nums_idc 32
[h264 @ 0x559068a82fa0] decode_slice_header error
[h264 @ 0x559068a82fa0] no frame!
[h264 @ 0x559068a82fa0] illegal modification_of_pic_nums_idc 32
[h264 @ 0x559068a82fa0] decode_slice_header error
[h264 @ 0x559068a82fa0] no frame!
[h264 @ 0x559068a81c30] decoding for stream 0 failed

The command for encoding ' ffmpeg -loglevel debug -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -s:v WxH -i -vf 'format=nv12,hwupload' -low_power 1 -c:v h264_vaapi output.h264'

ffmpeg commit: 00ae5c1d3d87efc7f13b86cce80e139c805db179
media-driver: ef45492
gmmlib: b8d74ac3fcea0dffa901ce62399d43a937212074
libva: 417b0184d4a767721e9b0a5f1597907707f545cf

@XinfengZhang
Copy link
Contributor

from @xhaihao , it is a CNL only issue. trying to reproduce it.

@XinfengZhang
Copy link
Contributor

reproduced, will fix it

@XinfengZhang
Copy link
Contributor

correct one comments, it's is a CNL only issue ---- not verified. maybe also exist with SKL

@Tianhaol
Copy link
Contributor

On SKL, ran the command, the following error was reported.
"xxxx: Invalid data found when processing input"
After specify input format with option -f rawvideo -pix_fmt nv12 , the command can work fine and ffprobe does not report any errors.

@XinfengZhang
Copy link
Contributor

@xhaihao please help to verify whether we can close the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
verifying PR: fix ready and verifying with build/test
Projects
None yet
Development

No branches or pull requests

3 participants