Gstreamer-VAAPI and Totem

[Julien Moutte]

Hi,

autocluttersink's role is just to provide a way for different platform
specific sink plugins to be automatically discovered and used to render
video buffers into clutter.

Now that being said, every clutter sink element just has to respect a
common api to draw in the proper actor/texture. The way you handle this
drawing and the fact that it's optimal or suboptimal is just a detail here.

To reply to your question about Fluendo's design choice here, you have to
take in account that we always try to support old versions of GStreamer
because of our customers.

We can't just make our products depend on a very recent API added for
gst-vaapi and tell all our customers using old GStreamer versions to go to
hell.

So I believe this is a good enough design to give freedom to everyone.
There's several clutter sink elements out there and if you can make the
gst-vaapi based on respect the common requirement to be usable with
autocluttersink then it should just work no ?

Best regards,

*Julien MOUTTE*
C.T.O.

FLUENDO Influencing the Multimedia World

San Francisco, USA & Barcelona, SPAIN
Contact phone:
Spain:  +34 933 175 153
United States: +1 415 773 5353
www.fluendo.com

Please consider the environment before printing this e-mail.



On Wed, Jun 6, 2012 at 7:41 PM, Nicolas Dufresne <
nicolas.dufresne at collabora.co.uk> wrote:

> Le mercredi 06 juin 2012 à 18:30 +0100, Bastien Nocera a écrit :
> > > Bastien, any input where I can follow the issue? Even better, any
> chance
> > > of seeing Totem working with VA-API backported to 3.4 so that I don't
> > > have to get all the 3.5.* libraries? :)
> >
> > Totem 3.5 makes use of autocluttersink, which rely on bug fixes in
> > clutter-gst. If you update those two, it might be enough.
>
> autocluttersink has never been tested along with gstreamer-vaapi (this
> arrived after my work). Instead of wrapping an X windows into a some DRI
> pixbuf, cluttersink (not autocluttersink) uses an new API in gstreamer
> that let it use the GstBuffer as textures that are directly rendered
> into the clutter scene.
>
> I do think this approach is more efficient then the autocluttersink one,
> and that fluendo could have implemented the GstVideoBuffer interface for
> the VA buffer rather then using this. It's a bit of a design war, my
> apology if this creates flames.
>
> cheers,
> Nicolas
>
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20120606/61458f48/attachment.htm>