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

IPTC not readable with other software (Photoshop CS6)

Comments

8 comments

  • Paul Steunebrink
    Need a bit more information:
    - how is your Metadata setting in Preferences > Image tab
    - do you review in PS an image that is viewed in CO8, or processed/exported to TIFF/JPEG/... from CO8?

    Hint: CO8 does not store metadata like IPTC inside the image file itself, unless/until you process. It is stored for CO8 to use, and the location depends on whether you use session or catalog. In addition, you can enable XMP in CO8, which allows PS to read it. This works for session only, as far as I understand.

    This might help understanding why CO8 IPTC data is not seen in PS.
    0
  • Phil Ricordel
    Hi Paul,

    I try to answer your question:

    - Good point here, none is the selected choice and none of the checkbox is checked
    - I review an image (.JPG) where I used CO8 to set the IPTC (easier than PS by the way). The .JPG had been generated before from Capture NX2

    I understand your explanation, but therfore which choice should I select into the droplist ?
    - None is not Ok I guess
    - Load or total synchronization ?

    My goal is to have the field read by the Hmtl code of the Web site in order to be able to display these information at the same time the image is viewed.
    0
  • Paul Steunebrink
    Assuming you work with session, you should set the preference metadata setting to Full Sync. This will allow CO8 to write (and read) IPTC to the XMP file. Photoshop should now be able to see it. But it is still not written into the JPEG file.

    I suggest to take a different path. Process (export) the JPEG to JPEG with CO8 and you are done. No hassle with preference setting and XMP files.
    0
  • Phil Ricordel
    Thanks Paul,

    Full sync working is not working even in sesssion.

    I do the following :
    - .JPG image, I edit into CO8 adding the IPTC information (with the Full sync parameter on)
    - Try to open with PS => nothing visible (XMP sidecar file is generated)
    - Try to save the .JPG under another name (name_2) => nothing visible using PS (XMP sidecar file generated)

    If you open the sidecar file :
    - .XMP and .XMP_2 contains the same information where one can see the information entered.

    My understanding is CO8 is doing the job registering the information into the .XMP file, but for a reason I don not see the PS program cannot read the information stored. I should miss something somewhere.
    0
  • Phil Ricordel
    Morning ,

    I still have no chance to solve this problem. Anyone have an idea ?
    0
  • mli20
    Please check that you have jpeg editing enabled in COP8 Preferences.

    "Save As" has no meaning within the scope of COP8. You must export to a new file. That will bake the metadata into the imagefile itself. XMPs are not read by any software I'm aware of when it comes to jpegs.

    Good luck.

    Cheers,
    Mogens
    0
  • Olaf Pokorny
    I also miss the possibility to write IPTC metadata directly into the image files. For now I still have to use Aperture to get this job done. By default Aperture also stores metadata only in its own library and writes them into the files during export. But in the menu (or by keyboard shortcut) I have the option to write all metadata into the original files. I wish to have this feature in CaptureOne. Could save me a lot of time...
    0
  • Paul Steunebrink
    [quote="op" wrote:
    I also miss the possibility to write IPTC metadata directly into the image files. For now I still have to use Aperture to get this job done. By default Aperture also stores metadata only in its own library and writes them into the files during export. But in the menu (or by keyboard shortcut) I have the option to write all metadata into the original files. I wish to have this feature in CaptureOne. Could save me a lot of time...

    Won't happen. Number one rule of Capture One is that it does not write into the original (raw) file to ensure 100% integrity. Maybe you can review your workflow to make it fit with Capture One.
    0

Post is closed for comments.