[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

[Stefan Kost]

Felipe Contreras schrieb:
> On Wed, Nov 25, 2009 at 9:44 AM, Stefan Kost <ensonic at hora-obscura.de> wrote:
>> Is this to workaround missing introspection features in omx-il? Then I
>> would simply call it (component-)metadata.
> 
> Consider a "registry/config" like this:
> 
> omx_nokiaaacdec = { .lib = "/usr/lib/libomxil-bellagio-nokia.so.1",
> .component = "OMX.Nokia.audio_decoder.aac" }
> omx_tiaacdec = { .lib = "/usr/lib/libOMX_Core.so", .component =
> "OMX.TI.AUDIO.DECODE", .role = "audio_decode.dsp.aac" }
> omx_mp3dec = { .lib = "/usr/lib/libOMX_Core.so", .component =
> "OMX.TI.AUDIO.DECODE", .role = "audio_decode.dsp.mp3" }
> omx_fooh264dec = { .lib = "/home/user/libfoovendor.so", .component =
> "OMX.foo.video_decoder.h264", .priority = 257 }
> 
> 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.

Stefan