Virb elite / Virb edit speed errors

Former Member
Former Member
After a half hour mountain bike ride I created a video using Virb edit downloaded from my Virb elite. The heart rate overlay display gives sensible readings but the speed overlay gives silly max readings e.g 145mph.
I used the Garmin fit app on the iPhone at the same time and this gave sensible speed readings (Max 32.1km/h).
Would appreciate any thoughts on this please.
  • Former Member
    0 Former Member over 10 years ago
    FIT errors etc.

    Thanks!

    I checked out the file from the 13th. It looks like the high speed values are indeed in the FIT file.

    They don't show up in BaseCamp because BaseCamp ignores the "speed" data in FIT, and calculates speed from lat/lon changes over time. VIRB Edit assumes that if the FIT file has speed data it's more accurate and prefers it over the calculated speed. That's unfortunately a wrong assumption in your case.

    We'll work on the device side to try to fix the erroneous speeds that get written out.

    On the VIRB Edit side we are working on a solution that lets the user pick which speed data they want to use: FIT speed, calculated speed, calculated 3D speed, etc.

    It looks like the bad data is at the beginning of the file, so you might be able to trim the video so the beginning isn't including and you should get better max values.

    I hope this is at least somewhat helpful, our apologies for the trouble.


    Thank you for the detailed reply.
    Hopefully you will be able to get to the bottom of where the FIT file is going wrong and issue a firmware upgrade to resolve this.
    A VIRB edit fix to use calculated speed would be most useful so I can use my existing files.
    I did import the GPX files into Excel and performed the speed calc from lat/lon differences which gave expected results.
  • Former Member
    0 Former Member over 10 years ago
    Speed errors in FIT files

    Thanks!

    I checked out the file from the 13th. It looks like the high speed values are indeed in the FIT file.

    They don't show up in BaseCamp because BaseCamp ignores the "speed" data in FIT, and calculates speed from lat/lon changes over time. VIRB Edit assumes that if the FIT file has speed data it's more accurate and prefers it over the calculated speed. That's unfortunately a wrong assumption in your case.

    We'll work on the device side to try to fix the erroneous speeds that get written out.

    On the VIRB Edit side we are working on a solution that lets the user pick which speed data they want to use: FIT speed, calculated speed, calculated 3D speed, etc.

    It looks like the bad data is at the beginning of the file, so you might be able to trim the video so the beginning isn't including and you should get better max values.

    I hope this is at least somewhat helpful, our apologies for the trouble.


    Trimmed video to the last 46 seconds and the speed is still the same (~146mph).
  • Former Member
    0 Former Member over 10 years ago
    Trimmed video to the last 46 seconds and the speed is still the same (~146mph).


    Have you tried editing the high speeds out of the fit file?
  • Former Member
    0 Former Member over 10 years ago
    Fit file errors

    Have you tried editing the high speeds out of the fit file?

    No but found a program that works by using the GPX file instead of the fit file. It is the free Dashware program which allows you to select the data file unlike Virb edit which automatically uses the fit file.
  • Former Member
    0 Former Member over 10 years ago
    Fit file problem

    Hi Falagar,
    Can you report any progress on the VIRB Elite/FIT file problem please.
    Thank you
    Alan



    Thanks!

    I checked out the file from the 13th. It looks like the high speed values are indeed in the FIT file.

    They don't show up in BaseCamp because BaseCamp ignores the "speed" data in FIT, and calculates speed from lat/lon changes over time. VIRB Edit assumes that if the FIT file has speed data it's more accurate and prefers it over the calculated speed. That's unfortunately a wrong assumption in your case.

    We'll work on the device side to try to fix the erroneous speeds that get written out.

    On the VIRB Edit side we are working on a solution that lets the user pick which speed data they want to use: FIT speed, calculated speed, calculated 3D speed, etc.

    It looks like the bad data is at the beginning of the file, so you might be able to trim the video so the beginning isn't including and you should get better max values.

    I hope this is at least somewhat helpful, our apologies for the trouble.