Menu

#181 Consider shutter lag for burst mode interval

1.0
open
nobody
None
2022-11-08
2016-07-31
No

First of all, great app – finally a camera app that will work for time-lapse photography!

I tried to take pictures for a time-lapse movie with OpenCamera today, using the Burst Mode feature. It was shortly after sunset, I had selected ISO 200 and set the burst mode interval to 3 seconds. However, the actual delay between shots was in the 5–6 second range, apparently due to shutter lag and possibly internal processing. Automatic ISO did not appear to suffer from this, but I wanted a low ISO to get more pronounced blur effects. With ISO 100 there is an even longer delay, which prompted me to go back to ISO 200.

Suggestion: start the timer for the next shot just before triggering the current one, not after. (Some extra logic will be needed if the shutter/processing lag is longer than the interval – in that case, the next shot should be triggered as soon as the camera is ready again.)

Discussion

  • Mark

    Mark - 2016-08-14

    Good point, have added to my todo.

     
  • Eric Sibert

    Eric Sibert - 2021-07-14

    I'm also trying to use Open Camera for Mapillary picture collecting. I tried the burst mode with 1.0 s. I set focus to infinity. I found that real interval was of 1.33 s. It is also not very stable on long term (at least for 10 mn, I found jumps up to 0.3 s). So I would appreciate that effective interval is equal to the asked one but also to have a long term stability.

     
    • Enteq

      Enteq - 2022-11-03

      I have an even worse problem that appeared recently with the Pixel 6 Pro with the current firmware: the lag for interval mode varies. Apparently the photo is only made when the phone is not moved too much, see also [#1000]

      Example (set to 0.5s, focus infinite !!)

      2022:11:01 16:29:21.139194+01:00
      2022:11:01 16:29:23.569789+01:00
      2022:11:01 16:29:27.273649+01:00
      2022:11:01 16:29:31.404508+01:00
      2022:11:01 16:29:32.241946+01:00
      2022:11:01 16:29:33.439311+01:00
      2022:11:01 16:29:37.203452+01:00
      2022:11:01 16:29:41.433806+01:00
      2022:11:01 16:29:43.970283+01:00
      2022:11:01 16:29:48.36290+01:00
      2022:11:01 16:29:50.599255+01:00
      2022:11:01 16:29:51.865928+01:00
      2022:11:01 16:29:55.897013+01:00
      2022:11:01 16:29:56.632316+01:00
      2022:11:01 16:29:57.764104+01:00
      2022:11:01 16:29:58.966344+01:00
      2022:11:01 16:30:00.433395+01:00
      2022:11:01 16:30:01.563358+01:00
      2022:11:01 16:30:03.97449+01:00
      2022:11:01 16:30:04.460477+01:00
      2022:11:01 16:30:05.861661+01:00
      2022:11:01 16:30:07.29540+01:00
      2022:11:01 16:30:08.266087+01:00
      2022:11:01 16:30:09.527707+01:00
      2022:11:01 16:30:11.461630+01:00
      
       

      Related

      Tickets: #1000


      Last edit: Enteq 2022-11-03
  • Anonymous

    Anonymous - 2022-11-04
    Harun mudhai ![](Header Header Header
    Cell Cell Cell
    Cell Cell Cell https://)
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB