[android-porting] Re: Camera Object in Video Capture Case

2009-02-17 Thread Dave Sparks
We cannot allow the application to make any changes to the camera that could potentially violate the contract between the camera and the media recorder. For example, let's say that the video frame size is set to CIF, and the application changes it to QCIF in the middle of a recording. This will ca

[android-porting] Re: Camera Object in Video Capture Case

2009-02-18 Thread steve2641
Dave, Can you explain a little further on what you mean when you say "enable a subset of safe API's"? Since a good percentage of the interface configuration is handled by the Camera Parameters, and the Camera Parameters are pretty much an direct interface between the App and the Camera HAL, I'm

[android-porting] Re: Camera Object in Video Capture Case

2009-02-18 Thread Dave Sparks
I don't want to add another API to MediaRecorder. We can add another parameter to the setParameter interface in the camera HAL to indicate if the call comes from the owner of the camera. The camera driver is then responsible for preventing other callers from changing anything that might affect th

[android-porting] Re: Camera Object in Video Capture Case

2009-02-19 Thread steve2641
We are not looking to allow the application to retrieve the preview frames during video recording. The callback I talk about is for another feature. I'll email you directly the general feature description. Another thought occurred to me, does the current architecture allow the displayed preview

[android-porting] Re: Camera Object in Video Capture Case

2009-02-24 Thread steve2641
Dave, any comments on my last reply? On Feb 19, 7:47 am, steve2641 wrote: > We are not looking to allow the application to retrieve the preview > frames during video recording.  The callback I talk about is for > another feature.  I'll email you directly the general feature > description. > > An

[android-porting] Re: Camera Object in Video Capture Case

2009-02-24 Thread Dave Sparks
I think we will be adding a general purpose callback mechanism from camera to application. I have to think about how to make that work in the MediaRecorder case without muddying things up too much. I believe this will address your request. There are also plans to add separate parameters for video

[android-porting] Re: Camera Object in Video Capture Case

2009-03-29 Thread ever
Dave, I find that setVideoSize in MediaRecorder leads to 1. ((AndroidCameraInput *)mVideoInputMIO)->SetFrameSize(ac->width, ac- >height); 2. config->SetOutputFrameSize(0, mVideoWidth, mVideoHeight); obviously AndroidCameraInput::SetFrameSize setup the video size of camera preview, and PVMp4H263Enc

[android-porting] Re: Camera Object in Video Capture Case

2009-03-30 Thread Dave Sparks
Yes, that's because the msm7k doesn't support separate encoder frame size. There will be changes coming in master to support different preview and encoder frame sizes. On Mar 29, 11:26 pm, ever wrote: > Dave, > I find that setVideoSize in MediaRecorder leads to > 1. ((AndroidCameraInput *)mVideo