Created attachment 164911 [details] XMP file not taken in account Hello, I believe I am facing a bug during my workflow for importing a new folder. Some .xmp files are taken in account and same other NOT. For years I always worked that way without issues until January this year after installing your 8.2 version. It was woking well in the previous version. I read all your documentation (great documentation, over 1000 pages, very detailled) and I cannot understand what is wrong in my settings or in my process. First, let explain my workflow for importing a new folder. 1- By using the windows copy tool, I copy the ARW (Sony raw files) from my camera to a window folder. 2- By using GEOSETTER, I insert geolocalisation into .XMP files. I like to use GEOSETTER because I can retrieve the country, the state (region in french) the city and the sublocation that I frequently use as search axis en Digikam. 3- I launch Digikam and in order to read the new folder content, I run Tool > Maintenance and I select the following options - Album : Only the main root of the new folder for performance reasons. - Sync metadata and database : Direction : From image image metadata to DataBase. So far, I believe I am using the default settings. Generally speaking, I am using WAL and NOT the lazzy synchronization as you mention in your documentation. All the maintenance process works well without any warning or error messages. 4- When I run Tag > Tag manager, I can see only a part of the new tags created by GEOSETTER. You will find in attachement one example of the .xmp file which does not create new tags (Paris 01). When I compare one of the xmp files taken / NOT taken in account, I cannot see any stucture diffence. Remember that all .xmp files are created by the same application, during the same run . I have to mention that I have recently installed you 8.2 version. Before in 8.0 version all was working fine. Tell me if you need other informations from side to help to understand and correct this concern. Tell me also if there is way of working for not facing this issue. I am a french native, so sorry for my poor english level. If you prefer, we can continu either in french or english as you prefer. Best Regards. SOFTWARE/OS VERSIONS Windows: 10 last build following Microsoft monthly update
Hi, With the Windows version 8.2.0, we found plenty of regression bugs due the new build of the bundle using MSVC compiler. Please double check if your problem still exists with the 8.3.0 pre-release installer available here : https://files.kde.org/digikam/ Best regards Gilles Caulier
Previous digiKam versions always read sidecars first of type BASISNAME.xmp if they were present. This has now been changed due to bug reports, it now explicitly depends on the sidecar setting for commercial programs. sidecar name for commercial program activated: BASENANE.xmp otherwise BASENAME.EXT.xmp. So in order to have a sidecar of the type you uploaded here, you have to activate this option. You need to decide if you need an exchange for programs that use BASENAME.xmp as a sidecar, we would recommend not enabling this option in order to use BASENAME.EXT.xmp Maik
Link to the sidcar settings doc: https://docs.digikam.org/en/setup_application/metadata_settings.html#sidecars-settings Maik
Created attachment 164919 [details] attachment-1354313-0.html Hello, Following your advise, I have installed the 8.3.0 pre release version and unfortunalely the issue is still the same. And no what can be the solution ? For time being, (= waiting for a completion of this bug issue), I will be happy even ith a turn aorround solution. Best Regards *Jean - Louis Joli* Le lun. 15 janv. 2024 à 10:43, <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=479833 > > caulier.gilles@gmail.com changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > > --- Comment #1 from caulier.gilles@gmail.com --- > Hi, > > With the Windows version 8.2.0, we found plenty of regression bugs due the > new > build of the bundle using MSVC compiler. > > Please double check if your problem still exists with the 8.3.0 pre-release > installer available here : > > https://files.kde.org/digikam/ > > Best regards > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug.
Please read Comment 2 and Comment 3, this is not a bug, but changed behavior. Maik
Created attachment 164942 [details] attachment-1433354-0.html Hi Maik, Thanks for your quick reply with a lot of details. Following your advise, I I read carefully the documentation part Metadata Settings / Sidecars settings Unfortunally, I cannot understand clearly the metadata parameters that I do have to apply in order to get what I expect. Let explain, my picture files are named as following : 1- The original RAW picture : A2400001.ARW. This picture have geolocalization data* included in the original file* (= not as a sidecar, xmp file) For time being, I first create the folder and after I read the new data by running Tools > Maintenance > Sync Metadata and Database by reading the data from the image to the DB. What must be the parameters I have to apply the settings in order Digikam will be able to create the new data for Country / State / City / Sublocation / Altitude as tags in DB ? Is that the good way of working or you advise another process ? 2- After treatment in order to create the JPG file, is named : A2400001_DxO6.JPG The software used (DxO in my case) is copying all metadata included into the new file created (= not as xmp file). By processing the same way as described above (Tools > Maintenance etc ...) and following the Digikam settings, will the new created pictures also included in the DB ? Else if it cannot work correctly, could you please advise for a way of working that can fit automatic tags creation in the Digikam DB ? Thanks in advance for helping me for solving this concern. Best Regards *Jean - Louis Joli* Le lun. 15 janv. 2024 à 11:07, Maik Qualmann <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=479833 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |metzpinguin@gmail.com > > --- Comment #2 from Maik Qualmann <metzpinguin@gmail.com> --- > Previous digiKam versions always read sidecars first of type BASISNAME.xmp > if > they were present. This has now been changed due to bug reports, it now > explicitly depends on the sidecar setting for commercial programs. > sidecar name for commercial program activated: BASENANE.xmp otherwise > BASENAME.EXT.xmp. > > So in order to have a sidecar of the type you uploaded here, you have to > activate this option. You need to decide if you need an exchange for > programs > that use BASENAME.xmp as a sidecar, we would recommend not enabling this > option > in order to use BASENAME.EXT.xmp > > Maik > > -- > You are receiving this mail because: > You reported the bug.
The name of your sidecar file that you uploaded "A2402601.xmp" corresponds to what many commercial programs create. digiKam would create and read “A2402601.ARW.xmp” in the standard settings. Do you see the difference? We prefer to use the file extension in the sidecar file name. That's why you have to activate the option "Sidecar file names are compatible with commercial programs" under Sidecar in the digiKam settings. Now all you have to do is re-read the metadata of your images where you miss the metadata (via Item Menu, Album Menu - re-read metadata from the image). There will no longer be any problems with newly imported images. Maik
Were you able to solve the problem by enabling the "Sidecar filenames compatible with commercial programs" option? Maik
Created attachment 165212 [details] attachment-2564871-0.html Hi Maik, Sorry for my late reply but my availability was very low during the past days. With your explanations and recommendations that you gave me during our email exchanges, now everything is working correctly. I have defined a Digikam customizing that meet with all my requirements. You can close my tikcket and consider it as succefully resolved. For my own, I prefer to modifiy the RAW files instead of creating sidecar files. I have the chance that Exiftool is able to write in my RAW file and of course it is easier to manage all the data inbeded into a single file (the picture file) instead of to have to manage 2 files linked (picture + sidecar file). Anyway, A big thank you for your support and generally speaking, a lot of congratulations for Digikam which I find very successful and I like using. Best Regards *Jean - Louis Joli* Le jeu. 25 janv. 2024 à 08:09, Maik Qualmann <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=479833 > > --- Comment #8 from Maik Qualmann <metzpinguin@gmail.com> --- > Were you able to solve the problem by enabling the "Sidecar filenames > compatible with commercial programs" option? > > Maik > > -- > You are receiving this mail because: > You reported the bug.