Bug 359083 - digiKam doesn't read JPG XMP data written by Lightroom
Summary: digiKam doesn't read JPG XMP data written by Lightroom
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Sidecar (show other bugs)
Version: 4.13.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-06 23:28 UTC by Unknown
Modified: 2022-01-19 10:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2016-02-06 23:28:25 UTC
RAW development settings written by Lightroom to a JPG file are not visible in digiKam when browsing the same images.

Reproducible: Always

Steps to Reproduce:
1. Make some RAW development on a JPG file in Lightroom
2. Open the file directly from disk in Photoshop - the settings are there
3. Try to open the same file in digiKam 

Actual Results:  
The RAW development settings settings are not seen in digiKam (it shows the original)

Expected Results:  
See the same as in LR development

I am not 100% sure if this is a bug as I am not an expert on XMP. But logically one would expect to have compatibility between programs. So if it is not a bug - please let me know if there is a workaround or if it can be implemented. Thanks.
Comment 1 caulier.gilles 2016-02-07 08:53:55 UTC
Ahhh... Wecome to wonderfull RAW world...

Well, no, it's not compatible : LR RAw decoder is propriétary, not dicumented, and of course not compatible with digiKam RAW decoder (libraw).

So the LR XMP data are for LR only. We don't know whats we can do with it.

Gilles Caulier
Comment 2 Unknown 2016-02-09 11:20:45 UTC
(In reply to caulier.gilles from comment #1)
> So the LR XMP data are for LR only. We don't know whats we can do with it.

Reverse engineering :P
Comment 3 caulier.gilles 2016-02-09 11:24:24 UTC
We have more important tasks to do than RE.

Even if RE is need, this must be done in Exiv2 libs with documentation. 

Good luck...