xmp sidecar files not supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyexiv2 |
New
|
Wishlist
|
Unassigned |
Bug Description
Currently exiv2 can write to XMP sidecar files, extracting and converting metadata from the image.
exiv2 can also set new values and write them out to XMP sidecar files, irrespective of any data in the image itself, e.g. with the command -M"set Xmp.iptc.
exiv2 has limited read capacity from XMP sidecar files, in that it can immediately insert directly from a sidecar into an image.
In contrast to exiv2, pyexiv2 lacks the functionality to write XMP sidecar files. This is a problem especially when creating XMP metadata for images formats that are dangerous or foolish to write to -- such as non-DNG RAW files -- where new metadata really does belong in an XMP sidecar.
Moreover, when reading XMP data from an image, the XMP sidecar is totally ignored. This mimics exiv2, but it would be more useful to have the option for pyexiv2 to assume that metadata in the most recent file of the XMP sidecar - image pair is higher priority. This would mimic the behavior of Adobe Bridge and Bibble, for instance. (The discussion in the subsection "PhotoMechanic issues" is useful: http://
Versions:
pyexiv 0.3.2
exiv2 0.21.1
description: | updated |
Changed in pyexiv2: | |
importance: | Undecided → Wishlist |
I have been attempting my own modest implementation of this request. After actually coding it, I ran into a serious problem: writing the XMP sidecar file fails to modify any existing values. This might be purely because of a problem in exiv2: http:// dev.exiv2. org/boards/ 3/topics/ 1052