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. ⚠️

Keywords repeatedly generated on JPG files

NN125462
Having been on holiday I have been processing files for a photo album taken both by myself (in Samsung .SRW RAW format) and my wife (with Panasonic JPEG format). I use Photo Supreme as my DAM to import all images to my PC and I use a very similar process for importing both .SRW and .JPG files into my library.

For both file types I set them to read only on import to force Photo Supreme to create sidecar .xmp files that can be read, shared and written to with Capture One.

I have no problem with the .SRW files throughout the processing workflow.

However everytime I select a JPG file in Capture one it is creating additional keywords in the XMP file.

For Example if I have a .xmp file containing "place" and "location" as keywords, after I select it in C1 in the browser and then look at another file, if I come back to it it is likely to have a list of keywords such as:

place
location
location
place

And for some this list of 2 or 3 keywords now stretches 20 or more deep and just keeps growing.

Just before I raise a ticket, I just wondered if anyone had seen this behaviour before and has any views on what might be causing it.
0

Comments

5 comments

Date Votes
  • mli20
    Usually there will not be xmp-files associated with jpegs: The metadata can be stored within the jpegs themselves.

    Maybe then C1 gets confused seeing jpegs together with similarnamed xmp-files, reading the info twice.

    Are you using catalogs?

    The same apparent problem exist with raw files though:

    http://mli20.smugmug.com/photos/i-9K3KbLZ/0/S/i-9K3KbLZ-S.jpg

    The reason for this might be due to:

    - The redundancy built into the C1 catalog leads to C1 at some point getting confused.
    - The xmp sync in C1 failing in some way

    I didn't report this to tech support as I have stopped using catalogs in C1, because of this and other reasons.

    Cheers,
    Mogens
    0
  • Drew Altdo
    Turn off the option to "Prefer Sidecar XMP over Embedded Metadata" to avoid this duplication.
    We're looking into it but it seems that Capture One reads the XMP twice when it should only reference it once.
    0
  • NN125462
    OK - thanks for the updates.

    Yes I am using catalogs.

    'm a bit paranoid about loosing/corrupting data and I don't like ANYTHING modifying my original photo files - that includes JPG as well as DNG RAW files that my Pentax uses. So I have configured my DAM programme to set the READ ONLY bit on all imported files. Thus the keyword data must only be stored in sidecar .xmp files. This wasn't a problem in earlier versions of C1 Pro.

    If I turn off "Prefer Sidecar XMP over Embedded Metadata" will C1 Pro still write any changes I make to exif data (as sometimes I will add a keyword from C1 if I have overlooked it on initial import to disk)

    I'll switch it off anyway and see how I get on.
    0
  • Drew Altdo
    [quote="NN125462" wrote:
    If I turn off "Prefer Sidecar XMP over Embedded Metadata" will C1 Pro still write any changes I make to exif data (as sometimes I will add a keyword from C1 if I have overlooked it on initial import to disk)


    Capture One is a Read Only software so it will not write to the RAW and embed data.
    With this setting OFF however, you can of course write to the IPTC fields and then sync those to a sidecar XMP (or amend an existing one).
    0
  • Permanently deleted user
    Hi,

    I have just been going through the same sort of problem, but on the Mac side (it affects TIFFs as well) and it has been driving me demented. I will try your syncing suggestions. Thanks.

    Andrew
    0

Post is closed for comments.