VIRB Edit 3.3.2 is available

Like Xxxzanka said: It is not usable version to export videos of 2-3 hours.

As i said in previous replies, in 3.1 versión my videos of 2-3 hours of road bike route, with speed, distance and map overlay, in 1080p - 50 fps, the export time is, aprox, 1% each 2 minutes. With this last version, same kind of routes's videos, with same overlay, 1080P - 50fps AND MEDIUM QUALITY as you said to me, it is now exporting ¡10% in 1 hour! Yes, medium quality is 'faster' than maximum quality, but is sloooooooooow sloooooow option too.

I will revert to 3.1 and i will not update until i see as a bug fixed in other futher version.

In 3.2 we switched our video encoding (used when exporting) to use ffmpeg instead of Media Foundation. That generally results in more reliable and better-looking output, but it might be a lot slower. Especially for systems with relatively powerful GPUs but relatively weak CPUs.

What we will do to address this is give users the option to choose the framework used for encoding (as well as decoding) in an upcoming release. Then you can choose which route you'd like to go.

I apologize for the inconvenience.

The combobox to select the G-Metrix source is a nice idea.
For my personal usage, I didn´t found a use case, yet. All Sensors can be connected with the Virb and my Vivoactive at the same time. But who knows :)

With that change, I cannot select the source of "Speed" anymore. I am connecting my Virb to an OBD II Adapter and have GPS and vehicle speed.
The "stock" gauges, which were added automatically are containing the GPS-Speed (I guess). From G-Metrix selection tab, I can only select the OBD-Speed.
In the previous version, there have been "Speed" and "Vehicle Speed" in the selection.

Is it possible to bring back both values or add "OBD" as a source in that option-field?
That would be great!

PS: How does the 3D speed work? Seems not to it on motorbike rides ;)

A 30min video export to MP4 (utilizing the lightest/fastest resolution settings) started yesterday at 3pm, was at 35% as of 11am today. That's about 1.5% per hour. I know some above posters mentioned slow exports, but is this expected behavior?

The combobox to select the G-Metrix source is a nice idea.
For my personal usage, I didn´t found a use case, yet. All Sensors can be connected with the Virb and my Vivoactive at the same time. But who knows :)

Well, as for my case, it's very useful due to the fact that the height sensor of Virb Elite is completely out of bounds: It gives values far off the true ones, even the tendency (going uphill or going downhill) is absolutely off reality. So I'm glad I can use the height sensor of an additionally available Garmin device, which records height data reliably.

All,
@Silvertrophy
The numbers you are seeing are pretty close to what we would expect. You will also observe that the performance difference between high and max is much larger than the difference between high and medium or medium and low.

Thank you very much for your reply! :)

The combobox to select the G-Metrix source is a nice idea.
For my personal usage, I didn´t found a use case, yet. All Sensors can be connected with the Virb and my Vivoactive at the same time. But who knows :)

With that change, I cannot select the source of "Speed" anymore. I am connecting my Virb to an OBD II Adapter and have GPS and vehicle speed.
The "stock" gauges, which were added automatically are containing the GPS-Speed (I guess). From G-Metrix selection tab, I can only select the OBD-Speed.
In the previous version, there have been "Speed" and "Vehicle Speed" in the selection.

Is it possible to bring back both values or add "OBD" as a source in that option-field?
That would be great!

PS: How does the 3D speed work? Seems not to it on motorbike rides ;)

3D speed takes elevation into account. But, VIRB X does not have a barometric altimeter, so altitude is quite noisy making 3D speed somewhat useless. But you might want to use it in case you are recording a sky-dive or something along those lines.

The point of adding this was to give users more flexibility, and allow them to choose if they want to use recorded speed (what the FIT file says how fast you were), 2D calculated (we calculate speed from position, might be useful in case the FIT speed is inaccurate for whatever reason) or 3D calculated (for events with fast changes of altitude).

Vehicle speed was renamed to OBD-II speed, it should still be the same thing.

Another thing we've changed is to fall back to different speeds if a specific one isn't available. There are automotive templates with OBD-II speed that would have been empty in 3.2, in 3.3 we will use recorded speed if OBD-II speed isn't available.

You should be able to pick which speed you want, but you don't select in the G-Metrix tab, but have to grab the correct gauge in the Overlays tab (filter under Gauges/Anzeigen > Speed/Geschwindigkeit).

A 30min video export to MP4 (utilizing the lightest/fastest resolution settings) started yesterday at 3pm, was at 35% as of 11am today. That's about 1.5% per hour. I know some above posters mentioned slow exports, but is this expected behavior?

That does seem very slow for a 30 minute video. May I ask what CPU(processor) and GPU(graphics card) your computer has?

Thanks for the reply. It's a dual core Intel Pentium 3558U / 1.7 GHz CPU, but I am not sure what the graphics card is other than "Intel HD" with 1792mb video memory. Am I taking on too much for my computer to handle?

Oh also, that 30min video got up to 89% complete and then crashed. That was after about 27 hours of processing I think.

You should be able to pick which speed you want, but you don't select in the G-Metrix tab, but have to grab the correct gauge in the Overlays tab (filter under Gauges/Anzeigen > Speed/Geschwindigkeit).

That´s what I need to know :)
Also, thank you for explaining 2D & 3D speed accurate. I was expecting something like that, but was astonished, that it differs so much. Knowing, that the X/XE doesn´t have a great altimeter, its clear now (I know that height measurement only by GPS is a mess. It´s not a critic :) ).

Sadly I cannot apply the barometric pressure (calculated height) via OBD II. This would be nice. (And other custom values like the current gear. But that´s another topic)

@Silvertrophy: Alright, that is indeed a use case! My watch doesn´t have a barometric sensor, either. But maybe my next one :)