[Kde-imaging] [Bug 204437] DNGConverter turns olympus ORF unusable

[Gustavo Claramunt]

https://bugs.kde.org/show_bug.cgi?id=204437





--- Comment #27 from Gustavo Claramunt <gclaramunt gmail com>  2009-08-25 00:51:09 ---
@Andreas, i'm unable to catch you, sorry (maybe my english limitations :P ). I
don't know if libraw/dcraw/other raw developers use that sub-ifd, so don't know
why is causing so much trouble.
I'm programmer (well, web programmer though) and casual photographer, so i
really don't know so much about exif "internals"... i only did some tests...
The only thing i know: removing Exif.OlympusIp.BlackLevel means that tag no
longer appears (tested many exif/metadata "visualizers") but raw developers
works as supposed to do...


@Alex, don't bother so much with Gilles DNGConverter... i did same tests using
Adobe DNG Converter, injecting original orf exif data to it with exiv2 and the
problem persisted. Then removed the infamous Exif.OlympusIp.BlackLevel and gone
right as with dngconverter.

Same tests using exiftool instead exiv2, same results.

So maybe is missinterpretation from raw development softwares confused finding
olympus specific exif into a file which should not have it?

I'd love using dng cause full xmp write support from Digikam (and so
interoperability between other softwares) but maybe i'd better stop dreaming of
that?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.