> SF sits above OMX just like OC. If you have an OMX-IL
> implementation that works with OC through Gallery, how difficult/easy
> would it be to move this to SF?
Most of the changes made in Opencore OMX IL (in
opecnore/nodes/*node.cpp) will apply to stagefright OMX IL too (mostly
in OMXCodec.cpp).
> SF sits above OMX just like OC. If you have an OMX-IL
> implementation that works with OC through Gallery, how difficult/easy
> would it be to move this to SF?
true, stagefright and opencore are peers.
as said above, we need SF OMX IL changes, OMX Core integration needs to be done.
basic steps are:
integrate omx core
in opencore -> we publish omx core .so in /etc/pvplayer.cfg files
in stagefright -> we publish our OMX library in libstagefrighthw.so library
add components against MIME type in OMXCodec.cpp->kDecoderInfo[] table
once your compoennt is picked up for your the media, put OMX IL fixes
as required.
> Also, does SF use a different player?
SF uses its own "Player Driver" ( implemented in
StagefirghtPlayer.cpp/AwesomePlayer.cpp)
any media-framework in android should implement android player driver
with start/stop/setdatasource/pause/resume/seekto/etc interfaces, to
take calls from libmedia,libmediaplayerservice.
as we discussed above, gallery or any media application wont be aware
of stagefright or opencore framework, it just uses android media
library calls (ofcourse native apps can directly talk to sf/oc).
internally Android media library picks a player type, as in
media/libmediaplayerservice/MediaPlayerService.cpp=>getPlayerType()
[1], and then process with start/stop/setdatasource/pause/resume/seek
calls
> --
> unsubscribe: android-porti...@googlegroups.com
> website: http://groups.google.com/group/android-porting
>
--
Regards,
Deva
www.bittoggler.com