Bug 481755

Summary:	Use ExifTool as a full native backend.
Product:	[Applications] digikam	Reporter:	Roberto <betokella>
Component:	Metadata-ExifTool	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	REPORTED ---
Severity:	wishlist	CC:	caro.portal, caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	8.3.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Roberto 2024-02-24 10:55:01 UTC

SUMMARY
***
"Delegate do exiftool backend all operations to write metadata to files" is marked but digikam will still use Exiv2.
***


STEPS TO REPRODUCE
1. Enable exiftool backend to write metadata
2. Bouce digikam (necessary?)
3. Write metadata to a file

OBSERVED RESULT
From debugview:
[11044] digikam.metaengine: Cannot export changes with Exiv2 backend:   (Error # 38 :  "Size of XMP JPEG segment is larger than 65535 bytes"
[11044] digikam.metaengine: Exiv2 error exception for "PXL_1369.JPG" Writing of metadata aborted!

EXPECTED RESULT
I am trying using exiftool to overcome the 64k limitation in XMP segment. Setting exiftool as backend should allow >64K. But there is no evidence in the log exiftool is actually being used. Checking the file directly with exiftool also does not show the additional tags I am trying to write.

SOFTWARE/OS VERSIONS
Windows: 10.0.19045 N/A Build 19045
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Roberto 2024-02-24 10:58:23 UTC

More complete log entry:
[4160] digikam.metaengine: "PXL_1369.JPG"  ==> New Iptc Keywords:  QList("NoNoNo", "Faces area range 15", "Portraits", "Collections")
[4160] digikam.metaengine: MetaEngine::metadataWritingMode 0
[4160] digikam.metaengine: Will write Metadata to file "PXL_1369.JPG"
[4160] digikam.metaengine: Check ExifTool availability: true
[4160] digikam.metaengine: Cannot export changes with Exiv2 backend:   (Error # 38 :  "Size of XMP JPEG segment is larger than 65535 bytes"
[4160] digikam.metaengine: Exiv2 error exception for "PXL_1369.JPG" Writing of metadata aborted!

Comment 2 Maik Qualmann 2024-02-24 11:18:41 UTC

We create an EXV container file with Exiv2, which is applied to the image/video file with ExifTool. If the creation of the EXV container fails, like in your case, we have a problem. Remember that digiKam is based on Exiv2 and it is not possible to switch completely to ExifTool without a lot of effort. But I'm actually planning a way to use ExifTool as natively as possible in the future.

Maik

Comment 3 caulier.gilles 2025-12-22 02:51:00 UTC

*** Bug 509279 has been marked as a duplicate of this bug. ***