VIRB Edit 3.0.1 is available

In VirbEdit 3.0, videos not recorded with a Virb camera (Go Pro, cell phone etc) do not correctly pair with GPS data, so you will see freezing behavior for such videos. We've fixed this internally and it should work correctly in 3.1.

What videos and GPS data are you using? Is this from VIRB Elite?

If you have a way to share the video and GPS data I'd love to take a look.

In my case video is coming from a VIRB basic and the GPS data from a Edge Touring Plus. I can't get the video and the GPS to sync at all. When I tried to sync to the first turn about 20 seconds in the GPS was several seconds ahead, maybe as much as 20 seconds. When I tried syncing to a point in the middle of the video the gauges just stopped working and nothing I did would get the gauges or the GPS working.

I'm back on 2.9.2 now until this is confirmed fixed.

Could you share the video file and the Edge track with us? Maybe via Dropbox or OneDrive.

I'd be a lot more confident that we have this fixed if I can verify this with your data.

In VirbEdit 3.0, videos not recorded with a Virb camera (Go Pro, cell phone etc) do not correctly pair with GPS data, so you will see freezing behavior for such videos. We've fixed this internally and it should work correctly in 3.1.

That´s great! Thank you very much. I understand, that you cannot make any videotype working, which is not especially recorded from your devices.
But for me, that is really an amazing feature, to cut several videos (Virb & GoPro) together and lay the gauges on the top of it.

Thanks for confirming! I just wanted to make sure we fixed the right thing. As Purdington said, we have this fixed and it will roll out with 3.1.

Is it also possible to fix the Virb XE release date in germany so quickly? :rolleyes:

I´m looking forward to my next motorcycle racetrack event, next month (Nürburgring Nordschleife) and hopefully show you a nice result afterwards :)

One more remark; I downgraded from 3.0.1 to the previous version but now the video doesn't want to export anymore. Upgrading back to 3.0.1 doesn't solve this; it gives the same error. :(

Thanks!

We'd still like to do the map overlays, but it's complicated. I will make sure we revisit this as soon possible.
We do use the GPU (quite a lot actually), but do not use CUDA. We're never really quite done with export (both reliability and performance). So this is definitely a possibility.

I second that! CUDA rendering would be great, as it would help my computer render projects much faster. Even if my GFX card is quite older now (GTX275), I know for sure CUDA makes any video conversion much faster.
Also, like in many video editors, couldn't it be possible to render only transitions or overlayed parts? I mean, if my project has no effect and no overlay, the whole video is rendered anyway (at least on my set-up), whereas the different rushes could be simply 'concatened'. I don't know if it is valid for mp4/h264 though.
The fact is that the final rendered video is compressed and quality may be degraded.
Haven't tried to re-render with Virb Edit 3.

I too want the edited GPX file that used to export with 2.9.2
My use is I record a cycling video, then I use Virb Edit to crop the video (begining and end) to get the part of the ride I want.
Then export it, I now have a video and GPX file for the part of the ride I want, I then use Cycleops VitualTraining or KinoMap to create a new ride using my cropped video and synced cropped GPX file so I can make a virtual ride for my indoor biking turbo trainer/simulator 'KICKR'.
Please bring this option back I need it. I have rolled back to 2.92 as it does what I need!!!

No, this was a nice feature. e.g. when you make videos to reride them virtually on a smart trainer, it was nice to have a matching GPX file. Could you please add this again?

This is the same reason I would like it put back, also the main reason I bought a Virb

It already is in Windows 8.1, (I believe Windows 7 is the problem).

Which limit has been elevated?

2.9.2 has 2 limits:
1. 4GB limit to create OUTPUT file. It only appears on Windows 7. It does not appear on Windows 8.
2. 4GB limit to accept input file. This limit exists both in Windows 7 & 8

I learned it the hard way:
- I installed especially a fresh copy of Windows 8 for that
- my intention was to be able just to make one sync of the gpx file with the video
- therefore I combine the 3-4 mp4 files from my camera into one using external program
- I was quite surprised that Virb Edit didn't want to accept it (Imported 0/1 files...). It was clearly the size issue since if I remuxed the video with lower resolution (so that it is below 4GB) it was not accepted either.

Is the limit no. 2 waived now?