VIRB Edit 5.1 Export Issues

Error Exporting Video in v. 5.1.0

This error just started occurring after upgrading to V 5.1.0. When I'm done editing and click Export, I see this:



Desktop
Dell Studio XPS running Windows 7 Pro 64 bit
9 GB RAM Intel Core i7 2.67 GB
AMD Radeon HD 5700 graphics card Driver v. 15.200.1062.1004

Error log attached

In shipping VIRB Edit processing into the Graphics Cards, is it Garmin's belief that user of one of the VIRB action cameras and thus VIRB Edit are into gaming and therefore have 'hot rod' graphics cards installed with processing power far beyond the standard graphics cards that are installed in the vast majority of computers?

If this is Garmin's assumption, then they are alienating a high number of users that are not into gaming and are using 'standard' equipped computers. Programs such as VIRB Edit need to work with the abilities of standard equipped computers - that is your customer base. I understand the geeks in development think everyone has equipped themselves with the latest 'hot rod' hardware that those individuals have equipped their own computers with - but that is not the case.

error log

Run starting at 6/21/2017 6:33:46 PM
6:33:46 PM Verbose [0C729690] BaseTimer_t::BaseTimer_t: duration: 16000000
6:33:46 PM Verbose [0C729690] RepeatingTimer_t::RepeatingTimer_t
6:33:46 PM Verbose [0C7294A0] BaseTimer_t::BaseTimer_t: duration: 16000000
6:33:46 PM Verbose [0C7294A0] RepeatingTimer_t::RepeatingTimer_t
6:34:28 PM Debug GetVideoInfo GetUuidInfo - Unable to read required atoms from mp4 file
6:34:28 PM Info **************Creating playback providers**************
6:34:28 PM Info VirbEdit Version: 5
6:34:28 PM Info Settings:
Width: 1280
Height: 720
FrameRate: 30000 / 1001
Quality: 1
Decoder:0
Encoder 0

6:34:28 PM Info Duration: 663.663
***Video***

Clip staring at 0
File: C:\Users\xxxxxxxx\AppData\Local\Garmin\VirbEdit\Preview\039a162b-6bfd-482d-9186-3f9bf2e60017.mp4
Start 0
End 663.663
Clip Duration 663.663
PlaybackSpeed 1
Volume 1
Has Widgets? Yes

**MF Metadata**
MF_MT_MAJOR_TYPE: MFMediaType_Audio
MF_MT_SUBTYPE: MFAudioFormat_AAC
MF_MT_AM_FORMAT_TYPE: FORMAT_WaveFormatEx
MF_MT_USER_DATA: 0 0 0 0 0 0 0 0 0 0 0 0 18 16 86 229 0
MF_MT_ALL_SAMPLES_INDEPENDENT: 1
MF_MT_FIXED_SIZE_SAMPLES: 1
MF_MT_SAMPLE_SIZE: 1
MF_MT_AAC_AUDIO_PROFILE_LEVEL_INDICATION : 0
MF_MT_AAC_PAYLOAD_TYPE : 0
MF_MT_AUDIO_AVG_BYTES_PER_SECOND: 15998
MF_MT_AUDIO_BITS_PER_SAMPLE: 16
MF_MT_AUDIO_BLOCK_ALIGNMENT: 1
MF_MT_AUDIO_NUM_CHANNELS: 2
MF_MT_AUDIO_PREFER_WAVEFORMATEX: 1
MF_MT_AUDIO_SAMPLES_PER_SECOND: 44100

MF_MT_MAJOR_TYPE: MFMediaType_Video
MF_MT_SUBTYPE: MFVideoFormat_H264
MF_MT_AM_FORMAT_TYPE: FORMAT_MPEG2Video
MF_MT_SAMPLE_SIZE: 1
MF_MT_AVG_BITRATE: 3072686
MF_MT_INTERLACE_MODE: 7
MF_MT_MPEG2_LEVEL: 31
MF_MT_MPEG2_PROFILE: 66
MF_MT_FRAME_RATE: 30000/1001
MF_MT_FRAME_SIZE: 1280/720
MF_MT_PIXEL_ASPECT_RATIO: 1/1

6:34:28 PM Info **************Creating playback providers**************

This looks like a playback log rather than export. Can you grab the logs at C:\Users\<user name>\AppData\Local\Temp\VirbExport\<VirbEdit version> ? The VirbEdit sub folder only has playback logs, all the export logs go to the VirbExport folder.

Can you grab the logs at C:\Users\<user name>\AppData\Local\Temp\VirbExport\<VirbEdit version> ? ...all the export logs go to the VirbExport folder.

I'm not seeing any VirbExport subfolder in that location. I just tried exporting a video and got the same failure message, but no VirbExport file.

The only VirbExport subfolder is under ...Local\Garmin\ but there are no logs there, only settings.

If I'm going to have to buy a new graphics card, how important is the 2Gb of memory? The Radeon 8570 card that Garmin recommends as a "minimum" only seems to come with 1Gb.

Issues with both playback and encode.

Hi Everyone,
Some users have reported export issues withe VIRB Edit 5.1 (lines/artifacts present in exported video, error prior to starting export, error when export progress reaches 100%, VIRB Edit crash when initiating export, etc). Unfortunately, very little information was provided along with these reports which doesn't help in their investigation. I'm creating this thread to ask users to provide relevant, specific information to help investigate these issues, in an overall effort to improve your VIRB Edit experience!

Would you please provide the following information?
- Turn on extra logging (and then reproduce the issue): Menu > About> check the Turn on extra logging checkbox.
- Send us export logs: These can be found at C:\Users\<user name>\AppData\Local\Temp\VirbExport\<VirbEdit version>. Make sure to get the logs from the VirbExport folder, not VirbEdit.
- List the resolution/fps/target quality setting at which the issue occurs.
- List the encoder/decoder combination.
- Machine specs, including RAM, video card model, driver SW date (to check if the driver is up to date), video driver RAM. Users can run dxdiag and send us the output in txt file format.
- Information regarding your clips (such as resolution/fps) would be helpful.

If you prefer, you can e-mail this to me through the forum (as opposed to posting this information in the forum).

Thanks in advance!

I have several problems with the Virb edit version 5.1.
The problems are related to playback and encoding. Let me describe what's going on.

I have a clip from a an original Virb camera. The clip is tall HD, 48 fps. In virb edit I added a gpx file which I took off on another gps unit (60csx) to the g-metrix of the video. I also added several gauges such as speed and track.

During playback the gauges do not update. They are stuck and never updating. I am using ffmpeg as both playback and encode. Although I have tried to switch the playback to DXVA with same result.

Now if I try to export the clip with ffmpeg encoder I am only getting 20% cpu utilization and the encode is slow. The quality target was set to high, 960p, 48 fps. In the previous version of Virb edit it would use all the cores. There was some strange line that appeared at the very top of the video.

My system setup is: Windows 7 Ultimate 64 bit. 8 core AMD FX 8320 CPU, 20 GB of ram. AMD 7850 GPU with latest drivers.

I have attached the screenshot of process explorer showing the threads running in the VirbExport.exe process. Both the encode and playback logs are also attached.

Brilliant, the form lost my long detailed reply.

A shortened version:

My issue is not an export issue, when importing from a Virb Elite the G-Metrics do not work when editing the video so the data is not imported properly. I have uploaded an entire SD card contents to Google Drive on support ID 9874259K0 - please try to reproduce with that data.

Other less serious issues:

I occasionally also get an "unable to export" error when trying to export but currently can't reproduce it. Despite the warning the video does in fact export correctly.
I also had an issue with no audio whilst editing - I can't reproduce this either.

Lastly I can't revert to a previous version of Virb Edit as I get into a failed app launch loop with dialogue flashing on my screen that is impossible to stop without a restart. It turns out that the dialogue is saying that a new version of virb edit is available, please use that.

I'm not seeing any VirbExport subfolder in that location

That most likely means the crash is occurring before export ever begins, which is good to know.

If I'm going to have to buy a new graphics card, how important is the 2Gb of memory?

That largely depends on what you intend to do. We try to set our minimum requirements such that your system will work if you use VirbEdit in the most taxing way possible. Virb 360 supports a 5.7K video mode. If you want to work with 5.7K videos, more is better. If you are mostly working with 1080p videos, 1GB is more than adequate. I have not seen out of memory issues with 1GB cards while working with 4K video either, but you are definitely getting close to the edge with 4K.

For reference, at 30 fps, 1 second of
5.7k uncompressed video = 2GB
4K uncompressed video = 1GB
1080p uncompressed video = 250MB