It's playbin2 that can notice that the autoplugging pulls in a sink element and decide to push that sink to playsink.<div><br></div><div>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.</div> <div><br></div><div>Cheers,</div><div><br clear="all">Julien Moutte,<br>FLUENDO S.A.<br> <br><br><div class="gmail_quote">On Mon, May 10, 2010 at 4:27 PM, Gwenole Beauchesne <span dir="ltr"><<a href="mailto:gbeauchesne@splitted-desktop.com">gbeauchesne@splitted-desktop.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Hi,<br> <br> I am trying to integrate VA-APIi support to the standard decodebin2<br> element. Currently, the VA-API plugins (vaapiconvert, vaapidecode,<br> vaapisink) have GST_RANK_NONE rank.<br> <br> So, the following won't work. That's normal:<br> $ gst-launch filesrc ! decodebin2 ! vaapisink<br> <br> Then, I changed GST_RANK_NONE to GST_RANK_PRIMARY, decodebin2 will now see<br> and use vaapidecode. However, it will fail to link vaapidecode to<br> vaapisink. Rather, it tries to link vaapidecode0:src to some<br> decodepad2:proxypad3 element.<br> <br> Would someone know why vaapisink0:sink is not tried instead? Or what<br> should be done in vaapisink so that decodebin2 actually links it to the<br> vaapidecode element it found previously?<br> <br> Thanks,<br> Gwenole.<br> <br> ------------------------------------------------------------------------------<br> <br> _______________________________________________<br> gstreamer-devel mailing list<br> <a href="mailto:gstreamer-devel@lists.sourceforge.net">gstreamer-devel@lists.sourceforge.net</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a><br> </blockquote></div><br></div>