Simply put the date inside digikam is not the "date taken"!
Hi, Which file format didi you use ? Which camera model did you use ? Did you import files using camera import tool from digiKam ? If yes, take a look to these settings : https://docs.digikam.org/en/setup_application/camera_settings.html#customize-the-behavior Also check well how metadata are taken from XMP side car (if you use it) with these settings: https://docs.digikam.org/en/setup_application/metadata_settings.html#sidecars-settings Gilles Caulier
Created attachment 166762 [details] attachment-1243963-0.html "Did you import files using camera import tool from digiKam ? " No, was I meant to? On Sat, 9 Mar 2024 at 16:35, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=482944 > > caulier.gilles@gmail.com changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > Severity|grave |normal > > --- Comment #1 from caulier.gilles@gmail.com --- > Hi, > > Which file format didi you use ? > > Which camera model did you use ? > > Did you import files using camera import tool from digiKam ? If yes, take a > look to these settings : > > > https://docs.digikam.org/en/setup_application/camera_settings.html#customize-the-behavior > > Also check well how metadata are taken from XMP side car (if you use it) > with > these settings: > > > https://docs.digikam.org/en/setup_application/metadata_settings.html#sidecars-settings > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug.
(In reply to mlh.kiwi from comment #2) The camera model was the samsung WB 700. And it did have a date created tag know as date taken which can be seen in the default windows properties
(In reply to caulier.gilles from comment #1) > Hi, > > Which file format didi you use ? > > Which camera model did you use ? > > Did you import files using camera import tool from digiKam ? If yes, take a > look to these settings : > > https://docs.digikam.org/en/setup_application/camera_settings.html#customize- > the-behavior > > Also check well how metadata are taken from XMP side car (if you use it) > with these settings: > > https://docs.digikam.org/en/setup_application/metadata_settings. > html#sidecars-settings > > Gilles Caulier file format was JPG
"Did you import files using camera import tool from digiKam ? " No, was I meant to? Well, you import files directly as collections. So respond to others Q... Gilles Caulier
Created attachment 166763 [details] attachment-1245327-0.html I did import yes as a folder I think. On Sat, 9 Mar 2024 at 16:40, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=482944 > > --- Comment #5 from caulier.gilles@gmail.com --- > "Did you import files using camera import tool from digiKam ? > " No, was I meant to? > > Well, you import files directly as collections. So respond to others Q... > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug.
How could this happen some of the photos are sorted properly others have completely false dates despite there being an original date.
I notice the make and model of the camera is also reported as unavailable?
(In reply to caulier.gilles from comment #5) > "Did you import files using camera import tool from digiKam ? > " No, was I meant to? > > Well, you import files directly as collections. So respond to others Q... > > Gilles Caulier I have responded to all your Q please help, otherwise this digiKam is unusable
And about the XMP sidecar usage ? I suspect that the metadata parser (Exiv2 library used in background) do not like well your files from your camera. You can try to use ExifTool backend instead but it's not guaranty. https://docs.digikam.org/en/setup_application/metadata_settings.html#behavior-settings Gilles caulier
Read also this entry: https://bugs.kde.org/show_bug.cgi?id=384086 And please provide a JPEg file samples to test here. Use a Cloud web-service. Gilles Caulier
Created attachment 166770 [details] attachment-1254681-0.html sample JPG: I know where the fake date is from. It is the modified date. But this should not be used as there is a date and time orginal On Sat, 9 Mar 2024 at 17:06, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=482944 > > --- Comment #11 from caulier.gilles@gmail.com --- > Read also this entry: > > https://bugs.kde.org/show_bug.cgi?id=384086 > > And please provide a JPEg file samples to test here. Use a Cloud > web-service. > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug.
(In reply to caulier.gilles from comment #11) > Read also this entry: > > https://bugs.kde.org/show_bug.cgi?id=384086 > > And please provide a JPEg file samples to test here. Use a Cloud > web-service. > > Gilles Caulier https://drive.google.com/file/d/1YMMDJEYidw72mDfNv7zIxj9ULrEiWqxS/view?usp=sharing
No problem here with a mac M1. no special settings. https://imgur.com/a/rB1Cr9x
(In reply to caulier.gilles from comment #14) > No problem here with a mac M1. no special settings. > > https://imgur.com/a/rB1Cr9x where was it sorted to? What does the date say?
(In reply to mlh.kiwi from comment #15) > (In reply to caulier.gilles from comment #14) > > No problem here with a mac M1. no special settings. > > > > https://imgur.com/a/rB1Cr9x > > where was it sorted to? What does the date say? I can see in the screenshot it was sorted correctly
Can you take a screen capture of the dysfunction under Windows ?
Created attachment 166772 [details] attachment-1257830-0.html https://drive.google.com/file/d/16HYGvAO0HgZ_sS2RKoqQvVR8CGTVUpMs/view?usp=sharing On Sat, 9 Mar 2024 at 17:30, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=482944 > > --- Comment #17 from caulier.gilles@gmail.com --- > Can you take a screen capture of the dysfunction under Windows ? > > -- > You are receiving this mail because: > You reported the bug.
(In reply to caulier.gilles from comment #17) > Can you take a screen capture of the dysfunction under Windows ? I have shared the link to that it
If the camera information is also shown as "unavailable", then the metadata has not been read from the image. This problem has been reported by users from time to time. We suspect a blockage if the images were opened in other programs during the first scan or antivirus programs. Add digiKam and Exiftool in the digiKam folder as an exception to the AntiVirus program. Perform a simple re-read of the metadata from the image to the database, either via the album or item menu. This will solve the problem for the images. Maik
can you try with the 8.3.0 pre-rellease available here : https://files.kde.org/digikam/ Note : the database contents must be sync with the file metadata. Use Tools/Maintenance/Sync Metadata and Database to do it https://docs.digikam.org/en/maintenance_tools/maintenance_metadata.html
(In reply to caulier.gilles from comment #21) > can you try with the 8.3.0 pre-rellease available here : > > https://files.kde.org/digikam/ > > Note : the database contents must be sync with the file metadata. Use > Tools/Maintenance/Sync Metadata and Database to do it > > https://docs.digikam.org/en/maintenance_tools/maintenance_metadata.html Do I need this newer verison for it to work.
you can try the Maik tips first without update...
Created attachment 166832 [details] attachment-1528898-0.html Even when I searched in the help for the "re-read metadata from files" it did not work. Also so I know in the future does doing this delete the digikam data for those files (I have set it to not write the digikam data to the files exdif) On Sun, 10 Mar 2024 at 10:51, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=482944 > > --- Comment #23 from caulier.gilles@gmail.com --- > you can try the Maik tips first without update... > > -- > You are receiving this mail because: > You reported the bug.
(In reply to caulier.gilles from comment #23) > you can try the Maik tips first without update... "New Auto-Tags tool based of deep-learning to identify and mark image contents automatically." "2024.03.10" so is it being released very soon? If so I will just wait till like tomorrow, but I also want to know can this deep learning system be used to do a stand alone search of images (standalone meaning it does not mark the contents)
There are two options in the Album or Item menu for metadata. You should run the option to re-read from image to database. This is important for your problem, as no metadata is written into your images. In the opposite case, no metadata would be written to your images if you have not activated the options to write in the digiKam metadata settings. Since we have never been able to reproduce this problem ourselves under Windows, it would be interesting to know whether your system or image collection has any special features. 1. Which antivirus program do you use? 2. Where are your images located, on a local hard drive, external drive or a network drive? 3. Is your image collection part of a Windows network share? Maik
Created attachment 166849 [details] attachment-1672254-0.html Avast And it's on a ssd Just one folder with all photos (I was using Dim 5 to sort by month I will end this if I get digikam working nicely as digikam seems much more advanced) On Sun, 10 Mar 2024, 8:22 pm Maik Qualmann, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=482944 > > --- Comment #26 from Maik Qualmann <metzpinguin@gmail.com> --- > There are two options in the Album or Item menu for metadata. You should > run > the option to re-read from image to database. This is important for your > problem, as no metadata is written into your images. In the opposite case, > no > metadata would be written to your images if you have not activated the > options > to write in the digiKam metadata settings. > > Since we have never been able to reproduce this problem ourselves under > Windows, it would be interesting to know whether your system or image > collection has any special features. > > 1. Which antivirus program do you use? > 2. Where are your images located, on a local hard drive, external drive or > a > network drive? > 3. Is your image collection part of a Windows network share? > > Maik > > -- > You are receiving this mail because: > You reported the bug.
Outside the fact that antivirus usage has side effects on a computer, you must to know that AVAST blow out your personal data : https://www.theverge.com/2024/2/22/24080135/avast-security-privacy-software-ftc-fine-data-harvesting In my office (more that 4500 people using computer on the same network), the native Microsoft antivirus is deployed everywhere on Windows computers (Windows 10).
A likely cause could also be an already closed Bug 481630 in digiKam-8.3.0. If there is heavy use of an SQLite database, this will result in data records being discarded and not being saved to the database. Maik
In other words, please use the 8.3.0 pre-release Windows installer. We are near the final release so it's safe to use as well. https://files.kde.org/digikam/ Note: it will be released certainly next Sunday, as i waiting my MacBook computer back at home after a batteries changes (without this computer, i cannot build the MacOS package). Gilles Caulier
(In reply to caulier.gilles from comment #30) > In other words, please use the 8.3.0 pre-release Windows installer. We are > near the final release so it's safe to use as well. > > https://files.kde.org/digikam/ > > Note: it will be released certainly next Sunday, as i waiting my MacBook > computer back at home after a batteries changes (without this computer, i > cannot build the MacOS package). > > Gilles Caulier Nah I will update it when it comes out thanks to the help of you guys I have been able to fix the issue(In reply to caulier.gilles from comment #30) > In other words, please use the 8.3.0 pre-release Windows installer. We are > near the final release so it's safe to use as well. > > https://files.kde.org/digikam/ > > Note: it will be released certainly next Sunday, as i waiting my MacBook > computer back at home after a batteries changes (without this computer, i > cannot build the MacOS package). > > Gilles Caulier I have now update to 8.30
(In reply to caulier.gilles from comment #28) > Outside the fact that antivirus usage has side effects on a computer, you > must to know that AVAST blow out your personal data : > > https://www.theverge.com/2024/2/22/24080135/avast-security-privacy-software- > ftc-fine-data-harvesting > > In my office (more that 4500 people using computer on the same network), the > native Microsoft antivirus is deployed everywhere on Windows computers > (Windows 10). I have removed AVAST and enabled the windows defender features.
Do you think I should delete the database and just re add the images again (I won't lose anything I was just using digikam as a better replacement to DIM 5 eg see the dates the map of where taken but these are all saved in the images)?
(In reply to mlh.kiwi from comment #33) I did do this , I even deleted that file in user data so I could start again yet it is still not working these images are still being sorted incorrectly, I just picked a random one as an example: https://drive.google.com/file/d/1jGCixGuHsZvtrRMRpJEf1BXjDvOaFMDm it is sorted/marked in digikam as https://drive.google.com/file/d/16HYGvAO0HgZ_sS2RKoqQvVR8CGTVUpMs 21/08/2017 10:24 am is time date and time shown by windows properties Again the camera is the Samsung WB700 (for these older photos)
This image produces errors in our primary engine (Exiv2) to read metadata from the image. In this case we would automatically switch to ExifTool. I suspect that ExifTool isn't working for you for some reason. Do you see an error message or a list of the metadata for this image in the Metadata section in the ExifTool tab in the right sidebar? digikam.metaengine: Exiv2 ( 2 ) : Directory Samsung2 has an unexpected next pointer; ignored. digikam.metaengine: Exiv2 ( 2 ) : Directory Samsung2, entry 0x0000 has unknown Exif (TIFF) type 0; setting type size 1. digikam.metaengine: Exiv2 ( 2 ) : Directory Samsung2, entry 0x0006 has unknown Exif (TIFF) type 259; setting type size 1. digikam.metaengine: Exiv2 ( 3 ) : Offset of directory Samsung2, entry 0x0006 is out of bounds: Offset = 0x00010006; truncating the entry Maik
Git commit eda2cf81b71d0e95ccc78c8838c80d4ce4e270ef by Maik Qualmann. Committed on 11/03/2024 at 21:54. Pushed by mqualmann into branch 'master'. show an error notification if ExifTool is not available M +12 -0 core/app/main/digikamapp.cpp M +1 -0 core/app/main/digikamapp.h M +1 -0 core/app/main/digikamapp_p.h M +3 -0 core/app/views/stack/itemiconview.cpp https://invent.kde.org/graphics/digikam/-/commit/eda2cf81b71d0e95ccc78c8838c80d4ce4e270ef
Hi, The Windows 8.3.0 pre-release installer will be rebuild this morning with last changes from Maik. Gilles Caulier
(In reply to caulier.gilles from comment #37) > Hi, > > The Windows 8.3.0 pre-release installer will be rebuild this morning with > last changes from Maik. > > Gilles Caulier Very good job. I did get that error right away out of curiosity are there other error messages that can show up?
Thanks for the feedback about your solved problem. We don't know other situation where a similar error message will appear. Gilles Caulier
(In reply to caulier.gilles from comment #39) > Thanks for the feedback about your solved problem. > > We don't know other situation where a similar error message will appear. > > Gilles Caulier Only problem is that did not solve the problem
(In reply to mlh.kiwi from comment #40) > (In reply to caulier.gilles from comment #39) > > Thanks for the feedback about your solved problem. > > > > We don't know other situation where a similar error message will appear. > > > > Gilles Caulier > > Only problem is that did not solve the problem exiftool 12.78 is the one I downloaded and this is seeming to be found by the digikam configure (In reply to mlh.kiwi from comment #40) > (In reply to caulier.gilles from comment #39) > > Thanks for the feedback about your solved problem. > > > > We don't know other situation where a similar error message will appear. > > > > Gilles Caulier > > Only problem is that did not solve the problem I re read the meta data from the files to database and yes it does work!