Virb Edit messing with data overlays - numbers incorrect

Hi All

I've been thinking that the data displays in the videos that I have created using Virb edit have been odd. They jump all over the place and do not look right. Take a look at this one:

https://www.youtube.com/watch?v=8j54nEUNrFM

watch the speed - it jumps up to 35 MPH then down to 27 then up to 34. It is not steady and my speed was relatively steady.

I worried that this might be due to the accuracy of the GPS on the camera but then I created this video using Dashware:

https://www.youtube.com/watch?v=mZ7tDrOzt_8

(apparently Dashware does not support power yet from Virb, I am sure they will fix that)

Again look at the speed, this is much more what I would expect. It sticks around 29 or 30 for most of the time and does not get up to 34 and does not drop randomly to 27.

Dashware is correct here. There's no way I could get to 34 MPG without a massive extra effort. My cadence does not alter that much so I wasn't going that fast. Also I don't slow to 27.

Both these videos were created using exactly the same video file and GPX file recorded by the camera.

Virb Edit is wrong.

I am pleased that it is not a problem with the data recording of the camera. it's (yet another) problem that can be fixed by updating the software.

Please fix this Garmin.

0 Former Member over 11 years ago

Which data did you use? Did you import directly from the VIRB Elite camera using VIRB Edit?

Which file did you use to create the Dashware video?

One thing I can think of is that you used a FIT file for Dashware which contains concrete speed data, while VIRB Edit currently only calculates speed from the GPS data which can be a bit erratic due to GPS signal bounce.

We will use the FIT file's speed data in a future version, that should smooth things out.

Feel free to attach the FIT and GPX file for your video and I can take a look.

0 Roaders over 11 years ago

I used the GPX file from the Virb which I copied off the camera myself. I used the same GPX file for both videos. I am away for the weekend now but I will post it when I get home.

0 Former Member over 11 years ago

Then Dashware must be doing some processing to smooth out the data and get rid of spikes. We currently display exactly whatever the GPX file contains (doing interpolation between points, but no smoothing). You can view the GPX file in BaseCamp and check the values.

0 Roaders over 11 years ago

Then Dashware must be doing some processing to smooth out the data and get rid of spikes. We currently display exactly whatever the GPX file contains (doing interpolation between points, but no smoothing). You can view the GPX file in BaseCamp and check the values.

Here is a link to the GPX file (I hope it works):

https://docs.google.com/file/d/0B4O9bypp9U8-M3NuazdQRUJ0QTg/edit?pli=1

I had a look at it but it is all lat/long rather than speeds. I don't have basecamp installed.

0 Former Member over 11 years ago

The overlays seem to show exactly what is in the track:

Dashware seems to take out most of the data points by running a smoothing algorithm.

0 Roaders over 11 years ago

Thanks for looking at that.

The Virb doesn't use my cadence / speed sensor to get better speed data then that isn't reliant on GPS?

If it doesn't do that is there any plans to add that in the future?

I saw that there is a wheel size setting in the Power meter setup but not in the cadence setup which implies that it won't use the speed sensor.

Thanks

0 Former Member over 11 years ago

Similar thing here https://vimeo.com/88690645 there's no way I touched 66mph. The Virb seems to display speed data from the GSC10 but record GPS speed data.

0 Former Member over 11 years ago

In a future version we will use the speed data from the FIT(not the GPX) file. That one should be more accurate.

0 Roaders over 11 years ago

Thanks for the reply. Can you explain why it will be more accurate? If the GPS position is inherently less accurate then regardless of which file it is stored in the speed will still be inaccurate...

Is there any chance of using Ant+ speed sensor as the 810 does?