Timestamps not matching up to video duration

[cshshsh]

I am trying to calculate the time elapsed between each video I have based off the timestamp indicated in the video file names. However, these calculations are not matching up to the duration of the recorded video. 

For example, I have a video that is named 090000, indicating it started recording at 09:00:00. It is 20 seconds long, so I would expect the next sequential video to start earliest 09:00:20. However, the timestamp of the next video is 090017, which would not be possible, and I have reviered the footage and there is no overlap in the recordings.

I would appreciate any insight behind what may be causing this and how I could calculate the time elapsed between videos accurately.

[jguerdat]

Is the camera connected to AC power? I wonder if "foresight" (3 seconds before the actual event that is triggering the recording) is happening. I don't know for sure that the Go 2 on AC power supports foresight but it's possible.

[StephenB]

---

@cshshsh wrote:

For example, I have a video that is named 090000, indicating it started recording at 09:00:00. It is 20 seconds long, so I would expect the next sequential video to start earliest 09:00:20. However, the timestamp of the next video is 090017, which would not be possible, and I have reviered the footage and there is no overlap in the recordings.

---

Have you also looked in the metadata of the file?  If you are using Windows,  then MediaInfoXP is a useful tool that shows you a lot of info - including recording length, and encoded time.

• https://www.videohelp.com/software/MediaInfoXP

You can also right-click on the file, select properties and then details.  But that only gives you the minute of the encoded time, not the second.

[cshshsh]

Hi all,

Thanks for the suggestions! I don't think it's a case of "foresight" since the videos with negative time elapsed in between vary so it's not just 3 seconds. I also looked at the metadata and it lines up with the file names. I guess I'll just treat it as measurement inaccuracy..