| Summary: | from Batch Queue Manager metadata for lens auto-correction are not recognized | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Joachim Ullrich <info> |
| Component: | BatchQueueManager-RAWProcessing | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version: | 7.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/commit/42e5f840691c56c96dbc70ab8c099f7278d9eb62 | Version Fixed In: | 7.7.0 |
| Sentry Crash Report: | |||
I need a sample image, I can't reproduce the problem here with my images. If not public to my private mail. I also use openSUSE Tumbleweed. If you have updated the lensfun database in previous versions of lensfun, you should delete this in the home (~/.local/share/lensfun) directory for a test. Maik Hi Maik, wouldn't have expected such a fast response. The raw-image has a size of 19MiB. Bugzilla limits the size of attachments to 4MiB. So I try it by mail. The image doesn't show persons, so no problem adding to the bug-report. My tumbleweed installation runs under virtualbox, my everyday distro is leap15.3 with currently digikam 7.1.0. I use tumbleweed mainly to check features of newer versions of apps. Neither with leap15.3 nor tumbleweed there is a "lensfun" folder below my home. I checked with strace that digikam finds and opens the lensfun database, i.e. all the xml-files from /usr/share/lensfun/version_1/ are opened and read. If I can do more to analyze the problem, let me know. So far I didn't try to debug digikam. Are there logging options for digikam or the batch queue manager? Best Regards Joachim Ullrich On 24.04.22 14:41, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=452947 > > Maik Qualmann<metzpinguin@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |metzpinguin@gmail.com > > --- Comment #1 from Maik Qualmann<metzpinguin@gmail.com> --- > I need a sample image, I can't reproduce the problem here with my images. If > not public to my private mail. I also use openSUSE Tumbleweed. If you have > updated the lensfun database in previous versions of lensfun, you should delete > this in the home (~/.local/share/lensfun) directory for a test. > > Maik > The test image is of a Canon PowerShot G1X with a fixed lens. Because there is no match between the Lensfun lens string and the lens metadata, digiKam only finds a partial match. Maik We could accept a full match as a workaround if the Lensfun lens string contains the full camera name or the suffix "& compatibles". Maik Git commit 42e5f840691c56c96dbc70ab8c099f7278d9eb62 by Maik Qualmann. Committed on 24/04/2022 at 15:50. Pushed by mqualmann into branch 'qt5-maintenance'. optimize lens detection logic FIXED-IN: 7.7.0 M +2 -1 NEWS M +3 -2 core/libs/dimg/filters/lens/lensfuniface.cpp https://invent.kde.org/graphics/digikam/commit/42e5f840691c56c96dbc70ab8c099f7278d9eb62 |
STEPS TO REPRODUCE 1. select a number of raw images and start batch queue manager 2. add auto lens auto-correction to batch workflow, check "use metadata" with lens auto-correction plugin 3. run queue OBSERVED RESULT for each image: 13:06:32 :: Item "IMG_0784.CR2" from queue "#1": Processing... 13:06:39 :: Item "IMG_0784.CR2" from queue "#1": Failed to process item... 13:06:39 :: Item "IMG_0784.CR2" from queue "#1": Cannot find all lens information to process lens auto-corrections 13:06:39 :: Item "IMG_0784.CR2" from queue "#1": Failed to process item... 13:06:39 :: Item "IMG_0784.CR2" from queue "#1": Failed to create file... EXPECTED RESULT successfull completion of the workflow for all images of the batch queue SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220420 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.3-1-default (64-bit) Graphics Platform: X11 Processors: 4 × AMD FX-8320E Eight-Core Processor Memory: 6.1 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; digikam-7.6.0-1.2.x86_64 kipi-plugins-lang-21.12.3-1.1.noarch liblensfun1-0.3.3-1.1.x86_64 lensfun-data-0.3.3-1.1.noarch digikam-lang-7.6.0-1.2.noarch libdigikamcore7-7.6.0-1.2.x86_64 libkipi-data-21.12.3-1.1.x86_64 digikam-plugins-7.6.0-1.2.x86_64 kipi-plugins-21.12.3-1.1.x86_64 ADDITIONAL INFORMATION 0. tested with raw images from a canon G1x and a canon slr EOS500D with sigma lens 24-70mm 1. comparable misbehavior with didikam7.1.0 under opensuse leap 15.3. 2. there are two different plugins listed for lens auto-correction: image editor: Adrian Schroeter, Gilles Caulier batch queue manager: Gilles Caulier 3. lens auto-correction works as expected (i.e. uses metadata for camera and lens settings), when a single raw image is opened in the image editor and lens auto-correction is applied from the image editor 4. lens auto-correction worked as expected with earlier version of digikam (< digikam 7.x). The workflow for batch raw conversion w8ith lens auto-correction has been used for several years. 5. samples can be provided Looks like a duplicate of https://bugs.kde.org/show_bug.cgi?id=428558 but the problem still exists. I want to point to the fact, that lens auto-correction from image editor works fine with digikam 7.6.0