Summary: | EOS R5 CR3 Missing exif data with current master branch code | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | K D Murray <foss> |
Component: | Metadata-Raw | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin |
Priority: | NOR | ||
Version: | 7.2.0 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.3.0 |
Description
K D Murray
2020-09-24 11:39:40 UTC
Can you share a CR3 file on the cloud to test in local ? Thanks in advance Gilles Caulier Sure! See https://cloudstor.aarnet.edu.au/plus/s/sVDMnJLFmdWPvJG password is DigikamBug#426923 No problem with Exif here : https://i.imgur.com/V0jAGRG.png Markernotes is empty because we cannot deal with these metadata using libraw. Only standard Exif are supported. Iptc is minimal. XMP is populated with Exif info decoded... So all work as expected. If you want more, please ask to Exiv2 to not lost time with patents troll and to support standard ISO container as CR3 and HEIF... Gilles Caulier Like Gilles, I can confirm that the basic metadata is displayed. Maybe the debug output in the terminal shows something: export QT_LOGGING_RULES="digikam.*=true Maik OK, so i can confirm the nightly appimage build does read the metadata. I assume it's an issue with a dependency from debian. Is there any easy way to make digikam build use mostly vendored libaries a la the appimage? For now i'm just saving metadata to sidecars with exiftool so I can see it in DK, so I have a workaround > I assume it's an issue with a dependency from debian.
No, it's not. We use libraw to parse CR3 files metadata, and libraw code is in digiKam core.
The CR3 metadata entries are re-routed to Exiv2 with an internal code from digiKam, an it do not depend of a specific Exiv2 version. So it must work as well.
the rest is Qt5 to sow information in GUI. Nothing special here.
Q : did you put something special in type mime settings in digiKam setup panel ?
There is a difference about CR3 files which have XMP sidecar or not ?
Gilles Caulier
> did you put something special in type mime settings in digiKam setup panel ? Not that I can find. I've checked: Configure Digkam -> Views -> Mime Types: no text in any "extra image/video/audio files" text boxes, and cr2 and cr3 are in the currently supported image list Configure Digkam -> Metadata -> Sidecars: both read and write to/from xmp files are enabled, writing to xmp is for read-only item only. Is there anywhere else I should look? > There is a difference about CR3 files which have XMP sidecar or not? Unless I make an XMP sidecar with exiftool which contains the full metadata from the CR3, there is no difference between CR3 files with or without XMP files. Oh, i forgot to say that there are also no notes about metadata when the qt debugging logs are enabled, so no hints from that either. The EOS R5 RAW is not supported by libraw at the moment. The loaded image in the Image Editor is broken. Darktable cannot open it either. Maik Well seen Maik... Kevin, please report again to libraw team the CR3 EOS R5 support wish, and don't forget to provide Raw file samples... Best Gilles Caulier Looks like broken CR3 from EOS R5/R6 is a known issue for libraw, with fixes in the pipeline. It appears the author of the new CR3 decoder is keeping it private for now, but will be in the next released version of libraw (I hope). https://github.com/LibRaw/LibRaw/issues/317#issuecomment-671383514 https://github.com/LibRaw/LibRaw/issues/317#issuecomment-674831840 Cheers, Kevin Git commit 86f907da7edaa01bbb519ddd1da871ac65b773f6 by Gilles Caulier. Committed on 28/12/2020 at 10:32. Pushed by cgilles into branch 'master'. Update internal Libraw to last 0.20.2 to imporve metadata extraction from Exif and Xmp https://www.libraw.org/news/libraw-0-20-2-Release Related: bug 320039, bug 403267 M +1 -0 NEWS M +39 -0 core/libs/rawengine/libraw/Changelog.txt M +3 -3 core/libs/rawengine/libraw/libraw/libraw_types.h M +1 -1 core/libs/rawengine/libraw/libraw/libraw_version.h M +12 -2 core/libs/rawengine/libraw/samples/dcraw_emu.cpp M +1 -1 core/libs/rawengine/libraw/samples/raw-identify.cpp M +7 -2 core/libs/rawengine/libraw/src/decoders/kodak_decoders.cpp M +2 -1 core/libs/rawengine/libraw/src/decoders/unpack_thumb.cpp M +5 -2 core/libs/rawengine/libraw/src/libraw_datastream.cpp M +1 -1 core/libs/rawengine/libraw/src/metadata/identify.cpp M +2 -1 core/libs/rawengine/libraw/src/metadata/makernotes.cpp M +34 -32 core/libs/rawengine/libraw/src/preprocessing/raw2image.cpp https://invent.kde.org/graphics/digikam/commit/86f907da7edaa01bbb519ddd1da871ac65b773f6 With next digiKam 7.3.0, a new ExifTool based metadata viewer have been introduced, and Exiftool support fully CR3 file format (Exif, Makernotes, etc..). See the screenshot taken with your CR3 sample : https://imgur.com/1F8sklz Gilles Caulier |