https://bugs.kde.org/show_bug.cgi?id=418645
--- Comment #13 from Martin <martin.alth...@mail.de> --- Where does this leave us? So various apps "have issues" with raw files. Including Darktable that clearly suggests to use DNG files. They do mention the purple cast here: https://www.darktable.org/2012/10/whats-involved-with-adding-support-for-new-cameras/ I am unsure which raw lib they actually use at this time in the above link it reads "darktable doesn’t use dcraw/libraw and more." Rawtherapee has no issues whatsoever with my DNG files (about 2700). They claim to use dcraw as raw reader. They even more suggest going to DNG via Adobe DNG converter (https://rawpedia.rawtherapee.com/How_to_convert_raw_formats_to_DNG) As an aside Ubuntu 18.04 has LibRaw 0.19.5 in the repository. As digikam appimage has all built in, that is irrelevant. Manually upgrading to current exiv2 0.27.2, brings no change in reading the metadata. I had a look with exiftool the output for an original S3Pro raw file and the converted DNG. Looking with diff, they are hugely different. Could it be an issue of the raw handler that is used? What is the big difference between Rawtherapee and digikam in this sense? Thinking into a different direction: could it be that Rawtherapee demosaics the file before displaying it? Unfortunately my coding days are long gone, so I'd be challenged to research into, how the "logic" works here. Maik, you seem to hint that progress with exiv2 is "slowish". What relevance does exiv2 have for interpreting the raw/dng files? I'm trying to figure out where the glitch is most likely to be. Thanks, Martin -- You are receiving this mail because: You are watching all bug changes.
