VIRB Edit 5.1.1 is now available

I expect there must be a further error message. This one blames the C Runtime called from C++ (I guess).
Now it would be interesting, why the call to urctbase.dll crashes. It should be in one or more previous logs.

But I am no VirbEdit developer. This is just a regular approach to find out which module causes the issue. In my case it was related to my graphics, which was quite obvious, because all logs contained "Intel", "Graphics" and similar things like that :)

You need to take a look into the EventLog and search for the error entry. Garmin cannot help you figuring this out, without further information.
Run: eventvwr
Navigate to Windows-Protokol -> Application.
There should be a red entry, level error, with the timestamp from your crash in Edit. (Reproduce it, to prevent searching)
The textbox below contains the data, which may refer on your graphics or something else.

This forum system won't let me paste it so others can see it.

I expect there must be a further error message. This one blames the C Runtime called from C++ (I guess).
Now it would be interesting, why the call to urctbase.dll crashes. It should be in one or more previous logs.

But I am no VirbEdit developer. This is just a regular approach to find out which module causes the issue. In my case it was related to my graphics, which was quite obvious, because all logs contained "Intel", "Graphics" and similar things like that :)

No other error logs available than this. I traced back all the way. It also crashed on my other pc, desktop.

I find it curious that Garmin pushes out VIRB Edit that seems to have many unresolved issues at the same time they implement new forum software that has even more issues than VIRB Edit.:mad:

Since I have not been able to copy & paste the details of the VIRB Edit crash here is a 'picture' of most of the dataciq.forums.garmin.com/.../1230372.jpg

Since I have tended to be negative on VIRB Edit updates - the processing time for EXPORT with 5.1.1 on my W10 Laptop is much improved over what I experienced with 4.2.3.

We are not in phatt city yet, however.

I have 2 VIRB Elites - one forward, one backward. In 'picture in picture' editing I cannot get both the A and B streams aligned.

Do I need to place in VIRB Edit the view whose camera I started first? Is their any way to manipulate which view gets the full screen and which view gets the inscreen view?

Wrong jump detection at exported video

Here another issue with the video export.

In the VIRB Edit GUI the activity for jump detection is set as skiing. During editing and video preview with the GUI the jumps are correctly detected for skiing (jump count, jump distance, duration). The activity type seems to be correctly saved in the file 'edited_movie.xml' with the key <ActivityType>1</ActivityType>.

However, when exporting the video to MP4 with VirbExport.exe, the jump detection is not set correctly, apparently it is set back to the default as biking. Apparently VirbExport.exe is not considering the activity type key in the movie project file.

Well, it might seem this is not such an important issue, but when the gauges show a total jump count of (for example) 47 instead of 3 for a 6-minute video, this is at least quite strange.

I noticed this issue at version 5.1.0 and hoped it would have been addressed at 5.1.1, but unfortunately not. Is there any plan for fixing it?
I have also reported it to the support, but did not really get an answer.

I am getting artifacts in the upper edge of the video after exporting my video.. Anyone else experiencing this?
I have tried all of the decoders, and it is also not possbile to go back to an older version and export the video from there.

Is there a fix for this?

Cheers,
Matiasciq.forums.garmin.com/.../1231741.jpg

In loading Edit 5.1.1 I noticed there is a step that involves interrogating and configuring the Graphics Card - will that insure that if 5.1.1 load successfully that it can be used successfully?



Loaded 5.1.1 to my Desktop. Still get the following when attempting to Export. Obviously with the 'set up' interrogating the Graphic card no 'Red Flags' are raised when mine is interrogated. If the Graphics Card is not 'up to snuff' for VIRB Edit's requirement, the install should be 'backed out' an the user given an error message that means something and is understandable to the 'non-geek'.

I found a solution to the crashing, hope this helps you: https://forums.garmin.com/forum/mac-windows-software/windows-software/virb-edit-aa/1230952-garmin-virb-edit-doesnt-work?p=1232103#post1232103

Still artifacts in version 5.1.2 :/