VIRB Edit 2.9.1 is available

2.9.x will pretty much just be bug fixes.

More or less when will be implemented power balance? Virb Edit or also Virb Elite fw update?

I apologize for that. That's quite embarrassing. We'll get it fixed in 2.9.x.

Thanks for letting us know.

No - I actually like the fact that there is no default overlay in the raw video. I don't like the default gauges and have often wished there was a way to turn them off. I have custom templates set up for when I want gauges, otherwise very happy just to see the video without gauges cluttering up the screen unless I want them.

I guess I have been reading these forums too long in that I expect sarcasm when there was none. :)

Well, for the short term the gauges will be turned back on, as that was really just a bug. But for the medium term we'll look into a way for you to set a default template for the raw video (including no template at all).

Haha, sarcasm is a wonderful thing, no worries, dammit! :)

I am sorry to hear export is giving you trouble. We will work hard to improve matters in 2.9.x.

What is the exact issue with aligning FIT files? We could use some more information to make sure we get it fixed.

If you want to go back to 2.8, uninstall 2.9, download and run the 2.8 installer from http://gawisp.com/perry/virb/.

Thank you for reply.
My video contains more than five parts. the first 3 parts - the continuous video. Other parts are made with pauses.
When I select to all parts of a large fit-file, the mapping information is incorrect. Somehow, the current time is read correctly, and the point, distance, height, etc. taken not for this moment. Somehow adjust new features does not work for this case.
When select all gpx for all parts, then distance and time every parts starts from '0'. The same problem in 2.8.0.

Something I have noticed with the speed overlay since upgrading to 2.9.1.from 2.80 is the speed dial is now calibrated to a max speed of 800km/h where it used to be 200km/h (same as the cadence value still is). I have attached a screenshot of it (gauges on the right).



Something else that was an issue prior to 2.9.1 but is still an issue, the numerical values and the position of the needle in the gauge never seem to line up. Take a look at the cadence values on the left side of the screen shot (above). RPM showing 119 but the needle just above is way past 150, they never seem to be synchronised (119 is the correct value).

Speed is also the same, although with the current calibration, is difficult to see. Have attached a screen shot of previous Virb Edit version (below) showing speed gauge discrepancies, needle shows speed of approx 125km/h.

What is the exact issue with aligning FIT files? We could use some more information to make sure we get it fixed.

@FALAGAR, can you guys work with the Edge team to somehow better sync the start and stop of the recording with an index point in the FIT file that the Edges generate when controlled remotely when its paired via ANT+?

For instance, as I start a video from the Edge, it should at least know that I did this and create some sort of sync point in its FIT file at a minimum (if not already done?), going further with this, perhaps create some sort of coordinated index point?

How is it supposed to work currently if using a Virb basic and not having an accurate time stamp due to no GPS chipset? is there any form of synchronization for time stamps?

I may be wrong, but my understanding was that the speed dial scale was set in accordance with the fit or gpx fit in use have you checked for any sudden spikes in your fit/gpx file?

That may be the answer as I know that the HRM and Power gauges definitely auto calibrate depending on max outputs, but when watching the video back there are no obvious spikes, it may be in the data somewhere but the values always seem to visually show roughly where they should be. Theoretically the Virb is "paired" with my GSC10 speed sensor (I know you don't actually pair them but when I spin the wheel by hand it registers on the Virb), so spikes like that would be unusual as it's not in my GC or Strava data as max speed for the ride.

Anyway I went back and created a new video using an old ride video, cropped it to the same section and the speed gauge showed the same as the previous one did (ie correct at a max of 200km/h), so it does appear that Virb Edit 2.9.1 is working ok, but really don't know where that odd data is coming from. The gauges still don't line up with the numeric values though.

Something I have noticed with the speed overlay since upgrading to 2.9.1.from 2.80 is the speed dial is now calibrated to a max speed of 800km/h where it used to be 200km/h (same as the cadence value still is). I have attached a screenshot of it (gauges on the right).



Something else that was an issue prior to 2.9.1 but is still an issue, the numerical values and the position of the needle in the gauge never seem to line up. Take a look at the cadence values on the left side of the screen shot (above). RPM showing 119 but the needle just above is way past 150, they never seem to be synchronised (119 is the correct value).

Speed is also the same, although with the current calibration, is difficult to see. Have attached a screen shot of previous Virb Edit version (below) showing speed gauge discrepancies, needle shows speed of approx 125km/h.

Thanks for reporting. We'll investigate.