Languages

Menu
Sites
Language
Is Z1 camera support continuous capture

Hi, 

I just want to know if the samsang Z1 camera support continuous capture, if yes, is the call back function _camera_capturing_cb was called every time or just call once after all continous capture finished, thanks.

camera_start_continuous_capture(cam_data.g_camera, 20, 300, _camera_capturing_cb, _camera_completed_cb, NULL);

 

Thanks.

List

Responses

10 Replies
Vikram

Hello,

Z1 doesn't support Burst shot( continuouse capture). and according to the description, camera_capture_cb() is called per each image.

 

int camera_start_continuous_capture  ( camera_h  camera, 
   int  count, 
   int  interval, 
   camera_capturing_cb  capturing_cb, 
   camera_capture_completed_cb  completed_cb, 
   void *  user_data 
 )

 

Remarks:

         If this is not supported zero shutter lag occurs. The capture resolution could be changed to the preview resolution.
 This function causes the transition of the camera state from CAMERA_STATE_CAPTURING to CAMERA_STATE_CAPTURED automatically
 and the corresponding callback function camera_capturing_cb() and camera_capture_completed_cb() will be invoked
 Each Captured image will be delivered through camera_capturing_cb().
 The camera_capture_completed_cb() callback notifies about the completion of an entire capture.
 The camera's preview should be restarted by calling camera_start_preview().

 

Hope this will help you.

 

Jean Yang

  Hi, 

Thanks for your info.

I have tested the  below APIs on Z1, all return false, seems Z1 not support continous capture. But I have one more question, what the min- interval value of the normal capture, I set an 200 millisecond in a for loop, but the interval always lager than it.

 

camera_is_supported_zero_shutter_lag(cam_data.g_camera);
camera_is_supported_continuous_capture(cam_data.g_camera);
 

Vikram

Hello,

This is the function of normal capture. but I couldn't find a parameter for interval inside. so I guess that you called camera_start_continuous_capture().

int camera_start_capture  ( camera_h  camera, 
  camera_capturing_cb  capturing_cb, 
  camera_capture_completed_cb  completed_cb, 
  void *  user_data 
 )

Jean Yang

Hi, 

I used normal capture, but in a for loop I set a delay. After tested, I found the camera need to take about 0.7 seconds to capture one image. Is there anyone know the the exactly min interval of the Z1 in normal capture?

my code is listed below:

for (int count = 0; count < 20; count++) {
            usleep(200000); //0.2second delay, but accually result is take one image need take 0.7 seconds
            camera_start_preview(cam_data.g_camera);
            error_code = camera_get_state(cam_data.g_camera, &state);
            dlog_print(DLOG_ERROR, LOG_TAG,
                    "camera_set_preview_cb  camera_get_state = %d", state);
            error_code = camera_start_capture(cam_data.g_camera,
                    _camera_capturing_cb, _camera_completed_cb, NULL);

            error_code = camera_get_state(cam_data.g_camera, &state);
            dlog_print(DLOG_ERROR, LOG_TAG,
                    "camera_start_capture count= %d camera_get_state = %d",
                    count, state);
        }

Vikram

Hello,

AFAK, actually nobody know the interval of Camera cpature because of some delay inside of firmware. Also the performance of camera application can be affected by other parameter like CPU&memory usage. so I think that  burst mode should be supported by firmware.  

Jean Yang

Hello, 

Yes, you are right, I have test in the code, the camera performance is impacted by the CPU&memory, and it's hard to got an exactly value. But what I want to do is try to find the minmum interval of Z1 in normal capture mode, can you share more details about the burst mode?

Jeongmo Yang

Hi,

 

camera_start_capture API will be failed if camera state is not "CAMERA_STATE_PREVIEW".

When you call camera_start_preview API after camera_capture_completed_cb,

You can start next capture since camera state will be changed from CAMERA_STATE_CAPTURED to CAMERA_STATE_PREVIEW.

I think it's the fastest timing for next capture.

But, It does not guarantee same capture interval.

Jean Yang

Hi, 

Yes, you are right, I have done the testing before, the interval is not fixed as you said, and the interval is not fast as I wanted, so hope there is now way in next version SDK.

Jeongmo Yang

continuous capture API is already provided in Tizen 2.3.

but, it's dependent on target and Z1 does not support it.(emulator also does not support it.)

I hope that continuous capture is supported in the future on next Tizen target.

 

Jean Yang

Exactly, Z1 does not support continous caputure...and you can say the SDK has the API, but since there is noly one Tizen device on martket, so I make a mistake here, anyway, as you said, hopt the next version Z2 has such function.