Hi there,

Just to make this clear. CAPTURE ONE 5 STRIPS OUT EXISTING METADATA WHEN IT LOADS THE IMAGES IN THE CURRENT SESSION. THERE IS NO GETTING THIS INFORMATION BACK. This isn't limited to C1 5, it also was the case in C1 4.x but in that case only the post IPTC4 info, the headline and the copyright owner were stripped out. (We had a few templates in Adobe Bridge and PhotoMechanic to resolve this stuff.)

I've been hammering on in the forums at phase one for years now about the poor support for metadata in Capture One. It seems now, as Capture One are piping on about how the new software supports extended metadata, it still only supports the pre 2004 implementation. The reality is that it has become worse, much much worse. In our case (Studio with capture one running on 5 machines - since 3.x.x) I have found that if you embed metadata in another application such as PhotoMechanic so as to make full use of the currrent iptc standards, Capture One strips almost all the metadata out of the RAW files. We find only our keywords left. I think this is a very serious issue, so wanted to take it beyond the companies discussion forums and support ticket systems where nothing seemingly gets done.

To head of a few comments. We don't use the metadata implementation in capture one because as i mentioned it is outdated. It also needs to be entered manually where many image handling software allows automation. PhotoMechanic is our product of choice, we know it now and we'd rather not change it unless something did the same job with less effort and time on our part.

Why is all this important? As our library grows (and yours) metadata is fast becoming the only way to locate images easily. It also contains info about what usage rights our clients have for the image, who the licenced user is, who is the owner or copyright holder, how to find the owner. who shot it, where it was shot, when it was shot.... you know, the Fundamental things!


I would love to hear from other users on their experiences on this. I'd love to find out that we are doing something wrong, or that a reinstall would fix this issue...