[digiKam-users] Keyword (metadata) consistency between programs

[Alan H]

Just for a bit of clarity with respect to my experience…
-the 4 th paragraph (If I edit that picture in digicam…): did digicam create the .xmp file in the format “filename.jpg.xmp”?
-the 5th paragraph (However, if I…): were you in ON1 when adding the keyword? Agreed on the second statement. ON1 appears to write JPG metadata (your last question) to its proprietary “filename.on1” sidecar file and creates these files automatically for all JPGs the moment any file in a directory is opened.

When I saw the configuration in digikiam to “Use a compatible file name for writing to sidecar files” and it appeared to create a sidecar in a format very similar to ON1’s, I thought I had at last found two apps for which the metadata sidecars would be interchangeable. It seems though that there is still some confusion about how they process each others sidecars.

It gets more confusing when .raw files come into the mix as I tried to show in previous posts. On1 writes a raw file’s metadata to a .raw sidecar but also seems to include (some?) raw metadata in the .on1 sidecar file, along with all of the parametric commands for whatever non-destructive edits are done. Again, in my experience, if the .on1 sidecar was, in particular, created by digikam both apps have difficulty writing/reading/parsing the JPG and RAW blocks appropriately.

Regarding the last question, I have opened a ticket with ON1 somewhat on that subject – how to get ON1 to read digikam’s filename.jpg.xmp and filename.raw.xmp files. Tech support got back to me and said they had to pass it up to their developers since they did not have an answer. I’ll try to steer the inquiry to writing to “proper” xmp sidecars as well. I’ll pass that info along when (hopefully) I have it.

This isn’t just a digicam vs ON1 issue. I have found sidecar compatibility issues between other popular photo processors – Luminar, DXO PL, Exposure, Affinity – that are trying to provide DAMs (or even just non-destructive editing sidecars). It is such a contentious issue in DXO that the user forum regularly advocates staying away from the DAM game and stick to what they do best.


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: woenx<mailto:marcpalaus at hotmail.com>
Sent: Tuesday, May 5, 2020 10:10 AM
To: digikam-users at kde.org<mailto:digikam-users at kde.org>
Subject: Re: [digiKam-users] Keyword (metadata) consistency between programs

Ok, so I installed both (On1 and Digikam) in a windows machine. I told
digikam to read and save all data to .xmp sidecars. I also told ON1 not to
save metadata and edits to .on1 files.

I first wanted to test the most basic assumption, that both can write and
read from sidecar files, so they can exchange information.

For that purpose, I created a directory which will be the picture library
for both Softwares, and I put a simple JPG picture I got online (with no
metadata).

If I edit that picture in digikam and add a keyword, I can see it generates
a .xmp file and the keyword is there, under a number of sections
<digiKam:TagsList>, <MicrosoftPhoto:LastKeywordXMP>,
<lr:hierarchicalSubject>, <mediapro:CatalogSets> and <dc:subject>.

However, if I take that same picture (the original one without metadata) and
I add a keyword, no .xmp sidecar is generated (and the metadata is not
embedded in the picture either). Moreover, it seems that the next time you
start ON1, it activates the saving to .on1 files again automatically.

If I add a keyword from ON1, digikam does not seem to see it. And
vice-versa.

So, how do you tell ON1 to store the metadata in a .xmp sidecar file?



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20200505/d702881a/attachment-0001.html>