The longer "nothing" happens (No bugs were fixed, no requested features were introduced) something new will happen. It was the same with Virb 360 which definitely consumed a lot of development. And nothing happened for a long time for older devices.
Like all Garmin services: Let´s introduce new features, before fixing old issues ;)
5.3.1 reliably does what I want out of VIRB Edit - not taking a chance with 5.4.2
I can relate lol. 5.4.2 did remove the bitrate cap of 40mbr, but does take longer to export at highest settings because of the increased quality and less use of gpu.
Could you please elaborate on the less use of GPU by the 5.4.2? I been noticing a massive increase in CPU usage while a massive decrease of GPU usage while exporting in 5.4.2 while in the same system, the 5.2.0 uses 100% of GPU and barely any CPU.
Everything before 5.0 encoded on the cpu only. Great quality, but terrible speed. In 5.0, they introduced offloading to the gpu, which was much faster. But, they messed up the quality with the settings garmin was encoding with. So 5.0 to 5.4 had a bitrate limit of around 40mb, which is just way too low for 2.7K and 4K and resulted in poor quality. 5.4.2 increased the bitrate beyond 40mb for the "high" and "max" quality settings. The "medium" setting in 5.4.2 produces the same quality, around 40mbr, as "max" did in previous 5.0+ versions. To get better quality, garmin moved the encoding of the video back to the cpu, for "high" and "max". It is possible to get great quality with encoding on the gpu, but garmin hasn't figured that out yet.
So if you want speed and gpu use, you should select "low" or "medium" quality setting. "high" and "max" will give best quality but at a cost of speed. Garmin currently hasn't been able to get good quality while encoding on gpu and they think it's because the gpu. It really isn't. Gpu quality can be as good as cpu quality. It's just the gpu encoding requires a different set of parameters to get quality and I haven't been able to get garmin to understand this over many discussions and testing I have done with them.
Decoding can still utilize the gpu on any setting. So on "high" and "max" you can still see a little gpu utilization, but just for decoding, which takes the least amount of time.
Picture in picture: Currently you can select the G-metrix Source once for all. Edit -> PiP -> G-Metrix Source (Virb x & Virb xe).
Also, you can go to G-metrix and see all the available data, with it´s source. In earlier versions of VE, you could select the source. Now it only shows what you´ve selected in PiP (Virb xe). The x is not there. This is somewhere between a bug and a feature request, I guess.
Background: Two Virbs: XE records OBD II data. X is placed for better GPS, but on a gimbal, which makes G-Force and leaning angle useless. Now, I can choose between OBD II- & gyro data or working GPS with correct laptime.
It would be really nice to make that selection in the G-metrix tab possible, again :)
EDIT2: It also seems, that Edit is not capable of high RPM´s. My motorbike turns 16.000rpm. At about ~15.000 it falls down to something below 1000.
