Virb Edit 3.1.0.2 crashing

Former Member
Former Member
Trying to assemble long Virb X video. More than 5h.
Got 2 installations.
Application crashing every 10-15 min when trying to put telemetry data on overlay

I've attached error message from desktop high-end video editing workstation below.

BTW seems that software do not hardly use any resources - CPU, RAM, disk, GPU's are standing still while software hardly performing tasks.

Seems that CUDA GPU Acceleration also is not integrated.

Trying to figure out more professional solution.

Virb Edit has very good UI/UX interface, but it has been created for short, low data intensity projects.

App: VIRB Edit
At: 8/30/2015 9:16:26 PM (UTC2)
OS: Windows 8 (64-bit)
Processor: x86, Processor Level: 6, Processors:6, Model: 63 Stepping: 2, RAM: 16670160
TELEMETRY.READANDPROCESSTELEMETRYFROMFILES-1694-3.1.0.2
External component has thrown an exception.
at telemetry.ReadAndProcessTelemetryFromFiles(unique_ptr<telemetry::Telemetry_t\,std::default_delete<telemetry::Telemetry_t> >* , list<std::pair<std::basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >\,std::basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> > >\,std::allocator<std::pair<std::basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >\,std::basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> > > > >* , optional<exif::DataReaderIntf_t const \&>* )
at VirbShared.TelemetryUtilities_t.ReadAndProcessTelemetryFromFiles(KeyValuePair`2[] aPathNamePairs)
at Virb.Service.Telemetry.TrackManagementService_t.LoadTelemetry(IDictionary`2 aMedia, CancellationToken aCancellationToken)
at Virb.ViewModel.EditViewModel_t.<>c__DisplayClass23.<UpdateTelemetry>b__20()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Virb.ViewModel.EditViewModel_t.<UpdateTelemetry>d__25.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Virb.ViewModel.EditViewModel_t.<<Initialize>b__0>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
Available Video Cards:
Name: NVIDIA GeForce GTX 780
Card Driver Version: 9.18.13.5306
Name: NVIDIA GeForce GTX 780
Card Driver Version: 9.18.13.5306

.NET Versions:
.NET FW 1.0 not installed.
.NET FW 1.1 not installed.
.NET FW 2.0 with SP2 installed
.NET FW 3.0 with SP2 installed
.NET FW 3.5 with SP1 installed
  • Former Member
    0 Former Member over 10 years ago
    I am facing similar problem (on Win8). In my case the video is much much smaller (22min). When I start adding overlays or scrolling through the various gauges, the whole program freezes (after only a few seconds). Task manager does not show any huge resource usage (13% CPU). It is worth noting that as far as Windows understands the program does not crash (there is no "not responding" messages), it simply freezes.

    This is reproducible every single time. I wish I could try a previous version, because for now the program is completely unusable for me.
  • Former Member
    0 Former Member over 10 years ago
    I am facing similar problem (on Win8). In my case the video is much much smaller (22min). When I start adding overlays or scrolling through the various gauges, the whole program freezes (after only a few seconds). Task manager does not show any huge resource usage (13% CPU). It is worth noting that as far as Windows understands the program does not crash (there is no "not responding" messages), it simply freezes.

    This is reproducible every single time. I wish I could try a previous version, because for now the program is completely unusable for me.


    Since there are no simple solution from Garmin nor community, I've switched to MAC version.
    At least not crashing :)