https://bugs.kde.org/show_bug.cgi?id=426923
Bug ID: 426923
Summary: EOS R5 CR3 Missing exif data with current master
branch code
Product: digikam
Version: 7.2.0
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Metadata-Raw
Assignee: digikam-bugs-n...@kde.org
Reporter: f...@kdmurray.id.au
Target Milestone: ---
SUMMARY
CR3 images from the EOS R5 don't seem to display metadata from exif etc.
Possible duplicate of https://bugs.kde.org/show_bug.cgi?id=424860, but I think
that the fixes in this issue are included in the current master branch and
therefore in theory are included in the version I'm running. I can confirm the
same behaviour with the released 7.1.0.
STEPS TO REPRODUCE
1. With digikam from current master branch
2. ./bootstrap.local && cd build && make install && ./finish_install.sh
3. Navigate to a directory containing CR3s
4. click metadata from RHS menu
5. Chose "no filter" from drop down menu, and "select all" under settings to
enable display of all metadata fields.
OBSERVED RESULT
No metadata in exif/makernotes/iptc panels of metadata tab, even with it set to
display all metadata.
EXPECTED RESULT
If I understand correctly, at least some basic EXIF metadata (e.g. exposure
settings, capture date, GPS) should be present in this view in digikam version
7.1.0+ thanks to bug 424860's Exiv2 workaround.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Frameworks 5.70.0
Qt 5.14.2 (built against 5.14.2)
The xcb windowing system
ADDITIONAL INFORMATION
My digikam database (sqlite) and config file (~/.config/digikamrc) were first
created with DK v 6.4-ish. I have confirmed that the behaviour I describe above
happens also when i back up digikamrc etc and start from scratch with
7.2.0-beta (from current master branch).
While no QT wizard, I'm more than happy to contribute code or whatever to
better support CR3s in digikam. I have some experience in C++, and a modest
background in image processing. I would need supervision, but if someone from
digikam knows approximately how to fix these issues but doesn't have time, I'm
happy to contribute code for this.
--
You are receiving this mail because:
You are watching all bug changes.
