XnView Software

Posted: **Wed Jun 16, 2021 9:03 pm**

Greetings. New user here. I am transitioning to Capture One and have been using XnView in the process to edit EXIF and view metadata. It's a welcomed piece of the puzzle I expect to keep around.

I think I have mostly figured out how best to configure preferences to complement Capture One, but a solution to one problem, if there's one, would help.

It's the way XnView reads and writes the creator contact data from/to the sidecar XMP. Here is what I see. The yyIPTC… data came from XnView. The xx… data came from Capture One. Both end up in the XMP sidecar simultaneously. Flat entries vs. structured CreatorContactInfo entries. Hence these data are not passed back and forth.

Code: Select all

   <Iptc4xmpCore:CiAdrCity>yyIPTC City</Iptc4xmpCore:CiAdrCity>
   <Iptc4xmpCore:CiAdrCtry>yyIPTC Country</Iptc4xmpCore:CiAdrCtry>
   <Iptc4xmpCore:CiAdrExtadr>yyIPTC Contact</Iptc4xmpCore:CiAdrExtadr>
   <Iptc4xmpCore:CiAdrPcode>yyIPTC Zip</Iptc4xmpCore:CiAdrPcode>
   <Iptc4xmpCore:CiAdrRegion>yyIPTC State</Iptc4xmpCore:CiAdrRegion>
   <Iptc4xmpCore:CiEmailWork>yyIPTC email</Iptc4xmpCore:CiEmailWork>
   <Iptc4xmpCore:CiTelWork>yyIPTC tel</Iptc4xmpCore:CiTelWork>
   <Iptc4xmpCore:CiUrlWork>yyIPTC website</Iptc4xmpCore:CiUrlWork>
   <Iptc4xmpCore:CreatorContactInfo>
    <rdf:Description>
     <Iptc4xmpCore:CiEmailWork>xxEmail</Iptc4xmpCore:CiEmailWork>
     <Iptc4xmpCore:CiTelWork>xxPhone</Iptc4xmpCore:CiTelWork>
     <Iptc4xmpCore:CiAdrPcode>xxZip</Iptc4xmpCore:CiAdrPcode>
     <Iptc4xmpCore:CiUrlWork>xxWebsite</Iptc4xmpCore:CiUrlWork>
     <Iptc4xmpCore:CiAdrExtadr>xxAddress</Iptc4xmpCore:CiAdrExtadr>
     <Iptc4xmpCore:CiAdrCity>xxCity</Iptc4xmpCore:CiAdrCity>
     <Iptc4xmpCore:CiAdrCtry>xxCountry</Iptc4xmpCore:CiAdrCtry>
     <Iptc4xmpCore:CiAdrRegion>xxState</Iptc4xmpCore:CiAdrRegion>
    </rdf:Description>
   </Iptc4xmpCore:CreatorContactInfo>

Aperture's export, by the way, also writes structured data the same way. I'm not familiar with how other software, Lightroom for example, deals with this.

So my questions are:
- Is there a configuration option I'm missing to change this?
- If not, is there a reason for this? Does other software need or prefer the flat structure in external XMP?

Thanks much and apologies if this has been discussed or documented. I did search.

Mac M1 Mini, macOS 11.4.
Edit XMP set to Mode: XMP only

Posted: **Mon Jun 21, 2021 2:50 pm**

could you send me a sample file, please?

Posted: **Wed Jun 23, 2021 5:24 pm**

Thanks Pierre,

I attached the xmp. Not exactly the same data from my previous post but it shows the same thing. The associated tif, while not that large, is too large to attach, even zipped. It's probably not relevant but let me know if that will help and how best to get it to you. (Or I could build a new example with a jpg.)

I've since been playing with Photo Mechanic and it also sees the hierarchical data when I Load… the xmp into the metadata info or template.

I appreciate you looking into this.

Cheers

Posted: **Fri Jun 25, 2021 1:48 pm**

Thanks to your detailed description I can reproduce the problem.

Posted: **Thu Sep 16, 2021 12:23 pm**

This problem is supposed to be fixed in XnView MP 0.99.0. Please check and confirm the bug fix here.

XnView Software

Creator Contact XMP Data to/from Capture One

Creator Contact XMP Data to/from Capture One

Re: Creator Contact XMP Data to/from Capture One

Re: Creator Contact XMP Data to/from Capture One

Re: Creator Contact XMP Data to/from Capture One

Re: Creator Contact XMP Data to/from Capture One