Deal with video/x-raw(memory:VASurface)

[Sebastian Dröge]

On Do, 2013-12-12 at 04:44 -0800, adrien_sch wrote:
> Hey guys, 
> 
> I'm exploring the vaapi plugins in 1.2 and I wanted to add few "standard"
> element after the vaapidecode or the vaapipostproc element.
> 
> For example : 
> filesrc location=/path/to/file ! demux ! h264parse ! vaapidecode !
> vaapipostproc format=2 ! videoconvert ! videomixer ! videoconvert !
> xvimagesink
> 
> The result of this pipeline is that the negociation failed between
> vaapipostproc and videomixer.
> 
> One thing that I don't understand, is why the src pad of vaapipostproc is :
> video/x-raw(memory:VASurface) format=I420 ? Why this feature doesn't allow
> to the videoconvert element to convert the stream ? What can I do to resolve
> this ? 
> 
> I was expecting that format=2 (I420) will result of a "standard" stream,
> usable by every "standard" element, as the omx decode element does. 

vaapipostproc seems to be able to only output VASurface memory, so can't
be used by normal, software GStreamer elements. Only by elements that
understand VAAPI.

This should be possible to fix in gstreamer-vaapi in the same way it is
done in the decoder currently. The element should correctly do the
GStreamer caps negotiation, and if downstream does not know anything
about VAAPI it should provide memory that can be used by these elements.

Best would be to file a bug about that at http://bugzilla.gnome.org
against gstreamer-vaapi. There's nothing you can do on the pipeline side
there to fix that, this has to be fixed in the gstreamer-vaapi code.

-- 
Sebastian Dröge, Centricular Ltd - http://www.centricular.com
Expertise, Straight from the Source
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20131213/685edd32/attachment-0001.pgp>