HI Girish,

Please check the docs at [mydroid]/external/opencore/docs for some
answers.
It sounds like you are particularly interested in the
openmax_call_sequences.pdf.



On Dec 10, 3:38 am, "Girish H T" <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> I am trying to understand the call flow of PV player and PV Author in
> OpenCORE PV frame work. I am intrested in understanding the call flow from
> application to till Openmax component.
>
> My questions are
>
> 1. If i want to replace the existing software codecs with hardware codecs
> (with or without OMX complaiance) wht will be the major changes in the
> current code.
>
> 2.How can track down the code flow from application to Openmax to hardware
> happens in PV Player and author is there any doc which explains about this ?
> If no doc atleast share the ideas.
>
> How does the commands flow ? Like when i say media player start from java
> application wht will be the major steps that will happen in the process..
>
> Like reading from the registry, creating the elements ... blah blah ..
>
> Say i have done with creating the nodes if some command is pushed in the
> command queue does it apply on all the nodes (parser, decoder,sink..) ?
>
> What is thread_Logon and thread_Logoff ? For each module i see these
> functions ? when will they get created.
>
> I guess the commands are sent in asynchronous fashion so its difficult for
> me to understand the code.
>
> 3.Which is the best place to start the if i want to replace software codecs
> with hardware codecs ? Why OMX complaince is only for decoder ? No OMX
> complaince for encoder, parser ... ?
>
> Please share the info..
>
> Regards
> Girish
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"android-framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to