They probably use FFmpeg to take care of getting the encoded media data than pushing that untouched data using some type of proxy server to the MediaPlayer to do the hardware decoding. That's probably all... :-)
On Sep 16, 2:22 am, Doug <beafd...@gmail.com> wrote: > If authentication over rtsp is a documented standard, then you could > file a bug with details and hope that it gets resolved in a future > version. > > Doug > > On Sep 15, 12:17 am, "B.Arunkumar" <awsnetworkrecor...@gmail.com> > wrote: > > > > > Hi, > > > Regarding your question, MediaPlayer supports RTSP streaming but > > does not take all RTSP URLs, (with authentication, for instance). > > Atleast that is the experience we have had. > > The built in C++ RTSP Stack that comes with mediaplayer seems to have > > limited capabilities. > > > Arunkumar > > > On Sep 11, 4:19 am, Doug <beafd...@gmail.com> wrote: > > > > On Sep 9, 1:30 am, "B.Arunkumar" <awsnetworkrecor...@gmail.com> wrote: > > > > > Would somebody have some idea what exactly has RockPlayer done in > > > > the Hardware Decoding mode on a high level basis? I mean have they > > > > used the mediaplayer as it is or they have changed something at the > > > > source code level of MediaPlayer to get more improvements than the > > > > MediaPlayer (support more RTSP Url formats) and things like that? > > > > Why do you say that MediaPlayer does not support rtsp? I ask this > > > because it does support rtsp. It's documented. The audio/video > > > format of the stream still has to be supported by the device, though. > > > > Doug -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
