VIRB Edit Software Version 2.3.2 Released

I still have the export issue with file szie > 4GB. I have recorded a 2h cross bike trip. Original 15,5 GB (1920x1080).
Do you believe this can be solved for Windows 7 users? What is the recommended recording format that will enable me to make these long vids?
Workaround 1: Converting the clips before importing to VE.
Workaround 2: Exporting all clips with gauge one by one, reimporting and merge with VE or other Video edit software?

We are looking into using a different framework for video export that doesn't have that limitation. But we are not sure when that might be.

So what you could do:

1. Upgrade to Windows 8.
2. Export smaller videos and use a different tool to stitch them together
3. Try exporting at the lowest resolution.
4. Try exporting with double or faster speed and make the video shorter that way.

I recognize that none of these options might be particularly appealing, and I apologize for that.

1: Using non-Virb videos (GoPro HD Hero 2) Did work before though, Can't afford to upgrade :(
2: Not running BitDefender but running AVG Free 2014 though

VIRB Edit is tailored to VIRB videos. Video is quite a complicated mess. Different codecs, different formats, etc. We test VIRB Edit with VIRB videos and trying very hard to make sure it works, making some assumptions about the format of the video. I am not entirely sure what changed between 2.2 and 2.3 that would have broken this, but it certainly was not intentional.

I realize that this is probably not what you want to hear, but we have to use our limited resources as best as we can. Making sure that Garmin customers who bought our hardware can successfully use our software takes priority. Once we get a bit farther along with VIRB Edit feature-wise and stability-wise we will try to make VIRB Edit a bit more video-format agnostic. I mentioned in a different post that we might start using a different framework for exporting, that *might* fix this issue as well, but it's really too early to tell.

My apologies.

One work-around that I have seen is to mute the audio. Go to the edit tab for each clip and set the volume to 0. Then try exporting again. Some of the logs of failed exports from non-VIRB videos suggest that export fails for the audio, so if you mute the sound it *might* work.

.....

I realize that this is probably not what you want to hear, but we have to use our limited resources as best as we can. Making sure that Garmin customers who bought our hardware can successfully use our software takes priority. Once we get a bit farther along with VIRB Edit feature-wise and stability-wise we will try to make VIRB Edit a bit more video-format agnostic. I mentioned in a different post that we might start using a different framework for exporting, that *might* fix this issue as well, but it's really too early to tell.

My apologies.

One work-around that I have seen is to mute the audio. Go to the edit tab for each clip and set the volume to 0. Then try exporting again. Some of the logs of failed exports from non-VIRB videos suggest that export fails for the audio, so if you mute the sound it *might* work.

First of all no apologies needed in regards to not working with other cameras/video sources just yet, I totally understand making sure the editor works with your own products first.

thanks for the audio tip as that seems to have solved my problem. I've just exported a 3min test without problems after putting the volume to 0. Now testing with a 23min video which appears to be exporting, just a warning about the 4Gb file size popping up but its still EXPORTING.

BOOM baby!
You've made this Bee a happy bunny :)

I can confirm the solution of setting volume to 0 for the NON-VIRB clips.
I've succeeded exporting clips without overlay. (will test with overlay later)
PowerDirectorPro 11.0:
1280x720 25fps
1280x720 30fps
AnyVideoConverter:
1280x720 x264 25fps
1280x720 x264 29.97fps
1280x720 x264 30fps
Setting the codec to xvid or mpeg4 and the video won't load.

This version works well on my win7 home premium pc.

What i would like to is speedometer not so crazy moving upp and down. 9km/h one second and 23 km/h next second when speed is really steady around 16km/h.

Look here to understand my point. http://m.youtube.com/watch?v=9hI8zZuYyP8

If virb camera itself now got support for ant powermeter i am 100% happy with product :)

There isn't much we can do about the speed on VIRB Edit's side of the equation. We could try to smooth out the speeds and take out any spikes, but that's always error-prone as well. That's assuming the track reports the data that you are seeing in the video.

If you look at the track in BaseCamp does it also have these crazy speeds? If it's smooth in BaseCamp then we are doing something wrong in VIRB Edit.

I apologize for the trouble.

So with 2.3.2 you cannot even play the clips in VIRB Edit? And 2.2.5 does play the clips?

Double-check you have the latest graphics card drivers. We are looking into playback issues currently.

This seems to be more peculiar. I installed Virb Edit on a new Fujitsu Laptop, running W8 prof.
Same result in addition to Runtime error. The "run as admin" didn't make difference.
More strange: It imported some Clips from my cellphone and played them With no protest.
Could it be the video files themselves causing the trouble? What about the memory Cards?

The files from my cellphone was already in my computer when I installed the Virb Edit.

Thank you for providing more information.

I would wager the clips from your cell phone are probably smaller (file size wise, resolution wise, bit-rate wise), so that your machine plays them fine.

VIRB videos are usually pretty large and we are seeing these playback issues caused by performance bottlenecks with some hardware. Laptops or older machines with weak or no dedicated graphics cards seem to have the most trouble.

Or the mobile videos use a different codec that your PC is happy with.

Could you tell me the exact model of that laptop, so I can look up the specs? And is that Windows 8, or Windows 8.1?

Crashed the app last night on a large 720P, combined 57min and 28min segments video. Couldn't complete it, lost 4 hours of encoding time :(

Reran in two segments. Total of the finished outputs are 5.3GB.

Would be really good to solve the 4GB barrier instability.