![]() I may check that soon and, as I indicated, I'm not surprised by the answer since I did notice that metadata is not displayed and implicitly noticed that the time that is used cannot possibly be related to metadata. Some mp4 files are listed by the wrong time, aparently file status change time.Īll files are listed by meta data creation time or at worst, file modification time. Of course metadata is far better than either. One note, actually modifying the file (with touch) changes both the status time and the modification time, whereas copying the file with cp -a only changes the status time, so modification time is better. I'll try to have a look at 3.0.0 ( I have a buggy windows version of it installed in windows) and see if it's doing the same thing. The only field that I found that matches the wrong date is thus the status change time, but that has the wrong date for both files, so I probably haven't fully tracked down what digikam is doing here. So everything that I have found so far looks basically the same.īut digikam says that file b has the correct date of name a.mp4 -printf "Access time: %a \nStatus change time: %c\nModification time: %t\n"Īccess time: Sat Mar 2 01:05:34.0000000000 2013 ![]() ![]() Relevant part of exif data for a.mp4, from exiftool:įile Modification Date/Time : 2012:12:10 08:46:12 09:00įile Modification Date/Time : 2012:12:05 19:45:20 09:00ĭigikam shows file a.mp4's date correctly but shows b.mp4 as march 12 2013įind. Also they show no exif information (probably because digikam uses exiv2 where exiftool is needed for mp4 files), so I would not expect very good date interpretation based on that. They are listed by digikam as having dates many months apart even though their file modification times and exif dates are correct. I have a few mp4 files taken on the same camera a a few days apart. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |