I wasn't sure where to post this, so I'm posting it here as it probably qualifies as a bug.

There is an issue affecting cameras that can record video in non-video modes. When recording multiple videos without switching the camera off, the CHDK bitrate / remaining time display gets more and more incorrect with each recording.

I believe the logic inside gui_osd_draw_movie_time_left() (core/gui_osd.c) fails for recordings made in modes other than video.

The following patch seems to help, although I'm not sure it's optimal and without side effects.

I wasn't sure where to post this, so I'm posting it here as it probably qualifies as a bug.

There is an issue affecting cameras that can record video in non-video modes. When recording multiple videos without switching the camera off, the CHDK bitrate / remaining time display gets more and more incorrect with each recording.

I believe the logic inside gui_osd_draw_movie_time_left() (core/gui_osd.c) fails for recordings made in modes other than video.

The following patch seems to help, although I'm not sure it's optimal and without side effects.

I first noticed this while working on the D6 movie support code, but managed to reproduce it on my Ixus115.Can somebody with a dedicated movie button camera confirm the issue?

I see something similar to a sx410 camera.The remaining time after a dozen recorded clips starts to grow instead to falling.Much stranger things happen if I delete the last recorded clip.After deleting of the last recorded video,for the remaining time and data rate are displayed completely wrong data.Regardless of the incorrect displayed data rate (KB/s), the size of the recorded file corresponds to the settings for the desired bitrate.With the restart of the camera everything returns to normal.

I wasn't sure where to post this, so I'm posting it here as it probably qualifies as a bug.

There is an issue affecting cameras that can record video in non-video modes. When recording multiple videos without switching the camera off, the CHDK bitrate / remaining time display gets more and more incorrect with each recording.

Can somebody with a dedicated movie button camera confirm the issue?

Good find. I confirmed this on elph130, and the patch seems to resolve it.

I don't see any obvious problems, but the but moving the record_running logic before the main if might make it easier to follow, as in the attached.