plugin overview

[Gary Thomas]

On 2012-12-14 12:26, Peter Rennert wrote:
> Try to use plain gst-inspect-0.10 without arguments.
>
> That gives at least the installed plugins. If you are really desperate you can check the autogen.sh files in the plugin repositories/ folders and see what plugins they check for.
> Generally the documentation is within the git repositories, so you should have a documentation local for your version.

Sure, that works for things that have been installed.  However, I'm working
on a small embedded system and I can't afford to install every possible
plugin and what I'm looking for is the deeper inspection of the plugins
for their elements so I can install just the plugin I need.  For example,
I was trying to run a pipeline which includes the timeoverlay element.
How am I to guess that that element is actually in gst-plugins-base-pango?
That's what the [cool] overview page gets me.  Too bad it seems to no longer
be available for the older gstreamer-0.10 series...

> On 12/14/2012 12:26 PM, Tim-Philipp Müller wrote:
>> On Fri, 2012-12-14 at 05:19 -0700, Gary Thomas wrote:
>>
>>> That helps with the manuals & documentation, but what about the plugin overview?  It seems to
>>> be a melange of information about all of the available plugins and is a great way to figure
>>> out what plugin provides what elements and which plugin pack (gst-plugins-bad, etc) contains
>>> what.  Any idea where to find that for an old gstreamer installation?
>> I don't think there's a 0.10 version of those online. It's mostly the
>> same in 1.0, besides some renames (ff* -> av*) and plugin moves (vp8*
>> moved to good).

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------