File naming and sequence

8.3 clearly isn't a limitation though - because the FIT file and the GPX files are already named with a long filename :)

No, it's not an actual limitation, but if you're used to using 8.3 filenames, you might not even consider something more rational like your suggestion that they name with the date. For example, I've been using Unix/Linux/OS X for decades, and ordinarily if I'm naming a file, I don't put whitespace in it so I don't have any problems using it from the command line (which I use a lot even on OS X). Only if I'm only going to use the file from double-click land will I put spaces in a filename. If you're used to 8.3, maybe you don't even think about it.

The other thing I wonder about is if the processor is having its hands full with recording video, since we have no idea what the hardware is. They don't do rational things like checkpoint video during recording so that you don't lose an entire clip if something goes wrong. (For a long time I only recorded in 1080p because I'd only lose up to 23 minutes that way.) They only write out the GPS tracks when you stop recording (you see the message), and they don't checkpoint them, either. Maybe they simply don't have the cycles to create a rational file name until video recording is stopped.

As a work around a filename-converter could be added to VIRB Edit, so when it imports clips it renames them to a date format (like a FIT).
If we ask FALAGAR nicely, we might tempt him to do this...:rolleyes:

I'd be happy with that... Naming it the same as the GPX file would be close enough for me.

Has there been taken any action to end this numbering chaos? :confused: I also stumbled upon it's effects and second the troubles you come accross having dozens of same named files around your hard drive(s). A consistent way of numbering would help such a lot.

The current firmware version is still the one from February 2015. :eek:

http://www8.garmin.com/support/download_details.jsp?id=6565

It would be great to have one more update to finally make the Virb Elite run as good as possible for those users who really like it - including me.

I have had multiple VIRB Elites (account of operational failures). Each of them started file names at 'VIRB0001' and incremented higher - never returning to VIRB0001.

Regardless of what the device calls the files I use my own naming conventions when I import them.