vMeta GStreamer 1.0 plugins

Daniel Drake dsd at laptop.org
Wed Aug 21 09:38:04 EDT 2013

On Wed, Aug 21, 2013 at 12:02 AM, Carlos Rafael Giani
<dv at pseudoterminal.org> wrote:
> I have written GStreamer 1.0 plugins for vMeta . You can find it here:
> https://github.com/dv1/gst-vmeta

Excellent! Thanks for working on this and sharing it.
It looks like you have rewritten the plugin more or less from scratch,
is that right? A wise move...

I see you have already included our recent fix for the Xv plugin too,
nice. The IPP deinterlace flag handling is not present, I guess you
have excluded that for good reason, I'm not even sure what it does...

Also looks great that you have got the xv plugin using vmeta libs to
allocate physical memory areas. Rather than facing the
libbmm/libphycontmem mess directly like the previous version did.

> The decoder should be stable. The existing sink has a flickering problem
> which seems to be caused by a race condition in the X11 driver that wasn't
> noticed so far due to timing coincidences in Marvell's 0.10 plugins. John
> Nettleton tried out my plugins on OLPCs and informed me that they worked.
> Perhaps it would be usefult to mention it here:
> http://wiki.laptop.org/go/Vmeta

I will mention it. That flickering problem will have to be solved
before this becomes useful to anyone though.

> I have heard about a new KMS X driver which will be pushed upstream soon.
> Until I can get it, I will not be addressing the sink's flickering, since
> the new driver may have fixed it already.

The new driver source is available on the dri-devel mailing list.
However there are several complications that must be solved before it
goes upstream.

Then a new X driver will be needed, and whoever steps up to maintain
that will have to decide if they really want to support the horrible
hack used by the vmetaxv plugin. And then implement it, test it, etc.

Then there will be a few other hurdles to go over before the new
drivers are really a convincing replacement. Like GPU support.

In other words, I don't see this being upstream soon, and even when
that does happen, there will probably be other major steps required
before it is really useful. So I would continue to focus on the
existing "stack".


More information about the Devel mailing list