Closed madanyang closed 10 years ago
I don't know anything about sidecar files, but if the libraries support them I suppose it's possible. I prefer the idea of writing the metadata into the image file - it doesn't get lost that way. Is there a standard naming convention for sidecar files?
Normally it is Filename.Extension.xmp. For example Digikam, darktable and AfterShotPro would write the xmp sidecar for DSC_1120.NEF as DSC_1120.NEF.xmp.
While it is definitely possible to write the metadata into the image file, the raw file should not be altered is my understanding, hence the sidecar files. All the above mentioned image editors do hold the info both in their databases and in the sidecar files. When exporting the edited picture then all the metadata can be embedded in to this final picture.
Can you send me one or two .xmp files to use for testing? I promise not to disclose their contents. Email to jim@jim-easterbrook.me.uk
Commit ec27dd3 enables use of existing sidecar files. If a sidecar exists, data is read from sidecar and image but only written to sidecar. I'll add config options to give more control over this.
Commit afcbda9 adds controls to make sidecars always, when needed or never, and to 'write protect' the image file. (If writing to the image file is enabled the metadata is written to both image and sidecar.) There are a few problems with metadata copying to sort out, but I think this enhancement is done.
Would it be possible to write these metadata to xmp.sidecar files so this becomes a non destructive process. Also needless to say it should be able to read sidecar files as well