Created attachment 149563 [details] Screen shot of the Exposure Blending interface. Note 3 image in the upper right. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Selected three images in the from Thumbnail 2. Select Blend Stacked images under Postprocessing 3. Select Preview in Exposure Blending window OBSERVED RESULT Previewed image appears miss read or corrupted in some way EXPECTED RESULT An exposure blended image product SOFTWARE/OS VERSIONS Windows: macOS: Monterey 12.4.0 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Each image in Thumbnail is editable. Don't know why the stacked version is corrupted
Hugin packages downloaded during the installation of DigiKam.
Please post the log from the terminal as described here for MacOS: https://www.digikam.org/contribute/ Maik
It works with JPG files without any problems. I see in the screenshot that you are using NEF files and I can reproduce the problem with that. A first analysis shows that when Exiv2 writes the metadata, the temporary TIF files are no longer readable. We can switch to ExifTool under digiKam-8.0.0 to write metadata. Then there is also no longer a problem with NEF files. Maik
Git commit 3d3870f743c1c0309196595a444c77f435514902 by Maik Qualmann. Committed on 09/06/2022 at 06:47. Pushed by mqualmann into branch 'qt5-maintenance'. copy not original metadata over metadata already saved by DImg This destroys the image files with Exiv2. FIXED-IN: 7.7.0 M +2 -1 NEWS M +13 -14 core/dplugins/generic/tools/expoblending/manager/expoblendingthread.cpp https://invent.kde.org/graphics/digikam/commit/3d3870f743c1c0309196595a444c77f435514902
Maik, thanks for confirming the bug and providing an interim solution, i.e., use JPG files, albeit they have lower bit depth. Yes the interim solution worked for me too. When do you estimate digiKam-8.0.0 will be available to download? Steve (In reply to Maik Qualmann from comment #3) > It works with JPG files without any problems. I see in the screenshot that > you are using NEF files and I can reproduce the problem with that. A first > analysis shows that when Exiv2 writes the metadata, the temporary TIF files > are no longer readable. We can switch to ExifTool under digiKam-8.0.0 to > write metadata. Then there is also no longer a problem with NEF files. > > Maik
Maik, also determined that digicam 7.6.0 works fine with both 8- and 16-bit TIF images. Using 16-bit TIF is a better work around. My work flow is Nikon Z7 > Nikon's NX Studio > export 8|16-bit TIF image. Thanks again. -Steve
Git commit 7efc95ba540bf1d758d42ac604d704c026b89d93 by Maik Qualmann. Committed on 09/06/2022 at 16:42. Pushed by mqualmann into branch 'qt5-maintenance'. better metadata handling in the panorama tool Setting metadata via QByteArray can buggy in current Exiv2 versions. M +2 -2 core/dplugins/generic/tools/expoblending/manager/expoblendingthread.cpp M +22 -30 core/dplugins/generic/tools/panorama/tasks/preprocesstask.cpp https://invent.kde.org/graphics/digikam/commit/7efc95ba540bf1d758d42ac604d704c026b89d93
It is planned to release digiKam-7.7.0 for the time being. However, the Exposure Blending tool has already been fixed in this version. The Windows version cannot be compiled at this time. After that we will probably switch to alpha/beta versions of digiKam-8.0.0. Maik