Created attachment 106386 [details] 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.
second part is fixed by https://phabricator.kde.org/R286:2dc250bc9239d9f30f55110f4b3b8329c202a5c3
Are you able to provide a test file for issue 1?
Since the provided patch does not work for every file, I need a file for testing a solution that works for everyone. If you have such a file, please upload it.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!