We have a new code drop coming soon that will address video record, passing live camera objects from the camera application to the media server for video record, and also hardware video overlays.
It would be helpful if you take a look at that code before you start on your own design. I think it would be better for everyone if we avoid forking the code as much as possible. On Dec 16, 6:46 pm, hanchao3c <[email protected]> wrote: > I have plan to give a new ISurface to PVPlayer and Camera. > > 1. The ISurface can implement base on Hardware video plane. (such as > fb driver or v4l driver) > 2.Change SurfaceFlinger to implement new ISurface and Surface > 3.Change some JAVA code to set it. > > The benifit: > 1.The code of PVPlayer and Camera needn't change. > 2.It can solve PVPlayer and Camera together. > > ==================================================== > For PVPlayer > In the file: > external/opencore/android/playerdriver.cpp > status_t PVPlayer::setVideoSurface(const sp<ISurface>& surface) > > android_surface_output.cpp will call this ISurface then give the frame > data. > > writeAsync->WriteFrameBuf->ISurface::postBuffer > ==================================================== > > ==================================================== > For Camera: > frameworks/base/camera/libcameraservice/CameraService.cpp > In the file: > status_t CameraService::Client::setPreviewDisplay(const sp<ISurface>& > surface) > > This ISurface is using for viewfinder. > ==================================================== --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
