In a video from a motorcycle ride, as a stop sign comes into view 30 or 40 yards ahead, the mph display drops to zero, pauses at zero for a bit, then starts accelerating again. Meanwhile the POV hasn't reached the stop sign yet. Then the POV in the video reaches the stop sign and stops, while the speed in the display has gone back up to 45 mph or whatever. It's ridiculous. The offset is enough to be a major annoyance.
Has anybody else encountered this?
Are there any plans to fix this? I just installed an update with a gratifying number of bug fixes, but this needs to be on the list. They could at least allow the user to enter a fudge factor offset and roughly calibrate by hand.
Or I could write a Perl script to offset all the times in the GPS data file by a given fudge factor, if that's text. UPDATE: FIT is not text, it's binary. OK, I'll work around their bugs in C instead.