| Summary: | Metadata is modified when saving after a simple crop in Image Editor. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | kde |
| Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Example of modified metadata
MakerNotes is way off |
||
|
Description
kde
2025-12-22 20:45:35 UTC
Created attachment 187882 [details]
MakerNotes is way off
Exiv2 has a serious error with the "original" image: digikam.metaengine: Exiv2 ( 3 ) : Directory Canon with 13312 entries considered invalid; not read. Internally, we still use Exiv2 to decode the metadata. The image appears to have already been processed by another program. Comment metadata added? By which program? Maik The only program I could think of is WLPG. So this sounds like another problem I read about which, if I remember correctly, was that the MakerNotes byte order was different than expected... Could it help my situation if I enabled everything related to ExifTool? Also, if it is simply not read, why would values change? This is the other place I was talking about. https://exiftool.org/forum/index.php?topic=11264.0 |