Bug 492715

Summary: Digikam displays the metadata of JXL files incomplete and/or altered
Product: [Applications] digikam Reporter: Rafael Linux User <rafael.linux.user>
Component: Metadata-ExifAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: metzpinguin, rafael.linux.user
Priority: NOR    
Version First Reported In: 8.4.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: https://invent.kde.org/graphics/digikam/-/commit/2276a248356ab97d738e65d70e3aff4d336c1f97 Version Fixed/Implemented In: 8.5.0
Sentry Crash Report:
Attachments: Comparison of metadata

Description Rafael Linux User 2024-09-06 13:43:50 UTC 
Created attachment 173382 [details]
Comparison of metadata

SUMMARY
After exporting from a RAW image to TIFF, WEBP and JXL, I noticed that the metadata displayed by Digikam from the JXL image is not correct and/or incomplete.

STEPS TO REPRODUCE
1. Export from RW2 file to TIFF, WEBP and JXL
2. Compare metadata included in each format

OBSERVED RESULT
Metadata of JXL showed by Digikam seems not the included in the JXL file

EXPECTED RESULT
Show same metadata stored in JXL file

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240902
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 7600

ADDITIONAL INFORMATION
RAW file https://www.transfernow.net/dl/20240906UsozTEUX
Screenshot comparing metadata of JXL and TIFF showed by Digikam from same RAW file.
Comment 1 Maik Qualmann 2024-09-06 13:59:33 UTC 
I cannot reproduce the problem, RAW2->TIFF->JXL using digiKam image editor. All metadata in JXL is correct. Note that ExifTool is required to write metadata to JXL images, the option must be activated in the digiKam settings under Metadata.

Maik
Comment 2 Maik Qualmann 2024-09-06 14:15:57 UTC 
I see in your screenshot that the TIFF has no sidecar, the JXL image does have a sidecar. So ExifTool is probably not activated to write metadata.

Maik
Comment 3 Maik Qualmann 2024-09-06 15:15:38 UTC 
The problem can be reproduced if ExifTool is not enabled and sidecar is enabled for read-only images.

The only problem I see is that certain XMP-Exif metadata does not seem to be interpreted correctly, I will look into this.

You should enable ExifTool though, otherwise you will definitely lose metadata with JXL.

Maik
Comment 4 Rafael Linux User 2024-09-06 23:51:04 UTC 
Indeed, this option was not activated and once activated, the metadata is exported correctly. This is the first time I have noticed this problem with the metadata and I had never changed this option, shouldn't this option be activated by default?
Comment 5 Maik Qualmann 2024-09-07 18:34:27 UTC 
Git commit 2276a248356ab97d738e65d70e3aff4d336c1f97 by Maik Qualmann.
Committed on 07/09/2024 at 18:32.
Pushed by mqualmann into branch 'master'.

fix decoding image metadata from XMP.exif* tags
We get the Exiv2::xmpText type for all XMP.exif.* metadata.
Possibly an Exiv2 bug?
FIXED-IN: 8.5.0

M  +1    -1    NEWS
M  +33   -1    core/libs/metadataengine/engine/metaengine_xmp.cpp

https://invent.kde.org/graphics/digikam/-/commit/2276a248356ab97d738e65d70e3aff4d336c1f97
Comment 6 Rafael Linux User 2024-09-07 20:59:00 UTC 
(In reply to Maik Qualmann from comment #5)
> Git commit 2276a248356ab97d738e65d70e3aff4d336c1f97 by Maik Qualmann.
> Committed on 07/09/2024 at 18:32.
> Pushed by mqualmann into branch 'master'.
> 
> fix decoding image metadata from XMP.exif* tags
> We get the Exiv2::xmpText type for all XMP.exif.* metadata.
> Possibly an Exiv2 bug?
> FIXED-IN: 8.5.0
> 
> M  +1    -1    NEWS
> M  +33   -1    core/libs/metadataengine/engine/metaengine_xmp.cpp
> 
> https://invent.kde.org/graphics/digikam/-/commit/
> 2276a248356ab97d738e65d70e3aff4d336c1f97

Thanks for your quick fix!!!!!