Re: [FFmpeg-devel] Recent regression in VA-API compatibility (assertion in H.264 encode)

2017-12-01 Thread Mark Thompson
On 01/12/17 18:37, Devin Heitmueller wrote: > Hi Mark, > >>> >>> Here’s the vainfo output which provides the version info for the driver, >>> va-api version, etc. This is on a Haswell system running Centos 7. >>> >>> libva info: VA-API version 0.34.0 >>> libva info: va_getDriverName() returns 0

Re: [FFmpeg-devel] Recent regression in VA-API compatibility (assertion in H.264 encode)

2017-12-01 Thread Mark Thompson
On 01/12/17 18:47, Devin Heitmueller wrote: > >>> Try this? (Not tested, hardware which can run a version that old isn't >>> immediately to hand.) >>> >>> --- a/libavcodec/vaapi_encode_h264.c >>> +++ b/libavcodec/vaapi_encode_h264.c >>> @@ -261,7 +261,8 @@ static int >>>

Re: [FFmpeg-devel] Recent regression in VA-API compatibility (assertion in H.264 encode)

2017-12-01 Thread Devin Heitmueller
>> Try this? (Not tested, hardware which can run a version that old isn't >> immediately to hand.) >> >> --- a/libavcodec/vaapi_encode_h264.c >> +++ b/libavcodec/vaapi_encode_h264.c >> @@ -261,7 +261,8 @@ static int >> vaapi_encode_h264_write_extra_header(AVCodecContext *avctx, >>

Re: [FFmpeg-devel] Recent regression in VA-API compatibility (assertion in H.264 encode)

2017-12-01 Thread Devin Heitmueller
Hi Mark, >> >> Here’s the vainfo output which provides the version info for the driver, >> va-api version, etc. This is on a Haswell system running Centos 7. >> >> libva info: VA-API version 0.34.0 >> libva info: va_getDriverName() returns 0 >> libva info: Trying to open

Re: [FFmpeg-devel] Recent regression in VA-API compatibility (assertion in H.264 encode)

2017-12-01 Thread Lim, Michele
The vainfo shows that you're running very old versions. You may be able to resolve the issues you're facing by first removing stale versions of libva, libva-utils and intel-vaapi-driver, then reinstalling with the latest: https://github.com/01org/libva https://github.com/01org/libva-utils

Re: [FFmpeg-devel] Recent regression in VA-API compatibility (assertion in H.264 encode)

2017-12-01 Thread Mark Thompson
On 01/12/17 16:48, Devin Heitmueller wrote: > Hello, > > It looks like a recent patch causes VA-API H.264 encode to stop working and > an assertion to be thrown. I ran a git bisect and narrowed it down to the > following commit: > > 32a618a948c20f18db102d0b0976790222a57105 is the first bad