[Gstreamer-openmax] [PATCH] a small bit of refactoring to gstomx_util, to allow for more flexibility of when the OMX component and port is instantiated

Stephen M. Webb stephenw at xandros.com
Wed Nov 25 11:42:08 PST 2009


On 25/11/09 14:28, Stefan Kost wrote:
> Felipe Contreras schrieb:
> >
> > I see no way this can be introspected, specially the libraries to
> > load. Once you have the library, component-name, and component-role,
> > then you can introspect the specific formats/profiles/levels
> > supported, etc.
>
> Now it becomres more clear. Is each omx component one so? I was thinking of
> having a .info file with each component (or a group of components). The
> info file would have what you can't introspect from the .so.

Trouble is, OpenMAX IL components may be supplied by third parties who know 
(or care) nothing of gst-openmax, and there may also be conflicts between 
components supplied by various third parties.  The .info idea is good but 
insufficient for solving the problem.  A configuration file is ideal for 
solving this problem.

-- 
Stephen M. Webb
Xandros
www.xandros.com




More information about the Gstreamer-openmax mailing list