[Helix-client-openmax] Query on OpenMax core,components and tunneling

[Helix-client-openmax] Query on OpenMax core,components and tunneling

Pranav Mehra pranav.mehra at samsung.com
Thu Sep 13 23:55:51 PDT 2007


Thanks Ukri for you prompt reply. For query 3) what I actually wanted to
suggest is, if  IL Client also had an API to setup tunneling in a way like

 

Component A->B

Component A-C

Instead of 

A->B

B->C

 

 

Eg: OMX_SetupTunnel(filereaderhandle, 1, audiodechandle,
0,1,audiosinkhandle);

Instead of

OMX_SetupTunnel(filereaderhandle, 1, audiodechandle, 0);

OMX_SetupTunnel(audiodechandle, 1, audiosinkhandle, 0);

 

So filereader is feeding both audiodecoder and audio sink component
simultaneously instead of relying on component intelligence(splitter)

 

Please share your thoughts on this.

 

Thanks,

Pranav

 

 

  _____  

From: helix-client-openmax-bounces at lists.helixcommunity.org
[mailto:helix-client-openmax-bounces at lists.helixcommunity.org] On Behalf Of
Ukri.Niemimuukko at nokia.com
Sent: Thursday, September 13, 2007 9:28 PM
To: helix-client-openmax at lists.helixcommunity.org
Subject: RE: [Helix-client-openmax] Query on OpenMax core,components and
tunneling

 

Hi,

 

1) Dynamic component loading is not defined in the spec yet, so the
mechanism is specific to the core. If components designed to be dynamically
loaded with the core from Vendor A need to be integrated into a core from
Vendor B, most likely the loading mechanisms aren't exactly compatible and
some integration effort is necessary.

 

2) No, I don't think there is a way to indicate when roles are queried, if a
component is not really available because of resource limitations. You'll
find out possibly as late as when moving the component from loaded to idle
state, when the resources are supposed to be acquired. At that point the
state transition may fail.

 

3) Tunnels are from one port to another port, one to one. Use a splitter
component, see figure 4-3 in IL spec 1.1. You probably also want to review
section 10 regarding buffer sharing. See figure 10-1.

 

Br,

 

Ukri

  _____  

From: helix-client-openmax-bounces at lists.helixcommunity.org
[mailto:helix-client-openmax-bounces at lists.helixcommunity.org] On Behalf Of
ext Pranav Mehra
Sent: Thursday, September 13, 2007 15:56
To: helix-client-openmax at lists.helixcommunity.org
Subject: [Helix-client-openmax] Query on OpenMax core,components and
tunneling

Hi All

 

I have few queries on open max 
 
1)Role of core in loading the dynamic components 
2)If the component is busy/unavailable, the IL client while querying for
roles of component can be indicated by component that it is unavailable
instead of trying to get handle and than getting indicated that it was to
wait for resources eachtime 
3)Whether a tunneling is possible three-way that is A->B and A->C. i.e the
same data from A can be simultaneously fed to B and C instead of setting up
tunneling explicitly by IL client 
 
Please express your thoughts on the same.

 

Thanks, 

Pranav 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.helixcommunity.org/pipermail/helix-client-openmax/attachments/20070914/fb765417/attachment.html


More information about the Helix-client-openmax mailing list
 

Site Map   |   Terms of Use   |   Privacy Policy   |   Contact Us

Copyright © 1995-2007 RealNetworks, Inc. All rights reserved. RealNetworks and Helix are trademarks of RealNetworks.
All other trademarks or registered trademarks are the property of their respective holders.