04-06-2021 05:30 AM
subsecond timestamp bug[ New ]
I noticed a bug in a 0.5s photo timelapse:
The Hero 9 black stores the subsectimeoriginal value with 4 chars, and when the value is between 0000 and 0999 it is not written correctly inside the exif metadata. Inside the attached example, the value should be 0990 but it's stored as 990 with an empty char before the first '9':
It looks like a bug in the integer to ascii conversion.
The result is that various software doesn't understand the value, or report a wrong one, and screw up my image/gpx correlation.