Mapillary_tools v0.14.4 raises unjustified MapillaryCaptureSpeedTooFastError errors at sequence borders

Observation

When processing a GoPro video using mapillary_tools v0.14.4 the tool raises unjustified MapillaryCaptureSpeedTooFastErrors:

c:\myfolder>mapillary_tools --verbose video_process GX020085.MP4
...
09:18:19.757 - ERROR - GX020085.MP4/GX020085_0_000001.jpg: Capture speed 994.321 km/h exceeds max allowed 400.000 km/h
09:18:19.761 - ERROR - GX020085.MP4/GX020085_0_001001.jpg: Capture speed 1078.096 km/h exceeds max allowed 400.000 km/h
09:18:19.764 - ERROR - GX020085.MP4/GX020085_0_002001.jpg: Capture speed 1291.775 km/h exceeds max allowed 400.000 km/h
09:18:19.767 - ERROR - GX020085.MP4/GX020085_0_003001.jpg: Capture speed 1241.966 km/h exceeds max allowed 400.000 km/h
09:18:19.770 - ERROR - GX020085.MP4/GX020085_0_004001.jpg: Capture speed 933.132 km/h exceeds max allowed 400.000 km/h
09:18:19.774 - ERROR - GX020085.MP4/GX020085_0_005001.jpg: Capture speed 1098.933 km/h exceeds max allowed 400.000 km/h
...
9:43:43.615 - INFO - 6589 image read in total
09:43:43.616 - INFO - 589 (710.0 MB) ready
09:43:43.808 - ERROR - 6000 (6.9 GB) MapillaryCaptureSpeedTooFastError
09:43:43.809 - ERROR - MapillaryProcessError: Failed to process 6000 files. To skip these errors, specify --skip_process_errors

context

• video captured with GoPro HERO11black, GPS speeds are valid
• mapillary_tools v0.14.4 executed using Python 3.10 on Win11 machine
• ffmpeg 8.0
• exiftool 13.34

attachments

• cmdline_output.txt
  command line output
• GX020085.json
  ffprobe output of the GX020085.MP4 video file

Start by reproducing video_process with the attached GX020085.MP4 context and compare cmdline_output.txt with GX020085.json, focusing on the reported sequence-border images. Trace the processing path that calculates capture speed and verify the fix against valid GoPro GPS speeds; done means those unjustified errors no longer occur without hiding genuine speed violations.