Apps & Software Archive

VIRB Edit Windows G-Metrix data showing moving speed while stationary, not a sync issue

G-Metrix data showing moving speed while stationary, not a sync issue

Former Member over 9 years ago

So I got an Edge 1000 cycling computer to have better data than the Virb X was able to provide... but for some reason even when importing the G-metrix data from Edge for speed, Virb edit is ignoring the data and doing some kind of smoothing algorithm or something that is creating erroneous speed outputs.

Here is a specific example (was riding along, came to a stop to look at map for a little over a minute) to demonstrate what I am talking about...you can clearly see the Edge is registering 0mph, and that Virb Edit is using Edge data for recorded speed... yet still a decaying speed is displayed the entire time I am stopped, and does not get accurate again until I am moving about 15mph.

Screen shot of Virb edit showing Edge data is reference for recorded speed, yet 0mph is recorded by Edge:

And a short video of entire time duration... clearly 0mph is correctly recorded by Edge, yet not until 10 seconds after I began to move again does the speed displayed by Virb Edit match what is displayed by the source data (the Edge 1000). It makes me question the validity of any of the displayed speeds at all times.
https://youtu.be/_SQp2pTMyNw

Is this a bug in Virb Edit? Why is it not just using actual speed from Edge when that is what I have requested?

0 Former Member over 9 years ago

Unfortunately these kinds of issues are always a bit difficult to track down.

1. How do you know that the Edge recorded speed data is correct in the FIT file? What the edge displays and what is in the FIT file is not necessarily the same.
2. What happens if you use the Calculated 2D speed gauge instead?

VIRB Edit does some smoothing/interpolation, but if the input data is dense enough what you describe should not happen.

There might well be a bug. If you can, share the FIT from X, Edge and ideally the source video with me and I can dig deeper.

0 Former Member over 9 years ago

Unfortunately these kinds of issues are always a bit difficult to track down.

1. How do you know that the Edge recorded speed data is correct in the FIT file? What the edge displays and what is in the FIT file is not necessarily the same.
2. What happens if you use the Calculated 2D speed gauge instead?

VIRB Edit does some smoothing/interpolation, but if the input data is dense enough what you describe should not happen.

There might well be a bug. If you can, share the FIT from X, Edge and ideally the source video with me and I can dig deeper.

Thank you for the offer to help! :D

1) you are right... I don't... but why would the fit file not record the same data that is displayed?
2) will check that out and get back to you later when I have more time... what is technical difference between Calculated 2D speed and recorded speed? I mean in terms of what the Garmin Edge is recording.

I will send the fit files later as well... but I just realized there is another variable that may be at play... I was using wheel speed sensor for edge speed.

Because of the limitations of GPS speed with 1hz, I had hoped the wheel speed sensor would fix everything... Isn't there a way to dumb down the G-metrix displayed data to just look at what the recorded speed is, same as on unit? No smoothing, no interpolation, etc. With wheel speed sensor it isn't needed because I am not using GPS for distance or speed.

0 Former Member over 9 years ago

Recorded speed is what the device tells us the speed is.
Calculated 2D speed gets derived / calculated from lat/lon.
Calculated 3D speed gets derived / calculated from lat/lon/elevation.

However, there is a wrinkle, we might not be handling the wheel speed sensor data properly (which gets logged outside of "regular" recorded speed in FIT).

Would still be great to get your data, would make a good testing case to make sure we have our ducks in a row.

Thank you for your help, and apologies for the trouble.

0 Former Member over 9 years ago

I went on vacation right after this and totally forgot about sending fit file. You want it emailed (if so where?) or just attach it on forum?

I just made another ride video and speed in gmetrix is not coming from wheel speed sensor even though sensor works fine and I am using exported data from Edge 1000...it is bizzare. It still uses gps speed for data display, even though I went through a lot of time, money, and hassle to use a cycling computer on moto just to have wheel speed sensor for accurate speed. Frustrating.

Is there any way to check if any progress was done on Garmin case number 11998671? It was for Virb ignoring speed sensor data (before I bought Edge 1000), and I am wondering if root issue is same thing; g-metrix ignoring speed sensor data and using gps only.

0 Former Member over 9 years ago

I just made another ride video and speed in gmetrix is not coming from wheel speed sensor even though sensor works fine and I am using exported data from Edge 1000...it is bizzare. It still uses gps speed for data display, even though I went through a lot of time, money, and hassle to use a cycling computer on moto just to have wheel speed sensor for accurate speed. Frustrating.

Is there any way to check if any progress was done on Garmin case number 11998671? It was for Virb ignoring speed sensor data (before I bought Edge 1000), and I am wondering if root issue is same thing; g-metrix ignoring speed sensor data and using gps only.

For reference:
https://forums.garmin.com/showthread.php?342783-Virb-X-using-wheel-speed-sensor-G-metrix-data-is-still-using-GPS-for-speed