Capture One 11 and Photo Mechanic Workflow
I use Capture One 11.0.1 and Photo Mechanic version 5 (build 19395) in my workflow. The applications are running on a Windows 10x64 system. I use Photo Mechanic for sorting and labelling of the photos. The transfer of the color class and rating information from PM to Capture One 11 works fine. Unfortunatly Capture One 11 can't read the crop data from Photo Mechanic.
Is Capture One basically reading the crop information from the XMP sidecar files?
Are there any settings in Capture One where I can optimize the synchronisation of the crop data between both applications?
Is Capture One basically reading the crop information from the XMP sidecar files?
Are there any settings in Capture One where I can optimize the synchronisation of the crop data between both applications?
0
-
How about the transfer of keywords between CaptureOne and Photo Mechanic, does that work? 0 -
[quote="Eric Nepean" wrote:
How about the transfer of keywords between CaptureOne and Photo Mechanic, does that work?
It works for me, but I follow a few basic rules that may not fit other users.
1) Horses for courses, I use C1 where I think C1 is my best tool. I use other tools for quite a few operations even if C1 allegedly can do it.
2) I maintain metadata in PM only, I do not trust C1 in metadata matters
3) I do not use hierarchical keywords (sometimes the hierarchy model in PM and C1 appear too different), and hierarchical models add more work and little benefit for me. I am apparently not capable of creating a time stable taxonomy for my kind of photography. Simplify, simplify and simplify... all the way back to simple keywords 😊
There are some general glitches with metadata, PM, C1 and DNG, not keyword related. I need to study the DNG and the relevant metadata specifications before blaming PM or C1. It has the lowest priority on my todo list.0 -
[quote="Eric Nepean" wrote:
How about the transfer of keywords between CaptureOne and Photo Mechanic, does that work?
The transfer of keywords and description from PM to CaptureOne works also fine in my workflow.0 -
[quote="NNN636442266700558351" wrote:
I use Capture One 11.0.1 and Photo Mechanic version 5 (build 19395) in my workflow. The applications are running on a Windows 10x64 system. I use Photo Mechanic for sorting and labelling of the photos. The transfer of the color class and rating information from PM to Capture One 11 works fine. Unfortunatly Capture One 11 can't read the crop data from Photo Mechanic.
Is Capture One basically reading the crop information from the XMP sidecar files?
Are there any settings in Capture One where I can optimize the synchronisation of the crop data between both applications?
Update on this Topic.
I placed a Service request and got a very kind reply from the PhaseOne support team.
Capture One only reads meta data out of XMP files and does not support reading crop data out of XMP.
We can certainly raise this as a feature request but it is not a feature which is currently supported.
In the meantime the feature request has been raised.0 -
[quote="NNN636442266700558351" wrote:
...Capture One only reads meta data out of XMP files and does not support reading crop data out of XMP.
You probably noted that there are two important points in that statement?
Firstly and in general, an image's metadata is registered in one or two regular files (and possibly also in a database system). You will find metadata embedded in the image file (sections for exif, iptc, xmp) and in an associated sidecar file, typically xmp. Alas, there are information overlap between the two files. Worse, the two sets of metadata may be inconsistent, even contradicting. Arguably even worse yet, the logically same piece of information may exist in multiple semantically different data elements in one file, and the information may be inconsistent between those elements. One application writes to an element that the next application does not read, or reads, but does not use the info for the intended purpose.
Secondly, Capture One does not use all information it reads from the sidecar file for the intended purpose. Photo Mechanic puts crop data in the XMP sidecar file, C1 reads that file (as stated), but C1 does not use the crop information.
Note that the part "Capture One only reads meta data out of XMP files" was probably stated in context the C1 Load Metadata function. It does probably not include the meaning "never ever reads metadata embedded in an image file" (think import and no sidecar present, for example).
PM users may have the option to write/read metadata to/from both places, metadata embedded in the image file and/or metadata in an associated XMP sidecar file.
Months ago I got a bit puzzled by the combination PM, C1 and DNG. One of my cameras puts DNG files on the card. PM apparently expects DNG to have metadata embedded. After reading the DNG specification, I thought that was reasonable. C1 never writes to the DNG (or other raw file), C1 never embeds metadata. The C1 Sync Metadata function writes only to the sidecar file regardless of the raw file being DNG or not. If PM only embeds metadata in the DNG file and "Capture One only reads meta data out of XMP files", metadata transfer from PM to C1 will not work.
Not so long ago a posting over at the PM forum indicated that PM would not write to a DNG sidecar because the DNG specification dictates metadata to be embedded in DNG. If I remember the DNG spec correctly, it does actually not dictate embedded, at least not embedded only, but I have learned to trust judgements from the main crew at Camera Bits Inc. I will need to read up on this and carefully sort out all those "may", "should" and "must" and the negated forms "may not", "should not" and "must not" before I blame PM for not writing or C1 for not reading metadata embedded in DNG. If you or some other C1 users who have PM in their workflow care to dig in, please do. Post your findings here or at the PM forum.0
Post is closed for comments.
Comments
5 comments