Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

time data does not match format #141

Closed
CaptFreezer opened this issue Jul 4, 2023 · 11 comments
Closed

time data does not match format #141

CaptFreezer opened this issue Jul 4, 2023 · 11 comments
Labels
gopro hardware/firmware issue a problem with the camera possibly-fixed Maybe fixed already, but I can't test it or would like confirmation

Comments

@CaptFreezer
Copy link

Hello,

first of all, thanks for this great tool, it helps alot to get GPS Data from my GoPro :)
but, one of my last videos are a bit strange.
I have 4 seperate files, and the 3rd one is throwing this error message:
ValueError: time data '5509100082240400' does not match format '%y%m%d%H%M%S.%f'
when i am using gopro-dashboard.py for the other 3 videos it renders fine, but that 3rd video is very strange, and i don't know what the problem could be..
i have read, that this number 5509100082240400 could be a GPS-DateTime value?
When i am using this cmdline
exiftool GH030037.MP4 -ee -G3 -sampletime -gpsdatetime
everything seems to be ok and working.. correct date and time values.. example:

[Doc1]          GPS Date Time                   : 2023:06:25 11:17:50.284
[Doc2]          GPS Date Time                   : 2023:06:25 11:17:50.284
[Doc3]          GPS Date Time                   : 2023:06:25 11:17:52.374
[Doc4]          GPS Date Time                   : 2023:06:25 11:17:52.374
[Doc5]          GPS Date Time                   : 2023:06:25 11:17:52.374
[Doc6]          GPS Date Time                   : 2023:06:25 11:17:55.784
[Doc7]          GPS Date Time                   : 2023:06:25 11:17:56.554
[Doc8]          GPS Date Time                   : 2023:06:25 11:17:58.039
...

If you need something for me to test or something else, i can help you with that.

Regards

@time4tea
Copy link
Owner

time4tea commented Aug 6, 2023

Hi - Thanks for your interest. This is something that has been reported one time before - that the GoPro is recording invalid datetime values in its datastream. It was previously reported in #22
I also raised it as an issue against the GoPro itself. - gopro/gpmf-parser#162 - but nobody was able to reliably reproduce the problem. It is possible that its a filesystem corruption issue,or a defect in the GoPro firmware.
Out of curiosity, what type of GoPro didd the recording?

@time4tea
Copy link
Owner

time4tea commented Aug 6, 2023

Hi @CaptFreezer - would you be able to share your mp4 file with me?

It will be used only for diagnostic reasons.

If you can, and please don't feel obliged, please send a link to [email protected]

I find that wetransfer can be good for this.

Thanks!

James

@CaptFreezer
Copy link
Author

My GoPro 9 Hero Black did the recording. The strange thing is, out of those 4 files, only the 3rd file has this issue.
I can share this video, when i am at home. Any sites you prefer to upload/download/share the file?

@time4tea
Copy link
Owner

time4tea commented Aug 7, 2023

Thank you for the info. If the file is 2GB or less, then wetransfer can be good.

If your file is bigger than this, we'll have to find an alternative...

Let know at [email protected]

Thanks!

@CaptFreezer
Copy link
Author

I think it will be 4GB, but i will see, when i am at home (at around 5:30 PM MESZ)

@time4tea
Copy link
Owner

time4tea commented Sep 2, 2023

Hi thanks for the file - I can definitely see that there are two dodgy timestamps in the file.... however actually the GPS chip was misbehaving throughout, and there is very little usable information in the file. I have seen this one time before, and there's not much I can do with the file unfortunately. I would suggest a factory reset, and upgrading to the latest firmware if this isn't already the latest version.

@time4tea
Copy link
Owner

time4tea commented Sep 2, 2023

By the way I love the video - If you can find a still frame that you don't mind sharing, I'd love to add it to the gallery.

@time4tea time4tea added the gopro hardware/firmware issue a problem with the camera label Sep 2, 2023
@time4tea
Copy link
Owner

time4tea commented Sep 2, 2023

It seems that whatever this bug in the GoPro firmware is, it won't be fixed. Maybe I'll try to find a way to workaround it.

@CaptFreezer
Copy link
Author

Thanks for the information. :)
If you can find a workaround, it will be nice. :)
If you want the map and speed thing in action, you can use this video: https://www.youtube.com/watch?v=S-Hf78bHOjY

@time4tea
Copy link
Owner

There is a workaround for this in 0.124.0 - Should be available in PyPI very soon.

@time4tea time4tea added the possibly-fixed Maybe fixed already, but I can't test it or would like confirmation label Jan 14, 2024
@bphilli7
Copy link

Chiming in... I recorded a series of videos on a GoPro Hero 10 using "timewarp". The gopro-dashboard-overlay software led me to this link. I believe the error message that was spammed when I processed my original video is due to the way the gopro firmware is recording the timestamp datastream in this timewarp mode. The video was 9600 frames in length (30fps, 5m:20s duration). gopro-dashboard-overlay reported 9360 identified Timeseries points, all of which had suspicious GPS packets.

gopro-dashboard-overlay log file.txt

Uploading the output of exiftool GH020037.MP4 -ee -G3 -sampletime -gpsdatetime > timestamps.txt for awareness. As can be seen, in this mode the GPS timestamps are "bursty". The Sample timestamps are periodic and linear.

timestamps.txt

I am very happy with this tool and thank you for your hard work on it. I only have GoPro timewarp videos at the moment but will start recording some new constant time videos to make more use of this excellent software.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gopro hardware/firmware issue a problem with the camera possibly-fixed Maybe fixed already, but I can't test it or would like confirmation
Projects
None yet
Development

No branches or pull requests

3 participants