https://bugs.kde.org/show_bug.cgi?id=457421
--- Comment #2 from Alec McLane <amcl...@snet.net> --- Dear Maik, Thank you for the quick reply. I am sending links to a JPEG and MOV that were taken about 3 minutes apart in the same location, in a time zone 5 hours later than my current one. In Digikam the JPEG has the time 2:08 PM, which was correct in that time zone, while the MOV has the time 9:05 AM, which was the time in my current location. My assumption would be that GPS data shouldn't be used to modify times, since the time considered as the proper time when viewing images and videos should be the time of day they was taken locally, regardless of the time zone. While I don't understand fully how different devices register time stamps on files, it seems that in this case the JPEG and MOV files have the correct timestamp in the file properties, as they appear on disk, so I wouldn't see any need to adjust this. Anyway, thanks for looking into it. Here are the links: http://gofile.me/6Z828/3Xh4j2VeLhttp://gofile.me/6Z828/bdNENHL8i Alec McLane On Tuesday, August 2, 2022 at 04:24:47 PM EDT, Maik Qualmann <bugzilla_nore...@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=457421 Maik Qualmann <metzping...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO CC| |metzping...@gmail.com Status|REPORTED |NEEDSINFO --- Comment #1 from Maik Qualmann <metzping...@gmail.com> --- This is a long discussed problem. Depending on the camera model (iPhone, camera, Android), we evaluate the time zone stored in the video metadata in order to come very close to the actual result. Unfortunately, some set the time zone correctly, others not. he current result is based on a long series of tests by users who have provided us with video samples. We need an image and video sample to analyze the problem. Maik -- You are receiving this mail because: You are watching all bug changes.