https://bugs.kde.org/show_bug.cgi?id=432369
--- Comment #3 from Thomas <filigra...@gmail.com> --- (In reply to Maik Qualmann from comment #1) > Well, I think the time the digiKam recognizes will be correct based on the > local time. > When we added reading video metadata, users provided us with a large number > of videos from various devices. Including documentation of when the video > was recorded, what digiKam is currently displaying and what users expect. > Unfortunately, the manufacturers of the devices store the video metadata for > time information differently. Some in local time, others in UTC with no time > zone, others with time zone, etc. > If we recognize an Android or Apple device based on the metadata, we assume > that the time in UTC and the time zones are correct and convert them. The > video files should be sorted in the time history together with the images in > the correct order. This was very important to the users. We should even add > the running time of the video, but we did not implement this because it is > not the standard for cameras and long exposure either. > > Maik If that was the case, then all my videos would be off since 90% are from the same time zone, only DST changes. The images as well. And, if the time was using the TZ of the filemodifydate, then all videos should be off, and all images as well? Not just the mp4s? What fields in an mp4 does it rely on? I should be able to find that data in the file, shouldn't I? I will try to reproduce it with a new file and report back, both my Huawei P20 and the wifes Sony XZ2C show the same issues. My E-m10 Mk II seems correct, but it records mov files. -- You are receiving this mail because: You are watching all bug changes.
