According to Google, photoshop:Caption is an established synonym for dc:Description, and I've found it more reliable to write the wildlife information to there. Capture One reads it no problem, as does my DAM software XnView. It's not an issue for me that it gets copied into Description, but just a prime example of how Capture One re-organises incoming metadata, potentially so it then can't be read by the software which wrote it.
According to Google, photoshop:Caption is an established synonym for dc:Description, and I've found it more rleaible to write the wildlife information to there. Capture One reads it no problem, as does my DAM software XnView. It's not an issue for me that it gets copied into Description, but just a prime example of how Capture One re-organises incoming metadata, potentially so it then can't be read by the software which wrote it.
Happy to oblige. The "before" XMP is generated by my own software, and includes geotags and "wildlife" tags as attributes which are readable by Capture One. The "After" version is after doing a "metadata sync" in C1, and has both changed attributes to elements, and in a couple of cases changed the namespace. The namespaces in my version have been carefully chosen so that the metadata is read by both C1 and ACR.
Capture One is a good example of a well-known program whichif you round-trip XMP data (i.e. sync from source XMP, make a metadata change and re-sync) changes both the namespace and whether data is presented as XMP attributes or elements! I've been battling with that for years...
... Apologies for the double reply. Interesting bug if you accidentally double-click "Post" 😂
Thanks. I use XMP as well, although that has its own many complexities, such as namespaces which get changed randomly by other programs in the pipeline. Also I need something which is embedded in the output JPG. ITPC is perfect for this purpose, Hopefully - m will do the trick.
Hi, I am trying to write a filename (including path) to one of the ITPC fields. If I write the data into an XMP file, read into Capture One and export the JPG, it works fine no problem, with no apparent limit on the text length. C1 and all the downstream software all respect the data regardless of being slightly over the official field length. However I also need to be able to write the same data direct to an existing JPG file using Exiftool. If I try to do this, I get a warning "Warning: [Minor]...
Hi, I am trying to write a filename (including path) to one of the ITPC fields. If I write the data into an XMP file, read into Capture One and export the JPG, it works fine no problem, with no apparent limit on the text length. C1 and all the downstream software all respect the data regardless of being slight over the official field length. However I also need to be able to write the same data direct to an existing JPG file using Exiftool. If I try to do this, I get a warning "Warning: [Minor] IPTC:Source...