# Mapillary\_Tools "Mapillary Capture Speed Too Fast Error" when capturing at freeway speeds via GoPro TimeWarp **URL:** \ **Category:** Contributing and equipment\ **Created:** [July 23, 2025, 6:21pm UTC](https://forum.mapillary.com/t/mapillary-tools-mapillary-capture-speed-too-fast-error-when-capturing-at-freeway-speeds-via-gopro-timewarp/9785 "2025-07-23T18:21:42Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![GITNE](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/gitne/32/70659_2.png) [@GITNE](https://forum.mapillary.com/u/GITNE)\ **Post date:** [July 24, 2025, 4:23pm UTC](https://forum.mapillary.com/t/mapillary-tools-mapillary-capture-speed-too-fast-error-when-capturing-at-freeway-speeds-via-gopro-timewarp/9785/10 "2025-07-24T16:23:31Z")
> [@GITNE](#): > > There is basically no way to detect a _TimeWarp_ video for any consumer 🤔 There is (even with standard metadata only)! But, it is overly complicated. 🤦 You have to count the number of timecodes per second and compare it to the playback fps. Fortunately, the MAX writes timecode data. 👍 This is indeed one of MAX’s true pros. Hence, if the timecode stream has fewer timecodes (frame timestamps) per second than the video stream playback fps then one can assume the video file to be a _TimeWarp_ video. Is it great? 🫤 Eh, no. Is it worth to put in the additional effort into `mapillary_tools`? I am not so sure because it is basically a GoPro only thing, which should have been solved better by GoPro in the first place by enabling camera users to choose a playback fps rate. 🤷 --- _[View the full topic](https://forum.mapillary.com/t/mapillary-tools-mapillary-capture-speed-too-fast-error-when-capturing-at-freeway-speeds-via-gopro-timewarp/9785)._