Virb Edit - Multiple problems

Latest version of Virb Edit, brand new computer (32 GB ram, SSD drive, Windows 7 64 bit).

I just got my Virb, and the camera is awesome. The main reason I bought the Virb is for the data overlays (Garmin Edge 810). Unfortunately while editing a single century ride, I've had constant issues that are ruining the experience.

The program crashes frequently (we're talking every 10 minutes of editing or so), and when I re-launch it often tells me that some clips are no longer available. When I try to browse to the clip, it tells me the clip does not match and won't let me import it.

After painstakingly syncing the GPS data to all the clips, if I edit a clip in the middle of the timeline then the GPS data on all subsequent clips does not remain in sync. It's a constant push-pull game that has me pulling my hair out.

When I go to sync GPS and zoom in, after panning and then click-dragging, the program wildly jumps and moves the map around so the point of interest is off-screen.

These are the main issues, but there are numerous other "minor" problems as well.

Like I said, I love the camera but this software is killing it for me. :(

0 NicoTR over 10 years ago

I am so unbelievably frustrated. Every time I try to edit a video--a process that should take 20 or 30 minutes given the simple editing tools available in Virb Edit--it takes hours upon hours. Every time the program crashes (often) or the red dot stop appearing on the GPS sync screen (also often), the program must be restarted. When the program restarts, all previous GPS syncs are lost! Do you know how frustrating this is when I have to go back and manually sync GPS to 30 clips, only to have it happen again, and again and again...

Is this program ever going to be fixed? Right now it's useless.

Same boat here, wasted time trying to create a video out of multiple clips :(

0 John_Stone over 10 years ago

So after a good night's sleep I felt like I was ready to make another attempt to complete the video I've been working on, oh, forever. I launched Virb Edit, and was reminded of yet another insidious bug: "The Clip is Missing. Would you like to locate it?". Um, nothing moved. So I click "Browse". Yep, there it is, right where it always was. I select the clip and get this message thrown at me: "The selected video does not match the missing video. Try again?" Yeah, it doesn't match because I EDITED IT. FOR A LONG TIME. So the only solution is to delete the missing clip, re-add it and then EDIT IT ALL OVER AGAIN.

This has happened quite a few times.

Seriously you guys, am I missing something here? This program is cruel joke.

0 Former Member over 10 years ago

Initially I had lots of trouble as well with sync and multiple clips, specially at long over 3 hours rides which also requires an exchange of battery. Syncing each individual clip with the same GPS seems stupid to me, but has to be done in virbedit as it is at the moment. Some time ago I started using GPSBabel, which has a filter to move the time stamps of the entire gps track.
The way I work now is to check for several clips in Virbedit what the delta in time is between the clip and the origial GPS track,this delta should be the same for all clips. In GPS Babel goto filtes and set the time difference.
You might also use the simplify option to reduce the number of track points to get rit of jumps in speed, %inlcine, %decline.
If you use the GPSBabel modified gpx track in virbedit, there is no need anymore to sync the clips, saves a lot of time and reduces possible crashes. Since 2.8.0 it runs stable at my PC.
I hope this might help you.
Video already posted in other thread.

www.youtube.com/watch

0 John_Stone over 10 years ago

ErivdBer, thanks for the information. I'll definitely give your suggestions a try and will report back here!

0 John_Stone over 10 years ago

ErivdBer, any thoughts on this error I'm getting? It's the stock FIT file straight from my Garmin Edge 810. Thanks.

0 Former Member over 10 years ago

So after a good night's sleep I felt like I was ready to make another attempt to complete the video I've been working on, oh, forever. I launched Virb Edit, and was reminded of yet another insidious bug: "The Clip is Missing. Would you like to locate it?". Um, nothing moved. So I click "Browse". Yep, there it is, right where it always was. I select the clip and get this message thrown at me: "The selected video does not match the missing video. Try again?" Yeah, it doesn't match because I EDITED IT. FOR A LONG TIME. So the only solution is to delete the missing clip, re-add it and then EDIT IT ALL OVER AGAIN.

This has happened quite a few times.

Seriously you guys, am I missing something here? This program is cruel joke.

We might be on to something here. Are you exporting the video to the same file that is an input into VIRB Edit? I can imagine all kinds of bad things happening in this case, and I worry we do not properly protect against that.

When you export, make sure it's always a new file (or at least doesn't overwrite a file that you use in this or a different video in VIRB Edit).

0 John_Stone over 10 years ago

No, of course not. I never even got close to the export phase. The missing clip errors mentioned above happen after the program crashes and has to be restarted, or if the program has to be restarted due to the missing red dot bug.

0 John_Stone over 10 years ago

I installed 2.9.1 this morning, and set about editing a short 40 mile ride video that I shot today. Every single one of the bugs mentioned in this thread remains. I will say that all the trouble starts once I begin to add the GPS files and sync them up (I waited until the video was otherwise completely edited to add the GPS data). Once the GPS data is imported and I begin the syncing progress, all hell breaks loose.

So I take it that A) The developers don't care, or B) They are simply unable to correct these app-killing bugs?

Which is it?

0 Former Member over 10 years ago

JohnStone,

I have no experience with FIT files I am using DAKOTA with only GPX output.
You might tick off waypoints and routes?
I had some errors in the past and the were gone by exporting to *.GDB, using mapsource to convert *.gdb to *.gpx

Hope this might help for you.