On 15/06/18 06:44, Xiang, Haihao wrote:
>
> I may confirm that the error is returned from the old version of libva and
> vaapi
> driver w/wo this patch, the command below works well for me if using the new
> version of libva and vaapi driver.
Trying others:
* The Mesa driver running on an
2018-06-08 11:09 GMT+02:00, Jerome Borsboom :
> If there are no more issues or remarks with these two patches, could
> someone please commit them?
I cannot test, sorry!
Perhaps you could send your public git key to Michael and push yourself?
Thank you, Carl Eugen
On Fri, Jun 15, 2018 at 07:29:31AM +0200, Jerome Borsboom wrote:
> Is your VAAPI library and VAAPI driver new enough? You need at least
> libva-2.1.0 (VA-API version 1.1.0) and intel-vaapi-driver-2.1.0 for
> interlaced VC-1 decoding. From the output, I think you are using an
> older version and
I may confirm that the error is returned from the old version of libva and vaapi
driver w/wo this patch, the command below works well for me if using the new
version of libva and vaapi driver.
Thanks
Haihao
> Is your VAAPI library and VAAPI driver new enough? You need at least
> libva-2.1.0
Is your VAAPI library and VAAPI driver new enough? You need at least
libva-2.1.0 (VA-API version 1.1.0) and intel-vaapi-driver-2.1.0 for
interlaced VC-1 decoding. From the output, I think you are using an
older version and the error is just the libva library bailing out for
not supporting
On Wed, May 09, 2018 at 07:50:23AM +0200, Jerome Borsboom wrote:
> Contrary to VC-1 spec, VAAPI expects the row address of the first
> macroblock row in the first slice to start from zero for the second
> field in a field interlaced picture.
>
> Signed-off-by: Jerome Borsboom
> ---
> This patch
If there are no more issues or remarks with these two patches, could
someone please commit them?
Thanks!
Regards,
Jerome
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, 2018-05-09 at 14:00 +0200, Jerome Borsboom wrote:
> > > Contrary to VC-1 spec, VAAPI expects the row address of the first
> > > macroblock row in the first slice to start from zero for the second
> > > field in a field interlaced picture.
> > >
> > > Signed-off-by: Jerome Borsboom
> > >
>> Contrary to VC-1 spec, VAAPI expects the row address of the first
>> macroblock row in the first slice to start from zero for the second
>> field in a field interlaced picture.
>>
>> Signed-off-by: Jerome Borsboom
>> ---
>> This patch set adds support for hardware decoding multi-slice field
On Wed, 2018-05-09 at 07:50 +0200, Jerome Borsboom wrote:
> Contrary to VC-1 spec, VAAPI expects the row address of the first
> macroblock row in the first slice to start from zero for the second
> field in a field interlaced picture.
>
> Signed-off-by: Jerome Borsboom
Contrary to VC-1 spec, VAAPI expects the row address of the first
macroblock row in the first slice to start from zero for the second
field in a field interlaced picture.
Signed-off-by: Jerome Borsboom
---
This patch set adds support for hardware decoding multi-slice
11 matches
Mail list logo