The media framework uses various private APIs, has components that talk
directly to hardware (DSPs for encoding/decoding, etc), etc. This doesn't
seem to me like a good idea.
And not for perspective -- you would not end up with two instances of media
service always running, because you are
I wouldn't care about Android 2.2 at this point, as the MediaPlayer is
really incomplete and buggy in this version and lower.
It is a lot better in 2.3.x and above.
Most third party video players use ffmpeg as the media framework.
--
You received this message because you are subscribed to the
Thanks for the response b0b.
I realize MediaPlayer will not do the job for me - at least in 2.2. But, is
there any framework-level requirement that is stopping me from building the
newer media framework source and deploying it on 2.2? Perhaps this would
make my app prohibitively large? Or
3 matches
Mail list logo
