Discontinuous distance/duration over clip transition

I took my VIRB Elite out today on a mountain bike ride since I had upgraded it to 3.7 and wanted to try it out. Video mode 1080p@30fps, UltraZoom with lens correction and stabilization on. The VIRB performed flawlessly. I got a low battery warning at about 1 hour 45 minutes but it continued running until I turned it off at 1:54:58.

So I got it home, imported the video into VIRB Edit 2.4, and put the 5 clips together into a project. My custom template includes the distance and duration counters (you need a transparent duration counter, by the way). The problem is that at the transition from the first to second clip, both distance and duration reset to zero. I've seen this before when I've had trouble with the VIRB (freezes) even if the transition occurred before the freeze, but I've never seen it for a continuous video that was recorded successfully. Clearly this is a problem with VIRB Edit 2.4, so I'm going to keep this video and the GPS tracks around until 2.5 comes out, but I just wanted to report the problem. I don't know why it should do that, especially since distance/duration is fine at all of the other clip transitions.
  • This saw some significant fixes in both 2.5.x and 2.6.0. Are there still issues with this in 2.6.0?
  • I haven't seen this particular bug in a while. The last video I did (with 2.6.0) had two continuous clips at the beginning and the transition was seamless. 2.6.0 has brought a more serious alignment bug, with replacement tracks, though.
  • I do have this problem still in 2.7.0
    Pretty reproducible if the video takes multiple hours...
    I guess its a bug in Virb Edit and not something that can be fixed by editing the GPX file?
  • Did you power down your VIRB while recording these long videos?

    We require that your VIRB remain on between your different videos at the moment. Otherwise we'd have to make up the distance data between clips.
  • You have to power down a VIRB after about 2 hours of recording, since the low battery warnings start about then. Ordinarily, there is no distance between clips: stop the bike, stop the camera, swap the batteries, start the camera, start the bike. What I do now is to use the track from my Edge 800, and then distance is continuous and duration is reasonable (counts the time I'm stopped, but that's fine). What with ANT+ drops and the ridiculous altitudes, you can rarely actually use the track from the VIRB Elite itself, anyway, which is a shame. It'd be nice if those were fixed. But it would also be nice for longer videos if we could just arbitrarily set the distance and duration counters at the beginning of a clip to whatever we choose, or even better tell it to "pick up continuously from the previous clip".
  • no, it was on continuously - powered through USB.
    The drop out in those videos doesn't just happen after a few hours - but if I take a clip of lets say 2 hours, I can be pretty sure that it drops out 1-2 times in between.
  • just checking one of my recent videos: duration is 3:37:35, drops are at 24:12 and 1:23:50.
    I'll try the new firmware in the next days and see if it fixes it... (hope it fixes also the external mic issue...)
  • just tested the 3.9 firmware: video is 39:24 - 2 files, drop out at 23:56, end of first file - so the new firmware didn't fix it.
  • FKEHREN:

    Is your VIRB Elite recording both FIT and GPX files? The setting you'd want to check is GPS > On, rather than GPS > When Recording or (unlikely) GPS > Off. If you're only recording GPS while recording video, then we don't have a way to track cumulative stats between movie files.

    Another possibility is that your device may be producing multiple FIT files per power session, which would confuse things for us at the moment. Checking that would require you recording for a lengthy time and then checking how many new FIT files show up in the device's Garmin/Activity/ folder when it's mounted on your computer, checking the time stamps to see what actually has been created since you last turned on your VIRB Elite.

    Obviously the second possibility's a bit more of a pain to check for. I recommend checking that GPS recording setting first.