thanks Praj ;) On 30 Mar, 18:15, praj <prajwal.san...@gmail.com> wrote: > A brief answer: > > Grep for this UUID in opencore dir "0x1d4769f0,0xca0c,0x11dc,0x95,0xff, > 0x08,0x00,0x20,0x0c,0x9a,0x66" > Eg in pvplayer.cfg (libopencore_rtspreg.so <- opencore/modules/ > linux_rtsp/node_registry) > Also grep this "PVMF_MIME_DATA_SOURCE_RTSP_URL" > > libopencore_rtspreg.so loads into mem: > libopencore_rtsp.so ( having libpvstreamingmanagernode.a + rtspclient > engine + sdp + rtp + etc) > > (source found in opencore/protocols/rtsp_client_engine, opencore/ > protocols/sdp/parser, opencore/nodes/streaming/streamingmanager/ > plugins/rtspunicast, etc, etc, etc) > > Good luck with all that. > > On Mar 30, 6:36 pm, André Barbosa <afilipebarb...@gmail.com> wrote: > > > I have tried to add new functionalities to the Android Media Player, > > however, I'm having some problems understanding the structure of the > > Android Media Player. > > I would like know if anyone has also done some work related to Media > > Player, more specifically in the integration of new features in the > > reception and buffering of stream rtsp or http.. > > > So far can see that after the call C functions through the JNI from > > the java interface, mediaLib use bpbinder to communicate with the > > playerdriver which in turn uses the pv_player_engine! However, I can't > > see where it makes the media buffer. > > If someone has already worked in this area and can share some > > information about the structure of Media Player..
-- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting To unsubscribe, reply using "remove me" as the subject.
