https://bugs.kde.org/show_bug.cgi?id=432369
--- Comment #6 from Thomas <filigra...@gmail.com> ---
My bad for being unclear, yes digikam shows it correctly.
I guess what bothers me is the fact that images and video are not treated the
same.
Created two test files, and the data is this:
======== IMG_20210201_182358.jpg
FileName : IMG_20210201_182358.jpg
FileModifyDate : 2021:02:01 18:29:53+01:00
ModifyDate : 2021:02:01 18:23:58
DateTimeOriginal : 2021:02:01 18:23:58
CreateDate : 2021:02:01 18:23:58
======== VID_20210201_182353.mp4
FileName : VID_20210201_182353.mp4
FileModifyDate : 2021:02:01 18:30:01+01:00
ModifyDate : 2021:02:01 17:23:53
CreateDate : 2021:02:01 17:23:53
2 image files read
And digikam shows them both correctly, the time is 18.23 just like the
filenames say.
But the metadata does not reflect this.
I don't like the fact that it adds 1 hour to the mp4, but not the jpg...
Especially when it is not consistent. If I use my Em10 it will not respect my
timezone and just use the createdate for my .mov files.
One file has this data, and with the above logic it should add 2hrs to it
(+1+DST):
FileName :
20200519_135904-VID-EM10_MkII.movFileModifyDate : 2020:05:19
13:59:04+02:00
ModifyDate : 2020:05:19 13:59:04
CreateDate : 2020:05:19 13:59:04
But it does not. It shows 13:59.
Makes handling files harder. I understand that it is to make the files show
correctly across devices, but a way to turn off the behavior would be nice,
when metadata is handled elsewhere. Or do all apps do it this way?
Now I have to keep track of how metadata is shown, wheter the file is from a
phone or a SLR etc.. I have plenty of devices from 2005 and forward, that seem
to use data in different ways.
I thought that if I set all dates to the taken date, image or video, device etc
doesn't matter, that it would show the date "By creation date" for everything.
Guess not. :(
--
You are receiving this mail because:
You are watching all bug changes.
