I observed a very strange behaviour using digikam together with hugin. workflow: jpegs imported from camera with digikam, creation of panoramas wih hugin on these files, panorama jpeg exif only contains limited information: section file properties (name, owner etc.), picture properties (color depth etc.) If pictures are transferred directly from camera to computer via Nautilus and the panorama is created the EXIF information is complete: It now contains section on photo such as time taken, camera model and also the information inserted by hugin which projection was used. All this information is displayed correctly in digikam. Reproducible: Always
Which digiKam version you use ?
Created attachment 79766 [details] screen shot of the good case (the last two sections are missing in the other case)
It is version 2.8 only, I guess the newest one ready for Ubuntu
I found (my) mistake. Hugin generate the picture in a folder already included in a collection of digikam. It seems there is no automatic meta data screening when new picture are detected upon start-up (Or is there an option to turn it on ????). I manually choose reread metadata from pictures and there we go ... Greetings, Georg
New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ?
Dear Gilles, I am now on 4.11. The problem somehow persists. I played around a bit. Case 1: Hugin panorama is generate while digikam is not running: ==> New pic is shown, all Metadata shows up correctly (Dateieigenschaften, Eigenschaften für Einträge, Fotoeinträge, digikam-Einstellungen [in the latter the projection information added by higin] Case 2: Hugin panorama is generated while digikam is running: ==> New pic is shown, Metadata is incomplete (shows only Dateieigenschaften, Eigenschaften für Einträge), date shown below pic is wrong (date of file generation of this panorama) When initiating manually to reread meta data, Metadata is updated and nearly complete (Dateieigenschaften, Eigenschaften für Einträge, digikam-Einstellungen but missing Fotoeinträge) date is correct digikam is closed and started again Now metadata is complete again (identical to case 1) Case 3: Hugin panorama is generated while digikam is running: as above but no manual rereading of metadata digikam is closed and started again Metadata is unchanged (incomplete, wrong date) as before closing digikam Hope this helps - there seems to be only a partial meta data updating when pictures appear while digikam is running. Greetings, Georg
re-opened
This file still valid using last digiKam 5.0.0 ? Gilles Caulier
Hi Gilles, have not updated yet. Just now installed with philip ppa. First impression is good. Short question: Digikam5 will not use the settings made in digikam4? And will build a new sql database? I will report on the issue after some testing. Georg
Some first test show that problem is still present: Digikam was running HDR processing in the background New pictures appear in album Metadate incompletely read (see first attachment) digikam closed and reopened Metadata stlll incomplete and timestamp of date of creation Upon item rereading metadata complete date is shown (see second attachment) I also include a picture of my settings.
Created attachment 100076 [details] pictures freshly generated while running digikam
Created attachment 100077 [details] after rereading meta date for this single picture
Created attachment 100078 [details] my settings (which might be important)
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at this url : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier
Hi Gilles, I tested the case again. A HDR and four LDR are generated while digikam is running (5.30 and 5.40 appimage). The new pictures are seen upon creation. Metadata is incomplete (only section File properties and properties of picture (jpg, size, etc.). Date shown is new creation date. Upon manual rereading of metadata: Date is corrected to date from EXIF (which is set by my script to the EXIF date from the underlying picture stack) and keyword HDR (which my script adds) is displayed under section digikam properties. Section picture properties (camera model and the other EXIF data) only reappears upon restarting digikam. Identical behaviour is seen for both versions. Hope this helps in finding the bug. Georg
Hi Gilles, I am now on 5.6.01 appimage. Case 1: New files generated while running digikam. There is now complete information on the right hand side for the new pics. However the internal date (shown just below the picture is wrong, time of creation and not time of shooting). The tag HDR is shown on the right hand side (but not below picture). Upon rereading metadata these mistakes are corrected. Case 2: Files are generated while digikam is not running. When digikam has started up the new files are correct (right hand side info, tag, date) - Just perfect. Best regards, Georg
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier
Dear Gilles, thanks for the new version. First experiences are good. I tested again what happens upon generation of a picture when digikam is running. The new picture appears in the folder and the metadata (below picture and on left side is correct). No requirement to reread metadata or to close/reopen digikam. Seems to be solved. Thanks!