[Digikam-devel] [digikam] [Bug 347737] Tagged RAW files do not show tags after round trip to RawTherapee

Eric Mesa ericsbinaryworld at gmail.com
Fri May 15 18:09:58 BST 2015


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

--- Comment #20 from Eric Mesa <ericsbinaryworld at gmail.com> ---
(In reply to Alan Pater from comment #19)
> 1st: It has nothing to do with RawTherapee as the XMP data was written to
> the Exif section of the CR2 image by libkexiv2 via digikam. RawTherapee
> carried over that data unchanged to the JPG.
> 
> 2nd: This is why it is labelled experimental. For CR2 images, the correct
> workflow is to allow digikam to only write to XMP sidecar files. Then once
> you have converted to JPG, import the XMP metadata from the sidecar file.
> 
> 3rd: There has been some work on improving RAW file support in exiv2, but it
> is not yet complete. This includes reading from Exif.Image.XMLPacket.

I wouldn't mind changing it to XMP sideca (or maybe sidecar+file?), but does
the same workflow hold for DNG files? Because I know that I had the same thing
happen with a DNG file as with a CR2 file. (In other words, the data was not
read in exiv2 after the JPEG was made). 

The reason I ask is that, at this point with how good support is across the
board for camera raw files, the only real reason for me to convert to DNGs is
to take advantage of being able to store metadata within the file rather than
in a sidecar file. Otherwise, RawTherapee, Digikam, etc can all read the CR2
file and it works just fine for archival purposes - my descendents will most
likely be able to find a converter and/or the most important files will most
likely have been made into JPEGs anyway. So, should I be able to save this data
to the DNG and expect the resultant JPEG to be read by Exiv2?

That said, I understand this is all FLOSS software done by volunteers. I'm not
trying to be entitled or whatever. I'm just trying to understand the
anticipated workflow as well as bugs to be filed/versions to wait for to expect
the functionality.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Digikam-devel mailing list