[gst-devel] decodebin2 + VA-API integration

[Julien Moutte]

It's playbin2 that can notice that the autoplugging pulls in a sink element
and decide to push that sink to playsink.

If you have defined caps so that autopluging terminates with a sink, it
should work with playbin2 automatically. That's what we do with Fluendo VA
decoders and sinks.

Cheers,

Julien Moutte,
FLUENDO S.A.


On Mon, May 10, 2010 at 4:27 PM, Gwenole Beauchesne <
gbeauchesne at splitted-desktop.com> wrote:

> Hi,
>
> I am trying to integrate VA-APIi support to the standard decodebin2
> element. Currently, the VA-API plugins (vaapiconvert, vaapidecode,
> vaapisink) have GST_RANK_NONE rank.
>
> So, the following won't work. That's normal:
> $ gst-launch filesrc ! decodebin2 ! vaapisink
>
> Then, I changed GST_RANK_NONE to GST_RANK_PRIMARY, decodebin2 will now see
> and use vaapidecode. However, it will fail to link vaapidecode to
> vaapisink. Rather, it tries to link vaapidecode0:src to some
> decodepad2:proxypad3 element.
>
> Would someone know why vaapisink0:sink is not tried instead? Or what
> should be done in vaapisink so that decodebin2 actually links it to the
> vaapidecode element it found previously?
>
> Thanks,
> Gwenole.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20100510/67800502/attachment.htm>