[Libva] vaapi intel-driver (vaapi-ext): assertion failed

gimli gimli at dark-green.com
Fri Feb 3 00:19:06 PST 2012


And you look at the source code at
https://github.com/huceke/xine-lib-vaapi/tree/vaapi-testing ?

The output plugin does nto use vaBeginPicture direct. Can you explain
further you you mean that ?

cu

Edgar (gimli) Hucek

On Fri, 03 Feb 2012 08:26:15 +0800, "Xiang, Haihao"
<haihao.xiang at intel.com>
wrote:
> On Thu, 2012-02-02 at 19:36 +0100, gimli wrote: 
>> The xine-lib vaapi output plugin also sopports software decoded output,
>> there we need vaDeriveImage/vaPutImage.
> 
> You are right. I mean they are unnecessary in the hardware decoding
> path.  I see the following function call sequence in the hardware
> decoding:
> 
>   1) vaCreateSuface(dpy, ..., &surface_id);
>   2) vaDeriveImage(dpy, surface_id, &image_id);
>   3) vaPutImage(dpy, surface_id, image_id, ...);
>   4) vaBeginPicture(dpy, context_id, surface_id);
>      ...
>      vaEndPicture(dpy, context_id);
> 
> 3) and 4) write the same surface.
> 
>> cu
>> 
>> Edgar (gimli) Hucek
>> 
>> >Hi,
>> >
>> >Could you try with the latest vaapi-ext branch?
>> 
>> >BTW many operations such as vaDeriveImage(), vaPutImage() are
>> >unnecessary for decoding in xine-lib-vaapi
>> 
>> >Thanks
>> >Haihao
>> 
>> _______________________________________________
>> Libva mailing list
>> Libva at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/libva


More information about the Libva mailing list