Metadata sync
I hope someone can enlighten me on how Metadata sync works (or is supposed to work). It should not be relevant, but I use a Windows 8.2 PC and run Capture One Pro 8.3.2 64 bit.
Edit->Preferences->Image has a Metadata section with a dropdown list of three selectable options for "Auto Sync sidecar XMP":
1) None
2) Load
3) Full Sync
There is a first check box "Prefer Embedded XMP over Embedded IPTC" (unchecked) and a second check box (checked) "Prefer Sidecar XMP over embedded Metadata".
The Metadata tool's "..."-button gives me a drop down menu with four entries, two of which are for Metadata synchronisation on a selected image:
A) Reload Metadata
B) Sync Metadata
Now, what combination of preference setting (None, Load or Full Sync) and Metadata tool operation (Reload or Sync) forces Capture One to update its metadata with information read from the XMP file?
Edit->Preferences->Image has a Metadata section with a dropdown list of three selectable options for "Auto Sync sidecar XMP":
1) None
2) Load
3) Full Sync
There is a first check box "Prefer Embedded XMP over Embedded IPTC" (unchecked) and a second check box (checked) "Prefer Sidecar XMP over embedded Metadata".
The Metadata tool's "..."-button gives me a drop down menu with four entries, two of which are for Metadata synchronisation on a selected image:
A) Reload Metadata
B) Sync Metadata
Now, what combination of preference setting (None, Load or Full Sync) and Metadata tool operation (Reload or Sync) forces Capture One to update its metadata with information read from the XMP file?
1
-
Suggested reading
viewtopic.php?p=56880#p56880
Let us know if you have any questions afterwards.0 -
Paul_Steunebrink wrote:
...Let us know if you have any questions afterwards.
Thank you for responding. The suggested reading kind of confirms my understanding of how metadata via a sidecar XMP file works. I will try to be a bit more specific in my problem description.
The XMP file has an attribute "xmp:label" where Capture One and other applications typically put the name of a color for the color label value. It is called "Color Tag" in the Capture One Metadata tool.
Capture One sets xmp_label attribute in the XMP file as one of those shown here:
xmp:label="None" or
xmp:label="Red" or
xmp:label="Orange" or
xmp:label="Yellow" or
xmp:label="Green" or
xmp:label="Blue" or
xmp:label="Pink" or
xmp:label="Purple"
depending on me selecting one of the available color tags and then using Sync to update the XMP file.
If I select color tag Purple, it is straight forward to make Capture One update an existing xmp:label="Blue" to become xmp:label="Purple" in the XMP file. Likewise, it is straight forward to see this changed color tag in other applications (and LR is not involved here, by the way).
Now I quit Capture One and update the same XMP file again, changing only the xmp:label="Purple" to xmp:label="Yellow". I can do that using a text editor or some other image application, and saving the file. Other image applications will show me the yellow label. Capture One will not. No matter what combination I try, Capture One refuses to update its notion of the color tag being "Purple". I hoped Capture One should be able to do that, and for a while I believed the Metdata tool "..."->Reload Metadata would do that for me. Not for me, no.
The strange thing is, that if I manipulate the star rating using the exact same method as outlined above, only now manipulating the attribute "xmp:Rating". I can set xmp:Rating="0", "1", "2", "3", "4" or "5" using just about any software tool at my disposal. It is straight forward to have Capture One update the corresponding Rating value in Metadata tools showing 0, 1, 2, 3, 4 or 5 stars by using Reload.
So yes, I am confused, and the suggested reading did not make things any clearer to me.
What am I supposed to do to make Capture One read and update its Color Tag setting (xmp:label attribute) from the value set in the XMP-file like Capture One does for rating?0 -
Hi,
now it is so, because C1 writes the "new" notation xmp:label but don't read it. C1 read only old notation photoshop:urgency value.0 -
RobiWan wrote:
...C1 writes the "new" notation xmp:label but don't read it. C1 read only old notation photoshop:urgency value.
Thanks,
I will see if I can manage to make it work. The urgency attribute has only been depreciated about one decade by now and LR users already complain about LR not supporting the urgency attribute.0 -
RobiWan wrote:
The only way I know is to use a extra software ...to make Colorlabels compatible between C1 and other software. It reads and write both values correctly.
Thank you for the information.
I bought a license for the suggested software and will see what I can make of it. Color tagging appears to work as you suggested, and I managed to make Photo Mechanic work to the same level of completeness, 5 out of the 8 color tags available in Photo Mechanic.
In the order of selectable Color tags appearing in Capture One Metadata tool, the color to photoshop:urgency mapping appears to be:
"None" photoshop:urgency="0"
"Red" photoshop:urgency="1"
"Orange" photoshop:urgency="6"
"Yellow" photoshop:urgency="7"
"Green" photoshop:urgency="2"
"Blue" photoshop:urgency="3"
"Pink" photoshop:urgency="5"
"Purple" photoshop:urgency="5"
Capture One apparently uses the color name (xmp:label="Pink" or xmp:label="Purple") to select what color tag (pink or purple) to use when it sees photoshop:urgency="5" in the XMP-file (it isprobably not a bug). Photo Mechanic lets me set the fifth color label to "Pink" or to "Purple" to control Capture One color tag selection when urgency = 5, but this better be a once and for all decision on my part.
I wonder if these things are explained in Capture One documentation.0 -
OddS wrote:
"Pink" photoshop:urgency="5"
"Purple" photoshop:urgency="5"
That is a very old BUG that Phase One has never resolved ☹️
C1 has internal correct value (Database) but writes always wrong value in XMP file. The good news is - C1 writes correct value in the new notation "xmp:label" and if you open a picture with FastRawViewer than you have a correct value for both xmp:label and photoshop:urgency.0 -
And in Capture One v 9.1.3, 2 years later IT IS STILL NOT FIXED.
These guys either truly don't care or aren't competent enough to make the fix. Or both.
The truth hurts--hurts users more than it hurts the feelings of C1 developers.
I just confirmed by going back and forth with both pairs Photo Mechanic<->Capture One and Lightroom<->Capture One that Capture one will update xmp:label but will not read it. Changes to color made in Capture One were reflected in the other products, but not the reverse.
Oh well, we just pay for the software; we don't matter.0 -
lewisl wrote:
And in Capture One v 9.1.3, 2 years later IT IS STILL NOT FIXED.
The list of issues fixed in 9.1 for Windows includes (quoute from announced March 17. by Jim_DK) :
"Pink color Tag improperly mapped to Photoshop urgency"
Thus, there may be both will and intention to sort it out. I am on the road, testing the announced fix will just have to wait till I'm back home.
Could you be more specific on how you tested the announced fix and how you currently see the pink color tag mapping works (or fails)?0 -
With reference to my previous posting(s):
C1 version 9.1.1 Color Tag "Pink" in Metadata followed by a Sync Metadata sets the xmp:Label to "Pink" and the photoshop:urgency to "4" in the xmp file. (A bug in older C1 versions produced photoshop:urgency="5" for tag color Pink, causing color tag confusion with other applications).
C1 version 9.1.1 produces on my system (Windows):
"Pink" photoshop:urgency="4"
"Purple" photoshop:urgency="5"
Color tags now appear to exchange correctly between C1 and Photo Mechanic via xmp files. Photo Mechanic has 8 color tags urgency 1-8. C1 has 7 color tags, thus, I can of course only use color tags for urgency values 1-7, but my ban on urgency=4 has been lifted 😊0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare