Virb Edit - Mac / Windows difference - Issues

Hello,
i've been using virb edit last version for a few days now, and have noticed something weird :
On windows :
- When i add the Speed gauge from the GPS recorded track, it's delayed, not exactly matching the video. Of course i can adjust but this got to be repetitive each time, when i make a video of several clips
- On mac, there's no issue related to that... any idea ?

Regarding edition, on both platforms, when i record a video based on "record only during move", i got lets say 5 clips. Trying to mount them all together, the G gauge, as well as Accel / Breaking, is only active for the very first clip. All consecutive clips will show a gauge to zero. I tried putting every single clip, and the software is able to read data (one by one). As soon as i put them all together while creating a new video, only the first one is showing some information.
All the other Gauge (Speed, Altimeter) are working fine all the way long.

I've noticed that on windows, only the first clip of all records (when triggered by a move) seem to have data readable. Whatever order i apply when creating the video, the first recorder video (even if located at the end) will show G data.
On Mac, all the clips are showing G Data separately, but when putting them together, only the first one (in the queue on the base line) has / shows the data from G Sensor.

I applied template as well as customized template, same issue. I do believe it's a bug in the way the software reads data and apply overlays --- any idea ?

Thanks a lot
  • Former Member
    0 Former Member over 10 years ago
    On Mac, all the clips are showing G Data separately, but when putting them together, only the first one (in the queue on the base line) has / shows the data from G Sensor.

    This is a known issue in 2.4 and should be fixed in our next release. There was also an issue with importing g-force data on the Windows side that has been fixed, although the behavior there was different.

    I've notified the PC team of possible differences in our default track offset behavior. Thanks for the heads up!