Exchanging with darktable

[nwinspeare]

Hello,
I now use darktable as my raw developper as it has become in my view a very professional editor. My problem is exchanging tags...
Darktable uses xmp files stored in a <filename>.<ext>.xmp format whereas most apps (LR,C1...) use <filename>.xmp
Could it be possible to have the option for Photomechanic to read/write to <filename>.<ext>.xmp ?
Thanks,
Nicolas

[Kirk Baker]

Nicolas,

I now use darktable as my raw developper as it has become in my view a very professional editor. My problem is exchanging tags...
Darktable uses xmp files stored in a <filename>.<ext>.xmp format whereas most apps (LR,C1...) use <filename>.xmp
Could it be possible to have the option for Photomechanic to read/write to <filename>.<ext>.xmp ?

No.  That's completely non-standard.  The Darktable developers should follow the standard.

-Kirk

[LateJunction]

Kirk,
I have just, inadvertently, posted a Support Ticket on this very subject, not realising this Feature Request part of the forum is available. Your response seems awfully blunt, if you'll forgive my saying so. What is this 'standard'? Is it an ISO standard? If not, who defines and maintains it? What are the 'penalties' associated with not following the 'standard? Could you make a little more time available to consider if there is a work-around you could suggest?

Tony Hamilton

[Bob M]

Perhaps LateJunction might be interested in the thread https://discuss.pixls.us/t/free-software-and-photo-metadata-a-chance-to-engage-with-the-broader-photography-industry/23068 on the pixls.us forum.

[Kirk Baker]

Tony,

Your response seems awfully blunt, if you'll forgive my saying so. What is this 'standard'?

It is not an official standard.

Is it an ISO standard? If not, who defines and maintains it?

No, not ISO.  It is a de-facto standard from Adobe.

What are the 'penalties' associated with not following the 'standard?

Lack of interoperability with other software (you've discovered this already).  Lower performance when querying the file system for the existence of these additional files.  Duplication of data in both the standard basename.XMP and the basename.ext.XMP files.  More file system clutter.  Lack of synchronization of the files depending on what software is used.  I really could go on with how bad it is if I were to think about it some more.

Could you make a little more time available to consider if there is a work-around you could suggest?

I can't think of a workaround.  We would have to modify our software to accommodate this unusual use of XMP files.

-Kirk