https://bugs.kde.org/show_bug.cgi?id=381821
Bug ID: 381821
Summary: Wrong value on high ISO settings & fix Exposure value
formatting
Product: frameworks-kfilemetadata
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: pinak.ah...@gmail.com
Reporter: fince...@hotmail.com
Target Milestone: ---
Created attachment 106386
--> https://bugs.kde.org/attachment.cgi?id=106386&action=edit
Fix for high ISO values & reformat Exposure tag
I don't know should I open two separate issues for these. Anyway,
------------------------------------------------------------------------
1) Wrong ISO value reported on high ISO settings
- kfilemetadata reports wrong ISO value (65535) if extreme ISO settings like
102400 is used.
This is because kfilemetadata exiv2extractor receives the value from
"Exif.Photo.ISOSpeedRatings" tag, which is, according to Exiv2 documentation, a
short integer, with a maximum limit of 65535. Obviously, ISO speed such as
102400 exceeds the limit and thus wrong value is set. This tag is specified in
ISO 12232 standard.
Instead of Exif.Photo.ISOSpeedRatings", ISO value can be retrieved from
""Exif.Photo.RecommendedExposureIndex" tag, at least for some cameras.
ExposureIndex tag gives correct ISO values at least for Canon 5D Mark 3 RAW
images (all ISO values tested and checked, including CR2 -> Adobe DNG
conversion files).
NOTE: I'm not sure whether RecommendedExposureIndex is registered by all camera
models or not so I can't be 100% sure if it can be used. Another small issue
with the index value is that decimal separator is missing in Dolphin (which I
think can easily be fixed).
------------------------------------------------------------------------
2) Exposure tag format
I find it extremely annoying how kfilemetadata currently handles
"Exif.Photo.ExposureTime" tag. Values such as 0.0008 are not very informative
while a camera can report 1/8000 for the same picture. After all, as a
photographer, I want get equivalent and good reference values for the ones used
in cameras.
The issue is caused by "QVariant::Double" which is used for Exposure tag in
exiv2extractor.cpp. Replacing it with "QVariant::String" fixes the issue.
------------------------------------------------------------------------
Proposed patch file for these issues as an attachment.
--
You are receiving this mail because:
You are watching all bug changes.
