I guess I still don't understand what type of control do you require for your decoder. In the most generic case of a multimedia framework, one would want only minimum control of a central entity, in this case the pvPlayer engine. The player engine in this case has the responsibility of controlling the underlying components, including the OMX Audio decoder node.
Is it possible to expose these interfaces out, yes. But then the application developer would have to handle 100s of APIs to enable a single playback session. Note that there are some cases when such an interaction is convenient. For such cases, we do provide extension interfaces (e.g., look at authordriver.cpp for encoder extension interfaces) but with limited capability. Again, this may change in the future where we may provide the flexibility to the user to control this using some APIs of the engine itself. So, in short, the control to the underlying nodes will not be exposed. If you want to control your decoder from the node, it must be an OMX API implementation. What API(s) do you want to call? What is the purpose? We can discuss options if you spell out your usecase. -Ravi On Jun 12, 12:33 am, saxoappeal <dimplej...@gmail.com> wrote: > Dear Ravi: > > Thank you Ravi, I think that you are a one of the most active and > smart engineers in the gourps. > I have seen your name on so many times, so many articles. > Anyway, > > Ravi: > What function(s) do you want to call from the decoder node? > > - the function written in the decoder source in /omx/omx_mp3 folder > from the PVMFOXMAudioDecNode. > > Ravi: > The interface is through OMX IL. If you integrate your component > (decoder) > correctly, there shouldn't be a need to modify the client (node). > - if i want to control the decoder from the node or application, what > can I do..? > > in fact, finally I want to control the decoder from the java > application. > So, I think that I need a way to control the decoder from the > PlayerEngine. > And, I guess that the node interface PVMFNodeInterface* is the key > pointer to control the node. > But, I am not sure it's right or not. > And, PVMFNodeInteface is the general interface, So, I can't not refer > to the actual PVMFOMXAudioDecNode from the Engine Source. > Am I wrong? or What is the most important thing that I should > understand the whole? > > Thanks > > On Jun 12, 2:10 pm, Ravi <yend...@pv.com> wrote: > > > What function(s) do you want to call from the decoder node? The > > interface is through OMX IL. If you integrate your component (decoder) > > correctly, there shouldn't be a need to modify the client (node). > > > -Ravi > > > On Jun 11, 8:32 pm, saxoappeal <dimplej...@gmail.com> wrote: > > > > Hi All > > > > I have written my customized mp3 decoder in codecs/omx/omx_mp3. > > > So, I found a way to send a message to decoder from audiodec_node in > > > node. > > > > now, I need to know how to call a functions in the decoder from node > > > or PlayerEngine. > > > I have read the sources hundreds times, I only get the > > > PVMFNodeInteface in the Engine. > > > But, Every tries I had failed. and I have no idea and I am crying... > > > > It's maybe a kind of stupid question..but I really want to know it. > > > Please help me... > > > > Thanks.- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
