audioflinger and surface flinger should not be impacted. basically, to rewrite the code in opencore/android is enough. that's something like gstreamer/android or xxxx/android...
On Feb 22, 11:53 am, Freepine <[email protected]> wrote: > I guess the entire media framework includes not only opencore, but also > media api, audio flinger and perhaps part of surface flinger:) > If you just want to replace opencore, I think you can look at the code of > PVPlayer, PVMediaRecorder and PVMetadataRetriever and replace them with your > own implementations. > > http://android.git.kernel.org/?p=platform/frameworks/base.git;a=tree;... > > On Sun, Feb 22, 2009 at 11:37 AM, jerand <[email protected]> wrote: > > > yes .. thats exactly my point .. if there are well defined interfaces; > > then third party applications should work as such if the same > > interface is used. > > please comment. > > > On Feb 22, 5:11 am, Paranoia <[email protected]> wrote: > > > is it impossible to use the same media api? i mean the app developer > > > does not need to care which media engine s/he is using. replace > > > opencore with gstreamer, or something else. > > > > On Feb 22, 1:21 am, Dave Sparks <[email protected]> wrote: > > > > > I don't think you want to replace the entire media framework. If you > > > > do, it's highly unlikely that 3rd party apps are going to work with > > > > your framework. > > > > > On Feb 21, 9:05 am,jerand<[email protected]> wrote: > > > > > > i want to replace the entire media framework with my own framework to > > > > > process media data .. > > > > > is that feasible ? how tightly is open core coupled with the > > > > > platform ? > > > > > > On Feb 20, 10:06 pm, rktb <[email protected]> wrote: > > > > > > > Please help me understand ... are you trying to replace "opencore" > > of > > > > > > "mediaplayer" ? > > > > > > > -Ravi > > > > > > > On Feb 20, 11:02 am, Paranoia <[email protected]> wrote: > > > > > > > > just read the code. it's not too difficult. > > > > > > > but you have to replace the whole mediaserver, if you want to > > replace > > > > > > > the opencore > > > > > > > > On Feb 21, 12:01 am, scs sek <[email protected]> wrote: > > > > > > > > > This can be partially reused for the application, Is there any > > > > > > > > document for platform interface? > > > > > > > > On 2/20/09, Dave Sparks <[email protected]> wrote: > > > > > > > > > > There is a well-defined interface for new media players. > > There are > > > > > > > > > already 3 players in Android: OpenCore, Vorbis, and MIDI. > > They each > > > > > > > > > implement MediaPlayerInterface. > > > > > > > > > > On Feb 19, 11:26 pm,jerand<[email protected]> wrote: > > > > > > > > >> are there any well-defined interfaces on how the android's > > app > > > > > > > > >> framework and open core interact? if so, is there any > > document for the > > > > > > > > >> same.Like > > > > > > > > >> Androids app framework ||| media interface ||| some media > > framework > > > > > > > > >> ||| platform interface ||| platform > > > > > > > > > >> or should new wrappers be written to map to player app of > > the > > > > > > > > >> application framework layer if am going to use the already > > added apps > > > > > > > > >> like player or recorder ? > > > > > > > > > >> one more approach could be to develop a new player app which > > uses the > > > > > > > > >> new framework, pack it and add to the app framework. > > > > > > > > > >> Basically I would like to know of the standard media > > interfaces for > > > > > > > > >> native android applications like player/ recorded !!!- Hide > > quoted text - > > > > > > > - Show quoted text -- 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 [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 -~----------~----~----~----~------~----~------~--~---
