On many of my flying videos, the speed displayed on the template goes away when I accelerate past 127 Kts - it just wanders around at random low values. The other parameters (altitude and heading) remain functioning. The GPS speed comes back when I drop back down below 120 Kts or so. Is there any way to inspect the .gpx files in order to determine if the problem is in the camera itself or the Virb Edit software?
GPX files are just text files in an XML format. The only problem might be the lack of end-of-line characters which will make everything run together (too lazy to go get my Elite and check). But a lot of text editors can view XML correctly even without the end-of-lines. At the top there should be a URL for the specification of the GPX format. My guess is that speeds in the GPX are in either m/s or km/h, so you're suspicion that it's a VIRB Edit unit conversion problem might be right. If it's a problem with the Elite itself, though, then you're probably out of luck, since it's very unlikely to be fixed.
Is it possible that Virb Edit is having trouble doing all the computations necessary to compute my speed at a certain point? My CPU is an Intel Core i7 2.79 GHz with 4 cores, 9GB RAM. I'm now using v. 5.1.1 and ffmpeg encoder and DXVA decoder as recommend by the "Detect Settings for Optimal Performance" function.
The problem is back, and I noticed that when reaching 127 Kts,, the indicated speed drops to zero and then continues to climb as I accelerate. It seems like adding 127 to the displayed speed is close to being correct. So does Virb Edit have a buffer limitation built in so that it can't handle speeds over 127 Kts?
