ofcourse.. :) one quick glance on s/w codec libraries is all required >>Sent from my iPhone aah..
On Sun, May 22, 2011 at 4:19 AM, HV <harishv.athr...@gmail.com> wrote: > Ya, i figured that out, thanks for responding though > > Sent from my iPhone > > On May 21, 2011, at 7:50 PM, Deva R <r.deva...@gmail.com> wrote: > > > stagefright s/w codecs are not omx components, but all are derived class of > OMXCodec (stagefright codec i/f class) > > On Tue, May 17, 2011 at 12:29 AM, HV < <harishv.athr...@gmail.com> > harishv.athr...@gmail.com> wrote: > >> Hi, >> >> I'm trying to understand StageFright's (SF) playback graph. Are the SF >> software codecs OMX components or just standalone modules? Meaning, can a >> player directly connect to libstagefright_aacdec and not worry about the OMX >> component part? Don't we need to handle the EmptyBuffer/FillBuffer calls for >> data management? >> >> Basically, with OpenCORE, we had something like this rt, Gallery -> >> OpenCORE - > OMX Core -> OMX AAC Component - > AAC s/w decoder. So, with SF, >> can a player directly call SF's aacdec? Would really appreciate a response >> >> Thanks >> HV >> >> -- >> unsubscribe: <android-porting%2bunsubscr...@googlegroups.com> >> android-porting+unsubscr...@googlegroups.com >> website: <http://groups.google.com/group/android-porting> >> http://groups.google.com/group/android-porting >> > > > > -- > Regards, > Deva > <http://www.bittoggler.com>www.bittoggler.com > > -- Regards, Deva www.bittoggler.com -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
