VIRB Edit 3.5.0 is available

Suggestion

Would it be possible for a new version, to handle a bit different with the G-Metrix data?
When I took a ride, the Map shows the whole track. Also the round-times and a lot of more stuff, related to the complete recording.
Now, you´ll cut the boring stuff away. The result is now a Map with a lot of missing parts and totally messed up times.

It would be great to add the videos with gmetrix, for a final data-result. Then "freeze" the data and begin to cut the film.
Currently you have to create an X-hour long movie with all the data, export and cut it to have a 2 minute movie.

Thanks Falagar!

Does this version resolve the ffmpeg audio sync issue with multiple clips?

Also the link is to the Mac version, for anyone wanting the Windows version, it's here: http://www8.garmin.com/support/download_details.jsp?id=6591

Cheers,
Brett

We believe that we did fix the issues that were causing videos with many clips to get out of sync slightly. We'd love to hear if it did indeed fix the issue for you.

Thanks alanebro82,

I can confirm that the sync issue is gone! :D however...

The audio quality now is very average. It sounds like it's clipped or running at a very low bitrate. I exported using High quality with FFMPEG as the decoder and encoder. Comparing the original audio to the exported audio it is very noticeable. I checked the details for both and the original is 128kbps/48kHz and the exported is 139kbps/44kHz, so that isn't consistent with the degradation I'm hearing.

Where previously I couldn't use this encoder due to the sync issue, I now can't use it due to the audio quality. Please let me know if you think there's something I should try to fix it.

Regards,
Brett

Thanks Falagar!

Does this version resolve the ffmpeg audio sync issue with multiple clips?

Also the link is to the Mac version, for anyone wanting the Windows version, it's here: http://www8.garmin.com/support/download_details.jsp?id=6591

Cheers,
Brett

Oops. Fixed it.

Thanks!

Would it be possible for a new version, to handle a bit different with the G-Metrix data?
When I took a ride, the Map shows the whole track. Also the round-times and a lot of more stuff, related to the complete recording.
Now, you´ll cut the boring stuff away. The result is now a Map with a lot of missing parts and totally messed up times.

It would be great to add the videos with gmetrix, for a final data-result. Then "freeze" the data and begin to cut the film.
Currently you have to create an X-hour long movie with all the data, export and cut it to have a 2 minute movie.

Hmm. What should happen is that the time/track start from a) the beginning of your first clip or b) whenever you set the activity start time. The track will then be drawn till where the last clip ends. We *should* be drawing a continuous track, and things like time and duration should be consistent as well.

It's entirely possible that something got broken along the way, I'll do some testing.

Thank you FALAGAR! Very much appreciated :)

I think it works if you only got a single clip. You can cut parts and the track/times are still fine. If you have several clips (15 Minutes parts) it doesn´t.

The latest version starts about 100 times faster :D

Maybe I figured it out a bit.
If you add one video an cut some parts out, it works exactly how you described it. The whole g-metrix are still available.
When the video is longer then 15 minutes, it will be cut in two. When deleting one of them, the map/time/ect. disappears for that. -> Understandable, but not always intended ;)
Using autorecording in motion, the video will also being cut and things like total distance don´t work anymore (reset to zero). If you delete a part, the gmetrix will also be deleted.
There is no relation between the metrix during one recording (which was splitted by 15 minutes or recording in motion).

Against that, cutting a circuit recording modifies the absolute time and current laptime, but not the Starting-/Endingpoint. With that, I´d be the fastest guy on the track :cool:

As a developer, I can absolutely follow why it is that way! But probably it can be improved a bit :)

Thanks for your investigation! We rewrote the way we handle G-Metrix to make it speedier and more extensible. This probably got broken along the way. It definitely used to work even for multiple clips. We should be able to get this fixed. Appreciate your help.

Droning noise on playback on version 3.5.0

Hello FALAGAR

I never had any problems with the older versions but when I recently updated to Version 3.5.0 (3/8/2016) I noticed that all of the videos processed by this version (include those without any g metrix) produces a droning background noise during playback.

Hope you can help me on this. Regards.