Issue
Garmin VIRB Edit Google Maps view in G-Metric data sync screen is not working. Instead of the map, the following error messages pop up.
Script Error
An error has occurred in the script on this page.
Error: Script error.
URL: https://maps.googleapis.com/maps/api/js?key=AIzaSyALG6yLmg2-yxayqbcZVVAolcIUzcX8eoc&sensor=false&v=3.12
You are using a browser that is not supported by the Google Maps JavaScript API. Please consider changing your browser.
Resolution
Garmin VIRB Edit software is discontinued and is no longer supported by Garmin. The issue occurs because VIRB Edit uses Internet Explorer based WebView to display Google Maps and this is no longer supported by Google.
The workaround is to make the following registry change to force Garmin VIRB Edit to use Microsoft Edge based WebView.
- Open Registry Editor (regedit.exe) and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION
- Create a new DWORD entry with the name VirbEdit.exe and HEX value of 00002ee1
- Restart Garmin VIRB Edit and you should be good to go.
May 2023
Windows 11 Pro (22H2)
Garmin VIRB Edit (5.4.3)
Não funcionou!
Alguem tem outra solução?
So the band-aid sudo-solution for me as of Oct 13, 2023 (since the prior workaround doesn't seem to work anymore):
1. Import the continuous gopro video segments.
2. Add same fit data to each video segment along with your gauge template. Click yes to all script error prompts.
3. Use g-matrix for 1st video segment. In the g-matrix adjustment screen, do not change the left side gopro video starting point (leave it as is which is at the beginning of the video segment). Only adjust the right side fit data slider to match the beginning of the video. This will set the *baseline additive amount of time value* for all of the subsequent video segments, so you'll want to verify and make sure it matches as close as possible. (Mine turned out to be 1:27 [1 min 27 sec] for the 1st segment.)
4. SUBTRACT 10 seconds from your *baseline additive amount of time value*. (So from my example, I take 1:27 and subtract 10 seconds, and value becomes 1:17)
5. Next, you'll see that each subsequent gopro video segment has a starting time in VIRB timeline. Mine was showing 11:47, 23:35, 35:23, 47:10, etc.
6. For each of these subsequent gopro video segments, edit g-matrix, add the value from step 4 (1:17) to each of the starting time and adjust only the right side fit data slider. (So my 2nd video segment would be adjusted to 13:04) [to be clear: 11:47 + 1:17 = 13:04]. My 3rd video segment would be adjusted to 24:02 [23:35 + 1:17 = 24:52], etc.
7. As you perform step 6, you might find that you can't adjust the slide to exact calculated value, since you can't use the arrows and have to rely on the slider. In this case, do your best to adjust to the closest number you can set to the calculated value (best fit seems to be just a little higher than the calculated value).
Good luck.
I'm getting the impression that emulating edge with FEATURE_BROWSER_EMULATION was a hack that got "fixed" by microsoft. The 12001 value is not listed in the documentation from microsoft, only up to 11000 for the last version of IE. Perhaps the issue that the ability to emulate Edge was removed from Windows?
Recently Virb Edit has showed a Maps API problem. I think this is caused by the ending of virb by garmin and Internet Explorer by Microsoft. Unfortunily i don't know if this problem have a viable solution. If anyone discover how to solute, will help us.
回避策の、次のレジストリ変更を行って、一旦解決しました。
しかし、最近（2023/8/19）に VIRB Edit を起動し、G-Metric データ同期画面に行ったところで、
再び スクリプトエラーが出て、Google マップ ビューが機能しなくなりました。
回避策の、次のレジストリ変更を正しく行っているにも関わらずです。
解決策をご教示いただけましたら幸いです。
thanks for that, weird that Garmin hasnt included this step in their installler
Thank you very much. It was a great help!