Video file dates are always 1-1-1970, and sometimes mp4 is corrupt
Posted: Thu Jun 28, 2018 5:08 pm
When my Windows computer imports videos taken by my H501SS the file dates are almost always 1-1-1970, with the file times being sometime after midnite. For instance, the time in one of my videos taken yesterday was 12:14 AM, or in other words, the video button was pushed 14 minutes after the drone was powered up.
Except for two videos taken today, which had no date/time of creation, and were unreadable. Which was very annoying as I was putting the drone through its paces and was hoping to post some of its antics here.
As a software developer I happen to know that 1-1-1970 00:00 is the default date/time in some computer systems (rather primitive ones, I am sorry to say), and unless a chip (such as an EEPROM, NVPROM or flash memory) in a system holds certain data such as the date/time between power-ups, one has to reset the date and time each time you start it up. Since the H501SS is not holding a date/time in memory, I am assuming that it must not have any non-volatile memory, or there is something wrong with my drone's system. So how do you set the correct date and time on this drone? And is it truly not possible to maintain date and time?
I don't know why the two videos taken today are unreadable, but compared with the other videos I've made so far, these two were over 1 GB in size, whereas all the others were less than 1 GB. Is that a factor?
Also, the file names are rather odd. They come out like this: hubsan_record_197011_8140.mp4. Obviously, the 1-1-1970 is being encoded in the file name -- but the usual way to do this would be to supply leading zeroes for numerals less than 10, e.g. hubsan_record_19700101_8140.mp4. So they're all like this, "hubsan_record_197011_xxxx", with the last four digits seeming to be a randomly-generated four digit number.
I would have expected an item of modern electronics like this to have modern firmware characteristics, so this is very surprising.
Except for two videos taken today, which had no date/time of creation, and were unreadable. Which was very annoying as I was putting the drone through its paces and was hoping to post some of its antics here.
As a software developer I happen to know that 1-1-1970 00:00 is the default date/time in some computer systems (rather primitive ones, I am sorry to say), and unless a chip (such as an EEPROM, NVPROM or flash memory) in a system holds certain data such as the date/time between power-ups, one has to reset the date and time each time you start it up. Since the H501SS is not holding a date/time in memory, I am assuming that it must not have any non-volatile memory, or there is something wrong with my drone's system. So how do you set the correct date and time on this drone? And is it truly not possible to maintain date and time?
I don't know why the two videos taken today are unreadable, but compared with the other videos I've made so far, these two were over 1 GB in size, whereas all the others were less than 1 GB. Is that a factor?
Also, the file names are rather odd. They come out like this: hubsan_record_197011_8140.mp4. Obviously, the 1-1-1970 is being encoded in the file name -- but the usual way to do this would be to supply leading zeroes for numerals less than 10, e.g. hubsan_record_19700101_8140.mp4. So they're all like this, "hubsan_record_197011_xxxx", with the last four digits seeming to be a randomly-generated four digit number.
I would have expected an item of modern electronics like this to have modern firmware characteristics, so this is very surprising.