Hi Dave and Andrew, Thank you for your response. It's very helpful to let me understand the internal of opencore.
John On Wed, Dec 10, 2008 at 11:48 AM, Dave Sparks <[EMAIL PROTECTED]>wrote: > > Yes, the decoders are all OMX. The encoders are still PV native > objects. We have a patch we will be putting out shortly to enable OMX > video encoders. > > On Dec 10, 8:32 am, John <[EMAIL PROTECTED]> wrote: > > Hi Dave, > > You mean opencore still use openmax interface for their own software > > codec? > > > > Thx > > John > > > > On Wed, Dec 10, 2008 at 10:04 AM, Dave Sparks <[EMAIL PROTECTED] > >wrote: > > > > > > > > > It's exactly as Andrew described it. There are two codec registries, > > > one for vendor supplied codecs and one for OpenCore software codecs. > > > If it is unable to find a vendor codec that satisfies the input/output > > > requirements, it falls back to OpenCore software codec. The reason for > > > that is that you may need multiple instances of a codec at the same > > > time. If there are no vendor codecs, then there is only one registry. > > > > > Example: Imagine you are playing MP3 in the background and the user's > > > selected ringtone is an MP3 file. While the music is playing, the > > > phone rings. The MP3 player is probably using the hardware codec (it > > > usually consumes less power than software codec), so when the ringtone > > > starts up, the PV framework instantiates a software codec instead. > > > > > On Dec 10, 6:32 am, John <[EMAIL PROTECTED]> wrote: > > > > Thx Andrew. > > > > According to my knowledge, besides OMX method(either vendor-specific > or > > > > opencore's OMX wrapper), opencore still has its' own software based > > > > codec(/mydroid/external/opencore/codecs_v2/video and audio). I'm > > > confusing > > > > how they handle the selection between software based codec and OMX > codec > > > > (either vendor-specific or opencore's OMX wrapper). > > > > > > John > > > > > > On Tue, Dec 9, 2008 at 5:49 PM, Andrew Green <[EMAIL PROTECTED] > > > > > wrote: > > > > > > > Inside the file > > > > > > /mydroid/external/opencore/codecs_v2/omx/omx_common/src/pv_omxmastercore.cpp > > > > > the function PV_MasterOMX_Init() loops through two sets of OMX > cores. > > > The > > > > > first is a vendor-specific OMX core that will offer up > vendor-specific > > > OMX > > > > > components. If a valid vendor-specific OMX codec is not found then > the > > > > > OpenCORE OMX codecs are iterated through as the backup. > > > > > > > Andrew > > > > > > > > Date: Tue, 9 Dec 2008 14:17:42 -0800 > > > > > > Subject: [android-porting] Can somebody explain how does the open > > > core > > > > > handle the selection between OPENMAX method and PV's own method? > > > > > > From: [EMAIL PROTECTED] > > > > > > To: [email protected] > > > > > > > > Can somebody explain how does the open core handle the selection > > > > > > between OPENMAX method and PV's own method? > > > > > > > > John > > > > > > > _________________________________________________________________ > > > > > Send e-mail faster without improving your typing skills. > > > > > > > > http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_. > > > .. > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
