Editing VIRB360 Videos -- so slow and stalls

Attempting to edit VIRB360 videos is an exercise in frustration and patience .. The Virb EDIT software simply stalls out at times .. It seems to be single threaded and will constantly sit at 99% CPU (on an 8 core machine -- meaning its just using 1 core) It will almost always be in R state -- meaning its doing something internally vs waiting on disk or network I/O which would be in U state

Simple things like trimming a few minutes off the front or rear of a video can take 5-10 minutes to completely while VIRB Edit is unresponsive. Opensnoop doesn't show any appreciable file activity during this time .. So its busy doing something internal.


During other times when it hangs it seems to want to spend a of time in /var/folders/sp/ which its carrying a tonne of .tmp files (about 900M at this moment) Really not a good place to do this as thats on the system drive .. It apparently ignores the settings for temporary storage which is typically some off board platters more suited for video editing . Moving them to a offboard drive via symbolic link sped things up .. but still not very optimal



It also rereads these files constantly .. sometimes hundreds of times in a minute .. sometimes stalling as it reads them over and over.


501 844 Garmin VIRB Edit 143 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework

501 844 Garmin VIRB Edit 143 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Resources

501 844 Garmin VIRB Edit 143 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Resources/Info.plist

501 844 Garmin VIRB Edit 143 /System/Library/CoreServices/SystemFolderLocalizations

501 844 Garmin VIRB Edit 143 /System/Library/CoreServices/SystemFolderLocalizations



In short, the user experience here is horrific .. I can literally edit a whole video in finalcut while I'm waiting for a trim left to execute in garmin VIRB edit.

  • Just got the new version installed Version 5.2.0 (170920.0945) It now seems to love to go back and re-read very old files which have nothing to do with a project .. Sitting here doing an import now and watching it (via opensnoop) go back and access files that are in my archive litterally from 2015 during its optimization process .. That said so far -- this new optimization process has taken 20 minutes so far on a 4.5 hour video import .. and its still at 1/13 with the CPU fans running and 2 out of 8 cores engaged ..



    2017 Sep 22 12:38:35 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:35 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:35 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:35 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:35 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:35 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:35 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/VIRB0161.MP4

    2017 Sep 22 12:38:36 501 6587 Garmin VIRB Edit 100 0x01000000 /Volumes/LaCie/2015 HotRocks Front_0060.MP4

    and so on --
  • So another new annoyance is the start up time .. the new Garmin VIrb EDIT wants to go out and access every file in its database .. every video file gets opened at least once ,, rather than stat() its actually doing an open() then close() which just chews up tonnes of time on hundreds of old files .. giving a start up time with a modest library like mine of about 4-5 minutes while it goes out and samples every video file out there.

    It also wants to "optimize clips for editing" every time you press "undo" in the editor, often leading to the spinning ball of death .. regardless of if you answer yes or no to the prompt.



  • Well another update and hopes that things will be better .. they are not .. they are worse than ever now ., I don't have to do anything now. Just load my clips, go into the timeline editor and walk away .. after a few hours Garmin VIRB edit will start the spinning ball of death.. becoming unusable .. Spindump shows a stack full of recursive calls to the same routines in the thread libraries ..

    this is unbelievably bad. I cant even edit recent footage at all.

    The spindump file is a whopping 12MB

    -rw-r--r-- 1 root wheel 12832382 Dec 6 11:11 /tmp/Garmin_VIRB_Edit_28854.spindump.txt