Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Color labels wit C1

RobiWan
Is there a chance that dieverse bugs with colors are ever resolved?
1 The colors purple and violet write the same values ​​in the *. xmp file. So that no exchange with other programs such as Media Pro possible.

2 The values ​​for color markings are written as
<photoshop:Urgency>1</photoshop:Urgency>

For years, other Firman write the standard in the form of
xmp:Label="1"

Here no serious interaction with other software programs possible ☹️
0

Comments

4 comments

Date Votes
  • Hank
    Does anyone know if there is a way to correct this situation?

    I have investigated the handling of color "labels" by Capture One by using a few jpeg files with no "side car" xmp files just to keep things simple.

    1. Nikon NX2 and PhotoMechanic handle the color labels correctly and as they change the values are seen in each of these programs. Color labels seem to be in the XMP data not the IPTC data.

    2. Media Pro sees the correct color values on import and reloading "annotations" will import any changes.

    3. Capture One will import the color "labels" but after that a reload does not import the updated values.
    Syncing the metadata does not work and generally I will most likely avoid using sync metadata.

    4. The color values seen by Capture One do not match Media Pro (which is what I expected).
    4. Brown 8. Cyan and 9. Grey are missing
    5. is used for both Pink (magenta) and Purple

    I would like to have some way to at least be able to import changes to the color labels.
    0
  • RobiWan
    [quote="hsautter" wrote:
    Does anyone know if there is a way to correct this situation?
    5. is used for both Pink (magenta) and Purple


    For this time is this very bad situation.
    There is a BUG, because C1 is writing for 2 colors the same value in sidecard files.
    Phase One know about this BUG and situation, but they have no any plans to correct it.
    0
  • brianmerwin
    Please remember that this is a user to user forum, so the dev team does check in from time to time but the best thing you can do (for all of us) is to create a support case in order to report the bug and get it in to their queue and actually get it fixed. And I agree, this is kind of a big deal (at least for me).

    Thanks!
    0
  • RobiWan
    [quote="brianmerwin" wrote:
    Please remember that this is a user to user forum,


    I know. I have created a ticked, the answer was "it's correct, there is a Bug, but we are do nothing to resolve it now. We are thinking about new strategy".

    Thera are some basics features there are not working correctly and I find that its not customer friendly to tell "we known there is a bug but we are do nothing for now"
    0

Post is closed for comments.