VIRB Edit 3.3.2 is available

Thanks for the reply. It's a dual core Intel Pentium 3558U / 1.7 GHz CPU, but I am not sure what the graphics card is other than "Intel HD" with 1792mb video memory. Am I taking on too much for my computer to handle?

That is a very low-performance CPU, so I wouldn't expect wonders. I assume this is some sort of netbook / low-end laptop?

Did you get an error message for that crash?

Also, what is the resolution of the videos you are exporting? 1080p?

No error message, just that Virb Edit had stopped responding. I didn't realize it was such a low performance CPU, since I had just bought the PC within the last 4 months. It's a mini-PC so not a laptop, but serves a similar purpose, I guess I"ll need to upgrade if I expect to use this software.

We will keep working on our end as well to make things work better, it *should* work on the machine you have. But yes, if you're looking to do video editing I'd recommend something a bit beefier for the best experience.

Exporting transparent PNG

I've finally also tried this VERY useful feature (many, many thanks for implementing it back in V2.8!) when trying to combine hyperlapsed videos with overlays. Basically, it works when feeding FFMPEG with the video out of Microsofts Hyperlapse Pro and the PNG sequence originating from Virb Edit. This procedure very charmingly results into a stabilized video with Garmin's data, gauges and diagrams.

The gauges are indeed nice and look as expected, but the diagrams (e. g. height over time) are only present in the very first frame - all other frames are rendered without contents.

To make a long story short, please have a look at the attached image! The upper part is the first frame, the lower part is one of the following frames. The difference in the lower part is obvious as the diagram there is missing any contents.

I've tried different settings concerning quality and dimension when exporting (e. g. high, medium, low and 1080p and 480p) but it all results into the same missing diagrams, except for the very first frame which is filled with all information as expected.

Garmin: Is there anything I can do about it now or would you consider this a bug to be solved with the next release?

Just to put it straight: The diagrams already get save this strange way by Virb Edit, they are not generated by FFMPEG (which is only needed to overlay them with some other video file).

(But mind the diagram of the track (right upper corner)! This one gets perfectly rendered in every frame.)

When you play back the video in VIRB Edit does the error exist as well?

Does it exist in the exported video?

You're on the 3.3.2 Windows version?

Hello!

The error only occurs within the sequence of PNG files. The video itself is just fine and has got all the overlayed data as arranged with Virb Edit 3.3.2 (yes, the current version).

My workaround for displaying the height is to use another gauge, a running bar along the left or right side of the video's frame with a little triangle as a mark for the current height which comes close to sort of a "diagram".

Of course it would be fine, if the PNG sequence also included all kind of diagrams - as the exported videos do.

We've fixed the graph export for PNGs, will be in 3.4.

(By the way: This is the kind of result I am after when using Virb Edit's PNG sequences in combination with videos created by Microsoft Hyperlapse pro:

www.youtube.com/watch

As Virb Edit can't directly process those hyperlapse videos due to missing timing information (normally found in mp4 atoms of Garmin's video files), one has to walk an extra mile with the PNG sequence and doing the overlay work with FFMPEG.)

)

I am a new VIRB user. I tested it today and I'm having the same issue. I was wondering if you any further information.

I have 3 one hour video files and a single 3 hour GPX file. In the 2.xx Virb this worked - the overlays went from 1 to 2 to 3 hours of elapsed overlay data.

Now what happens is that at 1 hours it starts back over with data from hour 0, and same at 2 hours.

This is clearly a bug with the new Version 3.0 synchronization. :(