VIRB Edit 3.3.0 Beta available

We are happy to announce that VIRB Edit 3.3.0 Beta is available.

You can download it at http://static.garmin.com/desktop-chandler/virbedit/installers/GarminVIRBEdit_3.3.0.0.dmg.

This version upgrades your database, so any changes you make in 3.3 will not be visible in 3.2. That means that you can try it out without risking your 3.2 data, because you can always roll back.

Please give it a try, we are mostly interested in your playback and export experience. We really appreciate your feedback.

This is the change list:

Added support for merging G-Metrix data from different sources (like adding cadence from an Edge to VIRB X acceleration).
Added support for choosing between FIT speed, calculated 2D and 3D speed.
Added elevation data to GPX export.
Added support for photo and video library existing on different physical storage devices.
Re-added time display to G-Metrix Sync and Activity Start Time pages.
Improved reliability and performance for displaying G-Metrix.
Improved usability and reliability of Garmin Connect integration.
Improved speed of loading G-Metrix templates.
Improved El Capitan support.
Improved performance.
Fixed various bugs.
  • Are all of the new extra decimal places in the gauges intentional? There's really not much point measuring cadence or heart rate in tenths.
  • Oh, and the elevation plot I like to use isn't working:


    This is with OS X 10.11.
  • Thanks for letting us know.

    The extra decimal places are not intentional. We'll get that ironed out.

    Does the elevation graph ever work for you? Or is it flat on every video?
  • Elevation data doesn't show on the graph on any of the videos I've checked. It does show in the separate elevation gauge (the simple numerical one) that I sometimes also use, so it's the graph that's screwed up.

    Edit: OK, I found one where the graph looks normal. So I checked more of them, and of the 14 videos I made in October where I still have the video/data in VIRB Edit, 3 have normal looking elevation plots. Most of them are using data from my Edge 800, only a couple are using the data from the VIRB (where the starting elevation was close enough to being right that it was usable).
  • Elevation data doesn't show on the graph on any of the videos I've checked. It does show in the separate elevation gauge (the simple numerical one) that I sometimes also use, so it's the graph that's screwed up.

    Edit: OK, I found one where the graph looks normal. So I checked more of them, and of the 14 videos I made in October where I still have the video/data in VIRB Edit, 3 have normal looking elevation plots. Most of them are using data from my Edge 800, only a couple are using the data from the VIRB (where the starting elevation was close enough to being right that it was usable).


    I think I tracked down what's happening. It looks like it's an issue with the video starting before the data does. Just to confirm this will fix the issue you're seeing, if you re-sync the file so the data starts before the video, does the elevation graph appear for you?
  • OK, I'll try that. My usual sequence is to start the video on the VIRB first, and then hit the "start" button on my Edge 800 as I set out, so that's almost certainly the problem. Should just trimming off the video before the start of the Edge track work? I'll edit this when I get a chance to try (probably tonight).

    Edit: OK, it worked (sort of). I chose a 2 hour video (720@60fps), trimmed the first 10 s off so that the video started after the data, and sure enough, the elevation graph returned. However, it's showing a per clip elevation graph rather than an entire video elevation graph as it usually does. I won't worry about it, since I assume once you fix the problem it will start working as it did in the past.
  • Should just trimming off the video before the start of the Edge track work?


    I use your usual sequence too (w/Edge 1000), and trimming the video segment prior to the Edge track fixed it for me.
  • I found a very quick way to exit the application: loaded a day's worth of videos and pictures. Wanted to see the pictures only so I used the gear to enable that display, then looked at the first picture, then clicked the next button under the picture on the left side, then clicked Next a second time and poof, it was gone.

    Restarted 3.3.0, did the same steps again and the same thing happened again, the screen disappeared instantly and an error report popped up.

    Sure wish VE was that quick the rest of the time. It's still as slow as molasses to import video into.

    The failure generated an Apple report, the contents of which I copied to a text file. Is it of any use to the developers?
  • Thanks for the report. That crash will be fixed in the next release.
  • Overlay still not working

    I see the data overlay is still not working, in any of the versions I am able to download for Mac, just stays paused

    Any idea when this will be fixed, it was the sole reason I bought the camera, if unable to resolve I would need to return it